<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Hi Bruce,<div><br></div><div>I agree, but don’t see anything conceptualized in the current TBRs which would represent this. I’m not sure how to fully capture this simply. For part of the prerequisites we’re describing — though I’m pretty sure it’s not a good idea — we could possibly add this into the hypothetical clarifying language to-be-added to the new Section 7.1.2.2.6 with something along the lines of “the CA Certificate whose Subject Name and Subject Public Key Information are being signed as a Cross-Certified Subordinate CA MUST contain a basicConstraints:pathLenConstraint and the value of the pathLenConstraint MUST NOT be `0`”. </div><div><br></div><div>However, that kind of requirement doesn’t prohibit such a CA Certificate from issuing Subscriber Certificates and I don’t know of a technical means of representing that a CA Certificate doesn’t issue end-entity certificates and so should not be used by relying parties in chain validation as the issuing CA of a leaf. Limiting it to Root CA Certificates was the best I could come up with that doesn’t scope creep this change substantially, but hopefully someone else sees something I don’t. If nothing else, we could probably add that language into this same new Section as a “If a Cross-Certified Subordinate CA contains more than one Reserved Certificate Policy Identifier, it MUST NOT sign Subscriber Certificates” sort of caveat/condition.</div><div><br></div><div>Thanks,</div><div>-Clint<br id="lineBreakAtBeginningOfMessage"><div><br><blockquote type="cite"><div>On Sep 6, 2024, at 1:18 PM, Bruce Morton <Bruce.Morton@entrust.com> wrote:</div><br class="Apple-interchange-newline"><div><meta charset="UTF-8"><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;">Hi Clint,<o:p></o:p></span></div><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;"><o:p> </o:p></span></div><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;">I think the requirement should apply to a certificate to a CA, which can issue CA certificates. I’m not sure of the right terminology, but I categorize this as a Root-to-Root CA or a Root-to-Intermediate CA Certificate. It would not apply to a CA certificate where the CA issues Subscriber certificates.<o:p></o:p></span></div><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;"><o:p> </o:p></span></div><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;"><o:p> </o:p></span></div><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;">Bruce.<o:p></o:p></span></div><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;"><o:p> </o:p></span></div><div><div style="border-width: 1pt medium medium; border-style: solid none none; border-color: rgb(225, 225, 225) currentcolor currentcolor; border-image: none; padding: 3pt 0in 0in;"><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><b><span style="font-size: 11pt; font-family: Calibri, sans-serif;">From:</span></b><span style="font-size: 11pt; font-family: Calibri, sans-serif;"><span class="Apple-converted-space"> </span>Validation <validation-bounces@cabforum.org><span class="Apple-converted-space"> </span><b>On Behalf Of<span class="Apple-converted-space"> </span></b>Clint Wilson via Validation<br><b>Sent:</b><span class="Apple-converted-space"> </span>Friday, September 6, 2024 2:45 PM<br><b>To:</b><span class="Apple-converted-space"> </span>Paul van Brouwershaven <Paul.vanBrouwershaven@entrust.com>; CA/Browser Forum Validation SC List <validation@cabforum.org><br><b>Subject:</b><span class="Apple-converted-space"> </span>[EXTERNAL] Re: [cabf_validation] Section 7.1.2.10.5 CA Certificate Certificate Policies for cross signing certificates<o:p></o:p></span></div></div></div><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><o:p> </o:p></div><div><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;">Hi Paul,<o:p></o:p></div></div><div><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><o:p> </o:p></div></div><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;">One concern I have with this change is its impact on the cross-certification of subordinate CAs which directly issue end-entity TLS certificates. That is, I think it appropriate to maintain the requirement/limitation that only one Reserved Certificate Policy Identifier be included in the Cross-Certified Subordinate CA Certificate where the CA Certificate being signed/certified is a Subordinate CA Certificate as opposed to a Root CA Certificate.<o:p></o:p></div><div><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><o:p> </o:p></div><div><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;">Since the introduction to this Profile in Section 7.1.2.2 states that the Profile is the same regardless of whether the “source” CA Certificate is a Root CA Certificate or a Subordinate CA Certificate, I<span class="Apple-converted-space"> </span><i>think</i><span class="Apple-converted-space"> </span>this newly added Section 7.1.2.2.6 would need to indicate clearly its scope of applicability against Cross-Certified Subordinate CA Certificate which are the result of issuing a CA Certificate using the same Subject Name and Subject Public Key Information as an existing Root CA Certificate.<o:p></o:p></div></div><div><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><o:p> </o:p></div></div><div><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;">It also seems like it may be helpful to clarify that the Certificate Policies extension defined in this newly added Section 7.1.2.2.6 needs to be compatible between the Cross-Certified Subordinate CA and its Issuing CA (though, perhaps, obvious, this would also help ensure that the separation of pre- and post-SC-062 CA Certificates is maintained, at least in the cases where the `anyPolicy` Policy Identifier is not used). I’m not entirely sure this is necessary, as I suspect it’s required elsewhere within Section 7, but I couldn’t find it in a quick search so thought I’d mention it.<o:p></o:p></div></div><div><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><o:p> </o:p></div></div><div><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;">Thanks!<o:p></o:p></div></div><div><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;">-Clint<o:p></o:p></div></div><div><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><o:p> </o:p></div></div><div><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><o:p> </o:p></div><div><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><br><br><o:p></o:p></div><blockquote style="margin-top: 5pt; margin-bottom: 5pt;"><div><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;">On Sep 6, 2024, at 6:21<span style="font-family: Arial, sans-serif;"> </span>AM, Paul van Brouwershaven via Validation <<a href="mailto:validation@cabforum.org" style="color: blue; text-decoration: underline;">validation@cabforum.org</a>> wrote:<o:p></o:p></div></div><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><o:p> </o:p></div><div><div><p class="MsoNormal" style="margin: 0in 0in 12pt; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;">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: 30pt; font-variant-caps: normal; text-align: start; -webkit-text-stroke-width: 0px; word-spacing: 0px;"><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;">### Purpose of the Ballot<o:p></o:p></span></div></div><div style="margin-left: 30pt; font-variant-caps: normal; text-align: start; -webkit-text-stroke-width: 0px; word-spacing: 0px;"><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;"><o:p> </o:p></span></div></div><div style="margin-left: 30pt; font-variant-caps: normal; text-align: start; -webkit-text-stroke-width: 0px; word-spacing: 0px;"><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;">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></div></div><div style="margin-left: 30pt; font-variant-caps: normal; text-align: start; -webkit-text-stroke-width: 0px; word-spacing: 0px;"><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;"><o:p> </o:p></span></div></div><div style="margin-left: 30pt; font-variant-caps: normal; text-align: start; -webkit-text-stroke-width: 0px; word-spacing: 0px;"><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;">The following motion has been proposed by Paul van Brouwershaven (Entrust) and endorsed by XXX (XXX) and XXX (XXX).<o:p></o:p></span></div></div><div style="margin-left: 30pt; font-variant-caps: normal; text-align: start; -webkit-text-stroke-width: 0px; word-spacing: 0px;"><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;"><o:p> </o:p></span></div></div><div style="margin-left: 30pt; font-variant-caps: normal; text-align: start; -webkit-text-stroke-width: 0px; word-spacing: 0px;"><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;">GitHub pull request for this ballot:<span class="apple-converted-space"> </span><a href="https://github.com/cabforum/servercert/pull/544" style="color: blue; text-decoration: underline;">https://github.com/cabforum/servercert/pull/544</a> <o:p></o:p></span></div></div><div style="margin-left: 30pt; font-variant-caps: normal; text-align: start; -webkit-text-stroke-width: 0px; word-spacing: 0px;"><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;"><o:p> </o:p></span></div></div><div style="margin-left: 30pt; font-variant-caps: normal; text-align: start; -webkit-text-stroke-width: 0px; word-spacing: 0px;"><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;">### Motion begins<o:p></o:p></span></div></div><div style="margin-left: 30pt; font-variant-caps: normal; text-align: start; -webkit-text-stroke-width: 0px; word-spacing: 0px;"><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;"><o:p> </o:p></span></div></div><div style="margin-left: 30pt; font-variant-caps: normal; text-align: start; -webkit-text-stroke-width: 0px; word-spacing: 0px;"><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;">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></div></div><div style="margin-left: 30pt; font-variant-caps: normal; text-align: start; -webkit-text-stroke-width: 0px; word-spacing: 0px;"><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;"><o:p> </o:p></span></div></div><div style="margin-left: 30pt; font-variant-caps: normal; text-align: start; -webkit-text-stroke-width: 0px; word-spacing: 0px;"><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;"><a href="https://github.com/cabforum/servercert/compare/929d9b4a1ed1f13f92f6af672ad6f6a2153b8230...89f80028b40ce6a1a5c52b406d37e5534460a1a1" style="color: blue; text-decoration: underline;">https://github.com/cabforum/servercert/compare/929d9b4a1ed1f13f92f6af672ad6f6a2153b8230...89f80028b40ce6a1a5c52b406d37e5534460a1a1</a><o:p></o:p></span></div></div><div style="margin-left: 30pt; font-variant-caps: normal; text-align: start; -webkit-text-stroke-width: 0px; word-spacing: 0px;"><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;"><o:p> </o:p></span></div></div><div style="margin-left: 30pt; font-variant-caps: normal; text-align: start; -webkit-text-stroke-width: 0px; word-spacing: 0px;"><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;">### Motion ends<o:p></o:p></span></div></div><div style="margin-left: 30pt; font-variant-caps: normal; text-align: start; -webkit-text-stroke-width: 0px; word-spacing: 0px;"><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;"><o:p> </o:p></span></div></div><div style="margin-left: 30pt; font-variant-caps: normal; text-align: start; -webkit-text-stroke-width: 0px; word-spacing: 0px;"><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;">This ballot proposes a Final Maintenance Guideline. The procedure for approval of this ballot is as follows:<o:p></o:p></span></div></div><div style="margin-left: 30pt; font-variant-caps: normal; text-align: start; -webkit-text-stroke-width: 0px; word-spacing: 0px;"><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;"><o:p> </o:p></span></div></div><div style="margin-left: 30pt; font-variant-caps: normal; text-align: start; -webkit-text-stroke-width: 0px; word-spacing: 0px;"><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;">Discussion (7+ days)<o:p></o:p></span></div></div><div style="margin-left: 30pt; font-variant-caps: normal; text-align: start; -webkit-text-stroke-width: 0px; word-spacing: 0px;"><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;"><o:p> </o:p></span></div></div><div style="margin-left: 30pt; font-variant-caps: normal; text-align: start; -webkit-text-stroke-width: 0px; word-spacing: 0px;"><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;">- Start time: TBC<o:p></o:p></span></div></div><div style="margin-left: 30pt; font-variant-caps: normal; text-align: start; -webkit-text-stroke-width: 0px; word-spacing: 0px;"><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;">- End time: TBC<o:p></o:p></span></div></div><div style="margin-left: 30pt; font-variant-caps: normal; text-align: start; -webkit-text-stroke-width: 0px; word-spacing: 0px;"><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;"><o:p> </o:p></span></div></div><div style="margin-left: 30pt; font-variant-caps: normal; text-align: start; -webkit-text-stroke-width: 0px; word-spacing: 0px;"><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;">Vote for approval (7 days)<o:p></o:p></span></div></div><div style="margin-left: 30pt; font-variant-caps: normal; text-align: start; -webkit-text-stroke-width: 0px; word-spacing: 0px;"><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;"> <o:p></o:p></span></div></div><div style="margin-left: 30pt; font-variant-caps: normal; text-align: start; -webkit-text-stroke-width: 0px; word-spacing: 0px;"><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;">- Start time: TBC<o:p></o:p></span></div></div><div style="margin-left: 30pt; font-variant-caps: normal; text-align: start; -webkit-text-stroke-width: 0px; word-spacing: 0px;"><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;">- End time: TBC<o:p></o:p></span></div></div><div class="MsoNormal" align="center" style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif; text-align: center;"><hr size="2" width="803" align="center" style="width: 601.95pt;"></div><div id="divRplyFwdMsg"><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><b><span style="font-size: 11pt; font-family: Calibri, sans-serif;">From:</span></b><span class="apple-converted-space"><span style="font-size: 11pt; font-family: Calibri, sans-serif;"> </span></span><span style="font-size: 11pt; font-family: Calibri, sans-serif;">Validation <<a href="mailto:validation-bounces@cabforum.org" style="color: blue; text-decoration: underline;">validation-bounces@cabforum.org</a>> on behalf of Paul van Brouwershaven via Validation <<a href="mailto:validation@cabforum.org" style="color: blue; text-decoration: underline;">validation@cabforum.org</a>><br><b>Sent:</b><span class="apple-converted-space"> </span>Thursday, September 5, 2024 16:40<br><b>To:</b><span class="apple-converted-space"> </span>CABforum3 <<a href="mailto:validation@cabforum.org" style="color: blue; text-decoration: underline;">validation@cabforum.org</a>><br><b>Subject:</b><span class="apple-converted-space"> </span>[EXTERNAL] [cabf_validation] Section 7.1.2.10.5 CA Certificate Certificate Policies for cross signing certificates</span><span style="font-size: 9pt; font-family: Helvetica, sans-serif;"><o:p></o:p></span></div><div><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 9pt; font-family: Helvetica, sans-serif;"> <o:p></o:p></span></div></div></div><div><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;">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></div><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;"><o:p> </o:p></span></div><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;">RFC 5280 states that you can have one CertPolicyId within the PolicyInformation, see below:<o:p></o:p></span></div><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;"><o:p> </o:p></span></div><div style="margin-left: 30pt;"><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><i><span style="font-size: 9pt; font-family: "Courier New";">certificatePolicies ::= SEQUENCE SIZE (1..MAX) OF PolicyInformation</span></i><span style="font-size: 9pt; font-family: "Courier New";"><o:p></o:p></span></div></div><div style="margin-left: 30pt;"><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 9pt; font-family: "Courier New";"><o:p> </o:p></span></div></div><div style="margin-left: 30pt;"><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><i><span style="font-size: 9pt; font-family: "Courier New";">PolicyInformation ::= SEQUENCE {</span></i><span style="font-size: 9pt; font-family: "Courier New";"><o:p></o:p></span></div></div><div style="margin-left: 30pt;"><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><i><span style="font-size: 9pt; font-family: "Courier New";"> policyIdentifier <span class="apple-converted-space"> </span><b>CertPolicyId</b>,</span></i><span style="font-size: 9pt; font-family: "Courier New";"><o:p></o:p></span></div></div><div style="margin-left: 30pt;"><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><i><span style="font-size: 9pt; font-family: "Courier New";"> policyQualifiers SEQUENCE SIZE (1..MAX) OF</span></i><span style="font-size: 9pt; font-family: "Courier New";"><o:p></o:p></span></div></div><div style="margin-left: 30pt;"><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><i><span style="font-size: 9pt; font-family: "Courier New";"> PolicyQualifierInfo OPTIONAL }</span></i><span style="font-size: 9pt; font-family: "Courier New";"><o:p></o:p></span></div></div><div style="margin-left: 30pt;"><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 9pt; font-family: "Courier New";"><o:p> </o:p></span></div></div><div style="margin-left: 30pt;"><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><b><i><span style="font-size: 9pt; font-family: "Courier New";">CertPolicyId<span class="apple-converted-space"> </span></span></i></b><i><span style="font-size: 9pt; font-family: "Courier New";">::= OBJECT IDENTIFIER</span></i><span style="font-size: 9pt; font-family: "Courier New";"><o:p></o:p></span></div></div><div><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;"><o:p> </o:p></span></div></div><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;">Section 7.1.2.10.5 of the TLS BR states for the policyIdentifier:<o:p></o:p></span></div><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;"><o:p> </o:p></span></div><div style="margin-left: 30pt;"><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><i><span style="font-size: 11pt;">The CA MUST include<span class="apple-converted-space"> </span><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: 11pt;"><o:p></o:p></span></div></div><div style="margin-left: 30pt;"><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;"><o:p> </o:p></span></div></div><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;">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></div><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;"><o:p> </o:p></span></div><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;">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></div><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;"><o:p> </o:p></span></div><div style="margin-left: 30pt;"><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><i><span style="font-size: 11pt;">Regardless of the order of PolicyInformation values, the Certificate Policies extension<span class="apple-converted-space"> </span><b><u>MUST contain exactly one</u></b> Reserved Certificate Policy Identifier.</span></i><span style="font-size: 11pt;"><o:p></o:p></span></div></div><div style="margin-left: 30pt;"><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;"><o:p> </o:p></span></div></div><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;">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></div><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;"><o:p> </o:p></span></div><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;">Paul<o:p></o:p></span></div><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;"><o:p> </o:p></span></div><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;"><o:p> </o:p></span></div><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;"><o:p> </o:p></span></div><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><i><span style="font-size: 9pt; font-family: Helvetica, sans-serif;">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.<span class="apple-converted-space"> </span><u>Please notify Entrust immediately and delete the message from your system.</u></span></i><span style="font-size: 9pt; font-family: Helvetica, sans-serif;"><o:p></o:p></span></div></div><div style="margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 9pt; font-family: Helvetica, sans-serif;">_______________________________________________<br>Validation mailing list<br><a href="mailto:Validation@cabforum.org" style="color: blue; text-decoration: underline;">Validation@cabforum.org</a><br><a href="https://lists.cabforum.org/mailman/listinfo/validation" style="color: blue; text-decoration: underline;">https://lists.cabforum.org/mailman/listinfo/validation</a></span></div></div></blockquote></div></div></div></div></div></blockquote></div><br></div></body></html>