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

2015-03-13 Thread D. J. Bernstein
I remain puzzled at the entire technological motivation that CloudFlare claims for this deliberate creation of interoperability problems. In particular, what exactly is the programming difficulty that they claim they're encountering in implementing QTYPE=*? Are they also having trouble

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

2015-03-12 Thread D. J. Bernstein
Paul Wouters writes: So if the MX or record has expired from the cache but another RRtype with larger TTL (say NS) is still in there, your ANY query will fail to find records. The client is behaving correctly. The ANY query isn't guaranteed to find the MX, but you're wrong in claiming

[DNSOP] dnsop-any-notimp violates the DNS standards

2015-03-09 Thread D. J. Bernstein
My qmail software is very widely deployed (on roughly 1 million SMTP server IP addresses) and, by default, relies upon ANY queries in a way that is guaranteed to work by the mandatory DNS standards. Specifically, query type ANY matches all RR types for that node on that server. There's an example

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

2015-03-09 Thread D. J. Bernstein
Edward Lewis writes: Operators are not bound to comply with what the IETF documents. As I said before, this is making a mockery of the IETF standardization process. Instead of * obeying the existing mandatory standards, * giving due respect to the installed base relying on the standards,