I am proposing the following ballot – are there two endorsers?  If we move soon 
on this, we can get this ballot approved before October 3, and there will be no 
lapse for these two Subcommittees.

(Note: I considered also converting the Governance Change Working Group to a 
Subcommittee, but it doesn’t belong as a Subcommittee of the SCWG, and our 
Bylaws do not permit Subcommittees of the Forum itself.  Also, Dimitris and Ben 
seem not to want to convert the Policy Working Group to a Subcommittee of the 
SCWG, so I have not included that.)

Ballot SC9 – Conversion of Validation and NetSec Working Groups to SCWG 
Subcommittees

Purpose of Ballot:

All Working Groups of the Forum will expire on October 3, 2018.  Bylaws 
Sections 5.3.1(e) and 5.3.4 allow any “Legacy” Working Groups (“LWG”) in 
existence when Bylaws v.1.9 was approved by the Forum to be converted to a 
Subcommittee of a Chartered Working Group pursuant to the procedures of Bylaws 
Section 5.3.1(e).

The Server Certificate Working Group wishes to convert the existing Validation 
Working Group and Network Security Working Group of the Forum into 
Subcommittees of the Server Certificate Working Group.

--- MOTION BEGINS ---

In accordance with Bylaws 5.3.1(e) and 5.3.4, the Server Certificate Working 
Group (SCWG) hereby converts the following Legacy Working Groups of the 
CA/Browser Forum (CABF) to Subcommittees of the SCWG, effective upon approval 
of this ballot.  The current Chairs of the Legacy Working Groups shall become 
the initial Chairs of the SCWG Subcommittees.  There shall be no expiry date 
for either SCWG Subcommittee.

1. The Validation Working Group of the CABF is converted to the Validation 
Subcommittee of the SCWG.

2. The Network Security Working Group of the CABF is converted to the Network 
Security Subcommittee of the SCWG.

--- MOTION ENDS ---

The procedure for approval of this ballot is as follows:

Discussion (7 days)
Start Time: 2018-09-xx, 7:00 am Eastern Time
End Time: 2018-09-xx, 7:00 am Eastern Time

Vote for approval (7 days)
Start Time: 2018-09-xx, 7:00 am Eastern Time
End Time: 2018-09-xx, 7:00 am Eastern Time


***
Additional Information

Ballot 143 – Formalization of Validation Working Group (approved Feb 2015)
https://www.cabforum.org/wiki/143%20-%20Formalization%20of%20validation%20working%20group


The CA-Browser Forum formally establishes the Validation Working Group as an 
official working group of the CAB Forum, replacing the previous informal EV 
working group. The scope of this working group is to address issues arising 
under adopted CAB Forum standards related to the validation of certificate 
information and the inclusion of information in certificates.



Scope: The Validation Working Group will consider all matters relating to the 
validation and inclusion of information in certificates under adopted CAB Forum 
guidelines.



Deliverables: The Working Group shall produce one or more documents offering 
options to the Forum for validation within the scope defined above.


Ballot 203 – Formation of Network Security Working Group (approved June 2017)
https://www.cabforum.org/wiki/203%20-%20Formation%20of%20Network%20Security%20Working%20Group


Scope

1. Consider options for revising, replacing or scrapping the Network Security 
Guidelines.

Deliverables

1. A report with one or more proposals for the future of the Network Security 
Guidelines.

2. For proposals involving replacement, details of the availability and 
applicability of the proposed alternative, and what modifications if any would 
be needed to it in order to make it suitable for use.

3. For proposals involving revision, details of the revisions that are deemed 
necessary and how the document will be kept current in the future.

4. For proposals involving scrapping, an explanation of why this is preferable 
to either of the other two options.

5. If there are multiple proposals, optionally a recommendation as to which one 
to pursue and an associated timeline.

6. A form of ballot or ballots to implement any recommendations.



Expiry

The Working Group shall expire once the deliverables have been completed, or on 
2018-06-19, whichever happens first. The expiry date given above shall be 
automatically postponed by 1 year on 2018-05-19 ("postponement date") and each 
anniversary of the postponement date thereafter unless three or more members 
separately or jointly request on the Public Mail List, within one month prior 
to a particular postponement date, that expiry of this Working Group not be 
postponed in that instance.

Bylaws v1.9

5.3.1 Formation of Chartered Working Groups
(e) CWGs may establish any number of subcommittees within its own Working Group 
to address any of such CWG’s business (each, a “Subcommittee”). A CWG-created 
Subcommittee needs to be approved by the CWG itself according to the approval 
process set forth in the CWG charter, but approval of the Forum is not 
necessary. Subcommittees must exist under an approved CWG.

5.3.4 Legacy Working Groups
Any “Legacy” Working Groups (“LWG”) in existence when this Bylaws v.1.8 is 
approved by the Forum shall have the option of (a) converting to a Subcommittee 
under a CWG pursuant to Section 5.3.1(e), (b) immediately terminating, or (c) 
continuing in effect without change for 6 months following such approval. For 
an LWG to continue beyond such 6 months, it must have a charter approved as 
described in Section 5.3.1 above, as if it was a new Working Group.

_______________________________________________
Public mailing list
[email protected]
https://cabforum.org/mailman/listinfo/public

Reply via email to