Interactive Connectivity Establishment Patiently Awaiting Connectivity (ICE PAC)
draft-ietf-ice-pac-06

Document Type Active Internet-Draft (ice WG)
Last updated 2020-04-29
Replaces draft-holmberg-ice-pac
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Nils Ohlmeier
Shepherd write-up Show (last changed 2019-10-15)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Murray Kucherawy
Send notices to Nils Ohlmeier <nohlmeier@mozilla.com>
IANA IANA review state Version Changed - Review Needed
IANA action state No IANA Actions
RFC Editor RFC Editor state EDIT
ICE Working Group                                            C. Holmberg
Internet-Draft                                                  Ericsson
Updates: 8445 (if approved)                                    J. Uberti
Intended status: Standards Track                                  Google
Expires: October 31, 2020                                 April 29, 2020

 Interactive Connectivity Establishment Patiently Awaiting Connectivity
                               (ICE PAC)
                         draft-ietf-ice-pac-06

Abstract

   During the process of establishing peer-to-peer connectivity, 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 and updates
   RFC8445 and RFC XXXX 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.

   [RFC EDITOR NOTE: Please replace RFC XXXX with the RFC number of
   draft-ietf-ice-trickle once it has been published.  Please also
   indicate that this specification updates RFC XXXX.]

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on October 31, 2020.

Holmberg & Uberti       Expires October 31, 2020                [Page 1]
Internet-Draft                   ICE PAC                      April 2020

Copyright Notice

   Copyright (c) 2020 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Relevant Scenarios  . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  No Candidates From Peer . . . . . . . . . . . . . . . . .   3
     3.2.  All Candidates Discarded  . . . . . . . . . . . . . . . .   4
     3.3.  Immediate Candidate Pair Failure  . . . . . . . . . . . .   4
   4.  Update to RFC 8445  . . . . . . . . . . . . . . . . . . . . .   4
   5.  Update to RFC XXXX  . . . . . . . . . . . . . . . . . . . . .   5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   7.  IANA considerations . . . . . . . . . . . . . . . . . . . . .   6
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   9.  Normative References  . . . . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   [RFC8445] describes a protocol, Interactive Connectivity
   Establishment (ICE), for Network Address Translator (NAT) traversal
   for UDP-based communication.

   When using ICE, endpoints will typically exchange ICE candidates,
   form a list of candidate pairs, and then test each candidate pair to
   see if connectivity can be established.  If the test for a given pair
   fails, it is marked accordingly, and if all pairs have failed, the
   overall ICE process typically is considered to have failed.

   During the process of connectivity checks, additional candidates may
   be created as a result of successful inbound checks from the remote
   peer.  Such candidates are referred to as peer-reflexive candidates,
   and once discovered, will be used to form new candidate pairs which
   will be tested like any other.  However, there is an inherent problem

Holmberg & Uberti       Expires October 31, 2020                [Page 2]
Internet-Draft                   ICE PAC                      April 2020

   here; if, before learning about any peer-reflexive candidates, an
   endpoint runs out of candidate pairs to check, either because it has
Show full document text