Re: [DNSOP] Definition of "trust anchor"

Petr Špaček <petr.spacek@nic.cz> Mon, 26 March 2018 12:39 UTC

Return-Path: <petr.spacek@nic.cz>
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 AB8C4124205 for <dnsop@ietfa.amsl.com>; Mon, 26 Mar 2018 05:39:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.01
X-Spam-Level:
X-Spam-Status: No, score=-7.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nic.cz
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 2YTFlaI57_UV for <dnsop@ietfa.amsl.com>; Mon, 26 Mar 2018 05:39:01 -0700 (PDT)
Received: from mail.nic.cz (mail.nic.cz [217.31.204.67]) (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 0E1001241F8 for <dnsop@ietf.org>; Mon, 26 Mar 2018 05:39:00 -0700 (PDT)
Received: from [IPv6:2001:1488:fffe:6:37:44ff:fe34:d861] (unknown [IPv6:2001:1488:fffe:6:37:44ff:fe34:d861]) by mail.nic.cz (Postfix) with ESMTPSA id ABA9360933 for <dnsop@ietf.org>; Mon, 26 Mar 2018 14:38:58 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1522067938; bh=Kf8U0wURfrYuovbTIGYs5bddCuSsNcAgDtOFaWV2wxA=; h=To:From:Date; b=UPjbFUeiMa9Wkjh6UbP4wjXfcTS5igLBDNLSievZ+LLRAigtExYkaNrgY83yOAlD7 zAuJjsxH//+dwetknklFbmDXYp1Mxm5bxtk49XI2bDP+EzsKn3Sv+9vhi36Ity3BWi 9ziWebxcg/Lzf9uvbDUT/wHZGjRJcVqOadUlfvxw=
To: dnsop@ietf.org
References: <90927103-F76F-488D-898C-514655CB9035@vpnc.org> <CAKr6gn07qX=V_o1CT0w91e3N7p+xeVrE_j13RnyyL-TYaYMSYg@mail.gmail.com>
From: Petr Špaček <petr.spacek@nic.cz>
Organization: CZ.NIC
Message-ID: <2b81d986-6853-725a-36dc-673ee90759c6@nic.cz>
Date: Mon, 26 Mar 2018 14:38:58 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <CAKr6gn07qX=V_o1CT0w91e3N7p+xeVrE_j13RnyyL-TYaYMSYg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: clamav-milter 0.99.2 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/YM09cMBaSy5QrAb8qP_96OTE5Dw>
Subject: Re: [DNSOP] Definition of "trust anchor"
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: Mon, 26 Mar 2018 12:39:08 -0000

On 26.3.2018 12:17, George Michaelson wrote:
> This doesn't seem a good fit for the PKI definition of a TA.
> 
> You can have several TA. any are sufficient to define a trust point to
> anchor validation. you don't care which.
> 
> how the path is built, is not the same as where it terminates. top
> down or bottom up is legal in PKI.

I propose to keep the citation as is and add clarifying sentence:

"This definition does not prescribe way how implementation of DNSSEC
validation builds authentication chain."

Petr Špaček  @  CZ.NIC

> 
> -G
> 
> On Sun, Mar 25, 2018 at 8:21 PM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:
>> The current text is:
>>
>> "A configured DNSKEY RR or DS RR hash of a DNSKEY RR.  A
>> validating security-aware resolver uses this public key or hash as
>> a starting point for building the authentication chain to a signed
>> DNS response." (Quoted from <xref target="RFC4033"/>, Section 2)
>>
>> The WG has has a preference for quoting from RFCs, but there was also some
>> hesitation about this. How would people change this, possibly updating RFC
>> 4033?
>>
>> --Paul Hoffman