Re: [Doh] WG Review: DNS Over HTTPS (doh)

Eliot Lear <> Thu, 21 September 2017 11:56 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 91029134B34; Thu, 21 Sep 2017 04:56:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Status: No, score=-14.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 18aA3T4Z3P6T; Thu, 21 Sep 2017 04:56:37 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 9D3B9134B39; Thu, 21 Sep 2017 04:56:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=5203; q=dns/txt; s=iport; t=1505994996; x=1507204596; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to; bh=oZLj8IhbonyfYcaHwetvAmtKa0kSIm3NZJ/Xr4+moo4=; b=iJUmpjZJOMMLcwnGoh+wODVRaRwBUqP3lF9qc5gs6UqN6te4dk8mOhTw Bp+jrODt+W//+wTjPLx8EJi5pXqr2gXGXbq5qAZ2TnsjXlTy+UgSih9Uh r0/V4RGNbGoUe+1NtwUlAOLNaf1FEh4t86YSZhsIiF0pIkLiflj3VNr8v 0=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CHAQA+qMNZ/xbLJq1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBhD5uJ4N2ixSQTQkikGuHUAcDhTsChFUVAQIBAQEBAQEBayiFGAE?= =?us-ascii?q?BAQECASNWBQsLBAoKKgICVwYNBgIBAYonCKZ/gicnilcBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEOD4MrhWILgnKIDoJgBaEThDuCIY17ghOFaoNahySVOoE5NSKBDTI?= =?us-ascii?q?hCBwVh2c+NokiAQEB?=
X-IronPort-AV: E=Sophos;i="5.42,425,1500940800"; d="asc'?scan'208,217";a="697356832"
Received: from (HELO ([]) by with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 21 Sep 2017 11:56:34 +0000
Received: from [] ([]) by (8.14.5/8.14.5) with ESMTP id v8LBuYbV027207; Thu, 21 Sep 2017 11:56:34 GMT
To: Mark Nottingham <>
Cc: Adam Roach <>, IETF <>,
References: <> <> <> <> <> <> <>
From: Eliot Lear <>
Message-ID: <>
Date: Thu, 21 Sep 2017 13:56:37 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="pPT8WMEb28JQgESOad4IsaeJq2gx0BdR6"
Archived-At: <>
Subject: Re: [Doh] WG Review: DNS Over HTTPS (doh)
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: DNS Over HTTPS <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 21 Sep 2017 11:56:39 -0000


I'll stop after this message.  Please see below:

On 9/21/17 1:41 PM, Mark Nottingham wrote:
> On 21 Sep 2017, at 7:28 pm, Eliot Lear <> wrote:
>> You still don't have a reasonable answer for discovery.
> Discovery isn't necessary for the primary use case -- user-driven configuration of their browser.

Earlier you wrote:

> The use case that I believe most have in mind is "as a user, I want to configure my [browser, OS] to use *this* DOH service for DNS resolution" -- where that configuration is manual; e.g., a configuration textbox or dropdown in the browser, or a file in /etc.

Please get your story straight.  Bypassing enterprise DNS entails all
the risks I previously mentioned.  No one here as mentioned a means to
mitigate those risks.  The only way I can think of is by tying this
function into the OS and using the existing discovery mechanisms.  But
if all you've got as a browser, everything looks like Javascript, I suppose.