Re: [dns-privacy] [Ext] Revised opportunistic encryption draft
Tony Finch <dot@dotat.at> Fri, 06 November 2020 00:59 UTC
Return-Path: <dot@dotat.at>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 051023A09BD for <dns-privacy@ietfa.amsl.com>; Thu, 5 Nov 2020 16:59:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 qeMtCcgMbYHq for <dns-privacy@ietfa.amsl.com>; Thu, 5 Nov 2020 16:59:02 -0800 (PST)
Received: from ppsw-30.csi.cam.ac.uk (ppsw-30.csi.cam.ac.uk [131.111.8.130]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 788653A0779 for <dprive@ietf.org>; Thu, 5 Nov 2020 16:59:02 -0800 (PST)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://help.uis.cam.ac.uk/email-scanner-virus
Received: from grey.csi.cam.ac.uk ([131.111.57.57]:59562) by ppsw-30.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.136]:25) with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) id 1kaq5k-000Cfd-e5 (Exim 4.92.3) (return-path <dot@dotat.at>); Fri, 06 Nov 2020 00:59:00 +0000
Date: Fri, 06 Nov 2020 00:59:00 +0000
From: Tony Finch <dot@dotat.at>
To: Brian Dickson <brian.peter.dickson@gmail.com>
cc: Eric Rescorla <ekr@rtfm.com>, Paul Hoffman <paul.hoffman@icann.org>, "dprive@ietf.org" <dprive@ietf.org>
In-Reply-To: <CAH1iCirz27EoahrYE8z9AV=Cf=A-i=iPP1deOYPWO8_k1mL+XA@mail.gmail.com>
Message-ID: <alpine.DEB.2.20.2011060046200.20609@grey.csi.cam.ac.uk>
References: <C0CBEBC5-D28A-46C0-AE50-078710015466@icann.org> <alpine.LRH.2.23.451.2010301202350.2587497@bofh.nohats.ca> <2444B21B-9465-4A5B-97CC-AF809309300A@icann.org> <CABcZeBPZFY9aQ5Nb0q_4uTMFRbY3-S2rus4vaeLaUmvU+h_ftg@mail.gmail.com> <2D07CBD0-30CE-418E-AD05-02E0A5EDB79F@icann.org> <CABcZeBNdNnyjzk0mOtfix=OvVTEpPzegEw_V5QfKvYtkFV+zOw@mail.gmail.com> <CAH1iCirz27EoahrYE8z9AV=Cf=A-i=iPP1deOYPWO8_k1mL+XA@mail.gmail.com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/lFzJVzrqFvWkeUX61HWZ5L-xn7c>
Subject: Re: [dns-privacy] [Ext] Revised opportunistic encryption draft
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Nov 2020 00:59:04 -0000
Brian Dickson <brian.peter.dickson@gmail.com> wrote: > > I think a better comparison (better meaning more relevance and closer > tracking of the transition and operation) would be the transition of SMTP > to SMTP using TLS without downgrade susceptibility. Yes. That was made a lot more difficult because it went through an intermediate step of unauthenticated TLS, so the protocols and implementations had to be designed to deal with the fact that a very large proportion of existing server certificates were wrong. I would prefer not to have to deal with that again. > First, a simple assertion: DoTA is only possible/available if it is > configured by the authoritative DNS operator. Thus, the control of the > state of whether DoTA is available for zones operated by that operator, > resides entirely with the operator. This also means that, depending on > how DoTA availability is signalled or detected, the methods of > correcting faults in the DoTA operation can vary. Thus, selecting > signalling/detection mechanisms should take the corrective actions > available into consideration. IMHO this should actually dominate the > design. Yes. > Third, I'll restate it here: The important characteristic is that whatever > method(s) are used, they need to be completely downgrade resistant to all > attack mechanisms, and they need to fail safe. With the caveat that incremental deployment needs to be possible: If a zone is hosted by multiple authoritative providers, it should be possible for one of those providers to deploy DoT without the co-operation of the zone owner or other providers, and without compromising the availability of the zone. That implies a zone only gets a guaranteed private transport if all of its authoritative providers guarantee a private transport. Tony. -- f.anthony.n.finch <dot@dotat.at> http://dotat.at/ Sole: East 4 to 6, occasionally 7 at first. Rough. Showers later. Good.
- [dns-privacy] Revised opportunistic encryption dr… Paul Hoffman
- Re: [dns-privacy] Revised opportunistic encryptio… Paul Wouters
- Re: [dns-privacy] [Ext] Revised opportunistic enc… Paul Hoffman
- Re: [dns-privacy] Revised opportunistic encryptio… John Levine
- Re: [dns-privacy] [Ext] Revised opportunistic enc… Eric Rescorla
- Re: [dns-privacy] [Ext] Revised opportunistic enc… Paul Hoffman
- Re: [dns-privacy] [Ext] Revised opportunistic enc… Paul Hoffman
- Re: [dns-privacy] [Ext] Revised opportunistic enc… John R Levine
- Re: [dns-privacy] [Ext] Revised opportunistic enc… Hollenbeck, Scott
- Re: [dns-privacy] [Ext] Revised opportunistic enc… Eric Rescorla
- Re: [dns-privacy] [Ext] Revised opportunistic enc… Brian Dickson
- Re: [dns-privacy] Revised opportunistic encryptio… Tony Finch
- Re: [dns-privacy] [Ext] Revised opportunistic enc… Tony Finch
- Re: [dns-privacy] [Ext] Revised opportunistic enc… Peter van Dijk
- Re: [dns-privacy] [Ext] Revised opportunistic enc… Paul Hoffman
- Re: [dns-privacy] [Ext] Revised opportunistic enc… Brian Dickson
- Re: [dns-privacy] [Ext] Revised opportunistic enc… Peter van Dijk
- Re: [dns-privacy] [Ext] Revised opportunistic enc… Brian Dickson
- Re: [dns-privacy] [Ext] Revised opportunistic enc… Peter van Dijk
- Re: [dns-privacy] [Ext] Revised opportunistic enc… Tony Finch
- Re: [dns-privacy] [Ext] Revised opportunistic enc… Paul Wouters
- Re: [dns-privacy] [Ext] Revised opportunistic enc… Paul Wouters
- Re: [dns-privacy] [Ext] Revised opportunistic enc… Tony Finch
- Re: [dns-privacy] [Ext] Revised opportunistic enc… Brian Dickson
- Re: [dns-privacy] [Ext] Revised opportunistic enc… Tony Finch
- Re: [dns-privacy] [Ext] Revised opportunistic enc… Peter van Dijk
- Re: [dns-privacy] [Ext] Revised opportunistic enc… Peter van Dijk
- Re: [dns-privacy] [Ext] Revised opportunistic enc… Tony Finch
- Re: [dns-privacy] [Ext] Revised opportunistic enc… Shumon Huque
- Re: [dns-privacy] [Ext] Revised opportunistic enc… Brian Dickson