5 ms·
The real reason why IPv6 has been so slow to get deployed is precisely that you can not just take an IPv4-using program and network, fix all the structs and API
by jerf 11y ago
The real reason why IPv6 has been so slow to get deployed is precisely that you can not just take an IPv4-using program and network, fix all the structs and API calls, and have an IPv6 program. This is a sideshow compared to the real problem. IPv6 is profoundly different in all sorts of ways. Yes, if you just want to open a TCP connection to a remote system you can use an IPv6 address instead of an IPv4 address and the resulting socket is usually essentially identical (it isn't necessarily but the differences often don't matter for the simple common case), but almost everything else changes. "DHCP" changes. Vast new rules about all the classes of IPv6 addresses, and all network hardware needs to implement new code to handle all that. IPv6 addresses are much more complicated than IPv4 addresses.
In fact probably most of the people reading this only think they know what an IPv6 address is... based on my experience with people who think they know what IPv6 is, most are wrong. Do you know what the "link local" portion of the address is off the top of your head? Do you know what an % sign in the IPv6 address signifies? (This being HN, of course a few thousand of you do; you don't need to prove that in a reply. But I bet the majority of people reading this do not.)
Just look at this page: https://en.wikipedia.org/wiki/IPv6_address https://en.wikipedia.org/wiki/IPv6_address
By contrast, I can't link you to the "Wikipedia page on IPv4 addresses", because it doesn't rate its own page. It just gets rolled into a single section on the IPv4 page in general: https://en.wikipedia.org/wiki/IPv4#Addressing https://en.wikipedia.org/wiki/IPv4#Addressing
And that's just addresses. There's huge swathes of other changes that require huge amounts of new code to be added to all network devices.
IPv6 isn't a failure (inasmuch as we really should have been done by now) because it requires a total upgrade of all network devices. Probably the vast bulk of critical devices have been upgraded in the time since IPv6 was first standardized. IPv6 was a failure because it also immensely complicated the network protocol and code did not just have to be "slightly modified" to work, but torn down and replaced with a much larger and more complicated chunk of code. IPv6 is not "just" IPv4 with bigger addresses. IPv6 doesn't fail to interoperate with IPv4 because of trivial networking issues, IPv6 fails to interoperate with IPv4 because it's a wildly different network stack that happens to offer similar enough TCP-like abstractions that user-level code often is only slightly affected, but everything else in the stack is profoundly affected.
The advantage of the "just extend it" plan is that it would have been that easy. Perhaps a judicious application of a few solutions to the worst IPv4 problems could have been added. But IPv6 is the technical equivalent of an appropriations bill in the US Congress. We have to do this, so let's take this opportunity to stuff every wish-list item in there we can. We didn't have to do that.
In a way, the article does a better job defending DJB's thesis than attacking it, precisely by pointing out that DJB's plan would have been relatively easy and feasible....
- lmm 11y agoBe specific. What is the "almost everything else" that so many people have to worry about? People who write IP address parsing libraries have to care about percent signs and formats. People who write DHCP clients have to care about DHCP changes. But neither of these are huge changes that affect everyone.
- krakensden 11y agoI've got one- every interface has two ipv6 ips, one real, one link local, which requires a lot of little tweaks in a lot of deployments. Or if you're doing DSR, the default route ordering rules are different.
- X-Istence 11y agoEvery interface can have 1 or more IPv6 IP's. Link-local and N number of others, where N is 0 or more. What kind of tweaks have you required in your deployments because of this? DSR is a special use case, and with each interface having a link-local address means you don't need to provide globally unique addresses, because the source/destination specify their route explicitly, each hop can use their link-local address. DSR would also require modification if it was using an extended version of IPv4...
- fulafel 11y agoLink local is by design invisible to normalapplications. You can't even use them in place of routable addresses in applications. (You have to do a special bind() with the right scope id)
- scurvy 11y agoI'll bite. How can you have more than one "default" route without PBR on the host? That's breaking the meaning of default. Why does link local need to be complicated? Router interfaces facing clients should be fe80::1. That way, every client knows it's default route is fe80::1%eth0 (or similar). Works great for multiple addresses from different networks on the same host, too.
- ambrice 11y ago