Comment by paperplatter

Comment by paperplatter 12 hours ago

Yes, everything has to be updated eventually, but going forward doesn't have to be this hard. A network and its hosts could start supporting ipv6 without changing anything else. Same addr and routes as before, same NAT, and no DNS6/DHCP6/etc, so very low effort and risk to turn it on. If a peer only supports v4, talk v4 to it for now.

Then once there's sufficient v6 adoption, you can disable v4 entirely and start using /40, /48, etc..

Dagonfly 2 hours ago

> Same addr and routes as before

But same addr is the problem we are trying to solve in the first place. Using your IP-new proposal (let's call it IPv5): If every IPv5 addr is just a padded version of the same IPv4 addr, then once IPv4 addresses are exhausted the IPv4-mapped-into-IPv5 addresses are also exhausted.

At that point you need to start handing out IPv5 addresses to hosts without an IPv4 address. And then, how does a IPv5-only host talk to a IPv4-only legacy host? That's the fundamental issue!

The same addr thing only buys you time until the address exhaustion becomes real.

Reply View 0 replies

kemotep 12 hours ago

But you can do that with IPV6? I have both an IPV4 and IPV6 address on this very device.

My confusion in the claims that we could do it differently is how the protocol could be updated without actually doing the work of updating everything on the network and adding the new address scheme.

Reply View 0 replies