Re: [dns-privacy] Last Call: <draft-ietf-dprive-rfc7626-bis-03.txt> (DNS Privacy Considerations) to Informational RFC

[Eric Rescorla <[e-mail]>]

On Thu, Jan 9, 2020 at 8:49 AM S Moonesamy <[e-mail]> wrote:

>
> >That's a very serious misrepresentation of DoH. Counter-example:
> >Google Chrome did DNS resolution with UDP, a long time ago.
>
> I mentioned web browser and not Google Chrome.  I tested a web
> browser which is not Google Chrome.  The DNS queries were sent to the
> local resolver.  I did another test with Firefox.  The DNS queries
> were also sent to the local resolver.
>

I think you're misunderstanding Stephane.

You wrote:
"The choice of resolvers was previously made by the network on which
the user was connected.  Recently, the Internet Engineering Steering
Group approved the standardization of a mechanism so that the choice
can be made by a web browser. "

This isn't correct. Web browsers have *always* been able to choose their
own resolver because DNS is just UDP packets, which the browser is quite
capable of sending (e.g., QUIC, WebRTC). Historically, browsers have
chosen to use the system resolver which customarily gets its choice of
resolver from the network, however, Chrome, at least, for some time has
done DNS resolution itself, albeit using the same resolver as the system
resolver used. However, they could easily have chosen to use 8.8.8.8
(or some other resolver) instead.

The point here is that DoH is orthogonal to the question of which resolver
you use.

-Ekr