<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=iso-8859-1">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle19
{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="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Thanks Rufus<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">For version 1, our goal is to set baseline requirements for S/MIME.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We’ve already discussed “leaving flex” in the profiles to express adherence to other schemes such as Qualified using qcStatement extensions. If there is a defined standard for expressing NIST SP 800-63-3 (or other similar reqs) in certs
today, that may also be of interest. If there is no current established practice, this is probably best left for a later version of the S/MIME BR.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best regards, Stephen<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Smcwg-public <smcwg-public-bounces@cabforum.org>
<b>On Behalf Of </b>Buschart, Rufus via Smcwg-public<br>
<b>Sent:</b> Monday, August 9, 2021 11:58 AM<br>
<b>To:</b> smcwg-public@cabforum.org<br>
<b>Subject:</b> [Smcwg-public] Identity and Authentication Assurance Level acc. NIST SP 800-63-3<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="DE">Dear S/MIME WG!<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="DE"><o:p> </o:p></span></p>
<p class="MsoNormal">Do you have best practices or recommendations on how to store the Identity and Authentication Assurance Level according to NIST SP 800-63-3 within a S/MIME certificate? Is this something we want to regulate within the S/MIME BRGs?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="DE" style="font-size:10.0pt;font-family:"Arial",sans-serif">Mit freundlichen Grüßen<br>
Rufus Buschart<br>
<br>
Siemens AG<br>
Information Technology<br>
Infrastructure<br>
Technical Solution & Service Quality 1<br>
IT IN COR TSQ-1<br>
Freyeslebenstr. 1<br>
91058 Erlangen, Deutschland<br>
Tel.: +49 1522 2894134<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><a href="mailto:rufus.buschart@siemens.com"><span lang="DE">mailto:rufus.buschart@siemens.com</span></a></span><span lang="DE" style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><a href="https://siemens.com"><span lang="DE">www.siemens.com</span></a></span><span lang="DE" style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><img border="0" width="202" height="80" style="width:2.1041in;height:.8333in" id="Picture_x0020_1" src="cid:image001.gif@01D78DE4.0A699330"></span><span lang="DE" style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
</span><span lang="DE" style="font-size:8.0pt;font-family:"Arial",sans-serif">Siemens Aktiengesellschaft: Vorsitzender des Aufsichtsrats: Jim Hagemann Snabe; Vorstand: Roland Busch, Vorsitzender; Cedrik Neike, Matthias Rebellius, Ralf P. Thomas, Judith Wiese;
Sitz der Gesellschaft: Berlin und München, Deutschland; Registergericht: Berlin-Charlottenburg, HRB 12300, München, HRB 6684; WEEE-Reg.-Nr. DE 23691322</span><span lang="DE"><o:p></o:p></span></p>
</div>
</body>
</html>