On Sun, 24 Mar 2019 at 11:46, Paul Hoffman <paul.hoff...@icann.org> wrote:
> > > I'm also not too hot for conflating "user consciously changes > > /etc/resolv.conf or equivalent" with "application makes the choice for > the > > user". > > The split here is more "someone changes from traditional without the user > knowing, when the user cares". If you have a better way to express that, > that would be great. > > > Perhaps we should talk about 'Per-application stubs'? Because this is the > > nub. > > Maybe, but I'm hesitant to make the break that way because some > applications' stubs use the traditional resolver, others don't. I would be > hesitant to conflate those two. > I don't think the current wording for DaO expresses the same point that you've made here. In particular, mentioning that DaO might refer to a user modifying /etc/resolv.conf is inconsistent with the intent that DaO is sending queries somewhere other than where the traditional configuration says. /etc/resolv.conf (and its equivalents in non-unix OSes) *are* the traditional place to configure that. Whatever that file says, I think any resolver that is consulting that file to find its upstreams is doing DaT. How about: DaO: DNS resolution between a stub resolver and a recursive resolver that differs from the recursive resolver configured in the traditional location(s) for a system. DaO can be configured by a user changing where a stub resolver gets its list of recursive servers, or an application running RDoT or DoH to a resolver that is not the same as the resolver configured in the traditional location for the operating system.
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
