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

rfc-editor@rfc-editor.org Tue, 19 January 2021 00:47 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 3CF183A1056 for <ietf-announce@ietfa.amsl.com>; Mon, 18 Jan 2021 16:47:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id IFk1ixophwYM for <ietf-announce@ietfa.amsl.com>; Mon, 18 Jan 2021 16:47:20 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08F413A10F2 for <ietf-announce@ietf.org>; Mon, 18 Jan 2021 16:47:10 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 94D79F407CD; Mon, 18 Jan 2021 16:46:54 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8863 on Interactive Connectivity Establishment Patiently Awaiting Connectivity (ICE PAC)
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, ice@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20210119004654.94D79F407CD@rfc-editor.org>
Date: Mon, 18 Jan 2021 16:46:54 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/i0ox47hcGXzyu8CinFDvxEtVFnA>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jan 2021 00:47:29 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 8863

        Title:      Interactive Connectivity Establishment 
                    Patiently Awaiting Connectivity (ICE PAC)
        Author:     C. Holmberg,
                    J. Uberti
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2021
        Mailbox:    christer.holmberg@ericsson.com,
        Pages:      6
        Updates:    RFC 8445, RFC 8838

        I-D Tag:    draft-ietf-ice-pac-06.txt

        URL:        https://www.rfc-editor.org/info/rfc8863

        DOI:        10.17487/RFC8863

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.

This document is a product of the Interactive Connectivity Establishment Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC