CA/Browser Forum posts
Posts by tag Ballot
Ballot 149 – Membership Criteria Clarification
July 10, 2015 by Ben WilsonVoting on Ballot 149 (Membership criteria clarification) has closed. The Forum received 17 YES votes from CA members: Buypass, Chungwa Telecom, Disig, Entrust, Globalsign, GoDaddy, HARICA, Logius PKIoverheid, OpenTrust, QuoVadis, SSC, Symantec, Trend Micro, Trustwave, TurkTrust, Visa and WoSign and 3 YES votes from Browser members: Google, Opera and Mozilla. Three Abstain votes were received from CA members Actalis, ANF, OATI. There were 0 NO votes. Therefore the ballot passes.
July 10, 2015 by Ben WilsonVoting on Ballot 149 (Membership criteria clarification) has closed. The Forum received 17 YES votes from CA members: Buypass, Chungwa Telecom, Disig, Entrust, Globalsign, GoDaddy, HARICA, Logius PKIoverheid, OpenTrust, QuoVadis, SSC, Symantec, Trend Micro, Trustwave, TurkTrust, Visa and WoSign and 3 YES votes from Browser members: Google, Opera and Mozilla. Three Abstain votes were received from CA members Actalis, ANF, OATI. There were 0 NO votes. Therefore the ballot passes.
Ballot 147 – Attorney Accountant Letter Changes
June 25, 2015 by Ben WilsonBallot 147 – Attorney-Accountant Letter Changes Voting on Ballot 147 has closed. Here are the results:
June 25, 2015 by Ben WilsonBallot 147 – Attorney-Accountant Letter Changes Voting on Ballot 147 has closed. Here are the results:
Ballot 146 – Convert Baseline Requirements to RFC 3647 Framework
April 16, 2015 by Ben WilsonBallot 146 – Convert Baseline Requirements to RFC 3647 Framework Voting has closed on Ballot 146, “Convert Baseline Requirements”
April 16, 2015 by Ben WilsonBallot 146 – Convert Baseline Requirements to RFC 3647 Framework Voting has closed on Ballot 146, “Convert Baseline Requirements”
Ballot 148 – Issuer Field Correction
April 2, 2015 by Ben WilsonVoting on Ballot 148, Issuer Field Correction, closed on 2 April 2015. We received 13 YES votes from CAs, 0 NO votes and 0 Abstentions We received 1 YES vote from Browsers, 0 NO votes and 0 Abstentions Therefore the ballot passes. Several votes were received after the ballot closed and were not counted. Full details are on the ballot tracking wiki. Ballot 148 resulted in the adoption of BRv1.2.5
April 2, 2015 by Ben WilsonVoting on Ballot 148, Issuer Field Correction, closed on 2 April 2015. We received 13 YES votes from CAs, 0 NO votes and 0 Abstentions We received 1 YES vote from Browsers, 0 NO votes and 0 Abstentions Therefore the ballot passes. Several votes were received after the ballot closed and were not counted. Full details are on the ballot tracking wiki. Ballot 148 resulted in the adoption of BRv1.2.5
Ballot 145 – Operational Existence for Government Entities
February 19, 2015 by Ben WilsonBallot 145 – Operational Existence for Government Entities Reason Because government entities aren’t operating as businesses, they are often not listed with a QIIS, especially immediately after the entity is created by either statute or order. The legal existence of these entities is verifiable through a QGIS, but this source in many countries (especially Arabic and African countries) does not always list a date of creation of these entities. Operational existence exists to ensure organizations aren’t fly-by-night scams/phishing entities. With government entities, these same risks are not present as they are created directly by government action.
February 19, 2015 by Ben WilsonBallot 145 – Operational Existence for Government Entities Reason Because government entities aren’t operating as businesses, they are often not listed with a QIIS, especially immediately after the entity is created by either statute or order. The legal existence of these entities is verifiable through a QGIS, but this source in many countries (especially Arabic and African countries) does not always list a date of creation of these entities. Operational existence exists to ensure organizations aren’t fly-by-night scams/phishing entities. With government entities, these same risks are not present as they are created directly by government action.
Ballot 144 – Validation rules for .onion names
February 18, 2015 by Ben WilsonBallot 144 – Validation Rules for .onion Names – passed with 6 Yes votes, 2 No votes and 13 Abstentions from the CAs and 3 Yes votes from the browsers. Detailed results are on the Forum’s ballot tracker (Ballot Results – Vote Tally at the bottom of the Ballots page on the Forum’s wiki). Ballot 144 reads as follows: Applicants want a CA-signed .onion address for several reasons, including: – Powerful web platform features are restricted to secure origins, which are currently not available to onion names (in part, because of the lack of IANA registration). Permitting EV certs for onion names will help provide a secure origin for the service, moving onion towards use of powerful web platform features.
February 18, 2015 by Ben WilsonBallot 144 – Validation Rules for .onion Names – passed with 6 Yes votes, 2 No votes and 13 Abstentions from the CAs and 3 Yes votes from the browsers. Detailed results are on the Forum’s ballot tracker (Ballot Results – Vote Tally at the bottom of the Ballots page on the Forum’s wiki). Ballot 144 reads as follows: Applicants want a CA-signed .onion address for several reasons, including: – Powerful web platform features are restricted to secure origins, which are currently not available to onion names (in part, because of the lack of IANA registration). Permitting EV certs for onion names will help provide a secure origin for the service, moving onion towards use of powerful web platform features.
Ballot 143 – Formalization of Validation Working Group
February 18, 2015 by Ben WilsonBallot 143 – Formalization of Validation Working Group Reason In order to address validation issues and inconsistencies in both the SSL Baseline Requirements and the EV Guidelines, the CAB Forum has held an informal working group previously referred to as the Extended Validation Working Group now known as the Validation Working Group, would like to modify its scope to include validation in the Baseline Requirements as well as the EV Guidelines.
February 18, 2015 by Ben WilsonBallot 143 – Formalization of Validation Working Group Reason In order to address validation issues and inconsistencies in both the SSL Baseline Requirements and the EV Guidelines, the CAB Forum has held an informal working group previously referred to as the Extended Validation Working Group now known as the Validation Working Group, would like to modify its scope to include validation in the Baseline Requirements as well as the EV Guidelines.
Ballot 142 – Elimination of EV Insurance Requirement
January 19, 2015 by Ben WilsonElimination of EV Insurance Requirement Voting on Ballot 142 closed on 19 January 2015.
January 19, 2015 by Ben WilsonElimination of EV Insurance Requirement Voting on Ballot 142 closed on 19 January 2015.
Ballot 141 – Elimination of EV Insurance Requirement; Financial Responsibility for Mis-Issued Certificates
January 19, 2015 by Ben WilsonBallot 141 – Elimination of EV Insurance Requirement; Financial Responsibility for Mis-Issued Certificates Voting on Ballot 141 closed on 19 January 2015.
January 19, 2015 by Ben WilsonBallot 141 – Elimination of EV Insurance Requirement; Financial Responsibility for Mis-Issued Certificates Voting on Ballot 141 closed on 19 January 2015.