Ballot SC024v2: Fall Cleanup

Ballot overview

• Ballot SC024v2: Fall Cleanup proposed minor, non-normative cleanup changes to the Baseline Requirements and the EV Guidelines.
• The stated goals included correcting typos, clarifying wording, removing obsolete effective dates and validation methods, updating algorithm-related requirements, and aligning references and formatting.
• The ballot text says it was based on Baseline Requirements version 1.6.6 and EV Guidelines version 1.7.0, with redlines linked in GitHub.

Voting result

• The ballot page states the voting period for Ballot SC24 had ended and the ballot has passed.
• Certificate Issuers: 24 yes, 0 no, 0 abstain.
• Certificate Consumers: 5 yes, 0 no, 0 abstain.
• The page states the bylaw approval requirements were met and quorum was met.

Main changes described

• Remove the overall 1 July 2012 effective date for the BRs.
• Correct the authorized port label from http to https.
• Fix typos such as contract to contact and assigns to assignees.
• Clarify that the Request Token should be documented in the CP/CPS or a referenced document.
• Move Request Token construction examples into the Request Token definition.
• Remove the definition of Test Certificate because it is no longer used.
• Correct acronyms and remove effective dates that are in the past.
• Remove validation methods that are no longer permitted.
• Align section 3.2.2.4 formatting and line spacing because the ballot was non-normative in impact.
• Replace unnecessarily gendered language with gender-neutral language.
• Clarify that usable OIDs in certificatePolicies are those documented by the CA, including CABF-defined OIDs for DV, OV, IV, and EV.
• Add the OID for organizationalUnitName to match the rest of the Subscriber DN documentation.
• Clean up algorithm requirements, including rewriting section 6.1.5 and partially rewriting section 7.1.3.
• Remove the now-expired grandfathering for OCSP responders.
• Standardize RFC 5280 references.
• In the EV Guidelines, unify references to the Baseline Requirements.

Dates

• The evidence does not provide explicit discussion, voting start, voting end, or IPR end dates.
• The ballot page does not state a normative effective date for a new requirement; it describes cleanup changes and removal of obsolete dates rather than introducing a new compliance deadline.