On Mon, Jun 15, 2015 at 11:49:47AM -0700, Paul Hoffman wrote: > > "Name Error" as a synonym for NXDOMAIN seems like it is worth including, > > somewhere. > > Are you sure that "name error" always refers to NXDOMAIN? If not, this is not > a can of worms we should open. >
To the extent it doesn't, such usage is not in line with STD 13. NXDOMAIN is the neologism here. RFC 1035 names RCODE 3 as "Name Error". > > In "origin", (a), the usual word for this in my experience is "apex". It > > would seem as well to mention apex here. If we're able to provide value > > judgements, we might recommend apex over this use of origin. > > "Apex" is defined two terms later". > I think Joe is right that people usually use "apex" to mean "origin" in the way the document defines it. I think we are attempting to reinforce a distinction that used to be in the RFCs but that seems to have blurred over time: the difference between the graph-theoretic space of the DNS and the implementation. It might be worth adding a sentence, however, that notes the way the terms are often used interchangably. > I searched for supporting material in RFC 5155 that could explain why to use > opt-out in words that would make sense in this document; I failed. If you > find some, that would be great. > If I recally correctly, it was excluded on socio-political grounds. A -- Andrew Sullivan [email protected] _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
