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

Eliot Lear <lear@cisco.com> Thu, 21 September 2017 11:56 UTC

Return-Path: <lear@cisco.com>
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 91029134B34; Thu, 21 Sep 2017 04:56:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
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: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 18aA3T4Z3P6T; Thu, 21 Sep 2017 04:56:37 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D3B9134B39; Thu, 21 Sep 2017 04:56:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; 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 aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 21 Sep 2017 11:56:34 +0000
Received: from [10.61.237.201] ([10.61.237.201]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id v8LBuYbV027207; Thu, 21 Sep 2017 11:56:34 GMT
To: Mark Nottingham <mnot@mnot.net>
Cc: Adam Roach <adam@nostrum.com>, IETF <ietf@ietf.org>, doh@ietf.org
References: <150549029332.2975.12341647131707994474.idtracker@ietfa.amsl.com> <20170920151458.GA22670@faui40p.informatik.uni-erlangen.de> <eaadc24d-6150-2396-64b6-708266de1c69@nostrum.com> <c06bfd5a-743a-aa9f-68b4-4a60badc8bed@cisco.com> <a34c98e2-7129-1d1a-947b-20cafa236119@nostrum.com> <5e9cb711-d798-c6b9-d6c3-c7619bcbadd7@cisco.com> <2E3B3E8E-7C8D-4662-B5C8-D11C390EE5ED@mnot.net>
From: Eliot Lear <lear@cisco.com>
Message-ID: <7a70c140-9905-db14-66a3-b9bd4ea02fff@cisco.com>
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: <2E3B3E8E-7C8D-4662-B5C8-D11C390EE5ED@mnot.net>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="pPT8WMEb28JQgESOad4IsaeJq2gx0BdR6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/nLyu26O59AeuKgS73nlvjXhSAFo>
Subject: Re: [Doh] WG Review: DNS Over HTTPS (doh)
X-BeenThere: doh@ietf.org
X-Mailman-Version: 2.1.22
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, 21 Sep 2017 11:56:39 -0000

Mark,

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 <lear@cisco.com> 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.

Eliot