Re: [Doh] Associating a DoH server with a resolver

[Ben Schwartz <[e-mail]>]

Hi Paul, thanks for the continuing work on this topic.

Two related questions:
1. Does the resolver have to return its own IP in the RR for
resolver-addresses.arpa, or can it return some other IP addresses?
2. If a client has some OS-specific way to enumerate the DNS server IPs for
the default network interface, is it still required to perform "Step 1"?
(Most OSes do have some enumeration mechanism like this.)

Other minor comments:
On Section 4, User Interface: I don't see the need for a user interface
here.  In my view, opportunistic security generally shouldn't require user
action and shouldn't produce a user-visible change.

I think interaction with DoT is worth discussing here, even though it's
probably trivial.  If I can probe for DoT and (with this draft) DoH, which
one do I probe first, and which should I prefer if both succeed?

--Ben

On Tue, Oct 23, 2018 at 4:15 PM Paul Hoffman <[e-mail]> wrote:

> Post-RFC-publication greetings. One of the topics that has been active in
> the DNS community since the standardization of DoH is how a browser or web
> application could use the resolver that the operating system on which it is
> running as a DoH server, or at least to use a DoH server associated with
> that resolver. I have taken a few stabs at designing a protocol to make it
> possible to fulfill that need; the result is the draft below.
>
> The draft is still in a very early stage. In fact, I've changed the
> underlying mechanism three times already because I forgot what browsers and
> operating systems could not do. I *think* the current draft is possible,
> but would not be surprised if someone pointed out that even this attempt is
> wrong. Regardless, the desire for such functionality seems strong.
>
> Also note the Security Considerations section of the draft. In short: all
> this gives you is opportunistic encryption because (I believe) we can't get
> any better now. I would be happy to be wrong about that, of course.
>
> Thoughts?
>
> --Paul Hoffman
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
>
>         Title           : Associating a DoH Server with a Resolver
>         Author          : Paul Hoffman
>         Filename        : draft-hoffman-resolver-associated-doh-04.txt
>         Pages           : 8
>         Date            : 2018-10-23
>
> Abstract:
>    Browsers and web applications may want to know if there are one or
>    more DoH servers associated with the DNS recursive resolver that the
>    operating system is already using.  This would allow them to get DNS
>    responses from a resolver that the user (or, more likely, the user's
>    network administrator) has already chosen.  This document describes a
>    protocol for a resolver to tell a client what its associated DoH
>    servers are.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-hoffman-resolver-associated-doh/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-hoffman-resolver-associated-doh-04
>
> https://datatracker.ietf.org/doc/html/draft-hoffman-resolver-associated-doh-04
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-hoffman-resolver-associated-doh-04
>
> _______________________________________________
> Doh mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/doh
>