<HTML>
<HEAD>
<TITLE>Re: Access to the IPv4 net for IPv6-only systems, was: Re: WG Action: Conclusion of IP Version 6 (ipv6)</TITLE>
</HEAD>
<BODY>
<FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12.0px'>Iljitsch,<BR>
<BR>
<BR>
Tunneling is great, but it requires to allocate an IPv4 address... that I may not have in the first place.<BR>
<BR>
- Alain.<BR>
<BR>
<BR>
On 9/28/07 4:39 PM, "Iljitsch van Beijnum" <iljitsch@muada.com> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12.0px'><BR>
<BR>
On 28-sep-2007, at 6:25, Jari Arkko wrote:<BR>
<BR>
>> And make it works both way, v4 to v6 and v6 to v4.<BR>
>> And also don’t call it NAT-PT. That name is dead.<BR>
<BR>
> For what it is worth, this is one of the things that I want<BR>
> to do. I don't want to give you an impression that NAT-PT++<BR>
> will solve all the IPv6 transition issues; I suspect dual stack<BR>
> is a better answer. But nevertheless, the IETF needs to<BR>
> produce a revised spec for the translation case. Fred and<BR>
> I are organizing an effort to do this.<BR>
<BR>
The problem with NAT-PT (translating between IPv6 and IPv4 similar to <BR>
IPv4 NAT) was that it basically introduces all the NAT ugliness that <BR>
we know in IPv4 into the IPv6 world. Rather than "solving" this issue <BR>
by trying harder, I would like to take the IETF to adopt the <BR>
following approach:<BR>
<BR>
1. for IPv6-only hosts with modest needs: use an HTTPS proxy to relay <BR>
TCP connections<BR>
<BR>
2. for hosts that are connected to IPv6-only networks but with needs <BR>
that can't be met by 1., obtain real IPv6 connectivity tunneled on-<BR>
demand over IPv6<BR>
<BR>
The advantage of 1. is that proxies and applications that can use <BR>
proxies are already in wide use. The advantage of 2. is that it <BR>
provides real IPv4 connectivity without compromises. Different hosts <BR>
(even on the same subnet) can have different IPv4 connectivity (NAT/<BR>
no NAT, firewalled/unfirewalled) without having to provision the <BR>
complete path between the user and the edge of the network <BR>
specifically for that type of connectivity. And no lost addresses for <BR>
subnetting etc.<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12.0px'><BR>
</SPAN></FONT>
</BODY>
</HTML>