Interactive Connectivity Establishment Patiently Awaiting Connectivity (ICE PAC)
draft-holmberg-ice-pac-01
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Christer Holmberg , Justin Uberti | ||
Last updated | 2019-03-11 | ||
Replaced by | draft-ietf-ice-pac | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-ietf-ice-pac | |
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
During the process of creating a peer-to-peer connection, ICE implementations can encounter situations where they have no candidate pairs to check, and, as a result, conclude that ICE processing has failed. However, because additional candidate pairs can be discovered during ICE processing, declaring failure at this point may be premature. This document discusses when these situations can occur and proposes a way to avoid premature failure.
Authors
Christer Holmberg
Justin Uberti
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)