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

The information below is for an old version of the document
Document Type Active Internet-Draft (ice WG)
Last updated 2019-03-27 (latest revision 2019-03-26)
Replaces draft-holmberg-ice-pac
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd Nils Ohlmeier
IESG IESG state I-D Exists
Consensus Boilerplate Yes
Telechat date
Responsible AD Adam Roach
Send notices to Nils Ohlmeier <nohlmeier@mozilla.com>
ICE Working Group                                            C. Holmberg
Internet-Draft                                                  Ericsson
Updates: 8445 (if approved)                                    J. Uberti
Intended status: Standards Track                                  Google
Expires: September 27, 2019                               March 26, 2019

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

Abstract

   During the process of creating a peer-to-peer connection, ICE
   implementations 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 proposes a way to avoid premature failure.

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 September 27, 2019.

Copyright Notice

   Copyright (c) 2019 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

Holmberg & Uberti      Expires September 27, 2019               [Page 1]
Internet-Draft                   ICE PAC                      March 2019

   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  . . . . . . . . . . . . . . . .   3
     3.3.  Immediate Candidate Pair Failure  . . . . . . . . . . . .   4
   4.  Update to RFC 8445  . . . . . . . . . . . . . . . . . . . . .   4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   6.  IANA considerations . . . . . . . . . . . . . . . . . . . . .   5
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

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

   Typically, when using ICE, endpoints will exchange candidate
   addresses, 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 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 race
   condition here; if, before learning about any peer-reflexive
   candidates, an endpoint runs out of candidate pairs to check, either
   because it has none, or it considers them all to have failed, it will
   prematurely declare failure and terminate ICE processing.  This race
   condition can occur in many common situations.

   This specification updates [RFC8445], by simply requiring that an
   endpoint wait a minimum amount of time before declaring ICE failure,
   even if there are no candidate pairs to check, or if all candidate
   pairs have failed.  This delay provides enough time for the discovery

Holmberg & Uberti      Expires September 27, 2019               [Page 2]
Show full document text