[v6ops] Last Call: <draft-ietf-v6ops-cpe-slaac-renum-06.txt> (Improving the Reaction of Customer Edge Routers to Renumbering Events) to Best Current Practice

The IESG <iesg-secretary@ietf.org> Thu, 31 December 2020 00:00 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: v6ops@ietf.org
Delivered-To: v6ops@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AD293A0BEE; Wed, 30 Dec 2020 16:00:09 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 7.24.0
Auto-Submitted: auto-generated
Precedence: bulk
CC: Owen DeLong <owen@delong.com>, draft-ietf-v6ops-cpe-slaac-renum@ietf.org, owen@delong.com, v6ops-chairs@ietf.org, v6ops@ietf.org, warren@kumari.net
Reply-To: last-call@ietf.org
Sender: <iesg-secretary@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <160937280919.30572.6826550493774973607@ietfa.amsl.com>
Date: Wed, 30 Dec 2020 16:00:09 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/q4ClXZBf6jjkekt7xditBjPaKQc>
Subject: [v6ops] Last Call: <draft-ietf-v6ops-cpe-slaac-renum-06.txt> (Improving the Reaction of Customer Edge Routers to Renumbering Events) to Best Current Practice
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Dec 2020 00:00:10 -0000

The IESG has received a request from the IPv6 Operations WG (v6ops) to
consider the following document: - 'Improving the Reaction of Customer Edge
Routers to Renumbering Events'
  <draft-ietf-v6ops-cpe-slaac-renum-06.txt> as Best Current Practice

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2021-01-13. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

This is the second IETF LC for this document -- it was originally LCed as Informational. IESG Eval suggested that it was more BCP-like, and so the document was returned to the V6OPS WG, and re-WGLCed as BCP. It is now being IETF LCed as BCP, and will then go through IESG Eval again.... and the process-elves rejoice...



Abstract


   In scenarios where network configuration information becomes invalid
   without any explicit signaling of that condition (such as when a
   Customer Edge Router crashes and reboots without knowledge of the
   previously-employed configuration information), hosts on the local
   network will continue using stale network configuration information
   for an unacceptably long period of time, thus resulting in
   connectivity problems.  This document specifies improvements to
   Customer Edge Routers that help mitigate the aforementioned problem
   for typical residential and small office scenarios.  This document
   updates RFC7084.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-v6ops-cpe-slaac-renum/



No IPR declarations have been submitted directly on this I-D.


The document contains these normative downward references.
See RFC 3967 for additional information: 
    rfc4191: Default Router Preferences and More-Specific Routes (Proposed Standard - IETF stream)
    rfc4861: Neighbor Discovery for IP version 6 (IPv6) (Draft Standard - IETF stream)
    rfc4862: IPv6 Stateless Address Autoconfiguration (Draft Standard - IETF stream)
    rfc8106: IPv6 Router Advertisement Options for DNS Configuration (Proposed Standard - IETF stream)
    rfc8415: Dynamic Host Configuration Protocol for IPv6 (DHCPv6) (Proposed Standard - IETF stream)