<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=""><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="">Would it be possible to move the Governance WG to a little later in the agenda in case I’m running a few minutes late?  Thanks.<br 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 Jan 22, 2018, at 6:03 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. Re: Revocation as a domain owner (Josh Aas)<br class="">   2. Re: Draft Agenda for CA/Browser Teleconference of Jan. 25,<br class="">      2018 at 11 am Eastern (Ryan Sleevi)<br class=""><br class=""><br class="">----------------------------------------------------------------------<br class=""><br class="">Message: 1<br class="">Date: Mon, 22 Jan 2018 20:03:11 -0600<br class="">From: Josh Aas <josh@letsencrypt.org><br class="">To: Wayne Thayer <wthayer@mozilla.com>,  "CA/Browser Forum Public<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>Discussion List" <public@cabforum.org><br class="">Subject: Re: [cabfpub] Revocation as a domain owner<br class="">Message-ID:<br class=""><span class="Apple-tab-span" style="white-space:pre">      </span><CAJH38kGiAqa2mdND1BaJiA3Py83VR5jw4-DMhiOv=_STpQcRvQ@mail.gmail.com><br class="">Content-Type: text/plain; charset="UTF-8"<br class=""><br class="">It can be very difficult for a CA to determine who is the legal owner<br class="">of a domain, thus taking action (e.g. revoking) on that basis creates<br class="">significant liability. The BRs should not introduce additional rules<br class="">requiring such determinations.<br class=""><br class="">A couple of ideas that don't depend on determining legal ownership:<br class=""><br class="">1) Let anyone revoke a certificate if they can demonstrate control of<br class="">the certificate's private key. Let's Encrypt does this, it has worked<br class="">out well.<br class=""><br class="">2) Allow people to revoke certificates if they can re-validate for all<br class="">of the domains in the cert. The Let's Encrypt API also allows this.<br class=""><br class="">Both of these methods are clearly defined and can be fully automated.<br class=""><br class="">On Wed, Jan 3, 2018 at 10:59 AM, Wayne Thayer via Public<br class=""><public@cabforum.org> wrote:<br class=""><blockquote type="cite" class="">Matthias,<br class=""><br class="">I think you've raised a valid point. I'm working on ballot 213 "Revocation<br class="">Timeline Extension" that makes changes to this section of the BRs, and I<br class="">will draft some language to attempt to address this. If you have any ideas<br class="">on how this requirement should be stated, please let me know.<br class=""><br class="">Thanks,<br class=""><br class="">Wayne<br class=""><blockquote type="cite" class=""><br class=""><br class="">I can't propose a ballot as I'm not a CAB member but adding the<br class="">requirement of having to revoke certificates on the domain owner's request<br class="">should probably be considered.<br class=""><br class=""><br class=""></blockquote><br class=""><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=""></blockquote><br class=""><br class=""><br class="">-- <br class="">Josh Aas<br class="">Executive Director<br class="">Internet Security Research Group<br class="">Let's Encrypt: A Free, Automated, and Open CA<br class=""><br class=""><br class="">------------------------------<br class=""><br class="">Message: 2<br class="">Date: Mon, 22 Jan 2018 21:03:05 -0500<br class="">From: Ryan Sleevi <sleevi@google.com><br class="">To: Kirk Hall <Kirk.Hall@entrustdatacard.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] Draft Agenda for CA/Browser Teleconference of<br class=""><span class="Apple-tab-span" style="white-space:pre">      </span>Jan. 25, 2018 at 11 am Eastern<br class="">Message-ID:<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span><CACvaWvbAUSN+f=8XkTrw175qJPgMDepxytgiOMoXRKcj+LBqDw@mail.gmail.com><br class="">Content-Type: text/plain; charset="utf-8"<br class=""><br class="">Hi Kirk,<br class=""><br class="">As a possible item, or a consideration in advance, could you make sure the<br class="">document status on https://cabforum.org/baseline-requirements-documents/ is<br class="">up to date? Your current status appears up to date, but our webpage seems a<br class="">bit behind.<br class=""><br class="">Similarly, https://cabforum.org/bylaws/ is not updated with the result of<br class="">Ballot 216 - I believe we should have a Version 1.8 of the Bylaws, based on<br class="">that?<br class=""><br class="">I note your meeting schedule in the footnotes still lists "June - London".<br class="">Is it correct that June 5-7 are the finalized dates for London?<br class=""><br class="">On Mon, Jan 22, 2018 at 8:53 PM, Kirk Hall via Public <public@cabforum.org><br class="">wrote:<br class=""><br class=""><blockquote type="cite" class="">Here is the draft agenda for our teleconference this *Thursday, January<br class="">25, 2018 at 11:00 am Eastern Time*.  Please suggest any additional topics<br class="">you would like to discuss.<br class=""><br class=""><br class=""><br class="">*Time*<br class=""><br class="">*Start (ET)*<br class=""><br class="">*Stop*<br class=""><br class="">*Item*<br class=""><br class="">*Description*<br class=""><br class="">*Presenters*<br class=""><br class="">*(Thursday) January 25, 2018*<br class=""><br class="">0:02<br class=""><br class="">11:00<br class=""><br class="">11:02<br class=""><br class="">1.<br class=""><br class="">Roll Call<br class=""><br class="">Kirk<br class=""><br class="">0:01<br class=""><br class="">11:02<br class=""><br class="">11:03<br class=""><br class="">2.<br class=""><br class="">Read Antitrust Statement<br class=""><br class="">Robin<br class=""><br class="">0:01<br class=""><br class="">11:03<br class=""><br class="">11:04<br class=""><br class="">3.<br class=""><br class="">Review Agenda<br class=""><br class="">Kirk<br class=""><br class="">0:02<br class=""><br class="">11:04<br class=""><br class="">11:06<br class=""><br class="">4.<br class=""><br class="">Approval of Minutes from teleconference of January 11, 2017<br class=""><br class="">Emailed and corrected by Kirk Jan. 11<br class=""><br class="">0:10<br class=""><br class="">11:06<br class=""><br class="">11:16<br class=""><br class="">5.<br class=""><br class="">Governance Change Working Group<br class=""><br class="">Virginia, Dean, Ben<br class=""><br class="">0:05<br class=""><br class="">11:16<br class=""><br class="">11:21<br class=""><br class="">6.<br class=""><br class="">Policy Review Working Group update<br class=""><br class="">Ben, Dimitris<br class=""><br class="">0:05<br class=""><br class="">11:21<br class=""><br class="">11:26<br class=""><br class="">7.<br class=""><br class="">Network Security Working Group update<br class=""><br class="">Ben<br class=""><br class="">0:10<br class=""><br class="">11:26<br class=""><br class="">11:36<br class=""><br class="">8.<br class=""><br class="">Validation Working Group update<br class=""><br class="">Tim<br class=""><br class="">0:05<br class=""><br class="">11:36<br class=""><br class="">11:41<br class=""><br class="">9.<br class=""><br class="">Ballot Status - Discussion of ballots (See Ballot Status table at end of<br class="">Agenda)<br class=""><br class="">All<br class=""><br class="">0:04<br class=""><br class="">11:41<br class=""><br class="">11:45<br class=""><br class="">10.<br class=""><br class="">Logistics for March F2F meeting ? Amazon, Herndon, VA<br class=""><br class="">Peter<br class=""><br class="">0:05<br class=""><br class="">11:45<br class=""><br class="">11:50<br class=""><br class="">11.<br class=""><br class="">Possible Topics for March F2F meeting<br class=""><br class="">All<br class=""><br class="">0:05<br class=""><br class="">11:50<br class=""><br class="">11:55<br class=""><br class="">12.<br class=""><br class="">Any Other Business<br class=""><br class="">Kirk<br class=""><br class="">0:01<br class=""><br class="">11:55<br class=""><br class="">11:56<br class=""><br class="">13.<br class=""><br class="">Next call: Feb. 8, 2018 at 11:00 am Eastern Time<br class=""><br class="">Kirk<br class=""><br class="">0:01<br class=""><br class="">11:56<br class=""><br class=""><br class=""><br class="">14.<br class=""><br class="">Adjourn<br class=""><br class="">Kirk<br class=""><br class=""><br class=""><br class="">*CURRENT STATUS OF BALLOTS (as of Jan. 22, 2018)*<br class=""><br class=""><br class=""><br class="">1.       *Ballots in Voting Period*<br class=""><br class="">None<br class=""><br class=""><br class=""><br class="">2.       *Ballots in Discussion Period*<br class=""><br class="">a.       Ballot 218 ?  Remove validation methods #1 and #5 (Tim) ?<br class="">revised Jan. 22<br class=""><br class=""><br class=""><br class="">3.       *Ballots in Review Period*<br class=""><br class="">a.       Ballot 217 ? Sunset RFC 2527 (Ryan) ? ends Jan. 29<br class=""><br class=""><br class=""><br class="">*4.       **Draft Ballots Under Consideration*<br class=""><br class="">a.       Ballot 206 - Changes to IPR Policy and Bylaws re Formation of<br class="">Working Groups<br class=""><https://www.cabforum.org/wiki/206%20-%20Changes%20to%20IPR%20Policy%20and%20Bylaws%20re%20Formation%20of%20Working%20Groups><br class="">(Virginia)<br class=""><br class=""><br class=""><br class=""><br class=""><br class="">*F2F Meeting Schedule: *<br class=""><br class="">2018: March 6-8 - Herndon, VA (Amazon), June ? London (Comodo), October ?<br class="">Shanghai (CFCA)<br class=""><br class="">2019: Feb-March ? Cupertino, CA (Apple), June ? Greece (HARICA,<br class="">tentative), October ? Guangzhou (GDCA)<br class=""><br class="">2020: Feb-March [Open], June ? Minneapolis (OATI), October [Open]<br class=""><br class=""><br class=""><br class=""><br class=""><br class=""><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=""></blockquote>-------------- next part --------------<br class="">An HTML attachment was scrubbed...<br class="">URL: <http://cabforum.org/pipermail/public/attachments/20180122/0c00c6cc/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 69, Issue 99<br class="">**************************************<br class=""></div></div></div><br class=""></body></html>