Aaron Brady
boosted
I've published the -00 for a new IETF draft: #DHCPv6 Recommended #IPv6 Address Option"
https://datatracker.ietf.org/doc/html/draft-nygren-dhc-recommended-ipv6-address-00
The primary use-case for this is hosting, datacenter, and cloud environments that want to assign a /64 per host but which also want to ensure the host configures one or more addresses (such as for management and running services). Operators configuring servers in these environments want to be able to ensure that a host will be available on a given /128 (for ssh'ing into, putting into DNS as a service endpoint, etc) while DHCPv6-PD also means that the host is free to use the rest of the /64 for its own purposes (eg, containers, K8s pods, temporary addresses, etc).
I'd also be happy to add a co-author if someone else is interested in seeing this through.
I've published the -00 for a new IETF draft: #DHCPv6 Recommended #IPv6 Address Option"
https://datatracker.ietf.org/doc/html/draft-nygren-dhc-recommended-ipv6-address-00
The primary use-case for this is hosting, datacenter, and cloud environments that want to assign a /64 per host but which also want to ensure the host configures one or more addresses (such as for management and running services). Operators configuring servers in these environments want to be able to ensure that a host will be available on a given /128 (for ssh'ing into, putting into DNS as a service endpoint, etc) while DHCPv6-PD also means that the host is free to use the rest of the /64 for its own purposes (eg, containers, K8s pods, temporary addresses, etc).
I'd also be happy to add a co-author if someone else is interested in seeing this through.