CA/Browser Forum
Home » All CA/Browser Forum Posts » Ballot SC42: 398-day Re-use Period

Ballot SC42: 398-day Re-use Period

Voting Results

The voting on SC42v2 has completed, and the ballot has passed.

Certificate Issuers

2****6 votes total, with no abstentions

· 24 Yes votes: Actalis, Amazon, Buypass, Certum (Asseco), CFCA, Chunghwa Telecom, D-TRUST, DigiCert, Disig, eMudhra, Entrust, Firmaprofesional, GDCA, GlobalSign, GoDaddy, HARICA, Izenpe, Let’s Encrypt/ISRG, Sectigo, SwissSign, Telia Company, TrustCor, SecureTrust, Visa, iTrusChina, Kamu SM

· 0 No Votes

· 0 Abstentions

Certificate Consumers

5 votes total, with no abstentions

  1. 5 Yes votes: Apple, Cisco, Google, Microsoft, Mozilla

  2. 0 No votes

  3. 0 Abstentions

Bylaw Requirements

  1. Bylaw 2.3(f) requires:
  • A “yes” vote by two-thirds of Certificate Issuer votes and by 50%-plus-one of Certificate Consumer votes. Votes to abstain are not counted for this purpose. This requirement was MET for Certificate Issuers and MET for Certificate Consumers.
  • at least one Certificate Issuer and one Certificate Consumer Member must vote in favor of a ballot for the ballot to be adopted. This requirement was MET.
  1. Bylaw 2.3(g) requires that a ballot result only be considered valid when “more than half of the number of currently active Members has participated”. Votes to abstain are counted in determining quorum. Half of the currently active members at the start of voting was 12, so the quorum was 13 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.

Ballot Text

Ballot SC42v2: 398-day IP Address and Domain Validation Reuse Period.

  • Type of Ballot:*

This is a ballot to adopt two Final Maintenance Guidelines which modify the Forum’s Baseline Requirements for the Issuance and Management of Publicly-Trusted Certificates (BRs) and the Guidelines for the Issuance and Management of Extended Validation Certificates (EVGs).

  • Purpose of Ballot:*

This ballot changes validation reuse periods for FQDN and IP Address validation to 398 days in section 4.2.1 of the BRs and for all purposes in section 11.14.3 of the EVGs. The ballot does not change the 825-day reuse period in section 4.2.1. of the BRs for Organizational Validation (OV) information.

Specifically:

  • It inserts as the last sentence in the third paragraph of BR section 4.2.1, “Effective 2021-10-01, for validation of Domain Names and IP Addresses according to Section 3.2.2.4 and 3.2.2.5, any reused data, document, or completed validation MUST be obtained no more than 398 days prior to issuing the Certificate.”

  • It replaces eight instances of “thirteen months” or “thirteen-month” in EVG section 11.14.3 with 398 days.

The following motion has been proposed by Ben Wilson of Mozilla and endorsed by Dimitris Zacharopoulos of HARICA and Chema Lopez of Firmaprofesional.

  • ## Motion begins*

This ballot modifies the “Baseline Requirements for the Issuance and Management of Publicly-Trusted Certificates” (“BRs”), based on Version 1.7.3:

Insert as the last sentence in the third paragraph of section 4.2.1 of the BRs, “Effective 2021-10-01, for validation of Domain Names and IP Addresses according to Section 3.2.2.4 and 3.2.2.5, any reused data, document, or completed validation MUST be obtained no more than 398 days prior to issuing the Certificate.” as illustrated in the following redline on GitHub:

https://github.com/cabforum/servercert/compare/9672b03bec91ad9a80f826e928e47f5c1f82964b…7cd105daf3baba01579c167d9fc10afacd49c503

This ballot modifies the “Guidelines for the Issuance and Management of Extended Validation Certificates” (“EVGs”) as follows, based on Version 1.7.4:

REPLACE all eight instances of “thirteen months” (or “thirteen-month”) in section 11.14.3 of the EVGs with 398 days and 398-day, respectively, as illustrated in the following redline on GitHub:

https://github.com/cabforum/servercert/compare/9672b03bec91ad9a80f826e928e47f5c1f82964b…7cd105daf3baba01579c167d9fc10afacd49c503

  • ## Motion ends*

This ballot proposes two Final Maintenance Guidelines.

The procedure for approval of this ballot is as follows:

  • Discussion (7+ days)*

Start Time: 2021-04-08 17:00:00 UTC

End Time: 2021-04-15 17:00:00 UTC

  • Vote for approval (7 days)*

Start Time: 2021-04-15 17:00:00 UTC

End Time: 2021-04-22 17:00:00 UTC

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