Re: [Doh] [Ext] Are we missing an architecture? (was Re: DNS Camel thoughts: TC and message size)

Paul Hoffman <paul.hoffman@icann.org> Thu, 14 June 2018 15:22 UTC

Return-Path: <paul.hoffman@icann.org>
X-Original-To: doh@ietfa.amsl.com
Delivered-To: doh@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD138130E62 for <doh@ietfa.amsl.com>; Thu, 14 Jun 2018 08:22:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.107
X-Spam-Level:
X-Spam-Status: No, score=-1.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 kY8-5XZFwAuh for <doh@ietfa.amsl.com>; Thu, 14 Jun 2018 08:22:36 -0700 (PDT)
Received: from out.west.pexch112.icann.org (unknown [64.78.40.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B1C7E130E45 for <doh@ietf.org>; Thu, 14 Jun 2018 08:22:36 -0700 (PDT)
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Thu, 14 Jun 2018 08:22:34 -0700
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1367.000; Thu, 14 Jun 2018 08:22:34 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: DoH WG <doh@ietf.org>
Thread-Topic: [Doh] [Ext] Are we missing an architecture? (was Re: DNS Camel thoughts: TC and message size)
Thread-Index: AQHUApbj6sr7HpgoCUqfpeUX7P+jQqRdpuYAgAFGhACAAAf3gIAAEfgAgAAGfgCAABRdgIAAEW+AgABrFoCAAAVKgIAAO6gAgABglACAAAKdgIAACAoAgAAMTYA=
Date: Thu, 14 Jun 2018 15:22:33 +0000
Message-ID: <3C2F4C66-8CA4-4954-90E3-D63410FAC90B@icann.org>
References: <1E183D79-5716-47E5-8604-A4F5DC7588C2@icann.org> <045241e6-6d9f-162c-6ae3-0b10d59d21de@bellis.me.uk> <6BB0D47F-2BA3-4D9A-A125-1D1E180B06E0@icann.org> <53c320bc-6ea0-21f4-c7a1-1da34bbdb38d@nic.cz> <CAHbrMsBoKE-pfz97ZDb9ReLKMedk2KJ7xLCw_MPmxVtqF7PcuA@mail.gmail.com> <20180613192030.GA2792@jurassic> <CAHbrMsACdaz13v=2jbpZq1RU-_CP36Cgz13iFFWVj8qrjQ0b=g@mail.gmail.com> <20180613205637.GA23215@jurassic> <CAOdDvNr0ob_zhMw1BT_h8n77ecx5vht8WJ7OiwwDPrj0Wxf8SA@mail.gmail.com> <20180614042217.GA25915@jurassic> <20180614044113.GA27115@jurassic> <alpine.DEB.2.20.1806140728270.30130@tvnag.unkk.fr> <74D48781-9F05-482C-ACB2-7AB027611489@sinodun.com> <alpine.DEB.2.20.1806141609050.29598@tvnag.unkk.fr> <D920175F-4D1D-4D68-BCAA-F7FD23072D93@sinodun.com>
In-Reply-To: <D920175F-4D1D-4D68-BCAA-F7FD23072D93@sinodun.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.32.234]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <D4A01EA8F359F84599B10DE0C9287E5F@pexch112.icann.org>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/beh3DS6t6cdO5C70qH6UY_s8w6o>
Subject: Re: [Doh] [Ext] Are we missing an architecture? (was Re: DNS Camel thoughts: TC and message size)
X-BeenThere: doh@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: DNS Over HTTPS <doh.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/doh>, <mailto:doh-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/doh/>
List-Post: <mailto:doh@ietf.org>
List-Help: <mailto:doh-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/doh>, <mailto:doh-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jun 2018 15:22:38 -0000

There were a bunch of DoH implementations at the last IETF Hackathon. The fact that two of these implementations are getting early publicity is not indicative of a trend.

On Jun 14, 2018, at 7:38 AM, Sara Dickinson <sara@sinodun.com>; wrote:
> The observation here is that this shift is being directly driven today by applications wanting to use DoH to their preferred resolver

It is one implementation of one application, not "applications". And Mozilla has not said if they want to use a preferred resolver or are just doing that now so that they can get better measurements about whether or not they want to deploy DoH at all. If Mozilla (or Chrome, or Edge, or ...) turns DoH into a way in the long term to force a lot of DNS traffic to just one preferred resolver, they will rightly suffer people moving away from them. It's pretty trivial to detect this type of behavior.

> for a variety of reasons, not by (for example) operating systems, enterprises, ISPs, end users or the DNS community. 

There was clearly interest in DoH for operating system use (by Stubby). Enterprises have indeed indicated they are interested in DoH to avoid redirecting of their traffic by intermediaries. We haven't heard from ISPs or end users, but we *certainly* have heard interest on this list from the DNS community.

--Paul Hoffman