5 ms·
There was no such world. IP could be easily widened just by taking IP addresses to 64 bits, allocating some new protocol numbers for that, and keeping everythi
by kazinator 7y ago
There was no such world.
IP could be easily widened just by taking IP addresses to 64 bits, allocating some new protocol numbers for that, and keeping everything exactly the same. In applications, the same old quad dot notation would work textually: 0.0.0.0 to 65535.65535.65535.65535, the latter being the broadcast address and so on.
The IPv4 space could be embedded such that 1.2.3.4 is both an IPv4 address made of octets, and an "IPv5" made of four hexadecades. Gateways and protocol stacks could convert the packet formats on the fly: a wide packet with addresses whose four values are below 256 could be narrowed, and then received received by IPv4. An IPv4 packet could be widened to "IPv5".
No stupid "neighbor" protocol; just good old ARP, widended to 64 bit IP addresses.
Machines now have native integers that can hold a 64 bit IP address; great for all the masking operations in routing logic and whatnot.
- dboreham 7y agoLike TUBA.
- phs2501 7y agoTUBA was TCP, UDP, and the Internet protocols on top of the OSI network stack (CLNP). It's about as from from IPv4 as you could imagine. https://tools.ietf.org/html/rfc1347 https://tools.ietf.org/html/rfc1347
- dboreham 7y agoFor anyone curious why we didn't just widen addresses, this misunderstanding is why ;)
- kazinator 7y agoThe real reason is probably closer to Fred Brooks' "second system effect". A new generation IP was regarded by some over-zealous engineers as an opportunity of putting in all sorts of new requirements. https://en.wikipedia.org/wiki/Second-system_effect https://en.wikipedia.org/wiki/Second-system_effect They also didn't know the story of the King's Toaster. (Since it refers to 80386's and Unix version 8, it must have already been written at the time.) http://www.ee.ryerson.ca:8080/~elf/hack/ktoast.html http://www.ee.ryerson.ca:8080/~elf/hack/ktoast.html
- kortex 7y agoA real engineer would use no microcontrollers, and leverage the physical properties of the materials at hand to automatically lower and raise the toast. https://youtu.be/1OfxlSG6q5Y https://youtu.be/1OfxlSG6q5Y
- cesarb 7y ago"Just widen the addresses" ideas like that are easy to come up with (though they usually keep the IPv4 address as either the prefix or the suffix of the "new" address), but the elephant in the room is always the same: how would a legacy host which only understands classical IPv4 (with 32-bit addresses) talk to a host which only has "new" (wider than 32-bit) addresses?
- deleted 7y ago[deleted]
- kazinator 7y ago> how would a legacy host which only understands classical IPv4 (with 32-bit addresses) talk to a host which only has "new" (wider than 32-bit) addresses? Hosts with 64 bit addresses would have to support 32 bit addresses also, just like is the case with IPv6 hosts that have to have IPv4 stacks. Under 64 bit addresses, it's conceivable that in fact there would not necessarily have to be an entire IPv4 stack; just protocol conversion to widen and unwiden the data format. The stack would have to know that certain connections have IPv4 peers, and so it would parse IPv4 datagrams coming from those hosts, and likewise send them IPv4 datagrams. It could be designed such that if the source and destination addresses (A.B.C.D) of a connection are such that A <= 255 && B <= 255 && C <= 255 && D <= 255, then the hosts may optionally use the smaller IPv4 packet format.
- deleted 7y ago[deleted]
- cesarb 7y agoStart from the other end: how would an IPv4-only host with an IP address of, for instance, 198.51.100.1, initiate a connection to a host with a "new" address of 459.256.369.257? The host at 459.256.369.257 can understand the "198.51.100.1" address, but the host at 198.51.100.1 has no way to represent 459.256.369.257 as the destination address in an IPv4 packet. And even if the answer is "they can't initiate a connection", the same problem also happens in the opposite direction. When the host at 459.256.369.257 initiates a connection to the IPv4-only host at 198.51.100.1, what should it put in the "source address" field, which only has 32 bits since it's an IPv4 packet? If it puts a dummy address there, how would the reply to that packet reach it?
- lmm 7y ago> The IPv4 space could be embedded such that 1.2.3.4 is both an IPv4 address made of octets, and an "IPv5" made of four hexadecades. Gateways and protocol stacks could convert the packet formats on the fly: a wide packet with addresses whose four values are below 256 could be narrowed, and then received received by IPv4. An IPv4 packet could be widened to "IPv5". What problem do you imagine this would solve? IPv4 and IPv6 need to be completely independent, because if an IPv4 router were ever to route an IPv6 packet it would send it to the wrong place, likely into a loop. Worse, such misrouting would be unpredictable as BGP tables shifted, links failed over, etc; you might have packets go around a loop several times and then eventually reach their final destination, you might have packets going fine in one direction but misrouted in the other, etc.. It would be a nightmare to debug. Given that IPv6 packets can never be routed by IPv4 routers, what value is gained by making it easy to embed IPv4 in IPv6? Hosts where both ends have IPv4 addresses ("narrow" in your terminology) are just going to talk IPv4 anyway. And it's not like 4over6 is particularly complex or delaying deployment.
- stingraycharles 7y agoI guess you can have clients that purely talk IPv6 talk with destinations (edge locations) that only talk IPv4, without requiring the whole end-to-end connection and intermediate routers to talk IPv4? You'll just have a router at the end which translates this IPv4-in-IPv6 packet into a pure IPv4 packet and everything will work.
- lmm 7y agoFor a v6-only host to talk to a v4-only host you need a router performing stateful NAT64 at some point (it's fundamentally impossible to statelessly route IPv4 packets to v6 hosts because there aren't enough v4 addresses). While in theory that router could live anywhere on the IPv6 network (and packets are routed to it via normal IPv6), normally you'd have it on the 6-only host's network (and coordinate with their DNS servers if they wanted to be able to connect to 4-only hosts by hostname via DNS64). It's a little ugly, but it's pretty much the same situation those v6-only hosts would be in if they were v4 hosts without public addresses (behind NAT), and they get to use ordinary direct connections when talking to a v6-enabled host on the outside.
- wmf 7y agoHere's a detailed explanation of why that isn't useful: https://hackerfall.com/story/ipv6-non-alternatives-djbs-article-13-years-later https://hackerfall.com/story/ipv6-non-alternatives-djbs-arti... and the HN discussion: https://news.ycombinator.com/item?id=10854570 https://news.ycombinator.com/item?id=10854570
- XorNot 7y agoNo it can not be. Routing hardware is hardware. 32 bits is physically etched into the ASIC chips which do it. If all it took was a software upgrade then IPv6 would be done by now. The IPv4 space is already embedded in the IPv6 space as part of the spec. You can't negotiate a middle ground with hardware.
- kazinator 7y ago> If all it took was a software upgrade then IPv6 would be done by now. Even if the routers were upgradable, there is the problem that IPv4 applications contain hard-coded uses of types like struct sockaddr_in. In some cases, entire programs are replicated just for IPv6: e.g. ping6, telnet6, ... These things don't write themselves.