<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><span style="-webkit-text-stroke-color: rgb(0, 0, 0); -webkit-text-stroke-width: initial;" class="">Hi Tim,</span><div class=""><br class=""></div><div class="">Just a couple of comments on the proposed charter.</div><div class=""><br class=""></div><div class="">First, it doesn’t really matter what you call the working group. You could call it the “Meatloaf WG” if you wanted to, although that’s probably not a great name. What’s important is making sure what you want to cover is included in the scope of the charter. So, for example, if you called a proposed WG the “Email WG,” but the charter scope said nothing about email, the WG would not be able to work on email issues.</div><div class=""><br class=""></div><div class="">On the other hand, you could call the working group the “Meatloaf WG,” and include S/MIME and email in the charter scope, and then the WG could work on both. It’s all about what’s in the charter scope.</div><div class=""><br class=""></div><div class="">Also, you mention the “Code Signing WG” in the out of scope section. A bit too much blatant copying? ;-)</div><div class=""><br class=""></div><div class="">P.S. I’m not advocating naming WGs after food items.<br class=""><div class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="" style="color: rgb(0, 0, 0); font-size: 12px; font-style: normal; font-variant-ligatures: normal; font-variant-position: normal; font-variant-caps: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; font-family: Helvetica; line-height: normal;"><br class=""></div><div class="" style="color: rgb(0, 0, 0); font-size: 12px; font-style: normal; font-variant-ligatures: normal; font-variant-position: normal; font-variant-caps: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; font-family: Helvetica; line-height: normal;"><span class="" style="orphans: 2; widows: 2;"><br class=""></span></div><div class="" style="color: rgb(0, 0, 0); font-size: 12px; font-style: normal; font-variant-ligatures: normal; font-variant-position: normal; font-variant-caps: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; font-family: Helvetica; line-height: normal;"><div style="margin: 0px; font-size: 14px; line-height: normal; -webkit-text-stroke-color: rgb(0, 0, 0); -webkit-text-stroke-width: initial;" class="">Best regards,</div><div style="margin: 0px; font-size: 14px; line-height: normal; -webkit-text-stroke-color: rgb(0, 0, 0); -webkit-text-stroke-width: initial; min-height: 17px;" class=""><br class=""></div><div style="margin: 0px; font-size: 14px; line-height: normal; -webkit-text-stroke-color: rgb(0, 0, 0); -webkit-text-stroke-width: initial;" class="">Virginia Fournier</div><div style="margin: 0px; font-size: 14px; line-height: normal; -webkit-text-stroke-color: rgb(0, 0, 0); -webkit-text-stroke-width: initial;" class="">Senior Standards Counsel</div><div style="margin: 0px; font-size: 14px; line-height: normal; -webkit-text-stroke-color: rgb(0, 0, 0); -webkit-text-stroke-width: initial;" class=""><span style="line-height: normal; font-family: 'Myriad Set Pro'; color: rgb(94, 94, 94); -webkit-text-stroke-color: rgb(94, 94, 94);" class=""></span> Apple Inc.</div><div style="margin: 0px; font-size: 14px; line-height: normal; -webkit-text-stroke-color: rgb(0, 0, 0); -webkit-text-stroke-width: initial;" class="">☏ 669-227-9595</div><div style="margin: 0px; font-size: 14px; line-height: normal; color: rgb(71, 135, 255); -webkit-text-stroke-color: rgb(71, 135, 255); -webkit-text-stroke-width: initial;" class=""><span style="color: rgb(0, 0, 0); -webkit-text-stroke-color: rgb(0, 0, 0);" class="">✉︎ <a href="mailto:vmf@apple.com" class=""><span style="-webkit-text-stroke-color: rgb(71, 135, 255);" class="">vmf@apple.com</span></a></span></div></div><div class="" style="color: rgb(0, 0, 0); font-size: 12px; font-style: normal; font-variant-ligatures: normal; font-variant-position: normal; font-variant-caps: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; font-family: Helvetica; line-height: normal;"><div class="" style="orphans: 2; widows: 2;"><div class=""><br class=""></div><div class=""><br class=""></div></div></div></div><br class="Apple-interchange-newline"></div><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">
</div>
<div><br class=""><div class="">On May 17, 2018, at 3:49 PM, <a href="mailto:public-request@cabforum.org" class="">public-request@cabforum.org</a> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Send Public mailing list submissions to<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span><a href="mailto:public@cabforum.org" class="">public@cabforum.org</a><br class=""><br class="">To subscribe or unsubscribe via the World Wide Web, visit<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>https://cabforum.org/mailman/listinfo/public<br class="">or, via email, send a message with subject or body 'help' to<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>public-request@cabforum.org<br class=""><br class="">You can reach the person managing the list at<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>public-owner@cabforum.org<br class=""><br class="">When replying, please edit your Subject line so it is more specific<br class="">than "Re: Contents of Public digest..."<br class=""><br class=""><br class="">Today's Topics:<br class=""><br class=""> 1. For Discussion: S/MIME Working Group Charter (Tim Hollebeek)<br class=""> 2. Re: For Discussion: S/MIME Working Group Charter (Tim Hollebeek)<br class=""><br class=""><br class="">----------------------------------------------------------------------<br class=""><br class="">Message: 1<br class="">Date: Thu, 17 May 2018 22:39:12 +0000<br class="">From: Tim Hollebeek <tim.hollebeek@digicert.com><br class="">To: CA/Browser Forum Public Discussion List <public@cabforum.org><br class="">Subject: [cabfpub] For Discussion: S/MIME Working Group Charter<br class="">Message-ID:<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span><BN6PR14MB1106B50F010C3C6130E302CC83910@BN6PR14MB1106.namprd14.prod.outlook.com><br class=""><span class="Apple-tab-span" style="white-space:pre"> </span><br class="">Content-Type: text/plain; charset="us-ascii"<br class=""><br class=""><br class=""><br class=""><br class=""><br class="">A rough first draft, based on text I blatantly stole from the Server<br class="">Certificate Working Group Charter and draft Code Signing Working Group<br class="">Charter:<br class=""><br class=""><br class=""><br class="">S/MIME Working Group Charter (should it be the Email Working Group, so it<br class="">can cover web-based mail as well?)<br class=""><br class=""><br class=""><br class="">Upon approval of the CAB Forum by ballot, the S/MIME Working Group ("Working<br class="">Group") is created to perform the activities as specified in this Charter,<br class="">subject to the terms and conditions of the CA/Browser Forum Bylaws and<br class="">Intellectual Property Rights (IPR) Policy, as such documents may change from<br class="">time to time. The definitions found in the Forum's Bylaws shall apply to<br class="">capitalized terms in this Charter. <br class=""><br class=""><br class=""><br class="">SCOPE: The authorized scope of the S/MIME Working Group shall be as follows:<br class=""><br class=""><br class=""><br class=""><br class="">1. To specify S/MIME Baseline Requirements, Extended Validation Guidelines,<br class="">Network and Certificate System Security Requirements, and other acceptable<br class="">practices for the issuance and management of code signing certificates used<br class="">to sign executables, libraries, and apps. <br class=""><br class=""><br class=""><br class="">2. To update such requirements and guidelines from time to time, in order to<br class="">address both existing and emerging threats, including responsibility for the<br class="">maintenance of and future amendments to the current S/MIME Baseline<br class="">Requirements, Extended Validation Requirements, and Network and Certificate<br class="">System Security Requirements. <br class=""><br class=""><br class=""><br class="">3. To perform such other activities that are ancillary to the primary<br class="">activities listed above. <br class=""><br class=""><br class=""><br class="">OUT OF SCOPE: The S/MIME Working Group will not address certificates<br class="">intended to be used primarily for client or server authentication, Code<br class="">Signing, VoIP, IM, or Web services. The Code Signing Working Group will not<br class="">address the issuance, or management of certificates by enterprises that<br class="">operate their own Public Key Infrastructure for internal purposes only, and<br class="">for which the Root Certificate is not distributed by any Application<br class="">Software Supplier. <br class=""><br class=""><br class=""><br class="">Anticipated End Date: None. <br class=""><br class=""><br class=""><br class="">Initial chairs and contacts: TBD<br class=""><br class=""><br class=""><br class="">Members eligible to participate: The Working Group shall consist of two<br class="">classes of voting members, the Certificate Issuers and the Certificate<br class="">Consumers. The CA Class shall consist of eligible Certificate Issuers and<br class="">Root Certificate Issuers meeting the following criteria: <br class=""><br class=""><br class=""><br class="">(1) Certificate Issuer: The member organization operates a certification<br class="">authority that has a current and successful WebTrust for CAs audit, or ETSI<br class="">TS 102042, ETSI 101456, or ETSI EN 319 411-1 audit report prepared by a<br class="">properly-qualified auditor, and that actively issues email certificates,<br class="">such certificates being treated as valid when verified by software from a<br class="">Certificate Consumer Member. Applicants that are not actively issuing<br class="">certificates but otherwise meet membership criteria 7 may be granted<br class="">Associate Member status under Bylaw Sec. 3.1 for a period of time to be<br class="">designated by the Forum. <br class=""><br class=""><br class=""><br class="">(2) Root Certificate Issuer: The member organization operates a<br class="">certification authority that has a current and successful WebTrust for CAs,<br class="">or ETSI TS 102042, ETSI TS 101456, ETSI EN 319 411-1 audit report prepared<br class="">by a properly-qualified auditor, and that actively issues email certificates<br class="">to subordinate CAs that, in turn, actively issue email certificates, such<br class="">certificates being treated as valid when verified by software from a<br class="">Certificate Consumer Member. Applicants that are not actively issuing<br class="">certificates but otherwise meet membership criteria may be granted Associate<br class="">Member status under Bylaw Sec. 3.1 for a period of time to be designated by<br class="">the Forum. <br class=""><br class=""><br class=""><br class="">(3) A Certificate Consumer can participate in this Working Group if it<br class="">produces a software product intended for use by the general public that can<br class="">validate S/MIME signatures attached to email messages. The Working Group<br class="">shall include Interested Parties and Associate Members as defined in the<br class="">Bylaws. Voting structure: In order for a ballot to be adopted by the Working<br class="">Group, two-thirds or more of the votes cast by the Certificate Issuers must<br class="">be in favor of the ballot and more than 50% of the votes cast by the<br class="">Certificate Consumers must be in favor of the ballot. At least one member of<br class="">each class must vote in favor of a ballot for it to be adopted. Quorum is<br class="">the average number of Member organizations (cumulative, regardless of Class)<br class="">that have participated in the previous three S/MIME Working Group Meetings<br class="">or Teleconferences (not counting subcommittee meetings thereof). If three<br class="">meetings have not yet occurred, quorum is ten (10). <br class=""><br class=""><br class=""><br class="">Summary of the work that the WG plans to accomplish: As specified in Scope<br class="">section above. <br class=""><br class=""><br class=""><br class="">Summary of major WG deliverables and guidelines: As specified in Scope<br class="">section above. <br class=""><br class=""><br class=""><br class="">Primary means of communication: listserv-based email, periodic calls, and<br class="">face-to-face meetings. <br class=""><br class=""><br class=""><br class="">IPR Policy: The CA/Browser Forum Intellectual Rights Policy, v. 1.3 or<br class="">later, SHALL apply to all Working Group activity.<br class=""><br class=""><br class=""><br class="">[1] Email BRs?<br class=""><br class=""><br class=""><br class="">-------------- next part --------------<br class="">An HTML attachment was scrubbed...<br class="">URL: <http://cabforum.org/pipermail/public/attachments/20180517/727d2b93/attachment-0001.html><br class="">-------------- next part --------------<br class="">A non-text attachment was scrubbed...<br class="">Name: smime.p7s<br class="">Type: application/pkcs7-signature<br class="">Size: 4940 bytes<br class="">Desc: not available<br class="">URL: <http://cabforum.org/pipermail/public/attachments/20180517/727d2b93/attachment-0001.p7s><br class=""><br class="">------------------------------<br class=""><br class="">Message: 2<br class="">Date: Thu, 17 May 2018 22:49:10 +0000<br class="">From: Tim Hollebeek <tim.hollebeek@digicert.com><br class="">To: Tim Hollebeek <tim.hollebeek@digicert.com>, "CA/Browser Forum<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>Public Discussion List" <public@cabforum.org><br class="">Subject: Re: [cabfpub] For Discussion: S/MIME Working Group Charter<br class="">Message-ID:<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span><BN6PR14MB1106063B28627FFB489D8E4B83910@BN6PR14MB1106.namprd14.prod.outlook.com><br class=""><span class="Apple-tab-span" style="white-space:pre"> </span><br class="">Content-Type: text/plain; charset="us-ascii"<br class=""><br class="">Oops, missed a spot:<br class=""><br class=""><br class=""><br class="">1. To specify S/MIME Baseline Requirements, Extended Validation Guidelines,<br class="">Network and Certificate System Security Requirements, and other acceptable<br class="">practices for the issuance and management of S/MIME certificates used to<br class="">sign and encrypt emails.<br class=""><br class=""><br class=""><br class="">-------------- next part --------------<br class="">An HTML attachment was scrubbed...<br class="">URL: <http://cabforum.org/pipermail/public/attachments/20180517/e549760d/attachment.html><br class="">-------------- next part --------------<br class="">A non-text attachment was scrubbed...<br class="">Name: smime.p7s<br class="">Type: application/pkcs7-signature<br class="">Size: 4940 bytes<br class="">Desc: not available<br class="">URL: <http://cabforum.org/pipermail/public/attachments/20180517/e549760d/attachment.p7s><br class=""><br class="">------------------------------<br class=""><br class="">Subject: Digest Footer<br class=""><br class="">_______________________________________________<br class="">Public mailing list<br class="">Public@cabforum.org<br class="">https://cabforum.org/mailman/listinfo/public<br class=""><br class=""><br class="">------------------------------<br class=""><br class="">End of Public Digest, Vol 73, Issue 80<br class="">**************************************<br class=""></div></div></div><br class=""></div></body></html>