Rob,

Can you give us an idea of when the report will be out?

p.s. AAAA is deployed too fyi.

thanks

/jim

On Sun, 10 Jun 2001, Rob Austein wrote:

> The basic problem is that neither the IPv6 community nor the DNS
> community has reached a clear consensus on whether the extra features
> of A6 over AAAA are worth the extra cost.  That's not a euphemism for
> "have decided that they're not", I really mean that we have people
> advocating each side in each group and have not answered the question.
> 
> So we attempted to approach the question from the angle of "what does
> IPv6 need the DNS to do?"  Since that question also appears to be a
> potential rathole, we tried to focus on the specific areas in which A6
> would allow us to do things that can't be done with just AAAA and some
> preprocessing during zone file generation.
> 
> All the cases we thought of that would justify A6 appeared to boil
> down to situations where the DNS data would have to change so fast
> that it isn't practical to update the DNS that quickly (eg, rapid
> renumbering, or GSE-like routing).
> 
> So the question to the IPv6 WGs is: is IPv6 going to be doing these
> things?  If so, AAAA probably is not sufficient, and A6 may be the
> answer.  If not, AAAA may or may not be sufficient, but the new
> features that A6 provides don't appear to be justified by IPv6's
> requirements.
> 
> --------------------------------------------------------------------
> IETF IPng Working Group Mailing List
> IPng Home Page:                      http://playground.sun.com/ipng
> FTP archive:                      ftp://playground.sun.com/pub/ipng
> Direct all administrative requests to [EMAIL PROTECTED]
> --------------------------------------------------------------------
> 

--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page:                      http://playground.sun.com/ipng
FTP archive:                      ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------

Reply via email to