Home » All CA/Browser Forum Posts » Ballot CSC-4 v1: Move deadline for transition to RSA-3072 and SHA-2 timestamp tokens

Ballot CSC-4 v1: Move deadline for transition to RSA-3072 and SHA-2 timestamp tokens

Voting on this ballot has closed. The results are below:

7 CAs voting in favor: Actalis, DigiCert, Entrust Datacard, GDCA, GlobalSign, GoDaddy, HARICA

0 CAs opposed

0 CAs abstaining

1 Certificate Consumer voting in favor: Microsoft

0 Certificate Consumers opposed

0 Certificate Consumers abstaining

Therefore the ballot passes.

Dean Coclin

CSCWG Chair

Ballot CSC-4 v1: Move deadline for transition to RSA-3072 and SHA-2 timestamp tokens

Purpose of the Ballot:

The current deadline for moving from RSA-2048 to RSA-3072 and from SHA-1 to SHA-2 for timestamp tokens falls on January 1, 2021, which is inconvenient due to code freezes due to the winter holidays. This ballot delays the deadline to June 1, 2021 for RSA-3072 and April 30, 2022 for SHA-2 timestamp tokens.

The following motion has been proposed by Tim Hollebeek of DigiCert, and endorsed by Ian McMillan of Microsoft and Hugh Mercer of GlobalSign.

Motion begins

This ballot modifies the “Baseline Requirements for the Issuance and Management of Publicly‐Trusted Code Signing Certificates“ version 2.0 according to the attached redline.

Motion ends

/uploads/baseline_requirements_for_the_issuance_and_management_of_code_signing.v.2.1.pdf

/uploads/baseline_requirements_for_the_issuance_and_management_of_code_signing.v.2.1_redline.pdf

The procedure for approval of this ballot is as follows:

Discussion (7+ days) Start Time: 2020-09-22, 12:45pm Eastern Time (US) End Time: 2020-09-29, 1:10pm Eastern Time (US)

Vote for approval (7 days) Start Time: 2020-09-29, 1:10pm Eastern Time (US) End Time: 2020-10-06, 1:10pm Eastern Time (US)

Latest releases

Server Certificate Requirements
SC-084: DNS Labeled With ACME Account ID Challenge (#566) - Mar 13, 2025

BRs release version 2.1.4

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