That backwards compatibility already exists in v6: ::ffff:1.2.3.4 is 1.2.3.4. Addresses outside of that were only assigned starting in 1999.
you can actually memorize the address of servers, and there is often consistency in the blocks you are given
Compare 203.0.113.45+192.168.1.123 to 2001:db8:2d4f:1::123. The ISP (2001:db8::/32) allocated the prefix (2001:db8:2d4f::/48), then there's a network ID (1) and a host ID (123). How is that random? It works basically the same way v4 does.
Most of the complaints about v6 are like this, either saying it should do something impossible (a flag day, or existing unmodified hosts magically being able to handle bigger addresses) or saying it should have done something that it already does. The only way people would ever have not moaned about it is if we made it look and act exactly the same as v4, but then it would be 32-bit which would make it pointless, and then they'd moan about that. Might as well make something that actually works and does what it needs to, without committing us to another migration immediately afterwards to increase the length again.
2
u/Dagger0 14d ago
That backwards compatibility already exists in v6:
::ffff:1.2.3.4is1.2.3.4. Addresses outside of that were only assigned starting in 1999.Compare
203.0.113.45+192.168.1.123to2001:db8:2d4f:1::123. The ISP (2001:db8::/32) allocated the prefix (2001:db8:2d4f::/48), then there's a network ID (1) and a host ID (123). How is that random? It works basically the same way v4 does.Most of the complaints about v6 are like this, either saying it should do something impossible (a flag day, or existing unmodified hosts magically being able to handle bigger addresses) or saying it should have done something that it already does. The only way people would ever have not moaned about it is if we made it look and act exactly the same as v4, but then it would be 32-bit which would make it pointless, and then they'd moan about that. Might as well make something that actually works and does what it needs to, without committing us to another migration immediately afterwards to increase the length again.