Improving ICE Interface Selection Using Port Control Protocol (PCP) Flow Extension
draft-reddy-mmusic-ice-best-interface-pcp-00

Document Type Expired Internet-Draft (individual)
Last updated 2014-04-12 (latest revision 2013-10-09)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-reddy-mmusic-ice-best-interface-pcp-00.txt

Abstract

A host with multiple interfaces needs to choose the best interface for communication. Oftentimes, this decision is based on a static configuration and does not consider the link characteristics of that interface, which may affect the user experience. This document describes a mechanism for an endpoint to query the link characteristics from the access router (the router at the other end of the endpoint's access link) using a Port Control Protocol (PCP) Flow Extension. This information influences endpoint's Interactive Connectivity Establishment (ICE) candidate selection algorithm.

Authors

Reddy K (tireddy@cisco.com)
Dan Wing (dwing@cisco.com)
Bill Steeg (billvs@cisco.com)
Reinaldo Penno (repenno@cisco.com)
Varun Singh (varun.singh@iki.fi)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)