[Smcwg-public] rfc822Name and/or otherName of type id-on-SmtpUTF8Mailbox

[Stefan Selbitschka]

Hello everyone,

from a consumer (MUA) point of view I vote for option 1)

"a least one rfc822Name as required with an option for additional 
rfc822Names or id-on-SmtpUTF8Mailbox"

This would give the best interoperability since some MUAs require the 
sender email address of a signed message to be in rfc822Names of 
subjectAltName of the signing certificate. If we allow certificates 
without an email in rfc822Name there will be compatibility issues.

Otherwise it would give MUAs a guaranteed source of information for work 
with.

regards
stefan


On 2/14/22 17:18, Stephen Davidson via Smcwg-public wrote:
> Hello:
> 
> In our discussions we have accommodated both the use of rfc822Name and 
> the use of otherName of type id-on-SmtpUTF8Mailbox in public trust S/MIME.
> 
> I’d like to clarify something as it appears in several areas of the 
> SMIME BR draft.  For the SAN, which of the following is the most 
> appropriate?
> 
>   * Applicant information SHALL include, but not be limited to, at least
>     one rfc822Name email address to be included in the Certificate’s
>     subjectAltName extension.
> 
> Or
> 
>   * Applicant information SHALL include, but not be limited to, at least
>     one rfc822Name or one otherName of type id-on-SmtpUTF8Mailbox to be
>     included in the Certificate’s subjectAltName extension.
> 
> In other words do we wish to define 1) a least one rfc822Name as 
> required with an option for additional rfc822Names or 
> id-on-SmtpUTF8Mailbox, or 2) at least one rfc822Name or 
> id-on-SmtpUTF8Mailbox (interchangeably)?
> 
> Feedback welcomed!
> 
> Many thanks, Stephen
> 
> 
> _______________________________________________
> Smcwg-public mailing list
> Smcwg-public at cabforum.org
> https://lists.cabforum.org/mailman/listinfo/smcwg-public
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4280 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.cabforum.org/pipermail/smcwg-public/attachments/20220216/cc6d28a0/attachment.p7s>