On Apr 29, 2015, at 12:54 PM, Warren Kumari <war...@kumari.net> wrote: > > First off - thanks for writing this. I personally *hate* writing > terminology sections in drafts; that someone is willing to write an > entire terminology draft, especially one on DNS fills me with awe... > > Anyway, Section 3: > "Some of response codes that are defined in [RFC1035] have gotten > their own shorthand names. Some common response code names that > appear without reference to the numeric value are "FORMERR", > "SERVFAIL", and "NXDOMAIN". All of the RCODEs are listed at > http://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml, > although that site uses mixed-case capitalization, while most > documents use all-caps." > > This is all true, but I'm not sure it says enough. I've used the term > NXDOMAIN in a few documents, and folk have pointed out that the are > not actually defined (or that it is an implementation specific term > (because of case?!)) , so we end up with things like: > "... MUST return a DNS response with the RCODE set to 3 (also commonly > known as an 'NXDOMAIN')". > > I realize that this is a terminology draft, and not a definition doc, > but if it had something like: > > NXDOMAIN -- A colloquial expression for RCODE 3, also commonly written > as 'NXDomain' or 'Non-Existent Domain' > or something similar we could write cleaner documents....
We had a definition for NXDOMAIN in an earlier version of the draft, but were asked to take it out. I'm with Warren on this (it should be in there), so maybe the WG wants to talk about this more... --Paul Hoffman _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
