kaih(_at_)khms(_dot_)westfalen(_dot_)de (Kai Henningsen) quotes me as saying:
therefore after a middle state of perhaps five more years, the majority
of services that anybody will want to access will be v4+v6 reachable,
and it will be realistic to consider provisioning first nat/v6 and then
nonat/v6 endhosts.
...and then adds...
;; ANSWER SECTION:
ftp.ipv6.debian.org. AAAA 3ffe:1001:210:16::5
ftp.ipv6.debian.org. AAAA 3ffe:8171:10:16::5
ftp.ipv6.debian.org. AAAA 2001:708:310:54::99
ftp.ipv6.debian.org. AAAA 2001:718:1:1:2d0:b7ff:fe46:fbb8
ftp.ipv6.debian.org. AAAA 2001:760:202:103::4
ftp.ipv6.debian.org. AAAA 2001:770:18:2::1:1
ftp.ipv6.debian.org. AAAA 2001:b68:e207::3
that's nonuseful in two ways. first, get rid of those "3ffe" things.
second, put these on the main name, don't make people use an alternate
name. for example:
ftp.freebsd.org has address 62.243.72.50
ftp.freebsd.org has address 204.152.184.73
ftp.freebsd.org has IPv6 address 2001:4f8:0:2::e
or
www.isc.org has address 204.152.184.88
www.isc.org has IPv6 address 2001:4f8:0:2::d
or
ftp.isc.org has address 204.152.184.110
ftp.isc.org has IPv6 address 2001:4f8:0:2::18
or
www.netbsd.org has address 204.152.190.12
www.netbsd.org has IPv6 address 2001:4f8:4:7:2e0:81ff:fe52:9a6b
;; ANSWER SECTION:
www.ipv6.microsoft.com. 3600 IN AAAA 2002:836b:9820::836b:9886
www.ipv6.microsoft.com. 3600 IN A 131.107.152.134
lovely addresses. but they should be attached to www.microsoft.com, not
www.ipv6.microsoft.com. this works fine and causes no problems for ipv4-only
hosts. using an alternate name for ipv6 in 2004 or later is chickenhearted.
--
Paul Vixie
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf