Skip to content

Ballot SMC016: Equivalence with Ballots SC096 and SC097 #300

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
srdavidson wants to merge 11 commits into
base: main
Choose a base branch
from
+15 −7
Open

Ballot SMC016: Equivalence with Ballots SC096 and SC097 #300

Changes from all commits
Commits
Show all changes
11 commits
Select commit Hold shift + click to select a range
1fcc495
sc96
srdavidson Jan 12, 2026
ee19dbe
Disallow SHA-1 and require revocation
XolphinMartijn Feb 11, 2026
8cea59e
Merge pull request #16 from XolphinMartijn/sha1
srdavidson Feb 11, 2026
55b19f7
Typo
srdavidson Feb 11, 2026
6c3546f
Version
srdavidson Feb 20, 2026
b04ab93
Revision table
srdavidson Feb 20, 2026
1b144af
Additional compliance date
srdavidson Feb 20, 2026
a746c65
Additional compliance date
srdavidson Feb 20, 2026
ef3e159
Minor format changes
srdavidson Feb 25, 2026
2d0d61b
Updates from discussion
srdavidson Mar 10, 2026
32915d1
Shall consistency
srdavidson Mar 12, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 15 additions & 7 deletions SBR.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,11 +1,11 @@
---
title: Baseline Requirements for the Issuance and Management of Publicly-Trusted S/MIME Certificates
subtitle: Version 1.0.12
subtitle: Version 1.0.14
author:
- CA/Browser Forum
date: October 13, 2025
date: TBD
copyright: |
Copyright 2025 CA/Browser Forum
Copyright 2026 CA/Browser Forum
This work is licensed under the Creative Commons Attribution 4.0 International license.
---

Expand Down Expand Up @@ -90,7 +90,8 @@ The following Certificate Policy identifiers are reserved for use by CAs as a me
| 1.0.9 | SMC011 |Add EUID as Registration Reference | May 14, 2025 |
| 1.0.10 | SMC012 |ACME for S/MIME Automation | July 2, 2025 |
| 1.0.11 | SMC013 |Introduction of PQC Algorithms | August 22, 2025 |
| 1.0.12 | SMC013 |DNSSEC for CAA | October 13, 2025 |
| 1.0.12 | SMC014 |DNSSEC for CAA | October 13, 2025 |
| 1.0.14 | SMC016 |Equivalence with Ballots SC096 and SC097 | TBD |

\* Publication Date is the date the new version was published following the Intellectual Property Review.

Expand All @@ -108,6 +109,7 @@ The following Certificate Policy identifiers are reserved for use by CAs as a me
| 1.0.8 | SMC010 | SHOULD implement MPIC | March 15, 2025 |
| 1.0.8 | SMC010 | SHALL implement MPIC | May 15, 2025 |
| 1.0.12 | SMC014 | SHALL implement DNSSEC for CAA | March 15, 2026 |
| 1.0.14 | SMC016 | SHALL sunset all remaining use of SHA-1 in Certificates and CRLs | September 15, 2026 |

## 1.3 PKI participants

Expand Down Expand Up @@ -981,6 +983,8 @@ DNSSEC validation back to the IANA DNSSEC root trust anchor MAY be performed on

DNSSEC validation back to the IANA DNSSEC root trust anchor is considered outside the scope of self-audits performed to fulfill the requirements in [Section 8.7](#87-self-audits).

DNSSEC validation back to the IANA DNSSEC root trust anchor is considered outside the scope of the logging requirements of [Section 5.4.1](#541-types-of-events-recorded).

#### 4.2.2.2 Multi-perspective issuance corroboration

CAs SHOULD implement [Section 3.2.2.9](https://github.com/cabforum/servercert/blob/main/docs/BR.md#3229-multi-perspective-issuance-corroboration) of the TLS Baseline Requirements before March 15, 2025. Effective May 15, 2025 CAs SHALL implement [Section 3.2.2.9](https://github.com/cabforum/servercert/blob/main/docs/BR.md#3229-multi-perspective-issuance-corroboration) of the TLS Baseline Requirements. This optional delay to the Phased Implementation Timeline for MPIC is intended to assist S/MIME Certificate Issuers with no TLS MPIC obligations.
Expand Down Expand Up @@ -2092,6 +2096,10 @@ The CA SHALL NOT use a different algorithm, such as the id-RSASSA-PSS (OID: 1.2.

When encoded, the `AlgorithmIdentifier` for RSA keys SHALL be byte-for-byte identical with the following hex-encoded bytes: `300d06092a864886f70d0101010500`

Effective September 15, 2026 the CA SHALL NOT sign a certificate using a signature algorithm that incorporates SHA-1.

Prior to September 15, 2026 the CA SHALL revoke any unexpired Subordinate CA Certificate whose signature algorithm incorporates SHA-1.

##### 7.1.3.1.2 ECDSA

The CA SHALL indicate an ECDSA key using the id-ecPublicKey (OID: 1.2.840.10045.2.1) algorithm identifier. The parameters SHALL use the `namedCurve` encoding.
Expand Down Expand Up @@ -2130,7 +2138,7 @@ The CA SHALL indicate an ML-DSA key using one of the following algorithm identif

The parameters for ML-DSA keys SHALL be absent. The CA MUST NOT use HashML-DSA; only "pure" ML-DSA is permitted.

When encoded, the AlgorithmIdentifier for ML-DSA keys SHALL be byte-for-byte identical with the following hex-encoded bytes:
When encoded, the `AlgorithmIdentifier` for ML-DSA keys SHALL be byte-for-byte identical with the following hex-encoded bytes:

* For ML-DSA-44, `300b0609608648016503040311`.
* For ML-DSA-65, `300b0609608648016503040312`.
Expand All @@ -2146,7 +2154,7 @@ The CA SHALL indicate an ML-KEM key using one of the following algorithm identif

The parameters for ML-KEM keys SHALL be absent.

When encoded, the AlgorithmIdentifier for ML-KEM keys SHALL be byte-for-byte identical with the following hex-encoded bytes:
When encoded, the `AlgorithmIdentifier` for ML-KEM keys SHALL be byte-for-byte identical with the following hex-encoded bytes:

* For ML-KEM-512, `300b0609608648016503040401`.
* For ML-KEM-768, `300b0609608648016503040402`.
Expand Down Expand Up @@ -3000,4 +3008,4 @@ Following the Effective Date for v 1.0.0 of these Requirements (September 1, 202

On or after September 15, 2024, all newly-issued Publicly-Trusted end entity S/MIME Certificates SHALL be issued from S/MIME Subordinate CAs that are compliant with these Requirements.

For backwards compatibility, Extant S/MIME CA Certificates that share the same Public Keys with S/MIME Subordinate CAs that are compliant with these Requirements, or are no longer used for signing end entity S/MIME Certificates, are not required to be revoked.
For backwards compatibility, Extant S/MIME CA Certificates that share the same Public Keys with S/MIME Subordinate CAs that are compliant with these Requirements, or are no longer used for signing end entity S/MIME Certificates, are not required to be revoked, with the exception of the required revocation of any Certificate whose signature algorithm incorporates SHA-1 as described in [Section 7.1.3.1.1](#71311-rsa).
Loading