There certainly is a big difference between the term certification (an act) and the term certificate (a data value). Certification implies that the CA does some validation before issuing a certificate. When a read an article and hit the term certificate authority, I stop reading thinking the guy cannot even get the term right. He/She does not know what a CA is.
Erik -----Original Message----- From: Spasm <[email protected]> On Behalf Of Michael Richardson Sent: 26 June 2020 23:57 To: [email protected]; Russ Housley <[email protected]>; [email protected]; Ben Kaduk <[email protected]> Cc: Ryan Sleevi <[email protected]>; Nico Williams <[email protected]> Subject: [lamps] on certification authorities. Russ Housley <[email protected]> wrote: > Thank you. Many people get it wrong, but X.509 and RFC 5280 (as well > as the earlier versions in RFC 2459 and RFC 3280) all use > {CA=} "certification authority". I guess it might be worth spreading this point more widely :-) I'll all for stamping out the wrong expansions, even if it sometimes seems pendantic. I'm told that Google is about to start their Cloud *Certificate* Authority. If that happens, I believe that any chance to assert the term will be completely lost :-) On the other hand, if they go with "certification authority", then perhaps the tide of the terminology will be reversed. -- Michael Richardson <[email protected]>, Sandelman Software Works -= IPv6 IoT consulting =- _______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
