Le 31 mars 2010 à 22:55, Dan Wing a écrit : > But Remi's point is that those same systems (running Windows XP > and IE6) using 6rd will be denied the ability to access content > via IPv6. Which removes an incentive for ISPs to add 6rd (and > offload the NAT44 they may soon have to install).
If I may, Dan, the fact that Free's native IPv6 is implemented with 6rd is not significant. (Hosts don't know about it, and Free could switch to dual stack in all their routers without users being able to notice it.) The important point is that Free offers native IPv6 to its customers in addition to IPv4, and that their DNS servers are both accessible in IPv4 AND capable to return AAAAs : - Dual-satck hosts behind Free's CPEs get their DNS addresses as usual in IPv4. - They query these DNS servers for both As and AAAAs. - They use IPv6 when getting AAAA responses (with A responses or alone) This has the great advantage to work without dual-stack hosts needing to acquire one or several IPv6 DNS addresses. (Means to acquire such addresses, such as DHCPv6 or RFC 5006, are not available in all hosts). In my understanding, this has been key for IPv6 to be actually used as soon as Free's CPEs advertised IPv6 prefixes on its customer LANs. Cheers, RD _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
