CA/Browser Forum
Home » All CA/Browser Forum Posts » Ballot FORUM-15: Election of CA/Browser Forum Chair

Ballot FORUM-15: Election of CA/Browser Forum Chair

Ballot Results

The voting period for Special Ballot Forum-15 has ended and the Ballot has Passed. Congratulations Dean!

Here are the results:

Voting by Certificate Issuers – 24 votes total including abstentions

– 24** Yes votes**: Actalis, Buypass, Camerfirma, Certigna (DHIMYOTIS), Certum (Asseco), Chunghwa Telecom, D-TRUST, DigiCert, Disig, eMudhra, Entrust Datacard, Firmaprofesional, GDCA, GlobalSign, HARICA, iTrusChina, Kamu SM, OATI, OISTE, SECOM, SHECA, SwissSign, TrustCor, SecureTrust. – 0 No votes: – 0 Abstain:

100% of voting Certificate Issuers voted in favor.

Voting by Certificate Consumers – 5 votes total including abstentions

– 5** Yes votes: Cisco, Google, Microsoft, Mozilla, 360 – 0 No votes**: – 0 Abstain:

100% of voting Certificate Consumers voted in favor.

Relevant Bylaw references

Bylaw 2.3(f) requires:

– a “yes” vote by two-thirds of Certificate Issuer votes and 50%-plus-one Certificate Consumer votes for approval. Votes to abstain are not counted for this purpose. This requirement was met for both Certificate Issuers and Certificate Consumers. – at least one Certificate Issuer and one Certificate Consumer Member must vote in favor of a ballot for the ballot to be adopted. This requirement was also met.

Under Bylaw 2.3(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 was 11, so quorum was** 12** votes – quorum was met.”

Ballot Content

The following motion has been proposed by the CA/Browser Forum Chair Dimitris Zacharopoulos of HARICA.

Purpose of Ballot

This special ballot is to confirm the new Chair of the CA/Browser Forum.

Motion begins

In accordance with Bylaw 4.1(c), Dean Coclin representing Digicert is hereby elected Chair of the CA/Browser Forum for a term commencing on November 1, 2020 and continuing through October 31, 2022.

Motion ends

Latest releases
Server Certificate Requirements
BRs/2.1.2 SC-080 V3: Sunset the use of WHOIS to identify Domain Contacts and relying DCV Methods - Dec 16, 2024

Ballot SC-080 V3: “Sunset the use of WHOIS to identify Domain Contact… (https://github.com/cabforum/servercert/pull/560) Ballot SC-080 V3: “Sunset the use of WHOIS to identify Domain Contacts and relying DCV Methods” (https://github.com/cabforum/servercert/pull/555)

Code Signing Requirements
v3.8 - Aug 5, 2024

What’s Changed CSC-25: Import EV Guidelines to CS Baseline Requirements by @dzacharo in https://github.com/cabforum/code-signing/pull/38 Full Changelog: https://github.com/cabforum/code-signing/compare/v3.7...v3.8

S/MIME Requirements
v1.0.8 - Ballot SMC010 - Dec 23, 2024

This ballot adopts Multi-Perspective Issuance Corroboration (MPIC) for CAs when conducting Email Domain Control Validation (DCV) and Certification Authority Authorization (CAA) checks for S/MIME Certificates. The Ballot adopts the MPIC implementation consistent with the TLS Baseline Requirements. Acknowledging that some S/MIME CAs with no TLS operations may require additional time to deploy MPIC, the Ballot has a Compliance Date of May 15, 2025. Following that date the implementation timeline described in TLS BR section 3.2.2.9 applies. This ballot is proposed by Stephen Davidson (DigiCert) and endorsed by Ashish Dhiman (GlobalSign) and Nicolas Lidzborski (Google).

Network and Certificate System Security Requirements
v2.0 - Ballot NS-003 - Jun 26, 2024

Ballot NS-003: Restructure the NCSSRs in https://github.com/cabforum/netsec/pull/35

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).