IETF Logo Mail Archive

Re: [DNSOP] Configured Trust Anchor vs. DS record

Evan Hunt <each@isc.org> Thu, 09 November 2017 17:48 UTC

Return-Path: <each@isc.org>
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 8253D12878D for <dnsop@ietfa.amsl.com>; Thu, 9 Nov 2017 09:48:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-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 a07_uvgfzhq1 for <dnsop@ietfa.amsl.com>; Thu, 9 Nov 2017 09:48:06 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) (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 AB4531286B2 for <dnsop@ietf.org>; Thu, 9 Nov 2017 09:48:06 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [149.20.48.19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 28B133BAC8A; Thu, 9 Nov 2017 17:48:05 +0000 (UTC)
Received: by bikeshed.isc.org (Postfix, from userid 10292) id 11344216C1C; Thu, 9 Nov 2017 17:48:05 +0000 (UTC)
Date: Thu, 09 Nov 2017 17:48:05 +0000
From: Evan Hunt <each@isc.org>
To: Petr Špaček <petr.spacek@nic.cz>
Cc: dnsop@ietf.org
Message-ID: <20171109174804.GA63012@isc.org>
References: <5C194845-AB79-47DE-B936-97560D071C5D@icann.org> <b21647d7-a710-e5f7-048f-d90eccc79c0f@nic.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <b21647d7-a710-e5f7-048f-d90eccc79c0f@nic.cz>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/YgH1PSlWkSSPAZtKy5e1jZF2NeM>
Subject: Re: [DNSOP] Configured Trust Anchor vs. DS record
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, 09 Nov 2017 17:48:12 -0000

On Thu, Nov 09, 2017 at 03:48:26PM +0100, Petr Špaček wrote:
> Nice write-up Edward! You have nicely summarized why Mark and me agree
> that validator should use longest suffix match when selecting TA to
> validate data.

+1.

> Things might get even more complicated when negative trust anchors are
> configured, bleh.

Fortuantely a negative trust anchor is a longest suffix match too.

-- 
Evan Hunt -- each@isc.org
Internet Systems Consortium, Inc.

v2.23.0 | Report a Bug | By Email