On Tue, Mar 30, 2010 at 12:15:39AM -0400, Andrew Sullivan wrote:
:: Rather than having the DNS magically lie to people, why not use the
:: DNS detection mechanism as an indicator that a customer has a broken
:: v6 implementation. Then you can turn off _that customer's_ IPv6
:: connectivity, contact them, and tell them what their problem is. This
:: has three benefits:
The problem here is the ISP doesn't actually know that their users have a
broken v6 implementation -- the only way they can test for it would be if
users went to their portals, which, in most cases, users won't do. So, the
only people who do know if the user has a working v6 implementation are
the content/hosting providers, who have a very limited action they can
take -- either give out AAAA to ISP recursive servers behind which there
are broken users and break those users, or don't hand out AAAA to those
resolvers, thereby not enabling ipv6 for *any* user behind that
resolver, whether they are working or not...
I can tell you that as a content provider, we are not willing to break
those users (would you be willing to negatively impact 400K+ users who
were able to get to you over ipv4 just fine, for the *maybe* 1k users who
could only get to you over ipv6? How about break 400k users so that
1.2M users can get to you over ipv6, even though all of those 1.2M
can get to you over ipv4 just fine?)
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...
Thanks,
-igor (the crazy yahoo guy who presented this) :)
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
