Below I'm just expressing the basic concept I have in mind, without proposing any changes to the TLS BRs wording for now.
In my opinion, it would be better to specify in the TLS BRs that the company name inserted in the organizationName attribute (where applicable) SHOULD always include the company type (where applicable). For example, if an OV certificate is issued to the (fictitious) company "Funky Clothes Ltd", then organizationName should have the value "Funky Clothes Ltd" and not simply "Funky Clothes".
I believe it's appropriate to do this, at least to avoid the ambiguity that arises from homonyms, and it also seems to me to be in the "spirit" of the TLS BRs (perhaps even more so in the EV GLs where the company type is denoted with "prefixes or suffixes"), and it seems to me that in practice CAs almost always follow this rule, although not exactly always. I would therefore welcome an addition to the BRs to clarify that the company type, when applicable, should always be inserted in the organizationName.
How about this?
Below I'm just expressing the basic concept I have in mind, without proposing any changes to the TLS BRs wording for now.
In my opinion, it would be better to specify in the TLS BRs that the company name inserted in the
organizationNameattribute (where applicable) SHOULD always include the company type (where applicable). For example, if an OV certificate is issued to the (fictitious) company "Funky Clothes Ltd", thenorganizationNameshould have the value "Funky Clothes Ltd" and not simply "Funky Clothes".I believe it's appropriate to do this, at least to avoid the ambiguity that arises from homonyms, and it also seems to me to be in the "spirit" of the TLS BRs (perhaps even more so in the EV GLs where the company type is denoted with "prefixes or suffixes"), and it seems to me that in practice CAs almost always follow this rule, although not exactly always. I would therefore welcome an addition to the BRs to clarify that the company type, when applicable, should always be inserted in the organizationName.
How about this?