<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;}
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;
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;
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;}
@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>Minutes of SMCWG<o:p></o:p></h2><p class=MsoNormal>September 30, 2020<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>These are the Approved Minutes of the Teleconference described in the subject of this message. <o:p></o:p></p><h3>Attendees <o:p></o:p></h3><p class=MsoNormal>Adrian Mueller (SwissSign), Ahmad Syafiq Md Zaini (MSC Trustgate.com), Andreas Henschel (D-TRUST), Atsushi Inaba (GlobalSign), Ben Wilson (Mozilla), Bruce Morton (Entrust DataCard), Burkhard Wiegel (Zertificon), Dean Coclin (DigiCert), Don Sheehy (WebTrust), Doug Beattie (GlobalSign), Dr. Holger Muehlbauer (TeleTrust), Hazhar Ismail (MSC Trustgate.com), Hugh Mercer (GlobalSign), India Donald (Federal PKI), James Knapp (Federal PKI), Janet Hines (Trustwave), Jeff Ward (WebTrust), Li-Chun Chen (Chunghwa Telecom ), Mads Henriksveen (BuyPass), Mike Guenther (SwissSign), Morad Abou Nasser (TeleTrust), Rufus Buschart (TeleTrust), Russ Housley (Vigil Security, LLC), Stephen Davidson (DigiCert), Tadahiko Ito (SECOM Trust Systems), Tim Crawford (WebTrust), Tim Hollebeek (DigiCert), Wendy Brown (Federal PKI)<o:p></o:p></p><h3>1. Roll Call<o:p></o:p></h3><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>The Roll Call was taken.<o:p></o:p></p><h3>2. Read Antitrust Statement<o:p></o:p></h3><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>The Antitrust/Compliance Statement was read.<o:p></o:p></p><h3>3. Review Agenda<o:p></o:p></h3><h3>4. Approval of minutes from last teleconference<o:p></o:p></h3><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>The minutes of the September 16 teleconference were approved.<o:p></o:p></p><h3>5. Discussion of approach and deliverables<o:p></o:p></h3><p class=MsoNormal>The discussion continued regarding the fields in S/MIME leaf certificates.<o:p></o:p></p><p class=MsoNormal><a href="https://docs.google.com/spreadsheets/d/1gEq-o4jU1FWvKBeMoncfmhAUemAgGuvVRSLQb7PedLU/edit?usp=sharing">https://docs.google.com/spreadsheets/d/1gEq-o4jU1FWvKBeMoncfmhAUemAgGuvVRSLQb7PedLU/edit?usp=sharing</a><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Validity period: confirming that initial version will seek a maximum validity SHOULD of 27 months and a MUST of 5 years rather than seek to vary by use of tokens or other variables.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Subject DN: will be addressed later in our work, with the exception of noting that all email addresses in an S/MIME certificate must be verified whether in Subject DN or SAN. There was a preference towards adopting the BR and Gmail requirement for an email address in the Subject to be repeated in the SAN).<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Subject Public Key Information: There was discussion at length regarding allowed algorithms. The Mozilla policy and BR focus on webpki preferences. However, there may be interest from Certificate Issuers and their customers in alternative algorithms. These include Curve25519 and Curve 448 (RFC 7748), BrainPool (recommended by German Government standard from BSI TR-03116), Gost (RFC 7901), SM2 (IETF draft-shen-sm2-ecdsa-02).<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Currently the Mozilla root store agreement states that “Root certificates in our root program, and any certificate which chains up to them, MUST use only algorithms and key sizes from the following set”. Mozilla stated openness to adapt that text should there be demand amongst S/MIME Certificate Issuers or Certificate Consumers. A decision was made to gather more information and revisit the subject in a later meeting.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Key Usage: There was discussion relating to dual use versus split use certificates (and the latter applicability when key escrow is provided). It was pointed out that the Gmail policy would seem to exclude split keys (as MUST for digitalSignature and/or nonrepudiation). There is significant variation in practice.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>There was discussion regarding key escrow: only allowing for encryption keys. There may be interest in marking keys where the CA generates keys, but may be deceptive as key escrow could be occurring outside the CA (such as using an enterprise key management system).<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><h3 style='mso-margin-top-alt:1.0pt;margin-right:0in;margin-bottom:1.0pt;margin-left:0in'>6. Any Other Business<o:p></o:p></h3><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>No other business.<o:p></o:p></p><h3>7. Next call<o:p></o:p></h3><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>The next call will take place on October 14, 2020 at 11:00am Eastern Time. <o:p></o:p></p><h3><span lang=DE>Adjourned</span><o:p></o:p></h3><p class=MsoNormal><o:p> </o:p></p></div></body></html>