Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updates to Code Signing Charter #40

Open
wants to merge 9 commits into
base: main
Choose a base branch
from
12 changes: 8 additions & 4 deletions CSCWG-charter.md
@@ -1,4 +1,4 @@
# Code-Signing Working Group Charter - Version 1.0
# Code-Signing Working Group Charter - Version 1.1

## Introduction

Expand Down Expand Up @@ -40,6 +40,8 @@ i. Certificate issuance and revocation

j. CA operational practices, physical/logical security, etc.

Additionally, the authorized scope of the CSCWG SHALL be to discuss, adopt, and maintain policies, frameworks and sets of standard related to the issuance of management of timestamp certificates by third-party Certificate Issuers under a publicly trusted root, limited to timestamp certificates containing a Certificate Policy Identifier value of "2.23.140.1.4.2" in their certificatePolicies extension.

The CSCWG SHALL exercise caution to ensure that its work product does not impede the issuance of other EKU types.

### 2. Out of Scope
Expand Down Expand Up @@ -140,9 +142,11 @@ Votes cast before the announcement of a Member’s suspension will stand.

#### 5.1 Voting Structure

The rules described in Bylaw 2.3 and 2.4 SHALL apply to all ballots, including Draft Guideline Ballots.
The rules described in the latest CA/Browser Forum Bylaws SHALL apply to all ballots, including Draft Guideline Ballots.

In order for a ballot to be adopted by the Code Signing Certificates Working Group, two-thirds or more of the votes cast by the Certificate Issuers must be in favor of the ballot and more than 50% of the votes cast by the Certificate Consumers must be in favor of the ballot. At least one member of each class must vote in favor of a ballot for it to be adopted.

In order for a ballot to be adopted by the Code Signing Certificates Working Group, two-thirds or more of the votes cast by the Certificate Issuers must be in favor of the ballot and more than 50% of the votes cast by the Certificate Consumers must be in favor of the ballot. At least one member of each class must vote in favor of a ballot for it to be adopted. Quorum is the average number of Member organizations (cumulative, regardless of Class) that have participated in the previous three (3) Code Signing Certificate Working Group Meetings or Teleconferences (not counting subcommittee meetings thereof). For transition purposes, if three (3) meetings have not yet occurred, quorum is three (3).
Quorum is defined as more than half the average number of Voting Members that have participated in the previous three (3) Code Signing Certificate Working Group Meetings or Teleconferences (not counting subcommittee meetings thereof).

#### 5.2 Other Organizational Matters

Expand All @@ -166,4 +170,4 @@ The deliverables of the CSCWG are defined in the Scope section above.

As with all Forum Working Group activity, the IPR Policy, v1.3 or later, SHALL apply to all activities and work of the CSCWG. All Participants in the CSCWG SHALL have on file with the Forum a valid, signed IPR Policy Agreement (v.1.3). A previously submitted IPR Policy Agreement (v1.3) by an existing Member of the Forum shall suffice as meeting the obligation under section 4.5 of the IPR Policy that a Participant in the CSCWG commit to CAB Forum License requirements.

In accordance with the Forum’s antitrust policy, an antitrust compliance statement SHALL be read at the start of all Working Group Meetings, in substantially the form written in Bylaw 1.3.
In accordance with the Forum’s antitrust policy, an antitrust compliance statement SHALL be read at the start of all Working Group Meetings, in substantially the form written in Bylaw 1.3.