Transitioning to IPv6 == dual-stack (Re: AAAA records to be added for ro

Hallam-Baker, Phillip wrote:
[..]
> example.com MX  1 1 1 smtp1.example.com
> smtp1.example.com A 10.1.1.1
> smtp1.example.com AAAA ......
Which is a perfect example of dual-stack.

As for 'home users', they will get an IPv4 NAT while IPv6 will be e2e.

> So what if you can pull up the .com domain via IPv6? The DNS server
> still has to be IPv4 capable or the query will quickly fail at
> microsoft.com, google.com or wherever.
In the mean time:

http://www.microsoft.com.sixxs.org
http://www.google.com.sixxs.org

or:
http://www.kame.net.ipv4.sixxs.org

if you have IPv4 but want to look at IPv6 only sites.

As "The Internet" for most people is SMTP (see above for the solution)
and HTTP (just add a IPv6/IPv4 proxy somewhere) there is not an issue at
all with going to IPv6 except for enabling proxies at the right places,
configuring tools to use them and getting the connectivity to the users.
For everything else SOCKS does still exist.

Greets,
 Jeroen

signature.asc
Description: OpenPGP digital signature

_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf