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

Document Type Active Internet-Draft (individual)
Last updated 2019-11-01
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
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: May 4, 2020
                                                            R. Patterson
                                                                  Sky UK
                                                        November 1, 2019

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

Abstract

   In scenarios where network configuration information related to IPv6
   prefixes becomes invalid without any explicit signaling of that
   condition (such as when a CPE 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 May 4, 2020.

Copyright Notice

   Copyright (c) 2019 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 May 4, 2020                  [Page 1]
Internet-Draft       Reaction to Renumbering Events        November 2019

   (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 CPE behavior . . . . . . . . . . . . . . . . . . . .   2
     2.1.  Interaction Between DHCPv6-PD and SLAAC . . . . . . . . .   3
     2.2.  Signaling Stale Configuration Information . . . . . . . .   3
   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   5.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   5
   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 Routers that
   help mitigate the aforementioned problem for residential or small
   office scenarios.

2.  Improved CPE behavior

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

   The updated behaviour is as follows:

   o  CPE routers MUST signal stale configuration information as
      specified in Section 2.2

Gont, et al.               Expires May 4, 2020                  [Page 2]
Internet-Draft       Reaction to Renumbering Events        November 2019

   o  CPE routers MUST implement the DHCPv6-PD/SLAAC interface specified
      in Section 2.1.

   o  CPE routers SHOULD NOT automatically send DHCPv6-PD RELEASE
      messages upon reboot events.
Show full document text