← CABF Ballot Browser
Ballot-199 passed

Ballot 199 – Require commonName in Root and Intermediate Certificates

Server Certificate Working Group

Key dates

Effective date
08 Jun 2017 9 years ago
Voting opened
02 May 2017 9 years ago
Voting closed
09 May 2017 9 years ago
Discussion opened
25 Apr 2017 9 years ago
Discussion closed
02 May 2017 9 years ago

AI Summary

Generated 2026-06-23 21:32 UTC

Ballot overview

  • Ballot 199, Require commonName in Root and Intermediate Certificates, proposes changes to the Baseline Requirements.
  • The purpose is to add a commonName requirement for Root CA Certificates and Subordinate CA Certificates, because the existing text for subject information did not fully specify required information.
  • The motion also renames and restructures sections covering subject information for subscriber certificates, root certificates, and subordinate CA certificates.

Proposed changes

  • Delete the existing subject information requirements in sections 7.1.2.1(e) and 7.1.2.2(h).
  • Rename section 7.1.4.2 to Subject Information – Subscriber Certificates.
  • Rename section 7.1.4.3 to Subject Information – Root Certificates and Subordinate CA Certificates.
  • Add a new section requiring these subject distinguished name fields for root and subordinate CA certificates:
    • subject:commonName must be present.
    • subject:organizationName must be present and contain either the Subject CA’s name or DBA as verified under Section 3.2.2.2.
    • subject:countryName must contain the two-letter ISO 3166-1 country code for the country where the CA’s place of business is located.

Ballot process and result

  • The ballot was in the voting period when described on the page.
  • The page states that the voting period ended on 9 May and that the ballot has passed.
  • Voting results shown on the page:
    • CAs: 14 yes, 1 no, 0 abstain
    • Browsers: 3 yes, 0 no, 0 abstain
  • The page states quorum was met and the approval thresholds were met for both CAs and browsers.
  • The page also states that if no Exclusion Notices are filed, the ballot becomes effective at the end of the Review Period.

Timing

  • Discussion: 25 Apr to 2 May
  • Vote for approval: 2 May to 9 May
  • Review Period: 30 days after filing of the Review Notice by the Chair
  • Effective date depends on the Review Period outcome and whether any Exclusion Notices are filed.
Model: gpt-5.4-mini Confidence: 0.93 Result: passed
Effective date
2017-06-08
Voting opened
2017-05-02
Voting closed
2017-05-09
Discussion opened
2017-04-25
Discussion closed
2017-05-02
Applicability and conditions

2017-06-08 — The ballot becomes effective at the end of the Review Period If the ballot is approved and no Exclusion Notices are filed during the 30-day Review Period after the Chair files the Review Notice

2017-05-09 — Vote on the ballot closes Voting period for approval

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

Proposers

Gervase Markham of Mozilla and endorsed by Patrick Tronnier of OATI and Ryan Sleevi of Google:

Excerpt

SearchHome » All CA/Browser Forum Posts » Ballot 199 – Require commonName in Root and Intermediate CertificatesBallot 199 – Require commonName in Root and Intermediate CertificatesResults on Ballot 199 – Require commonName in Root and Intermediate Certificates The voting period for Ballot 199 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