4 ms·
> 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 stack
by 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.