Not sure if it's too late to fix this, but I happened to notice this text in draft-ietf-6man-addr-select-opt-11:
"When the information from the DHCP server goes stale, the policy received from the DHCP server SHOULD be deprecated." Unfortunately, as RFC 4076 points out, information received via stateless DHCPv6 never expires. (That's one of the many reasons why DHCPv6... but I digress). What's the intent here? 1. This option is not recommended for use with stateless DHCPv6? 2. This option can be used with stateless DHCPv6, but its contents never expire? 3. This option can be used with stateless DHCPv6, and the client expires it whenever it feels like it? If #2, then perhaps this option needs a lifetime value? Unless the plan is that a) who/whatever solves the problem statement in RFC 4076 will solve this too, or b) that everyone needing this option will use stateful DHCPv6. Either way, it seems prudent to say something about this in the document, as otherwise it's a bit of a trap for the unwary.
-------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
