can’t deal with extensions that aren’t encoded in a string-based format …
why exactly is it a required field in EV certificates?
-Tim
From: Clint Wilson
Sent: Wednesday, October 11, 2023 4:48 PM
To: Tim Hollebeek ; CABforum3
Subject: Re: [cabf_validation] EVG 9.8.2
Hi Tim,
I had thought the point of including cabfOrganizationIdentifier was to enable
deprecation of subject:organizationIdentifier, rather than the inverse. It
seems it would be minimally appropriate to understand the discussions and/or
actions ETSI has taken post SC17 to address the topic of
Ballot SC17 added the cabfOrganizationIdentifer, which duplicates the
information encoded in the subject:organizationIdentifier field, just in a
different format/encoding. The subject:orgID field is standardized by ETSI
and used in the processing of eIDAS certificates; on the other hand, to