On Nov 28, 2014, at 8:38 AM, John Levine <jo...@taugh.com> wrote: > For the policy implementing resolvers, I'd suggest less loaded terms than > consensual and non-consensual, since we can rathole forever arguing about > to what degree Comcast's customers consent to having their NXDOMAINs replaced > with search pages. Something like default vs. non-default or opt-in vs. > opt-out > would describe it better.
I don't think "default policy-implementing resolver" makes any sense. While "opt-in policy-implementing resolver" does make sense, "opt-out policy-implementing resolver" does not. I'm not as concerned about the rathole as you are, but I certainly don't want to use terms that make no sense. > I'd also add NOERROR for a successful response with no records, and note that > some software erroneously confuses it with NXDOMAIN. Such a note is beyond the scope of the document (but worthy of its own, maybe), but listing NOERROR seems sensible. --Paul Hoffman _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
