<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>A rough first draft, based on text I blatantly stole from the Server Certificate Working Group Charter and draft Code Signing Working Group Charter:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>S/MIME Working Group Charter (should it be the Email Working Group, so it can cover web-based mail as well?)<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Upon approval of the CAB Forum by ballot, the S/MIME Working Group (“Working Group”) is created to perform the activities as specified in this Charter, subject to the terms and conditions of the CA/Browser Forum Bylaws and Intellectual Property Rights (IPR) Policy, as such documents may change from time to time. The definitions found in the Forum’s Bylaws shall apply to capitalized terms in this Charter. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>SCOPE: The authorized scope of the S/MIME Working Group shall be as follows: <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>1. To specify S/MIME Baseline Requirements, Extended Validation Guidelines, Network and Certificate System Security Requirements, and other acceptable practices for the issuance and management of code signing certificates used to sign executables, libraries, and apps. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>2. To update such requirements and guidelines from time to time, in order to address both existing and emerging threats, including responsibility for the maintenance of and future amendments to the current S/MIME Baseline Requirements, Extended Validation Requirements, and Network and Certificate System Security Requirements. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>3. To perform such other activities that are ancillary to the primary activities listed above. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>OUT OF SCOPE: The S/MIME Working Group will not address certificates intended to be used primarily for client or server authentication, Code Signing, VoIP, IM, or Web services. The Code Signing Working Group will not address the issuance, or management of certificates by enterprises that operate their own Public Key Infrastructure for internal purposes only, and for which the Root Certificate is not distributed by any Application Software Supplier. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Anticipated End Date: None. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Initial chairs and contacts: TBD<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Members eligible to participate: The Working Group shall consist of two classes of voting members, the Certificate Issuers and the Certificate Consumers. The CA Class shall consist of eligible Certificate Issuers and Root Certificate Issuers meeting the following criteria: <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>(1) Certificate Issuer: The member organization operates a certification authority that has a current and successful WebTrust for CAs audit, or ETSI TS 102042, ETSI 101456, or ETSI EN 319 411-1 audit report prepared by a properly-qualified auditor, and that actively issues email certificates, such certificates being treated as valid when verified by software from a Certificate Consumer Member. Applicants that are not actively issuing certificates but otherwise meet membership criteria 7 may be granted Associate Member status under Bylaw Sec. 3.1 for a period of time to be designated by the Forum. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>(2) Root Certificate Issuer: The member organization operates a certification authority that has a current and successful WebTrust for CAs, or ETSI TS 102042, ETSI TS 101456, ETSI EN 319 411-1 audit report prepared by a properly-qualified auditor, and that actively issues email certificates to subordinate CAs that, in turn, actively issue email certificates, such certificates being treated as valid when verified by software from a Certificate Consumer Member. Applicants that are not actively issuing certificates but otherwise meet membership criteria may be granted Associate Member status under Bylaw Sec. 3.1 for a period of time to be designated by the Forum. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>(3) A Certificate Consumer can participate in this Working Group if it produces a software product intended for use by the general public that can validate S/MIME signatures attached to email messages. The Working Group shall include Interested Parties and Associate Members as defined in the Bylaws. Voting structure: In order for a ballot to be adopted by the 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 S/MIME Working Group Meetings or Teleconferences (not counting subcommittee meetings thereof). If three meetings have not yet occurred, quorum is ten (10). <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Summary of the work that the WG plans to accomplish: As specified in Scope section above. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Summary of major WG deliverables and guidelines: As specified in Scope section above. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Primary means of communication: listserv-based email, periodic calls, and face-to-face meetings. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>IPR Policy: The CA/Browser Forum Intellectual Rights Policy, v. 1.3 or later, SHALL apply to all Working Group activity.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>[1] Email BRs?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>