Re: [dns-privacy] Concerns around deployment of DNS over HTTPS (DoH)
Kenji Baheux <kenjibaheux@google.com> Wed, 13 March 2019 04:34 UTC
Return-Path: <kenjibaheux@google.com>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6238412D826 for <dns-privacy@ietfa.amsl.com>; Tue, 12 Mar 2019 21:34:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.5
X-Spam-Level:
X-Spam-Status: No, score=-17.5 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, HTML_MESSAGE=0.001, 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=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vlq5Y6waz-pm for <dns-privacy@ietfa.amsl.com>; Tue, 12 Mar 2019 21:34:49 -0700 (PDT)
Received: from mail-lj1-x22f.google.com (mail-lj1-x22f.google.com [IPv6:2a00:1450:4864:20::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E5BF1277DB for <dns-privacy@ietf.org>; Tue, 12 Mar 2019 21:34:48 -0700 (PDT)
Received: by mail-lj1-x22f.google.com with SMTP id z20so274791ljj.10 for <dns-privacy@ietf.org>; Tue, 12 Mar 2019 21:34:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=lWJqqGWQlzrKkjzbP7eknMa6zezjSHaV3yNZREVN5c0=; b=Rn2311sxyHO8dg0caDtyjsqctTXekrZ3PiPWtU0VpG5jadosVQ3XwJjT70ZprNVtPs gmc8ljQHYfqgF2Wpgk5qUSw14fMxy0DinG4gtY1fpUgVvrupwoVgUEPxdo2u39FIUj7G aqYGx/eqocjzQEG0kJ7QUJEXYhyExuudr7ThgNF6uk4zz9rtU6WBAv0SZPO4xk1iuiyl Sif6r22QmUCxdVh4QtDJLV655QbqGtI0/1Y+/WHaovP1L3PooD1ajHc/aUsxjS4kmuOz D2FItQaI5cCk0IbBfUnbwEASBFAB3s5jyoYalC0nUZMz6UUroJDdJIfTCJ/jjCVMpovT A5AQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=lWJqqGWQlzrKkjzbP7eknMa6zezjSHaV3yNZREVN5c0=; b=W7zkFzpBIAYQBByfU/WkJVejIEjlzJ6BkVms/H5fzpovL7bt3fc4WcLzN4TYI5TXJe 2LBmra67I2IATFbMaXWvyzZgPEd3IW2dtYPX09RjErvYhzPOis5Iy3wRmhA0quFHAOlu V5LXD+uS7v0jYkdmt8xC9QgF9w3EWKNY6TbJnGFZOL0X+l0V3uekBFN1l9nZLPjP1C3I 9mSWkxImgW4VQ2c8nKbJoGQ8ustN76n7Nd00u7DnCxp0JTaJVhCLQKNbCHQ/27Junf5p DKlQnNSN2Pfy9SHjptrkq+AKsPYtJxifhEeXouWADOhttRZXnQ1vEDi9h2orAHg/+ZQP PhUg==
X-Gm-Message-State: APjAAAUMtwcEqSQkLtpzTs5izSPpIjmGD8b6nsnR7qJ9DIDrpTDesf9d dTSUoPR8nswK/lW3Zp5r1F/3N6vsjO7zDfTLF6w/SGVfDEY=
X-Google-Smtp-Source: APXvYqxdSnjzSwIyZD3RBAPRmvCrl6+9LTypRGtBujFiviN5uaLAxVvTpuIiCtFaa8jV0YJ6ITanfGMC+dADmHBHLk8=
X-Received: by 2002:a2e:2ce:: with SMTP id y75mr21156976lje.126.1552451686803; Tue, 12 Mar 2019 21:34:46 -0700 (PDT)
MIME-Version: 1.0
References: <CADWWn7W19TX7Q8gQTJFHvUxg7jpR8UB8033QtcPK-N7wKafQKw@mail.gmail.com> <alpine.LRH.2.21.1903122346180.26130@bofh.nohats.ca>
In-Reply-To: <alpine.LRH.2.21.1903122346180.26130@bofh.nohats.ca>
From: Kenji Baheux <kenjibaheux@google.com>
Date: Wed, 13 Mar 2019 13:34:34 +0900
Message-ID: <CADWWn7WmRFz-vr+ur8b+1UEr9FagFOk7Y1F2cU+EMnwq4Bv=MA@mail.gmail.com>
To: Paul Wouters <paul@nohats.ca>
Cc: dns-privacy@ietf.org
Content-Type: multipart/alternative; boundary="0000000000005307030583f253ce"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/MIAcwUu2Pnmr_0JwlSvgm-F-s-o>
Subject: Re: [dns-privacy] Concerns around deployment of DNS over HTTPS (DoH)
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Mar 2019 04:34:51 -0000
On Wed, Mar 13, 2019, 12:49 Paul Wouters <paul@nohats.ca> wrote: > On Wed, 13 Mar 2019, Kenji Baheux wrote: > > > I'm involved with Chrome's DoH efforts. > > > Our motivations in pursuing DoH in Chrome is to offer our users a better > user experience: > > > Hopefully, some performance wins. > > > Tentative plans: > > > We are considering a first milestone where Chrome would do an > automatic upgrade to DoH when a user’s existing resolver is capable of it. > > I'm confused how these two can both be done? You either prefer the local > ISP over Google DNS, or you prefer the faster of the two. > We would not change the underlying DNS provider. The only thing that would change is how the DNS query is done: vanilla or DoH (if the existing DNS provider is capable of it). Discovery is an open question. Until there is a better discovery story, we could have a list of known-to-be-DoH-compatible DNS providers that we could check against and map accordingly. Obviously, this doesn't scale but it seems reasonable for the experimentation phase (gathering data, etc). > > There are some unanswered questions about how we will be doing that > discovery, and would welcome input from the community. Perhaps, a good > topic for IETF 104. > > that is interesting indeed. You doing some static name lookups to test > would just make those names be in cache and not a good probe. And > probing nonsense is something that you do too much of already and it > is causing too much root zone noise :P > (^ ^; > > PS: I won't be able to join IETF 104 to discuss this face to face > > I'm already envious :) > > Paul >