Re: AAAA records to be added for root servers

[Franck Martin <franck@xxxxxxxxx>]

Seems to me that DNS software at the customer level should be able to respond to the applications immediately from the cache: switch from IPv6 to IPv4 because I have IPv4 info.

The standard behavior would be query with IPv6 the network DNS, and if they answer with IPv6 info, carry on, if they answer no info return error, or they answer switch to IPv4 because I have IPv4 info to give you.

Would that simplify the life of IPv6 applications?

Bill Manning wrote:

On Fri, Jan 04, 2008 at 07:57:29PM -0500, John C Klensin wrote:
  

(3) As Keith Moore has pointed out repeatedly for the general
case and as I and others have pointed out for more specific ones
(including today's mail-and-DNS case), dual stack is a nice
thing to do if one is developing operating systems and maybe if
one is developing servers.  But any form of "the application has
a choice of multiple addresses or interfaces and must choose"
puts the application into the routing business.  
    

	:) welcome to the end2end model and the rise of the
	   stupid network... :)

  

-- 
Franck Martin
ICT Specialist
franck@xxxxxxxxx
SOPAC, Fiji
GPG Key fingerprint = 44A4 8AE4 392A 3B92 FDF9  D9C6 BE79 9E60 81D9 1320
"Toute connaissance est une reponse a une question" G.Bachelard

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________

Ietf@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ietf