On Tue, 30 Mar 2010, Igor Gashinsky wrote:
So, the question now is, what can be done? By no means do I think that lying based on transport is a good idea, however, I simply don't have a better one, and, this is a real problem, which is delaying ipv6 deployment for a number of people. So, if anybody else has a better option, I (and other content providers) would love to hear it! Unfortunately, this is the best we've come up with thusfar...
I'm not sure how this trick is going to work when you step back a bit: You'll still need to maintain a whilelist of networks where the ISP has agreed to implement this hack in their DNS recursive server. You can't start serve AAAA records to others.
The only reason for doing the hack would be if you had stricter requirements than Google. They whilelist ISPs' resolvers but trust that the ISPs resolve issues that get reported to them. You would be whilelisting ISPs but require a mechanism that cuts down on broken IPv6 experience. You're right that even a google-whitelisted ISP user could experience issues (but not report to the ISP).
-- Pekka Savola "You each name yourselves king, yet the Netcore Oy kingdom bleeds." Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
