RFC 8168: DHCPv6 Prefix-Length Hint Issues
In plain English — editorial summary, not part of the RFC
DHCPv6 Prefix Delegation allows a client to include a prefix-length hint value in the IA_PD option to indicate a preference for the size of the prefix to be delegated, but it is unclear about how the client and server should act in different situations involving the prefix-length hint. This document provides a summary of the existing problems with the prefix-length hint and guidance on what the client and server could do in different situations.
Document record
- Document ID
- RFC8168
- Published
- May 2017
- Authors
- T. Li; C. Liu; Y. Cui
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9243A YANG Data Model for DHCPv6 ConfigurationCurrent
June 2022
- RFC 7934Host Address Availability RecommendationsCurrent
July 2016
- RFC 9096Improving the Reaction of Customer Edge Routers to IPv6 Renumbering EventsCurrent
August 2021
- RFC 8415Dynamic Host Configuration Protocol for IPv6 (DHCPv6)Obsoleted
November 2018
- RFC 7653DHCPv6 Active LeasequeryCurrent
October 2015
- RFC 7341DHCPv4-over-DHCPv6 (DHCP 4o6) TransportCurrent
August 2014
- RFC 9686Registering Self-Generated IPv6 Addresses Using DHCPv6Current
December 2024
- RFC 9915Dynamic Host Configuration Protocol for IPv6 (DHCPv6)Current
January 2026
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?