4 ms·
I wrote a proposal back in 1999 or so exploring IPv4-in-IPv4 as an alternative to IPv6. You would have used the outer IP header to traverse the internet backbo
by mhandley 5y ago
I wrote a proposal back in 1999 or so exploring IPv4-in-IPv4 as an alternative to IPv6. You would have used the outer IP header to traverse the internet backbone, and the inner IP header locally. It completely avoided the need to change any inter-domain infrastructure and, with some DNS-based gatewaying where the gateway to the Interent added/removed the outer IP header, could even be incrementally deployed to unmodified end systems (the idea was you would eventually modify end-systems/applications to add the outer header, as this simplifies applications and avoids the DNS hack).
But in the end, IPv6 is cleaner, and it seemed better not to distract too much from progress there. If I'd known it would have taken another quarter century to make much progress, I might have made a different decision.
There were quite a few "extend IPv4" solutions over the years.
- ArchOversight 5y agoISP's can already do that... by repackaging IPv4 traffic into IPv6 (when I worked at an ISP this was an experiment that was being done to test the viability to reduce IPv4 address requirements across the backbone, but you could also tunnel it over IPv4 I guess) so that the traffic traverses their entire network inside an IPv6 tunnel, and would get translated back to IPv4 on the edge. As a user you lose some visibility in terms of what routers your packet traverses, but the same can be said about MPLS tunnels/IPSec tunnels where your packet magically seems to have gone just 1 hop instead of the 10 it actually took.