<html xmlns:v="urn:schemas-microsoft-com:vml" 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:"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-top:0in;
margin-right:0in;
margin-bottom:8.0pt;
margin-left:0in;
line-height:105%;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
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:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link="#0563C1" vlink="#954F72" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;line-height:105%'>Thank you Matthias.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;line-height:105%'>There is also a reference in Section 8.4 bullet 3 which I have updated as<o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:0in;line-height:14.25pt;background:whitesmoke'><span style='font-size:10.5pt;font-family:Consolas;color:#777777'>3.</span><span style='font-size:10.5pt;font-family:Consolas;color:#4B69C6'> "ETSI EN 319 411-1 v1.3.1 or newer", which includes normative references to ETSI EN 319 401 <b>or ETSI EN 319 403-1</b> (the latest version of referenced ETSI documents should be applied); or</span><span style='font-size:10.5pt;font-family:Consolas;color:#333333'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;line-height:105%'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;line-height:105%'>The tooling that creates the PDF is being updated to better handle tables so those table display issues should be resolved soon.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;line-height:105%'>Regards, Stephen<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;line-height:105%'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;line-height:105%'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='margin-bottom:0in;line-height:normal'><b><span style='font-size:11.0pt'>From:</span></b><span style='font-size:11.0pt'> Wiedenhorst, Matthias <M.Wiedenhorst@tuvit.de> <br><b>Sent:</b> Thursday, September 15, 2022 5:39 AM<br><b>To:</b> Stephen Davidson <Stephen.Davidson@digicert.com>; smcwg-public@cabforum.org<br><b>Subject:</b> AW: Ballot SMC01: Final Guideline for “S/MIME Baseline Requirements”<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=EN-GB style='font-family:"Arial",serif;color:#1F497D'>Dear Stephen, Dear all,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-family:"Arial",serif;color:#1F497D'>I just realized one issue with regard to auditing and I am very sorry that I didn’t realize it earlier in one of the many times I read through the draft during its creation.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-family:"Arial",serif;color:#1F497D'>In section 8.2, number 4 it is written: "(For audits conducted in accordance with any one of the ETSI standards)accredited in accordance with ISO 17065 applying the requirements specified in ETSI EN 319 403;" However, since some time the ETSI EN 319 403-1 has been released as successor of 319 403. At the time being, both versions are valid and can be used for CAB accreditation. I assume most CAB’s are on their way to migrate accreditation to the newer 403-1, some have already finished. Hence, section 8.2 number 4 should be amended as follows:<br>"(For audits conducted in accordance with any one of the ETSI standards)accredited in accordance with ISO 17065 applying the requirements specified in ETSI EN 319 403<i> or ETSI EN 319 403-1</i>;"<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-family:"Arial",serif;color:#1F497D'>In addition, a reference to the new version should be added to section 1.6.3:<br><i>“ETSI EN 319 403-1, Electronic Signatures and Infrastructures (ESI); Trust Service Provider Conformity Assessment; Part 1:</i></span><i><span lang=EN-GB style='font-family:"Cambria Math",serif;color:#1F497D'>‐</span></i><i><span lang=EN-GB style='font-family:"Arial",serif;color:#1F497D'> Requirements for conformity assessment bodies assessing Trust Service Providers”</span></i><span lang=EN-GB style='font-family:"Arial",serif;color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-family:"Arial",serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-family:"Arial",serif;color:#1F497D'>I also noticed one other thing:<br>In the provided PDF there are some sections with tables, where text of the first two columns partly overlay each other. I found examples in sections 7.1.2.3 e), 7.1.4.2.5 and 7.1.4.2.6. I realize that this is only an issue of presentation and not of content, but nevertheless, maybe there is a way to fix it.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-family:"Arial",serif;color:#1F497D'>Best regards<br>Matthias<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal style='margin-bottom:0in;line-height:normal'><b><span lang=DE style='font-size:11.0pt'>Von:</span></b><span lang=DE style='font-size:11.0pt'> Smcwg-public <</span><a href="mailto:smcwg-public-bounces@cabforum.org"><span lang=DE style='font-size:11.0pt'>smcwg-public-bounces@cabforum.org</span></a><span lang=DE style='font-size:11.0pt'>> <b>Im Auftrag von </b>Stephen Davidson via Smcwg-public<br><b>Gesendet:</b> Donnerstag, 8. September 2022 09:03<br><b>An:</b> </span><a href="mailto:smcwg-public@cabforum.org"><span lang=DE style='font-size:11.0pt'>smcwg-public@cabforum.org</span></a><span lang=DE style='font-size:11.0pt'><br><b>Betreff:</b> [Smcwg-public] Ballot SMC01: Final Guideline for “S/MIME Baseline Requirements”<o:p></o:p></span></p><p class=MsoNormal><span lang=DE><o:p> </o:p></span></p><p style='margin:0in;background:white'><strong><span style='font-size:10.0pt;font-family:"Arial",serif;color:#333333;border:none windowtext 1.0pt;padding:0in'>Ballot SMC01: Final Guideline for “S/MIME Baseline Requirements” </span></strong><strong><span style='font-family:"Arial",serif;color:#333333;border:none windowtext 1.0pt;padding:0in'><o:p></o:p></span></strong></p><p style='margin:0in;background:white'><strong><span style='font-size:10.0pt;font-family:"Arial",serif;color:#333333;border:none windowtext 1.0pt;padding:0in'><o:p> </o:p></span></strong></p><p style='margin:0in;background:white'><strong><span style='font-size:10.0pt;font-family:"Arial",serif;color:#333333;border:none windowtext 1.0pt;padding:0in'>Purpose of Ballot:</span></strong><span lang=DE><o:p></o:p></span></p><p style='margin:0in;background:white'><span style='font-size:10.0pt;font-family:"Arial",serif;color:#333333'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Arial",serif;color:#333333'>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><p style='margin:0in;background:white'><span style='font-size:10.0pt;font-family:"Arial",serif;color:#333333'><o:p> </o:p></span></p><p style='margin:0in;background:white'><span style='font-size:10.0pt;font-family:"Arial",serif;color:#333333'>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><p style='margin:0in;background:white'><span style='font-size:10.0pt;font-family:"Arial",serif;color:#333333'><o:p> </o:p></span></p><p style='margin:0in;background:white'><span style='font-size:10.0pt;font-family:"Arial",serif;color:#333333;background:white'>The following motion has been proposed by Stephen Davidson of DigiCert and endorsed by Martijn Katerbarg of Sectigo and Ben Wilson of Mozilla.</span><span style='font-size:10.0pt;font-family:"Arial",serif;color:#333333'><o:p></o:p></span></p><p style='margin:0in;background:white'><span style='font-size:10.0pt;font-family:"Arial",serif;color:#333333'><o:p> </o:p></span></p><p style='margin:0in;background:white'><strong><span style='font-size:10.0pt;font-family:"Arial",serif;color:#333333;border:none windowtext 1.0pt;padding:0in'>Charter Voting References</span></strong><span style='font-size:10.0pt;font-family:"Arial",serif;color:#333333'><o:p></o:p></span></p><p style='margin:0in;background:white'><span style='font-size:10.0pt;font-family:"Arial",serif;color:#333333'><o:p> </o:p></span></p><p style='margin:0in;background:white'><span style='color:black'><a href="https://github.com/cabforum/servercert/blob/e6ad111f4477010cbff409cd939c5ac1c7c85ccc/docs/SMCWG-charter.md#51-voting-structure"><span style='font-size:10.0pt;font-family:"Arial",serif'>Section 5.1 (“Voting Structure”)</span></a></span><span style='font-size:10.0pt;font-family:"Arial",serif;color:#333333'> of the SMCWG Charter says:<o:p></o:p></span></p><p style='margin:0in;background:white'><span style='font-size:10.0pt;font-family:"Arial",serif;color:#333333'><o:p> </o:p></span></p><p style='margin:0in;background:white'><span style='font-size:10.0pt;font-family:"Arial",serif;color:#333333'>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><p style='margin:0in;background:white'><span style='font-size:10.0pt;font-family:"Arial",serif;color:#333333'><o:p> </o:p></span></p><p style='margin:0in;background:white'><strong><span style='font-size:10.0pt;font-family:"Arial",serif;color:#333333;border:none windowtext 1.0pt;padding:0in'>— MOTION BEGINS —</span></strong><b><span style='font-size:10.0pt;font-family:"Arial",serif;color:#333333;border:none windowtext 1.0pt;padding:0in'><br></span></b><span style='font-size:10.0pt;font-family:"Arial",serif;color:#333333'><br>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><p style='margin:0in;background:white'><span style='font-size:10.0pt;font-family:"Arial",serif;color:#333333'><o:p> </o:p></span></p><p style='margin:0in;background:white'><span style='font-size:10.0pt;font-family:"Arial",serif;color:#333333'>The proposed S/MIME Baseline Requirements may be found at </span><span style='color:black'><a href="https://github.com/cabforum/smime/compare/7b3ab3c55dd92052a8dc0d4f85a2ac26269c222e...28c0b904fe54f1c5f6c71d18c4786a3e02c76f52"><span style='font-size:10.0pt;font-family:"Arial",serif'>https://github.com/cabforum/smime/compare/7b3ab3c55dd92052a8dc0d4f85a2ac26269c222e...28c0b904fe54f1c5f6c71d18c4786a3e02c76f52</span></a></span><span style='font-size:10.0pt;font-family:"Arial",serif;color:#333333'> or the attached document.<o:p></o:p></span></p><p style='margin:0in;background:white'><span style='font-size:10.0pt;font-family:"Arial",serif;color:#333333'><o:p> </o:p></span></p><p style='margin:0in;background:white'><span style='font-size:10.0pt;font-family:"Arial",serif;color:#333333'>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><p style='margin:0in;background:white'><span style='font-size:10.0pt;font-family:"Arial",serif;color:#333333'><o:p> </o:p></span></p><p style='margin:0in;background:white'><strong><span style='font-size:10.0pt;font-family:"Arial",serif;color:#333333;border:none windowtext 1.0pt;padding:0in'>— MOTION ENDS —</span></strong><b><span style='font-size:10.0pt;font-family:"Arial",serif;color:#333333;border:none windowtext 1.0pt;padding:0in'><br></span></b><span style='font-size:10.0pt;font-family:"Arial",serif;color:#333333'><br>This ballot proposes a Final Guideline. The procedure for approval of this ballot is as follows:<o:p></o:p></span></p><p style='margin:0in;background:white'><span style='font-size:10.0pt;font-family:"Arial",serif;color:#333333'><o:p> </o:p></span></p><p style='margin:0in;background:white'><span style='font-size:10.0pt;font-family:"Arial",serif;color:#333333'>Discussion (7+ days)</span><span style='color:black'><br></span><span style='font-size:10.0pt;font-family:"Arial",serif;color:#333333'>Start Time: 8 September 2022 17:00 UTC</span><span style='color:black'><br></span><span style='font-size:10.0pt;font-family:"Arial",serif;color:#333333'>End Time: 15 September 2022 17:00 UTC<o:p></o:p></span></p><p style='margin:0in;background:white'><span style='font-size:10.0pt;font-family:"Arial",serif;color:#333333'><o:p> </o:p></span></p><p style='margin:0in;background:white'><span style='font-size:10.0pt;font-family:"Arial",serif;color:#333333'>Vote for approval (7 days)</span><span style='color:black'><br></span><span style='font-size:10.0pt;font-family:"Arial",serif;color:#333333'>Start Time: 15 September 2022 17:00 UTC</span><span style='color:black'><br></span><span style='font-size:10.0pt;font-family:"Arial",serif;color:#333333'>End Time: 22 September 2022 17:00 UTC<o:p></o:p></span></p><p style='margin:0in;background:white'><span style='font-size:10.0pt;font-family:"Arial",serif;color:#333333'><o:p> </o:p></span></p><p style='margin:0in;background:white'><span style='font-size:10.0pt;font-family:"Arial",serif;color:#333333'>IPR Review (60 days)<o:p></o:p></span></p><pre><span lang=DE style='font-size:7.5pt;font-family:"Arial",serif'><o:p> </o:p></span></pre><pre><strong><span lang=DE style='font-size:7.5pt;font-family:"Arial",serif'>______________________________________________________________________________________________________________________</span></strong><span lang=DE style='font-size:7.5pt;font-family:"Arial",serif'><o:p></o:p></span></pre><pre><strong><span lang=DE style='font-size:7.5pt;font-family:"Arial",serif'>Sitz der Gesellschaft/Headquarter:</span></strong><span lang=DE style='font-size:7.5pt;font-family:"Arial",serif'> TÜV Informationstechnik GmbH * Am TÜV 1 * 45307 Essen, Germany<o:p></o:p></span></pre><pre><strong><span lang=DE style='font-size:7.5pt;font-family:"Arial",serif'>Registergericht/Register Court:</span></strong><span lang=DE style='font-size:7.5pt;font-family:"Arial",serif'> Amtsgericht/Local Court Essen * HRB 11687 * USt.-IdNr./VAT No.: DE 176132277 * Steuer-Nr./Tax No.: 111/57062251<o:p></o:p></span></pre><pre><strong><span lang=DE style='font-size:7.5pt;font-family:"Arial",serif'>Geschäftsführung/Management Board:</span></strong><span lang=DE style='font-size:7.5pt;font-family:"Arial",serif'> Dirk Kretzschmar <o:p></o:p></span></pre><p class=MsoNormal style='margin-bottom:0in;line-height:normal'><span lang=DE style='font-size:11.0pt'><o:p> </o:p></span></p><pre><b><span lang=DE style='font-size:12.0pt;font-family:"Arial",serif;color:black'>TÜV NORD GROUP</span></b><span lang=DE><o:p></o:p></span></pre><pre><span lang=DE style='font-size:7.5pt;font-family:"Arial",serif;color:black'>Expertise for your Success<o:p></o:p></span></pre><pre><b><span lang=DE style='font-size:7.5pt;font-family:"Arial",serif;color:black'>Please visit our website: </span></b><a href="http://www.tuv-nord.com"><b><span lang=DE style='font-size:7.5pt;font-family:"Arial",serif'>www.tuv-nord.com</span></b></a><b><span lang=DE style='font-size:7.5pt;font-family:"Arial",serif;color:black'><o:p></o:p></span></b></pre><pre><b><span lang=DE style='font-size:7.5pt;font-family:"Arial",serif;color:black'>Besuchen Sie unseren Internetauftritt: </span></b><a href="http://www.tuev-nord.de"><b><span lang=DE style='font-size:7.5pt;font-family:"Arial",serif'>www.tuev-nord.de</span></b></a><span lang=DE><o:p></o:p></span></pre></div></body></html>