← CABF Ballot Browser
Ballot-217 passed

Ballot 217 – Sunset RFC 2527

Server Certificate Working Group

Key dates

Effective date
31 May 2018 8 years ago
Voting opened
14 Dec 2017 8 years ago
Voting closed
21 Dec 2017 8 years ago
Discussion opened
07 Dec 2017 8 years ago
Discussion closed
14 Dec 2017 8 years ago

AI Summary

Generated 2026-06-23 21:25 UTC

Ballot overview

  • Ballot 217, Sunset RFC 2527, was a Server Certificate Working Group ballot.
  • The ballot passed.
  • It was intended to sunset the use of RFC 2527 and require RFC 3647-based structure for CP/CPS disclosures.

What changed

  • For the Baseline Requirements, Section 2.2 was revised so that:
    • The CA must publicly disclose its Certificate Policy and/or Certification Practice Statement online on a 24x7 basis.
    • The CA must publicly disclose business practices to the extent required by the selected audit scheme.
    • Effective as of 31 May 2018, the CP/CPS must be structured in accordance with RFC 3647.
    • Before 31 May 2018, the CP/CPS may be structured in accordance with either RFC 2527 or RFC 3647.
    • The CP/CPS must include all material required by RFC 3647, or by RFC 2527 if structured that way.
  • For the EV Guidelines, Section 8.2.2 was revised similarly so that:
    • The CA must publicly disclose its Certificate Policy and/or Certification Practice Statement online on a 24x7 basis.
    • The CA must publicly disclose business practices to the extent required by the selected audit scheme.
    • Effective as of 31 May 2018, the CP/CPS must be structured in accordance with RFC 3647.
    • Before 31 May 2018, the CP/CPS may be structured in accordance with either RFC 2527 or RFC 3647.
    • The CP/CPS must include all material required by RFC 3647, or by RFC 2527 if structured that way.

Voting and approval

  • Voting by CAs: 15 yes votes, 0 no votes, 0 abstain.
  • Voting by browsers: 4 yes votes, 0 no votes, 0 abstain.
  • Quorum was met.
  • The approval thresholds were met for both CAs and browsers.
  • At least one CA member and one browser member voted in favor.

Timing

  • Discussion period: 2017-12-07 22:00:00 UTC to 2017-12-14 22:00:00 UTC.
  • Voting period: 2017-12-14 22:00:00 UTC to 2017-12-21 22:00:00 UTC.
  • The ballot page states the voting period had ended when the results were posted.
  • The motion text gives 31 May 2018 as the effective date for the RFC 3647 requirement.
Model: gpt-5.4-mini Confidence: 0.99 Result: passed
Effective date
2018-05-31
Voting opened
2017-12-14
Voting closed
2017-12-21
Discussion opened
2017-12-07
Discussion closed
2017-12-14
Applicability and conditions

2018-05-31 — By this date, CP/CPS disclosures must be structured in accordance with RFC 3647; before this date, RFC 2527 or RFC 3647 was permitted All CAs subject to the Baseline Requirements and EV Guidelines changes in this ballot

AI-generated from the CABF ballot page. The official CABF article remains the authoritative source.

Proposers

Ryan Sleevi of Google and endorsed by Tim Hollebeek of DigiCert and Dimitris Zacharopoulos of HARICA.

Excerpt

SearchHome » All CA/Browser Forum Posts » Ballot 217 – Sunset RFC 2527Ballot 217 – Sunset RFC 2527The voting period for Ballot 217 has ended and the ballot has passed. Here are the results.

View on cabforum.org → Last fetched 16 hours ago

We use only essential cookies and local browser storage for preferences and security. See our Privacy Policy for details.

Confirm action