3 ms·
Has it? 35% and rising. 55% in the US, 75% in India, 30% in China. It hasn't worked out how we thought, sure. But "Failed" is really strong for something that
by ggm 3y ago
Has it? 35% and rising. 55% in the US, 75% in India, 30% in China.
It hasn't worked out how we thought, sure. But "Failed" is really strong for something that 1/3 of the global Internet can (and does) use every day.
There are more people on IPv6 now, than there are users in the entire US Internet market.
https://stats.labs.apnic.net/ipv6/CN https://stats.labs.apnic.net/ipv6/CN (replace last 2 chars with any ISO3166 code, or XA for the world)
- hughesjj 3y agoYup, especially for cell phones. Pretty much any time in on Verizon or att in assigned an ipv6 addr
- ggm 3y agoWe all know people who go hard on IPv6 has failed. Well.. its true it didn't achieve what we hoped in the concept of IPv6 Transition So failure is in there. But it's a different kind of market failure to DECnet, or X.25, or Novell Netware. It's the kind of "fail" which means "didn't turn out as we expected" IPv6 has quirks which are a bummer. If we were able to fix the MTU problem by getting people to move to Jumbograms a lot of these go away, because they stem from fragmentation. So it's true, the design of IPv6 end only fragmentation distinct from V4 on the path fragmentation, that was a failure in design. But if you avoid fragmentation (and QUIC does for instance) then the MTU problem isn't a big deal in the end. More packets is faster clock pacing! I wish people were a bit more pragmatic and a bit less dogmatic about things. Fix MTU. fix links. Fix what you can. Deploy IPv6 because it works. And, it reduces pressure on your CGN.
- kiwijamo 3y agoIn some countries there's zero IPv6 on mobile despite good progress being made on fixed line IPv6.
- abwizz 3y agointeresting! i tend to regrad ipv6 as the "smartphones + india internet"
- activiation 3y agoI block IPv6 on my home router because everything still works without it and it simplifies my firewall a bit.
- ggm 3y agoI permit IPv6 SSH into my home network precisely because I have a static V6 delegation and can do it, where my IPv4 binding is necessarily mutable because of the use of CGN, and lack of pool addresses. If I want to "phone home" then this is simpler than managing dynamic-DNS to find where my home is right now on v4. Above the IP layer, TCP/UDP rules should be underlying AFI agnostic. But I can believe the firewall DSL don't make that easier.
- activiation 3y agoTechnically, I have a dynamic ipv4 IP address but in practice, it never changes unless I spoof my router's MAC address.