File formats:

Also available: XML file for editing

 

Status:

PROPOSED STANDARD

Updates:

RFC 8445, RFC 8838

Authors:

C. Holmberg
J. Uberti

Stream:

IETF

Source:

ice (art)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  10.17487/RFC8863

Discuss this RFC: Send questions or comments to the mailing list ice@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 8863

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.

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.