<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=us-ascii">
<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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
h2
{mso-style-priority:9;
mso-style-link:"Heading 2 Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:18.0pt;
font-family:"Calibri",sans-serif;
color:black;}
h3
{mso-style-priority:9;
mso-style-link:"Heading 3 Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:13.5pt;
font-family:"Calibri",sans-serif;
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.Heading2Char
{mso-style-name:"Heading 2 Char";
mso-style-priority:9;
mso-style-link:"Heading 2";
font-family:"Calibri",sans-serif;
color:black;
mso-ligatures:none;
font-weight:bold;}
span.Heading3Char
{mso-style-name:"Heading 3 Char";
mso-style-priority:9;
mso-style-link:"Heading 3";
font-family:"Calibri",sans-serif;
color:black;
mso-ligatures:none;
font-weight:bold;}
span.EmailStyle22
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@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">
<h2><a name="_Hlk116919592">Minutes of SMCWG<o:p></o:p></a></h2>
<p class="MsoNormal"><span style="mso-bookmark:_Hlk116919592">December 6, 2023<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_Hlk116919592"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_Hlk116919592">These are the </span>
<span style="mso-bookmark:_Hlk116919592"><span style="color:windowtext">Approved</span> Minutes of the meeting described in the subject of this message. Corrections and clarifications where needed are encouraged by reply.<o:p></o:p></span></p>
<h3><span style="mso-bookmark:_Hlk116919592">Attendees <o:p></o:p></span></h3>
<h3><span style="mso-bookmark:_Hlk116919592"><span style="font-size:11.0pt;font-weight:normal">Adrian Mueller - (SwissSign), Alison Wang - (TrustAsia), Andrea Holland - (VikingCloud), Andreas Henschel - (D-TRUST), Ashish Dhiman - (GlobalSign), Ben Wilson -
(Mozilla), Bruce Morton - (Entrust), Cade Cairns - (Google), Christophe Bonjean - (GlobalSign), Corey Bonnell - (DigiCert), Dimitris Zacharopoulos - (HARICA), Don Sheehy - (CPA Canada/WebTrust), Inaba Atsushi - (GlobalSign), Marco Schambach - (IdenTrust),
Martijn Katerbarg - (Sectigo), Mrugesh Chandarana - (IdenTrust), Nome Huang - (TrustAsia), Rebecca Kelley - (Apple), Renne Rodriguez - (Apple), Rollin Yu - (TrustAsia), Russ Housley - (Vigil Security LLC), Stephen Davidson - (DigiCert), Tadahiko Ito - (SECOM
Trust Systems), Thomas Zermeno - (SSL.com), Tim Hollebeek - (DigiCert), Tsung-Min Kuo - (Chunghwa Telecom), Wendy Brown - (US Federal PKI Management Authority)<o:p></o:p></span></span></h3>
<h3><span style="mso-bookmark:_Hlk116919592">1. Roll Call<o:p></o:p></span></h3>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="mso-bookmark:_Hlk116919592">The Roll Call was taken.<o:p></o:p></span></p>
<h3><span style="mso-bookmark:_Hlk116919592">2. Read Antitrust Statement<o:p></o:p></span></h3>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="mso-bookmark:_Hlk116919592">The statement was read concerning the antitrust policy, code of conduct, and intellectual property rights agreement.<o:p></o:p></span></p>
<h3><span style="mso-bookmark:_Hlk116919592">3. Review Agenda<o:p></o:p></span></h3>
<p class="MsoNormal"><span style="mso-bookmark:_Hlk116919592">Minutes were prepared by Stephen Davidson.<o:p></o:p></span></p>
<h3><span style="mso-bookmark:_Hlk116919592">4. Approval of minutes from last teleconference<o:p></o:p></span></h3>
<p class="MsoNormal"><span style="mso-bookmark:_Hlk116919592">The minutes for the teleconference of November 15 were approved.<o:p></o:p></span></p>
<h3><span style="mso-bookmark:_Hlk116919592">5. Discussion <o:p></o:p></span></h3>
<p class="MsoNormal"><span style="mso-bookmark:_Hlk116919592">Stephen Davidson confirmed that Ballot SMC04 was scheduled to conclude IPR review on December 8 and no comments had so far been received.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_Hlk116919592"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_Hlk116919592">Stephen walked through the draft text of a ballot to introduce CAA for SMIME, which may be seen at
</span><a href="https://url.avanan.click/v2/___https:/github.com/srdavidson/smime/compare/241e92cde85c25d7e0d4a5c70118ecadacd4d72b...c432153a4375fbfa59bd3a75fd55e915b2f31938___.YXAzOmRpZ2ljZXJ0OmE6bzpiODIzYzhjMjAwZjgwNjE0MzUyMjA1NjUzOTQzMDQxNTo2OmU4YTk6Zjk5MDBmMWRiNTE5ZjdlNjdmOGUxZjg3MTJmYWU0MzRlOGNjODVlMTYzODljY2UyMjQ0Mjk1YjhlYzRlMGU0NzpoOkY" title="Protected by Avanan: https://github.com/srdavidson/smime/compare/241e92cde85c25d7e0d4a5c70118ecadacd4d72b...c432153a4375fbfa59bd3a75fd55e915b2f31938"><span style="mso-bookmark:_Hlk116919592">https://github.com/srdavidson/smime/compare/241e92cde85c25d7e0d4a5c70118ecadacd4d72b...c432153a4375fbfa59bd3a75fd55e915b2f31938</span><span style="mso-bookmark:_Hlk116919592"></span></a><span style="mso-bookmark:_Hlk116919592"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_Hlk116919592">He noted that he’d received good feedback from Cade Cairns and others, and welcomed comments on the text as the plan is to move to ballot in January. The ballot will be proposed by Corey Bonnell.
Ben Wilson offered to be an endorser. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_Hlk116919592"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_Hlk116919592">Stephen noted that there was a proposal to change the location of CAA info in the TLS BR and that he hoped the groups would maintain consistency.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_Hlk116919592"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_Hlk116919592">It was agreed to set adoption as a SHOULD starting on Sept 15 2024 and a SHALL starting on March 15 2025. He noted that CAs should be contacting vendors or engineering teams about those dates.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_Hlk116919592"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_Hlk116919592">The WG discussed the Sponsor Legacy profile, in particular if the standard should be made more specific to ensure that the subject is a human user, not an unattended mailbox or device (which were
intended to use the Mailbox or Org-validated profiles). Stephen noted the Sponsor Legacy was intended to be a flexible profile to assist in moving the S/MIME universe into the auditable environment of the S/MIME BR.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_Hlk116919592"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_Hlk116919592">He said the WG had the choice to tighten the Legacy profiles, which implied them being around for a long while, or to focus attention on implementation issues that prevented movement to the Multipurpose
or Strict profiles. He asked CAs to provide feedback from their implementation, noting that he understood that ERAs may have difficulty providing givenName and surname as separate fields rather than the just the complete name as a CN. Tim Hollebeek commented
this may be a dominant issue for ERAs that might otherwise move to the Multipurpose profile.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_Hlk116919592"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_Hlk116919592">Ben said that for now the WG should retain the flexibility of the Legacy profiles with clarifications if required but that it was important to gather data to inform the improvement of the standard
as well as the eventual deprecation of the Legacy.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_Hlk116919592"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_Hlk116919592">Martijn Katerbarg proposed improvement to Section 1.2 describing Mailbox profiles as the current text might be understood to ban the CN, which was not intended.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_Hlk116919592"><o:p> </o:p></span></p>
<h3 style="mso-margin-top-alt:1.0pt;margin-right:0in;margin-bottom:1.0pt;margin-left:0in">
<span style="mso-bookmark:_Hlk116919592">6. Any Other Business<o:p></o:p></span></h3>
<p class="MsoNormal"><span style="mso-bookmark:_Hlk116919592"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_Hlk116919592">None<o:p></o:p></span></p>
<h3><span style="mso-bookmark:_Hlk116919592">7. Next call<o:p></o:p></span></h3>
<p class="MsoNormal"><span style="mso-bookmark:_Hlk116919592">Next call: Wednesday, December 20, 2023 at 11:00 am Eastern Time<o:p></o:p></span></p>
<h3><span style="mso-bookmark:_Hlk116919592"><span lang="DE">Adjourned</span></span><span style="mso-bookmark:_Hlk116919592"></span><o:p></o:p></h3>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
</div>
</body>
</html>