Improving the Reaction of Customer Edge Routers to Renumbering Events
draft-ietf-v6ops-cpe-slaac-renum-04

Document Type Active Internet-Draft (v6ops WG)
Last updated 2020-09-10 (latest revision 2020-08-25)
Replaces draft-gont-v6ops-cpe-slaac-renum
Stream IETF
Intended RFC status Informational
Formats plain text pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Doc Shepherd Follow-up Underway
Document shepherd Owen DeLong
Shepherd write-up Show (last changed 2020-07-07)
IESG IESG state Waiting for AD Go-Ahead
Consensus Boilerplate Yes
Telechat date
Responsible AD Warren Kumari
Send notices to Owen DeLong <owen@delong.com>, v6ops-chairs@ietf.org
IANA IANA review state IANA OK - No Actions Needed
IPv6 Operations Working Group (v6ops)                            F. Gont
Internet-Draft                                              SI6 Networks
Updates: 7084 (if approved)                                      J. Zorz
Intended status: Informational                                  6connect
Expires: February 26, 2021                                  R. Patterson
                                                                  Sky UK
                                                                 B. Volz
                                                                   Cisco
                                                         August 25, 2020

 Improving the Reaction of Customer Edge Routers to Renumbering Events
                  draft-ietf-v6ops-cpe-slaac-renum-04

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.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on February 26, 2021.

Gont, et al.            Expires February 26, 2021               [Page 1]
Internet-Draft       Reaction to Renumbering Events          August 2020

Copyright Notice

   Copyright (c) 2020 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   3
   3.  Improved Customer Edge Router Behavior  . . . . . . . . . . .   3
     3.1.  Interface Between WAN-side and LAN-side . . . . . . . . .   4
     3.2.  LAN-side Option Lifetimes . . . . . . . . . . . . . . . .   5
     3.3.  Signaling Stale Configuration Information . . . . . . . .   6
   4.  Recommended Option Lifetimes Configuration Values . . . . . .   8
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   8
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   9
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   In scenarios where network configuration information becomes invalid
   without any explicit signaling of that condition, nodes on the local
   network will continue using stale information for an unacceptably
   long period of time, thus resulting in connectivity problems.  This
   problem is documented in detail in [I-D.ietf-v6ops-slaac-renum].

   This document specifies improvements to Customer Edge (CE) Routers
   that help mitigate the aforementioned problem for residential and
   small office scenarios.  It specifies recommendations for the default
   behavior of CE Routers, and does not preclude the availability of
   configuration knobs that might allow an operator or user to manually-
   configure the CE Router to deviate from these recommendations.  This
   document updates RFC7084.

Gont, et al.            Expires February 26, 2021               [Page 2]
Internet-Draft       Reaction to Renumbering Events          August 2020
Show full document text