[Smcwg-public] Cardinality of subject fields

Sebastian Schulz sebastian.schulz at globalsign.com
Tue Jul 13 15:01:26 UTC 2021


Hey Corey, Hey All,

 

Agreed - would be good to clarify that right off the bat. Is there a reason
why multiple instances of the S field should be supported? For the
organisational Identifier the different registration schemes are a valid
point.

 

Generally, I'd say that having multiple instances of attributes present
significantly complicates validation and increases the risk of the
certificate representing outdated information at some point during its
validity. But given your argument for OID and the widespread use of multiple
OU for all sorts of information it might be yet another case of something
we'd want to avoid for "Strict" and allow for other profiles?

 

Best,

Seb

 

Sebastian Schulz
Product Manager Client Certificates

 

From: Smcwg-public <smcwg-public-bounces at cabforum.org> On Behalf Of Corey
Bonnell via Smcwg-public
Sent: 13 July 2021 15:16
To: SMIME Certificate Working Group <smcwg-public at cabforum.org>
Subject: [Smcwg-public] Cardinality of subject fields

 

Hello,

When reviewing the proposed set of allowed/required subject fields for the
profiles we have discussed this far, I realized that there is room for
better clarity regarding the allowed number of each attribute type that may
be present in each subject. For example, the current specification leaves it
unclear whether multiple CN attributes may be present in the subject Name.
The cardinality of each attribute type is currently left unstated in the TLS
BRs, which has led to a lack of clarity and disagreements on the allowed
number of various attribute types.

 

To prevent this confusion and provide concrete written guidance, I suggest
that we add a column to the profiles spreadsheet that indicates whether
multiple instances of an attribute type are allowed.

 

To start, I propose that the following attributes be allowed to appear more
than once:

*	OU (if we decide to allow its presence at all)
*	streetAddress
*	organizationalIdentifier (if different registration schemes are
specified)

 

All other attribute types must not appear more than once in each subject.

 

Thoughts?

 

Thanks,

Corey

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cabforum.org/pipermail/smcwg-public/attachments/20210713/b46d6252/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 8432 bytes
Desc: not available
URL: <http://lists.cabforum.org/pipermail/smcwg-public/attachments/20210713/b46d6252/attachment-0001.p7s>


More information about the Smcwg-public mailing list