10 ms·
IPv6 non-alternatives: DJB's article, 13 years later
- geocar 11y ago> you still need to upgrade all software on the planet and all routers on the planet. No, you don't. The biggest benefit to using IPv4 as the routing-infrastructure and extra bits (maybe an IP option) to describe the host is that most of the Internet (routers, etc) don't need to get upgraded, only hosts. Routers don't normally mess with the packets so only the first/last wifi/switch actually need upgrading. This is a small number of devices (certainly much smaller than all!). There could be a few routers that lose the option, and one option is to just fix those routers (still a much smaller number than all routers), but another option is to rely on connection tracking only when the service is behind such a router. The ubiquity of UPNP suggests this path would have worked just fine. NAT gives us a 32-bit port number pair, which requires memory, makes denial-of-service attacks easier, and is complicated. An IP option means that the hosts track the connection themselves. Another option would be to move port numbers into DNS. This might've been simple (48-bit addresses are pretty big), and only affected new services. We upgraded all of the webservers and web browsers faster than IPv6 deployed, so this probably would have just been a simple matter of mothballing IANA. However, I worry we're not actually arguing about what we think someone a decade (or two) ago thought could be the direction to talk about solving a problem. IPv6 is the biggest deploy attempted on the Internet, and it's been miserable. We should be talking about its failings, its mistakes, and how we could do better knowing what we learned, not patting ourselves on the back for doing the best we could've done knowing what we knew. IPv6 might be inevitable at this point, but that doesn't mean it was right.
- lmm 11y ago> No, you don't. The biggest benefit to using IPv4 as the routing-infrastructure and extra bits (maybe an IP option) to describe the host is that most of the Internet (routers, etc) don't need to get upgraded, only hosts. Routers don't normally mess with the packets so only the first/last wifi/switch actually need upgrading. This is a small number of devices (certainly much smaller than all!). That's the "BangIP" option discussed in the second half of the article and has all the problems discussed there (e.g. it makes multihoming more-or-less impossible)
- geocar 11y agoMultihoming (PI) isn't impossible but it certainly requires more work. I'm not yet convinced to throw the baby out with the bath water. Multihoming is also not the normal case: for a long time ARIN refused to make IPv6 PI allocations to existing IPv4 PI.
- Arnt 11y agoExclude the infrastructure that need to be upgraded to support larger routing tables, larger AS numbers or other extensions. Exclude all the infrastructure that needs to be upgraded because it supports/does DPI or packet filtering. Exclude the new infrastructure that's newly bought and insatlled in order to cope with the network growth that caused the need for v6 in the first place. Exclude the infrastructure that needs to be bought in order to support new media types (WLAN, VDSL, denser/faster fiber, whatever). Once all that is excluded, there isn't much infrastructure left.
- geocar 11y agoYou're describing IPv6. I'm describing IPv4 that uses the current dotted-quad as the network address and adds a new host address: The routing tables don't get bigger, AS numbers are 32 bit anyway and unlikely to get bigger, DPI is actually easier than with NAT since there's no ambiguity, there's no new media types, and upgrades can be done piecemeal. Seriously, it's better than IPv6 in every way but one: by being cheaper to deploy companies and consultants can't charge extra for IPv6 readiness over a few decades.
- zAy0LfpBZLC8mAC 11y ago> The routing tables don't get bigger They do, because of route fragmentation, not because of address size. > AS numbers are 32 bit anyway and unlikely to get bigger No, AS numbers were 16 bit until well after the introduction of IPv6.
- fulafel 11y agoThis is in fact one of the ipv6 transition mechanisms and was supported by Windows, Cisco, Apple Airports etc. (6to4)
- geocar 11y agoNot exactly. 6in4 gives IPv4 hosts IPv6 addresses which means we only have to upgrade all the edges, but we still have to upgrade all of them. What I propose (effectively) gives IPv6 (though I should call it something else) hosts IPv4 addresses: the exact opposite. You don't have to upgrade anything except the user's web browser (which clearly took less than 20 years).
- lmm 11y ago> 6in4 gives IPv4 hosts IPv6 addresses which means we only have to upgrade all the edges, but we still have to upgrade all of them. No-one's turning off their IPv4 stacks though. Under your proposal if one or other edge was IPv4-only then they'd use ordinary IPv4, you'd only see any benefit if both edges were IPv4+, right? Which is the same as when using 6to4. (If you really need to avoid dual-stack even on the local network you can use 6to4 and NAT64). (6to4 is largely a failure but the kind of approach you propose would have the same issues as far as I can see)
- geocar 11y agoA 6in4 address ends in an IPv4 address so it doesn't actually add any IP space: A 6in4 host can't allocate additional IPv6 addresses that are routed over IPv4. An IPv4+ address reserves 32 bits for the network address, and has (say) a 64 bit host address after it. This means that IPv4+ hosts can be allocated by anyone with an IPv4 address.
- lmm 11y ago> A 6in4 address ends in an IPv4 address so it doesn't actually add any IP space: A 6in4 host can't allocate additional IPv6 addresses that are routed over IPv4. Not so - if you have a single public IPv4 address you can turn that into an IPv6 /48 and put up to 16 bits worth of hosts behind it. Given that these are only for edges and not meant to have routing within them that should be plenty (having two different sets of routing logic applying to the same packets would be a recipe for difficult-to-debug disconnections and even-more-difficult-to-debug transient slowness).
- zAy0LfpBZLC8mAC 11y ago> No, you don't. The biggest benefit to using IPv4 as the routing-infrastructure and extra bits (maybe an IP option) to describe the host is that most of the Internet (routers, etc) don't need to get upgraded, only hosts. Routers don't normally mess with the packets so only the first/last wifi/switch actually need upgrading. This is a small number of devices (certainly much smaller than all!). What does WiFi or a switch even have to do with this?
- api 11y agoNow consider that IPv4 + NAT + NAT traversal is essentially a crap version of IPv4+ that uses UDP port numbers to achieve an unstable, unreliable 16 bit extension to the IPv4 address space. Of course because these port numbers are ephemeral and unreliable all P2P code must be full of complex logic to constantly check for dead paths, remap ports, deal with different kinds of NAT, etc. I happen to think DJB was right. If we could rewind history to, say, 1998 and implement an address space extension to IPv4 that was less of a severe change than IPv6 that probably would have been the better way forward. Personally I would have implemented IP64, using the existing IPv4 space as the most significant 32 bits of a 64 bit address space. The advantage here is that an IP remains something that can fit in a typical 64-bit CPU register and remains short enough that it's type-able and at least a little bit memorable. 64 bits would be plenty to address every device on Earth. There are some nice things about having a larger address space but most of them are minor compared with the address shortage problem. IPv6 gives you enough space for reliable stateless auto configuration, but in practice that's going out of favor since it turns out you need DHCP (DHCPv6) for other reasons besides just assigning addresses.
- XorNot 11y ago128-bit wasn't an arbitrary choice. It was done to ensure the routing tables would remain small and sane. It's why we use a 64-bit prefix, and a 64-bit address, for IPv6 network assignments as the default. Note those values and think of the significance.
- enip 11y agoInteresting times we live in. IPv4+ (better name) and Enhanced IP (possibly better protocol) both use IP options. I won't recap what IPv4+ does but here's a recap on the important bits of EnhancedIP. There is a proof of concept implementation available for Linux at www.enhancedip.org. You can download VMs to see how it works. Also, http://www.enhancedip.org/learnmore.html http://www.enhancedip.org/learnmore.html has a quick rundown with just enough detail to get the idea. EnhancedIP uses a 64-bit address that works as two IP addresses concatenated together. Enhanced IP requires NATs and end hosts to be upgraded but not core/edge routers. Enhanced IP is also backwards compatible with IPv4 as much as is possible. There is a draft RFC and a full paper available for Enhanced IP. Because the Internet wouldn't have to wait on a core router upgrade to get started, this might move along more quickly.
- jerf 11y agoThe 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....
- xaduha 11y agoIPv6 will get there eventually, there's no immediate need for it to happen overnight, obviously.
- solidangle 11y agoIndeed, at some point the situation with IPv4 will become so grave that it will become impossible to ignore IPv6. Transitioning to something like BangIP might be much easier, but it will be impossible to force people to adopt it, which will only lead to fragmentation. IPv6 might cause massive fragmentation on the internet right now, but once the IPv6 gets closer to 100% we can start dismantling the IPv4 infrastructure, which will force the remaining few to switch to IPv6. There's no way to do that with BangIP, as it involves keeping the IPv4 infrastructure intact, which will allow people to continue browsing a large part of the web and thus there will be little to no reason for a lot of people to switch to BangIP. In the end IPv6 will be a much better solution than BangIP.
- mkozlows 11y agoThis sounds a lot like the argument for XHTML 2.0.
- agwa 11y agoThere was never any pressure to switch to XHTML2 - HTML4/ XHTML1 kept working fine. In contrast, IPv4 is going to become increasingly painful.
- xaduha 11y agoThere was nothing wrong with XHTML 2.0 apart from 0 support from the vendors. So I guess it's better, right? (but let's not discuss XHTML 2.0 now)
- cpeterso 11y ago> once the IPv6 gets closer to 100% we can start dismantling the IPv4 infrastructure It's taken 20 years for IPv6 to get to 10%. In another 20 years (2036), will IPv6 be at 20%, 100%, or 0% (superseded by something else)?
- ctstover 11y agoI for one think the more incompatible V4 and V6 are the better! There are only two things that ever made any sense: 1) try as hard as possible to be fully inter-operable with each other, or 2) full clean break. Clearly, there was never a 100% consensus on the goal. As is now, I see it as a chance to start over with so many silly things (ie, 12 layers of NAT for everything in the cloud). When you look at all the gripping about problems, it's so much of a better pitch to think of it as this new global network to play with that opens more doors instead of some never-going-to-happen retrofit from hell.
- scurvy 11y agoSeconded. IPv6 brings a lot of nice things that we never would have had in an IPv4 based or extended world. Router fragmentation? Gone! Simple subnetting? Hello ipv6! DHCP? Gone (mostly)! Link local addresses? Got em! These are all positive things we wouldn't have if we were still clinging to IPv4.
- solotronics 11y agoI agree wholeheartedly. From an ISP perspective its dual stack. The IPv4 and IPv6 networks are separate but serve the same customers, basically they should be overlapping to all endpoints.
- maw 11y agoFrom what I can see, he also readily admits that IPv4 and IPv4+ hosts cannot talk to each other, or more clearly, we cannot start using the extended address space before almost everybody has IPv4+ capable software. I don't know whether to respond to that with "what?" or "yeah, so what?" but I'm leaning toward the former. IPv4 and IPv4+ hosts would communicate with each other, but IPv4 would only be able to communicate with the overlapping range of IPv4+. Addresses in this range would have initially been relatively valuable but their value would be expected to decrease over time as more hosts started working over IPv4+. I think djb was right, but obviously we're unlikely to ever find out.
- ambrice 11y ago"what"? Since you have a multiple IPv4+ hosts with the same IPv4 address, how would an IPv4 host communicate with an IPv4+ host?
- maw 11y agoThe idea of multiple IPv4+ hosts with the same IPv4 address doesn't come into it at all. (Questions of proxying in its various forms aren't really relevant.) So, to answer your question: it wouldn't.
- ambrice 11y agoWhat does proxying have to do with it? One of us is terribly misunderstanding the concept. As I understand IPv4+ concept in this article, your router gets address 1.2.3.4 then every device behind it gets 1.2.3.4.0.0.0.1, etc. That way all the routers in between don't need to be upgraded, they just get the packets to your router and don't care about the extra address bytes, and your router gets them to a particular device. Which is great for routers in the middle, but your web browser still has to use IPv4 and NAT workarounds until all the web servers are upgraded to support IPv4+.
- maw 11y agoAs I understand IPv4+ concept in this article, your router gets address 1.2.3.4 then every device behind it gets 1.2.3.4.0.0.0.1, etc. This is the bit that wasn't in djb's original article AFAIR. My take was that 1.2.3.4 and 1.2.3.4.0.0.0.1 would be the same machine -- or at least allocated to the same entity.
- enip 11y agoWhat about Enhanced IP as in www.enhancedip.org?
- teilo 11y agoEvery problem noted in this article also exists in Enhanced IP. It still requires all software and hardware layers to be redesigned. Every potential alternative to IPV6 is pointless. IPV6 is already implemented by every network vendor, and every modern operating system. Most consumer ISPs have already implemented it. All remaining ISPs, including Enterprise providers, are in the middle of implementing it. No alternative protocol, including Enhanced IP, is going to be implemented. Ever.
- enip 11y agoWhile Enhanced IP requires software upgrades it does not require any hardware upgrades. Enhanced IP rides over the IPv4 network without requiring re-peering like IPv6 does. I have already used Enhanced IP over the Internet and it works fine. Also, I wrote the kernel patches for Linux over a period of less than six months. If I can do this the other operating systems vendors could do it too. Instead of being at 10% network capability after 20 years, Enhanced IP has an advantage because it transports packets over IPv4. Enhanced IP also keeps protocols like ARP and DHCPv4 so there is less disruption here. Further, Enhanced IP uses IPv6 AAAA records for DNS lookups so this area of the network experiences less disruption too. You should consider reading about how we do this as it is pretty interesting. Please read our paper or RFC for further clarification or details. They can be found here: http://www.enhancedip.org/documentation.html http://www.enhancedip.org/documentation.html The one comment you make on your blog post that is true is that Enhanced IP is not compatible with multiple layers of NAT.