Re: [Doh] New: draft-livingood-doh-implementation-risks-issues

Eliot Lear <lear@cisco.com> Tue, 12 March 2019 17:09 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 EF5FB131154 for <doh@ietfa.amsl.com>; Tue, 12 Mar 2019 10:09:16 -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_HIGH=-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 Bv2E1f9zQLQp for <doh@ietfa.amsl.com>; Tue, 12 Mar 2019 10:09:15 -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 80097131180 for <doh@ietf.org>; Tue, 12 Mar 2019 10:09:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3103; q=dns/txt; s=iport; t=1552410554; x=1553620154; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=odlw4bHSqsI3KNah6CqITuUNskKeTU++8bEpXsLZOUQ=; b=Kmw/E3mj8wzLw/gkwcOAlHw7uVDwuzhHk9Tf8ps3JwGWirm9PgkuqovI 2Kr9N4CL0O508YQfDABOFM0QQ0DqddA74XL929eVfmwcVz335yfbMnZL+ HRWLFnK1SLzN3fX10Sh8BQU7Vn3vSKwcwGefFSc9WNFDqvsQQvM8hTrD5 Q=;
X-Files: signature.asc : 488
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AHAAAF54dc/xbLJq1kGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAQGBUwIBAQEBAQsBg0chEieNA4xBJZI2hXWBewgDAQGEbAK?= =?us-ascii?q?EWzYHDQEBAwEBCQEDAm0ohUoBAQEDAXkFCwsEARMuVwYTgyIBgW0IsX6FRYR?= =?us-ascii?q?lD4EvAYFIiXuBf4E4DBOCTIg8giYDkUKSbAmEW446GZM8ml+CbgIEBgUCFYF?= =?us-ascii?q?NATGBVjMaCBsVZQGCQT6QDj4DMJE/AQE?=
X-IronPort-AV: E=Sophos;i="5.58,471,1544486400"; d="asc'?scan'208,217";a="10640170"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 12 Mar 2019 17:09:12 +0000
Received: from ams3-vpn-dhcp7163.cisco.com (ams3-vpn-dhcp7163.cisco.com [10.61.91.250]) by aer-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id x2CH9BXN003236 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 12 Mar 2019 17:09:11 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <A027352F-2846-4463-8B02-44A137146799@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_82CE4DB0-9DBB-4290-893F-6779114381FF"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Tue, 12 Mar 2019 18:09:10 +0100
In-Reply-To: <20190312151639.oqgwgdficezoygfr@nic.fr>
Cc: "Livingood, Jason" <Jason_Livingood@comcast.com>, DoH WG <doh@ietf.org>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
References: <EA2A119D-06CF-4B0B-8994-86A99CD8AC0B@cable.comcast.com> <20190309182857.GA29321@laperouse.bortzmeyer.org> <BAB74C4B-D93A-4EBA-8F76-FEC4C68FF753@cable.comcast.com> <20190312151639.oqgwgdficezoygfr@nic.fr>
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-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/HfRaXRo75ywSBTOlGCGw6j7rn58>
Subject: Re: [Doh] New: draft-livingood-doh-implementation-risks-issues
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: Tue, 12 Mar 2019 17:09:20 -0000


> On 12 Mar 2019, at 16:16, Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote:
> 
> It seems to me there is a more profound issue here: should we (the
> IETF), when creating new protocols, ensure that *all* previous usages
> continue to work? Even if we never condoned them?

Wrong questions.  Right questions:

Should the IETF consider the world in which we live and how the protocols we are creating might change that world?
Should we propose mitigations for none, some, or all of the changes?

Eliot