RFC 9663: Using DHCPv6 Prefix Delegation (DHCPv6-PD) to Allocate Unique IPv6 Prefixes per Client in Large Broadcast Networks
In plain English — editorial summary, not part of the RFC
This document discusses an IPv6 deployment scenario when individual nodes connected to large broadcast networks (such as enterprise networks or public Wi-Fi networks) are allocated unique prefixes via DHCPv6 Prefix Delegation (DHCPv6-PD), as specified in RFC 8415.
Document record
- Document ID
- RFC9663
- Published
- October 2024
- Authors
- L. Colitti; J. Linkova; X. Ma
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9762Using Router Advertisements to Signal the Availability of DHCPv6 Prefix Delegation to ClientsCurrent
June 2025
- RFC 7934Host Address Availability RecommendationsCurrent
July 2016
- RFC 9686Registering Self-Generated IPv6 Addresses Using DHCPv6Current
December 2024
- RFC 9131Gratuitous Neighbor Discovery: Creating Neighbor Cache Entries on First-Hop RoutersCurrent
October 2021
- RFC 6957Duplicate Address Detection ProxyCurrent
June 2013
- RFC 9818DHCPv6 Prefix Delegation on IPv6 Customer Edge (CE) Routers in LANsCurrent
July 2025
- RFC 9872Recommendations for Discovering IPv6 Prefix Used for IPv6 Address SynthesisCurrent
September 2025
- RFC 9898Neighbor Discovery Considerations in IPv6 DeploymentsCurrent
November 2025
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?