October 2018 - council - lists.icann.org

Re: [council] The Information Transparency Initiative (ITI) Feedback Site is Now Live - ICANN - Blog by David Conrad
by Mary Wong July 3, 2019

July 3, 2019

Dear Ayden and all, We apologize if there were difficulties with accessing the feedback tool – there ought not to be any, so please do try it again if you wish to provide feedback. Please be assured that ICANN organization is committed to and interested in gathering the community’s feedback on each of the features that we will be rolling out with the objective of improving the findability, transparency, and accessibility of ICANN public content. The deadlines are, unfortunately, what they are in order to ensure that we are able to deliver on this major project on budget and on time. There will certainly be multiple and additional opportunities and forums for continuing community feedback, as noted in David’s blog that is referenced in the announcement below. Thank you. Best regards, Mary From: council <council-bounces(a)gnso.icann.org> on behalf of Ayden Férdeline <icann(a)ferdeline.com> Reply-To: Ayden Férdeline <icann(a)ferdeline.com> Date: Wednesday, April 25, 2018 at 09:17 To: Heather Forrest <haforrestesq(a)gmail.com> Cc: GNSO Council List <council(a)gnso.icann.org> Subject: Re: [council] Fwd: [So-ac-sg-cleaders] The Information Transparency Initiative (ITI) Feedback Site is Now Live - ICANN - Blog by David Conrad Given comments are being sought for less than a week, this does not strike me as a genuine consultative activity but appears to be a token form of participation intended to manipulate public opinion. This new website implies a shift towards greater consultation and community participation in ICANN's content strategy, but we cannot actually wield any influence by commenting here. (And not just because if you press the 'provide feedback' button, you see "The feedback survey is temporarily unavailable.") From what I understand we are not even being asked to comment on anything important. The list of 250 definitions, which I would like to review for neutrality and accuracy, are not online and it sounds like they have already been approved internally and are not open to community review. Are we really being asked to comment on just the glossary tool itself, and did ICANN really produce a video mockup and slide deck of something so incredibly mundane when it is up for public comment for just a week? Please forgive the negative sentiment to my message here, but it really seems a poor allocation of resources to me. Ayden Férdeline ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On 25 April 2018 3:03 PM, Heather Forrest <haforrestesq(a)gmail.com> wrote: Dear Council colleagues, I am pleased to pass on David Olive's update, below, on the Information Transparency Initiative. Best wishes, Heather ---------- Forwarded message ---------- From: "David Olive" <david.olive(a)icann.org<mailto:david.olive@icann.org>> Date: 24/04/2018 10:37 AM Subject: [So-ac-sg-cleaders] The Information Transparency Initiative (ITI) Feedback Site is Now Live - ICANN - Blog by David Conrad To: "so-ac-sg-cleaders(a)icann.org<mailto:so-ac-sg-cleaders@icann.org>" <so-ac-sg-cleaders(a)icann.org<mailto:so-ac-sg-cleaders@icann.org>> Cc: "David Conrad" <david.conrad(a)icann.org<mailto:david.conrad@icann.org>>, "Jana Juginovic" <jana.juginovic(a)icann.org<mailto:jana.juginovic@icann.org>> https://www.icann.org/news/blog/the-information-transparency-initiative-iti…<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blo…> The Information Transparency Initiative (ITI) Feedback Site is Now Live I'm pleased to announce that today, we launched the ITI feedback site[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_itifeedb…> (feedback.icann.org[feedback.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__feedback.icann.org&d=Dw…>). As I have written about in previous blogs and discussed at ICANN60 and ICANN61 sessions, this site[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_itifeedb…> is intended to provide you, the ICANN community, with the ability to share your input on the content and features the ITI team is working on to improve the findability, transparency, and accessibility of ICANN public content. The first item we are looking for your comments on is an updated Acronyms and Terms feature[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_itifeedb…> to replace the existing feature[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>. Our update doubles the number of terms available, provides up-to-date definitions for the terms, and improves search. Unlike most of the ITI project, we will launch this updated feature on the current https://icann.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_&d=DwMGa…> before 31 May 2018. The deadline to provide your input on the proposed updates to Acronyms and Terms is 30 April 2018, 23:59 UTC. Please visit feedback.icann.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_itifeedb…> to experience the proposed changes and complete a short survey. How the ITI Feedback Site Works The ITI Team will regularly post documents, mockups, or video walkthroughs of new content and features. The proposed content or feature items are listed on the homepage under the heading "Feedback Needed." Each item lists a deadline by which you need to provide input. Simply click on the item you're interested in. This will take you to another page, which provides you with the option to either download a mockup or watch a video walkthrough. Once you have completed that task, click on the "Feedback" button to complete a short survey or email your feedback to informationtransparency(a)icann.org<mailto:informationtransparency@icann.org>. Once the deadline has passed, the ITI Team will collect and publish all comments to feedback.icann.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_itifeedb…>. All published results of the survey will be anonymous, unless otherwise requested by the submitter. We will review all submissions and make our best efforts to implement the feedback, prioritizing input that serves the goals of improving search and accessibility, and increasing the transparency of our content. Feedback Deadlines We do have a tight deadline for community comments – one week for each new item. The reason for this timeline is we need to maintain a rigorous development schedule to ensure we are delivering the project on time and within budget. However, feedback.icann.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_itifeedb…> is not your only avenue to share input. ITI has many other opportunities to learn about ITI and provide comments including: * Regular sessions at ICANN Public Meetings. * Special sessions or webinars for Supporting Organizations and Advisory Committees (SO/ACs) on request or for special features and content like Public Comment. * Monthly blogs and newsletters. * Via email at informationtransparency(a)icann.org<mailto:informationtransparency@icann.org> Feedback Translations As I outlined above, we are working at a brisk development pace. This does limit our ability to fully translate feedback.icann.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_itifeedb…> and its survey. But, if you want to share feedback in another language, email us at informationtransparency(a)icann.org<mailto:informationtransparency@icann.org>. It is important to emphasize that one of the primary goals of ITI is a multilingual https://icann.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_&d=DwMGa…>, and the sooner we complete this project, the sooner we can deliver on that goal. ITI Goals ITI's goal is not a revamp of https://icann.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_&d=DwMGa…>. While the ITI team is working on making improvements to your User Experience (UX) on https://icann.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_&d=DwMGa…>, the vast majority of our efforts are focused on: * Creating content governance through new, enforced workflows and the creation of a consistent, multilingual taxonomy. * Building new technical infrastructures including a first-ever for ICANN document management system (DMS) and a new content management system (CMS). This new infrastructure will enforce this governance and enable improved content findability. Much of this foundational work won't be available on the feedback site for your input, but we will show the intended benefits of this work through the content and features we will share. ITI Update The ITI team has been hard at work completing that foundational work I mentioned above. We have completed the following tasks since the January 2018 launch of ITI: * The foundational build of the DMS and CMS, and the integration between the two platforms. * Sixty percent of the content audit and the taxonomy creation. * Interviews with SO/AC leaders, registrants, registrars, Fellows, and other ICANN stakeholders. We have also begun work on the following items: * Content modelling, workflow creation, and content governance enforcement in the DMS. * Accessibility guidelines and multilingual site implementation planning. ITI will launch in December 2019. ITI Backgrounders For those of you unfamiliar with ITI, you can read about what it is and how it will benefit the ICANN community in my kickoff blog[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blo…>. You can learn more about how the content audit and taxonomy will help your search experience in my January blog[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blo…>. We also outlined the differences between ITI and the Open Data Initiative (ODI) in our pre-ICANN61 blog[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blo…>. We Need Your Feedback Remember, we need your input to help us make the specific improvements to search, transparency, and accessibility that you need and want. Please visit the ITI feedback site[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_itifeedb…> and email us anytime at informationtransparency(a)icann.org<mailto:informationtransparency@icann.org>. Comments Log in to Comment[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_users_si…> or Sign Up[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_users_si…> Details * ICANN Blog * Author: David Conrad, Chief Technology Officer (CTO) and Senior Vice-President * 23 Apr 2018 David A. Olive Senior Vice President Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN) _______________________________________________ So-ac-sg-cleaders mailing list So-ac-sg-cleaders(a)icann.org<mailto:So-ac-sg-cleaders@icann.org> https://mm.icann.org/mailman/listinfo/so-ac-sg-cleaders

4 7

Amendments to the Consensus Policy Implementation Framework (CPIF)
by Brian Aitchison Nov. 1, 2018

Nov. 1, 2018

Dear GNSO Council members, Following conversations among ICANN org and the GNSO Council—in particular the IPC and the RrSG who provided written input—please find attached a redlined version of the CPIF that addresses the suggestions for amendments we received. Also attached is the original letter sent from ICANN org to the GNSO Council detailing the mandate and focus of the CPIF amendment process. We were not able to integrate all suggestions received into this round of CPIF amendments. You’ll see in the comment boxes the suggestions received, along with a rationale for why we did or did not update the document based on those suggestions. Generally speaking, we did not add amendments that merited more in-depth discussion between ICANN org and the Council. For example, the process for recruiting IRTs is based on a “call for volunteers”, so we could not add the IPC’s suggestion that IRT’s must “fairly represent all constituencies” until further discussion with the Council about how IRTs should be constituted. We also tried to minimize any redundant language that may overly simplify the process of soliciting GNSO Council input on an implementation via an IRT. In accordance with Point H of the CPIF, which directs “ICANN staff [to] continually review the implementation framework and related materials to encapsulate additional best-practices or to adjust the steps as a result of lessons learned with previous Consensus Policy projects,” ICANN org will continue to work with the GNSO Council to refine the CPIF. Currently we are working on defining a standard process for proposing amendments to it, which we will share with the Council when ready. ICANN org will continue to welcome input on how and where the CPIF should be amended. Any such input received will be tracked and evaluated for a future round of amendments, which we plan to begin in the next calendar year. To provide input, please email me at brian.aitchison(a)icann.org<mailto:brian.aitchison@icann.org> (please cc the Council list). Our Policy Team colleagues also welcome your input; should you have any, please feel free to discuss it with them during one of your meetings or via email. We request that the GNSO Council review the attached redlined CPIF document. If no further input is received, we will post it to icann.org’s implementation page at https://www.icann.org/policy/implementation on 10 December 2018. On behalf of ICANN org, we thank the Council and its members for providing input on this important process. Sincerely, Brian -- Brian Aitchison, PhD Lead Researcher Global Domains Division, Operations and Policy Research Internet Corporation for Assigned Names and Numbers (ICANN) Los Angeles, CA p. 310 578 8688 m. 424 353 9041 e. brian.aitchison(a)icann.org<mailto:brian.aitchison@icann.org> Sk. brian.aitchison.icann CONFIDENTIALITY NOTICE: This email and any attachments are for the sole use of the intended recipient(s) and contain information that may be confidential and/or legally privileged. If you have received this email in error, please notify the sender by reply email and delete the message. Any disclosure, copying, distribution or use of this communication by someone other than the intended recipient is prohibited.

2 1

Board resolution and rationale on reserve fund replenishment
by Marika Konings Oct. 30, 2018

Oct. 30, 2018

Dear All, As discussed during today’s wrap up session, please find below the Board resolution and rationale in relation to the reserve fund replenishment strategy. Best regards, Marika ================ https://www.icann.org/resources/board-material/resolutions-2018-10-25-en#2.f • Reserve Fund Replenishment Strategy Whereas, the Board confirmed by previous decision (resolutions 2018.02.04.09 – 2018.02.04.10) that the target level of the ICANN Reserve Fund should be at a minimum equivalent to 12 months of operating expenses. Whereas, the current level of the Reserve Fund is approximately of US$70 million as of 30 June 2018, reflecting a shortfall compared to the minimum target level of approximately US$68 million. Whereas, ICANN organization posted for public comment a proposed strategy to replenish the Reserve Fund and the Board took all comments submitted into account to determine the final Reserve Fund replenishment strategy. Whereas, the proposed replenishment strategy entails allocating to the Reserve Fund: (i) annual operational excess of funding over expenses for a total of US$32 million over an eight-year period; and (ii) US$36 million of new gTLD auction proceeds. Resolved (2018.10.25.22), the Board directs the President and CEO, or his designee(s), to take all actions necessary to increase the Reserve Fund through annual excesses from the operating fund of ICANN organization by a total amount of US$32 million over a period of seven to eight years, starting with FY19. Resolved (2018.10.25.23), the Board directs the President and CEO, or his designee(s), to take all actions necessary to allocate US$36 million of auction proceeds to the Reserve Fund, as soon as technically feasible. Rationale for Resolutions 2018.10.25.22 – 2018.10.25.23 Based on its fiduciary duties and considering the significant growth and risk profile that ICANN has seen since the creation of its Reserve Fund, the Board determined that the Reserve Fund required to be reviewed, especially in light of the significant drop in its level. The Board conducted an evaluation of the Rationale and Target level for the Reserve Fund, which was based on the public comments received on a first consultation paper. As a result, an updated ICANN Investment Policy was approved by the Board to include: (a) an updated Reserve Fund Rationale; and (b) a confirmation that the Reserve Fund Target Level will be set at a minimum of 12 months of Operating Expenses (See resolution https://features.icann.org/confirmation-reserve-fund-target-level) Once the Target Level was confirmed, the Board outlined a proposed strategy to replenish the Reserve Fund from its current level to its updated minimum Target Level, which was the subject of a second public comment process. The comments received provided for a wide range of views on the sources of funds and extent of use of such sources for the purpose of replenishment. Relative to the annual excess allocation, most comments received on this aspect suggested a higher allocation than the one proposed. On the allocation of auction proceeds, some comments suggested a lower allocation and others a higher allocation to the Reserve Fund. All comments but one indicated that no increase to ICANN fees should be considered. Also, the use of New gTLD Program funds for purpose of replenishment was not retained in the final proposed strategy due to the continued existence of risks associated with the program. Based on comments received, a final proposed replenishment strategy was drafted, which reflects a higher annual excess allocation than proposed, and is now submitted for Board approval and implementation. The remaining auction proceeds continue to be segregated and are not intended to be used for day-to-day operations. The Board will review the CCWG recommendations for a disbursement mechanism, as approved by the chartering organizations, and will then make a decision on the mechanism by which available proceeds should be disbursed, for implementation by ICANN org. At all times, the Board will continue to make all decisions in furtherance of ICANN's mission, under consideration of its duty of care and its fiduciary responsibility. This action is in the public interest and is consistent with ICANN's mission as it is important to ensure stability of ICANN organization in the way of an adequately funded Reserve Fund in case use of a Reserve Fund becomes necessary. This action will have a positive financial impact on ICANN and will enable ICANN to support its financial stability and sustainability. It will not have any impact on the security, stability or resiliency of the domain name system. This is an Organizational Administrative function that has already been subject to public comment as set forth above. Marika Konings Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) Email: marika.konings(a)icann.org<mailto:marika.konings@icann.org> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses<https://urldefense.proofpoint.com/v2/url?u=http-3A__learn.icann.org_courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>.

3 2

Thank you and best wishes
by Heather Forrest Oct. 29, 2018

Oct. 29, 2018

[image: 20171225_165055.jpg] Dear Council colleagues, I echo all of Donna's beautifully articulated sentiments. It has been a tremendous privilege working with you all and and achieving so much together. Puerto (left) and Rico (right) send their thanks. I'll send a photo of them in the fabulous blankets when I get home in a few weeks. I would love to see the Google searches that led up to that most perfect of gifts. :) With very best wishes, and sincerest thanks, Heather

3 2

It’s been a joy
by Austin, Donna Oct. 28, 2018

Oct. 28, 2018

Dear Councilors Hopefully I still have posting rights for one last message. I can’t believe how quickly four years has flown by. Sincere thanks to you all for the collegial spirit In which we’ve undertaken our work during that time. The last 12 months has been a series of unforeseen and unprecedented challenges, but thanks to Heather’s leadership and everyone’s willingness to engage and find a path forward, I think we’ve done pretty well. I’ll see you around and I hope I have an opportunity to work with you all again in some capacity. Many thanks Donna Sent from my iPhone

4 3

Call for Volunteers - SCBO
by Berry Cobb Oct. 28, 2018

Oct. 28, 2018

Hi All, As discussed at the GNSO Council wrap-up session in Barcelona, please find attached a call for volunteers to join the Standing Committee on ICANN's Budget and Operations. It will be helpful to have adequate representation from both houses. You can view the current membership here <https://community.icann.org/pages/viewpage.action?pageId=74580769> . The SCBO is formulating comments for the draft FY20 IANA/PTI budget, which is due 12 November 2018. The draft FY20 ICANN Org budget is expected to be posted on 17 December 2018. Thank you. B Berry Cobb GNSO Policy Consultant @berrycobb

1 0

Call for Volunteers - SCBO
by Berry Cobb Oct. 28, 2018

Oct. 28, 2018

Hi All, As discussed at the GNSO Council wrap-up session in Barcelona, please find attached a call for volunteers to join the Standing Committee on ICANN's Budget and Operations. It will be helpful to have adequate representation from both houses. You can view the current membership here <https://community.icann.org/pages/viewpage.action?pageId=74580769> . The SCBO is formulating comments for the draft FY20 IANA/PTI budget, which is due 12 November 2018. The draft FY20 ICANN Org budget is expected to be posted on 17 December 2018. Thank you. B Berry Cobb GNSO Policy Consultant @berrycobb

1 0

Re: [council] Proposed GNSO Council meeting dates 2019
by Flip Petillion Oct. 26, 2018

Oct. 26, 2018

Dear Nathalie, May I ask you to kindly confirm the dates for November and December? Thank you Kind regards, Flip Flip Petillion fpetillion(a)petillion.law +32484652653 www.petillion.law [signature_907712380]<http://www.petillion.law/> From: council <council-bounces(a)gnso.icann.org> on behalf of Nathalie Peregrine <nathalie.peregrine(a)icann.org> Date: Thursday, 25 October 2018 at 13:32 To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [council] Proposed GNSO Council meeting dates 2019 Dear all, Please have a quick look at the below list of proposed GNSO Council meeting dates for 2019. This is an agenda item for our Wrap-Up meeting later today (17:00 – 18:30 in GNSO room 115). Religious holidays and IG related events have been taken account as much as possible, but please point out conflicts if they have been left out. * January - 24th (Pacific time, during the GNSO Strategic Planning session) * February – 21st * March 13th (ICANN64 Kobe) * April 18th * May 16th * June 26th (ICANN65 Marrakech) * July 18th * August 22nd (August 15th is end of Eid al-Adha and French National Holiday) * September 19th * October 24th (17th is Sukkot - Jewish holiday) * November 6th (ICANN66 Montreal) * December 19th Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

2 1

Proposed GNSO Council meeting dates 2019
by Nathalie Peregrine Oct. 26, 2018

Oct. 26, 2018

Dear all, Please have a quick look at the below list of proposed GNSO Council meeting dates for 2019. This is an agenda item for our Wrap-Up meeting later today (17:00 – 18:30 in GNSO room 115). Religious holidays and IG related events have been taken account as much as possible, but please point out conflicts if they have been left out. * January - 24th (Pacific time, during the GNSO Strategic Planning session) * February – 21st * March 13th (ICANN64 Kobe) * April 18th * May 16th * June 26th (ICANN65 Marrakech) * July 18th * August 22nd (August 15th is end of Eid al-Adha and French National Holiday) * September 19th * October 24th (17th is Sukkot - Jewish holiday) * November 6th (ICANN66 Montreal) * December 19th Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

5 4

FW: [gnso-secs] Rafik as NCPH vice chair
by Nathalie Peregrine Oct. 26, 2018

Oct. 26, 2018

Dear councilors, Please see below notification from Farzaneh Badii that Rafik Dammak is the Non Contracted Party House representative GNSO Council Vice Chair. Kind regards, Nathalie From: Gnso-secs <gnso-secs-bounces(a)icann.org> on behalf of farzaneh badii <farzaneh.badii(a)gmail.com> Date: Thursday, October 25, 2018 at 6:57 PM To: Stephanie Perrin <stephanie.perrin(a)mail.utoronto.ca>, "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [gnso-secs] Rafik as NCPH vice chair Dear GNSO Secretariat We hereby confirm that Rafik has been re appointed to the gnso council vice chair position. Thank you -- Farzaneh

4 3

FW: Re: [Ext] RPM PDP Complaint referral
by McGrady, Paul D. Oct. 25, 2018

Oct. 25, 2018

FYI below. Phil has threatened to resign from the Co-Chair role before, which would be unfortunate and a little disruptive. This time he indicates that there may also be an “indeterminate suspension of the working group’s activities.” I’m not sure Co-chairs are allowed to suspend PDPs without Council’s OK. Obviously, this situation has now reached a critical point and threatens the timeline of this PDP which, if you believe in the existence of dependencies between this PDP and the Sub Pro PDP, could result in a delay of Round 2, ultimately affecting ICANN’s revenue stream. So, I think we should take this up as a matter of urgency. I don’t know if this is properly under Item 2 (Liaisons) of our agenda for later this evening or item 9 (dysfunctional PDPs). If neither, can we please add it? Best, Paul From: Corwin, Philip <pcorwin(a)verisign.com> Sent: Thursday, October 25, 2018 9:15 AM To: peg.rettino(a)icann.org Cc: Samantha.Eisner(a)icann.org; john.jeffrey(a)icann.org; kathy(a)kathykleiman.com; brian.beckham(a)wipo.int; McGrady, Paul D. <PMcGrady(a)winston.com> Subject: RE: Re: [Ext] RPM PDP Complaint referral Importance: High Thank you, Peg. I certainly understand that John has a busy schedule during the meeting. However, it is very unfortunate that at least a preliminary discussion was unable to take place here in Barcelona. The current situation involves an alleged violation of the Expected Standards of Behavior (ESB), which is a Board-adopted accountability measure. Agreement to comply with the ESB is a threshold requirement for participation by any individual in any ICANN activity. The individual alleged to have violated the ESB has taken the position that it is unenforceable against him under the current GNSO Guidelines, which raises the question of whether his consent to abide by it was sincere and valid. He has introduced private counsel into the enforcement procedure, when my prior experience with ESB enforcement actions in the context of GNSO working groups is that it is meant to be an informal procedure, with appeal of any adverse decision to GNSO Council available under section 3.7 of the Guidelines. These actions have rendered the co-chairs unable to perform their ESB enforcement role, and the individual claiming to be harmed by the alleged ESB violation has stated that the introduction of private counsel into the procedure is fundamentally unfair to him. There is also the claim by the accused individual that two of the three co-chairs are biased against him and must recuse themselves due to his own prior actions, a claim with which I disagree. Finally, the accused individual maintains a Twitter account with 1822 followers (as of today) to which he has in the past reposted his communications made on working group email lists; creating the possibility that statements made regarding this situation will be distributed to a large audience of unknown individuals and harm the public reputation of the co-chairs. Under these circumstances, it was justified and welcome for Council to take the matter out of the hands of the co-chairs at the conclusion of the GNSO discussion of it that took place on Sunday the 21st, with the co-chairs being told that the matter would be dealt with further by Council in consultation with ICANN Legal. Since Sunday an additional communication from the accused individual’s attorneys makes clear that their involvement now extends beyond the original allegation, and that any statement or action of any of the co-chairs to or in regard to their client in the context of working group meetings may trigger further communications by them to ICANN Legal. This escalation of their involvement means that the co-chairs not only have no present ability to decide ESB complaints, but that any direct engagement by the co-chairs with their client may be the subject of further action by private counsel, including the implicit threat of litigation brought against the co-chairs individually. This situation will have a substantial chilling effect on the ability of the co-chairs to administer the working group in an effective and orderly manner, especially since the communication received to date from ICANN Legal on the subject of indemnification under Section 20.1 of the Bylaws provides no firm assurance that the co-chairs will be regarded as “agents” eligible for indemnification if they are the targets of private litigation, and the co-chairs are also now aware that there are no ICANN-adopted Guidelines for “good faith” conduct in such situations. The next scheduled meeting of the Working group is scheduled for 1700 UTC on Wednesday, November 7th. In my view it is imperative that some satisfactory response to this situation occur before that date, as failure to do so may result in an indeterminate suspension of the working group’s activities and/or the resignation of one or more of the co-chairs. It is my understanding that the Legal staff may wish to interview the co-chairs individually as a preliminary step. If that is correct then I will be available for such a discussion next week at the following times (all US Eastern time): * Monday – late afternoon * Tuesday – afternoon * Wednesday – unavailable * Thursday -afternoon * Friday – afternoon (noting that the next planning call of the co-chairs generally takes place at 1500 UTC on Friday, and that the November 2nd call would involve planning for the meeting scheduled for November 7th) I look forward to further discussion with ICANN Legal staff on this matter. Sincerely, Philip S. Corwin Policy Counsel VeriSign, Inc. 12061 Bluemont Way Reston, VA 20190 703-948-4648/Direct 571-342-7489/Cell "Luck is the residue of design" -- Branch Rickey From: Peg Rettino [mailto:peg.rettino@icann.org] Sent: Thursday, October 25, 2018 6:41 AM To: Corwin, Philip <pcorwin(a)verisign.com<mailto:pcorwin@verisign.com>> Cc: Samantha Eisner <Samantha.Eisner(a)icann.org<mailto:Samantha.Eisner@icann.org>> Subject: [EXTERNAL] Re: Re: [Ext] RPM PDP Complaint referral Hi Phil, Unfortunately John’s schedule simply can’t work. This discussion will need to be a phone call either later next week or the week that follows. I’ll be in touch late next week to coordinate schedules. Wishing you a safe return! Best, Peg -- Peg Rettino Project Specialist & Executive Assistant to John Jeffrey General Counsel and Secretary ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094 peg.rettino(a)icann.org<mailto:peg.rettino@icann.org> Skype: peg.rettino Direct: 310-301-3868 From: "Corwin, Philip" <pcorwin(a)verisign.com<mailto:pcorwin@verisign.com>> Date: Thursday, October 25, 2018 at 10:15 AM To: Peg Rettino <peg.rettino(a)icann.org<mailto:peg.rettino@icann.org>> Cc: Sam Eisner <Samantha.Eisner(a)icann.org<mailto:Samantha.Eisner@icann.org>>, Kathy Kleiman <kathy(a)kathykleiman.com<mailto:kathy@kathykleiman.com>>, "brian.beckham(a)wipo.int<mailto:brian.beckham@wipo.int>" <brian.beckham(a)wipo.int<mailto:brian.beckham@wipo.int>> Subject: Re: Re: [Ext] RPM PDP Complaint referral I do hope we can meet today, as I believe that timely resolution of this matter is critical to the success of this PDP. I am available from to 12 to 5 today. Sent from my iPhone On Oct 24, 2018, at 4:02 PM, Peg Rettino <peg.rettino(a)icann.org<mailto:peg.rettino@icann.org>> wrote: Hi Phil, Apologies, it’s been a very hectic afternoon. Will need to look at tomorrow. Appreciate your flexibility. Stay tuned, Peg From: "Corwin, Philip" <pcorwin(a)verisign.com<mailto:pcorwin@verisign.com>> Date: Wednesday, October 24, 2018 at 4:00 PM To: Peg Rettino <peg.rettino(a)icann.org<mailto:peg.rettino@icann.org>> Cc: Sam Eisner <Samantha.Eisner(a)icann.org<mailto:Samantha.Eisner@icann.org>> Subject: RE: Re: [Ext] RPM PDP Complaint referral As I haven’t yet heard back, I could be available up to 6 tonight. If that doesn’t work then tomorrow I could meet between 9 and 9:50 (receiving award for Council service at 10) or, preferably, any time between 12 noon and 5 pm. Philip S. Corwin Policy Counsel VeriSign, Inc. 12061 Bluemont Way Reston, VA 20190 703-948-4648/Direct 571-342-7489/Cell "Luck is the residue of design" -- Branch Rickey From: Peg Rettino [mailto:peg.rettino@icann.org] Sent: Wednesday, October 24, 2018 6:14 AM To: Corwin, Philip <pcorwin(a)verisign.com<mailto:pcorwin@verisign.com>> Cc: Samantha Eisner <Samantha.Eisner(a)icann.org<mailto:Samantha.Eisner@icann.org>> Subject: [EXTERNAL] Re: Re: [Ext] RPM PDP Complaint referral Thank you Phil, I appreciate it. Hope to send you something soon. Best, Peg From: "Corwin, Philip" <pcorwin(a)verisign.com<mailto:pcorwin@verisign.com>> Date: Wednesday, October 24, 2018 at 11:58 AM To: Peg Rettino <peg.rettino(a)icann.org<mailto:peg.rettino@icann.org>> Cc: Sam Eisner <Samantha.Eisner(a)icann.org<mailto:Samantha.Eisner@icann.org>> Subject: Re: Re: [Ext] RPM PDP Complaint referral Today I am generally free to step out of meetings and come by anytime between 12 and 5. If that doesn’t work I can look at tomorrow. Sent from my iPhone On Oct 24, 2018, at 11:54 AM, Peg Rettino <peg.rettino(a)icann.org<mailto:peg.rettino@icann.org>> wrote: Hi Phil, It would be helpful to know your availability (today & tomorrow) firstly given I’m working with two fluctuating calendars. Thank you in advance! Best, Peg -- Peg Rettino Project Specialist & Executive Assistant to John Jeffrey General Counsel and Secretary ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094 peg.rettino(a)icann.org<mailto:peg.rettino@icann.org> Skype: peg.rettino Direct: 310-301-3868 From: "Corwin, Philip" <pcorwin(a)verisign.com<mailto:pcorwin@verisign.com>> Date: Wednesday, October 24, 2018 at 11:39 AM To: Sam Eisner <Samantha.Eisner(a)icann.org<mailto:Samantha.Eisner@icann.org>> Cc: Peg Rettino <peg.rettino(a)icann.org<mailto:peg.rettino@icann.org>> Subject: Re: [Ext] RPM PDP Complaint referral I would be pleased to meet with you. Let me know your availability. Sent from my iPhone On Oct 24, 2018, at 11:37 AM, Samantha Eisner <Samantha.Eisner(a)icann.org<mailto:Samantha.Eisner@icann.org>> wrote: Hi Phil - John and I are trying to connect with people who are on the ground here in Barcelona to help gain a better understanding of the situation. Please let us know if you have a few minutes to talk before you leave. Peg Rettino, cc'd here, can schedule us from our side. Best, Sam ____ Samantha Eisner Deputy General Counsel, ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, California 90094 USA Direct Dial: +1 310 578 8631 ________________________________ From: Corwin, Philip <pcorwin(a)verisign.com<mailto:pcorwin@verisign.com>> Sent: Monday, October 22, 2018 7:58 AM To: Samantha Eisner Subject: RE: [Ext] RPM PDP Complaint referral Greg is here in Barcelona. George is not here. So far as I am aware George has never attended an ICANN meeting. But Robin Gross is here, and she filed the attached on his behalf. Best regards Philip S. Corwin Policy Counsel VeriSign, Inc. 12061 Bluemont Way Reston, VA 20190 703-948-4648/Direct 571-342-7489/Cell "Luck is the residue of design" -- Branch Rickey From: Samantha Eisner [mailto:Samantha.Eisner@icann.org] Sent: Monday, October 22, 2018 10:28 AM To: Heather Forrest <haforrestesq(a)gmail.com<mailto:haforrestesq@gmail.com>>; Greg Shatan <gregshatanipc(a)gmail.com<mailto:gregshatanipc@gmail.com>>; George Kirikos <icann(a)leap.com<mailto:icann@leap.com>> Cc: Austin, Donna <Donna.Austin(a)team.neustar<mailto:Donna.Austin@team.neustar>>; rafik.dammak(a)gmail.com<mailto:rafik.dammak@gmail.com>; Kathy Kleiman <kathy(a)kathykleiman.com<mailto:kathy@kathykleiman.com>>; Beckham, James Brian <brian.beckham(a)wipo.int<mailto:brian.beckham@wipo.int>>; Corwin, Philip <pcorwin(a)verisign.com<mailto:pcorwin@verisign.com>> Subject: [EXTERNAL] Re: [Ext] RPM PDP Complaint referral Dear Greg & George, If either of you are here in Barcelona at ICANN63, I'm here if you'd like to meet in person to provide information or discuss. Thanks, Sam ____ Samantha Eisner Deputy General Counsel, ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, California 90094 USA Direct Dial: +1 310 578 8631 ________________________________ From: Heather Forrest <haforrestesq(a)gmail.com<mailto:haforrestesq@gmail.com>> Sent: Sunday, October 21, 2018 9:31 AM To: Greg Shatan; George Kirikos Cc: Samantha Eisner; Austin, Donna; Rafik Dammak; Kathy Kleiman; Beckham, James Brian; Corwin, Philip Subject: [Ext] RPM PDP Complaint referral Dear Greg, George, Following the update today provided by the RPM PDP WG Co-Chairs to the GNSO Council on the status of the unresolved complaint between you, GNSO Council leadership (myself, Donna Austin, Rafik Dammak) have discussed the matter with ICANN Legal. We have been advised to refer the matter of the involvement of legal counsel in your PDP-related complaint to ICANN Legal. All correspondence in relation to this matter from this point should be sent to Samantha Eisner, Deputy General Counsel, who is copied in this message. Kind regards, Heather Forrest, GNSO Chair Donna Austin, GNSO Council Vice Chair Rafik Damma, GNSO Council Vice Chair ________________________________ The contents of this message may be privileged and confidential. If this message has been received in error, please delete it without reading it. Your receipt of this message is not intended to waive any applicable privilege. Please do not disseminate this message without the permission of the author. Any tax advice contained in this email was not intended to be used, and cannot be used, by you (or any other taxpayer) to avoid penalties under applicable tax laws and regulations.

5 7

AC for GNSO Wrap Up
by Drazek, Keith Oct. 25, 2018

Oct. 25, 2018

https://participate.icann.org/bcn63-115 From: Emily Barabas <emily.barabas(a)icann.org> Sent: Thursday, October 25, 2018 5:01 PM To: Drazek, Keith <kdrazek(a)verisign.com> Subject: [EXTERNAL] https://participate.icann.org/bcn63-115 Emily Barabas | Policy Manager ICANN | Internet Corporation for Assigned Names and Numbers Email: emily.barabas(a)icann.org<mailto:emily.barabas@icann.org> | Phone: +31 (0)6 84507976

1 0

MP3, Adobe Connect recording and chat transcript/ GNSO Council meeting on Wednesday, 24 October 2018 at 13:00 UTC.
by Terri Agnew Oct. 25, 2018

Oct. 25, 2018

Dear GNSO Council, Please find below the MP3, Adobe Connect recording and chat of the GNSO Council meeting held on Wednesday, 24 October 2018 at 13:00 UTC. MP3 Part I: http://audio.icann.org/meetings/bcn63/bcn63-OPEN-2018-10-24-T1055-115-en-GN… Part II: http://audio.icann.org/meetings/bcn63/bcn63-OPEN-2018-10-24-T1306-115-en-GN… Adobe Connect Recording URL Part I: https://participate.icann.org/p3j97hwa2ao Part II: https://participate.icann.org/p8ykhei0r1e Adobe Connect chat Part I at: https://gnso.icann.org/sites/default/files/file/field-file-attach/transcrip… All on page: https://gnso.icann.org/en/group-activities/calendar Thank you. Happy listening and reading! With kind regards, Terri --- Terri Agnew Operations Support - GNSO Lead Administrator Internet Corporation for Assigned Names and Numbers (ICANN) Email: terri.agnew(a)icann.org<mailto:terri.agnew@icann.org> Skype ID: terri.agnew.icann Find out more about the GNSO by taking our interactive courses and visiting the GNSO Newcomer pages [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_g…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO [twitter.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Follow the GNSO on Facebook: https://www.facebook.com/icanngnso/ [facebook.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_icann…> http://gnso.icann.org/en/ [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_&d=Dw…>

1 0

Re: [council] [Ext] Re: Proposed GNSO Council meeting dates 2019
by Nathalie Peregrine Oct. 25, 2018

Oct. 25, 2018

Hello Michele, all, Not yet, as the confirmation of the NCPH vice-chair will be necessary to determine the rotation. For the time being, in order to be fair to councilors across all time-zones, we could consider a rotation of two meeting times: 11:00 UTC and 21:00UTC Kind regards, Nathalie From: Michele Blacknight <michele(a)blacknight.com> Date: Thursday, October 25, 2018 at 2:28 PM To: Nathalie Peregrine <nathalie.peregrine(a)icann.org>, "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [Ext] Re: [council] Proposed GNSO Council meeting dates 2019 Has there been any discussion on the times and their rotation? Thanks Michele -- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains https://www.blacknight.com/ [blacknight.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.blacknight.com_&d=…> http://blacknight.blog/ [blacknight.blog]<https://urldefense.proofpoint.com/v2/url?u=http-3A__blacknight.blog_&d=DwMG…> Intl. +353 (0) 59 9183072 Direct Dial: +353 (0)59 9183090 Personal blog: https://michele.blog/ [michele.blog]<https://urldefense.proofpoint.com/v2/url?u=https-3A__michele.blog_&d=DwMGaQ…> Some thoughts: https://ceo.hosting/ [ceo.hosting]<https://urldefense.proofpoint.com/v2/url?u=https-3A__ceo.hosting_&d=DwMGaQ&…> ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.: 370845 From: council <council-bounces(a)gnso.icann.org> on behalf of Nathalie Peregrine <nathalie.peregrine(a)icann.org> Date: Thursday 25 October 2018 at 13:32 To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [council] Proposed GNSO Council meeting dates 2019 Dear all, Please have a quick look at the below list of proposed GNSO Council meeting dates for 2019. This is an agenda item for our Wrap-Up meeting later today (17:00 – 18:30 in GNSO room 115). Religious holidays and IG related events have been taken account as much as possible, but please point out conflicts if they have been left out. * January - 24th (Pacific time, during the GNSO Strategic Planning session) * February – 21st * March 13th (ICANN64 Kobe) * April 18th * May 16th * June 26th (ICANN65 Marrakech) * July 18th * August 22nd (August 15th is end of Eid al-Adha and French National Holiday) * September 19th * October 24th (17th is Sukkot - Jewish holiday) * November 6th (ICANN66 Montreal) * December 19th Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

Re: [council] Proposed GNSO Council meeting dates 2019 AND today's Wrap Up session...
by Cheryl Langdon-Orr Oct. 25, 2018

Oct. 25, 2018

Please note I will fit in with whatever meeting schedule the GNSO Council settles on. Also please note my sincere apologies for today's wrap up session, I will be engaged in the 20y session (on the panel) at the same time... Sorry On Thu, Oct 25, 2018, 13:31 Nathalie Peregrine <nathalie.peregrine(a)icann.org> wrote: > Dear all, > > > > Please have a quick look at the below list of proposed GNSO Council > meeting dates for 2019. This is an agenda item for our Wrap-Up meeting > later today (17:00 – 18:30 in GNSO room 115). > > Religious holidays and IG related events have been taken account as much > as possible, but please point out conflicts if they have been left out. > > > > - January - 24th (Pacific time, during the GNSO Strategic Planning > session) > - February – 21st > - March 13th (ICANN64 Kobe) > - April 18th > - May 16th > - June 26th (ICANN65 Marrakech) > - July 18th > - August 22nd (August 15th is end of Eid al-Adha and French National > Holiday) > - September 19th > - October 24th (17th is Sukkot - Jewish holiday) > - November 6th (ICANN66 Montreal) > - December 19th > > > > > > > > Nathalie Peregrine > > Manager, Operations Support (GNSO) > > Internet Corporation for Assigned Names and Numbers (ICANN) > > Email: nathalie.peregrine(a)icann.org > <http://nathalie.peregrine@icann.org%20> > > Skype: nathalie.peregrine.icann > > > > Find out more about the GNSO by taking our interactive courses and > visiting the GNSO Newcomer pages > <https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…> > > > _______________________________________________ > council mailing list > council(a)gnso.icann.org > https://mm.icann.org/mailman/listinfo/council >

2 1

Proposed Council Wrap-Up Agenda
by Steve Chan Oct. 25, 2018

Oct. 25, 2018

Dear Councilors, Below, please find the proposed agenda for the Council Wrap-Up Session, scheduled for 17:00-18:30 in room 115. If you have any suggested additions, please let us know. Best, Steve Proposed Council Wrap-Up Agenda GAC Communiqué - Volunteers for drafting team Council liaisons - Status of Council liaisons, taking into account departing Councilors Current liaisons. Names high-lighted in red must be replaced. WHOIS Procedure Implementation Advisory Group (WPIAG): Keith Drazek Expedited Policy Development Process on the Temporary Specification on gTLD Registration Data: Rafik Dammak Rights Protection Mechanisms (RPMs) in All gTLDs PDP: Paul McGrady New gTLD Subsequent Procedures PDP: Keith Drazek, Donna Austin Curative Rights Protections for IGO/INGOs: Susan Kawaguchi Reconvened PDP on Red Cross: Heather Forrest GNSO Review WG: Rafik Dammak Protections of IGO names in All gTLDs: Keith Drazek Privacy & Proxy Services Accreditation Issues: Darcy Southwell Translation/Transliteration of Internationalized Registration Data: Rubens Kuhl Thick WHOIS: Susan Kawaguchi Standing Committee on ICANN Budget and Operating Plan: Heather Forrest GNSO Standing Selection Committee: Susan Kawaguchi GNSO Council Liaison to GNSO Working Groups – Role Description: https://gnso.icann.org/en/council/gnso-liaison-wg-22feb18-en.pdf GNSO Representative to the Empowered Community Administration confirmation Public comment periods - https://www.icann.org/public-comments PTI and IANA FY20 Budget -> SCBO CCWG Auction Proceeds? Reserve fund and connection to auction funds Strategic Planning Session Reminder to book travel Planning and next steps Membership of Standing Committee on ICANN’s Budget and Operations – Call for volunteers Relevant excerpt from the Charter: Members of the standing committee will be comprised of volunteers from the GNSO Council and the nomination of the chair will be determined by said committee. Each Stakeholder Group is expected to designate at least 1 Council member and 1 alternate to this effort. Membership to the standing committee is based on a Council member’s term. Constitution of the Committee will be reviewed at each AGM (Annual General Meeting) as Council member terms expire and new members are elected by their respective groups. The Standing Committee may decide to solicit additional volunteers throughout the year as needed. Members will be listed on the community wiki. Schedule of GNSO Council meetings for 2018 ICANN64 Meeting planning - update from kickoff Cross-community/high-interest topic session planning and coordination (SG/C) PDP 3.0 - next steps Steven Chan  Policy Director, GNSO Support ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536  Mobile: +1.310.339.4410 Office Telephone: +1.310.301.5800 Office Fax: +1.310.823.8649 Find out more about the GNSO by taking our interactive courses and visiting the GNSO Newcomer pages. Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO Follow the GNSO on Facebook: https://www.facebook.com/icanngnso/ http://gnso.icann.org/en/

3 4

Re: [council] Proposed GNSO Council meeting dates 2019
by Michele Neylon - Blacknight Oct. 25, 2018

Oct. 25, 2018

Has there been any discussion on the times and their rotation? Thanks Michele -- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains https://www.blacknight.com/ http://blacknight.blog/ Intl. +353 (0) 59 9183072 Direct Dial: +353 (0)59 9183090 Personal blog: https://michele.blog/ Some thoughts: https://ceo.hosting/ ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.: 370845 From: council <council-bounces(a)gnso.icann.org> on behalf of Nathalie Peregrine <nathalie.peregrine(a)icann.org> Date: Thursday 25 October 2018 at 13:32 To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [council] Proposed GNSO Council meeting dates 2019 Dear all, Please have a quick look at the below list of proposed GNSO Council meeting dates for 2019. This is an agenda item for our Wrap-Up meeting later today (17:00 – 18:30 in GNSO room 115). Religious holidays and IG related events have been taken account as much as possible, but please point out conflicts if they have been left out. * January - 24th (Pacific time, during the GNSO Strategic Planning session) * February – 21st * March 13th (ICANN64 Kobe) * April 18th * May 16th * June 26th (ICANN65 Marrakech) * July 18th * August 22nd (August 15th is end of Eid al-Adha and French National Holiday) * September 19th * October 24th (17th is Sukkot - Jewish holiday) * November 6th (ICANN66 Montreal) * December 19th Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

GAC Communique ICANN63
by Nathalie Peregrine Oct. 25, 2018

Oct. 25, 2018

*ICANN63, apologies! Dear all, The GAC Communique ICANN63 has been published: https://gac.icann.org/contentMigrated/icann63-barcelona-communique [gac.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gac.icann.org_contentM…> Kind regards, Nathalie Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

GAC Communique ICANN64
by Nathalie Peregrine Oct. 25, 2018

Oct. 25, 2018

Dear all, The GAC Communique ICANN64 has been published: https://gac.icann.org/contentMigrated/icann63-barcelona-communique Kind regards, Nathalie Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

FW: [gnso-secs] GNSO Council Vice-Chair
by Nathalie Peregrine Oct. 24, 2018

Oct. 24, 2018

Dear Councilors, Please see below a communication from Graeme Bunton, announcing Pam Little as Contracted Party House GNSO Council Vice Chair. Kind regards, Nathalie On 10/24/18, 5:37 PM, "Gnso-secs on behalf of Graeme Bunton" <gnso-secs-bounces(a)icann.org on behalf of gbunton(a)tucows.com> wrote: Hello Keith, and the rest of the GNSO Council, I am pleased to let you know that the Contracted Party House has selected Pam Little to serve as GNSO Council Vice Chair. We thank her for volunteering and are confident she'll be an excellent addition to Council leadership. Regards, Graeme Bunton, Chair, Registrar Stakeholder Group, on behalf of the Contracted Party House -- _________________________ Graeme Bunton Director, Analytics & Policy Tucows Inc. PH: 416 535 0123 ext 1634 _______________________________________________ Gnso-secs mailing list Gnso-secs(a)icann.org https://mm.icann.org/mailman/listinfo/gnso-secs

7 6

REMINDER: GALA INFORMATION Wednesday 24 October 2018
by Terri Agnew Oct. 24, 2018

Oct. 24, 2018

ICANN63 Gala Hosted by Ministry of Economy and Business and RED.ES Venue : Centre de Convencions Internacional de Barcelona (CCIB) – Area 5-6-7-8 Time : 19:00 – 22:00 Standing gala, food with local tastes, drinks, entertainment Tickets : Gala invitation will be required to attend ICANN63 Gala. The invitations will be available at the host booth ( Booth # 7 ) on Monday, 22 October, Tuesday, 23 October and Wednesday, 24 October. Session Leader: Ministry of Economy and Business and RED.ES Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

Please review: GNSO Council motions 24 October 2018
by Nathalie Peregrine Oct. 24, 2018

Oct. 24, 2018

Dear all, Please find below the resolutions from the GNSO Council at its meeting on Wednesday 24 October 2018. If no objections we will publish them on the GNSO website here: https://gnso.icann.org/en/council/resolutions Consent Agenda: Motion: Reappointment of GNSO Council Liaison to the Governmental Advisory Committee Submitted by Donna Austin Seconded by Michele Neylon Whereas: 1. As part of the discussions within ICANN between the GNSO and GAC on how to facilitate early engagement of the GAC in GNSO policy development activities, the option of appointing a GNSO liaison to the GAC was initially piloted in FY15 and F16, and subsequently confirmed by the GNSO Council as a permanent role at the start of FY17. 2. The GNSO Council appointed Julf Helsingius to the role of GNSO Liaison to the Governmental Advisory Committee on 1 November 2017, until the end of the ICANN AGM 2018. 3. The GNSO Council has an obligation to review the role annually and reconfirm the appointment unless the review indicates otherwise and/or the Liaison has indicated that he/she is no longer available to continue in this role, in which case a new selection process will take place. 4. The GNSO Council leadership has met with Julf Helsingius to discuss his experience and to confirm that he is willing to continue in this role. 5. The GNSO Council has reviewed the annual report prepared by the GNSO Liaison to the GAC. Resolved: 1. The GNSO Council hereby reappoints Julf Helsingius to the role of GNSO Liaison to the Governmental Advisory Committee until the end of the ICANN AGM 2019. 2. The GNSO Council leadership team will inform the GAC leadership team accordingly, and will co-ordinate with Julf Helsingius as well as the GAC leadership team and GAC Secretariat on next steps and the continued successful implementation of this role. Vote results [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…> Motion to adopt the charter for the GNSO Standing Committee on Budget and Operations (SCBO) on a permanent basis Submitted by: Ayden Férdeline Seconded by: Rafik Dammak Whereas, 1. In 2017 the GNSO Council expressed its desire to establish the GNSO Standing Committee on Budget and Operations (SCBO) to assist with the development of GNSO Council comments that relate to ICANN’s Budgetary and Finance matters; 2. On 21 December 2017, the GNSO Council adopted the formation of the SCBO and its interim charter; 3. In late 2017 and early 2018, GNSO Council members as well as subject matter experts from GNSO Stakeholder Groups and Constituencies joined the SCBO; 4. In FY18, the SCBO developed four public comments (IANA-PTI FY19 Budget, ICANN's Reserve Fund Target Level, ICANN’s Draft FY19 Budget and Operating Plan, and ICANN Reserve Fund: Proposed Replenishment Strategy) on behalf of the GNSO Council that were later accepted and posted to ICANN’s public forum; and 5. On 17 September 2018, the SCBO delivered an After-Action Report on the SCBO experiences and lessons learned wherein the report suggested that the SCBO charter did not warrant any changes and that the SCBO become a permanent Standing Committee of the GNSO Council. Resolved, 1. The GNSO Council adopts the GNSO Standing Committee on Budget and Operations (SCBO) charter on a permanent basis (see: https://gnso.icann.org/sites/default/files/file/field-file-attach/draft-ica… [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…>); 2. The GNSO Council thanks the Council members and subject matter experts for their contributions through the FY19 budget planning cycle; 3. The GNSO Council will appoint the incoming Council Chair as the Council liaison to the SCBO and add Council Vice-Chairs as observers; 4. The GNSO Council instructs the GNSO Secretariat to launch a fresh call for volunteers per the membership criteria outlined in the SCBO Charter as soon as possible; and 5. The GNSO Council tasks the SCBO to carry out the review and comment formulation for future ICANN fiscal-year draft budget planning cycles and to submit its proposed recommendations to the GNSO Council with sufficient time for its consideration. Vote results [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…> Motion to recommend the implementation of certain improvements to enhance the efficiency and effectiveness of the GNSO Policy Development Process (PDP 3.0) Submitted by Rafik Dammak Seconded by Heather Forrest Whereas, 1. In January 2018, the GNSO Council held an inaugural three-day Strategic Planning Session during which it, amongst other activities, reviewed the workload for the year ahead and identified potential milestones, noting that the current average timeline for delivery of an Initial Report has increased at least 2-4 times compared to previous PDPs. 2. The GNSO Council began identify challenges being encountered in PDPs, informed by a staff discussion paper on optimizing increased engagement and participation while ensuring efficient and effective policy development. 3. In order to engage the broader GNSO community in this discussion, the GNSO Council organized a collaborative session involving the members of the current PDP Leadership Teams as well as the broader community to summarize key points from the Strategic Planning Session, elaborate on the challenges that PDPs presently face and identified, and begin to brainstorm possible solutions. 4. As a result of these discussions, staff was tasked to publish a discussion paper that synthesizes the challenges that were identified as part of these discussions as well as possible improvements — both immediate and longer term — that the Council and PDP Working Groups could consider implementing to enhance efficiency and effectiveness of GNSO policy development activities. This discussion paper was published on 8 May 2018 (see https://gnso.icann.org/en/drafts/pdp-discussion-paper-11may18-en.pdf [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_draf…>). 5. GNSO Stakeholder Groups, Constituencies as well as other SO/ACs were invited to provide their input and feedback on the discussion paper. A summary report of the feedback received was shared with the Council on 10 September 2018 (see https://gnso.icann.org/en/drafts/pdp-summary-feedback-10sep18-en.pdf [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_draf…>) followed by a dedicated webinar on 11 September 2018 to further review and discuss the input received (see https://participate.icann.org/p1s5rcio69b/) 6. Based on the input received as well as the subsequent webinar, Council leadership developed a proposed GNSO PDP 3.0 Final Report and Recommendations for Council consideration (see (https://gnso.icann.org/sites/default/files/file/field-file-attach/pdp-incre… [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…>). 7. The GNSO Council and broader community reviewed and discussed the GNSO PDP 3.0 Final Report and Recommendations during the GNSO Weekend Session at ICANN63 (Oct 2018). Resolved, 1. The GNSO Council hereby adopts the GNSO PDP 3.0 Final Report and Recommendations and instructs GNSO Support Staff to work with the incoming Council leadership on the roll out of the Implementation Plan. 2. The GNSO Council requests the incoming 2018/19 Council leadership to report on a quarterly basis on the status of implementation. 3. The GNSO Council thanks all those that have contributed to the discussions on GNSO PDP 3.0 as well as the proposed improvements to enhance the efficiency and effectiveness of the GNSO PDP. Vote results [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…> Motion to terminate the Next-Generation gTLD Registration Directory Service (RDS) to replace WHOIS Policy Development Process Submitted by Stephanie Perrin Seconded by Darcy Southwell Whereas, 1. Following submission of the WHOIS Policy Review Team's Final Report, the ICANN Board passed a resolution on 8 November, 2012, launching an Expert Working Group on gTLD Registration Directory Services (EWG) to (1) help redefine the purpose of gTLD registration data and consider how to safeguard the data, and (2) propose a model for gTLD registration directory services to address accuracy, privacy, and access issues. 2. Upon publication of the EWG's Final Report in June, 2014, an informal group of Generic Names Supporting Organization (GNSO) Councilors and ICANN Board members collaborated to propose a Process Framework for structuring a GNSO Policy Development Process (PDP) to successfully address these challenging issues. 3. On 26 May, 2015, the ICANN Board adopted that Process Framework and reaffirmed its 2012 request for a Board-initiated PDP to define the purpose of collecting, maintaining and providing access to gTLD registration data, and to consider safeguards for protecting data, using the recommendations in the EWG's Final Report as an input to, and, if appropriate, as the foundation for a new gTLD policy. 4. On 19 November 2015, the GNSO Council adopted the charter for the next-generation gTLD Registration Directory Service (RDS) to replace WHOIS Policy Development Process Working group. 5. Following ICANN61 (March 2018), the RDS PDP Leadership decided to put on hold WG meetings indefinitely. This decision was made in light of the uncertain status of GDPR-related work and the possible duplication of efforts as a result of the adoption by the ICANN Board of the Temporary Specification for gTLD Registration Data. 6. Following the initiation by the GNSO Council of the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration data, the RDS PDP on 17 July 2018, the GNSO Council Liaison to the RDS PDP WG, Stephanie Perrin, submitted, at the request of the RDS PDP WG, the required Termination Summary [https://gnso.icann.org/sites/default/files/file/field-file-attach/next-gen-… [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…>] to recommend to the GNSO Council that the RDS PDP WG be terminated as per section 15 of the PDP Manual. 7. The GNSO Council has reviewed the Termination Summary. Resolved, 1. The GNSO Council hereby terminates the next-generation gTLD Registration Directory Service (RDS) to replace WHOIS Policy Development Process. 2. The GNSO Chair will share the Termination Summary as well as the Council decision with the ICANN Board for its information. 3. The GNSO Secretariat will inform the RDS PDP WG of this decision. 4. The GNSO Council expresses its sincere appreciation to the members of the RDS PDP Working Group, leadership team and ICANN support staff for all its work and efforts. Vote results [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…> Motion for GNSO Council Adoption of the Final Report of the IGO-INGO ACCESS to Curative Rights PDP Working Group - WITHDRAWN PRIOR TO THE COUNCIL MEETING BY DONNA AUSTIN Submitted by Donna Austin Seconded by Whereas: 1. On 5 June 2014, the GNSO Council launched [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> a Policy Development Process (PDP) on access to curative rights mechanisms at the second level of the domain name system by International Governmental Organizations (IGOs) and Non-Governmental Organizations; 2. On 25 June 2014, the GNSO Council approved the initial Charter [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_draf…> for the PDP Working Group, which was subsequently amended<https://community.icann.org/download/attachments/48347887/WG%20Charter%20-%…> on 16 April 2015; 3. This PDP has followed the prescribed PDP steps as stated in the Bylaws, resulting in a Final Report [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_issu…> delivered to the GNSO Council on 9 July 2018; 4. The PDP Working Group has reached consensus on all the recommendations in its Final Report; 5. At its 19 July 2018 meeting, the GNSO Council had acknowledged [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> the report and “the need to consider the topic of curative rights protections for IGOs in the broader context of appropriate overall scope of protection for all IGO identifiers (including IGO acronyms)”. The GNSO Council had declared its intention to review the Final Report (including the Minority Statements submitted) “with a view toward developing a possible path forward that will also facilitate the resolution of the outstanding inconsistencies between GAC advice and prior GNSO policy recommendations on the overall scope of IGO protections” as well as act on the recommendations “at the earliest opportunity following its review and deliberations on these topics”; 6. The GNSO Council had also noted that, until outstanding issues concerning protections for IGO names and acronyms are resolved, IGO acronyms remain reserved on an interim basis at the second level of the domain name system for those gTLDs delegated under the 2012 New gTLD Program round; and 7. The GNSO Council has reviewed and discussed the Working Group’s recommendations, including at a special Council discussion on 9 October 2018 where the Council also discussed the following questions: a. What questions/topics was the Working Group chartered to consider? b. Did the Working Group consider those charter topics/questions, and did it do so in a legitimate way? c. Has the Working Group followed due process? d. What were the process issues (if any) encountered by the Working Group? e. Did the Working Group address GAC advice on this topic? Resolved: 1. The GNSO Council adopts all the PDP Working Group’s final recommendations as contained in the Final Report. 2. The GNSO Council thanks the members of the PDP Working Group for their hard work in developing the recommendations. 3. Should the PDP recommendations be adopted by the ICANN Board, the GNSO Council directs ICANN staff to convene an Implementation Review Team. The Implementation Review Team will be tasked with assisting ICANN staff in developing the implementation details for the PDP recommendations, evaluating the proposed implementation of the recommendations as approved by the Board, and working with ICANN staff to ensure that the resultant implementation conforms to the intent of the approved recommendations. The Implementation Review Team shall operate in accordance with the Implementation Review Team Principles and Guidance approved by the GNSO Council in June 2015. 4. The GNSO Council requests that, following the adoption by the ICANN Board of the PDP recommendations, ICANN staff issue a call for volunteers for the Implementation Review Team, to be circulated at a minimum to the members of the PDP Working Group. Vote results [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…> Kind regards, Nathalie

1 0

Question from Remote Participant - GNSO Council Public Session Part I
by Ariel Liang Oct. 24, 2018

Oct. 24, 2018

Dear GNSO Councilors, During the GNSO Council Public Session Part I today, a remote participate (Paul Tattersfield) asked a question to the Council. Unfortunately, we ran out of time during the Open Mic section, so his question could not be read out. Staff hereby are forwarding the question from Paul below: Paul Tattersfield: Please can I formally ask the GNSO to go back to Professor Swaine the International Law expert who wrote the report for the IGO/INGO working group and ask him to comment publicly on his report to the working group, as I believe he made a material error as a matter of fact. Best Regards, Ariel Ariel Xinyue Liang GNSO Policy Support Specialist Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +1 310 804 2761 Skype: ariel.liang.icann www.icann.org

1 0

FW: Fwd: IMPORTANT: INFORMATION CONCERNING THE RESERVE FUND
by Drazek, Keith Oct. 24, 2018

Oct. 24, 2018

FYI From: Erika Mann <erika(a)erikamann.com> Sent: Wednesday, October 24, 2018 4:08 PM To: Drazek, Keith <kdrazek(a)verisign.com> Subject: [EXTERNAL] Fwd: IMPORTANT: INFORMATION CONCERNING THE RESERVE FUND Dear Keith - as discussed right now! Kind regards, Erika ---------- Forwarded message ---------- From: Erika Mann <erika(a)erikamann.com<mailto:erika@erikamann.com>> Date: Wed, Oct 24, 2018 at 1:27 PM Subject: Fwd: IMPORTANT: INFORMATION CONCERNING THE RESERVE FUND To: Heather Forrest <haforrestesq(a)gmail.com<mailto:haforrestesq@gmail.com>>, "Austin, Donna" <Donna.Austin(a)team.neustar<mailto:Donna.Austin@team.neustar>>, Rafik Dammak <rafik.dammak(a)gmail.com<mailto:rafik.dammak@gmail.com>> Dear Heather, Donna, Rafik - I'm forwarding you the information I send to the CCWG AP today concerning an upcoming Board resolution about the replenishment of the reserve fund. I'm a bit concerned to send this information to the whole GNSO, simply because it then will be on public record immediately and the Board will not pass the resolution before tomorrow. Erika ---------- Forwarded message ---------- From: Erika Mann <erika(a)erikamann.com<mailto:erika@erikamann.com>> Date: Wed, Oct 24, 2018 at 1:20 PM Subject: IMPORTANT: INFORMATION CONCERNING THE RESERVE FUND To: ccwg-auctionproceeds(a)icann.org<mailto:ccwg-auctionproceeds@icann.org> Dear CCWG AP colleagues - Cherine Chalaby asked for a meeting this morning, October 24, to inform me as CCWG AP Co-Chair about a resolution the Board will pass tomorrow morning, October 25, concerning the replenishment of the Reserve Fund. Maarten Botterman attended the meeting and Chris Disspain was present for a short period at the beginning of the meeting. To replenish the Reserve Fund, the Board resolution will request a contribution from ICANN ORG on an annual basis (8 years), total $32 Million, and an immediate contribution from Auction Proceed, total $36 Million. These two amounts seen together would replenish the Reserve Fund (in 8 years) to the agreed height. Cherine was interested in informing us ahead of the decision and I mentioned, that we were expecting such a move and, as far as this is concerned, we're not surprised to see the Board passing this resolution tomorrow and that we do appreciate his approach in informing us ahead of passing the resolution. Reminder: The 'Document for Public comment – Replenishment Strategy for the ICANN Reserve Fund' (open date, March 6th, 2018/closed April 25th, 2018) mentioned the following about the replenishment of the fund in relation to the topics mentioned above: https://www.icann.org/en/system/files/files/proposed-reserve-fund-replenish… § Contribution from ICANN Org: Future adopted budgets could be made to provide a contribution to the Reserve Fund on an annual basis. This would require ICANN Org to plan each fiscal year for expenses to be lower than funding by an amount explicitly designated for the purpose of replenishing the Reserve Fund. Given ICANN’s funding constraints, contributions from ICANN org to the Reserve Fund replenishment result from a reduced allocation of ICANN’s resources to its on-going activities, in order to produce a surplus that is allocated to the Reserve Fund. Such allocation is and needs to continue being the subject of community engagement and input. § Auction Proceeds: ICANN currently has US$ 104 million collected from auctions that were held as the mechanism of last resort to resolve string contention in the new gTLD program (including investment returns). This amount excludes US$ 132 million relating to the auction of the .WEB string net of auction fees Kind regards, Erika Barcelona, October 24, 2018

1 0

RPM Correspondence
by Mary Wong Oct. 24, 2018

Oct. 24, 2018

As requested by Phil Corwin, one of the two RPM co-chairs who spoke at the Council’s open mic session that just concluded, please find attached the correspondence referred to by him and Brian Beckham. Best regards, Mary (on behalf of Phil and Brian) From: "BECKHAM, Brian" <brian.beckham(a)wipo.int> Date: Wednesday, October 24, 2018 at 14:50 To: Heather Forrest <haforrestesq(a)gmail.com>, Mary Wong <mary.wong(a)icann.org>, "Donna.Austin(a)team.neustar" <Donna.Austin(a)team.neustar>, "rafik.dammak(a)gmail.com" <rafik.dammak(a)gmail.com> Cc: "Corwin, Philip" <pcorwin(a)verisign.com>, Kathy Kleiman <kathy(a)kathykleiman.com>, "Paul D. McGrady Jr." <PMcGrady(a)winston.com>, Samantha Eisner <Samantha.Eisner(a)icann.org> Subject: [Ext] Fw: Correspondence on behalf of George Kirikos Dear Councilors, As mentioned in-person, FYI the below and attached. Kind regards, ________________________________ From: Bernstein, Andrew <abernstein(a)torys.com> Sent: Wednesday, October 24, 2018 4:59 AM To: samantha.eisner(a)icann.org; BECKHAM, Brian; kathy(a)dnrc.tech; pcorwin(a)verisign.com; mcgradygnso(a)gmail.com; gregshatanipc(a)gmail.com Cc: Robin Gross; George Kirikos; icann(a)leap.com Subject: Correspondence on behalf of George Kirikos Dear Sirs/Mesdames, We are counsel for George Kirikos. Please see the attached correspondence. Regards, Andrew Bernstein P. 416.865.7678 | F. 416.865.7380 | 1.800.505.8679 79 Wellington St. W., 30th Floor, Box 270, TD South Tower Toronto, Ontario M5K 1N2 Canada | www.torys.com [torys.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.torys.com&d=DwMFAw&…> [Torys LLP][torys.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.torys.com&d=DwMFAw&…> This email and any attachments are for the sole use of the intended recipients and may be privileged or confidential. Any distribution, printing or other use by anyone else is prohibited. If you are not an intended recipient, please contact the sender immediately, and permanently delete this email and attachments. Le présent courriel et les documents qui y sont joints sont exclusivement réservés à l'utilisation des destinataires concernés et peuvent être de nature privilégiée ou confidentielle. Toute distribution, impression ou autre utilisation est interdite aux autres personnes. Si vous ne faites pas partie des destinataires concernés, veuillez en informer immédiatement l'expéditeur, ainsi que supprimer ce courriel et les documents joints de manière permanente. World Intellectual Property Organization Disclaimer: This electronic message may contain privileged, confidential and copyright protected information. If you have received this e-mail by mistake, please immediately notify the sender and delete this e-mail and all its attachments. Please ensure all e-mail attachments are scanned for viruses prior to opening or using.

1 0