Skip to main content

Interactive Connectivity Establishment Patiently Awaiting Connectivity (ICE PAC)
RFC 8863

Revision differences

Document history

Date By Action
2021-04-22
Gunter Van de Velde Closed request for Last Call review by OPSDIR with state 'Overtaken by Events'
2021-01-18
(System)
Received changes through RFC Editor sync (created alias RFC 8863, changed abstract to 'During the process of establishing peer-to-peer connectivity, Interactive Connectivity Establishment (ICE) …
Received changes through RFC Editor sync (created alias RFC 8863, changed abstract to '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.', changed pages to 6, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2021-01-18, changed IESG state to RFC Published, created updates relation between draft-ietf-ice-pac and RFC 8445, created updates relation between draft-ietf-ice-pac and RFC 8838)
2021-01-18
(System) RFC published