On Wed, 17 Dec 2003, Eric A. Hall wrote: > A couple of critical points to keep in mind here. First is that RFC 1886 > (the ADDR spec) already defined a just-include rule for additional data, > and draft-hall-qtype-addr-01 just tries to optimize the existing rule.
Whether this optimization is appropriate is a different subject.. > Second is that getting incomplete additional-data is going to be > unavoidable -- perhaps a legacy cache only returns the A RRs in subsequent > responses, one of which goes to your host. Given these considerations, > incomplete additional-data is just something that clients are going to > have to deal with regardless of what we do here. It's a fact of life. I'm not sure if we have to resign to the fact of incomplete additional-data. In your example, wouldn't the legacy cache not be able to handle the AAAA record query in the first place if it wouldn't return the AAAA records from its cache -- I don't somehow this particular failure mode. -- 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
