first, thank you for this statement, and for the policies it describes.
Puneet Sood wrote on 2019-03-22 15:08:
...
As a core principle, Google Public DNS aims to provide a DNS resolver
that respects our users’ privacy. Towards that goal, we aim to provide
high quality implementations of various DNS transport mechanisms that
our users can use to reach the service. This includes the traditional
UDP and TCP transports as well as DNS-over-TLS and DNS-over-HTTPS that
provide privacy for the user’s communication with a DNS resolver.
-Puneet Sood
TL/Manager for the Google Public DNS team.
this position (for google public dns) is inconsistent with the google
chrome design description here:
Kenji Baheux wrote on 2019-03-23 22:43:
2) What other reasons are you considering when doing DOH instead of DOT
to protect privacy. >
> We are not considering DOT, just DOH.
this disparity is concerning. for reasons amply described here...
From: Brian Dickson <brian.peter.dick...@gmail.com>
Date: Sun, 24 Mar 2019 04:48:27 -0700
Message-ID: <CAH1iCipSi+kT32d78Pi+hwPNyuw=in3utjmscnrs+ug+88g...@mail.gmail.com>
Archived-At:
<https://mailarchive.ietf.org/arch/msg/dnsop/ZKhwanjOyj5YtxzH4QOs8IsPsEs>
...i remain hopeful that google will adopt a DoT support policy for all
services (such as Public DNS) _and all products_ (such as Chrome).
--
P Vixie
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
