BCP 234, RFC 9096 on Improving the Reaction of Customer Edge Routers to IPv6 Renumbering Events

rfc-editor@rfc-editor.org Mon, 30 August 2021 23:03 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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 973093A261C; Mon, 30 Aug 2021 16:03:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 slgv2nYiVSSs; Mon, 30 Aug 2021 16:03:23 -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 D311D3A2618; Mon, 30 Aug 2021 16:03:23 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 46F2FF4074E; Mon, 30 Aug 2021 16:03:04 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 234, RFC 9096 on Improving the Reaction of Customer Edge Routers to IPv6 Renumbering Events
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, v6ops@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20210830230304.46F2FF4074E@rfc-editor.org>
Date: Mon, 30 Aug 2021 16:03:04 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/-DcpDR7lRwHaA6atZUcvrk29tM8>
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: Mon, 30 Aug 2021 23:03:30 -0000

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

        BCP 234        
        RFC 9096

        Title:      Improving the Reaction of Customer 
                    Edge Routers to IPv6 Renumbering Events 
        Author:     F. Gont,
                    J. Žorž,
                    R. Patterson,
                    B. Volz
        Status:     Best Current Practice
        Stream:     IETF
        Date:       August 2021
        Mailbox:    fgont@si6networks.com,
                    jan@6connect.com,
                    richard.patterson@sky.uk,
                    bevolz@gmail.com
        Pages:      11
        Updates:    RFC 7084
        See Also:   BCP 234

        I-D Tag:    draft-ietf-v6ops-cpe-slaac-renum-08.txt

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

        DOI:        10.17487/RFC9096

This document specifies improvements to Customer Edge routers that
help mitigate the problems that may arise when network configuration
information becomes invalid without any explicit signaling of that
condition to the local nodes. This document updates RFC 7084.

This document is a product of the IPv6 Operations 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