Improving the Reaction of Customer Edge Routers to IPv6 Renumbering Events
draft-ietf-v6ops-cpe-slaac-renum-07
IPv6 Operations Working Group (v6ops) F. Gont
Internet-Draft SI6 Networks
Updates: 7084 (if approved) J. Zorz
Intended status: Best Current Practice 6connect
Expires: August 20, 2021 R. Patterson
Sky UK
B. Volz
Cisco
February 16, 2021
Improving the Reaction of Customer Edge Routers to IPv6 Renumbering
Events
draft-ietf-v6ops-cpe-slaac-renum-07
Abstract
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 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 August 20, 2021.
Copyright Notice
Copyright (c) 2021 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
Gont, et al. Expires August 20, 2021 [Page 1]
Internet-Draft Reaction to Renumbering Events February 2021
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 . . . . . . . . . . . . . . . . . . . . 2
3. Improved Customer Edge Router Behavior . . . . . . . . . . . 3
3.1. Automatic DHCPv6 RELEASEs . . . . . . . . . . . . . . . . 4
3.2. Stability of IAIDs . . . . . . . . . . . . . . . . . . . 4
3.3. Interface Between WAN-side and LAN-side . . . . . . . . . 4
3.4. LAN-side Option Lifetimes . . . . . . . . . . . . . . . . 5
3.5. Signaling Stale Configuration Information . . . . . . . . 7
4. Recommended Option Lifetimes Configuration Values . . . . . . 9
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
6. Security Considerations . . . . . . . . . . . . . . . . . . . 9
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
8.1. Normative References . . . . . . . . . . . . . . . . . . 10
8.2. Informative References . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction
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 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.
2. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
Show full document text