CA/Browser Forum
Home » Posts » Ballot 215 – Fix Ballot 190 Errata

Ballot 215 – Fix Ballot 190 Errata

The voting period for Ballot 215 has ended and the ballot has passed. Here are the results.

Voting by CAs – 18 votes total including abstentions

  • 18 Yes votes: Buypass, CFCA, D-TRUST, DigiCert, Disig, Entrust, GDCA, GlobalSign, GoDaddy, HARICA, Izenpe, OATI, QuoVadis,, Symantec, TWCA, TrustCor, Trustwave

  • 0 No votes:

  • 0 Abstain:

100% of voting CAs voted in favor

Voting by browsers – 3 votes total including abstentions

  • 3 Yes votes: Apple, Google, Mozilla

  • 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 8, so quorum was 9 votes – 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.

Ballot 215 – Fix Ballot 190 Errata


Ballot 190 inadvertently added “or a Delegated Third Party” back into section of the Baseline Requirements, which conflicts with the results of Ballot 204 that removed it from section This ballot re-removes “Delegated Third Party” from section of the Baseline Requirements.

The following motion has been proposed by Ben Wilson of DigiCert and endorsed by Rich Smith of Comodo and Tim Hollebeek of Trustwave.

Motion begins

In the Baseline Requirements v. 1.5.2., section, remove instances of “or a Delegated Third Party” and “or Delegated Third Party”, as further indicated by red strike-outs in the attached PDF file (here – Ballot 215).

–Motion Ends–

The procedure for approval of this Final Maintenance Guideline ballot is as follows (exact start and end times may be adjusted to comply with applicable Bylaws and IPR Agreement):

BALLOT 215 Status: Final Maintenance Guideline Start time (16:00 UTC) End time (16:00 UTC)

Discussion begins September 21, 2017 (immediately) and ends September 28, 2017 16:00 UTC (7 days)

Vote for approval begins September 28, 2017 16:00 UTC and ends October 5, 2017 16:00 UTC (7 days)

If vote approves ballot: Review Period (Chair to send Review Notice) (30 days) which begins upon filing of Review Notice by Chair and ends 30 days after filing of Review Notice by Chair. 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.

From Bylaw 2.3: 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 Bylaw Section 2.3(j).

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:

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 Bylaw 2.2(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.

Latest releases
Code Signing Requirements
v3.7 - Mar 4, 2024

S/MIME Requirements
v1.0.4 - Ballot SMC06 - May 11, 2024

Ballot SMC06: Post implementation clarification and corrections

Edit this page
The Certification Authority Browser Forum (CA/Browser Forum) is a voluntary gathering of Certificate Issuers and suppliers of Internet browser software and other applications that use certificates (Certificate Consumers).