ICE and STUN Timing Experiments for WebRTC
draft-jennings-ice-rtcweb-timing-01
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Cullen Fluffy Jennings | ||
Last updated | 2017-01-09 (Latest revision 2016-07-08) | ||
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
This draft summarizes the results in some experiments looking at the impact of proposed changes to ICE based on the latest consumer NATs. It looks and the amount of non congestion controlled bandwidth a browser can use and the impacts of that on ICE timing. This draft is not meant to become an RFC. It is purely information to help guide development of other specifications.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)