Hello, Le Mercredi 31 Mai 2006 20:10, Manfredi, Albert E a écrit : > To enable this, one could assign an option in the IP header, > conceptually similar to the source routing option. So at the end of > the standard IP header would be appended the source and destination > private IP addresses from behind the NAT.
Such a proposal would probably have made sense in the first half of the nineties. I'm actually pretty confident such a proposal has already been made, though I must admit I don't known - at that time I wouldn't have recognized the Internet (let alone IP and IETF) if it ate my ice cream as I was still attending primary school. As you also mention, this would imply extending the Domain Name System, much like IPv6 already did (AAAA), re-did (A6), and then undid (back to AAAA). And it would require updating all IP stacks in, at least, end nodes and NAT boxes. Forgot to mention it would probably wreak havoc to the BSD socket API, and require re-investing all that has been done into IPv6-support in existing applications and network infrastructure again. To sum up, ten years ago, while it would not have been as technically “clean” as IPv6, it would probably have been less costly and disruptive to deploy, all the more as it could probably have been completed in a shorter time frame. Nowadays, the cost would probably outweighs what's left (however huge) to be invested to pursue the IPv6 transition. Regards, -- Rémi Denis-Courmont
pgpuAf9WTtKdP.pgp
Description: PGP signature
-------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
