IETF Logo Mail Archive

Re: [yang-doctors] [Last-Call] Yangdoctors last call review of draft-ietf-netconf-trust-anchors-13

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 13 January 2021 01:24 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E79AA3A07E2; Tue, 12 Jan 2021 17:24:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, 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 nGj5lwt4qIAx; Tue, 12 Jan 2021 17:24:45 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 65B573A046B; Tue, 12 Jan 2021 17:24:44 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 91EFB38982; Tue, 12 Jan 2021 20:26:13 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 2UEtQkuwWY3q; Tue, 12 Jan 2021 20:26:13 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 2A0273897F; Tue, 12 Jan 2021 20:26:13 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id B35701F9; Tue, 12 Jan 2021 20:24:42 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: =?us-ascii?Q?=3D=3Futf-8=3Fb=3FSsO8cmdlbiBTY2jDtm53w6RsZGVy=3F=3D?= <j.schoenwaelder@jacobs-university.de>
cc: yang-doctors@ietf.org, last-call@ietf.org, netconf@ietf.org, draft-ietf-netconf-trust-anchors.all@ietf.org
In-Reply-To: <161047687248.13931.17900123352005904827@ietfa.amsl.com>
References: <161047687248.13931.17900123352005904827@ietfa.amsl.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Tue, 12 Jan 2021 20:24:42 -0500
Message-ID: <22275.1610501082@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/XMYEX1AS5r5uU27XmRtWqgj7e4Q>
Subject: Re: [yang-doctors] [Last-Call] Yangdoctors last call review of draft-ietf-netconf-trust-anchors-13
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Email list of the yang-doctors directorate <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jan 2021 01:24:47 -0000

Jürgen Schönwälder via Datatracker wrote:
    > - In 2.2.1, I was not sure what CA certificates are and what EE
    > certificates are. I then tried to guess EE = end entity cert, but
    > this does not explain CA since the term used in crypto types is
    > trust anchor cert. The description in the XML clarified that my
    > guess was kind of correct. Perhaps explain upfront what these
    > acronyms mean? Or perhaps the acronyms can be avoided by simply
    > spelling things out? They do not appear to be used frequently.

    > - s/<!-- Entity Certs/<!-- End Entity Certs/

"End Entity" goes back to RFC2510, and I don't think it's defined in any of
our documents.  I was expecting to see it in RFC4949 or RFC5280, but it's
used in 5280, but not defined.
I guess it comes from X509.v3, which is still behind the stupid paywall.

The term EE/End Entity is in my opinion a great term, but it also took me
awhile to learn it.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

v2.8.7 | Report a Bug | By Email