<font size=2 face="sans-serif">CERTUM votes NO.</font>
<br>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">Od:
</font><font size=1 face="sans-serif">Jeremy Rowley <jeremy.rowley@digicert.com></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Do:
</font><font size=1 face="sans-serif">"public@cabforum.org"
<public@cabforum.org></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Data:
</font><font size=1 face="sans-serif">2015-10-26 22:38</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Temat:
</font><font size=1 face="sans-serif">[cabfpub] Short-Lived
Certificate Ballot</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Wysłane przez:
</font><font size=1 face="sans-serif">public-bounces@cabforum.org</font>
<br>
<hr noshade>
<br>
<br>
<br><font size=3 face="Arial">Here’s the official Short-Lived Cert Ballot.
The review period starts tomorrow. With the ballot starting on Nov 3. </font>
<p><font size=3 face="Arial"><b>Ballot 153 – Short-Lived Certificates</b></font>
<p><font size=3 face="Arial">The following motion has been proposed by
Jeremy Rowley of DigiCert and endorsed by Ryan Sleevi of Google and Gervase
Markham of Mozilla.</font>
<p><font size=3 face="Arial">-- MOTION BEGINS --</font>
<p><font size=3 face="Arial">1) Add/revise the following definitions:</font>
<p><font size=3 face="Arial"><u>Issuance Time: The time at which a Certificate’s
digital signature is calculated.</u></font>
<p><font size=3 face="Arial"><u>Short-Lived Certificate: A Certificate
with a Validity Period less than 96 hours and a notBefore time no earlier
than 24 hours before the Issuance Time and a notAfter time no later than
72 hours after the Issuance Time.</u></font>
<p><font size=3 face="Arial">Validity Period: The period of time <strike>measured</strike>
from <u>notBefore through notAfter, inclusive</u>. <strike>the date when
the Certificate is issued until the Expiry Date.</strike></font>
<p><font size=3 face="Arial">2) Modify Section 4.9.10 as follows:</font>
<p><font size=3 face="Arial">4.9.10. On</font><font size=3 face="Cambria Math">‐</font><font size=3 face="Arial">line
Revocation Checking Requirements</font>
<p><font size=3 face="Arial">Effective 1 January 2013, the CA SHALL support
an OCSP capability using the GET method for Certificates issued in accordance
with these Requirements.</font>
<p><font size=3 face="Arial">For the status of Subscriber Certificates
<u>other than a Short-Lived Certificate containing a cRLDistributionPoints
extension</u>: The CA SHALL update information provided via an Online Certificate
Status Protocol at least every four days. OCSP responses from this service
MUST have a maximum expiration time of ten days.</font>
<p><font size=3 face="Arial">3) Modify Section 7.1.2.3 as follows:</font>
<p><font size=3 face="Arial">7.1.2.3. Subscriber Certificate …</font>
<p><font size=3 face="Arial">b. cRLDistributionPoints This extension <u>MUST
be present for Short-Lived Certificates that lack an authorityInformationAccess
extension and</u> MAY be present for all other certificates. If present,
it MUST NOT be marked critical, and it MUST contain the HTTP URL of the
CA’s CRL service. See Section 13.2.1 for details.</font>
<p><font size=3 face="Arial">c. authorityInformationAccess With the exception
of stapling <u>and Short-Lived Certificates</u>, <strike>which is noted
below</strike>, this extension MUST be present. It MUST NOT be marked critical,
and it MUST contain the HTTP URL of the Issuing CA’s OCSP responder (accessMethod
= 1.3.6.1.5.5.7.48.1). It SHOULD also contain the HTTP URL of the Issuing
CA’s certificate (accessMethod = 1.3.6.1.5.5.7.48.2).</font>
<p><font size=3 face="Arial">The HTTP URL of the Issuing CA’s OCSP responder
MAY be omitted <u>for Short-Lived Certificates containing a cRLDistributionPoints
extension or if</u> Subscriber “staples” OCSP responses for the Certificate
in its TLS handshakes [RFC4366].</font>
<p><font size=3 face="Arial">-- MOTION ENDS --</font>
<p><font size=3 face="Arial">The review period for this ballot shall commence
at 27 October 2015, and will close at 3 November 2015. Unless the motion
is withdrawn during the review period, the voting period will start immediately
thereafter and will close at 10 November 2015. Votes must be cast by posting
an on-list reply to this thread.</font>
<p><font size=3 face="Arial">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: </font><a href=https://cabforum.org/members/><font size=3 color=#0082bf face="Arial"><u>https://cabforum.org/members/</u></font></a>
<p><font size=3 face="Arial">In order for the motion to be adopted, two
thirds or more of the votes cast by members in the CA category and greater
than 50% of the votes cast by members in the browser category must be in
favor. Quorum is currently nine (9) members– at least nine members must
participate in the ballot, either by voting in favor, voting against, or
abstaining.</font>
<br><font size=3 face="Calibri"> </font><tt><font size=2>_______________________________________________<br>
Public mailing list<br>
Public@cabforum.org<br>
</font></tt><a href=https://cabforum.org/mailman/listinfo/public><tt><font size=2>https://cabforum.org/mailman/listinfo/public</font></tt></a><tt><font size=2><br>
</font></tt>
<br>