<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 12px; font-family: Arial, sans-serif; "><div><div><div>GlobalSign Votes YES.</div><div><div><br></div><p></p></div></div></div><div><br></div><span id="OLK_SRC_BODY_SECTION"><div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><span style="font-weight:bold">From: </span> Steve Roylance <<a href="mailto:steve.roylance@globalsign.com">steve.roylance@globalsign.com</a>><br><span style="font-weight:bold">Date: </span> Monday, 22 July 2013 11:28<br><span style="font-weight:bold">To: </span> <<a href="mailto:public@cabforum.org">public@cabforum.org</a>><br><span style="font-weight:bold">Cc: </span> Ben Wilson <<a href="mailto:ben@digicert.com">ben@digicert.com</a>>, Gervase Markham <<a href="mailto:gerv@mozilla.org">gerv@mozilla.org</a>>, 'Stephen Davidson' <<a href="mailto:S.Davidson@quovadisglobal.com">S.Davidson@quovadisglobal.com</a>><br><span style="font-weight:bold">Subject: </span> Ballot 105 – Technical Constraints for Subordinate Certificate Authorities yielding broader and safer PKI adoption.<br></div><div><br></div><div><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div style="color: rgb(0, 0, 0); font-family: Arial, sans-serif; font-size: 12px; "><div>Dear all,</div><div><br></div><div>As we made some slight modifications to the Wiki version last week to add clarity and address final concerns I'm sending out the agreed modified version as an e-mail (which matches the Wiki) so that people can vote based on the e-mail version for their own records.</div><div><br></div><div>Steve</div><div><br></div><div><div><br></div></div></div><span id="OLK_SRC_BODY_SECTION"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><p class="line867" style="color: rgb(0, 0, 0); font-family: Arial, 'Lucida Grande', sans-serif; background-color: rgb(255, 255, 255); "><strong><font size="4">Ballot 105 – Technical Constraints for Subordinate Certificate Authorities yielding broader and safer PKI adoption.</font></strong></p><p class="line867" style="color: rgb(0, 0, 0); font-family: Arial, 'Lucida Grande', sans-serif; font-size: 12px; background-color: rgb(255, 255, 255); "><span class="anchor" id="line-3"></span></p><p class="line874" style="color: rgb(0, 0, 0); font-family: Arial, 'Lucida Grande', sans-serif; font-size: 12px; background-color: rgb(255, 255, 255); ">Steve Roylance made the following motion, and Gervase Markham from Mozilla and Stephen Davidson from Quovadis endorsed it:<span class="anchor" id="line-4"></span><span class="anchor" id="line-5"></span></p><p class="line867" style="color: rgb(0, 0, 0); font-family: Arial, 'Lucida Grande', sans-serif; font-size: 12px; background-color: rgb(255, 255, 255); "><strong>Motion Begins</strong><span class="anchor" id="line-6"></span><span class="anchor" id="line-7"></span></p><p class="line874" style="color: rgb(0, 0, 0); font-family: Arial, 'Lucida Grande', sans-serif; font-size: 12px; background-color: rgb(255, 255, 255); ">EFFECTIVE IMMEDIATELY, this ballot provides clarity to the language covering external audits for Subordinate CAs, removing ambiguity as well as providing better alignment of the Baseline Requirements to the Mozilla CA Root program where the subject is already covered and accepted by the wider PKI community. In addition, the proposal sets out to aid wider and broader PKI adoption by Subordinate CAs by defining the use of Technical Constraints and highlighting how additional barriers to adoption within the guidelines can be optional when using Name Constraints, specifically the requirement for ‘OCSP Good’ responses originally proposed in Ballot 100. We propose amending the Baseline Requirements Guidelines as follows:<span class="anchor" id="line-8"></span><span class="anchor" id="line-9"></span></p><p class="line867" style="background-color: rgb(255, 255, 255); "></p><div><p class="line867"><font face="Arial,Lucida Grande,sans-serif"><b>Section 1 – Scope <i>(Adding scope)</i></b></font></p></div><blockquote style="margin:0 0 0 40px; border:none; padding:0px;"><p class="line867"><span style="font-family: Arial, 'Lucida Grande', sans-serif; ">These Requirements are applicable to all Certification Authorities within a chain of trust. They are to be flowed down from the Root Certification Authority through successive Subordinate Certification Authorities.</span></p></blockquote><div><p class="line867"><font face="Arial,Lucida Grande,sans-serif"><b>Section 4 – Definitions <i>(Additional Definition)</i></b></font></p></div><blockquote style="margin:0 0 0 40px; border:none; padding:0px;"><p class="line867"><font face="Arial,Lucida Grande,sans-serif">Technically Constrained Subordinate CA Certificate: A Subordinate CA certificate which uses a combination of Extended Key Usage settings and Name Constraint settings to limit the scope within which the Subordinate CA Certificate may issue Subscriber or additional Subordinate CA Certificates.</font></p></blockquote><div><p class="line867"><font face="Arial,Lucida Grande,sans-serif"><b>Section 9.2.7 Other Subject Attributes<i> (Moving to 9.2.8)</i></b></font></p></div><blockquote style="margin:0 0 0 40px; border:none; padding:0px;"><p class="line867"><font face="Arial,Lucida Grande,sans-serif"><b>Section 9.2.7 Subject Information – Subordinate CA Certificates <i>(Adding a new section)</i></b></font></p><p class="line867"><span style="font-family: Arial, 'Lucida Grande', sans-serif; ">By issuing a Subordinate CA Certificate, the CA represents that it followed the procedure set forth in its Certificate Policy and/or Certification Practice Statement to verify that, as of the Certificate’s issuance date, all of the Subject Information was accurate.</span></p></blockquote><div><p class="line867"><font face="Arial,Lucida Grande,sans-serif"><b>Section 9.4 Validity Period <i>(Clarifying the Validity Period for Subscriber Certificates)</i></b></font></p></div><p class="line867"><font face="Arial,Lucida Grande,sans-serif"><i>Was:-</i></font></p><blockquote style="margin:0 0 0 40px; border:none; padding:0px;"><p class="line867"><font face="Arial,Lucida Grande,sans-serif"><b>9.4 Validity Period</b></font></p></blockquote><p></p></div></span><span id="OLK_SRC_BODY_SECTION"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><p class="line867" style="background-color: rgb(255, 255, 255); "></p><blockquote style="margin:0 0 0 40px; border:none; padding:0px;"><p class="line867"><font face="Arial,Lucida Grande,sans-serif">Certificates issued after the Effective Date MUST have a Validity Period no greater than 60 months. Except as provided for below, Certificates issued after 1 April 2015 MUST have a Validity Period no greater than 39 months. Beyond 1 April 2015, CAs MAY continue to issue Certificates with a Validity Period greater than 39 months but not greater than 60 months provided that the CA documents that the Certificate is for a system or software that:</font></p></blockquote><p class="line867"><font face="Arial,Lucida Grande,sans-serif"><i>Amended to:-</i></font></p><blockquote style="margin:0 0 0 40px; border:none; padding:0px;"><p class="line867"><font face="Arial,Lucida Grande,sans-serif"><b>9.4 Validity Period</b></font></p></blockquote><p></p></div></span><blockquote style="margin:0 0 0 40px; border:none; padding:0px;"><span id="OLK_SRC_BODY_SECTION"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><p class="line867" style="background-color: rgb(255, 255, 255); "></p><p class="line867"><font face="Arial,Lucida Grande,sans-serif"><b>9.4.1 Subscriber Certificates</b></font></p><p></p></div></span></blockquote><span id="OLK_SRC_BODY_SECTION"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><p class="line867" style="background-color: rgb(255, 255, 255); "></p><blockquote style="margin:0 0 0 40px; border:none; padding:0px;"><p class="line867"><font face="Arial,Lucida Grande,sans-serif">Subscriber Certificates issued after the Effective Date MUST have a Validity Period no greater than 60 months. Except as provided for below, Subscriber Certificates issued after 1 April 2015 MUST have a Validity Period no greater than 39 months. Beyond 1 April 2015, CAs MAY continue to issue Subscriber Certificates with a Validity Period greater than 39 months but not greater than 60 months provided that the CA documents that the Certificate is for a system or software that:</font></p></blockquote><div><p class="line867"><font face="Arial,Lucida Grande,sans-serif"><b>9.5 Subscriber Public Key <i>(Alignment of Key checking for all certificates)</i></b></font></p></div><blockquote style="margin:0 0 0 40px; border:none; padding:0px;"><p class="line867"><font face="Arial,Lucida Grande,sans-serif"><b>9.5 Public Key</b></font></p></blockquote><p></p></div></span><span id="OLK_SRC_BODY_SECTION"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><p class="line867" style="background-color: rgb(255, 255, 255); "></p><div><p class="line867"><b style="font-family: Arial, 'Lucida Grande', sans-serif; ">9.7 Additional Technical Requirement<i> (Moving to Section 9.8)</i></b></p></div><div><p class="line867"><font face="Arial,Lucida Grande,sans-serif"><b>9.7 Technical Constraints in Subordinate CA Certificates via Name Constraints & EKU <i>(New section)</i></b></font></p></div><blockquote style="margin:0 0 0 40px; border:none; padding:0px;"><p class="line867"><font face="Arial,Lucida Grande,sans-serif"><b>9.7 Technical Constraints in Subordinate CA Certificates via Name Constraints & EKU</b></font></p></blockquote><p></p></div></span><blockquote style="margin:0 0 0 40px; border:none; padding:0px;"><div><span style="font-family: Arial, 'Lucida Grande', sans-serif; background-color: rgb(255, 255, 255); ">For a Subordinate CA Certificate to be considered Technically Constrained, the certificate MUST include an Extended Key Usage (EKU) extension specifying all extended key usages that the Subordinate CA Certificate is authorized to issue certificates for. The anyExtendedKeyUsage KeyPurposeId MUST NOT appear within this extension. If the Subordinate CA Certificate includes the id-kp-serverAuth extended key usage, then the Subordinate CA Certificate MUST include the Name Constraints X.509v3 extension with constraints on dNSName, iPAddress and DirectoryName as follows:-</span></div></blockquote><span id="OLK_SRC_BODY_SECTION"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><p class="line867" style="background-color: rgb(255, 255, 255); "></p><blockquote style="margin:0 0 0 40px; border:none; padding:0px;"><blockquote style="margin:0 0 0 40px; border:none; padding:0px;"><p class="line867"><font face="Arial,Lucida Grande,sans-serif">(a) For each dNSName in permittedSubtrees, the CA MUST confirm that the Applicant has registered the dNSName or has been authorized by the domain registrant to act on the registrant's behalf in line with the verification practices of section 11.1</font></p></blockquote></blockquote><p></p></div></span><span id="OLK_SRC_BODY_SECTION"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><p class="line867" style="background-color: rgb(255, 255, 255); "></p><blockquote style="margin:0 0 0 40px; border:none; padding:0px;"><blockquote style="margin:0 0 0 40px; border:none; padding:0px;"><p class="line867"><font face="Arial,Lucida Grande,sans-serif">(b) For each iPAddress range in permittedSubtrees, the CA MUST confirm that the Applicant has been assigned the iPAddress range or has been authorized by the assigner to act on the assignee's behalf.</font></p><p class="line867"><font face="Arial,Lucida Grande,sans-serif">(c) For each DirectoryName in permittedSubtrees the CA MUST confirm the Applicants and/or Subsidiary’s Organizational name and location such that end entity certificates issued from the subordinate CA Certificate will be in compliancy with section 9.2.4 and 9.2.5.</font></p></blockquote></blockquote><blockquote style="margin:0 0 0 40px; border:none; padding:0px;"><p class="line867"><font face="Arial,Lucida Grande,sans-serif">If the Subordinate CA Certificate is not allowed to issue certificates with an iPAddress, then the Subordinate CA Certificate MUST specify the entire IPv4 and IPv6 address ranges in excludedSubtrees. The Subordinate CA Certificate MUST include within excludedSubtrees an iPAddress GeneralName of 8 zero octets (covering the IPv4 address range of 0.0.0.0/0). The Subordinate CA Certificate MUST also include within excludedSubtrees an iPAddress GeneralName of 32 zero octets (covering the IPv6 address range of ::0/0). Otherwise, the Subordinate CA Certificate MUST include at least one iPAddress in permittedSubtrees.</font></p></blockquote><p></p></div></span><span id="OLK_SRC_BODY_SECTION"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><p class="line867" style="background-color: rgb(255, 255, 255); "></p><blockquote style="margin:0 0 0 40px; border:none; padding:0px;"><p class="line867"><span style="font-family: Arial, 'Lucida Grande', sans-serif; font-size: 12px; ">A decoded example for issuance to the domain and sub domains of example.com by organization :- Example LLC, Boston, Massachusetts, US would be:-</span></p></blockquote><p></p><blockquote style="margin:0 0 0 40px; border:none; padding:0px;"><p class="line867" style="color: rgb(0, 0, 0); font-family: Arial, sans-serif; font-size: 12px; background-color: rgb(255, 255, 255); "><span style="font-family: Arial, 'Lucida Grande', sans-serif; "><span class="Apple-tab-span" style="white-space:pre"> </span>X509v3 Name Constraints:</span></p><p class="line867" style="color: rgb(0, 0, 0); font-family: Arial, sans-serif; font-size: 12px; background-color: rgb(255, 255, 255); "><font face="Arial,Lucida Grande,sans-serif"><span class="Apple-tab-span" style="white-space:pre"> </span>Permitted:</font></p><p class="line867" style="color: rgb(0, 0, 0); font-family: Arial, sans-serif; font-size: 12px; background-color: rgb(255, 255, 255); "><font face="Arial,Lucida Grande,sans-serif"><span class="Apple-tab-span" style="white-space:pre"> </span>DNS:example.com </font></p><p class="line867" style="color: rgb(0, 0, 0); font-family: Arial, sans-serif; font-size: 12px; background-color: rgb(255, 255, 255); "><font face="Arial,Lucida Grande,sans-serif"><span class="Apple-tab-span" style="white-space:pre"> </span>DirName: C=US, ST=MA, L=Boston, O=Example LLC</font></p><p class="line867" style="color: rgb(0, 0, 0); font-family: Arial, sans-serif; font-size: 12px; "><span class="Apple-tab-span" style="white-space: pre; "> </span>Excluded:</p></blockquote><div style="color: rgb(0, 0, 0); font-family: Arial, sans-serif; font-size: 12px; "><blockquote style="margin:0 0 0 40px; border:none; padding:0px;"><span class="anchor" id="line-67"></span></blockquote><div><blockquote style="margin:0 0 0 40px; border:none; padding:0px;"><p class="line891" style="margin: 0.25em 0px; "><span class="Apple-tab-span" style="white-space:pre"> </span>IP:0.0.0.0/0.0.0.0 </p><p class="line891" style="margin: 0.25em 0px; "><span class="anchor" id="line-68"></span><span class="Apple-tab-span" style="white-space:pre"> </span>IP:0:0:0:0:0:0:0:0/0:0:0:0:0:0:0:0<span class="anchor" id="line-69"></span><span class="anchor" id="line-70"></span></p></blockquote></div></div><p class="line874" style="background-color: rgb(255, 255, 255); "></p><blockquote style="margin:0 0 0 40px; border:none; padding:0px;"><p class="line874"><font face="Arial,Lucida Grande,sans-serif">If the Subordinate CA is not allowed to issue certificates with dNSNames, then the Subordinate CA Certificate MUST include a zero-length dNSName in excludedSubtrees. Otherwise, the Subordinate CA Certificate MUST include at least one dNSName in permittedSubtrees.</font></p></blockquote><div><p class="line874"><font face="Arial,Lucida Grande,sans-serif"><b>Section 11.1.1 Authorization by Domain Name Registrant <i>(Adding clarification)</i></b></font></p></div><blockquote style="margin:0 0 0 40px; border:none; padding:0px;"><p class="line874"><span style="font-family: Arial, 'Lucida Grande', sans-serif; ">Note: FQDNs may be listed in Subscriber Certificates using dNSNames in the subjectAltName extension or in Subordinate CA Certificates via dNSNames in permittedSubtrees within the Name Constraints extension.</span></p></blockquote><div><p class="line874"><font face="Arial,Lucida Grande,sans-serif"><b>Section 11.1.2 Authorization for an IP Address<i> (Adding clarification)</i></b></font></p></div><blockquote style="margin:0 0 0 40px; border:none; padding:0px;"><p class="line874"><span style="font-family: Arial, 'Lucida Grande', sans-serif; ">Note: IPAddresses may be listed in Subscriber Certificates using IPAddress in the subjectAltName extension or in Subordinate CA Certificates via IPAddress in permittedSubtrees within the Name Constraints extension.</span></p></blockquote><div><p class="line874"><font face="Arial,Lucida Grande,sans-serif"><b>Section 13.2.6 Response for non-issued certificates <i>(Amending applicability)</i></b></font></p></div><p class="line874"><font face="Arial,Lucida Grande,sans-serif"><i>Was:-</i></font></p><blockquote style="margin:0 0 0 40px; border:none; padding:0px;"><p class="line874"><font face="Arial,Lucida Grande,sans-serif"><b>13.2.6 Response for non-issued certificates</b></font></p></blockquote><p></p></div></span><span id="OLK_SRC_BODY_SECTION"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><p class="line874" style="background-color: rgb(255, 255, 255); "></p><blockquote style="margin:0 0 0 40px; border:none; padding:0px;"><p class="line874"><font face="Arial,Lucida Grande,sans-serif">If the OCSP responder receives a request for status of a certificate that has not been issued, then the responder SHOULD NOT respond with a "good" status. The CA SHOULD monitor the responder for such requests as part of its security response procedures. Effective 1 August 2013, OCSP responders MUST NOT respond with a "good" status for such certificates.</font></p></blockquote><p class="line874"><font face="Arial,Lucida Grande,sans-serif"><i>Amended to:-</i></font></p><blockquote style="margin:0 0 0 40px; border:none; padding:0px;"><p class="line874"><font face="Arial,Lucida Grande,sans-serif"><b>13.2.6 Response for non-issued certificates</b></font></p></blockquote><p></p></div></div></span><span id="OLK_SRC_BODY_SECTION"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><p class="line874" style="background-color: rgb(255, 255, 255); "></p><blockquote style="margin:0 0 0 40px; border:none; padding:0px;"><p class="line874"><font face="Arial,Lucida Grande,sans-serif">If the OCSP responder receives a request for status of a certificate that has not been issued, then the responder SHOULD NOT respond with a "good" status. The CA SHOULD monitor the responder for such requests as part of its security response procedures. Effective 1 August 2013, OCSP responders for CAs which are not Technically Constrained in line with Section 9.7 MUST NOT respond with a "good" status for such certificates.</font></p></blockquote><div><p class="line874"><font face="Arial,Lucida Grande,sans-serif"><b>Section 17 Audit <i>(Clarification notes added to the section heading)</i></b></font></p></div><blockquote style="margin:0 0 0 40px; border:none; padding:0px;"><p class="line874"><font face="Arial,Lucida Grande,sans-serif">Certificates that are capable of being used to issue new certificates MUST either be Technically Constrained in line with section 9.7 and audited in line with section 17.9 only, or Unconstrained and fully audited in line with all remaining requirements from section 17. A Certificate is deemed as capable of being used to issue new certificates if it contains an X.509v3 basicConstraints extension, with the cA boolean set to true and is therefore by definition a Root CA Certificate or a Subordinate CA Certificate.</font></p></blockquote><div><p class="line874"><font face="Arial,Lucida Grande,sans-serif"><b>Section 17.9 Regular Quality Assessment of Technically Constrained Subordinate CAs <i>(New Section)</i></b></font></p></div><blockquote style="margin:0 0 0 40px; border:none; padding:0px;"><p class="line874"><font face="Arial,Lucida Grande,sans-serif">During the period in which a Technically Constrained Subordinate CA issues Certificates, the CA which signed the Subordinate CA SHALL monitor adherence to the CA’s Certificate Policy and the Subordinate CA’s Certification Practice Statement. On at least a quarterly basis, against a randomly selected sample of the greater of one certificate or at least three percent of the Certificates issued by the Subordinate CA, during the period commencing immediately after the previous audit sample was taken, the CA shall ensure all applicable Baseline Requirements are met.</font></p></blockquote><div><p class="line874"><font face="Arial,Lucida Grande,sans-serif"><b>Appendix B - Certificate Extensions (Normative) <i>(Clarify F and add G)</i></b></font></p></div><p class="line874"><font face="Arial,Lucida Grande,sans-serif"><i>Was:-</i></font></p><blockquote style="margin:0 0 0 40px; border:none; padding:0px;"><p class="line874"><font face="Arial,Lucida Grande,sans-serif"><b>F. nameConstraints (optional)</b> If present, this extension SHOULD be marked critical*.</font></p></blockquote><p></p></div></div></span><span id="OLK_SRC_BODY_SECTION"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><p class="line874" style="background-color: rgb(255, 255, 255); "></p><blockquote style="margin:0 0 0 40px; border:none; padding:0px;"><p class="line874"><font face="Arial,Lucida Grande,sans-serif">* Non-critical Name Constraints are an exception to RFC 5280 that MAY be used until the Name Constraints extension is supported by Application Software Suppliers whose software is used by a substantial portion of Relying Parties worldwide.</font></p></blockquote><p class="line874"><font face="Arial,Lucida Grande,sans-serif"><i>Amended to:-</i></font></p><blockquote style="margin:0 0 0 40px; border:none; padding:0px;"><p class="line874"><font face="Arial,Lucida Grande,sans-serif"><b>F. nameConstraints (optional) </b>If present, this extension SHOULD be marked critical*.</font></p></blockquote><p></p></div></div></span><blockquote style="margin:0 0 0 40px; border:none; padding:0px;"><span id="OLK_SRC_BODY_SECTION"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><p class="line874" style="background-color: rgb(255, 255, 255); "></p><p class="line874"><font face="Arial,Lucida Grande,sans-serif">* Non-critical Name Constraints are an exception to RFC 5280 (4.2.1.10), however, they MAY be used until the Name Constraints extension is supported by Application Software Suppliers whose software is used by a substantial portion of Relying Parties worldwide.</font></p><p></p></div></div></span><span id="OLK_SRC_BODY_SECTION"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><p class="line874" style="background-color: rgb(255, 255, 255); "></p><p class="line874"><font face="Arial,Lucida Grande,sans-serif"><b>G. extkeyUsage (optional)</b> For Subordinate CA Certificates to be Technically constrained in line with section 9.8, then either the value id-kp-serverAuth [RFC5280] or id-kp-clientAuth [RFC5280] or both values MUST be present**. </font><span style="font-family: Arial, 'Lucida Grande', sans-serif; ">Other values MAY be present. If present, this extension SHOULD be marked non-critical.</span></p><p></p></div></div></span></blockquote><span id="OLK_SRC_BODY_SECTION"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><blockquote style="margin:0 0 0 40px; border:none; padding:0px;"><p class="line874" style="background-color: rgb(255, 255, 255); "></p><p class="line874"><font face="Arial,Lucida Grande,sans-serif">** Generally Extended Key Usage will only appear within end entity certificates (as highlighted in RFC 5280 (4.2.1.12)), however, Subordinate CAs MAY include the extension to further protect relying parties until the use of the extension is consistent between Application Software Suppliers whose software is used by a substantial portion of Relying Parties worldwide.</font></p><p></p></blockquote></div></div></span><div><span style="background-color: rgb(255, 255, 255); font-family: Arial, 'Lucida Grande', sans-serif; font-size: 12px; ">The review period for this ballot shall commence on July 15th, 2013 and will close on July 22nd, 2013. Unless the motion is withdrawn during the review period, the voting period will start immediately thereafter and will close at July 29, 2013. Votes must be cast by posting an on-list reply to this thread.</span></div><span id="OLK_SRC_BODY_SECTION"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div><p class="line874" style="color: rgb(0, 0, 0); font-family: Arial, 'Lucida Grande', sans-serif; font-size: 12px; background-color: rgb(255, 255, 255); "><span class="anchor" id="line-122"></span></p></div><div><p class="line867" style="color: rgb(0, 0, 0); font-family: Arial, 'Lucida Grande', sans-serif; font-size: 12px; background-color: rgb(255, 255, 255); "><strong>Motion Ends</strong><span class="anchor" id="line-123"></span><span class="anchor" id="line-124"></span></p></div><p class="line862" style="color: rgb(0, 0, 0); font-family: Arial, 'Lucida Grande', sans-serif; font-size: 12px; background-color: rgb(255, 255, 255); ">A vote in favor of the motion must indicate a clear 'yes' in the response. A vote against must indicate a clear 'no' in the response. A vote to abstain must indicate a clear 'abstain' in the response. Unclear responses will not be counted. The latest vote received from any representative of a voting member before the close of the voting period will be counted. Voting members are listed here: <a class="http" href="http://www.cabforum.org/forum.html" style="color: blue; border: 0px; text-decoration: none; ">http://www.cabforum.org/forum.html</a> <span class="anchor" id="line-125"></span>In order for the motion to be adopted, two thirds or more of the votes cast by members in the CA category and one half or more of the votes cast by members in the browser category must be in favor. Also, at least seven members must participate in the ballot, either by voting in favor, voting against, or abstaining.</p></div><div style="color: rgb(0, 0, 0); font-family: Arial, sans-serif; font-size: 12px; "><p></p></div></div></span></div></div></span></body></html>