CA/Browser Forum
Home » All CA/Browser Forum Posts » Ballot 16- Unverified Content

Ballot 16- Unverified Content

Ballot 16- Unverified Content (Failed)

Motion

Stephen Davidson made the following motion, and Bruce Morton and Nick Hales endorsed it:

Motion begins

The Guidelines should be amended by the following erratum.

Erratum begins

“Insert the following new item in Section 6, EV Certificate Content Requirements.

(b) Other Subject Organization Information

EV Certificates SHALL NOT contain fields other than those defined in these Guidelines. Allowed EV Certificate fields SHALL NOT contain values other than those defined in these Guidelines. Notwithstanding the foregoing, organizationUnitName (OID 2.5.4.11) attributes MAY be included in the Subject field. The Guidelines do not place constraints on the values assigned to these OU attributes, however, the CA MUST ensure, using industry best practices, that these OU attributes are not misleading to the Relying Party.”

Erratum ends

Motion ends

The ballot review period comes into effect at 1700 EDT on (Friday) 11 July 2008, and will close at 1700EDT on (Friday) 18 July 2008. Unless the motion is withdrawn during the review period, the voting period will start immediately thereafter and will close at 1700 EDT on (Friday) 25 July 2008.

Votes must be cast by ‘reply all’ to this email.

A vote in favour of the motion must indicate a clear ‘yes’ in the response. A vote against must indicate a clear ‘no’ in the response. A vote to abstain must indicate a clear ‘abstain’ in the response. Unclear responses will not be counted.

The latest vote received from any representative of a voting member before the close of the voting period will be counted.

Latest releases
Server Certificate Requirements
SC099: Improve Recording of Validation Methods - May 19, 2026

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.14 - Ballot SMC016 - May 5, 2026

This ballot maintains consistency between the S/MIME Baseline Requirements and the TLS Baseline Requirements with changes introduced by Ballots SC096 and SC097. Specifically, this ballot: Creates a carve-out of the logging requirements for DNSSEC specifically, stating these are not in scope. For audit purposes, change management logging is able to confirm if the appropriate controls are in effect or not. Sunsets all remaining use of SHA-1 signatures in Certificates and CRLs. It is noted that most uses of SHA-1 signatures are already deprecated by SC097. With this ballot, all unexpired Subordinate CA Certificates issuing S/MIME containing the SHA-1 signature algorithm must be revoked. This proposal does not prohibit the use of SHA-1 to generate issuerKeyHash or issuerNameHash values as currently required by RFC 5019. Includes minor formatting corrections.

Unable to retrieve latest release information from the netsec repository.
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).