Reaction of Stateless Address Autoconfiguration (SLAAC) to Flash- Renumbering Events
draft-gont-v6ops-slaac-renum-02
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Fernando Gont , Jan Zorz , Richard Patterson | ||
Last updated | 2020-02-20 | ||
Replaced by | draft-ietf-v6ops-slaac-renum | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
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 | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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
Jan Zorz
Richard Patterson
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)