CA/Browser Forum
Home » All CA/Browser Forum Posts » Ballot 137 – Voting Process Bylaw Amendment (Passed)

Ballot 137 – Voting Process Bylaw Amendment (Passed)

Ballot 137 – Voting Process Bylaw Amendment

Voting on Ballot 137 – Voting Process Bylaw Amendment closed on 16 October 2014.

The Chair received “yes” votes from Certinomis, Chunghwa Telecom, Comodo, DigiCert, Disig, Entrust, GlobalSign, GoDaddy, Kamu Sertifikasyon Merkezi, Microsoft, Mozilla, Opentrust, Opera, SECOM, SSC, SttartCom, Symantec, Trend Micro, TURKTRUST, TWCA, and WoSign.

Actalis, ANF, Buypass, Google, Izenpe, and Logius PKIoverheid abstained.

Therefore, Ballot 137 passed.

Ben Wilson proposed the following ballot and Moudrick Dadashov of SSC and Dean Coclin of Symantec have endorsed it.

Reason: The reason for this ballot is to clarify the election process followed by the Forum in selecting new officers.

- Motion Begins –

In Section 4.1 of the Bylaws,

  • add a subheading for the first paragraph, to read as follows: **“(a) Term of office:” **

  • amend the subsequent paragraphs as follows:

(b) Manner of conducting nominations:

At least sixty (60) days prior to the Upon expiration or early termination of the current Chair’s term or upon his/her early termination as Chair, the Chair or Vice Chair will announce through the management mailing list that nominations are open for the office of Chair and the Vice Chair will automatically be nominated as to become the next Chair, but Forum Members may nominate themselves or others to be additional candidates as Chair. A Vice Chair may decline the nomination to the office of Chair and/or indicate an intent to seek nomination for re-election to the office of Vice Chair. The nomination period for Chair will last for at least one week but no longer than four weeks. Upon the close of the nominations for Chair, the nomination period for the office of Vice Chair shall immediately open. The nomination period for Vice Chair will last for at least one week but no longer than four weeks.

(c) Manner of holding officer elections:

If a single individual is nominated for a position, the Forum will hold a ballot to confirm appointment of the nominee. For the confirmation ballot, each Forum Member is entitled to a single vote regardless of the number of participating Forum Member representatives or whether the Forum Member is categorized as a CA or product supplier. If multiple votes are received from a Forum Member’s representatives, the last vote submitted during the voting period is considered the Forum Member’s vote. The single nominee is considered confirmed if a majority of the Forum members who vote are in favor of the appointment, regardless of the number of votes cast and irrespective of whether 2/3 of the CAs or 1/2 of the product suppliers approve appointment of the nominee.

If more than one candidate is nominated for Chair or Vice Chair, the Forum will announce an election ballot to determine which candidate will fill the position. upon close of nominations, Within two weeks after the close of the nomination period, the Chair or Vice Chair will establish an election committee and announce the election ballot on the management mailing list along with the ballot start date, ballot end date, and a description of the voting process. The Chair or Vice Chair will appoint the election committee by selecting at least two volunteers who have a reputation for independence, preferably individuals without voting rights in the Forum and that participate as Interested Parties. The election committee is responsible solely for tallying Forum Member votes in connection with the election ballot. The description must include the email address(es) where members will send their vote, which should be the email addresses of the election committee. ballot will be held in the regular manner to select the new Chair. If the election of a new Chair means the office of Vice Chair becomes vacant, the Members may nominate themselves or other candidates to the office of Vice Chair, and a ballot will be held in the regular manner to elect the new Vice Chair.

For election ballots, each Forum Member is entitled to a single vote regardless of the number of participating Forum Member representatives or whether the Forum Member is categorized as a CA or product supplier. If multiple votes are received from a Forum Member’s representatives, the last vote submitted during the voting period is considered the Forum Member’s vote. Within two weeks after the election ballot closes, the election committee will compile the votes, ensure that only one vote is counted per Forum Member, confirm the results with other members of the election committee, and publish the ballot results by sending an email to the public mailing list. The election committee will not include any votes submitted before or after the voting period when compiling the votes. The ballot results email will contain only the following information: a short description of the ballot purpose, the total number of votes submitted during the ballot period, and the name of the nominee receiving the most votes. The election committee may include other language as necessary to accurately describe the ballot and any concerns the election committee had with the ballot, provided that such language does not disclose how individual Forum Members voted. The election committee will treat the votes of individual Forum Members as confidential information. The nominee receiving the most votes is appointed to the applicable position, regardless of the number of votes cast and irrespective of whether 2/3 of the CAs or ½ of the product suppliers voted for the nominee. If the election ballot results in a tie among the candidates receiving the most votes, the Chair or Vice Chair will call for another election ballot that includes only the two tying candidates.

## Motion ends

The review period for this ballot shall commence at 2200 UTC on Thursday, 2 October 2014, and will close at 2200 UTC on Thursday, 9 October 2014. Unless the motion is withdrawn during the review period, the voting period will start immediately thereafter and will close at 2200 UTC on Thursday, 16 October 2014. Votes must be cast by posting an on-list reply to this thread.

A vote in favor 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. 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 greater than 50% 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 abstaining.

Latest releases
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.6 - Ballot SMC08 - Aug 29, 2024

This ballot sets a date by which issuance of certificates following the Legacy generation profiles must cease. It also includes the following minor updates: Pins the domain validation procedures to v 2.0.5 of the TLS Baseline Requirements while the ballot activity for multi-perspective validation is concluded, and the SMCWG determines its corresponding course of action; Updates the reference for SmtpUTF8Mailbox from RFC 8398 to RFC 9598; and Small text corrections in the Reference section

Network and Certificate System Security Requirements
v2.0 - Ballot NS-003 - Jun 26, 2024

Ballot NS-003: Restructure the NCSSRs in https://github.com/cabforum/netsec/pull/35

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).