[Doh] Seeking input on draft-03

[Ben Schwartz <[e-mail]>]

Hi all,

The authors of draft-ietf-doh-dns-over-https have been making good
progress, and a draft-03 is now ready with several changes and
clarifications.

One important difference is that draft-03 no longer proposes a
".well-known" entry.  In draft-02 and prior, clients could check for the
presence of a DOH service at the default path, given only the domain name
of a server.  In draft-03, there is no default path, so clients must be
configured with the full URL of the DOH endpoint.

Is this change compatible with your use cases?  Would this alter the way
users interact with your systems?  How do you think DOH client
configuration should work?

Please respond with your thoughts,
Ben Schwartz