Ballot 223 – Update BR Section 8.4 for CA audit criteria
The voting period for Ballot 223 has ended and the ballot has passed. Here are the results.
Voting by CAs – 24 votes total including abstentions
24 Yes votes: Actalis, Amazon, Buypass, Camerfirma, CFCA, Chunghwa Telecom, Cisco, D-TRUST, DigiCert, Disig, Entrust Datacard, GDCA, GlobalSign, GoDaddy, HARICA, Izenpe, OATI, QuoVadis, Sertifitseerimiskeskus, SHECA, SSL.com, SSC, TrustCor, Trustwave
0 No votes:
0 Abstain:
100% of voting CAs voted in favor
Voting by browsers – 5 votes total including abstentions
5 Yes votes: Apple, Comodo Group Inc., Microsoft, Mozilla, 360
0 No votes:
0 Abstain:
100% of voting browsers voted in favor
Under Bylaw 2.2(g), a ballot result will be considered valid only when more than half of the number of currently active Members has participated. Votes to abstain are counted in determining a quorum. Half of currently active Members as of the start of voting is 9, so quorum was 10 votes. There were 29 votes total – quorum was met.
Bylaw 2.2(f) requires a yes vote by two-thirds of CA votes and 50%-plus-one browser votes for approval. Votes to abstain are not counted for this purpose. This requirement was met for both CAs and browsers.
At least one CA Member and one browser Member must vote in favor of a ballot for the ballot to be adopted. This requirement was met
The ballot passes.
The following motion has been proposed by Dimitris Zacharopoulos of HARICA and endorsed by Moudrick M. Dadashov of SSC and Tim Hollebeek from Digicert.
Background:
Section 8.4 of the Baseline Requirements describes the audit criteria for CAs that issue Publicly-Trusted SSL/TLS Certificates. This ballot attempts to achieve two things:
- Remove the old ETSI TS documents
- Align the WebTrust and ETSI requirements
“WebTrust for Certification Authorities” is equivalent to “ETSI EN 319 401” and “WebTrust Principles and Criteria for Certification Authorities – SSL Baseline with Network Security” combined with “WebTrust for Certification Authorities” is equivalent to “ETSI EN 319 411-1”.
Motion begins
Replace the first two numbered items in section 8.4 from:
- WebTrust for Certification Authorities v2.0;
- A national scheme that audits conformance to ETSI TS 102 042 / ETSI EN 319 411-1; or
to:
- “WebTrust for CAs v2.0 or newer” AND “WebTrust for CAs SSL Baseline with Network Security v2.2 or newer”; or
- ETSI EN 319 411-1, which includes normative references to ETSI EN 319 401 (the latest version of the referenced ETSI documents should be applied); or
Motion ends
The procedure for this ballot is as follows (exact start and end times may be adjusted to comply with applicable Bylaws and IPR Agreement):
BALLOT 223 v2 Status: Update BR Section 8.4 for CA audit criteria
| Start time (22:00 UTC) | End time (22:00 UTC) | |
|---|---|---|
| Discussion (7+ days) | 30 April 2018 | 7 May 2018 |
| Vote for approval (7 days) | 8 May 2018 | 15 May 2018 |
| If vote approves ballot: Review Period (Chair to send Review Notice) (30 days) If Exclusion Notice(s) filed, ballot approval is rescinded and PAG to be created. If no Exclusion Notices filed, ballot becomes effective at end of Review Period. Votes must be cast by posting an on-list reply to this thread on the Public Mail List. | Upon filing of Review Notice by Chair | 30 days after filing of Review Notice by Chair |
From the Bylaws section 2.4(a): “If the Draft Guideline Ballot is proposing a Final Maintenance Guideline, such ballot will include a redline or comparison showing the set of changes from the Final Guideline section(s) intended to become a Final Maintenance Guideline, and need not include a copy of the full set of guidelines. Such redline or comparison shall be made against the Final Guideline section(s) as they exist at the time a ballot is proposed, and need not take into consideration other ballots that may be proposed subsequently, except as provided in Section 2.4(j) below”.
Votes must be cast by posting an on-list reply to this thread on the Public list. 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: /about/membership/members/
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 shown on CA/Browser Forum wiki. Under the Bylaws section 2.3(g), at least the required quorum number must participate in the ballot for the ballot to be valid, either by voting in favor, voting against, or abstaining.