To:
Robert Elz <kre@munnari.OZ.AU>
Cc:
ngtrans@sunroof.eng.sun.com, namedroppers@ops.ietf.org, ipng@sunroof.eng.sun.com, dnsop@cafax.se
From:
Jun-ichiro itojun Hagino <itojun@iijlab.net>
Date:
Wed, 15 Aug 2001 20:40:10 +0900
In-reply-to:
kre's message of Wed, 15 Aug 2001 18:16:22 +0700. <2674.997874182@brandenburg.cs.mu.OZ.AU>
Sender:
owner-dnsop@cafax.se
Subject:
Re: (ngtrans) Joint DNSEXT & NGTRANS summary
> | (2) it is unclear as to how will be doing AAAA synthesis, and we cannot > | ensure that it will happen at the leaf >Who cares? If someone asks for an AAAA, and gets back an AAAA, then >they're happy right? If the server provided an A6, was asked for an >A6, and answered with an A6, it is happy, right? Something between >original (probably stub) resolver and server converted. Who cares >what it was? >The operators of the resolver might care - for lots of reasons, in which >case they provide the back end resolver that does the synthesis. you should care about this. there's no guarantee that AAAA synthesis happen between end client and master/slave nameservers. AAAA will leak from leaf to the core. > | (3a) impose lookup delays to IPv6 clients. >No, no delays at all (other than what is involved in the A6 lookup). if people query both AAAA and A6, there will be more delays. > | (3b) server admins need to maintain both A6 and AAAA in zoen file, > | which is unhappy. >No, only A6 records, that's what AAAA synthesis is all about, remember... you seem to be assuming that there's some AAAA synthesis server between IPv6 end node and nameservers. your assumption does not hold, especially during the transition period. because the assumption does not hold, zone admins need to maintain AAAA records too. itojun