On Sat, 3 Apr 2010, Brian E Carpenter wrote: :: I prefer the current situation, where occasionally I have to :: disable IPv6 manually due to being on an IPv6-broken network :: where DNS serves up AAAA records and my regular tunnel is too :: slow. This seems OK, since people using v6 on XP are normally doing :: so as conscious early adopters.
A few months ago I woudl have agreed with you -- anybody who configures IPv6 on windows XP woudl be concidered a "power user", and therefore can suppot and troubleshoot themselves. Unfortunately, a few months ago I found out that one of the torrent clients is enabling IPv6 on XP machine without users even knowing about it. Now, the game has changed, because it's not only powerusers who have ipv6 configured, it's everyone, and I can no longer rely on them to fix themselves, so, now I need to find a way to not break those users when I hand out AAAA without having them be involved. :: I do think that Google's solution to this, i.e. being selective :: about who gets the AAAA records in the first place, is much less :: of hack with less harmful side effects. :: :: Surely a better hack would be for recursive resolvers in IPv6-broken :: networks not to serve up AAAA records at all? Tunnel users could :: always find another resolver. It is the same hack. You would use that very same feature that was developed to accomplish this (filter-aaaa) -- what's more, when your network stops being v6-broken, you get the extra benefit that the users who can query your dns resolvers over ipv6 can now get AAAA's as first step of rollout... -igor -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
