On Wed, 10 Mar 2004, Tim Chown wrote: > In draft-ietf-dnsop-ipv6-dns-issues-04.txt: > > "This memo presents operational considerations and issues with IPv6 > Domain Name System (DNS), including a summary of special IPv6 > addresses, documentation of known DNS implementation misbehaviour, > recommendations and considerations on how to perform DNS naming for > service provisioning and for DNS resolver IPv6 support, > considerations for DNS updates for both the forward and reverse > trees, and miscellaneous issues." > > So this draft already contains DNS implementation misbehaviour issues, > which are closely related to misbehavior-against-aaaa. Given the > ipv6-dns-issues draft is an "overview" and already exists, I feel we > should incorporate misbehavior-against-aaaa into ipv6-dns-issues, > especially if the document can contain recommendations on avoiding > (or detecting) the problem.
Umm. ipv6-dns-issues document gives a summary of misbehavior-against-aaaa. Naturally, instead of giving a summary, it could give a full-fledged description. But that would bloat the ipv6-dns-issues document by 5-10 pages. Is that what we want? Isn't it better to just give overview, and keep detailed description of misbehaviour in a separate document? That's how I feel at least -- I've always envisioned ipv6-dns-issues as "what's up with IPv6 and DNS -- if interested, look [here and there] for more details" not "full compendium of all the gory details of IPv6 and DNS". -- Pekka Savola "You each name yourselves king, yet the Netcore Oy kingdom bleeds." Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings . dnsop resources:_____________________________________________________ web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html
