They rolled out IPv6 because it flattened that network again, and instead of worrying about being in the right segment for reachability everything now gets a globally unique IP address. It massively simplified their internal management.
And Microsoft has supported IPv6 since Windows 2000: https://news.microsoft.com/2000/03/15/microsoft-announces-ip....
I understand that LTE networks are exclusively IPv6, ditto "5G".
My frustration with IPv6 is that my home ISP (Wave Broadband's DOCSIS service) is still IPv4 and they still have no plans to roll-out IPv6 even though Wave's WaveG service has been IPv6 for as long as I can remember. I understand the cause of this is because Wave's network is incredibly hetereogenous because Wave's business-model was to expand by buying-up smaller regional cablecos but to retain their infrastructure (and talent) compared to Comcast's approach of asset-stripping (bad for employees, but good for customers...).
I want IPv6 so I can stop having to faff around with NAT. I'd love to be able to RDP-in directly to my desktop at home without having to pay companies like TeamViewer and Splashtop.
----
Update: I found Wave's peering page's IPv6 status page and it remains unchanged since 2011 (and possibly since 2008). Wow.
Compare:
https://web.archive.org/web/20110102140910/http://as11404.ne...
Live:
I still use HE's tunnel even though Spectrum Cable has provided good native IPv6 service for several years. Ping times over HE are just as good as native Spectrum, probably because everybody peers at the same place in Los Angeles.
The only problem with HE is that Netflix is clamping down on VPNs, and they consider a HE tunnel to be a VPN. So my home router advertises the native Spectrum prefix with a higher priority than the HE prefix.
My own frustration with IPv6 is that virtually no public hotspots support it. My Verizon phone does, so I often use it as a hotspot even when public WiFi is available.
I was aware of it, but I could swear that I heard news a couple of years ago that they shut it down due to decreased demand, but thank you for letting me know it's still running. I'll see if I can use it!
My ISP (RCN in Chicago) doesn't support IPv6 either. I tried HE, but ran into the above issue. Now I'm seriously considering getting an IPv6 block directly from ARIN (and paying the few hundred a year fees) to use with HE tunnels, to work around the Netflix block.
Would love to find a cheaper solution though.
We were working on some IPv6 projects that require IPv6 connectivity, and he didn't want to faff about with a tunnel or something along those lines, so he cancelled his Wave account and switched to Comcast.
Wave lost a customer due to not supporting IPv6... it's high time that ISP's started getting on-board.
What makes you think your ISP will give you more than one IP even when they are no longer in short supply? If it's something that has value to you, it's something they will want to be paid for.
[1] See https://www.ripe.net/about-us/press-centre/understanding-ip-... . I note that there is a lot of misinformation and badly-informed blog posts in the top search results for "ipv6 subnet size" like this one, ugh: https://www.crucial.com.au/blog/2011/04/15/ipv6-subnet-cheat... - which is wrong because IPv6 simply doesn't have 128-bit-sized subnet option (whereas you can have a 32-bit sized subnet in IPv4, which is how most residential ISPs/CPEs are configured).
So it's certainly possible for an ISP to give a customer just one IPv6 address. I'm not sure, but I think there is no rule that prefixes obtained with PD must be /64's. They could in principle give you a /126 or /127 to limit you to just a few hosts on your LAN, and charge to give you anything better. This would break stateless autoconfiguration but it would still work with DHCPv6.
Your best workaround is still www.tunnelbroker.com, HE's free IPv6 tunnel service.
Ask for a /56! Spectrum in Los Angeles hands out /56s, and I understand many other residential IPv6 ISPs do as well. You get your own 8 bits worth of subnets on top of /64 for easy SLAAC address assignment. This works "for free" not only because the IPv6 address space is large enough to do this, but more importantly because IPv6 does NOT have any fixed subnet sizes - routing is hierarchical and subnet assignment is transparent. /64 is just the size used by SLAAC address auto-configuration, another bit of IPv6 magic.
Thank you so very much for NOS, which was my very first introduction to IP over packet and what initially got me interested in amateur radio (going on 30 years ago!) and is, in part, what led to me initially getting licensed and drawn into the world of networking at a young age.
73,
N9WWV
--
P.S. Welcome to HN!
God, I knew the IPv6 space was insanely large, but Jesus h, man.
128 bits is a lot.
(the /64 as the physical subnet allows using hardware MAC addresses and RNG temporary/private addresses instead of needing DHCP/etc).
In actual reality, global IPv6 adoption is at ~33% [0, 1], so I'd say this is, at best, a premature and naive presumption. ISPs actively engage in rent-seeking, and resource scarcity is another contributing factor. In-short, there's nothing in OPs comment that warrants the downvotes.
[0] - https://www.google.com/intl/en/ipv6/statistics.html [1] - https://www.akamai.com/uk/en/resources/our-thinking/state-of...
Any internet service you want to be widely available will need to be dual-stack as long as we are alive.
Worldwide, Google is undercounting, because they are blocked in China. Google claims that China is 0.27% IPv6, but actually China is around 55%, according to APNIC. Policy goal in China is all IPv6 by 2025.
In 2005 the US government mandated that all their computers be v6 connected by 2008. [1] This year they updated the mandate to 80% by 2025. [2]
I learned networking in college in 1996 and I remember v6 coming up but so far I've never had to use it and chances are that I'll be able to retire still getting away with only working with v4.
[0] https://blog.apnic.net/2018/05/21/what-drives-ipv6-deploymen... [1] https://georgewbush-whitehouse.archives.gov/omb/memoranda/fy... [2] https://www.cio.gov/assets/resources/internet-protocol-versi...
There may be some class A owners who are trying to hold back IPv6 so they can make money off their class A, but Comcast isn't one of them.
Apple has long had IPv6 support in their operating systems, so I don't think they have been trying to hold it back either.
Ford, Softbank, Daimler, and Prudential? It is not immediately obvious to me if they could do anything to hold it back even if they wanted to.