Skip to main content

ND Prefix Robustness Improvements

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Eduard V , Paolo Volpato , Loba Olopade
Last updated 2023-03-05 (Latest revision 2022-09-01)
RFC stream (None)
Intended RFC status (None)
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:


IPv6 prefixes could become invalid abruptly as a result of outages, network administrator actions, or particular product shortcomings. That could lead to connectivity problems for the hosts attached to the subtended network. This document has two targets: on one hand, to analyze the cases that may lead to network prefix invalidity; on the other to develop a root cause analysis for those cases and propose a solution. This may bring to extensions of the protocols used to convey prefix information and other options. This document updates RFC 4861 and RFC 4862.


Eduard V
Paolo Volpato
Loba Olopade

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