CA/Browser Forum
Home » All CA/Browser Forum Posts » Ballot SC25: Define New HTTP Domain Validation Methods v2

Ballot SC25: Define New HTTP Domain Validation Methods v2

BALLOT RESULTS

The voting period for Ballot SC25 has ended and the Ballot has Passed. Here are the results:

Voting by Certificate Issuers

24 votes total including abstentions

24 Yes votes: Actalis, Amazon, Buypass, Camerfirma, Certigna (DHIMYOTIS), Certum (Asseco), Chunghwa Telecom, D-TRUST, DigiCert, eMudhra, Entrust Datacard, Firmaprofesional, GDCA, GlobalSign, GoDaddy, HARICA, Izenpe, Let’s Encrypt, OISTE, SSL.com, SwissSign, TrustCor, SecureTrust (former Trustwave), TurkTrust – 0 No votes: – 0 Abstain:

100% of voting Certificate Issuers voted in favor.

Voting by Certificate Consumers

  • 5 votes total including abstentions*

5 Yes votes: Apple, Cisco, Google, Microsoft, Mozilla – 0 No votes: – 0 Abstain:

100% of voting Certificate Consumers voted in favor.

Relevant Bylaw references

Bylaw 2.3(f) requires:

– a “yes” vote by two-thirds of Certificate Issuer votes and 50%-plus-one Certificate Consumer votes for approval. Votes to abstain are not counted for this purpose. This requirement was met for both Certificate Issuers and 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 also met.

Under Bylaw 2.3(g), “a ballot result will be considered valid only when more than half of the number of currently active Members has participated”. Votes to abstain are counted in determining a quorum. Half of currently active Members as of the start of voting was 10, so quorum was 11 votes – quorum was met.”

Ballot SC25: Define New HTTP Domain Validation Methods v2

**Purpose of Ballot: **

This ballot sets a sunset date for the current Method 6 and defines two new Domain Validation methods. One is intended to replace Method 6 (Agreed-Upon Change to Website) and the other that describes the ACME HTTP method defined in section 8.3 of RFC 8555.

The following motion has been proposed by Doug Beattie of GlobalSign and endorsed by Jacob Hoffman-Andrews of Lets Encrypt and Bruce Morton of Entrust.

  • -MOTION BEGINS-*

This ballot modifies the “Baseline Requirements for the Issuance and Management of Publicly-Trusted Certificates” as defined in the following redline, based on Version 1.6.7:

https://github.com/dougbeattie/documents/commit/bb90ff37c4bc043636229138d992 3fcff670cdfc#diff-7f6d14a20e7f3beb696b45e1bf8196f2

  • -MOTION ENDS-*

This ballot proposes a Final Maintenance Guideline.

The procedure for approval of this ballot is as follows:

Discussion (7+ days)

Start Time: 17-January 2020 09:00 Eastern

End Time: Not before 24-January 2020 09:00 Eastern

Vote for approval (7 days)

Start Time: 24-January 2020 12:30 Eastern

End Time: 31-January 2020 12:30 Eastern

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.6 - Ballot SMC08 - Aug 29, 2024

This ballot sets a date by which issuance of certificates following the Legacy generation profiles must cease. It also includes the following minor updates: Pins the domain validation procedures to v 2.0.5 of the TLS Baseline Requirements while the ballot activity for multi-perspective validation is concluded, and the SMCWG determines its corresponding course of action; Updates the reference for SmtpUTF8Mailbox from RFC 8398 to RFC 9598; and Small text corrections in the Reference section

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