<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:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Wingdings;
panose-1:5 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;
margin-bottom:.0001pt;
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.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle24
{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><!--[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-DE" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span lang="DE" style="font-size:11.0pt;mso-fareast-language:EN-US">Hi Martjin,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="DE" 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">under normal circumstances I’d share your opinion about the long duration for the last valid certificate based on the legacy profile. But in this case, I’d say we need
to take into consideration, that latest from the effective date on, downstream applications will need to be able to handle S/MIME certificates that follow one of the stronger profiles. I believe this will be a very challenging target to achieve, especially
since S/MIME certificate handling often is part of the business logic, opposite to TLS certificates that are handled typically very down in the software stack. Also nobody is forcing the mail client suppliers to accept certificates based on the legacy profile
until the sunset date. They could phase them out earlier. But I’d like to avoid that CAs are becoming incompliant, because they need to support legacy applications that are not easy to adapt.<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">/Rufus<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"><o:p> </o:p></span></p>
<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">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt">From:</span></b><span lang="EN-US" style="font-size:11.0pt"> Martijn Katerbarg <martijn.katerbarg@sectigo.com>
<br>
<b>Sent:</b> Tuesday, 20 September 2022 19:55<br>
<b>To:</b> Buschart, Rufus (IT IPS SIP ET) <rufus.buschart@siemens.com>; SMIME Certificate Working Group <smcwg-public@cabforum.org>; Clint Wilson <clintw@apple.com>; Stephen Davidson <Stephen.Davidson@digicert.com><br>
<b>Subject:</b> Re: [Smcwg-public] 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-US" style="font-size:11.0pt;mso-fareast-language:EN-US">If you take the end of 2026 as deprecation date for issuing Legacy profile certificates, that would mean the last one of those would expire somewhere in Q1 2030. That’s
more than 7 years from now. <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">Compare that to the fact that at least one Trusted Root Store operator previously set a deadline of April 2022 (a decision that was later reversed).<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">I think the proposal of around October 2024 is a fair target for this deprecation. That’s just about 2 years from now, and, estimating that the SMIME BRs should be in
effect somewhere in Q3 of 2023, leaves more than a year from the effective date.
<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">With 8 months in-between the SMIME BRs adoption date and it’s effective date, I’d say it makes sense to incorporate this date through a separate ballot instead of adding
this to the first version. That has the added effect of it having more potential to become a separate news item, and “spread the word”.<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">Regards,<br>
<br>
Martijn<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>
<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 <<a href="mailto:smcwg-public-bounces@cabforum.org">smcwg-public-bounces@cabforum.org</a>> on behalf of Buschart, Rufus via Smcwg-public <<a href="mailto:smcwg-public@cabforum.org">smcwg-public@cabforum.org</a>><br>
<b>Date: </b>Monday, 19 September 2022 at 15:20<br>
<b>To: </b>Clint Wilson <<a href="mailto:clintw@apple.com">clintw@apple.com</a>>, SMIME Certificate Working Group <<a href="mailto:smcwg-public@cabforum.org">smcwg-public@cabforum.org</a>>, Stephen Davidson <<a href="mailto:Stephen.Davidson@digicert.com">Stephen.Davidson@digicert.com</a>><br>
<b>Subject: </b>Re: [Smcwg-public] Ballot SMC01: 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 lang="EN-US" style="font-size:11.0pt;mso-fareast-language:EN-US">I think this proposed date of Oct. 2024 is far too early, as there are systems down stream which are consuming the certificates and might need to be adjusted. It will
take time to inform the customers of the CAs, the customers need to understand and need to identify the affected systems, need to get in touch with the vendors, identify necessary changes, allocate money, get development resources, implement the changes, test
them and roll them into production </span><span lang="EN-US" style="font-size:11.0pt;font-family:Wingdings;mso-fareast-language:EN-US">à</span><span lang="EN-US" style="font-size:11.0pt;mso-fareast-language:EN-US"> I’d say we should aim for something like
as early as end of 2026 as sunset date for legacy profiles.</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;mso-fareast-language:EN-US"> </span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;mso-fareast-language:EN-US">/Rufus</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;mso-fareast-language:EN-US"> </span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<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">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt">From:</span></b><span lang="EN-US" style="font-size:11.0pt"> Smcwg-public <<a href="mailto:smcwg-public-bounces@cabforum.org">smcwg-public-bounces@cabforum.org</a>>
<b>On Behalf Of </b>Clint Wilson via Smcwg-public<br>
<b>Sent:</b> Thursday, 15 September 2022 18:28<br>
<b>To:</b> Stephen Davidson <<a href="mailto:Stephen.Davidson@digicert.com">Stephen.Davidson@digicert.com</a>>; SMIME Certificate Working Group <<a href="mailto:smcwg-public@cabforum.org">smcwg-public@cabforum.org</a>><br>
<b>Subject:</b> Re: [Smcwg-public] Ballot SMC01: Final Guideline for “S/MIME Baseline Requirements”</span><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>
<p class="MsoNormal"><span style="font-size:11.0pt">As you’re considering changes, one concern that I still have is there remains no deprecation date for the Legacy profile — just the callout that it will be deprecated in the future. While I don’t believe this
to be a blocker to voting in favor of the ballot, I do think it would be better to adopt a date sooner than later so there’s ample time for CAs to adjust, rather than having a shorter time frame if a date is set in the future instead.<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">My proposal would be roughly (give or take a few months) October 1, 2024 as the date after which no new Legacy certs should be issued, which would mean the deprecation would complete some time in 2028. While
I’d prefer an earlier deprecation date, as mentioned numerous times, I think this time frame remains tractable.<o:p></o:p></span></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><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 Sep 15, 2022, at 9:01 AM, Stephen Davidson via Smcwg-public <<a href="mailto:smcwg-public@cabforum.org">smcwg-public@cabforum.org</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>
<p class="MsoNormal" style="margin-bottom:8.0pt;mso-line-height-alt:10.5pt"><span style="font-size:11.0pt">Thank you Matthias.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;mso-line-height-alt:10.5pt"><span style="font-size:11.0pt">Under the by-laws we may incorporate feedback into the text. I will add this, as well as changes addressing some other suggestions that have been made,
for circulation to the SMCWG before we move to ballot.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;mso-line-height-alt:10.5pt"><span style="font-size:11.0pt">Best regards, Stephen<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;mso-line-height-alt:10.5pt"><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>
<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">Wiedenhorst, Matthias <<a href="mailto:M.Wiedenhorst@tuvit.de"><span style="color:#0563C1">M.Wiedenhorst@tuvit.de</span></a>><span class="apple-converted-space"> </span><br>
<b>Sent:</b><span class="apple-converted-space"> </span>Thursday, September 15, 2022 5:39 AM<br>
<b>To:</b><span class="apple-converted-space"> </span>Stephen Davidson <<a href="mailto:Stephen.Davidson@digicert.com"><span style="color:#0563C1">Stephen.Davidson@digicert.com</span></a>>;<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>AW: Ballot SMC01: Final Guideline for “S/MIME Baseline Requirements”<o:p></o:p></span></p>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:10.5pt"> <span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:10.5pt"><span lang="EN-GB" style="font-family:"Arial",sans-serif;color:#1F497D">Dear Stephen, Dear all,</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:10.5pt"><span lang="EN-GB" style="font-family:"Arial",sans-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.</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:10.5pt"><span lang="EN-GB" style="font-family:"Arial",sans-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<span class="apple-converted-space"><i> </i></span><i>or ETSI EN 319 403-1</i>;"</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:10.5pt"><span lang="EN-GB" style="font-family:"Arial",sans-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",sans-serif;color:#1F497D">Requirements
for conformity assessment bodies assessing Trust Service Providers”</span></i><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:10.5pt"><span lang="EN-GB" style="font-family:"Arial",sans-serif;color:#1F497D"> </span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:10.5pt"><span lang="EN-GB" style="font-family:"Arial",sans-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.</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:10.5pt"><span lang="EN-GB" style="font-family:"Arial",sans-serif;color:#1F497D">Best regards<br>
Matthias</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:10.5pt"><span lang="EN-GB"> </span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<div>
<p class="MsoNormal"><b><span lang="DE" style="font-size:11.0pt">Von:</span></b><span class="apple-converted-space"><span lang="DE" style="font-size:11.0pt"> </span></span><span lang="DE" style="font-size:11.0pt">Smcwg-public <<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>Im
Auftrag von<span class="apple-converted-space"> </span></b>Stephen Davidson via Smcwg-public<br>
<b>Gesendet:</b><span class="apple-converted-space"> </span>Donnerstag, 8. September 2022 09:03<br>
<b>An:</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>Betreff:</b><span class="apple-converted-space"> </span>[Smcwg-public] Ballot SMC01: Final Guideline for “S/MIME Baseline Requirements”</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
</div>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:10.5pt"><span lang="DE"> </span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<div>
<p class="MsoNormal" style="background:white"><strong><span style="font-family:"Arial",sans-serif;color:#333333;border:none windowtext 1.0pt;padding:0cm">Ballot SMC01: Final Guideline for “S/MIME Baseline Requirements”</span></strong><span style="font-size:11.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><strong><span style="font-family:"Arial",sans-serif;color:#333333;border:none windowtext 1.0pt;padding:0cm"> </span></strong><span style="font-size:11.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><strong><span style="font-family:"Arial",sans-serif;color:#333333;border:none windowtext 1.0pt;padding:0cm">Purpose of Ballot:</span></strong><span style="font-size:11.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Arial",sans-serif;color:#333333"> </span><span style="font-size:11.0pt"><o:p></o:p></span></p>
</div>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:10.5pt"><span style="font-family:"Arial",sans-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.</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Arial",sans-serif;color:#333333"> </span><span style="font-size:11.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Arial",sans-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.</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Arial",sans-serif;color:#333333"> </span><span style="font-size:11.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Arial",sans-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:11.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Arial",sans-serif;color:#333333"> </span><span style="font-size:11.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><strong><span style="font-family:"Arial",sans-serif;color:#333333;border:none windowtext 1.0pt;padding:0cm">Charter Voting References</span></strong><span style="font-size:11.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Arial",sans-serif;color:#333333"> </span><span style="font-size:11.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black"><a href="https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fcabforum%2Fservercert%2Fblob%2Fe6ad111f4477010cbff409cd939c5ac1c7c85ccc%2Fdocs%2FSMCWG-charter.md%2351-voting-structure&data=05%7C01%7Crufus.buschart%40siemens.com%7Cb3c934224778424eb0d108da9b313e8a%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C637992933055563380%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=YU954Q27M9hsVu1Fyzmvi66z%2F%2BCkjzlH34WRV7DeIEE%3D&reserved=0"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#0563C1">Section
5.1 (“Voting Structure”)</span></a></span><span class="apple-converted-space"><span style="font-family:"Arial",sans-serif;color:#333333"> </span></span><span style="font-family:"Arial",sans-serif;color:#333333">of the SMCWG Charter says:</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Arial",sans-serif;color:#333333"> </span><span style="font-size:11.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Arial",sans-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).</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Arial",sans-serif;color:#333333"> </span><span style="font-size:11.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><strong><span style="font-family:"Arial",sans-serif;color:#333333;border:none windowtext 1.0pt;padding:0cm">— MOTION BEGINS —</span></strong><b><span style="font-family:"Arial",sans-serif;color:#333333;border:none windowtext 1.0pt;padding:0cm"><br>
</span></b><span style="font-family:"Arial",sans-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.</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Arial",sans-serif;color:#333333"> </span><span style="font-size:11.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Arial",sans-serif;color:#333333">The proposed S/MIME Baseline Requirements may be found at<a href="https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fcabforum%2Fsmime%2Fcompare%2F7b3ab3c55dd92052a8dc0d4f85a2ac26269c222e...28c0b904fe54f1c5f6c71d18c4786a3e02c76f52&data=05%7C01%7Crufus.buschart%40siemens.com%7Cb3c934224778424eb0d108da9b313e8a%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C637992933055563380%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Xt7dHCIbs8ZAv2krT41qVATtpqZlj0ToCbo3jTwHhiE%3D&reserved=0"><span style="color:#0563C1">https://github.com/cabforum/smime/compare/7b3ab3c55dd92052a8dc0d4f85a2ac26269c222e...28c0b904fe54f1c5f6c71d18c4786a3e02c76f52</span></a><span class="apple-converted-space"> </span>or
the attached document.</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Arial",sans-serif;color:#333333"> </span><span style="font-size:11.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Arial",sans-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.</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Arial",sans-serif;color:#333333"> </span><span style="font-size:11.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><strong><span style="font-family:"Arial",sans-serif;color:#333333;border:none windowtext 1.0pt;padding:0cm">— MOTION ENDS —</span></strong><b><span style="font-family:"Arial",sans-serif;color:#333333;border:none windowtext 1.0pt;padding:0cm"><br>
</span></b><span style="font-family:"Arial",sans-serif;color:#333333"><br>
This ballot proposes a Final Guideline. The procedure for approval of this ballot is as follows:</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Arial",sans-serif;color:#333333"> </span><span style="font-size:11.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Arial",sans-serif;color:#333333">Discussion (7+ days)</span><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black"><br>
</span><span style="font-family:"Arial",sans-serif;color:#333333">Start Time: 8 September 2022 17:00 UTC</span><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black"><br>
</span><span style="font-family:"Arial",sans-serif;color:#333333">End Time: 15 September 2022 17:00 UTC</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Arial",sans-serif;color:#333333"> </span><span style="font-size:11.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Arial",sans-serif;color:#333333">Vote for approval (7 days)</span><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black"><br>
</span><span style="font-family:"Arial",sans-serif;color:#333333">Start Time: 15 September 2022 17:00 UTC</span><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black"><br>
</span><span style="font-family:"Arial",sans-serif;color:#333333">End Time: 22 September 2022 17:00 UTC</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Arial",sans-serif;color:#333333"> </span><span style="font-size:11.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Arial",sans-serif;color:#333333">IPR Review (60 days)</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
</div>
<pre><span lang="DE" style="font-size:7.5pt;font-family:"Arial",sans-serif"> </span><o:p></o:p></pre>
<pre><strong><span lang="DE" style="font-size:7.5pt;font-family:"Arial",sans-serif">______________________________________________________________________________________________________________________</span></strong><o:p></o:p></pre>
<pre><strong><span lang="DE" style="font-size:7.5pt;font-family:"Arial",sans-serif">Sitz der Gesellschaft/Headquarter:</span></strong><span lang="DE" style="font-size:7.5pt;font-family:"Arial",sans-serif"> TÜV Informationstechnik GmbH * Am TÜV 1 * 45307 Essen, Germany</span><o:p></o:p></pre>
<pre><strong><span lang="DE" style="font-size:7.5pt;font-family:"Arial",sans-serif">Registergericht/Register Court:</span></strong><span lang="DE" style="font-size:7.5pt;font-family:"Arial",sans-serif"> Amtsgericht/Local Court Essen * HRB 11687 * USt.-IdNr./VAT No.: DE 176132277 * Steuer-Nr./Tax No.: 111/57062251</span><o:p></o:p></pre>
<pre><strong><span lang="DE" style="font-size:7.5pt;font-family:"Arial",sans-serif">Geschäftsführung/Management Board:</span></strong><span lang="DE" style="font-size:7.5pt;font-family:"Arial",sans-serif"> Dirk Kretzschmar </span><o:p></o:p></pre>
<div>
<p class="MsoNormal"><span lang="DE" style="font-size:11.0pt"> </span><span style="font-size:11.0pt"><o:p></o:p></span></p>
</div>
<pre><b><span lang="DE" style="font-size:12.0pt;font-family:"Arial",sans-serif">TÜV NORD GROUP</span></b><o:p></o:p></pre>
<pre><span lang="DE" style="font-size:7.5pt;font-family:"Arial",sans-serif">Expertise for your Success</span><o:p></o:p></pre>
<pre><b><span lang="DE" style="font-size:7.5pt;font-family:"Arial",sans-serif">Please visit our website: <a href="https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.tuv-nord.com%2F&data=05%7C01%7Crufus.buschart%40siemens.com%7Cb3c934224778424eb0d108da9b313e8a%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C637992933055563380%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=RV6mUVltJKhsiYLYsdfbRSM2%2F2AlDNBT2H%2FWUar6zMg%3D&reserved=0"><span style="color:#0563C1">www.tuv-nord.com</span></a></span></b><o:p></o:p></pre>
<pre><b><span lang="DE" style="font-size:7.5pt;font-family:"Arial",sans-serif">Besuchen Sie unseren Internetauftritt: <a href="https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.tuev-nord.de%2F&data=05%7C01%7Crufus.buschart%40siemens.com%7Cb3c934224778424eb0d108da9b313e8a%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C637992933055719597%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JRp3S6OfzjrVzeB7FrA5f%2FtM6hcEZON9ykb5V0ALFy8%3D&reserved=0"><span style="color:#0563C1">www.tuev-nord.de</span></a></span></b><o:p></o:p></pre>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif">_______________________________________________<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",sans-serif;color:#0563C1">Smcwg-public@cabforum.org</span></a></span><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif"><br>
</span><span style="font-size:11.0pt"><a href="https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.cabforum.org%2Fmailman%2Flistinfo%2Fsmcwg-public&data=05%7C01%7Crufus.buschart%40siemens.com%7Cb3c934224778424eb0d108da9b313e8a%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C637992933055719597%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=jvnOkLCcIMw16jrWCv5IEzfjno3o2OZAhmnZbvoi5uo%3D&reserved=0"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:#0563C1">https://lists.cabforum.org/mailman/listinfo/smcwg-public</span></a><o:p></o:p></span></p>
</div>
</blockquote>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt"> <o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>