CA/Browser Forum
Home » All CA/Browser Forum Posts » Ballot SC61v4 – New CRL Entries must have a Revocation Reason Code

Ballot SC61v4 – New CRL Entries must have a Revocation Reason Code

Voting Results

Certificate Issuers 24 votes total, with no abstentions:

  • 24 Issuers voting YES: iTrusChina, HARICA, Telia, D-Trust, Digicert, Entrust, OISTE, NAVER Cloud, eMudhra, GlobalSign, Fastly, Chunghwa Telecom, SwissSign, SECOM, Buypass, VikingCloud, JPRS, Disig, GDCA, Izenpe, CFCA, Certum, Goddaddy, Let’s Encrypt
  • 0 Issuers voting NO
  • 0 Issuers ABSTAIN

Certificate Consumers 3 votes total, with no abstentions:

  • 3 Consumers voting YES: Microsoft, Google, Mozilla
  • 0 Consumers voting NO
  • 0 Consumers ABSTAIN

Bylaws Requirements

  1. Bylaw 2.3(6) requires:
  • In order for a ballot to be adopted by the Forum, two‐thirds (2/3) or more of the votes cast by the Voting Members in the Certificate Issuer category must be in favour of the ballot. This requirement was MET.
  • at least fifty percent (50%) plus one (1) of the votes cast by the Voting Members in the Certificate Consumer category must be in favour of the ballot. This requirement was MET.
  • At least one (1) Voting Member in each category must vote in favour of a ballot for the ballot to be adopted. This requirement was MET.
  1. Bylaw 2.3(7) requires:
  • A ballot result will be considered valid only when more than half of the number of currently active Voting Members has participated. The number of currently active Voting Members is the average number of Voting Member organizations that have participated in the previous three (3) Forum Meetings and Forum Teleconferences.
  • Half of the currently active members at the start of voting was 13, so the quorum was 14 for this ballot. This requirement was MET.

Ballot Contents

Purpose of Ballot SC-061 v.4 The purpose of this ballot is to modify sections 4.9.1.1 and 7.2.2 of the Baseline Requirements to incorporate the CRL reason codes that Mozilla has adopted in section 6.1.1 of the Mozilla Root Store Policy. The following motion has been proposed by Ben Wilson of Mozilla and endorsed by David Kluge of Google Trust Services and Kiran Tummala of Microsoft.

Motion Begins

This ballot modifies sections 4.9.1.1 and 7.2.2 of the “Baseline Requirements for the Issuance and Management of Publicly-Trusted Certificates” as defined in the following redline, based on Version 1.8.6:

https://github.com/cabforum/servercert/compare/e87bc5fcf35f533e58899311e538e6ffe959102e

Motion Ends

This ballot proposes a Final Maintenance Guideline. The procedure for approval of this ballot is as follows:

Discussion (7+ days)

Start Time: February 8, 2023 03:00 UTC

End Time: Not before February 15, 2023 03:00 UTC

Vote for approval (7 days)

Start Time: February 15, 2023 04:00 UTC

End Time: February 22, 2023 04:00 UTC

Ballot Status

This ballot now enters the IP Rights Review Period to permit members to review the ballot for relevant IP rights issues.

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