[rfc-dist] BCP 217, RFC 8421 on Guidelines for Multihomed and IPv4/IPv6 Dual-Stack Interactive Connectivity Establishment (ICE)

rfc-editor@rfc-editor.org Thu, 19 July 2018 22:28 UTC

Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73526130E2B for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 19 Jul 2018 15:28:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.201
X-Spam-Level:
X-Spam-Status: No, score=-5.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ok7SUoXSh65w for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 19 Jul 2018 15:28:44 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD24C130E3A for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Thu, 19 Jul 2018 15:28:44 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id B4381B81B57; Thu, 19 Jul 2018 15:28:37 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 3E82FB81B56; Thu, 19 Jul 2018 15:28:37 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20180719222837.3E82FB81B56@rfc-editor.org>
Date: Thu, 19 Jul 2018 15:28:37 -0700
Subject: [rfc-dist] BCP 217, RFC 8421 on Guidelines for Multihomed and IPv4/IPv6 Dual-Stack Interactive Connectivity Establishment (ICE)
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, ice@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: rfc-dist <rfc-dist-bounces@rfc-editor.org>

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

        BCP 217        
        RFC 8421

        Title:      Guidelines for Multihomed and IPv4/IPv6 Dual-Stack 
                    Interactive Connectivity Establishment (ICE) 
        Author:     P. Martinsen,
                    T. Reddy,
                    P. Patil
        Status:     Best Current Practice
        Stream:     IETF
        Date:       July 2018
        Mailbox:    palmarti@cisco.com, 
                    TirumaleswarReddy_Konda@McAfee.com, 
                    praspati@cisco.com
        Pages:      9
        Characters: 20268
        See Also:   BCP 217

        I-D Tag:    draft-ietf-ice-dualstack-fairness-07.txt

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

        DOI:        10.17487/RFC8421

This document provides guidelines on how to make Interactive
Connectivity Establishment (ICE) conclude faster in multihomed and
IPv4/IPv6 dual-stack scenarios where broken paths exist.  The
provided guidelines are backward compatible with the original ICE
specification (see RFC 5245).

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


BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for 
improvements. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

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
_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org