3 ms·
> Remove SLAAC and stateless DHCPv6. This statement then implies that we would need to have NAT66. Why? Stateful DHCP then implies the possibility of an endpoi
by kccqzy 3y ago
> Remove SLAAC and stateless DHCPv6.
This statement then implies that we would need to have NAT66. Why? Stateful DHCP then implies the possibility of an endpoint having only a single assigned address. But what if the endpoint needs to have multiple addresses such as tethering or running VMs? With SLAAC the endpoint can just get multiple addresses. Now, just because today stateful DHCPv6 is a possibility, hypervisors need to have NAT66 built in. So the status quo is strictly worse than either only SLAAC or only stateful DHCPv6.
- RedShift1 3y agoThe VM could just have a bridged network connection, no NAT66 required.
- cyberax 3y agoStateful DHCPv6 allows prefix delegation even now, in its half-assed stupid form. And if you don't want/have prefix delegation, you can just use multiple DUIDs to get several leases for one endpoint. Unlike in V4, this is fully supported in V6. Your VM hypervisor will need to request an address during the VM startup, but I think it's actually better from the management standpoint. The network operator will be able to see VMs as the first class citizens in the network management console. > But what if the endpoint needs to have multiple addresses such as tethering or running VMs? Android developers are actually adding support for stateful DHCPv6 for exactly that reason :) They want to support tethering for V6 without doing NAT or bridging.