<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:"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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:12.0pt;
font-family:"Aptos",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Aptos",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=blue vlink=purple style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt'>SSL.com will endorse this ballot. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>Regards,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>Tom<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>SSL.com<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> Validation <validation-bounces@cabforum.org> <b>On Behalf Of </b>Paul van Brouwershaven via Validation<br><b>Sent:</b> Friday, September 6, 2024 8:22 AM<br><b>To:</b> CABforum3 <validation@cabforum.org><br><b>Subject:</b> Re: [cabf_validation] Section 7.1.2.10.5 CA Certificate Certificate Policies for cross signing certificates<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:11.0pt;color:black'>Following yesterday's discussion in the validation subcommittee teleconference, we are now seeking two members to endorse the ballot. Feedback is also welcome, either here or on the pull request.<o:p></o:p></span></p></div><div style='margin-left:30.0pt'><p class=MsoNormal><span style='font-size:11.0pt;color:black'>### Purpose of the Ballot<o:p></o:p></span></p></div><div style='margin-left:30.0pt'><p class=MsoNormal><span style='font-size:11.0pt;color:black'><o:p> </o:p></span></p></div><div style='margin-left:30.0pt'><p class=MsoNormal><span style='font-size:11.0pt;color:black'>This ballot duplicates the content of section 7.1.2.10.5 (CA Certificate Certificate Policies) into section 7.1.2.2 (Cross-Certified Subordinate CA Certificate Profile) as section 7.1.2.2.6 (Cross-Certified Subordinate CA Certificate Certificate Policies), modifying the requirement from "MUST contain exactly one Reserved Certificate Policy Identifier" to "MUST include at least one Reserved Certificate Policy Identifier" to allow the inclusion of multiple Reserved Certificate Policy Identifiers in a Cross-Certified Subordinate CA Certificate.<o:p></o:p></span></p></div><div style='margin-left:30.0pt'><p class=MsoNormal><span style='font-size:11.0pt;color:black'><o:p> </o:p></span></p></div><div style='margin-left:30.0pt'><p class=MsoNormal><span style='font-size:11.0pt;color:black'>The following motion has been proposed by Paul van Brouwershaven (Entrust) and endorsed by XXX (XXX) and XXX (XXX).<o:p></o:p></span></p></div><div style='margin-left:30.0pt'><p class=MsoNormal><span style='font-size:11.0pt;color:black'><o:p> </o:p></span></p></div><div style='margin-left:30.0pt'><p class=MsoNormal><span style='font-size:11.0pt;color:black'>GitHub pull request for this ballot: <a href="https://github.com/cabforum/servercert/pull/544">https://github.com/cabforum/servercert/pull/544</a> <o:p></o:p></span></p></div><div style='margin-left:30.0pt'><p class=MsoNormal><span style='font-size:11.0pt;color:black'><o:p> </o:p></span></p></div><div style='margin-left:30.0pt'><p class=MsoNormal><span style='font-size:11.0pt;color:black'>### Motion begins<o:p></o:p></span></p></div><div style='margin-left:30.0pt'><p class=MsoNormal><span style='font-size:11.0pt;color:black'><o:p> </o:p></span></p></div><div style='margin-left:30.0pt'><p class=MsoNormal><span style='font-size:11.0pt;color:black'>MODIFY the "Baseline Requirements for the Issuance and Management of Publicly-Trusted TLS Server Certificates" ("TLS Baseline Requirements") based on Version 2.0.6 as specified in the following redline:<o:p></o:p></span></p></div><div style='margin-left:30.0pt'><p class=MsoNormal><span style='font-size:11.0pt;color:black'><o:p> </o:p></span></p></div><div style='margin-left:30.0pt'><p class=MsoNormal><span style='font-size:11.0pt;color:black'><a href="https://github.com/cabforum/servercert/compare/929d9b4a1ed1f13f92f6af672ad6f6a2153b8230...89f80028b40ce6a1a5c52b406d37e5534460a1a1">https://github.com/cabforum/servercert/compare/929d9b4a1ed1f13f92f6af672ad6f6a2153b8230...89f80028b40ce6a1a5c52b406d37e5534460a1a1</a><o:p></o:p></span></p></div><div style='margin-left:30.0pt'><p class=MsoNormal><span style='font-size:11.0pt;color:black'><o:p> </o:p></span></p></div><div style='margin-left:30.0pt'><p class=MsoNormal><span style='font-size:11.0pt;color:black'>### Motion ends<o:p></o:p></span></p></div><div style='margin-left:30.0pt'><p class=MsoNormal><span style='font-size:11.0pt;color:black'><o:p> </o:p></span></p></div><div style='margin-left:30.0pt'><p class=MsoNormal><span style='font-size:11.0pt;color:black'>This ballot proposes a Final Maintenance Guideline. The procedure for approval of this ballot is as follows:<o:p></o:p></span></p></div><div style='margin-left:30.0pt'><p class=MsoNormal><span style='font-size:11.0pt;color:black'><o:p> </o:p></span></p></div><div style='margin-left:30.0pt'><p class=MsoNormal><span style='font-size:11.0pt;color:black'>Discussion (7+ days)<o:p></o:p></span></p></div><div style='margin-left:30.0pt'><p class=MsoNormal><span style='font-size:11.0pt;color:black'><o:p> </o:p></span></p></div><div style='margin-left:30.0pt'><p class=MsoNormal><span style='font-size:11.0pt;color:black'>- Start time: TBC<o:p></o:p></span></p></div><div style='margin-left:30.0pt'><p class=MsoNormal><span style='font-size:11.0pt;color:black'>- End time: TBC<o:p></o:p></span></p></div><div style='margin-left:30.0pt'><p class=MsoNormal><span style='font-size:11.0pt;color:black'><o:p> </o:p></span></p></div><div style='margin-left:30.0pt'><p class=MsoNormal><span style='font-size:11.0pt;color:black'>Vote for approval (7 days)<o:p></o:p></span></p></div><div style='margin-left:30.0pt'><p class=MsoNormal><span style='font-size:11.0pt;color:black'> <o:p></o:p></span></p></div><div style='margin-left:30.0pt'><p class=MsoNormal><span style='font-size:11.0pt;color:black'>- Start time: TBC<o:p></o:p></span></p></div><div style='margin-left:30.0pt'><p class=MsoNormal><span style='font-size:11.0pt;color:black'>- End time: TBC<o:p></o:p></span></p></div><div class=MsoNormal align=center style='text-align:center'><hr size=2 width="98%" align=center></div><div id=divRplyFwdMsg><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'> Validation <<a href="mailto:validation-bounces@cabforum.org">validation-bounces@cabforum.org</a>> on behalf of Paul van Brouwershaven via Validation <<a href="mailto:validation@cabforum.org">validation@cabforum.org</a>><br><b>Sent:</b> Thursday, September 5, 2024 16:40<br><b>To:</b> CABforum3 <<a href="mailto:validation@cabforum.org">validation@cabforum.org</a>><br><b>Subject:</b> [EXTERNAL] [cabf_validation] Section 7.1.2.10.5 CA Certificate Certificate Policies for cross signing certificates</span> <o:p></o:p></p><div><p class=MsoNormal> <o:p></o:p></p></div></div><div><div><p class=MsoNormal style='mso-line-height-alt:.75pt'><span style='font-size:1.0pt;color:white'>We would like to clarify the following requirement in section 7.</span><span style='font-size:1.0pt;font-family:"Arial",sans-serif;color:white'> </span><span style='font-size:1.0pt;color:white'>1.</span><span style='font-size:1.0pt;font-family:"Arial",sans-serif;color:white'> </span><span style='font-size:1.0pt;color:white'>2.</span><span style='font-size:1.0pt;font-family:"Arial",sans-serif;color:white'> </span><span style='font-size:1.0pt;color:white'>10.</span><span style='font-size:1.0pt;font-family:"Arial",sans-serif;color:white'> </span><span style='font-size:1.0pt;color:white'>5 CA Certificate Certificate Policies, specifically for cross signing certificates. RFC 5280 states that you can have one CertPolicyId within the PolicyInformation, see below:</span><span style='font-size:1.0pt;font-family:"Arial",sans-serif;color:white'> </span><span style='font-size:1.0pt;color:white'><o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:11.0pt;color:black'>We would like to clarify the following requirement in section 7.1.2.10.5 CA Certificate Certificate Policies, specifically for cross signing certificates.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'>RFC 5280 states that you can have one CertPolicyId within the PolicyInformation, see below:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'><o:p> </o:p></span></p><div style='margin-left:30.0pt'><p class=MsoNormal><i><span style='font-size:9.0pt;font-family:"Courier New";color:black'>certificatePolicies ::= SEQUENCE SIZE (1..MAX) OF PolicyInformation</span></i><span style='font-size:9.0pt;font-family:"Courier New";color:black'><o:p></o:p></span></p></div><div style='margin-left:30.0pt'><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Courier New";color:black'><o:p> </o:p></span></p></div><div style='margin-left:30.0pt'><p class=MsoNormal><i><span style='font-size:9.0pt;font-family:"Courier New";color:black'>PolicyInformation ::= SEQUENCE {</span></i><span style='font-size:9.0pt;font-family:"Courier New";color:black'><o:p></o:p></span></p></div><div style='margin-left:30.0pt'><p class=MsoNormal><i><span style='font-size:9.0pt;font-family:"Courier New";color:black'> policyIdentifier <b>CertPolicyId</b>,</span></i><span style='font-size:9.0pt;font-family:"Courier New";color:black'><o:p></o:p></span></p></div><div style='margin-left:30.0pt'><p class=MsoNormal><i><span style='font-size:9.0pt;font-family:"Courier New";color:black'> policyQualifiers SEQUENCE SIZE (1..MAX) OF</span></i><span style='font-size:9.0pt;font-family:"Courier New";color:black'><o:p></o:p></span></p></div><div style='margin-left:30.0pt'><p class=MsoNormal><i><span style='font-size:9.0pt;font-family:"Courier New";color:black'> PolicyQualifierInfo OPTIONAL }</span></i><span style='font-size:9.0pt;font-family:"Courier New";color:black'><o:p></o:p></span></p></div><div style='margin-left:30.0pt'><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Courier New";color:black'><o:p> </o:p></span></p></div><div style='margin-left:30.0pt'><p class=MsoNormal><b><i><span style='font-size:9.0pt;font-family:"Courier New";color:black'>CertPolicyId </span></i></b><i><span style='font-size:9.0pt;font-family:"Courier New";color:black'>::= OBJECT IDENTIFIER</span></i><span style='font-size:9.0pt;font-family:"Courier New";color:black'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;color:black'><o:p> </o:p></span></p></div><p class=MsoNormal><span style='font-size:11.0pt;color:black'>Section 7.1.2.10.5 of the TLS BR states for the policyIdentifier:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'><o:p> </o:p></span></p><div style='margin-left:30.0pt'><p class=MsoNormal><i><span style='font-size:11.0pt;color:black'>The CA MUST include <b><u>at least one</u></b> Reserved Certificate Policy Identifier (see Section 7.1.6.1) associated with the given Subscriber Certificate type (see Section 7.1.2.7.1) directly or transitively issued by this Certificate.</span></i><span style='font-size:11.0pt;color:black'><o:p></o:p></span></p></div><div style='margin-left:30.0pt'><p class=MsoNormal><span style='font-size:11.0pt;color:black'><o:p> </o:p></span></p></div><p class=MsoNormal><span style='font-size:11.0pt;color:black'>This 'at least one' seems to contradict RFC 5280 which indicates that we can only have one policyIdentifier in the PolicyInformation sequence.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'>Then at the bottom of this section the TLS BRs states that entire certificate policies extension MUST contain exactly one Reserved Certificate Policy Identifier:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'><o:p> </o:p></span></p><div style='margin-left:30.0pt'><p class=MsoNormal><i><span style='font-size:11.0pt;color:black'>Regardless of the order of PolicyInformation values, the Certificate Policies extension <b><u>MUST contain exactly one</u></b> Reserved Certificate Policy Identifier.</span></i><span style='font-size:11.0pt;color:black'><o:p></o:p></span></p></div><div style='margin-left:30.0pt'><p class=MsoNormal><span style='font-size:11.0pt;color:black'><o:p> </o:p></span></p></div><p class=MsoNormal><span style='font-size:11.0pt;color:black'>While we can repeat the PolicyInformation within the certificatePolicies extension does this mean that CAs are prohibited from issuing a cross signing certificate (from a multi-purpose root to another multi-purpose root) with policy contrains that include DV, OV and EV reserved certificate policy identifiers. If our reading of this section is correct, this would mean that CAs need to issue three seperate cross signing certificates in that case.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'>Paul<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'><o:p> </o:p></span></p><p class=MsoNormal><i>Any email and files/attachments transmitted with it are intended solely for the use of the individual or entity to whom they are addressed. If this message has been sent to you in error, you must not copy, distribute or disclose of the information it contains. <u>Please notify Entrust immediately and delete the message from your system.</u></i> <o:p></o:p></p></div></div></body></html>