CA/Browser Forum
Home » All CA/Browser Forum Posts » Ballot FORUM-9: Bylaws and Server Certificate Working Group Charter Updates

Ballot FORUM-9: Bylaws and Server Certificate Working Group Charter Updates

Results

The voting period for Ballot Forum-9 has ended and the Ballot has Passed. Here are the results:

Voting by Certificate Issuers

11 votes total including abstentions

  • 11 Yes votes: Chunghwa Telecom, DarkMatter, DigiCert, Disig, eMudhra, Entrust Datacard, GDCA, GlobalSign, HARICA, SHECA, SecureTrust.

  • 0 No votes:

  • 0 Abstain:

100% of voting Certificate Issuers voted in favor.

Voting by Certificate Consumers

3 votes total including abstentions

  • 3 Yes votes: Cisco, Microsoft, Mozilla
  • 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.
  • 21 member companies attended the last teleconference, and quorum was updated accordingly. Half of currently active Members as of the start of voting was 10, so quorum was 11 votesquorum was met.

Ballot FORUM-9

Purpose of Ballot: The Forum has identified and discussed a number of improvements to be made to the current version of the Bylaws to improve clarity and allow the Forum to function more effectively. Major changes include:

  • Formalize Subcommittees at the Forum level
  • Automatically grant Forum membership to CWG members
  • Move Forum membership requirements to the SCWG Charter and clarify them
  • Clarify CWG voting rules
  • Clarify process for CWG officer elections

The following motion has been proposed by Wayne Thayer of Mozilla and endorsed by Dimitris Zacharopoulos of HARICA and Tim Hollebeek of DigiCert to amend the Bylaws of the CA/Browser Forum and the Server Certificate Working Group Charter.

Motion Begins

  1. Amendment to the Bylaws: replace the entire text of the Bylaws of the CA/Browser Forum with the following:

    https://github.com/cabforum/documents/blob/f749189752994b378fae2ca9b8f22f51fcc2e204/docs/Bylaws.md

  2. Amendment to the SCWG Charter: replace the entire text of the Server Certificate Working Group Charter with the following:

    https://github.com/cabforum/documents/blob/f749189752994b378fae2ca9b8f22f51fcc2e204/docs/SCWG-charter.md

Motion ends

WARNING: USE AT YOUR OWN RISK. THE REDLINE BELOW IS NOT THE OFFICIAL VERSION OF THE CHANGES (CABF Bylaws, Section 2.4(a)):

A comparison of the changes can be found at: https://github.com/cabforum/documents/compare/0616216..f749189?diff=split

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