Skip to main content

Using Router Advertisements to Signal the Availability of DHCPv6 Prefix Delegation to Clients
RFC 9762

Revision differences

Document history

Date By Action
2025-06-16
(System)
Received changes through RFC Editor sync (created document RFC 9762, created became rfc relationship between draft-ietf-6man-pio-pflag and RFC 9762, set title to 'Using …
Received changes through RFC Editor sync (created document RFC 9762, created became rfc relationship between draft-ietf-6man-pio-pflag and RFC 9762, set title to 'Using Router Advertisements to Signal the Availability of DHCPv6 Prefix Delegation to Clients', set abstract to '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.', set pages to 14, set standardization level to Proposed Standard, added RFC published event at 2025-06-16, created updates relation between RFC 9762 and RFC 4861, created updates relation between RFC 9762 and RFC 4862)
2025-06-16
(System) RFC published