3 ms·
Whenever I see articles like this (and there have been tons over the past decade), I can never stop thinking about how poorly designed IPv6 was for adoption. To
by hn_throwaway_99 5y ago
Whenever I see articles like this (and there have been tons over the past decade), I can never stop thinking about how poorly designed IPv6 was for adoption. Tons of other people have commented on this, but if we simply extended the IPv4 address space, instead of having a parallel space with IPv6, the transition would have gone much more smoothly IMO.
- sedatk 5y agoI agree that IPv6 roll-out strategy has been broken from the beginning but how does "extending the space" help here? You still need to add support to the new space in all relevant layers. What does the extension strategy change here?
- icedchai 5y agoHow would that even work? The IPv4 address fields are 32-bits. If you extend them, you have a new protocol, just like IPv6. There could've been some parallel efforts (like opening up the 240/4 former class-E space for assignment), but that would just be a short term patch. IPv6 has been available for over 20 years. This is way longer than IPv4 was available when the Internet went "mainstream" in the mid-90's. ISPs need to get their ass in gear.
- hn_throwaway_99 5y agoThis post is an "oldie but goodie", I think it's been around probably at least 20 years, and the section titled "The IPv6 mess, part one: incompatibility" explains what I'm talking about. https://cr.yp.to/djbdns/ipv6mess.html https://cr.yp.to/djbdns/ipv6mess.html
- deleted 5y ago[deleted]
- icedchai 5y agoI've seen it. Unfortunately, he doesn't provide a real solution. The fact that some newer ISPs (like Verizon FIOS) are still not offering IPv6 in some areas is embarrassing.