CA/Browser Forum
Home » All CA/Browser Forum Posts » Ballot 166 – Clarification of Membership Requirements

Ballot 166 – Clarification of Membership Requirements

Voting on Ballot 166 (Membership Update) has now closed. The results are as follows:

From the CAs, we received 18 YES votes, zero NO votes and zero Abstentions

From the Browsers, we received 3 YES votes, zero NO votes and zero Abstentions.

Therefore the ballot passes.

Full ballot results can be found here: https://docs.google.com/spreadsheets/d/1FBsMZjlzyvK3mFR1u4qMqvZwlI86yJ-v0am1pCBo8uI/edit#gid=4

Ballot 166: Clarification of Membership Requirements

The following motion has been proposed by Dean Coclin of Symantec and endorsed by Gerv Markham of Mozilla and Kirk Hall of Trend Micro:

Background

Section 2.1 (a)(1) says that Issuing CAs “actively issue certificates to Web servers…”

Section 2.1(b) of the bylaws lists the items needed in a membership application by CAs.

But that section does not ask the CA applicant to provide a 3rd party website where the CA/B Forum can validate that they are actively issuing certs to web servers. We do however ask the applicant this question, after they have submitted their application. It would be helpful to have this in the bylaws so we don’t have to go back and ask every time.

Motion begins

In CA/B Forum Bylaws, add under 2.1(b):

(7) The URL of at least one third party website that includes a certificate issued by the Applicant in the certificate chain.

Motion ends

The review period for this ballot shall commence at 2200 UTC on 21 March 2016, and will close at 2200 UTC on 28 March 2016. Unless the motion is withdrawn during the review period, the voting period will start immediately thereafter and will close at 2200 UTC on 4 April 2016. Votes must be cast by posting an on-list reply to this thread.

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/members/

Latest releases
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.6 - Ballot SMC08 - Aug 29, 2024

This ballot sets a date by which issuance of certificates following the Legacy generation profiles must cease. It also includes the following minor updates: Pins the domain validation procedures to v 2.0.5 of the TLS Baseline Requirements while the ballot activity for multi-perspective validation is concluded, and the SMCWG determines its corresponding course of action; Updates the reference for SmtpUTF8Mailbox from RFC 8398 to RFC 9598; and Small text corrections in the Reference section

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