CA/Browser Forum
Home » All CA/Browser Forum Posts » Ballot 89 – Publish Recommendations for the Processing of EV SSL Certificates v.2(passes)

Ballot 89 – Publish Recommendations for the Processing of EV SSL Certificates v.2(passes)

Voting on Ballot 89 closed. Ten voted in favor – Buypass, Comodo, D-TRUST, DigiCert, GoDaddy, Izenpe, SSC, Symantec, Trend Micro, and Opera. Mozilla abstained. There were none opposed. Therefore, Ballot 89 passes.

Motion

Rick Andrews made the following motion, and Ben Wilson and Kirk Hall endorsed it:

Motion begins

The CA/Browser Forum authorizes the publication of “Recommendations for the Processing of Extended Validation SSL Certificates, v. 2.0” (available here: Recommendations for the Processing of EV SSL Certificates.v.2.0).

Upon adoption, the words “Proposed Draft” will be removed from the document on the CA/Browser Forum Web site.

The ballot review period comes into effect today, 3 January 2014, at 2100 UTC and will close at 2100 UTC on Friday, 10 January 2014. Unless the motion is withdrawn during the review period, the voting period will start immediately thereafter and will close at 2100 UTC on Friday, 17 January 2014. Votes must be cast by posting an on-list reply to this thread.

Motion ends

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 one half or more of the votes cast by members in the browser category must be in favor. Also, at least six members must participate in the ballot, either by voting in favor, voting against, or abstaining.

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