Improving the Reaction of Customer Edge Routers to Renumbering Events
draft-gont-v6ops-cpe-slaac-renum-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Fernando Gont , Jan Zorz , Richard Patterson | ||
| Last updated | 2019-11-01 | ||
| Replaced by | draft-ietf-v6ops-cpe-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-cpe-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), 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.
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.)