IETF Logo Mail Archive

Re: [DNSOP] Resolver behaviour with multiple trust anchors

Tony Finch <dot@dotat.at> Thu, 02 November 2017 15:53 UTC

Return-Path: <dot@dotat.at>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90B0013FABC for <dnsop@ietfa.amsl.com>; Thu, 2 Nov 2017 08:53:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 phMJu9k8CV1p for <dnsop@ietfa.amsl.com>; Thu, 2 Nov 2017 08:53:46 -0700 (PDT)
Received: from ppsw-32.csi.cam.ac.uk (ppsw-32.csi.cam.ac.uk [131.111.8.132]) (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 1358F13F710 for <dnsop@ietf.org>; Thu, 2 Nov 2017 08:53:46 -0700 (PDT)
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]:57298) by ppsw-32.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.136]:25) with esmtps (TLSv1:ECDHE-RSA-AES256-SHA:256) id 1eAHoL-0001Qn-2c (Exim 4.89) (return-path <dot@dotat.at>); Thu, 02 Nov 2017 15:53:41 +0000
Date: Thu, 02 Nov 2017 15:53:41 +0000
From: Tony Finch <dot@dotat.at>
To: Paul Hoffman <paul.hoffman@vpnc.org>
cc: Bob Harold <rharolde@umich.edu>, "dnsop@ietf.org" <dnsop@ietf.org>
In-Reply-To: <A1F19B08-DD23-41A7-8FF9-CACB0613527D@vpnc.org>
Message-ID: <alpine.DEB.2.11.1711021549250.3122@grey.csi.cam.ac.uk>
References: <121CDBC2-D68C-48EE-A56E-46C61FC21538@sidn.nl> <CAN6NTqxy4SWxsUNZyBA=1TZxdhWtVxaTDYLoA1qO2nKf202g9w@mail.gmail.com> <E94AE36A-CA69-47DB-A2B7-41D0C3644855@nohats.ca> <4678D8A8-1AA0-4684-BFD1-40C969305C49@icann.org> <alpine.LRH.2.21.1710311541090.23568@bofh.nohats.ca> <54030D6D-0B7D-4408-A50A-FDBD66A940B4@kahlerlarson.org> <CA+nkc8CqoX87L9YPoJfx7dSOZY4Pm5RXKNvKVBkFB_KX+EK4KQ@mail.gmail.com> <A1F19B08-DD23-41A7-8FF9-CACB0613527D@vpnc.org>
User-Agent: Alpine 2.11 (DEB 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/wGI92G7u27Jk36oZ95Ws5ZOlUCE>
Subject: Re: [DNSOP] Resolver behaviour with multiple trust anchors
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Nov 2017 15:53:48 -0000

Paul Hoffman <paul.hoffman@vpnc.org> wrote:
> On 2 Nov 2017, at 8:04, Bob Harold wrote:
>
> > I generally agree with you, but wonder if there is a performance penalty to
> > searching every possible path before failing.  Is that a reasonable concern?
>
> These are reasonable questions, ones that were actively discussed in the PKIX
> world 20+ years ago. The consensus conclusion was that any performance penalty
> was worth the consistency of answers, since the relying part (the stub
> resolver in our case) had no control over the order of evaluation.

It's worth noting that the PKIX chain of trust is a directed graph whereas
the DNS is a tree, and trees are a lot easier to follow. (No loops etc.)

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/  -  I xn--zr8h punycode
Fitzroy: Cyclonic 4 or 5, increasing 6 at times. Slight or moderate. Rain or
thundery showers. Good, occasionally poor.

v2.23.0 | Report a Bug | By Email