Amazon Instant Video and NAT64/DNS64

Brian E Carpenter brian.e.carpenter at gmail.com
Thu Nov 29 09:01:05 CET 2012


On 28/11/2012 21:29, Cameron Byrne wrote:
> Phillip,
> 
> On Wed, Nov 28, 2012 at 11:41 AM, Philipp Kern
> <philipp.kern at fsmi.uni-karlsruhe.de> wrote:
>> Cameron,
>>
>> am Wed, Nov 28, 2012 at 09:15:15AM -0800 hast du folgendes geschrieben:
>>> Just FYI on what IPv4 literals look like to IPv6 + NAT64/DNS64
>> I still wonder why we don't push the NAT64 prefix down to the clients who could
>> then do the v4 to v6 conversion themselves and appear as they are dual-stacked.
>>
> 
> We will.  What you described is called 464XLAT
> http://tools.ietf.org/html/draft-ietf-v6ops-464xlat-08, and the prefix
> discovery is at
> http://tools.ietf.org/html/draft-ietf-behave-nat64-discovery-heuristic-13

Even without that, DNS64/NAT64 in the host was always considered a possibility,
especially if you want DNSSEC to work. But as RFC 6147 says "The main drawback
of this mode is its deployability, since it requires changes in the end hosts."

    Brian


More information about the ipv6-ops mailing list