4 ms·
Correct. I am convinced that the best way to speed up IPv6 adoption is to provide IPv6-only networking but with NAT64. Historical evidence is on this: cell pho
by kccqzy 3y ago
Correct. I am convinced that the best way to speed up IPv6 adoption is to provide IPv6-only networking but with NAT64.
Historical evidence is on this: cell phone ISPs have started doing this a long time ago and look at how high the IPv6 adoption is on mobile.
Also, an IPv6-only network removes the happy eyeballs algorithm so any routing issues on the IPv6 internet won't be papered over by the speed of the IPv4 internet, so there's more incentive to fix that.
(If you are interested in doing this at home, the most up-to-date documentation is a presentation from RIPE https://ripe87.ripe.net/wp-content/uploads/presentations/8-IPv6-mostly_on_OpenWRT.pdf https://ripe87.ripe.net/wp-content/uploads/presentations/8-I... that covers NAT64/DNS64/DHCP108/PREF64).
Of course everything I said above is conditioned on speeding up IPv6 adoption as a goal. Unfortunately for many, IPv6 adoption is not a goal at all, so nothing I said above applies to them.
- ianburrell 3y agoDon't forget about MAP-T which does IPv4 NAT over IPv6. The client is IPv4, the ISP is IPv6, and server is IPv4. This is still CGNAT but IPv6 is provided. But means ISP uses IPv6 internally. The problem for NAT64 in general use is that there is lots of IPv4-only software. NAT64 is great for business networks where control the software, but home users are going to try to use their Xbox 360 or Windows game from the 90s.
- deleted 3y ago[deleted]