Article is vague on the most critical point: Does this mean IPv6-only? (That's the plain meaning of "convert".)
Because for an entire nation to go IPv6-only is a huge step, and may force the hand of Big Tech at a "tipping point" that Dan Bernstein said may never come.
If everyone in Vietnam, and hopefully a few more nations, is eventually unable to reach IPv4-based servers, then hopefully that will spur adoption everywhere else! But to cut off service like that is nearly unthinkable here in the West. Could you imagine if Comcast just said "ok, we're terminating your IPv4 access now, glhf!"
"IPv6 only" includes transition tech (usually NAT64+DNS64) so clients can still reach IPv4 servers. No one is seriously talking about cutting themselves off from half the Internet.
So if NAT64+DNS64 moderate this, it seems like there's no meaningful barrier to IPv6-only clients. But, NAT64 translators seem as user-hostile as CGNAT. If this is "transition only", at what point can those translators be removed? Is there an exit plan that would present a smooth and clean, IPv6-only experience, once full transition is accomplished? Or will these be an enduring crutch for decades to come?
DJB's rant wasn't even great at the time and technology has advanced since then. Sadly, a bunch of people have gotten a pretty wrong understanding of IPv6 by reading it. And of course DJB has neither updated it nor deleted it.
NAT64 is indeed a form of CGNAT, but everyone today is behind NAT44 so it's no worse. And remember that you can do P2P over native IPv6 so you're better off in that way. Networks like T-Mobile that use NAT64 today are seeing >50% native IPv6 traffic and <50% NAT64 traffic. Eventually the NAT64 traffic gets smaller and smaller and when it hits ~1% you could decide to turn it off.
5 comments
[ 3.2 ms ] story [ 19.1 ms ] threadBecause for an entire nation to go IPv6-only is a huge step, and may force the hand of Big Tech at a "tipping point" that Dan Bernstein said may never come.
If everyone in Vietnam, and hopefully a few more nations, is eventually unable to reach IPv4-based servers, then hopefully that will spur adoption everywhere else! But to cut off service like that is nearly unthinkable here in the West. Could you imagine if Comcast just said "ok, we're terminating your IPv4 access now, glhf!"
https://cr.yp.to/djbdns/ipv6mess.html
So if NAT64+DNS64 moderate this, it seems like there's no meaningful barrier to IPv6-only clients. But, NAT64 translators seem as user-hostile as CGNAT. If this is "transition only", at what point can those translators be removed? Is there an exit plan that would present a smooth and clean, IPv6-only experience, once full transition is accomplished? Or will these be an enduring crutch for decades to come?
NAT64 is indeed a form of CGNAT, but everyone today is behind NAT44 so it's no worse. And remember that you can do P2P over native IPv6 so you're better off in that way. Networks like T-Mobile that use NAT64 today are seeing >50% native IPv6 traffic and <50% NAT64 traffic. Eventually the NAT64 traffic gets smaller and smaller and when it hits ~1% you could decide to turn it off.