Reaction of Stateless Address Autoconfiguration (SLAAC) to Renumbering Events
draft-gont-6man-slaac-renum-01

Document Type Expired Internet-Draft (individual)
Last updated 2019-08-22 (latest revision 2019-02-18)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-gont-6man-slaac-renum-01.txt

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), nodes on the local network will continue using stale prefixes for an unacceptably long period of time, thus resulting in connectivity problems. This document analyzes these problem scenarios, and proposes workarounds to improve network robustness. This document updates RFC4861 and RFC4862 to allow for a more robust reaction to network configuration changes.

Authors

Fernando Gont (fgont@si6networks.com)
Jan Zorz (jan@go6.si)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)