IETF Logo Mail Archive

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

Eliot Lear <lear@cisco.com> Mon, 11 March 2019 07:43 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 1DD471310E7 for <doh@ietfa.amsl.com>; Mon, 11 Mar 2019 00:43:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.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, 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 9oLWGNc-Wr-q for <doh@ietfa.amsl.com>; Mon, 11 Mar 2019 00:43:53 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A0DBB128678 for <doh@ietf.org>; Mon, 11 Mar 2019 00:43:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5414; q=dns/txt; s=iport; t=1552290233; x=1553499833; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=DcB1rZoMP0dZE6brX63jnlzVOiDN1SC0hX9H++6hZyA=; b=AIxtMhEn906zMtpIaSjq3qcF//yRUrJ6lXDHLYPFUNX3wiUvqsxv0arN 0Nu570PyXjB0o2/TC38BsEIFD2dig/ZTa9k86CdCQ5rUoBWDrsuqifogY BrVqqwJHbBYq0RY5cm4YyffuTTENKcl8KRuRMdNW5qN684NfZsouSxWYU M=;
X-Files: signature.asc : 488
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0A9AABpEYZc/xbLJq1kGQEBAQEBAQEBAQEBAQcBAQEBAQGBZYNpEieECYh5jFySM4duCAMBAYRsAoRbOBIBAQMBAQcBAwJtKIVKAQEBAwEjVgULCwQUKgICVwYTFIMOAYFtCK8EgS+FRYRRD4EvgUmJe4F/gTgfgkyICzGCJgOKSIYoTJJlCYRZjjMZgXmFZotbmlGCbgIEBgUCFYFeIYFWMxoIGxVlAYJBPoFYF44fPgMwkD4BAQ
X-IronPort-AV: E=Sophos;i="5.58,467,1544486400"; d="asc'?scan'208,217";a="10607167"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 11 Mar 2019 07:43:50 +0000
Received: from ams3-vpn-dhcp7163.cisco.com (ams3-vpn-dhcp7163.cisco.com [10.61.91.250]) by aer-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id x2B7hnZN005204 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 11 Mar 2019 07:43:50 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <825A194A-1DC5-44C0-A7CD-34E0B8C8A5E7@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_680F1187-45F8-4E2C-8FD9-252BAB4A43A8"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Mon, 11 Mar 2019 08:43:48 +0100
In-Reply-To: <CAHw9_iLS7UEv3ckqQ+ML_Fu6ANjfkDbnq3V-H=58dXAT43hzvA@mail.gmail.com>
Cc: "Livingood, Jason" <Jason_Livingood@comcast.com>, Jim Reid <jim@rfc1035.com>, DoH WG <doh@ietf.org>, Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Warren Kumari <warren@kumari.net>
References: <155218771419.28706.1428072426137578566.idtracker@ietfa.amsl.com> <FACB852B-4BC4-4234-A728-9068708EFB10@rfc1035.com> <20190310080101.GA11452@laperouse.bortzmeyer.org> <FCA55D75-08BA-419A-8089-A4C986C21770@cable.comcast.com> <CAHw9_iLS7UEv3ckqQ+ML_Fu6ANjfkDbnq3V-H=58dXAT43hzvA@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.102.3)
X-Outbound-SMTP-Client: 10.61.91.250, ams3-vpn-dhcp7163.cisco.com
X-Outbound-Node: aer-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/a3HRFJ747GMXo6za8kGJ0oMRS0s>
Subject: Re: [Doh] New I-D: draft-reid-doh-operator
X-BeenThere: doh@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 11 Mar 2019 07:43:55 -0000

Hi Warren,

> On 11 Mar 2019, at 03:27, Warren Kumari <warren@kumari.net> wrote:
> 
> DoH is a protocol - the concerns you are talking about (and I'm glad they are being discussed, they are important policy discussions) are not specific to DoH -- this sentence works just as well with DNS-over-TLS, plain DNS, using some completely proprietary name resolution mechanism. It is trivial for any "large app" writer to invent a proprietary way to do DNS resolution - please please, let's keep the DoH (protocol) versus "apps doing their own resolution" separate.


A standardized DoH enables alternative interoperable service infrastructure to be formed and not be easily blocked by access providers.  That’s different from all other models, and it has ramifications. The point is that our providing the path of interoperability means, as Paul Vixie points out, that we owe it to ourselves and to the community to understand those ramifications.

We have been here before.  When the IAB allocated 10/8, they were providing an interoperable method for private networks in direct response to people picking networks out of a hat.  It too had substantial ramifications.[1]*

It is absolutely possible for the existing infrastructure to adopt DoH, and I suspect that will happen.  But that is not the driving use case today.  An alternate DNS infrastructure is the driving use case, and we should be mindful of that.

Eliot
[1] RFCs 1597, 1617, 1918, et al.
* Amusingly, Paul and I were heavily involved in that discussion as well.

v2.23.0 | Report a Bug | By Email