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

Document Type Active Internet-Draft (v6ops WG)
Last updated 2020-03-09
Replaces draft-gont-v6ops-cpe-slaac-renum
Stream IETF
Intended RFC status (None)
Formats plain text pdf htmlized bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
IPv6 Operations Working Group (v6ops)                            F. Gont
Internet-Draft                                              SI6 Networks
Intended status: Informational                                   J. Zorz
Expires: September 10, 2020                                Go6 Institute
                                                            R. Patterson
                                                                  Sky UK
                                                           March 9, 2020

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

Abstract

   In scenarios where network configuration information related to IPv6
   prefixes 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 prefixes), hosts on the
   local network will continue using stale prefixes 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.

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 September 10, 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

Gont, et al.           Expires September 10, 2020               [Page 1]
Internet-Draft       Reaction to Renumbering Events           March 2020

   (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.  Improved Customer Edge Router Behavior  . . . . . . . . . . .   2
     2.1.  Interface Between DHCPv6-PD and SLAAC . . . . . . . . . .   3
     2.2.  Signaling Stale Configuration Information . . . . . . . .   3
   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   5.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   4
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

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

   This document specifies improvements to Customer Edge (CE) Routers
   that help mitigate the aforementioned problem for residential or
   small office scenarios.

2.  Improved Customer Edge Router Behavior

   This section specifies and clarifies requirements for Customer Edge
   Routers -- particularly when they advertise with Stateless Address
   Autoconfiguration (SLAAC) [RFC4862] prefixes learned via
   DHCPv6-Prefix Delegation (DHCPv6-PD) [RFC8415] or prefixes derived
   from them -- that can help mitigate the problem discussed in
   Section 1.  This would obviously make robustness dependent on the
   Customer Edge Router (on which the user or ISP may have no control),
   as opposed to the host itself.

   The updated behaviour is as follows:

Gont, et al.           Expires September 10, 2020               [Page 2]
Internet-Draft       Reaction to Renumbering Events           March 2020

   o  CE routers MUST signal stale configuration information as
Show full document text