RFC 8863: Interactive Connectivity Establishment Patiently Awaiting Connectivity (ICE PAC)
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC8863
- Published
- January 2021
- Authors
- C. Holmberg; J. Uberti
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 6
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8840A Session Initiation Protocol (SIP) Usage for Incremental Provisioning of Candidates for the Interactive Connectivity Establishment (Trickle ICE)Updated
January 2021
- RFC 7825A Network Address Translator (NAT) Traversal Mechanism for Media Controlled by the Real-Time Streaming Protocol (RTSP)Current
December 2016
- RFC 6544TCP Candidates with Interactive Connectivity Establishment (ICE)Current
March 2012
- RFC 8829JavaScript Session Establishment Protocol (JSEP)Obsoleted
January 2021
- RFC 8656Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)Current
February 2020
- RFC 9429JavaScript Session Establishment Protocol (JSEP)Current
April 2024
- RFC 8016Mobility with Traversal Using Relays around NAT (TURN)Current
November 2016
- RFC 5770Basic Host Identity Protocol (HIP) Extensions for Traversal of Network Address TranslatorsCurrent
April 2010
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?