<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)"><!--[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:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@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:Aptos;}
@font-face
{font-family:-webkit-standard;
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* 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;}
code
{mso-style-priority:99;
font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
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;
mso-ligatures:none;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:660624022;
mso-list-template-ids:184724286;}
@list l1
{mso-list-id:1170753767;
mso-list-template-ids:-78498536;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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>What is the rationale? These are extensions that are optionally being put into the certificate at the request of the customer. Sure, if they’re critical, some software that doesn’t understand them will be forced to reject them, but that’s how critical extensions are intended to work.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>So I don’t really understand what such a restriction is trying to accomplish.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>-Tim<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><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>Russ Housley via Smcwg-public<br><b>Sent:</b> Monday, February 12, 2024 10:22 AM<br><b>To:</b> Martijn Katerbarg <martijn.katerbarg@sectigo.com><br><b>Cc:</b> SMIME Certificate Working Group <smcwg-public@cabforum.org><br><b>Subject:</b> Re: [Smcwg-public] Certificate Template Information extension and SBR allowance<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:13.5pt;font-family:"-webkit-standard",serif'>I think the text should require such extension to be non-critical.</span><o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"-webkit-standard",serif'>Russ</span><o:p></o:p></p><div><p class=MsoNormal><br><br><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal>On Feb 12, 2024, at 5:54 AM, Martijn Katerbarg via Smcwg-public <<a href="mailto:smcwg-public@cabforum.org">smcwg-public@cabforum.org</a>> wrote:<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>Thanks all. Proposed language is in<span class=apple-converted-space> </span><span lang=SV><a href="https://url.avanan.click/v2/___https:/github.com/srdavidson/smime/pull/10___.YXAzOmRpZ2ljZXJ0OmE6bzpmZDdkNmUwYWRjN2NiYWJhZWE2NGI2MmNmYWExODIzYzo2OmUxOGI6OTU3ZDM3ODZkYTdmOWRlZTIxMjAyYTE2YWRjMmVlM2Y3N2UzNjc4NTRjNjhhZTk1MTcyN2M2ZTU2ZjU1MTQ3MjpoOkY" title="Protected by Avanan: https://github.com/srdavidson/smime/pull/10"><span lang=EN-US>https://github.com/srdavidson/smime/pull/10</span></a></span><span style='font-size:10.0pt'><o:p></o:p></span></p></div><div><p class=MsoNormal> <span style='font-size:10.0pt'><o:p></o:p></span></p></div><div><p class=MsoNormal> <span style='font-size:10.0pt'><o:p></o:p></span></p></div><div id=mail-editor-reference-message-container><div><div style='border:none;border-top:solid windowtext 1.0pt;padding:3.0pt 0in 0in 0in;border-color:currentcolor currentcolor;border-image: none'><p class=MsoNormal style='margin-bottom:12.0pt'><b><span style='font-size:12.0pt;font-family:"Aptos",sans-serif'>From:<span class=apple-converted-space> </span></span></b><span style='font-size:12.0pt;font-family:"Aptos",sans-serif'>Tim Hollebeek <<a href="mailto:tim.hollebeek@digicert.com">tim.hollebeek@digicert.com</a>><br><b>Date:<span class=apple-converted-space> </span></b>Wednesday, 17 January 2024 at 22:01<br><b>To:<span class=apple-converted-space> </span></b>Clint Wilson <<a href="mailto:clintw@apple.com">clintw@apple.com</a>>, Martijn Katerbarg <<a href="mailto:martijn.katerbarg@sectigo.com">martijn.katerbarg@sectigo.com</a>>, SMIME Certificate Working Group <<a href="mailto:smcwg-public@cabforum.org">smcwg-public@cabforum.org</a>><br><b>Cc:<span class=apple-converted-space> </span></b>Dimitris Zacharopoulos <<a href="mailto:dzacharo@harica.gr">dzacharo@harica.gr</a>><br><b>Subject:<span class=apple-converted-space> </span></b>RE: [Smcwg-public] Certificate Template Information extension and SBR allowance</span><span style='font-size:10.0pt'><o:p></o:p></span></p></div><div><p class=MsoNormal>Yep. If you use a SDO OID, you MUST use it in compliance with all the associated restrictions in the relevant standard.<span style='font-size:10.0pt'><o:p></o:p></span></p></div><div><p class=MsoNormal> <span style='font-size:10.0pt'><o:p></o:p></span></p></div><div><p class=MsoNormal>Otherwise you’re using the OID for something else entirely, which you do not have the “right” to do.<span style='font-size:10.0pt'><o:p></o:p></span></p></div><div><p class=MsoNormal> <span style='font-size:10.0pt'><o:p></o:p></span></p></div><div><p class=MsoNormal>You cannot claim that you have the “right” to use the CABF OrgID extension to identify a cheeseburger in order to allow customers to put cheeseburgers in certificates. If you’re using an extension, you need to use it in the intended way.<span style='font-size:10.0pt'><o:p></o:p></span></p></div><div><p class=MsoNormal> <span style='font-size:10.0pt'><o:p></o:p></span></p></div><div><p class=MsoNormal>Using extensions in non-standard ways eventually renders them useless and gets them banned (see: Organizational Unit).<span style='font-size:10.0pt'><o:p></o:p></span></p></div><div><p class=MsoNormal> <span style='font-size:10.0pt'><o:p></o:p></span></p></div><div><p class=MsoNormal>-Tim<span style='font-size:10.0pt'><o:p></o:p></span></p></div><div><p class=MsoNormal> <span style='font-size:10.0pt'><o:p></o:p></span></p></div><div style='border:none;border-left:solid windowtext 1.5pt;padding:0in 0in 0in 4.0pt;border-color:currentcolor currentcolor currentcolor blue;border-image: none'><div><div style='border:none;border-top:solid windowtext 1.0pt;padding:3.0pt 0in 0in 0in;border-color:currentcolor currentcolor;border-image: none'><div><p class=MsoNormal><b>From:</b><span class=apple-converted-space> </span>Clint Wilson <<a href="mailto:clintw@apple.com">clintw@apple.com</a>><span class=apple-converted-space> </span><br><b>Sent:</b><span class=apple-converted-space> </span>Tuesday, January 16, 2024 3:19 PM<br><b>To:</b><span class=apple-converted-space> </span>Martijn Katerbarg <<a href="mailto:martijn.katerbarg@sectigo.com">martijn.katerbarg@sectigo.com</a>>; SMIME Certificate Working Group <<a href="mailto:smcwg-public@cabforum.org">smcwg-public@cabforum.org</a>><br><b>Cc:</b><span class=apple-converted-space> </span>Tim Hollebeek <<a href="mailto:tim.hollebeek@digicert.com">tim.hollebeek@digicert.com</a>>; Dimitris Zacharopoulos <<a href="mailto:dzacharo@harica.gr">dzacharo@harica.gr</a>><br><b>Subject:</b><span class=apple-converted-space> </span>Re: [Smcwg-public] Certificate Template Information extension and SBR allowance<span style='font-size:10.0pt'><o:p></o:p></span></p></div></div></div><div><p class=MsoNormal> <span style='font-size:10.0pt'><o:p></o:p></span></p></div><div><p class=MsoNormal>While I think I agree with the intent of Tim’s statement (especially in the context of this discussion and its applicability thereto), taken literally I believe it is stating something with broader impact than intended. <span style='font-size:10.0pt'><o:p></o:p></span></p></div><div><div><p class=MsoNormal>What I mean is that it’s important to carry the complete context of an OID over, including the requirements and/or prerequisites outlined for the use of an OID (to the extent specified or stipulated by the governing SDO). The “right” exists, but so to do obligations coinciding with the use of many (all?) OIDs. I believe everyone here’s suitably aware of this, but just wanted to state it explicitly so that too much nuance isn’t lost with any potential changes made to the text.<span style='font-size:10.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal> <span style='font-size:10.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal>Cheers,<span style='font-size:10.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal>-Clint<span style='font-size:10.0pt'><o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'> <span style='font-size:10.0pt'><o:p></o:p></span></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><div><p class=MsoNormal>On Jan 16, 2024, at 11:27 AM, Martijn Katerbarg via Smcwg-public <<a href="mailto:smcwg-public@cabforum.org">smcwg-public@cabforum.org</a>> wrote:<span style='font-size:10.0pt'><o:p></o:p></span></p></div></div><div><p class=MsoNormal> <span style='font-size:10.0pt'><o:p></o:p></span></p></div><div><div><div><div><p class=MsoNormal>> Absolutely. Any OID that comes from a Standards Development Organization is intended for use by other organizations, and everyone has the “right” to use them.<span style='font-size:10.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal> <span style='font-size:10.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal> <span style='font-size:10.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal> <span style='font-size:10.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal>I’d like to be able to read it this way, but I am concerned that the current language is too limiting in this regard.<span style='font-size:10.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal> <span style='font-size:10.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal>Tim, since you also mentioned not liking the language, I’ll see if I can come up with an alternative to make this clear, and also make the implied allowance a stated fact.<span style='font-size:10.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal> <span style='font-size:10.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal> <span style='font-size:10.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal> <span style='font-size:10.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal>Regards,<span style='font-size:10.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal> <span style='font-size:10.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal>Martijn<span style='font-size:10.0pt'><o:p></o:p></span></p></div></div><div id=ms-outlook-mobile-signature><div><div><p class=MsoNormal> <span style='font-size:10.0pt'><o:p></o:p></span></p></div></div></div><div id=mail-editor-reference-message-container><div><p class=MsoNormal> <span style='font-size:10.0pt'><o:p></o:p></span></p></div><div class=MsoNormal align=center style='text-align:center'><hr size=1 width="100%" align=center></div><div id=divRplyFwdMsg><div><p class=MsoNormal><strong><span style='font-family:"Calibri",sans-serif'>From:</span></strong><span class=apple-converted-space> </span>Tim Hollebeek <<a href="mailto:tim.hollebeek@digicert.com">tim.hollebeek@digicert.com</a>><br><strong><span style='font-family:"Calibri",sans-serif'>Sent:</span></strong><span class=apple-converted-space> </span>Wednesday, January 10, 2024 10:58:58 pm<br><strong><span style='font-family:"Calibri",sans-serif'>To:</span></strong><span class=apple-converted-space> </span>Dimitris Zacharopoulos <<a href="mailto:dzacharo@harica.gr">dzacharo@harica.gr</a>>; SMIME Certificate Working Group <<a href="mailto:smcwg-public@cabforum.org">smcwg-public@cabforum.org</a>><br><strong><span style='font-family:"Calibri",sans-serif'>Cc:</span></strong><span class=apple-converted-space> </span>Martijn Katerbarg <<a href="mailto:martijn.katerbarg@sectigo.com">martijn.katerbarg@sectigo.com</a>><br><strong><span style='font-family:"Calibri",sans-serif'>Subject:</span></strong><span class=apple-converted-space> </span>RE: [Smcwg-public] Certificate Template Information extension and SBR allowance<span style='font-size:10.0pt'><o:p></o:p></span></p></div></div><p class=MsoNormal style='margin-bottom:12.0pt'> <span style='font-size:10.0pt'><o:p></o:p></span></p><div><div><p class=MsoNormal>Absolutely. Any OID that comes from a Standards Development Organization is intended for use by other organizations, and everyone has the “right” to use them.<span style='font-size:10.0pt'><o:p></o:p></span></p></div></div><div><p class=MsoNormal> <span style='font-size:10.0pt'><o:p></o:p></span></p></div><div><div><p class=MsoNormal>-Tim<span style='font-size:10.0pt'><o:p></o:p></span></p></div></div><div><p class=MsoNormal> <span style='font-size:10.0pt'><o:p></o:p></span></p></div><div style='border:none;border-left:solid windowtext 1.5pt;padding:0in 0in 0in 4.0pt;border-color:currentcolor currentcolor currentcolor blue;border-image: none'><div><div style='border:none;border-top:solid windowtext 1.0pt;padding:3.0pt 0in 0in 0in;border-color:currentcolor currentcolor;border-image: none'><div><div><p class=MsoNormal><b>From:</b><span class=apple-converted-space> </span>Dimitris Zacharopoulos <<a href="mailto:dzacharo@harica.gr">dzacharo@harica.gr</a>><span class=apple-converted-space> </span><br><b>Sent:</b><span class=apple-converted-space> </span>Wednesday, January 10, 2024 12:48 PM<br><b>To:</b><span class=apple-converted-space> </span>Tim Hollebeek <<a href="mailto:tim.hollebeek@digicert.com">tim.hollebeek@digicert.com</a>>; SMIME Certificate Working Group <<a href="mailto:smcwg-public@cabforum.org">smcwg-public@cabforum.org</a>><br><b>Cc:</b><span class=apple-converted-space> </span>Martijn Katerbarg <<a href="mailto:martijn.katerbarg@sectigo.com">martijn.katerbarg@sectigo.com</a>><br><b>Subject:</b><span class=apple-converted-space> </span>Re: [Smcwg-public] Certificate Template Information extension and SBR allowance<span style='font-size:10.0pt'><o:p></o:p></span></p></div></div></div></div><div><p class=MsoNormal> <span style='font-size:10.0pt'><o:p></o:p></span></p></div><div><div><div><p class=MsoNormal><span style='font-family:"Arial",sans-serif'>I also believe that any publicly supported and documented X.509 extension (e.g. defined by IETF or ITU-T) are allowed for use by CAs, as long as they are documented in the CA's CPS.<span class=apple-converted-space> </span><br><br>Is there anything that prevents it in the current CA/B Forum documents?<span class=apple-converted-space> </span><br><br><br>Thanks,<span class=apple-converted-space> </span></span><span style='font-size:10.0pt'><o:p></o:p></span></p></div></div></div><div><p><span style='font-size:9.0pt;font-family:"Arial",sans-serif'>DZ.</span><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'><o:p></o:p></span></p></div><div><div><p><span style='font-size:9.0pt;font-family:"Arial",sans-serif'>Jan 10, 2024 20:38:19 Tim Hollebeek via Smcwg-public <<a href="mailto:smcwg-public@cabforum.org">smcwg-public@cabforum.org</a>>:</span><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'><o:p></o:p></span></p></div><blockquote style='border:none;border-left:solid windowtext 2.25pt;padding:0in 0in 0in 8.0pt;margin-left:0in;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt;border-color:currentcolor currentcolor currentcolor rgb(204, 204, 204);border-image: none'><div><div><p class=MsoNormal>You don’t need a contract to have a right to use someone else’s extension.<span style='font-size:10.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal>I would say that if Microsoft has public documentation that says or implies that the extension can and should be used by other organizations, then other organizations “have the right” to use that extension.<span style='font-size:10.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal>That said, I have never liked this language, which comes from the TLS BRs. I would support making it more clear as to what is and isn’t allowed, and even maybe clarifying what problem is being solved with these requirements.<span style='font-size:10.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal>-Tim<span style='font-size:10.0pt'><o:p></o:p></span></p></div></div><div style='border:none;border-left:solid windowtext 1.5pt;padding:0in 0in 0in 4.0pt;border-color:currentcolor currentcolor currentcolor blue;border-image: none'><div><div style='border:none;border-top:solid windowtext 1.0pt;padding:3.0pt 0in 0in 0in;border-color:currentcolor currentcolor;border-image: none'><div><div><p class=MsoNormal><b>From:</b><span class=apple-converted-space> </span>Smcwg-public <<a href="mailto:smcwg-public-bounces@cabforum.org">smcwg-public-bounces@cabforum.org</a>><span class=apple-converted-space> </span><b>On Behalf Of<span class=apple-converted-space> </span></b>Martijn Katerbarg via Smcwg-public<br><b>Sent:</b><span class=apple-converted-space> </span>Wednesday, January 10, 2024 5:54 AM<br><b>To:</b><span class=apple-converted-space> </span>SMIME Certificate Working Group <<a href="mailto:smcwg-public@cabforum.org">smcwg-public@cabforum.org</a>><br><b>Subject:</b><span class=apple-converted-space> </span>[Smcwg-public] Certificate Template Information extension and SBR allowance<span style='font-size:10.0pt'><o:p></o:p></span></p></div></div></div></div><div><div><p class=MsoNormal><span lang=SV>Hi all,</span><span style='font-size:10.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal>There’s been a request within the S/MIME working group to bring forward issues that have arisen since the adoption of the SBRs. While we’ve not seen a whole lot of issues, we believe we may have discovered one now.<span style='font-size:10.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal>We offer support for Windows’s own auto-enrollment features. In the past we used to include the “Certificate Template Information” extension (OID 1.3.6.1.4.1.311.21.7) for this purpose. Since we started issuing SBR compliant certificates prior to September 1<sup>st</sup>, we removed support for this extension on publicly trusted S/MIME certificates.<span style='font-size:10.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal>As we now have noticed, this has led to a partial breakdown of the auto-enrollment system. From what we understand, the auto-enrollment mechanism is specifically looking for this extension in certificates, if a certificate for a particular required Certificate Template (as specified through AD) is not found, auto-enrollment will “do its job”, and request a new certificate. This can lead to multiple new certificates being installed in a single day, all because the extension is missing.<span style='font-size:10.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal>We’ve investigated bringing back support for the extension, and are led to the conclusion that no, this extension would not be allowed per the current language. A breakdown:<span style='font-size:10.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal>Section 7.1.2.4 (<a href="https://url.avanan.click/v2/___https:/github.com/cabforum/smime/blob/main/SBR.md%237124-all-certificates___.YXAzOmRpZ2ljZXJ0OmE6bzphYmIxNjU3ZGU1ZTYwODNjM2Q3N2NjOTI2NDlhNTFhNzo2Ojk4ZDE6N2VhYmQyYzcxNDdhYjlhZDExZmE0MDI3ZWVmYzEyNDY0YzM5YjI1Yzc0NjEzZmUwZTU2MGJjMzhiM2QxMWRjMDpoOkY" title="Protected by Avanan: https://github.com/cabforum/smime/blob/main/SBR.md#7124-all-certificates">https://github.com/cabforum/smime/blob/main/SBR.md#7124-all-certificates</a><span class=apple-converted-space> </span>) states:<span style='font-size:10.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><i>“All fields and extensions SHALL be set in accordance with<span class=apple-converted-space> </span><a href="https://url.avanan.click/v2/___https:/datatracker.ietf.org/doc/html/rfc5280___.YXAzOmRpZ2ljZXJ0OmE6bzphYmIxNjU3ZGU1ZTYwODNjM2Q3N2NjOTI2NDlhNTFhNzo2OmIzZWM6YWE0NTVlYmI4ZDk2OWMwMzJkZmQ1NzM5YzE3YzAwOGUyOGFiYWE2ZTMyNDA4YWY4YTc2MzQyZWVlNDNlMjIzNTpoOkY" title="Protected by Avanan: https://datatracker.ietf.org/doc/html/rfc5280">RFC 5280</a>. The CA SHALL NOT issue a Certificate that contains a<span class=apple-converted-space> </span></i><code><i><span style='font-size:10.0pt'>keyUsage</span></i></code><span class=apple-converted-space><i> </i></span><i>flag,<span class=apple-converted-space> </span></i><code><i><span style='font-size:10.0pt'>extKeyUsage</span></i></code><span class=apple-converted-space><i> </i></span><i>value, Certificate extension, or other data not specified in<span class=apple-converted-space> </span><a href="https://url.avanan.click/v2/___https:/github.com/cabforum/smime/blob/main/SBR.md%237121-root-ca-certificates___.YXAzOmRpZ2ljZXJ0OmE6bzphYmIxNjU3ZGU1ZTYwODNjM2Q3N2NjOTI2NDlhNTFhNzo2OmZjMDg6MzYxZGEyOGIzOWI5YmEzY2Y4MjRiOTczYzlkZGMzYmIyNTk4YWU4ZjRkNTRhNzdmNGNlNGI4Y2E3MGZhOGVjZDpoOkY" title="Protected by Avanan: https://github.com/cabforum/smime/blob/main/SBR.md#7121-root-ca-certificates">Section 7.1.2.1</a>,<span class=apple-converted-space> </span><a href="https://url.avanan.click/v2/___https:/github.com/cabforum/smime/blob/main/SBR.md%237122-subordinate-ca-certificates___.YXAzOmRpZ2ljZXJ0OmE6bzphYmIxNjU3ZGU1ZTYwODNjM2Q3N2NjOTI2NDlhNTFhNzo2OmU0MTg6MzE4Mzc4YTg4NThmMzMxOWY3Yjk3OGM1MmMyNzgzNTNkYzRiMmRiNTg4NWM0YmFlOTQ4MDAyZTMxZWQyYWY0NzpoOkY" title="Protected by Avanan: https://github.com/cabforum/smime/blob/main/SBR.md#7122-subordinate-ca-certificates">Section 7.1.2.2</a>, or<span class=apple-converted-space> </span><a href="https://url.avanan.click/v2/___https:/github.com/cabforum/smime/blob/main/SBR.md%237123-subscriber-certificates___.YXAzOmRpZ2ljZXJ0OmE6bzphYmIxNjU3ZGU1ZTYwODNjM2Q3N2NjOTI2NDlhNTFhNzo2OmRmM2E6ZDE5OTU5Yjg2ODJhYmVkOGZhYjUzMDcwNGY3MDNiZTQ2ZTQ3YTkxMWQ1NjE0OGMxOTJmNjQwYmIxNTI0ZDAwZjpoOkY" title="Protected by Avanan: https://github.com/cabforum/smime/blob/main/SBR.md#7123-subscriber-certificates">Section 7.1.2.3</a><span class=apple-converted-space> </span>unless the CA is aware of a reason for including the data in the Certificate. If the CA includes fields or extensions in a Certificate that are not specified but are otherwise permitted by these Requirements, then the CA SHALL document the processes and procedures that the CA employs for the validation of information contained in such fields and extensions in its CP and/or CPS.”</i><span style='font-size:10.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal>So far, we could see allowing the extension. We have “a reason for including the data in the Certificate”, and we could update our CPS. However, the language continues with an additional SHALL NOT:<span style='font-size:10.0pt'><o:p></o:p></span></p></div></div><p><i><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'>“CAs SHALL NOT issue a Certificate with:</span></i><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'><o:p></o:p></span></p><ol style='margin-top:0in' start=1 type=1><li class=MsoNormal style='mso-list:l0 level1 lfo1'><i>Extensions that do not apply in the context of the public Internet (such as an<span class=apple-converted-space> </span></i><i><span style='font-size:10.0pt;font-family:"Courier New"'>extKeyUsage</span></i><span class=apple-converted-space><i> </i></span><i>value for a service that is only valid in the context of a privately managed network), unless:<br>i. such value falls within an OID arc for which the Applicant demonstrates ownership, or<br>ii. the Applicant can otherwise demonstrate the right to assert the data in a public context; or</i><span style='font-size:10.0pt'><o:p></o:p></span></li><li class=MsoNormal style='mso-list:l0 level1 lfo1'><i>Field or extension values which have not been validated according to the processes and procedures described in these Requirements or the CA's CP and/or CPS.</i>”<span style='font-size:10.0pt'><o:p></o:p></span></li></ol><div><div><p class=MsoNormal>So while the first section might allow us to incorporate the extension, it seems we also need to meet one of the statements in this block:<span style='font-size:10.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal>“<i>Extensions that do not apply in the context of the public Internet (such as an<span class=apple-converted-space> </span></i><i><span style='font-size:10.0pt;font-family:"Courier New"'>extKeyUsage</span></i><span class=apple-converted-space><i> </i></span><i>value for a service that is only valid in the context of a privately managed network), unless:”<br></i>This extension indeed does not apply in the context of the public Internet. So, we move into the exception cases:<span style='font-size:10.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><i>”i. such value falls within an OID arc for which the Applicant demonstrates ownership, or”<br></i>No. Neither us, nor the Applicant owns the OID. It’s an OID under the Microsoft OID arc.<span style='font-size:10.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal>”<span class=apple-converted-space><i> </i></span><i>ii. the Applicant can otherwise demonstrate the right to assert the data in a public context; or”<br></i>Unless the Applicant gets a contract stating they were given the right by Microsoft, we don’t see how this requirement is met.<span class=apple-converted-space> </span><span style='font-size:10.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal>Then we’re left with “<i>Field or extension values which have not been validated according to the processes and procedures described in these Requirements or the CA's CP and/or CPS.”<br></i>This one is a bit odd. Does this suddenly suggest or imply that the CA may include any field or extension that has been validated according only to the CA’s CP and/or CPS? Item “(ii)” ends with an “or”. However, we believe this is an incorrect editorial bit that should be updated, since the list shifts back to a previous indentation.<span style='font-size:10.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal>All in all, we’re left with the understanding that, no, this extension is not allowed (with the exception that if Microsoft were to be the Applicant, it would be allowed).<span style='font-size:10.0pt'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal>With this breakdown, we’re left with a few questions:<span style='font-size:10.0pt'><o:p></o:p></span></p></div></div><ol start=1 type=1><li class=MsoListParagraph style='mso-list:l1 level1 lfo2'>Have other CAs run into the same issue?<span style='font-size:10.0pt'><o:p></o:p></span></li><li class=MsoListParagraph style='mso-list:l1 level1 lfo2'>Do other CAs share the same conclusion?<span style='font-size:10.0pt'><o:p></o:p></span></li><li class=MsoListParagraph style='mso-list:l1 level1 lfo2'>If this does appear to be an issue, should an extension by the platform of one of our Certificate Consumers, be specifically added as an allowed extension?<span style='font-size:10.0pt'><o:p></o:p></span></li></ol><div><div><p class=MsoNormal>Regards,<br><br>Martijn<br>Sectigo<span style='font-size:10.0pt'><o:p></o:p></span></p></div></div></div></blockquote></div></div><div><p class=MsoNormal> <span style='font-size:10.0pt'><o:p></o:p></span></p></div></div></div><div><p class=MsoNormal>_______________________________________________<br>Smcwg-public mailing list<br><a href="mailto:Smcwg-public@cabforum.org">Smcwg-public@cabforum.org</a><br><a href="https://url.avanan.click/v2/___https:/lists.cabforum.org/mailman/listinfo/smcwg-public___.YXAzOmRpZ2ljZXJ0OmE6bzpmZDdkNmUwYWRjN2NiYWJhZWE2NGI2MmNmYWExODIzYzo2OjVmMTI6MmVkNDVhZTJjMWQ0ZGU2MjI2YjExOTExNjczYjBhMmJjZjdlMjk3OGQ4OTNmNTJjYmJkY2JkYmI0OGNhZmIzMjpoOkY" title="Protected by Avanan: https://lists.cabforum.org/mailman/listinfo/smcwg-public">https://lists.cabforum.org/mailman/listinfo/smcwg-public</a><span style='font-size:10.0pt'><o:p></o:p></span></p></div></div></blockquote></div><div><p class=MsoNormal> <span style='font-size:10.0pt'><o:p></o:p></span></p></div></div></div></div></div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'>_______________________________________________<br>Smcwg-public mailing list<br></span><a href="mailto:Smcwg-public@cabforum.org"><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'>Smcwg-public@cabforum.org</span></a><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'><br></span><a href="https://url.avanan.click/v2/___https:/lists.cabforum.org/mailman/listinfo/smcwg-public___.YXAzOmRpZ2ljZXJ0OmE6bzpmZDdkNmUwYWRjN2NiYWJhZWE2NGI2MmNmYWExODIzYzo2OjlmZDY6NzQ4ODQ4YjNlZWU0YTc5ZTFiNjExZDY0NDk4YjQyZTAyYWIwZGQ0YmM3OTdmOTRmMjJiY2YzZmZjM2Q2M2M0NTpoOkY" title="Protected by Avanan: https://lists.cabforum.org/mailman/listinfo/smcwg-public"><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'>https://lists.cabforum.org/mailman/listinfo/smcwg-public</span></a><o:p></o:p></p></div></blockquote></div><p class=MsoNormal><o:p> </o:p></p></div></div></div></body></html>