[rfc-dist] RFC 9386 on IPv6 Deployment Status

rfc-editor@rfc-editor.org Thu, 20 April 2023 00:59 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: rfc-dist@ietfa.amsl.com
Delivered-To: rfc-dist@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58064C16B5AE; Wed, 19 Apr 2023 17:59:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.948
X-Spam-Level:
X-Spam-Status: No, score=-3.948 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aakEgNH5wC4T; Wed, 19 Apr 2023 17:59:42 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB6DDC15155A; Wed, 19 Apr 2023 17:59:42 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 8E4774C093; Wed, 19 Apr 2023 17:59:42 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, v6ops@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20230420005942.8E4774C093@rfcpa.amsl.com>
Date: Wed, 19 Apr 2023 17:59:42 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-dist/QUbiWBzOW6n69qPiSl0s7ahI90U>
Subject: [rfc-dist] RFC 9386 on IPv6 Deployment Status
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Apr 2023 00:59:46 -0000

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

        
        RFC 9386

        Title:      IPv6 Deployment Status 
        Author:     G. Fioccola,
                    P. Volpato,
                    J. Palet Martinez,
                    G. Mishra,
                    C. Xie
        Status:     Informational
        Stream:     IETF
        Date:       April 2023
        Mailbox:    giuseppe.fioccola@huawei.com,
                    paolo.volpato@huawei.com,
                    jordi.palet@theipv6company.com,
                    gyan.s.mishra@verizon.com,
                    xiechf@chinatelecom.cn
        Pages:      37
        Obsoletes:  RFC 6036

        I-D Tag:    draft-ietf-v6ops-ipv6-deployment-10.txt

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

        DOI:        10.17487/RFC9386

This document provides an overview of the status of IPv6 deployment
in 2022. Specifically, it looks at the degree of adoption of IPv6 in
the industry, analyzes the remaining challenges, and proposes further
investigations in areas where the industry has not yet taken a clear
and unified approach in the transition to IPv6. It obsoletes RFC
6036.

This document is a product of the IPv6 Operations Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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