Ballot 109 – Create SSL Performance Working Group(passed)

Ballot 109 – Create SSL Performance Working Group

Voting on Ballot 109 has closed. Seventeen voted in favor – Buypass, Comodo, DigiCert, Disig, GlobalSign, GoDaddy, QuoVadis, SECOM, SSC, StartCom, Symantec, Trustis , TURKTRUST, Google, Microsoft, Opera, and Mozilla. There were no abstentions and none opposed. Therefore, Ballot 109 passes.

Gervase Markham (Mozilla) made the following motion, endorsed by Rick Andrews from Symantec, Richard Wang from WoSign, Ben Wilson from DigiCert, and Ryan Hurst from GlobalSign:

— Motion begins —

The CAB Forum shall create a Working Group, to be known as the SSL Performance Working Group.

Scope: the Working Group shall consider all matters having a bearing on software deployments which use SSL and the Web PKI. Examples might include: certificate contents, choice of proposed ciphers, webserver configuration, and OCSP configuration.

Deliverables: the Working Group shall produce one or more documents giving best practice guidance for getting the best performance from a SSL deployment which uses the Web PKI while still providing acceptable levels of security. The expectation is that such documentation will be submitted to the Forum for publication as (a) non-binding Forum document(s).

Expiration Date: the Working Group shall expire twenty-seven months (“one EV”) from the passing of this resolution, unless extended by a further ballot of the Members, such a ballot to specify the extension period and any necessarily modifications of the scope and deliverables.

… Motion ends …

Voting starts at 2200 UTC on Monday, October 21, 2013. The voting period will close at 2200 UTC on Monday, October 28, 2013. During this period, if the ballot is modified for reasons other than to correct minor typographical errors, then the ballot will be deemed to have been withdrawn.

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. Also, quorum is currently six (6) members– at least six members must participate in the ballot, either by voting in favor, voting against, or by abstaining for the vote to be valid.

Check Also

Ballot CSC-19: Remove TLS BR References

Results of Review Period (Mailing list post is available here.) The IPR review period ended …