Re: [dns-operations] [DNSOP] dnsop-any-notimp violates the DNS standards

2015-03-13 Thread Darcy Kevin (FCA)
According to their own statement, Cloudflare perceived the "problem" to be the code-complexity of their DNS implementation -- in particular, they characterized the complexity of their (former) QTYPE=*-handling code as "enormous". Their "fix" was to feign ignorance (RCODE=NOTIMP) of QTYPE=* and

Re: [dns-operations] [DNSOP] dnsop-any-notimp violates the DNS standards

2015-03-10 Thread Darcy Kevin (FCA)
Regarding the statement "query type ANY 'matches all RR types CURRENTLY IN THE CACHE'." Actually, there's nothing in RFC 1034 that clearly *mandates* this behavior -- Section 3.7.1 says only that a QTYPE of * "matches all RR types", whereas Section 5.3.3 ("Algorithm") says to return "the answer

Re: [dns-operations] [DNSOP] dnsop-any-notimp violates the DNS standards

2015-03-09 Thread Darcy Kevin (FCA)
My 2 cents... It is commonplace, these days, to clearly enumerate "MANDATORY TO IMPLEMENT" elements of a protocol specification. But, this was not the typical practice at the time RFCs 1034/1035 was written, and I don't think we can apply modern standards-parlance retroactively. RFC 1034/1035 c