<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-top:0in;
margin-right:0in;
margin-bottom:8.0pt;
margin-left:0in;
line-height:106%;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@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">Hi all:<o:p></o:p></p>
<p class="MsoNormal">We’ve had some useful discussion in the group lately about areas where the S/MIME BR may deviate from existing guidance from root programs or Cert Consumer software.<o:p></o:p></p>
<p class="MsoNormal">For example the gmail profile currently stipulates for keyUsage:<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">Bit positions must be set for either: digitalSignature and/or nonRepudiation/ contentCommitment<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">Bit positions may be set for: dataEncipherment and/or keyEncipherment<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">Other bit positions must not be set.<o:p></o:p></p>
<p class="MsoNormal">Under this profile, the use of split (separate signing and key management) keys would not be allowed. Split keys are a common S/MIME deployment.<o:p></o:p></p>
<p class="MsoNormal">We’d like to verify the reach of the Cert Consumer profiles where the draft S/MIME BR deviates from existing texts. We’ve gone through detailed work to incorporate the existing guidance but, for example, the draft S/MIME BR will allow
the use of split keys:<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">For signing only, bit positions MUST be set for: digitalSignature<br>
Bit positions MAY be set for:nonRepudiation/ contentCommitment <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">For key management only, bit positions MUST be set for: keyEncipherment<br>
Bit positions MAY be set for: dataEncipherment<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">For dual use, bit positions MUST be set for: keyEncipherment and digitalSignature<br>
Bit positions MAY be set for: nonRepudiation/contentCommitment and/or dataEncipherment<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">Other bit positions MUST NOT be set.<o:p></o:p></p>
<p class="MsoNormal">Do we have agreement from the Cert Consumers on this approach?<o:p></o:p></p>
<p class="MsoNormal">Best regards, Stephen<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>