Explicit signaling of Stateless Address Autoconfiguration (SLAAC) to Renumbering Events
draft-olopade-6man-slaac-signaling-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Loba Olopade | ||
| Last updated | 2021-04-22 (Latest revision 2020-10-19) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
After a renumbering event in an IPv6 network utilizing SLAAC, hosts might continue to use stale addresses, as they are unaware of the changes. Likewise, routers, who may deprecate the use of these prefixes, are unaware of their use on the hosts. This scenario could have an adverse effect on communication with the host. This document proposes changes to the SLAAC algorithm that will explicitly allow routers to learn of these stale prefixes that are still assigned on the network.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)