Ballot 146 – Convert Baseline Requirements to RFC 3647 Framework

Ballot 146 – Convert Baseline Requirements to RFC 3647 Framework

Voting has closed on Ballot 146, “Convert Baseline Requirements”

Among CAs, there were 18 YES votes, 1 NO vote and 2 Abstentions Among Browsers, there was 1 YES vote and 1 Abstention

Therefore, the ballot passes.

Here are Version 1.3.0 and a helpful Conversion Table

The Certificate Policy Review Working Group was chartered by Ballot 128 to (i) consider existing and proposed standards, (ii) create a list of potential improvements based on the considered standards that improve the existing CAB Forum work product, (iii) evaluate the transition to a 3647 format based on the amount [of work involved]. One deliverable of the CP Review WG was to propose a ballot to improve CA infrastructure based on existing standards and documents and recommend whether to finish the 3647 conversion presented by Jeremy Rowley in January 2014.

The CP Review WG has met and concluded that the best path forward for the Forum is to complete a conversion to the RFC 3647 for the Baseline Requirements with an initial step that merely moves existing content from the Baseline Requirements into the RFC 3647 format.

Attached is the RFC-3647-formatted Baseline Requirements for the Issuance and Management of Publicly-Trusted Certificates.

CAB Forum BR 1.3.0– updated based on passage of Ballot 148 – CA Browser Forum Baseline Requirements – Ballot 146

Ben Wilson of DigiCert made the following motion, Tim Hollebeek from Trustwave and Jody Cloutier from Microsoft have endorsed it.

Motion Begins

Be it resolved that the CA / Browser Forum adopts the attached CA/B Forum Baseline Requirements for the Issuance and Management of Publicly-Trusted Certificates, v.1.3.0, effective upon adoption.

Motion Ends

The review period for this ballot shall commence at 2200 UTC on Thursday 2 April 2015 and will close at 2200 UTC on Thursday 9 April 2015, unless the comment period is further extended an additional week during the regular fortnightly CA/B Forum call earlier on that date. Otherwise, unless the motion is withdrawn during the review period or the review period is otherwise extended, the voting period will start immediately thereafter and will close at 2200 UTC on Thursday 16 April 2015.

Votes must be cast by posting an on-list reply to this thread. A vote in favor of the ballot must indicate a clear ‘yes’ in the response. A vote against the ballot 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.

Voting members are listed here: . In order for the motion to be adopted, two thirds or more of the votes cast by members in the CA category and more than one half of the votes cast by members in the browser category must be in favor. Quorum is currently nine (9) members– at least nine members must participate in the ballot, either by voting in favor, voting against, or by abstaining for the vote to be valid.