RFC 9762

Using Router Advertisements to Signal the Availability of DHCPv6 Prefix Delegation to Clients, June 2025

File formats:

icon for HTML icon for text file icon for v3pdf icon for XML
Also available: XML file for editing
 
Status:
PROPOSED STANDARD
Updates:
RFC 4861, RFC 4862
Authors:
L. Colitti
J. Linkova
X. Ma, Ed.
D. Lamparter
Stream:
IETF
Source:
6man (int)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC9762

Discuss this RFC: Send questions or comments to the mailing list ipv6@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 9762


Abstract

This document defines the P flag in the Prefix Information Option (PIO) of IPv6 Router Advertisements (RAs). The flag is used to indicate that the network prefers that clients use the deployment model in RFC 9663 instead of using individual addresses in the on-link prefix assigned using Stateless Address Autoconfiguration (SLAAC) or DHCPv6 address assignment.

This document updates RFC 4862 to indicate that the Autonomous flag in a PIO needs to be ignored if the PIO has the P flag set. It also updates RFC 4861 to specify that the P flag indicates DHCPv6 prefix delegation support for clients.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.




Advanced Search