IPv6 Neighbor Discovery Prefix Registration
draft-thubert-6lo-prefix-registration-03
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Pascal Thubert | ||
Last updated | 2023-06-26 | ||
Replaced by | draft-ietf-6lo-prefix-registration | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources |
GitHub Repository
|
||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-ietf-6lo-prefix-registration | |
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
This document updates the 6LoWPAN extensions to IPv6 Neighbor Discovery (RFC 8505) to enable a node that owns or is directly connected to a prefix to register that prefix to neighbor routers. The registration indicates that the registered prefix can be reached via the advertising node without a loop. The prefix registration also provides a protocol-independent interface for the node to request neighbor router(s) to redistribute the prefix to the larger routing domain using their specific routing protocols. As an example, this document extends RFC 9010 to enable the 6LR to inject the registered prefix in RPL.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)