Geoff,
Here are the definitions from X.509:
X.509, Clause 3.3 (Definitions):
certification authority (CA): An authority trusted by one or more
users to
create and assign public-key certificates. Optionally the
certification
authority may create the users' keys.
authority: An entity, responsible for the issuance of
certificates. Two types
are defined in this Specification; certification authority which
issues public-key
certificates and attribute authority which issues attribute
certificates.
CA-certificate: A certificate for one CA issued by another CA.
X.509, Clause 7 (Public-keys and public-key certificates):
An end-entity certificate is a certificate issued by a CA to a
subject that is
not an issuer of other public-key certificates.
A CA-certificate is a certificate issued by a CA to a subject that
is itself a
CA and therefore is capable of issuing public-key certificates.
CA-certificates
can be themselves categorized by the following types: [ ...
self-issued certificate,
self-signed certificate, cross-certificate].
Dave
Geoff Huston wrote:
> Now i'm in a terminology soup too.
>
> I thought that it was appropriate to talk about a CA, where CA stands
> for "Certification Authority", which is an entity that issues digital
> certificates for use by other parties, so it was appropriate to talk
> about a CA's manifest, CRLs issued by a CA and certificates issued by
> a CA,
>
> You are proposing to use the term "CA certificate" instead.
>
> Now for me the "CA certificate" is not the active entity, its the "CA".
>
> I looked arounf in RFC5280 and did not find any use of "CA
> certificate" and heading off into wiki-land also found use of the term
> "CA", but not "CA Certificate" as an activity entity.
>
> So I'll hold off on this and see if others could offer views on what
> is usual here in terms of accepted terminology.
>
_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr