<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="">Hi Kirk,<div class=""><br class=""></div><div class="">Yes, we can consider adding this to the IPR Policy for this ballot. But the problem is that every time something comes up, someone wants to add it to this ballot. This is part of the reason we’ve been working on this ballot for over a year and it’s still not done.</div><div class=""><br class=""></div><div class="">At some point, we have to call this ballot closed for new subject matter, new issues, and new changes. <b class="">Now is that point. </b> From this point forward we are not accepting anything new for Ballot 206. We will consider correcting typos, glaring errors, fake news, etc., but nothing substantive. Come on folks - we’ve been looking at these documents for over a year. We are not trying to boil the ocean with one ballot.</div><div class=""><br class=""></div><div class="">Any new issues, questions, changes, non-fake news, etc. that comes up from this point on will need to be held for another ballot. </div><div class=""><br class=""></div><div class="">Thanks for your help.<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;"><span class="" style="orphans: 2; widows: 2;"><span style="font-family: Arial; orphans: auto; widows: auto;" class=""><br class=""></span></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;"><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 Feb 4, 2018, at 6:01 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. Review Notices (Kirk Hall)<br class=""><br class=""><br class="">----------------------------------------------------------------------<br class=""><br class="">Message: 1<br class="">Date: Mon, 5 Feb 2018 02:00:56 +0000<br class="">From: Kirk Hall <Kirk.Hall@entrustdatacard.com><br class="">To: CA/Browser Forum Public Discussion List <public@cabforum.org><br class="">Subject: [cabfpub] Review Notices<br class="">Message-ID:<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span><f055926d98be4a7595504154057fd9dc@PMSPEX04.corporate.datacard.com><br class="">Content-Type: text/plain; charset="utf-8"<br class=""><br class="">Virginia ? we have been following the steps you listed below, and have been sending out ?Review Notices? since Ballot 190 that included the specific Ballot language in ?track changes? mode showing how our guidelines (BRs or EVGL) were amended by each Ballot ? I believed that this complied with our Bylaws shown below.<br class=""><br class="">Unfortunately, as Ryan pointed out a few days ago, our Review Notices can?t include just the specific Ballot language showing the changes that were made by the Ballot, but must include ?a complete draft of the Draft Guideline [i.e., the entire BR or EVGL document itself] that is the subject of such notice?. Oddly enough, the IPR Agreement language doesn?t allow the ?Draft Guideline? that is sent with the Review Notice to show what changes were made by the Ballot, so it?s not very helpful to Members for their IP review.<br class=""><br class="">As a result, I will be sending out revised Review Notices this week that include the entire ?Draft Guideline that is the subject of such notice? for the following ballots: Ballots 190, 191-193, 195-197, 199, 201, 204, 207, 210, 214-215, and 217. Because there were no Exclusion Notices filed last time in response to the Review Notices sent (except for Ballot 190, where royalty free licenses were granted), I doubt there will be any new Exclusion Notices submitted this time.<br class=""><br class="">As a separate matter, I note that the Governance Change Working Group is already working on an updated draft of our IPR Agreement. I suggest the WG consider changing IPRA Sec. 4.1 so that Review Notices for Final Maintenance Guidelines (our typical ballots) only provide the specific Guideline language that was changed by a Ballot (in ?track changes? mode), and not the entire Draft Guideline (i.e., don?t send the entire BR or EVGL document that doesn?t showing the changes made by the Ballot). That would seem more useful to Forum Members in reviewing a Review Notice for the purpose of providing Exclusion Notices.<br class=""><br class="">Here?s a further explanation.<br class=""><br class="">WHAT OUR BYLAWS SAY ABOUT BALLOTS AND REVIEW NOTICES<br class=""><br class="">Here are the relevant portions of what our Bylaws say about Ballots that propose a ?Final Maintenance Guideline? (something that amends the existing BRs or EVGL), which is different from a ?Final Guideline? (which is a whole new set of requirements in a new document):<br class=""><br class="">2.4 Requirements for Draft Guideline Ballots<br class="">This section applies to any ballot that proposes a Final Guideline or a Final Maintenance Guideline (a ?Draft Guideline Ballot?), all as defined under the Forum?s IPR Policy. Draft Guideline Ballots must comply with the following rules in addition to the requirements set forth in Section 2.3 above.<br class="">(a) A Draft Guideline Ballot will clearly indicate whether it is proposing a Final Guideline or a Final Maintenance Guideline. If the Draft Guideline Ballot is proposing a Final Guideline, such ballot will include the full text of the Draft Guideline intended to become a Final Guideline. If the Draft Guideline Ballot is proposing a Final Maintenance Guideline, such ballot will include a redline or comparison showing the set of changes from the Final Guideline section(s) intended to become a Final Maintenance Guideline, and need not include a copy of the full set of guidelines. ***<br class="">(b) [Discussion period details]<br class="">(c) [Voting period details]<br class=""><br class="">(d) [Announcement of vote result]<br class="">(e) If a Draft Guideline Ballot passes the Initial Vote, the Chair shall initiate, no later than the 3rd business day after the announcement of the Initial Vote results, the Review Period of 30 or 60 days, as applicable and as described in Section 4.1 of the IPR Policy. The Chair will initiate the Review Period by sending the Review Notice to both the Member Mail List and the Public Mail List. The Review Notice will clearly specify the open and close dates and times (with time zone) of the Review Period. [Vice Chair may do this if the Chair does not]<br class="">(f) [Chair to distribute any Exclusion Notices received]<br class="">(g) [Exclusion Notices must also be sent to the Public List]<br class=""><br class="">(h) If no Exclusion Notices are filed during the Review Period with respect to a Draft Guideline Ballot, then the results of the Initial Vote are automatically deemed to be final and approved, and Draft Guidelines then become either Final Guidelines or Final Maintenance Guidelines, as designated in the Draft Guidelines Ballot. The Chair will notify both the Member Mail List and the Public Mail List of the final approval within 3 business days, as well as update the Public Website of Final Guidelines and Final Maintenance Guidelines within 10 business days of the close of the Review Period.<br class="">(i) If Exclusion Notice(s) are filed during the Review Period [PAG created, etc.].<br class="">(j) [What to do if two overlapping Ballots amend the same sections]<br class=""><br class=""><br class="">WHAT OUR IPR AGREEMENT SAYS ABOUT BALLOTS AND REVIEW NOTICES<br class=""><br class="">Our IPR Agreement is largely consistent with the Bylaws, but includes this provision requiring the entire ?Draft Guideline? be part of the Review notice, as Ryan pointed out a few days ago. This means the entire updated BR or EVGL document, not showing what the Ballot changes were:<br class=""><br class="">IPR Agreement Sec. 4.1 - Review of Draft Specifications.<br class="">Prior to the approval of a CAB Forum Draft Guideline as a CAB Forum Final Guideline or Final Maintenance Guideline there shall be a review period during which Participants may exclude certain Essential Claims from CAB Forum RF Licenses. The CAB Forum Chair shall initiate the Review Period by distributing to each CAB Forum Participant a notice of review period and a complete draft of the Draft Guideline that is the subject of such notice (?Review Notice?). Each Participant on behalf of itself and its Affiliates shall have sixty (60) days following the date of the receipt of such Review Notice (?Review Period?) to review such Draft Guideline and consider any licensing obligations with respect to any Essential Claims that may be encompassed by such Draft Guideline. The approval of a CAB Forum Final Maintenance Guideline shall follow the same process except that the Review Period shall be thirty (30) days.<br class=""><br class=""><br class="">From: Public [mailto:public-bounces@cabforum.org] On Behalf Of Virginia Fournier via Public<br class="">Sent: Thursday, February 1, 2018 12:22 PM<br class="">To: public@cabforum.org<mailto:public@cabforum.org><br class="">Subject: [EXTERNAL][cabfpub] Review Notices<br class=""><br class="">I agree that some Review Notices that have been sent out may not comply with Section 2.4(e) of the Bylaws. The sequence of events is important, and there was a very thorough discussion about this sequence in connection with the ballot.<br class=""><br class="">A thumbnail sketch of the sequence:<br class=""><br class=""><br class=""> * 7-day discussion period<br class=""> * 7-day voting period<br class=""> * Ballot passes the Initial Vote (if it doesn?t, stop here).<br class=""> * Chair initiates Review Period (30 or 60 days) with Review Notice to Public and Member lists<br class=""> * If no exclusion notices are filed during the Review Period, then ballot is approved.<br class=""> * If there are exclusion notices filed during the Review Period, then ballot is not approved at that time, then PAG, etc.<br class=""><br class="">So, here?s the question, was a Review Notice sent out after a Ballot passed, and, if so, did the Review Notice include the correct information? If not, the Ballot was not properly approved, a new Review Notice will need to be sent out with the correct information, and participants will need to be given a new Review Period. Otherwise, the Ballot will not be ?approved? according to the Bylaws.<br class=""><br class="">Any questions about this?<br class=""><br class="">Best regards,<br class=""><br class="">Virginia Fournier<br class="">Senior Standards Counsel<br class="">? Apple Inc.<br class="">? 669-227-9595<br class="">?? vmf@apple.com<mailto:vmf@apple.com><br class=""><br class=""><br class=""><br class=""><br class=""><br class="">On Feb 1, 2018, at 10:33 AM, public-request@cabforum.org<mailto:public-request@cabforum.org> wrote:<br class=""><br class="">Send Public mailing list submissions to<br class=""> public@cabforum.org<mailto:public@cabforum.org><br class=""><br class="">To subscribe or unsubscribe via the World Wide Web, visit<br class=""> https://cabforum.org/mailman/listinfo/public<br class="">or, via email, send a message with subject or body 'help' to<br class=""> public-request@cabforum.org<mailto:public-request@cabforum.org><br class=""><br class="">You can reach the person managing the list at<br class=""> public-owner@cabforum.org<mailto: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. Re: Public Digest, Vol 69, Issue 118 (Ryan Sleevi)<br class=""><br class=""><br class="">----------------------------------------------------------------------<br class=""><br class="">Message: 1<br class="">Date: Thu, 1 Feb 2018 13:32:15 -0500<br class="">From: Ryan Sleevi <sleevi@google.com<mailto:sleevi@google.com>><br class="">To: Kirk Hall <Kirk.Hall@entrustdatacard.com<mailto:Kirk.Hall@entrustdatacard.com>>, "CA/Browser Forum<br class=""> Public Discussion List" <public@cabforum.org<mailto:public@cabforum.org>><br class="">Cc: Virginia Fournier <vfournier@apple.com<mailto:vfournier@apple.com>><br class="">Subject: Re: [cabfpub] Public Digest, Vol 69, Issue 118<br class="">Message-ID:<br class=""> <CACvaWvayCXkZ1s00FtLz+sPnM3PVQvUiJX_6FNwKBi9JKpzjOA@mail.gmail.com<mailto:CACvaWvayCXkZ1s00FtLz+sPnM3PVQvUiJX_6FNwKBi9JKpzjOA@mail.gmail.com>><br class="">Content-Type: text/plain; charset="utf-8"<br class=""><br class="">Hi Kirk,<br class=""><br class="">As mentioned previously, these Review Notices don't comply with Section<br class="">2.4(e) of the Bylaws and our IPR Policy, Section 4.1<br class=""><br class="">As per https://cabforum.org/wp-content/uploads/CABF-IPR-Policy-v.1.2.pdf<br class="">Prior to the approval of a CAB Forum Draft Guideline as a CAB Forum Final<br class="">Guideline or Final<br class="">Maintenance Guideline there shall be a review period during which<br class="">Participants may exclude<br class="">CA/B Forum Intellectual Property Rights Policy, v. 1.2 Page 2<br class="">certain Essential Claims from CAB Forum RF Licenses. The CAB Forum Chair<br class="">shall initiate the<br class="">Review Period by distributing to each CAB Forum Participant **a notice of<br class="">review period and a<br class="">complete draft of the Draft Guideline that is the subject of such notice<br class="">(?Review Notice?)**. Each<br class="">Participant on behalf of itself and its Affiliates shall have sixty (60)<br class="">days following the date of<br class="">the receipt of such Review Notice (?Review Period?) to review such Draft<br class="">Guideline and<br class="">consider any licensing obligations with respect to any Essential Claims<br class="">that may be encompassed<br class="">by such Draft Guideline. The approval of a CAB Forum Final Maintenance<br class="">Guideline shall<br class="">follow the same process except that the Review Period shall be thirty (30)<br class="">days.<br class=""><br class=""><br class="">I think the important part is "a complete draft of the Draft Guideline"<br class=""><br class="">Not a redline, but the complete draft - the fully integrated text.<br class=""><br class=""><br class="">On Thu, Feb 1, 2018 at 1:28 PM, Kirk Hall via Public <public@cabforum.org<mailto:public@cabforum.org>><br class="">wrote:<br class=""><br class="">Virginia ? yes, we have been posting Review Notices for every ballot that<br class="">changes the Guidelines since Ballot 190 to the Public list ? just search on<br class="">?Review Notice? and you should see them. Here is an example.<br class=""><br class=""><br class=""><br class="">*From:* Public [mailto:public-bounces@cabforum.org] *On Behalf Of *Virginia<br class="">Fournier via Public<br class="">*Sent:* Wednesday, January 31, 2018 8:09 PM<br class="">*To:* public@cabforum.org<mailto:public@cabforum.org><br class="">*Subject:* [EXTERNAL]Re: [cabfpub] Public Digest, Vol 69, Issue 118<br class=""><br class=""><br class=""><br class="">Hi - I don?t recall seeing any Review Notices sent out pursuant to Section<br class="">2.4(e) of the Bylaws. What is happening with those?<br class=""><br class=""><br class=""><br class=""><br class=""><br class="">Best regards,<br class=""><br class=""><br class=""><br class="">Virginia Fournier<br class=""><br class="">Senior Standards Counsel<br class=""><br class="">? Apple Inc.<br class=""><br class="">? 669-227-9595 <(669)%20227-9595><br class=""><br class="">?? vmf@apple.com<mailto:vmf@apple.com><br class=""><br class=""><br class=""><br class=""><br class=""><br class=""><br class=""><br class=""><br class=""><br class=""><br class=""><br class="">On Jan 27, 2018, at 4:20 PM, public-request@cabforum.org<mailto:public-request@cabforum.org> wrote:<br class=""><br class=""><br class=""><br class="">Send Public mailing list submissions to<br class=""> public@cabforum.org<mailto:public@cabforum.org><br class=""><br class="">To subscribe or unsubscribe via the World Wide Web, visit<br class=""> https://cabforum.org/mailman/listinfo/public<br class="">or, via email, send a message with subject or body 'help' to<br class=""> public-request@cabforum.org<mailto:public-request@cabforum.org><br class=""><br class="">You can reach the person managing the list at<br class=""> public-owner@cabforum.org<mailto: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. Updated CABF documents - Record of Review Notices (Kirk Hall)<br class=""><br class=""><br class="">----------------------------------------------------------------------<br class=""><br class="">Message: 1<br class="">Date: Sun, 28 Jan 2018 00:20:52 +0000<br class="">From: Kirk Hall <Kirk.Hall@entrustdatacard.com<mailto:Kirk.Hall@entrustdatacard.com>><br class="">To: CA/Browser Forum Public Discussion List <public@cabforum.org<mailto:public@cabforum.org>><br class="">Subject: [cabfpub] Updated CABF documents - Record of Review Notices<br class="">Message-ID:<br class=""> <db5933c86e0a4825a58723cc548c3a67@PMSPEX04.corporate.<br class="">datacard.com<mailto:db5933c86e0a4825a58723cc548c3a67@PMSPEX04.corporate.%0bdatacard.com>><br class="">Content-Type: text/plain; charset="us-ascii"<br class=""><br class="">I attached updated copies of the BRs, EVGL, and Bylaws in "show changes"<br class="">mode, in both Word and pdf format. Please review. If there are no edits,<br class="">we can finalize and post to the CABF website at the end of next week.<br class=""><br class="">A note on timing. The changes to the BRs and EVGL all come from a single<br class="">ballot, Ballot 217, which only became effective on Jan. 20, 2018 (a week<br class="">ago). Under our Bylaws, updated BRs and EVGLs should have been circulated<br class="">by last Wednesday, so I am 3 days late - I apologize for any inconvenience.<br class=""><br class="">Our Bylaws do not specify any time limit on when updated copies of the<br class="">Bylaws must be created and circulated, and these revised Bylaws include<br class="">only the changes from Ballot 216, which became effective Dec. 21, 2017 -<br class="">about five weeks ago. Again, I apologize if anyone was inconvenienced by<br class="">not receiving an updated copy of the Bylaws before today.<br class=""><br class="">I also attach a document "Record of Review Notices Since Ballot 190 (27<br class="">Jan 2018)" which indicates there have been no Exclusion Notices filed on<br class="">Guidelines ballots since Ballot 190. Members were already aware of this,<br class="">as anyone claiming an Exclusion Notice must post it to the Public list (and<br class="">none have been posted since Ballot 190), but we will maintain and update<br class="">this new document and send it out in the future on the Public list after<br class="">the Review Period for each Guidelines ballot expires.<br class="">-------------- next part --------------<br class="">An HTML attachment was scrubbed...<br class="">URL: <http://cabforum.org/pipermail/public/attachments/<br class="">20180128/bffb6a85/attachment.html<http://cabforum.org/pipermail/public/attachments/%0b20180128/bffb6a85/attachment.html>><br class="">-------------- next part --------------<br class="">A non-text attachment was scrubbed...<br class="">Name: Record of Review Notices Since Ballot 190 (27 Jan 2018).pdf<br class="">Type: application/pdf<br class="">Size: 117077 bytes<br class="">Desc: Record of Review Notices Since Ballot 190 (27 Jan 2018).pdf<br class="">URL: <http://cabforum.org/pipermail/public/attachments/<br class="">20180128/bffb6a85/attachment.pdf<http://cabforum.org/pipermail/public/attachments/%0b20180128/bffb6a85/attachment.pdf>><br class="">-------------- next part --------------<br class="">A non-text attachment was scrubbed...<br class="">Name: Record of Review Notices Since Ballot 190 (27 Jan 2018).docx<br class="">Type: application/vnd.openxmlformats-officedocument.<br class="">wordprocessingml.document<br class="">Size: 18341 bytes<br class="">Desc: Record of Review Notices Since Ballot 190 (27 Jan 2018).docx<br class="">URL: <http://cabforum.org/pipermail/public/attachments/<br class="">20180128/bffb6a85/attachment.docx<http://cabforum.org/pipermail/public/attachments/%0b20180128/bffb6a85/attachment.docx>><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<mailto: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 69, Issue 118<br class="">***************************************<br class=""><br class=""><br class=""><br class=""><br class="">---------- Forwarded message ----------<br class="">From: Kirk Hall <Kirk.Hall@entrustdatacard.com<mailto:Kirk.Hall@entrustdatacard.com>><br class="">To: "CA/Browser Forum Public Discussion List" <public@cabforum.org<mailto:public@cabforum.org>><br class="">Cc:<br class="">Bcc:<br class="">Date: Thu, 21 Dec 2017 22:22:35 +0000<br class="">Subject: Notice of Review Period ? Ballot 217<br class=""><br class="">*NOTICE OF REVIEW PERIOD ? BALLOT 217*<br class=""><br class=""><br class=""><br class="">This Review Notice is sent pursuant to Section 4.1 of the CA/Browser<br class="">Forum?s Intellectual Property Rights Policy (v1.2). This Review Period is<br class="">for Final Maintenance Guidelines (30 day Review Period). A complete draft<br class="">of the Draft Guideline that is the subject of this Review Notice is<br class="">attached.<br class=""><br class=""><br class=""><br class="">Date Review Notice Sent: December 21, 2017<br class=""><br class=""><br class=""><br class="">Ballot for Review: Ballot 217 ? Sunset RFC 2527<br class=""><br class=""><br class=""><br class="">Start of Review Period: December 21, 2017 at 23:00 UTC<br class=""><br class=""><br class=""><br class="">End of Review Period: January 20, 2018 at 23:00 UTC<br class=""><br class=""><br class=""><br class="">Please forward any Exclusion Notice relating to Essential Claims to the<br class="">Chair by email to kirk.hall@entrustdatacard.com<mailto:kirk.hall@entrustdatacard.com> before the end of the<br class="">Review Period. See current version of CA/Browser Forum Intellectual<br class="">Property Rights Policy for details.<br class=""><br class=""><br class=""><br class="">*(Optional form of Exclusion Notice is attached)*<br class=""><br class=""><br class=""><br class="">*Ballot 217: Sunset RFC 2527*<br class=""><br class=""><br class=""><br class="">*-- MOTION BEGINS --*<br class=""><br class=""><br class=""><br class="">This ballot modifies the "Baseline Requirements for the Issuance and<br class="">Management of Publicly-Trusted Certificates" as follows, based upon Version<br class="">1.5.1:<br class=""><br class=""><br class=""><br class="">In Section 2.2, replace the text:<br class=""><br class=""><br class=""><br class="">"The CA SHALL publicly disclose its Certificate Policy and/or<br class="">Certification Practice Statement through an appropriate and readily<br class="">accessible online means that is available on a 24x7 basis. The CA SHALL<br class="">publicly disclose its CA business practices to the extent required by the<br class="">CA's selected audit scheme (see Section 8.1). The disclosures MUST include<br class="">all the material required by RFC 2527 or RFC 3647, and MUST be structured<br class="">in accordance with either RFC 2527 or RFC 3647. "<br class=""><br class=""><br class=""><br class="">with the following:<br class=""><br class=""><br class=""><br class="">"The CA SHALL publicly disclose its Certificate Policy and/or<br class="">Certification Practice Statement through an appropriate and readily<br class="">accessible online means that is available on a 24x7 basis. The CA SHALL<br class="">publicly disclose its CA business practices to the extent required by the<br class="">CA's selected audit scheme (see Section 8.1).<br class=""><br class=""><br class=""><br class="">Effective as of 31 May 2018, the Certificate Policy and/or Certification<br class="">Practice Statement MUST be structured in accordance with RFC 3647. Prior to<br class="">31 May 2018, the Certificate Policy and/or Certification Practice Statement<br class="">MUST be structured in accordance with either RFC 2527 or RFC 3647. The<br class="">Certificate Policy and/or Certification Practice Statement MUST include all<br class="">material required by RFC 3647 or, if structured as such, RFC 2527."<br class=""><br class=""><br class=""><br class=""><br class=""><br class="">This ballot modifies the "Guidelines for the Issuance and Management of<br class="">Extended Validation Certificates" as follows, based on Version 1.6.6:<br class=""><br class=""><br class=""><br class="">In Section 8.2.2, replace the text:<br class=""><br class=""><br class=""><br class="">"Each CA MUST publicly disclose their EV Policies through an appropriate<br class="">and readily accessible online means that is available on a 24x7 basis. The<br class="">CA is also REQUIRED to publicly disclose its CA business practices as<br class="">required by WebTrust for CAs and ETSI TS 102 042 and ETSI EN 319 411-1.<br class="">The disclosures MUST be structured in accordance with either RFC 2527 or<br class="">RFC 3647."<br class=""><br class=""><br class=""><br class="">With the following:<br class=""><br class=""><br class=""><br class="">"Each CA MUST publicly disclose its Certificate Policy and/or<br class="">Certification Practice Statement through an appropriate and readily<br class="">accessible online means that is available on a 24x7 basis. The CA SHALL<br class="">publicly disclose its CA business practices to the extent required by the<br class="">CA's selected audit scheme (see Section 17.1).<br class=""><br class=""><br class=""><br class="">Effective as of 31 May 2018, the CA's Certificate Policy and/or<br class="">Certification Practice Statement MUST be structured in accordance with RFC<br class="">3647. Prior to 31 May 2018, the CA's Certificate Policy and/or<br class="">Certification Practice Statement MUST be structured in accordance with<br class="">either RFC 2527 or RFC 3647. The Certificate Policy and/or Certification<br class="">Practice Statement MUST include all material required by RFC 3647 or, if<br class="">structured as such, RFC 2527."<br class=""><br class=""><br class=""><br class="">*-- MOTION ENDS --*<br class=""><br class=""><br class=""><br class="">_______________________________________________<br class="">Public mailing list<br class="">Public@cabforum.org<mailto:Public@cabforum.org><br class="">https://cabforum.org/mailman/listinfo/public<br class="">-------------- next part --------------<br class="">An HTML attachment was scrubbed...<br class="">URL: <http://cabforum.org/pipermail/public/attachments/20180201/d5b63453/attachment.html><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<mailto: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 70, Issue 4<br class="">*************************************<br class=""><br class="">-------------- next part --------------<br class="">An HTML attachment was scrubbed...<br class="">URL: <http://cabforum.org/pipermail/public/attachments/20180205/ff172eb7/attachment.html><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 70, Issue 17<br class="">**************************************<br class=""></div></div></div><br class=""></div></body></html>