Using Prefix-Specific Link-Local Addresses to Improve SLAAC Robustness
draft-link-6man-gulla-01
| Document | Type | Expired Internet-Draft (individual) Expired & archived | |
|---|---|---|---|
| Author | Jen Linkova | ||
| Last updated | 2025-09-04 (Latest revision 2025-03-03) | ||
| Replaces | draft-link-6man-truce, draft-link-v6ops-gulla | ||
| 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
When an IPv6 prefix assigned to a link changes, hosts may not be explicitly notified about the change. Similarly, in some scenario a link attachement for the host may change without the host detecting it. In both cases the host does not receive any signals to trigger the network stack configuration refresh, so it may continue to use "old" addresses which are not valid for the link. This leads to packet loss and service disruption. This document proposes a mechanism to mitigate this issue. Routers are advised to send Router Advertisements containing distinct Prefix Information Options (PIOs) from different link-local addresses. This, in conjunction with RFC6724 (Default Source Address Selection) Rule 5.5 and RFC8028 (first-hop selection requirements), enables hosts to detect prefix changes more rapidly and select the correct source address, thereby improving the robustness of SLAAC.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)