A new Request for Comments is now available in online RFC libraries.
RFC 9926
Title: Prefix Registration for IPv6 Neighbor
Discovery
Author: P. Thubert, Ed.
Status: Standards Track
Stream: IETF
Date: February 2026
Mailbox: [email protected]
Pages: 24
Updates: RFC 4861, RFC 6550, RFC 8505, RFC 8928, RFC 9010
I-D Tag: draft-ietf-6lo-prefix-registration-18.txt
URL: https://www.rfc-editor.org/info/rfc9926
DOI: 10.17487/RFC9926
This document updates IPv6 Neighbor Discovery (RFC 4861) and IPv6
Subnet Neighbor Discovery (RFC 8505, RFC 8928) 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
unicast prefix registration allows the node to request one or more
neighbor routers to redistribute the prefix in another routing domain
regardless of the routing protocol used in that domain. This
document updates the Routing Protocol for Low-Power and Lossy
Networks (RPL), as specified in RFCs 6550 and 9010, to enable a
6LoWPAN Router (6LR) to inject the registered prefix in RPL.
This document is a product of the IPv6 over Networks of Resource-constrained
Nodes Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected]. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
_______________________________________________
6lo mailing list -- [email protected]
To unsubscribe send an email to [email protected]
