On Wed, 31 Mar 2010, Dan Wing wrote: :: Users running IE6 today are IPv4-only users. If/when they go :: to IPv6, they will be running Windows 7 and whatever browser :: is shipped by Microsoft.
Why do you say that? As far as I know, IE6 is an ipv6-capable browser, as long as it's going to FQDN's.. So, what about IE6/XP users who installed bittorent clients (or spyware/trojans) that enabled ipv6 for them without the user knowing about it? :: It seems solvably operationally, by asking ISPs to point their :: IPv4-only subscribers at an ISP-operated DNS server which :: purposefully breaks AAAA responses (returns empty answer), and :: to point their dual-stack subscribers at an ISP-operated DNS :: server which functions normally. :: :: Advanced IPv4-only users wanting to do AAAA queries (e.g., :: Teredo users, 6to4 users, etc.) should be sufficiently advanced :: to point themselves at the ISP's normal nameserver or a :: public DNS server on the Internet (e.g., Hurricane :: Electric's, Google's, etc.). That won't affect users running :: uTorrent (which uses Teredo to provide IPv6 connectivity) :: because it doesn't do AAAA queries to find peers. This is *exactly* what we are proposing -- the feature to return empty answers would be needed for ipv4-only subscribers in order to keep them ipv4-only. Also, if a fully ipv6-capable user visits that person's home, the recursor would then be able to make the call on if they should pass through AAAA to that particular user or not... I am by no means advocating to make this behavior a default, just a feature. Thanks -igor _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
