Home » Working Groups » S/MIME Cert WG » Ballots

S/MIME Certificate Working Group Ballots

Ballots by Status

Voting Period

There are no ballots with the status "Voting Period" in the S/MIME Certificate Working Group

IPR Review Period

There are no ballots with the status "IPR Review" in the S/MIME Certificate Working Group

Discussion Period

There are no ballots with the status "Discussion Period" in the S/MIME Certificate Working Group

Draft / Under Consideration

There are no ballots with the status "New" in the S/MIME Certificate Working Group
There are no ballots with the status "Pre-Ballot" in the S/MIME Certificate Working Group

Passed

SMC016: Equivalence with Ballots SC096 and SC097
SMC015v2: Allow mDL for Authentication of Individual Identity
SMC014: DNSSEC for S/MIME
SMC013: Enable PQC Algorithms for S/MIME
SMC012: Introduce ACME for S/MIME
SMC011: Add EUID as Registration Reference
SMC010: Introduction of Multi-Perspective Issuance Corroboration
Forum-33: Election of CA/Browser S/MIME Certificate WG Vice Chair
SMC09: Pre-Linting, WebTrust for NetSec, and Minor Updates
Election Ballot Forum-27: Election of CA/B Forum S/MIME Certificate WG Chair
SMC08: Deprecate Legacy Generation Profiles and Minor Updates
SMC07: Align Logging Requirement and Key Escrow clarification
SMC06: Post implementation clarification and corrections
SMC05: Adoption of CAA for S/MIME
SMC04: Addition of ETSI TS 119 411-6 to audit standards
SMC03: Corrections and clarifications for “S/MIME Baseline Requirements”
SMC01: Final Guideline for “S/MIME Baseline Requirements"
SMC02: Confirmation Ballot for Vice Chair
SMCWG Chair Election / 2022

Cancelled

Ballot SMC017: Increase Minimum RSA CA Key Size

Failed

There are no ballots with the status "Ballot Failed" in the S/MIME Certificate Working Group

Information about Ballots

Latest releases

Server Certificate Requirements
SC099: Improve Recording of Validation Methods - May 19, 2026

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.14 - Ballot SMC016 - May 5, 2026

This ballot maintains consistency between the S/MIME Baseline Requirements and the TLS Baseline Requirements with changes introduced by Ballots SC096 and SC097. Specifically, this ballot: Creates a carve-out of the logging requirements for DNSSEC specifically, stating these are not in scope. For audit purposes, change management logging is able to confirm if the appropriate controls are in effect or not. Sunsets all remaining use of SHA-1 signatures in Certificates and CRLs. It is noted that most uses of SHA-1 signatures are already deprecated by SC097. With this ballot, all unexpired Subordinate CA Certificates issuing S/MIME containing the SHA-1 signature algorithm must be revoked. This proposal does not prohibit the use of SHA-1 to generate issuerKeyHash or issuerNameHash values as currently required by RFC 5019. Includes minor formatting corrections.

Network and Certificate System Security Requirements
Version 2.0.5 (Ballot NS-008) - Jul 9, 2025