Reaction of Stateless Address Autoconfiguration (SLAAC) to Flash- Renumbering Events
draft-gont-v6ops-slaac-renum-02

Document Type Replaced Internet-Draft (individual)
Last updated 2020-02-20
Replaced by draft-ietf-v6ops-slaac-renum
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 Replaced by draft-ietf-v6ops-slaac-renum
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-v6ops-slaac-renum-02.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 documents this problem, and discusses operational workarounds that may help to improve network robustness. Additionally, it highlights areas where further work may be needed.

Authors

Fernando Gont (fgont@si6networks.com)
Jan Zorz (jan@go6.si)
Richard Patterson (richard.patterson@sky.uk)

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