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)
Expired & archived
|
|
|---|---|---|---|
| Authors | Tirumaleswar Reddy.K , Dan Wing , Bill Ver Steeg , Reinaldo Penno , Varun Singh | ||
| Last updated | 2014-04-12 (Latest revision 2013-10-09) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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
Tirumaleswar Reddy.K
Dan Wing
Bill Ver Steeg
Reinaldo Penno
Varun Singh
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)