Add DHCPv6-PD Preferred flag support (RFC 9762) #276
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change adds support for advertising the DHCPv6-PD Preferred (P) flag in Prefix Information Options, as specified in RFC 9762.
The P flag allows routers to indicate to clients that DHCPv6-PD is available on the network.
https://www.rfc-editor.org/rfc/rfc9762.html
Wireshark already supports parsing and displaying this flag as “DHCPv6-PD Preferred Flag (P)” in Prefix Information Options.
Note that, since glibc does not seem to define
ND_OPT_PI_FLAG_*constants for this flag, the current naming (ND_OPT_PI_FLAG_DHCPv6_PD_PREF) may not be optimal.I also saw the Android Developers Blog post “Simplifying advanced networking with DHCPv6 Prefix Delegation,” which relates to this topic.