CA/Browser Forum
Home » All CA/Browser Forum Posts » Ballot SMC010 - Introduction of Multi-Perspective Issuance Corroboration

Ballot SMC010 - Introduction of Multi-Perspective Issuance Corroboration

IPR Review of Ballot SMC010: Introduction of Multi-Perspective Issuance Corroboration

This Review Notice is sent pursuant to Section 4.1 of the CA/Browser Forum’s Intellectual Property Rights Policy (v1.3). This Review Period of 30 days is for one Final Maintenance Guidelines. The complete Draft Maintenance Guideline that is the subject of this Review Notice in red-line is at https://cabforum.org/2024/11/07/ballot-smc010-introduction-of-multi-perspective-issuance-corroboration/CA-Browser-Forum-SMIMEBR-1.0.8-Redline.pdf.

  • Start of Review Period: 1600 UTC on November 22, 2024

  • End of Review Period: 1600 UTC on December 22, 2024

Members with any Essential Claim(s) to exclude must forward a written Notice to Exclude Essential Claims to the Working Group Chair and also submit a copy to the CA/B Forum public mailing list (public at cabforum.org) before the end of the Review Period.

For details, please see the current version of the CA/Browser Forum Intellectual Property Rights Policy.

(An optional template for submitting an Exclusion Notice is available at https://cabforum.org/wp-content/uploads/Template-for-Exclusion-Notice.pdf)

Results of Ballot SMC010: Introduction of Multi-Perspective Issuance Corroboration

The voting period for SMC010: Introduction of Multi-Perspective Issuance Corroboration has completed. The ballot has: PASSED

Voting Results

Certificate Issuers

16 votes in total:

  • 16 voting YES: Actalis S.p.A., Chunghwa Telecom, DigiCert, Disig, eMudhra, Entrust, GlobalSign, HARICA, IdenTrust, Logius PKIoverheid, OISTE Foundation, SECOM Trust Systems, Sectigo, SwissSign, TWCA, VikingCloud
  • 0 voting NO:
  • 0 ABSTAIN:

Certificate Consumers

4 votes in total:

  • 4 voting YES: Apple, Google, Mozilla, rundQuadrat
  • 0 voting NO:
  • 0 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.
  • The quorum was 11 for this ballot. This requirement was MET.

This ballot now enters the IP Rights Review Period to permit members to review the ballot for relevant IP rights issues. This will be notified in a separate email.

Ballot SMC010: Introduction of Multi-Perspective Issuance Corroboration

Summary:

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

— Motion Begins —

This ballot modifies the “Baseline Requirements for the Issuance and Management of Publicly-Trusted S/MIME Certificates” (“S/MIME Baseline Requirements”), based on Version 1.0.6. MODIFY the Baseline Requirements as specified in the following Redline:

https://github.com/cabforum/smime/compare/c66dfe265f5fabf70150af68746d5cb9ba09f942..f61d2cd692eaa32c4624418324bcace8411e4a17

— Motion Ends —

This ballot proposes a Final Maintenance Guideline. This ballot does not conflict with the contents of Ballot SMC09 (see https://cabforum.org/2024/10/09/ballot-smc09-pre-linting-webtrust-for-netsec-and-minor-updates/) which is also based on Version 1.0.6 and has not been fully approved. The procedure for approval of this ballot is as follows:

Discussion (at least 7 days)

  • Start time: November 7, 2024 at 12:00:00 UTC
  • End time: November 14, 2024 at 14:00:00 UTC

Vote for approval (7 days):

  • Start time: November 14, 2024 at 20:00:00 UTC
  • End time: November 21, 2024 at 20:00:00 UTC

IPR Review (30 days)

Latest releases
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.7 - Ballot SMC09 - Nov 25, 2024

This ballot includes updates for the following: • Require pre-linting of leaf end entity Certificates starting September 15, 2025 • Require WebTrust for Network Security for audits starting after April 1, 2025 • Clarify that multiple certificatePolicy OIDs are allowed in end entity certificates • Clarify use of organizationIdentifer references • Update of Appendix A.2 Natural Person Identifiers This ballot is proposed by Stephen Davidson (DigiCert) and endorsed by Clint Wilson (Apple) and Martijn Katerbarg (Sectigo).

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