Ballot 161 – Notification of incorrect issuance

Ballot overview

• Ballot 161, Notification of incorrect issuance, proposed adding section 2.2.1 to the Baseline Requirements.
• The proposal required a CA that issues a certificate in violation of the requirements to publicly disclose a report within one week of becoming aware of the violation.
• A link to the report had to be sent at the same time to incidents@cabforum.org.
• Effective 01-Jul-16, the CA had to announce in its Certificate Policy and/or Certification Practice Statement where such reports would be found, and the location had to be as accessible as the CP/CPS.
• The report had to include details of the error, its cause, the time of issuance and discovery, and public certificates for all issuer certificates in the trust chain.
• For certificates issued prior to 01-Mar-16, the report could truncate Subject Distinguished Name fields and subjectAltName extension values to the registerable domain name.
• The report had to be made available to the CA’s Qualified Auditor for the next Audit Report.

Ballot process and result

• The review period was scheduled to commence at 2300 UTC on 29 January 2016 and close at 2300 UTC on 5 February 2016.
• The voting period was scheduled to start immediately after the review period and close at 2300 UTC on 12 February 2016.
• Voting on Ballot 161 closed on 12 February 2016.
• The results were 0 YES, 14 NO, and 5 Abstentions from the CAs, and 3 YES, 0 NO, and 0 Abstentions from the browsers.
• The ballot fails.

Outcome

• Because the ballot failed, it never became normative.
• The proposed effective date is not applicable as a compliance date.