Re: [DNSOP] [Doh] New I-D: draft-reid-doh-operator

Puneet Sood <> Fri, 22 March 2019 22:09 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 2134512762F for <>; Fri, 22 Mar 2019 15:09:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -17.501
X-Spam-Status: No, score=-17.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id vpQ7qdvx-h4y for <>; Fri, 22 Mar 2019 15:08:59 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::c2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id DDCBA131530 for <>; Fri, 22 Mar 2019 15:08:58 -0700 (PDT)
Received: by with SMTP id l5so2814476ywa.0 for <>; Fri, 22 Mar 2019 15:08:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=BBgHaxCTxjfEZlRuABV6w65bb+fKt31xyTSKufVCrxw=; b=km/ixRhGOL49p98O/a/CbS/ITaHMkPK63YNJjLz0fceQd7Or9rPJvvi3SZYkZPwM5I yJm5yX3YEWHBWmJRhYCPEYphhWYU7T7sXqElxLEn0+Ckqo2Bv6FNDaxIZ38xSSpDg96I vXNj/uy0+7zJLTZPP6cHWOfC7HZeVb5jvq/NHAuFWw45/ANk0RsLewXBPE/AC8feVODK J1DT9DB5Ckw51Qq6lyCED9Jy5BA0Iv2BvHfJWHC6PByJSPOSK4lnu3WemfRWRrxC+Es2 wP7g6HLE0/SH5Wft8xm50QouWBv2KvCmlFnh8X8rH71sgDmmYNu4STINkO/x8PSU7iAH W3pg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=BBgHaxCTxjfEZlRuABV6w65bb+fKt31xyTSKufVCrxw=; b=mqdfF29+RbsD40TtwCBWDHpTRWBDewWc8J+LYV2GXxfLyKbwxhQv4vTZPBvfsAvLHE e/SXK84hzpLye9UNlHWeZew0VNg1d7n7SfZtvHA2uZs1ASelWh7lk17FxQnsfXxB7kS3 RrznRJOg+3Xs2CY88hSnNOWkF7i47s9w/a8Q/myPPHc/89TI/RUzZ7qN7oyZ9QwCi/M3 qk6hDYoUbRXC/T+fwvVg5lrEyMZMOo81lfGKpb9u9z3h+QuZNWTYpRrMgy0JwsD9ZneB 09y2tpn0MkSDr8zcntQz/awCnDSUBRKYwOBAjAnWd5a38IovAgZeDFUKuuSIHUzkWcOw xo7A==
X-Gm-Message-State: APjAAAXcYFym+UeVgffbryUfYhLkSJqCbDe/ww38KgwX7P911vMEmxta m2h9BE1Ume6OpdKTeISHyWQkhT7A3ZkW+POmv9Gv+w==
X-Google-Smtp-Source: APXvYqwIsYedSOJlGUjHj9Toj+ACruI6tzGv4kQwtZ08KBVJN60VNvxenKxiBCDS1dPs0sHjWxg6isI9ZtgbhWAzv+M=
X-Received: by 2002:a25:4643:: with SMTP id t64mr10435697yba.462.1553292537751; Fri, 22 Mar 2019 15:08:57 -0700 (PDT)
MIME-Version: 1.0
References: <> <3457266.o2ixm6i3xM@linux-9daj> <> <1914607.BasjITR8KA@linux-9daj> <> <> <> <> <> <> <> <>
In-Reply-To: <>
From: Puneet Sood <>
Date: Fri, 22 Mar 2019 18:08:45 -0400
Message-ID: <>
To: 神明達哉 <>
Cc: Joe Abley <>, Ted Hardie <>, DoH WG <>, Brian Dickson <>, Jared Mauch <>, dnsop <>, paul vixie <>, Michael Sinatra <>, Stephen Farrell <>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <>
Subject: Re: [DNSOP] [Doh] New I-D: draft-reid-doh-operator
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 22 Mar 2019 22:09:02 -0000


There has been much discussion in the IETF lists over the impact of
using DNS-over-HTTPS (DoH) in a network. We would like to clarify the
Google Public DNS position on this topic. The post I am replying to is
particularly relevant since it makes some assumptions about the plans
of the Google Public DNS service.

For future support of a RFC 8484 compliant service, we plan to do the following:
* Serve RFC 8484 compliant DoH from the well known Google Public DNS
anycast IP addresses (e.g. on the standard HTTPS port 443.
* Migrate our existing DoH services to the well known Google Public
DNS anycast IP addresses, including the beta version (at and IETF draft version (at

The Google Public DNS anycast IP addresses are distinct from the IP
addresses used to host web content for Google properties. This will
allow operators to control access to the Google Public DNS DoH service
on their networks without impeding access to other Google services.

For DoH implementers we want to ensure the same access to our
implementation whether it is a Google product (like the Chrome
browser) or a third-party product. To this end we aim to track IETF
work on standardized ways to detect DoH support by the system-selected
DNS resolver service (like

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.

PS: I am attending IETF 104 and will be available for face-to-face discussion.

On Wed, Mar 20, 2019 at 2:40 PM 神明達哉 <> wrote:
> At Wed, 20 Mar 2019 12:38:05 +0100,
> Joe Abley <> wrote:
> > > Often as an industry we may discuss various solutions that are great for oneself but don’t scale when looking at the big picture.
> >
> > I think what we are seeing is the fundamental tension between privacy and control. You need to give up some privacy in order to make the control possible; you need to give up some control in order to afford privacy.
> > Some in this thread want certainty that they are able to exercise control, e.g. for devices in their network.
> > Some in this thread want certainty that they can obtain privacy, e.g. for for their device in any network.
> [...]
> Thank you for the nice, concise summary.  I think it's well-balanced
> observation of where we are.  (I'm so glad I can finally see a
> constructive post after seeing a common pattern of boring IETF
> discussion, where people with different opinions just keep stating
> their views without making any real progress:).
> > Seems to me that there's a middle ground within sight here.
> >
> > Standardise this privacy mechanism, and specify (with reasoning) that it should be implemented such that the existence of the channel (but not the content) can be identified as distinct from other traffic by third parties. Maybe specify use of a different port number, as was done with DoT.
> I see that those who want to exercise control can live with this (or
> at least using a different set of IP addresses for DoH servers than
> those for other ordinary web services).  But I'm not so sure if that's
> acceptable for the other group..  In that sense I'm curious whether
> some big possible DoH providers are now willing to accept this middle
> ground.  If my memory is correct the longer term plan at Google (and
> maybe also Clouldflare?) is to provide DoH service on the same IP
> addresses as those for other ordinary and popular web services (and on
> port 443, of course), so that an intermediate operator cannot easily
> block access to their DoH services.
> > Those who choose to ignore that direction and create a covert channel using port 443 instead will do so. Nothing much we can do to stop that today (I guarantee it is already happening). The future is not really different.
> True.  But I think giant providers tend to respect a community
> consensus.  Niche or really malicious players may/will still ignore
> it, but it would be very difficult for them to collocate their DoH
> services with other important web services that can hardly be blocked,
> so it shouldn't be a big problem for "those who want certainty of
> control".  So if we can really agree on the above "middle ground" and
> publish a BCP or something that describes the consensus, I guess we
> can now really work on technical issues.  But I'm not sure if we can
> reach that consensus.
> --
> JINMEI, Tatuya
> _______________________________________________
> Doh mailing list