7 ms·
I know this idea has long missed the boat, but why wasn't IPv4 address space extended by adding an IPv4 Option header that could carry extra address bits? You
by rwmj 11y ago
I know this idea has long missed the boat, but why wasn't IPv4 address space extended by adding an IPv4 Option header that could carry extra address bits?
You could even have made IPv4 addresses variable length this way, from 32 up to a very large number of bits, and hierarchical. And it's relatively easy to make such a scheme backwards compatible, because you can have (say) a webserver sitting on 1.2.3.4 answering queries for older clients that don't know how to form a 1.2.3.4.5.6 address packet.
- xorcist 11y agoGiven that you don't want to tie next-generation allocations to existing v4 prefixes, that scheme ends up more complicated than what we got with v6. You would still need a gateway to keep state if you're moving traffic between v4-only endpoints and v6-only, which would end up pretty much like NAT64. The opportunity to break backwards compatibility in v6 brought many other good things as well: fixed fields that are easier to route, more sane network allocation schemes, router discovery for LANs, and lots of other bits and pieces.
- josteink 11y ago> I know this idea has long missed the boat, but why wasn't IPv4 address space extended by adding an IPv4 Option header that could carry extra address bits? Because that wouldn't be compatible with existing IPv4 deployments and would cause a reliability havoc when a node not configured to deal with it mangled packets transparently somewhere in between your source and destination end-points. I don't get the resistance against IPv6. It works. It's a fresh take. Yes it requires some new stuff to be deployed and configured here and there, maybe even requires you to learn something new, but if you thought extending IPv4 would have been any other way you are deluding yourself. If you're going to do a significant change to something as big as the internet (and introducing a new address scheme is that, no matter how you implement it), you might as well step back and think it all through instead of applying yet another hack. So tell me. Why are you opposed to IPv6? Why do you want to hang on to this old IPv4-thing which is already at the bursting point, at the edge of what it can take?
- mirimir 11y ago> So tell me. Why are you opposed to IPv6? I'm very concerned about implications for anonymity. If every device has a unique IPv6 address, then just one leak can compromise all other anonymized connections.
- xorcist 11y agoCheck out RFC 4941, "Privacy Extensions". It's probably already implemented on the computer you're using right now.
- spystath 11y agoYou can still track the prefix though. In a standard /64 deployment only the suffix will change so there is still some information leaking if you have a static prefix (obviously, as in static IPv4). However, my ISP defaults to dynamic /64 prefix unless you opt in for static prefix. I believe most ISPs should probably do the same.
- wtbob 11y agoIf you have a dynamic prefix then you can't (easily) run servers; you'd need some sort of dynamic DNS as well. And if you have dynamic DNS and dynamic reverse-resolution…there goes anonymity anyway. IP isn't anonymous; it wasn't designed to be, and probably (given the problems it's trying to solve) shouldn't be. Anonymity should be an overlay.
- spystath 11y agoIf you run a server you pretty much need to expose your IP one way or another anyway, even in IPv4. Well, I suppose you can use something like dynamic dns but still... I totally agree, though, anonymity is not part of IP. I was not implying that, just that there are still ways for home users to somehow shuffle their IPs within the IPv6 framework.
- Arnt 11y agoVarious forms of this were actually considered. They all share the characteristic that you discover old v4-only devices late rather than early. You can run a mostly-v6 network and have no way to search for the remaining v4-only devices (or programs). That problem was held to be too much of an "ouch".
- mojuba 11y ago> you discover old v4-only devices late rather than early Could you explain what this means?
- Arnt 11y agoSuppose you have a network with a hundred devices and an addressing scheme that allows 256. You add an extension such that you can use 65536 addresses, and add another 150 devices. Now you have six addresses left under the old scheme (and lots under the new). But do you have a way to discover whether any of the first hundred devices break soon? Or even the 150 new devices? You could add a device on a new-only address before you run completely out of the old-compatible addresses, but that won't test completely. There might still be devices that will connect, but log the connections improperly, or have a buffer overrun and crash randomly, or, or, or. There might be software on a device that supports only old addresses, even though the device itself supports the extension scheme. If the network is a big one, where different parties own and operate the devices, then you may well be completely unable to test whether the extension scheme is universally supported. Before the day when you run completely out of unextended addresses, that is. Contrast this with a dualstack approach, where you can make a list at any time: THESE devices are on v4 only and will be a problem when v4 runs out, THOSE OTHERS are on v4+v6.
- Arnt 11y agoI am overcome by a desire to mention an anecdote... about the financial-services company with three old servers that didn't support the new buzzword, but there was some magic compatibility and everything seemed to work. Until there was a lawsuit, a subpoena and it turned out that data sent among the three old servers used some legacy protocol without mandatory logging as demanded by law.
- ay 11y agoIP options were not an option, unfortunately. One of the many studies: http://www.eecs.berkeley.edu/Pubs/TechRpts/2005/EECS-2005-24.pdf http://www.eecs.berkeley.edu/Pubs/TechRpts/2005/EECS-2005-24...
- crusso 11y agoThat study is about using options on the network today, not really about creating a standard for the options that would handle the address space issue with the knowledge that support would roll out over time. Any solution will involve some changes to network infrastructure. If they had simply added some bytes to the address and not tried to tackle every other perceived wrong with IPv4, we wouldn't be talking about this exact same problem 17 years after IPv6 was introduced.
- deleted 11y ago[deleted]