[cabfpub] LEI information in web certificates

Mike Reilly (GRC) Mike.Reilly at microsoft.com
Mon Jul 9 15:22:24 UTC 2018

Tim, we attended the GLEIF workshop as well and found the potential use for the LEI interesting.  I've read through the mail thread on this topic between you and Ryan and generally support pursuing options for the CABF to look at some standard as to how LEI may be used for OV and EV certs.  I'd be interested in what others within the CABF think about this topic.  Thanks, Mike

From: Public <public-bounces at cabforum.org> On Behalf Of Tim Hollebeek via Public
Sent: Friday, July 6, 2018 1:30 PM
To: CA/Browser Forum Public Discussion List <public at cabforum.org>
Subject: [cabfpub] LEI information in web certificates

As many of you are aware, the GLEIF foundation recently invited CA/Browser Forum members to its identity management workshop.  Some people have contacted us about the possibility of putting LEI identifiers into web certificates.  This is in some ways similar to the recent proposal from ETSI to put additional identity information into certificates, though it has the advantage that we are free to determine ourselves how best to encode it.

CAs are already allowed to include this information in certificates, assuming it has been appropriately validated.  There is a Global Legal Entity Identifier Index that is authoritative for LEIs.  However it would be valuable if there were a standardized CABF OID and extension so that every CA that chooses to include this information includes it in an interoperable way.  This also allocates the OID in a namespace we control, allowing us to state in the BRs the purpose and semantics of the extension, and require that it only be used for authentic and validated LEIs.

It seems to me that it would be worthwhile to standardize this, instead of every CA coming up with their own way of doing it.  What do other people think?


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cabforum.org/pipermail/public/attachments/20180709/abae0e29/attachment-0003.html>

More information about the Public mailing list