Discovery of path characteristics using STUN
draft-reddy-tram-stun-path-data-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2015-07-24 (latest revision 2015-01-20) | ||
| 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) | ||
https://www.ietf.org/archive/id/draft-reddy-tram-stun-path-data-01.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 path characteristics, which may affect the user experience. This document describes a mechanism for an endpoint to discover the path characteristics using Session Traversal Utilities for NAT (STUN) messages. The measurement information can then be used to influence the endpoint's Interactive Connectivity Establishment (ICE) candidate pair selection algorithm.
Authors
Reddy K
(tireddy@cisco.com)
Dan Wing
(dwing@cisco.com)
Paal-Erik Martinsen
(palmarti@cisco.com)
Varun Singh
(varun@callstats.io)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)