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

[Juergen Schoenwaelder <[e-mail]>]

To clarify my comment: I was confused by the acronyms that were never
expanded, not by the expanded terms themselves. In other words, this
is mostly an editorial nit to get fixed.

/js

On Wed, Jan 13, 2021 at 12:54:55PM +0000, tom petch wrote:
> From: netconf <[e-mail]> on behalf of Michael Richardson <[e-mail]>
> Sent: 13 January 2021 01:24
> 
> 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.
> 
> <tp>
> End Entity has been around TLS since at least RFC5246.
> 
> Tom Petch
> 
> 
> --
> Michael Richardson <[e-mail]>   . o O ( IPv6 IøT consulting )
>            Sandelman Software Works Inc, Ottawa and Worldwide
> 
> 
> 
> 

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: [phone]         Campus Ring 1 | 28759 Bremen | Germany
Fax:   [phone]         <https://www.jacobs-university.de/>