On Tue, Mar 30, 2010 at 09:04:39AM -0700, Nicholas Weaver wrote:
> His linux host would do an A and an AAAA query and, until the AAAA
> query timed out, delay creating connections eg, through SSH, web
> browsing, etc. An amazingly painful experience for him until he
> diagnosed it.
But the answer to this breakage that is being proposed is to turn on,
apparently at ISPs' recursive resolvers, a different kind of breakage,
and one without a useful way to detect when it's no longer needed. In
other words, we'll introduce some sort of bizarre breakage to
dual-stack systems (ones that might work correctly, even) without any
plan for how we'll even know when to turn this breakage off. And this
while we desperately need to wean people off IPv4 and onto IPv6.
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:
1. The customer doesn't break in surprising ways.
2. Other customers don't break for no reason.
3. The customer learns s/he has an issue, and can take steps to
correct it before IPv4 is too expensive to use any more.
I am not among those who think that the number of clients involved
with this is "insignificant". I know that something people sometimes
hear, but the abolute number of people involved does make this a real
problem. I just don't think that the right answer is to break
perfectly well-functioning systems for everyone else in order to work
around clients that are implemented wrong.
A
--
Andrew Sullivan
[email protected]
Shinkuro, Inc.
_______________________________________________
DNSOP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsop
