Why should anyone care if an internal network is on IPv6 or not? That is probably the silliest part of the NAT66 debate. I am only going to be deploying IPv6 for the few hosts that actually need to receive inbound connections. And I don't expect that to be more than a few hosts on a home network regardless of how much home automation I have.
The only place where we need IPv6 is on the backbone. Folk can run their internal protocols over a transport mechanism of small pyramids with hand engraving performed by a small army of elves for all I care (although I would appreciate a YouTube video of those who are using that mechanism).
If you look at the strategy for the end-of-life for IPv4, surely it will involve placing every network that is not already behind a NAT behind NAT64? As in, the day that IPv4 addresses are no longer being maintained by the NICs and the backbone routers are refusing to accept BGP traffic advertising v4. At that point even NET18 is going to be sequestered behind a NAT because the day that the Internet shuts down IPv4 will come at least 20 years before endpoints stop doing IPv4.
Even if some of my home devices have IPv4, that is not going to be the general case.
If we had assigned five bytes to IPv4 addresses instead of 4 or we had started on a slightly smaller planet, we would not be talking about IPv6 at all, even though 2^40 bytes would clearly be insufficient. Instead we would adopt a two tier architecture and assign IP addresses to networks rather than hosts.
-----Original Message-----
From: ietf-bounces@xxxxxxxx on behalf of Fred Baker
Sent: Tue 12/2/2008 12:54 AM
To: Christian Huitema
Cc: Iljitsch van Beijnum; IETF Discussion
Subject: Re: [BEHAVE] Lack of need for 66nat : Long term impacttoapplicationdevelopers
you might take a look at he nat66 document and the behave IPv4/IPv6
documents. they're pretty different.
On Dec 1, 2008, at 7:07 PM, Christian Huitema wrote:
> Of course, Iljitsch points an interesting issue. If NAT66 behaves
> exactly like, say, NAT 64, then why would the organization bother to
> use IPv6 rather than sticking with net 10?
_______________________________________________
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf
_______________________________________________ Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf