5 ms·
This post gives a very good explanation of what a sensible transition plan would have looked like. It mainly starts with IPv4 address space being a subset of IP
by hn_throwaway_99 9y ago
This post gives a very good explanation of what a sensible transition plan would have looked like. It mainly starts with IPv4 address space being a subset of IPv6, instead of a totally new address space: http://cr.yp.to/djbdns/ipv6mess.html http://cr.yp.to/djbdns/ipv6mess.html
- growse 9y agoIPv4 is a subset of IPv6! They literally invented a way to map from an IPv4 address to IPv6 with a special prefix.
- convolvatron 9y agowth happened with that, in the original proposal it was 96 bits of zero, then that was deprecated, and then they added :ffff:0:0 with the same functionality
- wyufro 9y agoNo, they have different functions. Sending to ::1.2.3.4 would send an IPv6-in-IPv4 packet to 1.2.3.4. Using ::ffff:1.2.3.4 tells the OS that you want to send a proper IPv4 packet and no IPv6 is used on the wire. I don't know why the former was deprecated, but I think almost no OS supported it so might've been just that.
- Avernar 9y agoThe former was depricated because the automatic tunneling transition method was depricated and none of the current IPV6 transition methods use them. Now some software use those addresses to store IPV4 addresses in the same memory as an IPV6 address.
- dom0 9y agoThe article itself isn't dated, but for reference Last-Modified: Sat, 02 Aug 2003 14:27:40 GMT
- hn_throwaway_99 9y agoThe old date of the article kind of proves my point. It's 14 years later, and we still get huge HN threads around the very-incomplete state of IPv6 transition.
- wmf 9y agoWhen you work out the details of DJB's "plan" you discover that it's just as messy as IPv6, maybe worse. http://archive.is/eHvKF http://archive.is/eHvKF