Interactive Connectivity Establishment Patiently Awaiting Connectivity
RFC 8863, “Interactive Connectivity Establishment Patiently Awaiting Connectivity”, is a Proposed Standard document published in January 2021 by C. Holmberg, J. Uberti. It updates RFC 8445, RFC 8838. The canonical text is published by the RFC Editor.
Abstract
During the process of establishing peer-to-peer connectivity, Interactive Connectivity Establishment (ICE) agents 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.
This document updates RFCs 8445 and 8838 by requiring that an ICE agent wait a minimum amount of time before declaring ICE failure, even if there are no candidate pairs left to check.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 8863 is hosted at rfc-editor.org. Available in HTML,TXT,PDF,XML.
- RFC 8862 Best Practices for Securing RTP Media Signaled with SIP
- RFC 8864 Negotiation Data Channels Using the Session Description Protocol
- RFC 8861 Sending Multiple RTP Streams in a Single RTP Session: Grouping RTP Control Protocol Reception Statistics and Other Feedback
- RFC 8865 T.140 Real-Time Text Conversation over WebRTC Data Channels
- RFC 8860 Sending Multiple Types of Media in a Single RTP Session
- RFC 8866 SDP: Session Description Protocol
- RFC 8859 A Framework for Session Description Protocol Attributes When Multiplexing
- RFC 8867 Test Cases for Evaluating Congestion Control for Interactive Real- Time Media