<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
font-size:10.0pt;
font-family:"Courier New";}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.fontstyle0
{mso-style-name:fontstyle0;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Consolas",serif;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=en-SE link=blue vlink=purple style='word-wrap:break-word;-webkit-nbsp-mode: space;line-break:after-white-space'><div class=WordSection1><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;mso-fareast-language:EN-US'>Well, that assumes that an S/MIME signature cannot be legally binding. But I’m not sure that’s valid for every country in the world.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;mso-fareast-language:EN-US'>Martijn<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;mso-fareast-language:EN-US'><o:p> </o:p></span></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal style='margin-bottom:12.0pt'><b><span style='font-size:12.0pt;color:black'>From: </span></b><span style='font-size:12.0pt;color:black'>Smcwg-public <smcwg-public-bounces@cabforum.org> on behalf of Pedro FUENTES via Smcwg-public <smcwg-public@cabforum.org><br><b>Date: </b>Wednesday, 26 October 2022 at 09:18<br><b>To: </b>Tim Hollebeek <tim.hollebeek@digicert.com><br><b>Cc: </b>SMIME Certificate Working Group <smcwg-public@cabforum.org><br><b>Subject: </b>Re: [Smcwg-public] [EXTERNAL]-Re: Ballot SMC01v3: Final Guideline for “S/MIME Baseline Requirements”<o:p></o:p></span></p></div><div style='border:solid black 1.0pt;padding:2.0pt 2.0pt 2.0pt 2.0pt'><p class=MsoNormal style='line-height:12.0pt;background:#FAFA03'><span style='color:black'>CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.<o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><div><p class=MsoNormal><span style='font-size:11.0pt'>These works in Europe are oriented to Qualified Certificates, and legally binding digital signatures. <o:p></o:p></span></p><div><p class=MsoNormal><span style='font-size:11.0pt'>We are talking here about S/MIME…<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt'>So, yes, this is apples and oranges...<o:p></o:p></span></p><div><p class=MsoNormal><span style='font-size:11.0pt'><br><br><o:p></o:p></span></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal><span style='font-size:11.0pt'>On 26 Oct 2022, at 09:13, Tim Hollebeek <<a href="mailto:tim.hollebeek@digicert.com">tim.hollebeek@digicert.com</a>> wrote:<o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><div><div><p class=MsoNormal><span style='font-size:11.0pt'>It’s really apples and oranges, but if people want parity, I’d point out that the TLS IV validation has not changed in something like seven years, and were not particularly state of the art at that time. There’s a lot of great work on identity vetting that has been done in the meantime, especially in Europe.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt'>If people want to work on updating TLS IV vetting to be more in line with recent standards, that would be a reasonable topic to discuss.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt'>-Tim<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt'> <o:p></o:p></span></p></div><div style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><div><p class=MsoNormal><b><span style='font-size:11.0pt'>From:</span></b><span class=apple-converted-space><span style='font-size:11.0pt'> </span></span><span style='font-size:11.0pt'>Smcwg-public <<a href="mailto:smcwg-public-bounces@cabforum.org">smcwg-public-bounces@cabforum.org</a>><span class=apple-converted-space> </span><b>On Behalf Of<span class=apple-converted-space> </span></b>Pedro FUENTES via Smcwg-public<br><b>Sent:</b><span class=apple-converted-space> </span>Tuesday, October 25, 2022 10:58 AM<br><b>To:</b><span class=apple-converted-space> </span>Adriano Santoni <<a href="mailto:adriano.santoni@staff.aruba.it">adriano.santoni@staff.aruba.it</a>>; SMIME Certificate Working Group <<a href="mailto:smcwg-public@cabforum.org">smcwg-public@cabforum.org</a>><br><b>Subject:</b><span class=apple-converted-space> </span>Re: [Smcwg-public] [EXTERNAL]-Re: Ballot SMC01v3: Final Guideline for “S/MIME Baseline Requirements”<o:p></o:p></span></p></div></div></div><div><p class=MsoNormal><span style='font-size:11.0pt'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt'>I share the exact same thoughts on the parallelism in identity validation requirements with for the TLS certificates.<o:p></o:p></span></p></div><div><div><p class=MsoNormal><span style='font-size:11.0pt'> <o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt'>But this discussion is futile once the voting has just started.<o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt'> <o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt'>BR/P<o:p></o:p></span></p></div><div><div><p class=MsoNormal><span style='font-size:11.0pt'><br><br><br><o:p></o:p></span></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><div><p class=MsoNormal><span style='font-size:11.0pt'>On 25 Oct 2022, at 16:54, Adriano Santoni via Smcwg-public <<a href="mailto:smcwg-public@cabforum.org">smcwg-public@cabforum.org</a>> wrote:<o:p></o:p></span></p></div></div><div><p class=MsoNormal><span style='font-size:11.0pt'> <o:p></o:p></span></p></div><div><div><p class=MsoNormal><span style='font-size:9.0pt'>Stephen,</span><span style='font-size:11.0pt'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:9.0pt'>I regret not having participated in the discussion on this issue at the time, and I apologize again for raising this issue only now.<span class=apple-converted-space> </span></span><span style='font-size:11.0pt'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:9.0pt'>However, I remain of the opinion that the "real time" requirement is an exaggeration for S/MIME certificates (while it is undoubtedly appropriate for eIDAS qualified signature certificates).<span class=apple-converted-space> </span></span><span style='font-size:11.0pt'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:9.0pt'>Neither Mozilla nor Microsoft require ETSI audits on S/MIME certificates to be based on an NCP type policy: both browser vendors accept the LCP policy, as can be seen from their respective root store program websites. If I am mistaken, please Ben and Karina correct me.</span><span style='font-size:11.0pt'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:9.0pt'>However, if the other CAs reading us here (and especially those that issue IV S/MIME certificates) believe that §<span class=fontstyle0>3.2.4.2</span><span class=apple-converted-space> </span>is fine AS IS, it is important to realize that it clashes with some (many?) of their current procedures. From the moment these BRs are enacted and referred to by at least one root store policy, those CA's procedures immediately become non-compliant. If everyone realizes this and is okay with it, then it's fine to me too; otherwise let's talk about it.</span><span style='font-size:11.0pt'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:Helvetica'>I want to point out that I am not questioning the value of "real time" from a security point of view, but I don't understand why an IV S/MIME cert should be more secure than an IV SSL cert (for which no "real time" is required for the scan of a photo id). Both are issued to natural persons and should be equally secure, at least. Indeed, an IV SSL cert should in my opinion be more secure than an IV S/MIME cert, given that its possible insecurity impacts on many more subjects.</span><span style='font-size:11.0pt'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:Helvetica'>I am saying this only as a matter of logic, not because it is "a priori" necessary that the SSL BR and the S/MIME BR are aligned.</span><span style='font-size:11.0pt'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:Helvetica'>On top of that, I think we all agree that the S/MIME BR should reflect current procedures, at least for the "legacy" generation; how about requiring "real time" for the "strict" generation?</span><span style='font-size:11.0pt'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:Helvetica'>Adriano</span><span style='font-size:11.0pt'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:Helvetica'> </span><span style='font-size:11.0pt'><o:p></o:p></span></p></div><div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:Helvetica'>Il 25/10/2022 15:38, Stephen Davidson ha scritto:</span><span style='font-size:11.0pt'><o:p></o:p></span></p></div></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt;font-variant-caps: normal;text-align:start;-webkit-text-stroke-width: 0px;word-spacing:0px'><div align=center><table class=MsoNormalTable border=1 cellpadding=0 width="30%" style='width:30.0%'><tr><td valign=top style='background:yellow;padding:1.0pt 1.0pt 1.0pt 1.0pt'><div><p class=MsoNormal><span style='font-size:11.0pt;color:red'>NOTICE:</span><span class=apple-converted-space><span style='font-size:11.0pt;color:black'> </span></span><span style='font-size:11.0pt;color:black'>Pay attention - external email - Sender is<span class=apple-converted-space> </span><a href="mailto:Stephen.Davidson@digicert.com"><span style='color:#0563C1'>Stephen.Davidson@digicert.com</span></a></span><span style='font-size:11.0pt'><o:p></o:p></span></p></div></td></tr></table></div><p class=MsoNormal align=center style='text-align:center'><span style='font-size:9.0pt;font-family:Helvetica'> </span><span style='font-size:11.0pt'><o:p></o:p></span></p><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:Helvetica'> </span><span style='font-size:11.0pt'><o:p></o:p></span></p></div><p class=MsoNormal style='margin-bottom:8.0pt;line-height:11.55pt'><span style='font-size:11.0pt'>Hello Adriano:<o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:8.0pt;line-height:11.55pt'><span style='font-size:11.0pt'>This text has been in the draft S/MIME BR for close to 10 months and has been reviewed at some length.<o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:8.0pt;line-height:11.55pt'><span style='font-size:11.0pt'>Certificate Consumers stated that information included in the Subject DN needs to be reliably validated, and that a link needs to be made between the Subject and the cert, whether the Subject is a legal entity or a real natural person.<o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:8.0pt;line-height:11.55pt'><span style='font-size:11.0pt'>The requirement in question was derived from ETSI TS 119 461, which defines baseline procedures aimed at delivering at the NCP (Normalized Certificate Policy) level.<o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:8.0pt;line-height:11.55pt'><span style='font-size:11.0pt'>The issue with some legacy practices is that separate images of the ID and a user could be harvested and presented without the Subject’s knowledge. By requiring their linked collection, the standard seeks to improve security in the remote vetting methods.<o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:8.0pt;line-height:11.55pt'><span style='font-size:11.0pt'>Best, Stephen<o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:8.0pt;line-height:11.55pt'><span style='font-size:11.0pt'> <o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:8.0pt;line-height:11.55pt'><span style='font-size:11.0pt'> <o:p></o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><div><div><p class=MsoNormal><b><span style='font-size:11.0pt'>From:</span></b><span class=apple-converted-space><span style='font-size:11.0pt'> </span></span><span style='font-size:11.0pt'>Smcwg-public<span class=apple-converted-space> </span><a href="mailto:smcwg-public-bounces@cabforum.org"><span style='color:#0563C1'><smcwg-public-bounces@cabforum.org></span></a><span class=apple-converted-space> </span><b>On Behalf Of</b><span class=apple-converted-space> </span>Adriano Santoni via Smcwg-public<br><b>Sent:</b><span class=apple-converted-space> </span>Monday, October 24, 2022 5:34 PM<br><b>To:</b><span class=apple-converted-space> </span><a href="mailto:smcwg-public@cabforum.org"><span style='color:#0563C1'>smcwg-public@cabforum.org</span></a><br><b>Subject:</b><span class=apple-converted-space> </span>Re: [Smcwg-public] [External Sender] Ballot SMC01v3: Final Guideline for “S/MIME Baseline Requirements”<o:p></o:p></span></p></div></div></div></div><p class=MsoNormal style='margin-bottom:8.0pt;line-height:11.55pt'><span style='font-size:11.0pt'> <o:p></o:p></span></p><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:Helvetica'>All,</span><span style='font-size:11.0pt'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:Helvetica'>I apologize for raising doubts at the very "last minute", but since the SMC BR are about to be put to the vote, I wanted to give them a complete re-reading and I noticed a passage that leaves me a little perplexed.</span><span style='font-size:11.0pt'><o:p></o:p></span></p></div><p class=MsoNormal style='margin-bottom:8.0pt;line-height:11.55pt'><span style='font-size:11.0pt'>Maybe this aspect was discussed at length, but then I missed that discussion - sorry about that (in case).<o:p></o:p></span></p><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:Helvetica'>Under "<span class=fontstyle0>3.2.4.2 Validation of individual identity</span>" we have the following sentence:</span><span style='font-size:11.0pt'><o:p></o:p></span></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal style='margin-bottom:8.0pt;line-height:11.55pt'><span class=fontstyle0><span style='font-size:11.0pt'>The CA or RA MAY use manual (in person) or remote procedures. A remote process SHALL ensure that the Applicant has the document in hand and presents the document</span></span><span class=apple-converted-space><span style='font-size:11.0pt'> </span></span><span class=fontstyle0><i><span style='font-size:11.0pt'>in real‐time</span></i></span><span class=apple-converted-space><span style='font-size:11.0pt'> </span></span><span class=fontstyle0><span style='font-size:11.0pt'>in front of a camera.</span></span><span style='font-size:11.0pt'><o:p></o:p></span></p></blockquote><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:Helvetica'>Where did we borrow "in real-time" from? Not from the TLS BR nor from EVGL, it seems.<span class=apple-converted-space> </span></span><span style='font-size:11.0pt'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:Helvetica'>What's the rationale for that? It seems too demanding, to me, for S/MIME certificates.</span><span style='font-size:11.0pt'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:Helvetica'>Several CAs that I am aware of are doing individual identity verification (for S/MIME certificates) based on a Photo ID and a selfie (showing both the Applicant and his/her Photo ID), and this latter is not required to be taken in "real time".</span><span style='font-size:11.0pt'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:Helvetica'>I am therefore a bit surprised that all the people here agree on this "in real time" which implies the non-compliance of current procedures and the need to move to more complex and more expensive procedures. Seems a bit excessive for S/MIME certificates.</span><span style='font-size:11.0pt'><o:p></o:p></span></p></div><p class=MsoNormal style='margin-bottom:8.0pt;line-height:11.55pt'><span style='font-size:11.0pt'>Adriano<span class=apple-converted-space> </span><o:p></o:p></span></p><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:Helvetica'> </span><span style='font-size:11.0pt'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:Helvetica'> </span><span style='font-size:11.0pt'><o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-bottom:8.0pt;line-height:11.55pt'><span style='font-size:11.0pt'>Il 14/10/2022 20:12, Stephen Davidson via Smcwg-public ha scritto:<o:p></o:p></span></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div align=center><table class=MsoNormalTable border=1 cellspacing=3 cellpadding=0 width="30%" style='width:30.0%'><tr><td valign=top style='background:yellow;padding:1.0pt 1.0pt 1.0pt 1.0pt'><div><div><p class=MsoNormal><span style='font-size:11.0pt;color:red'>NOTICE:</span><span class=apple-converted-space><span style='font-size:11.0pt;color:black'> </span></span><span style='font-size:11.0pt;color:black'>Pay attention - external email - Sender is<span class=apple-converted-space> </span><a href="mailto:01000183d7b27b10-4ccf8875-64fd-49e8-817e-0df9fe3a5117-000000@amazonses.com"><span style='color:#0563C1'>01000183d7b27b10-4ccf8875-64fd-49e8-817e-0df9fe3a5117-000000@amazonses.com</span></a></span><span style='font-size:11.0pt'><o:p></o:p></span></p></div></div></td></tr></table></div><p class=MsoNormal align=center style='text-align:center'><span style='font-size:11.0pt'> <o:p></o:p></span></p><div><div><p class=MsoNormal><span style='font-size:11.0pt'> <o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><b><span style='font-size:11.0pt'>Ballot SMC01v3: Final Guideline for “S/MIME Baseline Requirements”</span></b><span style='font-size:11.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><b><span style='font-size:11.0pt'> </span></b><span style='font-size:11.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><i><span style='font-size:11.0pt'>Note: the voting period for this ballot will commence following the SMCWG session at the upcoming CA/B Forum face-to-face Meeting 57.</span></i><span style='font-size:11.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><b><span style='font-size:11.0pt'> </span></b><span style='font-size:11.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><b><span style='font-size:11.0pt'>Purpose of Ballot:</span></b><span style='font-size:11.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt'> <o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt'>The S/MIME Certificate Working Group was chartered to discuss, adopt, and maintain policies, frameworks, and standards for the issuance and management of Publicly-Trusted S/MIME Certificates. This ballot adopts a new “S/MIME Baseline Requirements” that includes requirements for verification of control over email addresses, identity validation for natural persons and legal entities, key management and certificate lifecycle, certificate profiles for S/MIME Certificates and Issuing CA Certificates, as well as CA operational and audit practices.<o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt'> <o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt'>An S/MIME Certificate for the purposes of this document can be identified by the existence of an Extended Key Usage (EKU) for id-kp-emailProtection (OID: 1.3.6.1.5.5.7.3.4) and the inclusion of a rfc822Name or an otherName of type id-on-SmtpUTF8Mailbox in the subjectAltName extension in the Certificate.<o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt'> <o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt'>The following motion has been proposed by Stephen Davidson of DigiCert and endorsed by Martijn Katerbarg of Sectigo and Ben Wilson of Mozilla.<o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt'> <o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt'>In accordance with the By-Laws, the discussion period has been extended with the distribution of this new version of the ballot, incorporating content that arose during the discussion period including regarding the use of suspension and updating ETSI references in section 8.2.<o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt'> <o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><b><span style='font-size:11.0pt'>Charter Voting References</span></b><span style='font-size:11.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt'> <o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt'>Section 5.1 (“Voting Structure”) of the SMCWG Charter says:<o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt'> <o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt'>In order for a ballot to be adopted by the SMCWG, two-thirds or more of the votes cast by the Certificate Issuers must be in favor of the ballot and more than 50% of the votes cast by the Certificate Consumers must be in favor of the ballot. At least one member of each class must vote in favor of a ballot for it to be adopted. Quorum is the average number of Member organizations (cumulative, regardless of Class) that have participated in the previous three (3) SMCWG Meetings or Teleconferences (not counting subcommittee meetings thereof).<o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt'> <o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><b><span style='font-size:11.0pt'>— MOTION BEGINS —</span></b><span style='font-size:11.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt'> <o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt'>This ballot adopts the “Baseline Requirements for the Issuance and Management of Publicly-Trusted S/MIME Certificates” (“S/MIME Baseline Requirements”) as Version 1.0.0.<o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt'> <o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt'>The proposed S/MIME Baseline Requirements may be found at<span class=apple-converted-space> </span><a href="https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__github.com_cabforum_smime_pull_178_files%26d%3DDwMGaQ%26c%3DeuGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM%26r%3DeAcAJg7itXZRmAlXshymUW0TZ5HnBHQtF21zSfT5h5s%26m%3DKBuQclN2SfCC3W6zMNTTIglSP40byG_PyLDtfvXMTEI%26s%3DD4Ei6uOHfylvVIZob5ReF9tbDCiD5Q2wPfcBpxXpld8%26e%3D&data=05%7C01%7Cmartijn.katerbarg%40sectigo.com%7Ca69956c013db49e9614d08dab7224152%7C0e9c48946caa465d96604b6968b49fb7%7C0%7C0%7C638023655019197386%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vQnW6VPqgO%2FS2TiKcrt9aZBQ12yaBZOsE8Spmnsv9VU%3D&reserved=0"><span style='color:#0563C1'>https://github.com/cabforum/smime/pull/178/files</span></a><span class=apple-converted-space> </span>or the attached document. A redline of changes since the SMC01 Ballot discussion started may be found at<span class=apple-converted-space> </span><a href="https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__github.com_cabforum_smime_compare_28c0b904fe54f1c5f6c71d18c4786a3e02c76f52...b1ff7867dc85392e4c57b1993ed571e61e34dee2%26d%3DDwMGaQ%26c%3DeuGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM%26r%3DeAcAJg7itXZRmAlXshymUW0TZ5HnBHQtF21zSfT5h5s%26m%3DKBuQclN2SfCC3W6zMNTTIglSP40byG_PyLDtfvXMTEI%26s%3D8zE9nYGBsHvMQVu-aEBAmkfCG0cOMKbqXm-t7Iu7j34%26e%3D&data=05%7C01%7Cmartijn.katerbarg%40sectigo.com%7Ca69956c013db49e9614d08dab7224152%7C0e9c48946caa465d96604b6968b49fb7%7C0%7C0%7C638023655019353143%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2FrnMAmwUIXwwxDHzF11KAopo7ebuHAmoThHmFeG62Zo%3D&reserved=0"><span style='color:#0563C1'>https://github.com/cabforum/smime/compare/28c0b904fe54f1c5f6c71d18c4786a3e02c76f52...b1ff7867dc85392e4c57b1993ed571e61e34dee2</span></a><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt'> <o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt'>The SMCWG Chair or Vice-Chair is permitted to update the Relevant Dates and Version Number of the S/MIME Baseline Requirements to reflect final dates.<o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt'> <o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><b><span style='font-size:11.0pt'>— MOTION ENDS —</span></b><span style='font-size:11.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt'> <o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt'>This ballot proposes a Final Guideline. The procedure for approval of this ballot is as follows:<o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt'> <o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt'>Discussion (7+ days)<o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt'>Start Time: 14 October 2022 14:00 ET (US Eastern)<o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt'>End Time: not before 21 October 2022 14:00 ET (US Eastern)<o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt'> <o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt'>Vote for approval (7 days)<o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt'>Start Time: To be confirmed<o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt'>End Time: To be confirmed<o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt'> <o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt'>IPR Review (60 days)<o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt'> <o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt'> <o:p></o:p></span></p></div></div><p class=MsoNormal style='margin-bottom:8.0pt;line-height:11.55pt'><span style='font-size:11.0pt'> <o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:8.0pt;line-height:11.55pt'><span style='font-size:11.0pt'> <o:p></o:p></span></p><div><div><p class=MsoNormal><span style='font-size:11.0pt'><br><br><br><br><o:p></o:p></span></p></div></div><pre>_______________________________________________<o:p></o:p></pre><pre>Smcwg-public mailing list<o:p></o:p></pre><pre><a href="mailto:Smcwg-public@cabforum.org"><span style='color:#0563C1'>Smcwg-public@cabforum.org</span></a><o:p></o:p></pre><pre><a href="https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__lists.cabforum.org_mailman_listinfo_smcwg-2Dpublic%26d%3DDwMGaQ%26c%3DeuGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM%26r%3DeAcAJg7itXZRmAlXshymUW0TZ5HnBHQtF21zSfT5h5s%26m%3DKBuQclN2SfCC3W6zMNTTIglSP40byG_PyLDtfvXMTEI%26s%3D50Sc78MatgGNY_CDsR9dWLCtAtURsPptE5R-uICDIiA%26e%3D&data=05%7C01%7Cmartijn.katerbarg%40sectigo.com%7Ca69956c013db49e9614d08dab7224152%7C0e9c48946caa465d96604b6968b49fb7%7C0%7C0%7C638023655019353143%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Av6ImTr0CsoCWkUjn%2Fs05Cum%2FQXnB%2B31JFSCVd6krRc%3D&reserved=0"><span style='color:#0563C1'>https://lists.cabforum.org/mailman/listinfo/smcwg-public</span></a><o:p></o:p></pre></blockquote></blockquote><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:Helvetica'>_______________________________________________<br>Smcwg-public mailing list<br></span><span style='font-size:11.0pt'><a href="mailto:Smcwg-public@cabforum.org"><span style='font-size:9.0pt;font-family:Helvetica;color:#0563C1'>Smcwg-public@cabforum.org</span></a></span><span style='font-size:9.0pt;font-family:Helvetica'><br></span><span style='font-size:11.0pt'><a href="https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__lists.cabforum.org_mailman_listinfo_smcwg-2Dpublic%26d%3DDwICAg%26c%3DeuGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM%26r%3D-bX5hBm1IdRDykQ-dBR8tsFRCM4v1VXUyG7RZa2WqPY%26m%3D18G_plWPAeJu5QRlrkP0W1yv8Gr8jI4iylgOxeXnCo8%26s%3DSWfQR2dc-tyhruDnioj37UW1IeiZOGDXW2S9EYiHy4g%26e%3D&data=05%7C01%7Cmartijn.katerbarg%40sectigo.com%7Ca69956c013db49e9614d08dab7224152%7C0e9c48946caa465d96604b6968b49fb7%7C0%7C0%7C638023655019353143%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=A66Ir%2F2TgWzKBx6maXF4DTaKkVx%2F2RjLPCDrEF6KbBM%3D&reserved=0"><span style='font-size:9.0pt;font-family:Helvetica;color:#0563C1'>https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.cabforum.org_mailman_listinfo_smcwg-2Dpublic&d=DwICAg&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=-bX5hBm1IdRDykQ-dBR8tsFRCM4v1VXUyG7RZa2WqPY&m=18G_plWPAeJu5QRlrkP0W1yv8Gr8jI4iylgOxeXnCo8&s=SWfQR2dc-tyhruDnioj37UW1IeiZOGDXW2S9EYiHy4g&e=</span></a><o:p></o:p></span></p></div></div></blockquote></div><div><p class=MsoNormal><span style='font-size:11.0pt'> <o:p></o:p></span></p></div><div><div><div><div><div><div><div><div><div><div><div><div><p class=MsoNormal><b><span style='font-size:8.5pt;color:#F62400'><br>WISeKey SA</span></b><span style='font-size:11.0pt'><o:p></o:p></span></p></div><div><div><p class=MsoNormal><b><span style='font-size:8.5pt'>Pedro Fuentes<br></span></b><span style='font-size:8.5pt'>CSO - Trust Services Manager</span><span style='font-size:9.0pt'><br></span><span style='font-size:7.5pt'>Office: + 41 (0) 22 594 30 00<br>Mobile: + 41 (0) </span>791 274 790<span style='font-size:11.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:7.5pt'>Address: Avenue Louis-Casaï 58 | </span>1216 Cointrin | Switzerland<span style='font-size:11.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><b><span style='font-size:9.0pt'>Stay connected with <a href="https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.wisekey.com%2F&data=05%7C01%7Cmartijn.katerbarg%40sectigo.com%7Ca69956c013db49e9614d08dab7224152%7C0e9c48946caa465d96604b6968b49fb7%7C0%7C0%7C638023655019353143%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ByXm7fHajXXhFBLfFQKQUX8KLDVp5hrIjv%2BPdiqFOwg%3D&reserved=0"><span style='color:#F62400'>WISeKey</span></a><br></span></b><span style='font-size:7.5pt;color:darkgray'><br><br><br></span><span style='font-size:11.0pt'><o:p></o:p></span></p></div></div><div><div><div><p class=MsoNormal><b><span style='font-size:7.5pt;color:#78A600'>THIS IS A TRUSTED MAIL</span></b><span style='font-size:7.5pt;color:#78A600'>: This message is digitally signed with a WISeKey identity. If you get a mail from WISeKey please check the signature to avoid security risks</span><span style='font-size:11.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:7.0pt;color:darkgray'><br><br><br></span><span style='font-size:11.0pt'><o:p></o:p></span></p></div></div><div><div><div><p class=MsoNormal><b><span style='font-size:7.0pt;color:darkgray'>CONFIDENTIALITY: </span></b><span style='font-size:7.0pt;color:darkgray'>This email and any files transmitted with it can be confidential and it’s intended solely for the use of the individual or entity to which they are addressed. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. If you have received this email in error please notify the sender</span><span style='font-size:11.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:9.0pt'> </span><span style='font-size:11.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><b><span style='font-size:7.0pt;color:darkgray'>DISCLAIMER: </span></b><span style='font-size:7.0pt;color:darkgray'>WISeKey does not warrant the accuracy or completeness of this message and does not accept any liability for any errors or omissions herein as this message has been transmitted over a public network. Internet communications cannot be guaranteed to be secure or error-free as information may be intercepted, corrupted, or contain viruses. Attachments to this e-mail are checked for viruses; however, we do not accept any liability for any damage sustained by viruses and therefore you are kindly requested to check for viruses upon receipt.</span><span style='font-size:11.0pt'><o:p></o:p></span></p></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></blockquote></div><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><div><div><div><div><div><div><div><div><div><div><div><p class=MsoNormal><b><span style='font-size:8.5pt;color:#F62400'><br>WISeKey SA</span></b><span style='font-size:11.0pt'><o:p></o:p></span></p><div><p class=MsoNormal><b><span style='font-size:8.5pt;color:black'>Pedro Fuentes<br></span></b><span style='font-size:8.5pt;color:black'>CSO - Trust Services Manager</span><span style='font-size:9.0pt;color:black'><br></span><span style='font-size:7.5pt;color:black'>Office: + 41 (0) 22 594 30 00<br>Mobile: + 41 (0) </span><span style='color:black'>791 274 790</span><span style='font-size:11.0pt;color:black'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:7.5pt;color:black'>Address: </span><span style='font-size:7.5pt'>Avenue Louis-Casaï 58 | </span>1216 Cointrin | Switzerland<span style='font-size:11.0pt'><o:p></o:p></span></p></div><div><p class=MsoNormal><b><span style='font-size:9.0pt;color:black'>Stay connected with <a href="https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.wisekey.com%2F&data=05%7C01%7Cmartijn.katerbarg%40sectigo.com%7Ca69956c013db49e9614d08dab7224152%7C0e9c48946caa465d96604b6968b49fb7%7C0%7C0%7C638023655019353143%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ByXm7fHajXXhFBLfFQKQUX8KLDVp5hrIjv%2BPdiqFOwg%3D&reserved=0"><span style='color:#F62400'>WISeKey</span></a><br></span></b><span style='font-size:7.5pt;color:darkgray'><br><br></span><span style='font-size:11.0pt'><o:p></o:p></span></p></div><div><div><p class=MsoNormal><b><span style='font-size:7.5pt;color:#78A600'>THIS IS A TRUSTED MAIL</span></b><span style='font-size:7.5pt;color:#78A600'>: This message is digitally signed with a WISeKey identity. If you get a mail from WISeKey please check the signature to avoid security risks</span><span style='font-size:9.0pt;color:black'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:7.0pt;color:darkgray'><br><br></span><span style='font-size:9.0pt;color:black'><o:p></o:p></span></p></div><div><div><p class=MsoNormal><b><span style='font-size:7.0pt;color:darkgray'>CONFIDENTIALITY: </span></b><span style='font-size:7.0pt;color:darkgray'>This email and any files transmitted with it can be confidential and it’s intended solely for the use of the individual or entity to which they are addressed. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. If you have received this email in error please notify the sender</span><span style='font-size:9.0pt;color:black'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><b><span style='font-size:7.0pt;color:darkgray'>DISCLAIMER: </span></b><span style='font-size:7.0pt;color:darkgray'>WISeKey does not warrant the accuracy or completeness of this message and does not accept any liability for any errors or omissions herein as this message has been transmitted over a public network. Internet communications cannot be guaranteed to be secure or error-free as information may be intercepted, corrupted, or contain viruses. Attachments to this e-mail are checked for viruses; however, we do not accept any liability for any damage sustained by viruses and therefore you are kindly requested to check for viruses upon receipt.</span><span style='font-size:9.0pt;color:black'><o:p></o:p></span></p></div></div></div></div></div></div></div></div></div></div></div></div></div></div><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p></div></div></div></body></html>