June 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

RPM Working Group status report on its Council-approved data collection exercise
by Mary Wong Aug. 15, 2018

Aug. 15, 2018

Dear Councilors, Please find attached the first report from the RPM Review PDP Working Group, summarizing where things stand with the extensive data collection effort that the Council approved in September 2017, for the Sunrise and Trademark Claims RPMs. You may recall that the Council’s approval also expressly requested monthly reports beginning in January 2018. As the Request for Proposal was issued at the end of January, with interested potential vendors beginning to engage in February, the report consolidates the January and February activities. It also includes the full RFP timeline. Please let staff or the current Working Group chairs (Kathy Kleiman and Phil Corwin, cc’d on this email) know if you have any questions or comments. Thank you! Cheers Mary

3 2

Status Update: Privacy and Proxy Services Accreditation Implementation Review Team
by Darcy Southwell July 17, 2018

July 17, 2018

Dear Councilors, I wanted to provide you with an update regarding the Privacy and Proxy Services Accreditation Implementation Review Team. Accreditation Agreement IRT members have been working with Staff for some time on the draft accreditation agreement and have gotten to a place where most of the language is supported by a general consensus. However, there is one key issue that remains unresolved – the PSWG insists the contract require Privacy/Proxy providers to respond to “high priority” requests within 24 hours. In Puerto Rico, a small group of registrars met with key PSWG representatives to try to reach a resolution on this issue, and then the entire IRT working group met again to continue attempts to reach a resolution. The discussion has continued on the email list, but remains unresolved. It is the PSWG’s position that disclosure of customer information for “high priority” requests must be done within 24 hours because lives are in danger. They were clear in their statements during the small group meeting in Puerto Rico that these “high priority” requests should ideally be responded to immediately upon receipt but at least within one hour. The PSWG feels they have compromised extensively by agreeing to 24 hours. Registrar members of the IRT are concerned with the contractual language for a few reasons: (1) it creates a presumption of immediate disclosure (assuming the provider doesn’t have to perform any investigation/verification relating to the request, (2) a potential demand to bypass or ignore due process, and 3) creates an unworkable expectation of privacy/proxy providers around the globe, many of whom who do not operate with 24x7 staffing for this type of issue. Some registrar members have also expressed concern that establishing this 24-hour disclosure requirement is stepping beyond the policy recommendations of the PDP and effectively creating new policy. Accreditation Pricing In Puerto Rico, Staff presented its accreditation pricing model, based on simple cost recovery for ICANN. IRT member asked a number of questions about the detail behind the pricing model, and await that detail from Staff. Based on various meetings in Puerto Rico, some IRT members expressed concern that the pricing model simply mirrors the registrar accreditation model and was not based on any sort of actual cost-recovery plan. And as mentioned on the Council list last month and during our Council meetings in Puerto Rico, there is also concern that some affected departments within ICANN org are not aware of the impact this program may have on its needs for personnel or other support. Data Escrow Specification Significant revisions were needed by Staff to adjust the current registrar data escrow specification to fit into this accreditation program. Staff is expected to deliver that draft to the IRT this week. Last week’s meeting was canceled due to the AdobeConnect issues. This week’s meeting was canceled to allow staff time to get the data escrow specification draft done and circulated to the members. Next meeting should be Tuesday, April 10. Staff has indicated the proposed documents will be ready for publication for public comment in late April or Early May. I understand this issue will be listed for discussion on our April 26, 2018, Council meeting agenda. Thanks, Darcy ---------------- Darcy Southwell | Compliance Officer M: +1 503-453-7305 │ Skype: darcy.enyeart

2 6

[public comment] New Fellowship Approach – Should the Council Respond?
by Ayden Férdeline July 3, 2018

July 3, 2018

Dear all, In our wrap up session on Thursday, I committed to reviewing the [Draft Proposal of the New Fellowship Program Approach](https://www.icann.org/public-comments/fellowship-proposal-2018-06… and briefly bulleting where I think the Council should consider responding. In short, I think the Council does not need to respond to this comment, as individual GNSO Stakeholder Groups/Constituencies would be better placed to do so. However if the Council were to respond, I would suggest we focus our remarks on: - the proposed metrics for measuring the performance of the fellowship program and how these might be improved (at present, two of the four proposed metrics are ‘number of applications by region’ and ‘number of applications by sector [stakeholder group]’, both of which will not help us understand whether the program is actually bringing active participants into the community’s policy work); and - the willingness of the GNSO to be involved in the selection process of future fellows at the Stakeholder Group/Constituency level. In addition, the proposed new approach calls for SO/ACs to be involved in identifying the skills that fellows should possess. I was thinking, when the GNSO initiates new Policy Development Process Working Groups in the future, perhaps we can add a new section to the working group initiation template to include desired skills in fellows relevant to that working group, which could then be communicated to the fellowship program administrators and selection committee for their information when assessing/recruiting candidates? Finally, the consultation notes that, “budgetary decisions are not a part of this process,” so we are not being asked at this time to comment on the proposed cost implications. Looking forward to hearing your thoughts on whether or not we should respond here. Best wishes, Ayden Férdeline

5 4

Reminder: Document and Motion deadline Monday, 9 July 2018 at 23:59 UTC for the GNSO Council Meeting 19 July 2018 at 12:00 UTC
by Nathalie Peregrine July 2, 2018

July 2, 2018

Dear all, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Monday 9 July 2018 at 23:59 UTC) of the GNSO Council Meeting on Thursday 19 July 2018 at 12:00 UTC. Motions should be sent to the Council mailing list by a councilor and will then be posted on the Wiki at: https://community.icann.org/x/DYNHBQ Thank you very much. With kind regards, Nathalie

1 1

GNSO Video Interviews in ICANN62
by Ariel Liang June 28, 2018

June 28, 2018

Dear GNSO Councilors, Happy the end of ICANN62! Communications Department has produced a few video interviews for the GNSO this meeting. Special thanks to Heather, Donna, Rafik, Jeff, Cheryl, Barbara, John, Wolf-Ulrich, Tatiana, Robin, Claudia, Steve, and Martin for their participation in the interviews! You may view the videos following the links below. These videos have also been featured in the ICANN62 newsletter. In particular, the video of the GNSO Council Leadership discussing EPDP was the headline of today’s newsletter. There was a social media push of this video across different platforms (e.g., Twitter, Facebook, Linkedin). Staff will feature this video on the GNSO website and also include it (and the other videos) in the post ICANN meeting report. ICANN62 GNSO Council Leadership * GNSO Experiences with GDPR During the Policy Forum<https://youtu.be/iHPMeTA1uf8> SubPro PDP * New gTLD Subsequent Procedures<https://youtu.be/ujErN_AuTww> GNSO Learn Course Videos * Intro to the Commercial Stakeholder Group<https://youtu.be/w7WrrJNIOqE> * Intro to the Non-Commercial Stakeholder Group<https://youtu.be/uJTU2LwdEn4> * Intro to the Business Constituency<https://youtu.be/PFoeUWHdSpQ> * Intro to the Not-for-Profit Operational Concerns Constituency<https://youtu.be/6LqyLoI_TJY> Have a safe trip back, and see you in Barcelona! Best Regards, Ariel Ariel Xinyue Liang Policy Analyst | Washington, DC Internet Corporation for Assigned Names and Numbers (ICANN)

1 0

Comms on EPDP progress
by Heather Forrest June 28, 2018

June 28, 2018

Dear Council colleagues, An immediate follow up on communication of EPDP progress to the wider community. Donna, Rafik and I have completed a brief video interview (4-5 minutes total, they tell us) highlighting the significant progress made on the EPDP charter this week. We will continue to work with the comms team to get the message out to the broader community - at this stage a social media campaign, policy newsletter coverage, and other ideas are being explored. To be continued - Best wishes, Heather

5 7

GAC Communiqué
by Johan Helsingius June 28, 2018

June 28, 2018

FYI, the final GAC ICANN62 communiqué attached. Julf

1 1

GAC Communique
by Michele Neylon - Blacknight June 28, 2018

June 28, 2018

Attached -- 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

1 0

Comments on the draft EPDP Charter
by Stephanie Perrin June 28, 2018

June 28, 2018

I have made extensive comments to the document. Stephanie Perrin

2 3

Proposed agenda GNSO Council Wrap Up Session
by Marika Konings June 28, 2018

June 28, 2018

Dear All, Please find below the proposed agenda for the GNSO Council wrap up session. As a reminder, the wrap up takes place today from 12.15 – 13.15 in Salon 7. Best regards, Marika Proposed Agenda for GNSO Council Wrap Up Session 1. volunteers for the GNSO Review of the GAC Communique, 2. volunteers to work with Donna to develop input to the short term and long term improvements for reviews (deadline for comments: 31 July). 3. Council input on draft proposal of the new fellowship program approach (deadline for comments: 27 July) 4. EPDP DT a. Confirmation of next DT call b. Leadership EOI: i. Deadline for submissions ii. Confidentiality iii. Who reviews/decides? iv. Impact on timeline c. EPDP Team Composition i. Any concerns about latest draft? ii. GNSO Council liaison d. EPDP Charter i. Commitment to get comments / proposed edits in as soon as possible ii. Encourage list discussion to resolve differences 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<http://learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-…>.

1 0

Re: [council] [Epdp-dt] Unified Access Model
by Johan Helsingius June 28, 2018

June 28, 2018

On 27-06-18 17:02, Johan Helsingius wrote: > Looking forward to the GAC/Board meeting. Will report back. Again apologies for the rather unpolished and unstructured notes, but wanted to get them to you promptly. >From the GAC / board discussion on GDPR: - Does the board plan adjustments to temp spec? Göran confirmed the discussion should happen in the GNSO EPGP. Chris Disspain stated that the board doesn't plan any changes, but doesn't rule it out. - Unfied Access Model Org will seek guidance from DPAs based on model proposed by icann.org. progress depends on if org gets advice from DPAs, and what the advice is - Coordination of the different threads and efforts Chris Disspain sees EPDP and access model as parallel efforts, but "there is a framework for coordination", the board will assess the situation each 90 days as it decides about renewing temporary specification, closely affiliating with GNSO and GAC. Org is eagerly waiting for budget input from GNSO On a question on GAC participation/liaison with the EPDP, Manal did mention the wish for 5 members, and mentioned desire for equal / balanced representation. There was concern expressed about scope (wanting access and accreditation included), but Chris Disspain stated that from the point of timing, it might be better to do access separately, perhaps as another temporary specification (that can then later be made the subject of a PDP / EPDP).

2 2

GAC on EPDP
by Johan Helsingius June 28, 2018

June 28, 2018

Some quick heads-up notes from the GAC discussion on the EPDP. The GAC discussion presented issues to be discussed with the GNSO and the board: - Membership - GAC wants "parity with GNSO stakeholder groups" - They want to know the current thinking on scope, expected timeline in determining scope, and incorporating GAC input on scope - Respective roles of board and GNSO in defining scope - Who is in charge of overall process? Julf

5 6

Heqads up - GAC advice on GDPR
by Johan Helsingius June 27, 2018

June 27, 2018

GAC is still busy drafting their Panama Communiqué, but it looks like it will contain advice to the board with regards to GDPR / Whois / Temporary Specification that will contain something like: 1. GAC advices the ICANN Board to take all steps necessary to ensure development and implementation of a access model that addresses accreditation, authentication, access and accountability, and applies to all contracted parties as quickly as possible 2. GAC asks the ICANN Board to publish status report four weeks prior to ICANN63 In the rationale, they state "In order to protect the public interest, as well as the secure, stable, and resilient operation of the DNS, the development and implementation of a unified access model is of utmost importance. The GAC considers that direct involvement and action is required by ICANN Org to facilitate and support this." They will also have advice on IGO identifiers, basically being unhappy that the board hasn't followed previous advice. Julf

1 0

Please review: GNSO Council motions 27 June 2018
by Nathalie Peregrine June 27, 2018

June 27, 2018

Dear all, Please find below the resolutions voted during the GNSO Council meeting held today in Panama, on Wednesday 27 June 2018. These will be posted shortly on the Resolutions page<https://gnso.icann.org/en/council/resolutions> of the GNSO web site. Motion to approve the Customer Standing Committee Amended Charter Submitted by Donna Austin Seconded by Heather Forrest Whereas: 1. The Customer Standing Committee (CSC) was established as one of the post IANA Transition entities and conducted its first meeting on 6 October 2016. 2. The ICANN Bylaws, Section 17.3 (c) and the CSC Charter required the ccNSO and RySG to conduct a review of the CSC Charter one year after the first meeting of the CSC. 3. In May 2017, a drafting team appointed by the ccNSO and RySG developed a Terms of Reference for the Charter Review, which was subsequently adopted by the ccNSO and RySG in July 2017. 4. The ccNSO and RySG appointed members to form the Charter Review Team from their respective SO and SG to conduct a review of the CSC Charter in accordance with the Terms of Reference. 5. The Charter Review Team conducted a series of consultations with the CSC, the direct customers of the IANA naming function, the independent PTI Directors, and the community at large and published an Initial Report of their findings and an Amended CSC Charter for public comment on 11 April 2018 until 1 June 2018. 6. The GNSO Council discussed the Initial Report during their meeting of 24 May 2018, and submitted comments on the Initial Report as part of the public comment process. 7. The public comment period resulted in a number of comments that were considered and addressed by the Charter Review Team in their Final Report and Amended Charter. 8. The GNSO Council, along with the ccNSO Council, is required to ratify any recommended changes to the CSC Charter. 9. The ccNSO and GNSO Councils discussed the Charter Review process during their most recent face-to-face meeting in San Juan, on 12 March 2018, and are expected to discuss the Final Review<https://gnso.icann.org/sites/default/files/file/field-file-attach/csc-chart…> and Amended Charter<https://gnso.icann.org/sites/default/files/file/field-file-attach/csc-revis…> at the forthcoming ICANN meeting in Panama, on 27 June 2018. Resolved: 1. The GNSO Council approves the changes made to the CSC Charter as a result of the Charter Review Process, and will inform the ccNSO Council accordingly. 2. The GNSO Council will work on a joint communication with the ccNSO Council to inform the CSC that the Amended Charter has been ratified and should now be put into place. 3. The GNSO Council also notes the recommendation in the Final Report that the ccNSO and GNSO Councils conduct an analysis of the requirements of the IANA Naming Function Review and the CSC Effectiveness Review with a view to creating synergies and avoiding overlap and has appointed two Councilors to conduct the recommended analysis in cooperation with two representatives from the ccNSO. 4. The GNSO Council thanks the CSC Review Team for their efforts in undertaking the Review. Vote results<https://gnso.icann.org/sites/default/files/file/field-file-attach/gnso-coun…> Motion – Completion of the Final Report of the IGO/INGO Access to Curative Rights Protection Mechanisms PDP (Curative Rights PDP) Submitted by Heather Forrest Seconded by Michele Neylon Whereas, 1. The origin of the IGO/INGO Access to Curative Rights Protection Mechanisms Policy Development Process (Curative Rights PDP) traces back to a consensus recommendation from a previous PDP, the Protection of IGO and INGO Identifiers in All gTLDs PDP (IGO/INGO Protection PDP). The IGO/INGO Protection PDP considered whether and how the names and acronyms of international governmental organizations (IGOs) and international non-governmental organizations (INGOs) should be protected at the top and second levels of the domain name system (DNS). This earlier PDP resulted in a number of recommendations that were inconsistent with GAC advice on this topic. On 30 April 2014, the ICANN Board approved the PDP recommendations that were consistent with GAC advice, so that the GAC, GNSO and the affected community groups could continue to work on reconciling the remaining inconsistencies. 2. A faciliated dialogue between the GAC and GNSO took place at ICANN58 in March 2017. Based on these discussions, in May 2017, the GNSO Council agreed to initiate a new PDP to revisit the IGO/INGO Protection PDP’s recommendation concerning certain Red Cross names. 3. On 5 June 2014, the Council of the Generic Names Supporting Organization (GNSO) chartered the Curative Rights PDP. This new PDP was initiated to evaluate (i) whether the UDRP and/or URS should be amended to enable their access and use by IGOs and INGOs whose identifiers had been recommended for protection by the IGO-INGO Protection PDP and if so, in what way; or (ii) whether a separate narrowly-tailored procedure modeled on these curative rights protection measures to apply only to protected IGO and INGO identifiers should be developed. 4. The Curative Rights PDP Working Group commenced its work in August 2014 and issued its Initial Report for public comments in January 2017, with the public comment period closing on 30 March 2017. Following its analysis of the input received, the Curative Rights PDP Working Group came to agreement on modifying one of its initial recommendations by ICANN59 in June 2017. 5. Since June 2017, the Curative Rights PDP WG has been engaged in trying to reach consensus on one remaining issue concerning IGO jurisdictional immunity. In December 2017, a Working Group member filed an appeal pursuant to Section 3.7 of the GNSO Working Group Guidelines<https://gno.icann.org/sites/default/files/file/field-file-attach/annex-1-gn…> (the Guidelines) to challenge the mechanisms the Co-Chairs proposed be used to determine consensus in relation to this remaining issue. An attempt to resolve the member’s concerns with the PDP Co-Chairs took place in January 2018 in accordance with the Guidelines. Following unsuccessful resolution with the Co-Chairs, the matter was raised with the GNSO Council Chair as prescribed by Section 3.7. Discussions between the GNSO Council Chair, the GNSO Council liaison, the appellants and the PDP Co-Chairs culminated in a proposal for the GNSO Council Liaison to meet with and gather inputs from WG members at and after ICANN61 to assist in the consensus-building process by providing WG members with an opportunity to express their views on the WG’s draft recommendations. A summary report of those meetings was prepared and shared with the Working Group in April 2018 in resolution of the Section 3.7 appeal, and the GNSO Council liaison offered to continue to support the WG in developing its Final Report. As of 16 June 2018, the Working Group is continuing to work toward a Final Report. 6. In January 2018, the GNSO Council held a Strategic Planning Session at which the Council agreed that, to ensure effective allocation of resources and improve management of the community’s workload, a timely resolution of policy development processes should be a priority. 7. At its May 2018 meeting, the GNSO Council liaison informed the Council that the Curative Rights PDP would aim to wind up its work by June 2018. 8. As the scope of the Curative Rights PDP includes consideration of the applicability and usability of existing second level dispute resolution processes (i.e. curative mechanisms) in relation to IGO/INGO names and acronyms, its outcome is likely to affect the full scope of the final protections that are ultimately decided upon for IGO acronyms, and thus the differences that remain between GAC advice and conclusions of the earlier IGO/INGO Protection PDP. Given the length of time that has elapsed since the Board first placed IGO acronyms on a temporary reserved list and the possibility of additional conflict between GAC advice and GNSO policy on the topic of IGO protections, the GNSO Council believes it is imperative that the Curative Rights PDP is concluded in a timely and effective manner. 9. On 10 June 2018, a new Section 3.7 appeal was made under the GNSO Working Group Guidelines challenging the involvement of the PDP Chair (the other Co-Chair having resigned in May), the GNSO Council liaison and policy staff in developing the PDP’s Final Report. This new appeal is currently proceeding through the recommended steps in the GNSO Working Group Guidelines. The appellant has expressed willingness for the substantive work of the PDP to continue towards resolution of the Final Report while the appeal process progresses. 10. Following consultation with the Working Group Chair, GNSO Council Liaison, and GNSO Council leadership team, and notwithstanding the most recent appeal, the GNSO Chair proposed on 13 June 2018 that the target date for completing and submitting the Curative Rights PDP Final Report to the GNSO Council be revised to July 2018 to provide the Working Group with additional time necessary to complete its work and finalize the Final Report. Resolved, 1.The GNSO Council acknowledges the effort of the Curative Rights PDP Working Group since ICANN60 to reach consensus on its final recommendations, and requests that the Final Report be submitted in time to meet the July 2018 GNSO Council meeting document deadline. The GNSO Council directs ICANN staff to inform the Working Group that, in line with the Council’s priority to ensure responsible allocation of resources and timely management of the PDP, the GNSO Council expects to consider this matter at its July 2018 meeting. 2. The GNSO Council acknowledges and appreciates the effort of Susan Kawaguchi in the role of GNSO Council Liaison to assist in resolving the Section 3.7 appeals and to facilitate the group’s efforts to achieve the milestone of a Final Report in a timely manner. Vote results<https://gnso.icann.org/sites/default/files/file/field-file-attach/gnso-coun…> 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

GNSO Chair election timeline and incoming councilors
by Nathalie Peregrine June 27, 2018

June 27, 2018

Dear all, Please see attached the timeline for the GNSO Chair nomination open date and election. Please remember that new councilors are eligible for nomination as Council chair so the Stakeholder Groups and Constituencies’ elections should be over by the date of nominations. New councilors are to be announced on the 25th August 2018. 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

Re: [council] [Epdp-dt] EPDP Scope Matrix
by McGrady, Paul D. June 27, 2018

June 27, 2018

Thanks Marika and Michele. All, while I appreciate Keith’s work, I actually find it unhelpful and a step backwards. It appears that much of the content of Section 4 of the Temp Spec has been pushed off to another ePDP rather than being dealt with in context and holistically as the Board in its motion, the SSAC in its advice and the European Commission in its public statement yesterday in our combined GAC/GNSO Session indicate are our next steps here. Let’s not revert back to trying to carve up the Temp Spec into pieces and push off the inconvenient bits. It is time for the community to solve this entire problem. For transparency, I am copying in the usual Council list. I understand that we set up a separate list for this work, but our work here in Panama has been in public and transparent. I think we should stick with that. Best, Paul From: Epdp-dt [mailto:epdp-dt-bounces@icann.org] On Behalf Of Michele Neylon - Blacknight Sent: Wednesday, June 27, 2018 7:15 AM To: Marika Konings <marika.konings(a)icann.org>; Epdp-dt(a)icann.org Subject: Re: [Epdp-dt] EPDP Scope Matrix Very helpful – thanks -- 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: Epdp-dt <epdp-dt-bounces(a)icann.org<mailto:epdp-dt-bounces@icann.org>> on behalf of Marika Konings <marika.konings(a)icann.org<mailto:marika.konings@icann.org>> Date: Wednesday 27 June 2018 at 06:45 To: "Epdp-dt(a)icann.org<mailto:Epdp-dt@icann.org>" <Epdp-dt(a)icann.org<mailto:Epdp-dt@icann.org>> Subject: [Epdp-dt] EPDP Scope Matrix Dear All, On behalf of Keith, please find attached the scope matrix that was referenced during the discussions yesterday. Best regards, Marika 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<http://learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-…>. ________________________________ 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.

1 0

Motion to approve the Customer Standing Committee Amended Charter
by Austin, Donna June 27, 2018

June 27, 2018

Hi All The documents Heather forwarded to the Council related to the Customer Standing Committee, particularly the Amended Charter of the Customer Standing Committee, are relevant to the Motion to approve the Customer Standing Committee Amended Charter that I forwarded to the Council list last Saturday. All documents are attached here for ease of reference. Thanks Donna From: council [mailto:council-bounces@gnso.icann.org] On Behalf Of Austin, Donna via council Sent: Saturday, June 16, 2018 6:38 PM To: council(a)gnso.icann.org Subject: [council] Motion to approve the Customer Standing Committee Amended Charter Dear Councilors Please find attached a motion for consideration by the Council on 27 June 2018, to approve the Customer Standing Committee Amended Charter. I expect that the Final Report of the Customer Standing Committee Charter Review, which includes the Amended Charter, will be provided to the Council on Monday or Tuesday of next week. Thanks Donna Donna Austin Neustar, Inc. / Senior Policy Manager, Registry Solutions Mobile: +1 310 890 9655 donna.austin(a)team.neustar<mailto:donna.austin@team.neustar> / Website: home.neustar<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.home.neustar_&d=DwM…> Follow Neustar: LinkedIn<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.linkedin.com_compan…> / Twitter<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.twitter.com_neustar…> Reduce your environmental footprint. Print only if necessary. ________________________________ The information contained in this email message is intended only for the use of the recipient(s) named above and may contain confidential and/or privileged information. If you are not the intended recipient you have received this email message in error and any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately and delete the original message.

1 1

Updated Final Proposed Agenda GNSO Council Meeting - 27 June 2018 at 13:00 local time -18:00 UTC
by Nathalie Peregrine June 27, 2018

June 27, 2018

Dear all, Please below find the updated final proposed agenda for the ICANN62 GNSO Council Meeting on 27 June 2018 at 13:00 local time, 18:00 UTC. Final Proposed Agenda 27 June 2018 Please note that all documents referenced in the agenda have been gathered on a Wiki page for convenience and easier access: https://community.icann.org/x/xBUFBQ [community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> This agenda was established according to the GNSO Operating Procedures [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> v3.3, updated on 30 January 2018 For convenience: · An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda. · An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda. Coordinated Universal Time: 18:00 UTC: https://tinyurl.com/ybuhhqmo [tinyurl.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__tinyurl.com_ybuhhqmo&d…> Local time in Panama: 13:00 11:00 Los Angeles; 14:00 Washington; 19:00 London; 23:00 Islamabad; (Thursday 28 June) 03:00 Tokyo; 04:00 Hobart GNSO Council Meeting Remote Participation: https://62.schedule.icann.org/meetings/699481 [62.schedule.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__62.schedule.icann.org_…> Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call. ___________________________________ Item 1. Administrative Matters (5 mins) 1.1 - Roll Call 1.2 - Updates to Statements of Interest 1.3 - Review / Amend Agenda 1.4 - Note the status of minutes for the previous Council meetings per the GNSO Operating Procedures: Minutes [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…> of the GNSO Council meeting on the 24 May 2018 were posted on 14 June 2018 Minutes of the GNSO Council meeting on the 12 June 2018 will be posted on 28 June 2018 Item 2. Opening Remarks / Review of Projects & Action List (10 minutes) 2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…>and Action Item List [community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> Item 3. Consent Agenda (0 minutes) Item 4: COUNCIL UPDATE – SSAC to Brief the GNSO on Use of Emoji in Domain Names (15 minutes) On 2 November 2017, the ICANN Board, in considering SAC095 [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…>, adopted [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> the following: · Resolved (2017.11.02.09), the Board hereby directs that conformance to IDNA2008 and its successor will continue to be a necessary condition to determine valid IDN TLD labels. · Resolved (2017.11.02.10), the Board requests that the Country Code Names Supporting Organization (ccNSO) and the Generic Names Supporting Organization (GNSO) engage with the SSAC to more fully understand the risks and consequences of using a domain name that includes emoji in any of its labels,and inform their respective communities about these risks. · Resolved (2017.11.02.11), the Board requests that the ccNSO and GNSO integrate conformance with IDNA2008 and its successor into their relevant policies so as to safeguard security, stability, resiliency and interoperability of domain names. · Resolved (2017.11.02.12), the Board directs the ICANN CEO, or his designee(s), to engage with gTLD and ccTLD communities on the findings and recommendations in SAC095 Accordingly, the GNSO Council has invited the Security and Stability Advisory Committee (SSAC) to brief the GNSO Council on the risks of emoji as domain names in any of its labels and to help inform what specific steps the GNSO may need to take to properly account for those risks. Here, the Council will receive a briefing from Patrik Fältström, to help the Council determine what next steps may be necessary. 4.1 – Update (Patrik Fältström - SSAC) 4.2 – Council discussion 4.3 – Next Steps Item 5: COUNCIL VOTE – IGO-INGO Access to Curative Rights Protection Mechanisms (15 minutes) The IGO-INGO Access to Curative Rights Protection Mechanisms PDP WG had been working to resolve a final recommendation relating to IGO jurisdictional immunity and registrants’ rights to file court proceedings. During the course of trying to determine consensus on a set of options for this final recommendation, several WG members challenged the proposed method for determining initial consensus and appealed via section 3.7 of the GNSO Working Group Guidelines [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…>. Following discussions with the members utilizing the appeal process and the GNSO chair and the Council liaison to the WG, the Council liaison to the WG solicited input from the WG members on the set of options under consideration. The WG has since held several meetings to try and reach final consensus for its Final Report, including opening up the formal consensus call on 10 May 2018. The WG Chair has designated his assessment of consensus levels for recommendations 1-4, as well as for the 6 options under consideration for recommendation 5. A second section 3.7 appeal was filed in June 2018, to assert that the Chair, Council liaison, and policy staff are not performing their role, that short deadlines are being imposed, and that proper procedure is not being followed for the consensus call. With the connection to a previous PDP on IGO protections, where work continues to reconcile inconsistencies with GAC Advice, and the GNSO Council’s emphasis on improving the timely resolution of PDPs, the Council requests that the Final Report be delivered in time for consideration for the July 2018 GNSO Council meeting. Here, the Council will vote on whether or not to request delivery of the Final Report by the Council’s July meeting. 5.1 – Presentation of motion [community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> (Heather Forrest) 5.2 – Council discussion 5.3 – Council vote (voting threshold: simple majority) Item 6: COUNCIL VOTE – Approval of Changes Made to the Customer Standing Committee (CSC) Charter (15 minutes) The ccNSO and RySG appointed members to form the Charter Review Team from their respective SO and SG to conduct a review of the Customer Standing Committee (CSC) Charter in accordance with the Terms of Reference. The CSC Charter review team (RT) sought comment and input on its findings and proposed amendments to the CSC Charter, as included in the RT's Initial Report [community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di…>. On 11 May 2018, Council member volunteers were sought to develop a draft comment for Council consideration for public comment [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> on the Initial Report on Review of the CSC Charter. The Council discussed the Initial Report during their meeting on 24 May 2018 and submit their comments during the public comment process. Taking into account comments received, the Review Team prepared a Final Report and Amended Charter [community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…>for consideration and adoption by the ccNSO and GNSO Councils. Here, the Council will vote to approve the changes made to the CSC Charter as a result of the Charter Review Process. 6.1 – Presentation of motion [community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> (Donna Austin) 6.2 – Council discussion 6.3 – Council vote (voting threshold: simple majority) Item 7: COUNCIL UPDATE – Protections for Certain Red Cross Names in All gTLDs Policy Amendment Process (10 minutes) Following discussions around possible ways of reconciling inconsistent GAC advice and GNSO policy recommendations relating to National Society names of the Red Cross Movement and the two names of the international components of the Movement (http://sched.co/9xr2 [sched.co]<https://urldefense.proofpoint.com/v2/url?u=http-3A__sched.co_9xr2-29&d=DwMG…>), the ICANN Board passed a resolution requesting that the GNSO Council initiate the process outlined in Section 16 of the GNSO’s Policy Development Process (PDP) Manual, which sets forth the requisite steps for amending policy recommendations that have been approved by the GNSO Council but not yet approved by the ICANN Board (https://www.icann.org/resources/board-material/prelim-report-2017-03-16-en#… [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>). The Board’s request related to the 190 Red Cross National Society names and the two international movement names and a limited defined set of their variants. On 03 May 2017, the Council resolved [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> to initiate the Section 16 process as requested by the Board, which resulted in the limited reconvening of the original PDP on Protection of IGO and INGO Identifiers in All gTLDs. The Reconvened WG began its deliberations on 14 June 2017 and is nearing completion of its preliminary work, expecting to publish its Initial Report in the near future. Here, the Council will receive an update on the status of the Reconvened WG. 7.1 – Update (Thomas Rickert - WG Chair) 7.2 – Council discussion 7.3 – Next Steps Item 8: COUNCIL VOTE – Initiation of Expedited Policy Development Process on the ICANN Board Temporary Specification (30 minutes) On 11 May 2018, ICANN released the Temporary Specification [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> on gTLD Registration Data, which served as the main agenda topic for the subsequent Board Workshop in Vancouver. This proposed Temporary Specification provides an interim solution until the community completes a policy development process on the temporary specification which is expected to complete within a one year period. On 14 May 2018, ICANN released a revised Temporary Specification [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> and scheduled a webinar on 15 May 2018 to discuss the topic. The Board passed a resolution [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>, noting their intent to adopt the Temporary Specification on or around 17 May 2018. On 17 May 2017, the ICANN Board approved [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> the proposed Temporary Specification for gTLD Registration Data [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>, which establishes temporary requirements for how ICANN and its Contracted Parties will comply with both ICANN contractual requirements and the European Union’s General Data Protection Regulation (GDPR). On 21 May 2018, the Council and SG/C chairs met to discuss possible next steps for the ICANN Board adoption of the Temporary Specification. On its 24 May 2018 meeting, the Council discussed possible next steps following ICANN Board adoption of the Temporary Specification. On 5 June 2018, the Council met with the ICANN Board to discuss a set of questions [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_corr…>the Council and ICANN Board developed, as well as overall next steps. Subsequently, Council leadership and staff developed a Mindmap [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…> to help understand the elements around a potential Expedited Policy Development Process (EPDP), such as timing, team composition, and planning for ICANN62. On 12 June 2018, the Council held an Extraordinary Council Meeting to discuss next steps on addressing the Temporary Specification. There, the Council agreed in principle that an EPDP was the right way to address the issue and that next steps should be taken, specifically drafting of the charter and initiation. In the period leading up to and at ICANN62, the Council has worked together to draft the charter for the EPDP. Here, the Council will vote to initiate an EPDP on the Temporary Specification, as well as to adopt the EPDP’s charter. 8.1 – Presentation of motion [community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> (Council Leadership) 8.2 – Council discussion 8.3 – Council vote (voting threshold: Supermajority) Taking this action is within the GNSO’s remit as outlined in ICANN’s Bylaws as the GNSO ‘shall be responsible for developing and recommending to the Board substantive policies relating to generic top-level domains and other responsibilities of the GNSO as set forth in these Bylaws’ (Art.11.1). Furthermore, this action complies with the requirements set out in Annex A-1 GNSO Expedited Policy Development Process of the ICANN Bylaws as well as the EPDP Manual. Item 9: ANY OTHER BUSINESS (15 minutes) 9.1 – GNSO Chair election timeline 9.2 – Call for Volunteers - Revised ICANN Procedure Handling WHOIS Conflicts with Privacy Law 9.3 – Open Microphone ________________________________ Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article 11, Section 11.3(i)) See https://www.icann.org/resources/pages/governance/bylaws-en/#article11 [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>. Appendix 2: GNSO Council Absentee Voting Procedures (GNSO Operating Procedures, Section 4.4) See https://gnso.icann.org/sites/default/files/file/field-file-attach/op-proced… [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…> References for Coordinated Universal Time of 18:00 UTC Local time between March and October Summer in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PDT) UTC-7 (-1 day) 11:00 San José, Costa Rica (CST) UTC-6 (-1 day) 12:00 New York/Washington DC, USA (EDT) UTC-4 14:00 Buenos Aires, Argentina (ART) UTC-3 15:00 Rio de Janeiro, Brazil (BRST) UTC-3 15:00 London, United Kingdom (GMT) UTC+1 19:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 19:00 Paris, France (CEST) UTC+2 20:00 Islamabad, Pakistan (PKT) UTC+5 23:00 Singapore (SGT) UTC+8 (+1 day) 02:00 Tokyo, Japan (JST) UTC+9 (+1 day) 03:00 Sydney/Hobart, Australia (AEDT) UTC+10 (+1 day) 04:00 ---------------------------------------------------------------------------- DST starts/ends on Sunday 28 of October 2018, 2:00 or 3:00 local time (with exceptions) for EU countries and on Sunday 4 of November 2018 for the US. ---------------------------------------------------------------------- For other places see http://www.timeanddate.com [timeanddate.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.timeanddate.com_&d=…> and https://tinyurl.com/ybuhhqmo [tinyurl.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__tinyurl.com_ybuhhqmo&d…>

1 0

Slide deck GNSO Council: Strategic Outlook Trends Identification Wednesday 27 June 2018 18h30 - 19h30
by Nathalie Peregrine June 26, 2018

June 26, 2018

Dear all, On behalf of the Multistakeholder Strategy & Strategic Initiatives (MSSI) team, and in preparation for the closed GNSO Council session on Strategic Outlook Trends Identification on Wednesday 27 June 2018 from 18h30 – 19h30 in Salon 7, please find the slides attached to this email for your perusal prior to the session. 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

Fwd: [So-ac-sg-cleaders] Conveying Messages on Stephane Van Gelder to Stephane’s family
by Heather Forrest June 26, 2018

June 26, 2018

Dear Council colleagues, Please see below regarding delivering messages to the family of Stephane Van Gelder. Best wishes, Heather ---------- Forwarded message ---------- From: David Olive <david.olive(a)icann.org> Date: Tue, Jun 26, 2018 at 11:58 AM Subject: [So-ac-sg-cleaders] Conveying Messages on Stephane Van Gelder to Stephane’s family To: "so-ac-sg-cleaders(a)icann.org" <so-ac-sg-cleaders(a)icann.org>, SOAC-Leaders-ICANNMeeting-Planning < soac-leaders-icannmeeting-planning(a)icann.org> Cc: Benedetta Rossi <benedetta.rossi(a)icann.org>, Mary Wong < mary.wong(a)icann.org>, "Tanzanica S. King" <tanzanica.king(a)icann.org> Dear Community Members: Many community members have asked about a way for them to convey their thoughts and impressions of Stephane Van Gelder to Stephane’s family, including his wife Julie Talfournier Van Gelder who was here in Panama to accept the 2018 Multistakeholder Ethos Award on his behalf. As of this afternoon (Tuesday 26 June), we will be placing a small table in the Convention Center foyer each day in front of the stage, with blank notecards that anyone may use to pen a short note. ICANN organization will collect all your notes at the end of the meeting on Thursday afternoon, and will be sure to send them to Julie on the community’s behalf. Best regards, David Sent from my iPhone 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 https://mm.icann.org/mailman/listinfo/so-ac-sg-cleaders

1 0

Fwd: SSAC2018-17: SSAC Input to the Chartering of GNSO ePDP on Temporary Specification of gTLD Registration Data
by Heather Forrest June 26, 2018

June 26, 2018

Dear Council colleagues, Posting to the Council list the advice below and attached just received from the SSAC in relation to the EPDP. Best wishes, Heather ---------- Forwarded message ---------- From: Andrew McConachie <andrew.mcconachie(a)icann.org> Date: Tue, Jun 26, 2018 at 8:45 AM Subject: SSAC2018-17: SSAC Input to the Chartering of GNSO ePDP on Temporary Specification of gTLD Registration Data To: "haforrestesq(a)gmail.com" <haforrestesq(a)gmail.com> Cc: Marika Konings <marika.konings(a)icann.org>, SSAC Admin Committee < ssac-exec-comm(a)icann.org> Dear Heather Forrest, On behalf of the SSAC please find, "SSAC2018-17: SSAC Input to the Chartering of GNSO Expedited Policy Development Process on Temporary Specification of gTLD Registration Data” attached. This correspondence will also be published shortly on the SSAC’s website. Sincerely, Andrew McConachie ICANN Policy Support for the SSAC

1 0

Notes from today's HIT on EPDP
by Heather Forrest June 25, 2018

June 25, 2018

Dear Council colleagues, I took (very rough!) notes during the HIT today, and share these in the attached document. Please note - they are rough and I've captured the inputs as best and quickly as I could to help inform tomorrow's Drafting Team discussions, which will start at 0900. Best wishes, Heather

1 0

Official Announcement - 2018 Multistakeholder Ethos Award Honors Stéphane Van Gelder
by Terri Agnew June 25, 2018

June 25, 2018

https://www.icann.org/news/announcement-2018-06-25-en 2018 Multistakeholder Ethos Award Honors Stéphane Van Gelder PANAMA CITY – 25 June 2018 – The Internet Corporation for Assigned Names and Numbers (ICANN) is honored to announce the recipient of the 2018 Multistakeholder Ethos Award. This year, the community selection panel posthumously recognized a long-time member of the ICANN community: Stéphane Van Gelder. The award was presented today at ICANN62 in Panama City to Stéphane Van Gelder’s wife Julie Talfournier Van Gelder. Community member Keith Drazek presented the award on behalf of the community selection panel. He enumerated Stéphane Van Gelder’s many contributions and attested to how he was admired for “his passion, his fairness, his ability to find the best in people, and his true gift for uniting people.” Cherine Chalaby, Chair, ICANN Board, and Göran Marby, President and CEO, ICANN, also remembered Stéphane Van Gelder. Chalaby stated that Van Gelder’s “impact on the ICANN community, and many of us individually, cannot be overstated.” Marby urged community members present to continue in Stéphane Van Gelder’s spirit and “see the people behind the discussions.” Marby turned the podium over to Julie Talfournier Van Gelder, who spoke movingly about her husband, a man who she said “helped reveal the strength and skills in so many people.” The Multistakeholder Ethos Award honors members of the ICANN community who have made outstanding contributions to ICANN’s multistakeholder model of Internet governance. Stéphane Van Gelder was selected from a list of 16 nominees as the person who best demonstrated the spirit of collaboration, strongly promoting consensus. The community selection panel composed of nine members from different Supporting Organizations and Advisory Committees recognized Van Gelder for his immense dedication and commitment to ICANN’s multistakeholder model, which served as an example to others in the community. The multistakeholder model is built on achieving consensus, and Van Gelder’s contributions epitomize this ideal, making him the perfect recipient for the 2018 Multistakeholder Ethos Award. A unique point that stood out from the beginning of the community selection panel’s process was that Stéphane Van Gelder received nominations or endorsements from at least 10 different community groups, and also from several individuals and community leaders. It was an unprecedented level of support and something that the selection committee immediately recognized as important. The breadth and depth of cross-community support spoke directly to his impact representing each of the award’s criteria – breaking down silos, working across multiple groups, engaging in a collegial manner, and a record of substantive and meaningful contribution over many years. Stéphane Van Gelder’s contributions were distinct, and the level of support from the ICANN community was undeniable. From 2008 to 2012, he served on the Generic Names Supporting Organization (GNSO) Council as an elected representative of what was then called the Registrars Constituency (now the Registrar Stakeholder Group). On the GNSO Council, he served as vice chair in 2010 and was elected and served two consecutive terms as chair in 2011 and 2012. During his tenure as GNSO chair, Van Gelder oversaw and shepherded multiple key projects, including: * Completion of an extensive update of the GNSO's operating procedures. * Establishment of the Domain Name System Security (DNS) Security and Stability Analysis Working Group, working jointly with the At-Large Advisory Committee (ALAC), Country Code Names Supporting Organization (ccNSO), and Number Resource Organization (NRO). * Completion of the Fast Flux, Post-Expiration Domain Name Recovery and Inter-Registrar Transfer Policy (IRTP) Part B Policy Development Processes (PDPs), and the joint ccNSO-GNSOInternationalized Domain Name Working Group. * Launch of the IRTP Part C, Thick WHOIS, and Locking of Domain Names subject to Uniform Dispute Resolution Policy Proceedings PDPs. * Completion of the Applicant Guidebook for the 2012 New Generic Top-Level Domain (gTLD) Program and the launch of the program. Van Gelder was also a long-time contributor to the ICANN Nominating Committee, beginning in 2013, serving as its chair in 2015 and associate chair in 2017. He was a well-respected and much appreciated member of not only the GNSO, but of the broader ICANN community. His genuine passion, energy, and commitment to ICANN’s mission and his achievements in various roles across the community were second to none. All of these qualities and accomplishments strongly support the selection of Stéphane Van Gelder as the recipient of ICANN’s 2018 Multistakeholder Ethos Award. At this time when we celebrate his contributions, ICANN also extends our deepest condolences to his family, friends, and colleagues. Launched in 2014 at ICANN50, the <https://community.icann.org/x/YyOAAw> Multistakeholder Ethos Award recognizes ICANN participants who have invested in consensus-based solutions, acknowledged the importance of ICANN’s multistakeholder model of Internet governance, and contributed in a substantive way to the higher interests of ICANN’s organization and community.

1 0

Lunch open at 12:00 Salon 7 Councilors & Board members only
by Nathalie Peregrine June 25, 2018

June 25, 2018

Dear Councilors, Please ensure to be at 12:00 local time in Salon 7. The previous session will be ending at that time and the lunch buffet will be open to GNSO councilors and Board members only. Please help yourself to food upon arrival to be ready for the start of the GNSO Working session at 12:15 local time with the ICANN Board members. Thank you! 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

Fwd: [gnso-chairs] [CORRESPONDENCE] 2 Letters - Cherine Chalaby to GNSO Council Leadership
by Heather Forrest June 25, 2018

June 25, 2018

Dear Council colleagues, Good morning, welcome to Panama, and the start of ICANN62! In anticipation of today's lunchtime meeting with the ICANN Board, please find attached a letter from Cherine on behalf of Board colleagues setting out responses to our 3 questions sent on Friday on EPDP planning (picket fence, budget and discussion paper). These three questions and responses form our agenda for today's lunchtime meeting. Best wishes, Heather ---------- Forwarded message ---------- From: Board Calendaring <Board-Calendaring(a)icann.org> Date: Sun, Jun 24, 2018 at 9:57 PM Subject: [gnso-chairs] [CORRESPONDENCE] 2 Letters - Cherine Chalaby to GNSO Council Leadership To: "gnso-chairs(a)icann.org" <gnso-chairs(a)icann.org>, "gnso-secs(a)icann.org" < gnso-secs(a)icann.org> Cc: Secretary <secretary(a)icann.org>, Correspondence < Correspondence(a)icann.org>, Cherine Chalaby <cherine.chalaby(a)board.icann.org>, Board Ops Team <board-ops-team(a)icann.org> Dear Ms. Heather Forrest, Please find the attached 2 letters from Cherine Chalaby as follows: 1. 2018-06-24 in response to your 22 June 2018 letter from the GNSO Council Leadership 2. 2018-06-11 Memorializing the response to your 8 June 2018 letter in which David Olive provided answers via email to the questions proposed therein in order to respond in time for your 12 June Extraordinary Meeting. You may expect both letters to be posted to the ICANN Correspondence page: https://www.icann.org/resources/pages/correspondence. With kind regards, Wendy Profit ICANN – Senior Manager, Board Operations 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094 _______________________________________________ Gnso-chairs mailing list Gnso-chairs(a)icann.org https://mm.icann.org/mailman/listinfo/gnso-chairs

1 0

Ethos Award recipient announced
by Mary Wong June 24, 2018

June 24, 2018

Dear Councilors – FYI, should you or your community members wish to attend the Ethos Award ceremony tomorrow morning: https://www.icann.org/news/announcement-2018-06-24-en Thank you. Cheers Mary

1 0

**Updated: For your review: GNSO June 2018 Project List
by Terri Agnew June 24, 2018

June 24, 2018

**Update attached - Brian Beckham was confirmed as co-chair for RPM Dear Councilors, Attached please find the updated Project List in both red-line and clean version for your review before the Council meeting. If there are no comments, the list will be posted on the website on page: <https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_counc il_project&d=DgMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f 4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=bcZnPuqiDY4_TMPBs 3UPEUuqx-bS0HF55Trpa8n_FnY&s=YH_cwffIV-OMrgs6pTu37csGmNJ3QHxniBkjyRh9J2s&e=> http://gnso.icann.org/en/council/project and be directly viewed at : <https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_meetings _projects-2Dlist.pdf&d=DgMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM& r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=bcZnPuq iDY4_TMPBs3UPEUuqx-bS0HF55Trpa8n_FnY&s=Md4eGTKVkiG-gC-Gmw4artPvS0zM3M5oceJO4 BALy7g&e=> http://gnso.icann.org/meetings/projects-list.pdf Thanks so much, Kind regards, Terri

1 0

GNSO Council Abstention Notification Form [#278]
by ICANN June 24, 2018

June 24, 2018

1 0

Fwd: [SOAC-Leaders-ICANNMeeting-Planning] CCWG ON INTERNET GOVERNANCE - REPORT ON ACTIVITIES FROM NOVEMBER 2017 TO JUNE 2018
by Heather Forrest June 23, 2018

June 23, 2018

Dear Council colleagues, With thanks to Nigel Hickson I post this report from the CCWG-IG. Best wishes, Heather ---------- Forwarded message ---------- From: Nigel Hickson <nigel.hickson(a)icann.org> Date: Sat, Jun 23, 2018 at 8:08 AM Subject: [SOAC-Leaders-ICANNMeeting-Planning] CCWG ON INTERNET GOVERNANCE - REPORT ON ACTIVITIES FROM NOVEMBER 2017 TO JUNE 2018 To: "soac-leaders-icannmeeting-planning(a)icann.org" < soac-leaders-icannmeeting-planning(a)icann.org> Cc: Mandy Carver <Mandy.Carver(a)icann.org>, Young-eum Lee <yesunhoo(a)gmail.com > Good morning On behalf of the co-chairs of the CCWG on Internet Governance (and with apologies for lateness) I attach a Report on Activities and dialogue in the Working Group. Please distribute as is deemed appropriate and useful. Best Nigel _______________________________________________ SOAC-Leaders-ICANNMeeting-Planning mailing list SOAC-Leaders-ICANNMeeting-Planning(a)icann.org https://mm.icann.org/mailman/listinfo/soac-leaders-icannmeeting-planning

1 0

FAQ published on implementing the Temporary Specification
by Mary Wong June 22, 2018

June 22, 2018

Dear Councilors, You may be interested to know that ICANN Org has just published the following FAQ on implementing the Temp Spec: https://www.icann.org/resources/pages/gtld-registration-data-specs-faqs-201… Best regards, Mary Sent from a mobile phone, apologies for errors and brevity

1 0

GNSO Council related meetings ICANN62
by Nathalie Peregrine June 22, 2018

June 22, 2018

Dear councilors, Please find attached the ics calendar invitations for the following meetings: Monday 25 June 2018 08:00 – 08:30: GNSO Policy Briefing 12:15 – 15:00: GNSO Working session 17:00 – 18:30: High Interest Session: Community Input to GNSO Expedited PDP Charter Development Tuesday 26 June 2018 08:30 – 09:00: GNSO Policy Briefing 09:00 – 15:00 GNSO EPDP on Temporary Specification for gTLD Registration Data - Initiation Request and Charter DT meeting 11:30 – 12:30: GNSO & GAC meeting 16:30 – 16:45: Last 15 mins of Cross-Community Session: WHOIS/RDS Policy: Post-GDPR Development and Next Steps for EPDP update 17:00 – 18:30: Cross-Community Session: Accreditation and Access to Non-Public WHOIS Data Post-GDPR 18:30 – 19:30: closed Informal Council meeting Wednesday 27 June 2018 08:00 – 09:00: joint ccNSO – GNSO Council session 08:30 – 09:00: GNSO Policy Briefing 09:00 – 10:15: Placeholder for PDP discussion 13:00 – 15:00: GNSO Council meeting 18:30 – 19:30: GNSO Strategic Outlook session (closed) Thursday 28 June 2018 08:30 – 09:00: GNSO Policy Briefing 12:15 – 13:15: GNSO Wrap-Up session Alternatively, please go to the ICANN62 website schedule,<https://62.schedule.icann.org/meetings> login, and on the bottom right hand side of each meeting frame, choose ADD. This will add the meetings you select to your schedule. Once you have finished doing this go to EXPORT/ DOWNLOAD MY SCHEDULE, this will automatically add the events to your default calendar. Thank you! 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

Public comment opens: Initial Report on the Protections for Certain Red Cross Names in all gTLDs – Policy Amendment Process
by Berry Cobb June 22, 2018

June 22, 2018

Dear GNSO Council. FYI. The Reconvened PDP WG on the Red Cross names published their initial report for public comment yesterday for 40 days. After the comment period closes, the WG will review all comments and prepare its Final Report for GNSO Council consideration. The WG is targeting the August meeting. Additionally, Thomas Rickert (WG Chair) will provide a brief update to the Council at its ICANN 62 meeting next Wednesday. Thank you. B Announcement below: _____ <https://urldefense.proofpoint.com/v2/url?u=http-3A__icann.org_news_announce…> Initial Report on the Protections for Certain Red Cross Names in all gTLDs – Policy Amendment Process [icann.org] Open Date: 21 June 2018 Close Date: 31 July 2018 Originating Organization: GNSO Categories/Tags: Policy Development Brief Overview: Obtain community input on proposed recommendations for amending prior consensus recommendations with respect to the reservation protection of ICRC, IFRC, and National Societies, as instructed by the GNSO Council. This is the IGO-INGO Working Group's Initial Report. Link: <https://www.icann.org/public-comments/red-cross-protection-initial-2018-06-…> https://www.icann.org/public-comments/red-cross-protection-initial-2018-06-… <https://urldefense.proofpoint.com/v2/url?u=http-3A__icann.org_news_announce…> Read more [icann.org] Berry Cobb GNSO Policy Consultant @berrycobb

1 0

Final Proposed Agenda GNSO Council Meeting - 27 June 2018 at 18:00 UTC (13:00 - 15:00 local time)
by Nathalie Peregrine June 22, 2018

June 22, 2018

Dear all, Please below find the updated final proposed agenda for the GNSO Council Meeting on 27 June 2018 at 18:00 UTC (13:00 – 15:00 local time). Final proposed agenda 27 June 2018 – GNSO Council Meeting ICANN62, Panama Please note that all documents referenced in the agenda have been gathered on a Wiki page for convenience and easier access: https://community.icann.org/x/xBUFBQ [community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> This agenda was established according to the GNSO Operating Procedures [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> v3.3, updated on 30 January 2018 For convenience: · An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda. · An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda. Coordinated Universal Time: 18:00 UTC: https://tinyurl.com/ybuhhqmo [tinyurl.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__tinyurl.com_ybuhhqmo&d…> Local time in Panama: 13:00 11:00 Los Angeles; 14:00 Washington; 19:00 London; 23:00 Islamabad; (Thursday 28 June) 03:00 Tokyo; 04:00 Hobart GNSO Council Meeting Remote Participation: https://62.schedule.icann.org/meetings/699481 [62.schedule.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__62.schedule.icann.org_…> Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call. ___________________________________ Item 1. Administrative Matters (5 mins) 1.1 - Roll Call 1.2 - Updates to Statements of Interest 1.3 - Review / Amend Agenda 1.4 - Note the status of minutes for the previous Council meetings per the GNSO Operating Procedures: Minutes [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…> of the GNSO Council meeting on the 24 May 2018 were posted on 14 June 2018 Minutes of the GNSO Council meeting on the 12 June 2018 will be posted on 28 June 2018 Item 2. Opening Remarks / Review of Projects & Action List (10 minutes) 2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…>and Action Item List [community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> Item 3. Consent Agenda (0 minutes) Item 4: COUNCIL UPDATE – SSAC to Brief the GNSO on Use of Emoji in Domain Names (15 minutes) On 2 November 2017, the ICANN Board, in considering SAC095 [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…>, adopted [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> the following: · Resolved (2017.11.02.09), the Board hereby directs that conformance to IDNA2008 and its successor will continue to be a necessary condition to determine valid IDN TLD labels. · Resolved (2017.11.02.10), the Board requests that the Country Code Names Supporting Organization (ccNSO) and the Generic Names Supporting Organization (GNSO) engage with the SSAC to more fully understand the risks and consequences of using a domain name that includes emoji in any of its labels, and inform their respective communities about these risks. · Resolved (2017.11.02.11), the Board requests that the ccNSO and GNSO integrate conformance with IDNA2008 and its successor into their relevant policies so as to safeguard security, stability, resiliency and interoperability of domain names. · Resolved (2017.11.02.12), the Board directs the ICANN CEO, or his designee(s), to engage with gTLD and ccTLD communities on the findings and recommendations in SAC095 Accordingly, the GNSO Council has invited the Security and Stability Advisory Committee (SSAC) to brief the GNSO Council on the risks of emoji as domain names in any of its labels and to help inform what specific steps the GNSO may need to take to properly account for those risks. Here, the Council will receive a briefing from Patrik Fältström, to help the Council determine what next steps may be necessary. 4.1 – Update (Patrik Fältström - SSAC) 4.2 – Council discussion 4.3 – Next Steps Item 5: COUNCIL VOTE – IGO-INGO Access to Curative Rights Protection Mechanisms (15 minutes) The IGO-INGO Access to Curative Rights Protection Mechanisms PDP WG had been working to resolve a final recommendation relating to IGO jurisdictional immunity and registrants’ rights to file court proceedings. During the course of trying to determine consensus on a set of options for this final recommendation, several WG members challenged the proposed method for determining initial consensus and appealed via section 3.7 of the GNSO Working Group Guidelines [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…>. Following discussions with the members utilizing the appeal process and the GNSO chair and the Council liaison to the WG, the Council liaison to the WG solicited input from the WG members on the set of options under consideration. The WG has since held several meetings to try and reach final consensus for its Final Report, including opening up the formal consensus call on 10 May 2018. The WG Chair has designated his assessment of consensus levels for recommendations 1-4, as well as for the 6 options under consideration for recommendation 5. A second section 3.7 appeal was filed in June 2018, to assert that the Chair, Council liaison, and policy staff are not performing their role, that short deadlines are being imposed, and that proper procedure is not being followed for the consensus call. With the connection to a previous PDP on IGO protections, where work continues to reconcile inconsistencies with GAC Advice, and the GNSO Council’s emphasis on improving the timely resolution of PDPs, the Council requests that the Final Report be delivered in time for consideration for the July 2018 GNSO Council meeting. Here, the Council will vote on whether or not to request delivery of the Final Report by the Council’s July meeting. 5.1 – Presentation of motion (Heather Forrest) 5.2 – Council discussion 5.3 – Council vote (voting threshold: simple majority) Item 6: COUNCIL VOTE – Approval of Changes Made to the Customer Standing Committee (CSC) Charter (15 minutes) The ccNSO and RySG appointed members to form the Charter Review Team from their respective SO and SG to conduct a review of the Customer Standing Committee (CSC) Charter in accordance with the Terms of Reference. The CSC Charter review team (RT) sought comment and input on its findings and proposed amendments to the CSC Charter, as included in the RT's Initial Report. On 11 May 2018, Council member volunteers were sought to develop a draft comment for Council consideration for public comment [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> on the Initial Report on Review of the CSC Charter. The Council discussed the Initial Report during their meeting on 24 May 2018 and submit their comments during the public comment process. Taking into account comments received, the Review Team prepared a Final Report and Amended Charter for consideration and adoption by the ccNSO and GNSO Councils. Here, the Council will vote to approve the changes made to the CSC Charter as a result of the Charter Review Process. 6.1 – Presentation of motion (Donna Austin) 6.2 – Council discussion 6.3 – Council vote (voting threshold: simple majority) Item 7: COUNCIL UPDATE – Protections for Certain Red Cross Names in All gTLDs Policy Amendment Process (10 minutes) Following discussions around possible ways of reconciling inconsistent GAC advice and GNSO policy recommendations relating to National Society names of the Red Cross Movement and the two names of the international components of the Movement (http://sched.co/9xr2 [sched.co]<https://urldefense.proofpoint.com/v2/url?u=http-3A__sched.co_9xr2-29&d=DwMG…>), the ICANN Board passed a resolution requesting that the GNSO Council initiate the process outlined in Section 16 of the GNSO’s Policy Development Process (PDP) Manual, which sets forth the requisite steps for amending policy recommendations that have been approved by the GNSO Council but not yet approved by the ICANN Board (https://www.icann.org/resources/board-material/prelim-report-2017-03-16-en#… [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>). The Board’s request related to the 190 Red Cross National Society names and the two international movement names and a limited defined set of their variants. On 03 May 2017, the Council resolved [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> to initiate the Section 16 process as requested by the Board, which resulted in the limited reconvening of the original PDP on Protection of IGO and INGO Identifiers in All gTLDs. The Reconvened WG began its deliberations on 14 June 2017 and is nearing completion of its preliminary work, expecting to publish its Initial Report in the near future. Here, the Council will receive an update on the status of the Reconvened WG. 7.1 – Update (Thomas Rickert - WG Chair) 7.2 – Council discussion 7.3 – Next Steps Item 8: COUNCIL VOTE – Initiation of Expedited Policy Development Process on the ICANN Board Temporary Specification (30 minutes) On 11 May 2018, ICANN released the Temporary Specification [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> on gTLD Registration Data, which served as the main agenda topic for the subsequent Board Workshop in Vancouver. This proposed Temporary Specification provides an interim solution until the community completes a policy development process on the temporary specification which is expected to complete within a one year period. On 14 May 2018, ICANN released a revised Temporary Specification [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> and scheduled a webinar on 15 May 2018 to discuss the topic. The Board passed a resolution [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>, noting their intent to adopt the Temporary Specification on or around 17 May 2018. On 17 May 2017, the ICANN Board approved [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> the proposed Temporary Specification for gTLD Registration Data [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>, which establishes temporary requirements for how ICANN and its Contracted Parties will comply with both ICANN contractual requirements and the European Union’s General Data Protection Regulation (GDPR). On 21 May 2018, the Council and SG/C chairs met to discuss possible next steps for the ICANN Board adoption of the Temporary Specification. On its 24 May 2018 meeting, the Council discussed possible next steps following ICANN Board adoption of the Temporary Specification. On 5 June 2018, the Council met with the ICANN Board to discuss a set of questions [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_corr…>the Council and ICANN Board developed, as well as overall next steps. Subsequently, Council leadership and staff developed a Mindmap [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…> to help understand the elements around a potential Expedited Policy Development Process (EPDP), such as timing, team composition, and planning for ICANN62. On 12 June 2018, the Council held an Extraordinary Council Meeting to discuss next steps on addressing the Temporary Specification. There, the Council agreed in principle that an EPDP was the right way to address the issue and that next steps should be taken, specifically drafting of the charter and initiation. In the period leading up to and at ICANN62, the Council has worked together to draft the charter for the EPDP. Here, the Council will vote to initiate an EPDP on the Temporary Specification, as well as to adopt the EPDP’s charter. 8.1 – Presentation of motion (Council Leadership) 8.2 – Council discussion 8.3 – Council vote (voting threshold: Supermajority) Item 9: ANY OTHER BUSINESS (15 minutes) 9.1 – GNSO Chair election timeline 9.2 – Call for Volunteers - Revised ICANN Procedure Handling WHOIS Conflicts with Privacy Law 9.3 – Open Microphone ________________________________ Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article 11, Section 11.3(i)) See https://www.icann.org/resources/pages/governance/bylaws-en/#article11 [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>. Appendix 2: GNSO Council Absentee Voting Procedures (GNSO Operating Procedures, Section 4.4) See https://gnso.icann.org/sites/default/files/file/field-file-attach/op-proced… [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…> References for Coordinated Universal Time of 18:00 UTC Local time between March and October Summer in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PDT) UTC-7 (-1 day) 11:00 San José, Costa Rica (CST) UTC-6 (-1 day) 12:00 New York/Washington DC, USA (EDT) UTC-4 14:00 Buenos Aires, Argentina (ART) UTC-3 15:00 Rio de Janeiro, Brazil (BRST) UTC-3 15:00 London, United Kingdom (GMT) UTC+1 19:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 19:00 Paris, France (CEST) UTC+2 20:00 Islamabad, Pakistan (PKT) UTC+5 23:00 Singapore (SGT) UTC+8 (+1 day) 02:00 Tokyo, Japan (JST) UTC+9 (+1 day) 03:00 Sydney/Hobart, Australia (AEDT) UTC+10 (+1 day) 04:00 ---------------------------------------------------------------------------- DST starts/ends on Sunday 28 of October 2018, 2:00 or 3:00 local time (with exceptions) for EU countries and on Sunday 4 of November 2018 for the US. ---------------------------------------------------------------------- For other places see http://www.timeanddate.com [timeanddate.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.timeanddate.com_&d=…> and https://tinyurl.com/ybuhhqmo [tinyurl.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__tinyurl.com_ybuhhqmo&d…>

1 0

Public comment forum now open for the Initial Report from the Reconvened PDP Working Group on Red Cross Names
by Mary Wong June 21, 2018

June 21, 2018

Dear Councilors, Please see below for a link to the public comment forum that was just opened on the Initial Report from the reconvened PDP Working Group on the names of the Red Cross National Societies, the International Committee of the Red Cross and the International Federation of Red Cross and Red Crescent Societies. The comment period will remain open for 40 days, closing on 31 July 2018. Staff understands that Thomas Rickert, the Working Group chair, will be providing the Council with a brief status update during your public meeting at ICANN62 next week. Thanks and cheers Mary & Berry From: Mary Wong <mary.wong(a)icann.org> Date: Thursday, June 21, 2018 at 16:58 To: "gnso-igo-ingo(a)icann.org" <gnso-igo-ingo(a)icann.org> Subject: Public comment forum now open for our Initial Report Dear all, As Berry is traveling, I am pleased to send this notification on behalf of him and the staff supporting this effort. The Initial Report has now been published for public comment, with a duration of 40 days such that the comment period will close on 31 July 2018: https://www.icann.org/public-comments/red-cross-protection-initial-2018-06-…. As noted previously by Berry, in addition to the Initial Report itself (https://gnso.icann.org/en/issues/igo-ingo/red-cross-protection-policy-amend…) we have also posted the proposed list of finite and specific Red Cross names so that the community can see and comment on it as well: https://gnso.icann.org/en/issues/igo-ingo/red-cross-identifiers-proposed-re…. Thanks and cheers Mary & Berry From: Gnso-igo-ingo <gnso-igo-ingo-bounces(a)icann.org> on behalf of "mail(a)berrycobb.com" <mail(a)berrycobb.com> Date: Wednesday, June 20, 2018 at 16:07 To: "gnso-igo-ingo(a)icann.org" <gnso-igo-ingo(a)icann.org> Subject: [Gnso-igo-ingo] Initial Report for Public Comment Hi All, Please find attached a redline and clean version of the WG’s Initial Report to be published for public comment starting tomorrow for 40 days. For those that submitted proposed changes, thank you. There were no objections to the consensus levels assigned to the proposed recommendations nor were there objections to the list of identifiers listed as an outstanding issue. Thus, those identifiers are included in the list of names to be protected. Once the PCF is posted on icann.org, I will send a link to the list. Note: as you will see in the redline, there are still a few outstanding items for the WG to consider when it reconvenes to consider the comments submitted and readies the report for submission to the GNSO Council. I left them intact as markers for when the time comes. Thank you all. B Berry A. Cobb 720.839.5735 mail(a)berrycobb.com<mailto:mail@berrycobb.com> @berrycobb

1 0

Fwd: IPC Outreach Reception - ICANN 62
by Heather Forrest June 20, 2018

June 20, 2018

Dear Council colleagues, On behalf of Brian Winterfeldt, President of the IPC, I'm pleased to convey the invitation below. Best wishes, safe travels, see you in Panama, Heather

1 0

For your review: GNSO June 2018 Project List
by Terri Agnew June 20, 2018

June 20, 2018

Dear Councilors, Attached please find the updated Project List in both red-line and clean version for your review before the Council meeting. If there are no comments, the list will be posted on the website on page: <https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_counc il_project&d=DgMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f 4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=bcZnPuqiDY4_TMPBs 3UPEUuqx-bS0HF55Trpa8n_FnY&s=YH_cwffIV-OMrgs6pTu37csGmNJ3QHxniBkjyRh9J2s&e=> http://gnso.icann.org/en/council/project and be directly viewed at : <https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_meetings _projects-2Dlist.pdf&d=DgMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM& r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=bcZnPuq iDY4_TMPBs3UPEUuqx-bS0HF55Trpa8n_FnY&s=Md4eGTKVkiG-gC-Gmw4artPvS0zM3M5oceJO4 BALy7g&e=> http://gnso.icann.org/meetings/projects-list.pdf Thanks so much, Kind regards, Terri

1 0

Fwd: Fine Report CSC Charter Review Team
by Heather Forrest June 20, 2018

June 20, 2018

Dear Council colleagues, Please find below an email from Bart Boswinkel communicating the Final Report of the Customer Standing Committee (CSC) Charter Review and calling on the Council to consider in particular a recommendation for further analysis by the GNSO and ccNSO Councils. We have an opportunity to discuss CSC-related matters with the ccNSO Council when we meet with them on Wednesday at 0800. Best wishes, Heather ---------- Forwarded message ---------- From: Bart Boswinkel <bart.boswinkel(a)icann.org> Date: Tue, Jun 19, 2018 at 8:04 PM Subject: Fine Report CSC Charter Review Team To: "Heather Forrest (Heather.Forrest(a)acu.edu.au)" < Heather.Forrest(a)acu.edu.au> Cc: "CSC-review(a)icann.org" <CSC-review(a)icann.org>, Marika Konings < marika.konings(a)icann.org> Dear Heather Please find attached a copy of the Final Report of the Customer Standing Committee (CSC) Charter Review prepared by the CSC Charter Review Team, along with a standalone version of the Proposed Amended CSC Charter. In accordance with the CSC Charter and the ICANN bylaws, any recommended changes to the CSC Charter as a result of the CSC Charter review are to be ratified by both the GNSO and ccNSO Councils. Therefore the CSC Review Team seeks consideration of the Proposed Amended Charter by the GNSO Council with a view to having the recommended changes ratified. We also call your attention to a recommendation in the Final Report requesting that the ccNSO and GNSO Councils conduct an analysis of the requirements of the IANA Naming Function Review and the CSC Effectiveness Review with a view to creating synergies and avoiding overlap. We understand that some progress has been made in this regard and we thank the Council for their prompt attention to this matter. Regards On behalf of the CSC Charter Review Team Bart Boswinkel

1 0

ePDP DT / Leadership Issues
by McGrady, Paul D. June 19, 2018

June 19, 2018

I think we have at least two questions to address: 1. What is the ideal configuration of the leadership team for an EPDP? * 1 chair * 2 or more co-chairs * 1 chair and 1 or more vice-chairs * Some other model 2. Depending on the answer to the above, who should be nominated for leadership and what is that process? Historically, WG's select their own leadership and that is ratified by the Council. Is that the same plan for the ePDP? Let's discuss. PS: From the chat on today's call I saw (and want to capture for your discussion): Ayden Ferdeline: Chair - Thomas Rickert Best, Paul ________________________________ 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.

1 0

ICANN Org Proposed Unified Access Model
by Ayden Férdeline June 19, 2018

June 19, 2018

Could this, in any way, have implications for the EPDP? https://www.icann.org/news/blog/data-protection-privacy-update-seeking-comm… There is no deadline for the submission of feedback, and it does not appear on the public comment page, so I presume it is an informal request for community input. Best wishes, Ayden

3 2

Action Items: GNSO Council meeting 12 June 2018
by Nathalie Peregrine June 19, 2018

June 19, 2018

Dear Councilors, Please find the action items, as stated during the meeting, below arising from the extraordinary GNSO Council meeting held on Tuesday 12 June 2018. Please take note of the action items coming out of the Council sessions and the proposed timing for delivering on these actions. Please ensure your wiki logins are up to date as all Action Items have been assigned to councilors and/or staff and posted on the Action Item wiki page here[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…>. If you are logged into the wiki when you go to that page, your name will be highlighted alongside the action item assigned to you. Please refer to this page for the recent status updates on the Action items. ACTION ITEMS FROM THE EXTRAORDINARY GNSO COUNCIL MEETING 12 JUNE 2018 Item 2. COUNCIL DISCUSSION – Next steps following adoption of ICANN Board Temporary Specification Outcomes: * Agreement in principle that the Expedited Policy Development Process (EPDP) is the proper mechanism to address the Temporary Specification. Action Items: * Council Leadership to communicate above outcome to the ICANN Board * Council to begin some initial EPDP processes (e.g., initiation, charter drafting). * Councilors to share feedback on Temporary Specification mapping document on Council mailing list. * Council Leadership to follow up with the ICANN Board regarding its question 5 in this document: https://gnso.icann.org/sites/default/files/file/field-file-attach/olive-to-… * Council Leadership to investigate whether the IPC and/or BC might be open to allowing the Council to drive one of the group’s Cross-Community sessions. * ICANN Staff to update ICANN62 schedule placeholders to reflect EPDP charter drafting/initiation. Also, change the closed Tuesday 09:00-10:15 session to an open one. * ICANN Staff to circulate draft of EPDP initiation request and draft charter * ICANN Staff to circulate Doodle poll to allow for Councilors to meet and discuss the EPDP initiation/charter drafting prior to ICANN62; subsequently, schedule meeting. * Council Leadership to follow up with the ICANN Board/ICANN Org to have them designate what they feel is within the picket fence for the Temporary Specification. Thank you, 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

Re: [council] [gnso-secs] Draft minutes of the GNSO extraordinary Council meeting Tuesday 12 June 2018
by Nathalie Peregrine June 19, 2018

June 19, 2018

Dear Councilors, Please find the updated version attached, with added Action items. Kind regards, Nathalie From: Gnso-secs <gnso-secs-bounces(a)icann.org> on behalf of Nathalie Peregrine <nathalie.peregrine(a)icann.org> Date: Monday, June 18, 2018 at 10:12 AM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [gnso-secs] Draft minutes of the GNSO extraordinary Council meeting Tuesday 12 June 2018 Dear Councilors, Attached, please find the draft minutes of the GNSO extraordinary Council meeting on Tuesday 12 June 2018 for your review. If there are no comments, these minutes will be published on the website as approved, according to the GNSO Rules of Procedure [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> section 3.5 "If no objections are received within 10 days, the minutes will be deemed to have been approved for posting" on 28 June 2018. Thank you very much. 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

Draft minutes of the GNSO extraordinary Council meeting Tuesday 12 June 2018
by Nathalie Peregrine June 18, 2018

June 18, 2018

Dear Councilors, Attached, please find the draft minutes of the GNSO extraordinary Council meeting on Tuesday 12 June 2018 for your review. If there are no comments, these minutes will be published on the website as approved, according to the GNSO Rules of Procedure [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> section 3.5 "If no objections are received within 10 days, the minutes will be deemed to have been approved for posting" on 28 June 2018. Thank you very much. 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

Deadline today: Document and Motion deadline Sunday, 17 June 2018 at 23:59 UTC for the GNSO Council Meeting 27 June 2018 at 18:00 UTC
by Nathalie Peregrine June 17, 2018

June 17, 2018

Dear all, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Sunday, 17 June 2018 at 23:59 UTC) of the GNSO Council Meeting on Wednesday, 27 June 2018 at 18:00 UTC. Motions should be sent to the Council mailing list by a councilor and will then be posted on the Wiki at: https://community.icann.org/x/yBUFBQ [community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> Thank you very much. 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

Placeholder motion on commencement of EPDP
by Heather Forrest June 17, 2018

June 17, 2018

Dear colleagues, In view of the workload ahead of us this week and in Panama, Council leadership believes it prudent to put a plaeholder motion on our June agenda in relation to commencing an EPDP. Of course, whether the motion is timely and considered in Panama depends entirely on the discussions to come, but having it on the agenda enables us to consider it if that's timely, whereas not having it on the agenda prevents doing so and misses an opportunity. With that explanation, please find attached a placeholder motion. Best wishes, Heather

2 1

Motion submission for June agenda
by Heather Forrest June 17, 2018

June 17, 2018

Dear Council colleagues, Please find attached a motion submitted for our June Council agenda. Best wishes as we rapidly approach go-time to Panama, Heather

2 1

Motion to approve the Customer Standing Committee Amended Charter
by Austin, Donna June 17, 2018

June 17, 2018

Dear Councilors Please find attached a motion for consideration by the Council on 27 June 2018, to approve the Customer Standing Committee Amended Charter. I expect that the Final Report of the Customer Standing Committee Charter Review, which includes the Amended Charter, will be provided to the Council on Monday or Tuesday of next week. Thanks Donna Donna Austin Neustar, Inc. / Senior Policy Manager, Registry Solutions Mobile: +1 310 890 9655 donna.austin(a)team.neustar<mailto:donna.austin@team.neustar> / Website: home.neustar<http://www.home.neustar/> Follow Neustar: LinkedIn<http://www.linkedin.com/company/5349> / Twitter<http://www.twitter.com/neustar> Reduce your environmental footprint. Print only if necessary. ________________________________ The information contained in this email message is intended only for the use of the recipient(s) named above and may contain confidential and/or privileged information. If you are not the intended recipient you have received this email message in error and any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately and delete the original message.

2 1

Reminder: Document and Motion deadline Sunday, 17 June 2018 at 23:59 UTC for the GNSO Council Meeting 27 June 2018 at 18:00 UTC
by Terri Agnew June 16, 2018

June 16, 2018

Dear all, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Sunday, 17 June 2018 at 23:59 UTC) of the GNSO Council Meeting on Wednesday, 27 June 2018 at 18:00 UTC. Motions should be sent to the Council mailing list by a councilor and will then be posted on the Wiki at: <https://community.icann.org/x/yBUFBQ> https://community.icann.org/x/yBUFBQ Thank you very much. With kind regards, Terri --- Terri Agnew Operations Support - GNSO Lead Administrator Internet Corporation for Assigned Names and Numbers (ICANN) Email: <mailto:terri.agnew@icann.org> terri.agnew(a)icann.org Skype ID: terri.agnew.icann Find out more about the GNSO by taking our interactive courses and visiting the <https://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy…> GNSO Newcomer pages Follow @GNSO on Twitter: <https://twitter.com/ICANN_GNSO> https://twitter.com/ICANN_GNSO Follow the GNSO on Facebook: <https://www.facebook.com/icanngnso/> https://www.facebook.com/icanngnso/ <http://gnso.icann.org/en/> http://gnso.icann.org/en/

2 2

Re: [council] For your review - EPDP Initiation Request and EPDP Team Charter Templates
by Michele Neylon - Blacknight June 15, 2018

June 15, 2018

Marika et al I’ve made a few notes on the document (attached) Regards 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 Marika Konings <marika.konings(a)icann.org> Date: Wednesday 13 June 2018 at 00:01 To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [council] For your review - EPDP Initiation Request and EPDP Team Charter Templates Dear All, As discussed during today’s extraordinary Council meeting, staff has gone ahead and prepared a template for the EPDP Initiation Request as well as the EPDP Team Charter (see attached). As there is some duplication between the Initiation Request and the Charter, staff would like to suggest that you focus your attention on the EPDP Team charter for now. Once elements such as scope and team composition have been agreed on, these can then be lifted from the charter into the EPDP Initiation Request. Also note that staff has taken the liberty to prepopulate some of the sections of the charter to facilitate your deliberations. These entries are either based on existing charter language / practices / procedures and/or aspects that have come up in the context of the discussions to date, including the PDP 3.0 conversations. In addition, staff has flagged some items highlighted in yellow that will require further feedback before draft language can be added. Of course, it is up to you to edit / delete / add as you deem appropriate. If there is anything further that staff can do to facilitate your deliberations and drafting, please let me know. Best regards, Marika 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<http://learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-…>.

3 2

ICANN vs EPAG - round two
by Michele Neylon - Blacknight June 14, 2018

June 14, 2018

https://www.internetnews.me/2018/06/14/icann-vs-epag-icann-seeks-appeal-plu… -- 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

1 0

For your review - EPDP Initiation Request and EPDP Team Charter Templates
by Marika Konings June 14, 2018

June 14, 2018

Dear All, As discussed during today’s extraordinary Council meeting, staff has gone ahead and prepared a template for the EPDP Initiation Request as well as the EPDP Team Charter (see attached). As there is some duplication between the Initiation Request and the Charter, staff would like to suggest that you focus your attention on the EPDP Team charter for now. Once elements such as scope and team composition have been agreed on, these can then be lifted from the charter into the EPDP Initiation Request. Also note that staff has taken the liberty to prepopulate some of the sections of the charter to facilitate your deliberations. These entries are either based on existing charter language / practices / procedures and/or aspects that have come up in the context of the discussions to date, including the PDP 3.0 conversations. In addition, staff has flagged some items highlighted in yellow that will require further feedback before draft language can be added. Of course, it is up to you to edit / delete / add as you deem appropriate. If there is anything further that staff can do to facilitate your deliberations and drafting, please let me know. Best regards, Marika 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<http://learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-…>.

2 1

Suggestion for membership criteria of proposed Expedited Policy Development Process
by Ayden Férdeline June 13, 2018

June 13, 2018

Dear all, I have just finished reviewing the proposed agenda for our meeting next week along with the mindmap that Council leadership and staff have developed (thanks for doing this!). I would like to put forward a suggestion for the Expedited Policy Development Process (EPDP) team criteria. While the scope of the EPDP remains unclear at present, what I took away from the call between the Board and the Council on Tuesday was that compliance with the law is crucial. As such I think it is imperative that *all* members be able to demonstrate that they have a basic understanding of the principles and legal terms of data protection. I would like to request that any community member who is appointed to the EPDP, or staff member supporting the EPDP, be able to demonstrate they have completed at least 3 hours of data protection training. I do not think this would be a huge burden, but I think it would make work easier, as there should be a common understanding of essential terms. There are short half-day 'Data Protection 101' classes run by institutions like the policy neutral International Association of Privacy Professionals, whose courses only use definitions of terms that have been defined in law for over 20 years. For those who don't hold this certification, I would like to request that ICANN reimburse the members of the EPDP for their modest and reasonable costs in obtaining it. I would like to hear your thoughts here, however I would also like to ask that this suggestion please be given serious consideration. Thank you. Best wishes, Ayden Férdeline

11 24

Doodle poll: GNSO Council Preparation call Initiation Request and Charter Drafting
by Nathalie Peregrine June 12, 2018

June 12, 2018

Dear all, As a follow-up action item from the extraordinary GNSO Council meeting held earlier, please be so kind as to complete the below Doodle poll in order to schedule a GNSO Council preparation call regarding Initiation Request and Charter drafting. The doodle poll slots have been chosen in order to have timeslots taking councilors’ time-zones into account, so as with GNSO Council meeting times, a certain flexibility is required ☺ Doodle poll: https://doodle.com/poll/p8vdnd95fgpb3vkt 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

MP3, Adobe Connect recording and chat transcript/ Extraordinary GNSO Council meeting on Tuesday, 12 June 2018 at 12:00 UTC.
by Terri Agnew June 12, 2018

June 12, 2018

Dear GNSO Council, Please find below the MP3, Adobe Connect recording and chat of the Extraordinary GNSO Council meeting held on Tuesday, 12 June 2018 at 12:00 UTC. MP3: <https://audio.icann.org/gnso/gnso-council-12jun18-en.mp3> https://audio.icann.org/gnso/gnso-council-12jun18-en.mp3 Adobe Connect Recording URL: <https://participate.icann.org/p2gm9co4zpi/> https://participate.icann.org/p2gm9co4zpi/ Adobe Connect chat at: <https://gnso.icann.org/sites/default/files/file/field-file-attach/transcrip…> https://gnso.icann.org/sites/default/files/file/field-file-attach/transcrip… All on page: <https://gnso.icann.org/en/group-activities/calendar> 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: <mailto:terri.agnew@icann.org> terri.agnew(a)icann.org Skype ID: terri.agnew.icann Find out more about the GNSO by taking our interactive courses and visiting the <https://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy…> GNSO Newcomer pages Follow @GNSO on Twitter: <https://twitter.com/ICANN_GNSO> https://twitter.com/ICANN_GNSO Follow the GNSO on Facebook: <https://www.facebook.com/icanngnso/> https://www.facebook.com/icanngnso/ <http://gnso.icann.org/en/> http://gnso.icann.org/en/

1 0

GDPR Training for EPDP
by Martin Pablo Silva Valent June 12, 2018

June 12, 2018

Dear all, Here goes something I would like to bring up. I was listening to todays morning call on the essential and difficult need to spread quickly more training among our icann colleagues on how GDPR works (not awareness, but actual skills to debate policy). In any case, I think that just a a two hours webinar (or a one hour session in Panama), regardless of the amazing people we have on board, we could use an already strong program that is deep enough to give meaningful knowledge, but is not overwhelming to learn in the next weeks. I found this “Get GDPR Ready” https://iapp.org/train/gdprready <https://iapp.org/train/gdprready> Course of International Association of Privacy Professionals (IAPP <https://iapp.org/>). On the other hand, the course is qualified for “Certified Information Privacy Professional /Europe”, which gives both legitimacy and some sort of credit afterwards. The course is not cheap, at least not for ICANN community members to individually purchase, so I think it would be ideal if ICANN strikes some sort of deal to have this course open, not in ICANN times, but in EPDP times!!! I know Sam Pfeifle, IAPP Content Director, is the person who did the presentation of this matter at INTA 2018, and I heard good thing about it. If INTA could strike a deal, ICANN should too. I think this is the right track to bring a game changer element to the EPDP debate, a fast track training by trusted party already set-up to implement tomorrow. Disclosure, I have attended as guest some IAPP events at Argentina, usually at some big trademark law firm, but I have no direct nor indirect relationship, nor-whatsoever, with them. Cheers, Martín

1 0

GNSO Council Abstention Notification Form [#277]
by ICANN June 12, 2018

June 12, 2018

1 0

Fwd: Mapping the Temp Spec to Existing ICANN Agreements and Policies
by Heather Forrest June 12, 2018

June 12, 2018

Dear Council colleagues, An immediate follow-up to my previous email - below and attached is the response outstanding to #9 (mapping across other ICANN policies), which I understand may require further refinements. Sincere thanks to Cherine, Chris, David and their colleagues for providing this information as quickly as possible. Best wishes, Heather ---------- Forwarded message ---------- From: David Olive <david.olive(a)icann.org> Date: Tue, Jun 12, 2018 at 2:01 PM Subject: Mapping the Temp Spec to Existing ICANN Agreements and Policies To: "haforrestesq(a)gmail.com" <haforrestesq(a)gmail.com>, " gnso-chairs(a)icann.org" <gnso-chairs(a)icann.org> Cc: Cherine Chalaby <cherine.chalaby(a)board.icann.org>, Chris Disspain < chris(a)disspain.uk>, Goran Marby <goran.marby(a)icann.org>, John Jeffrey < john.jeffrey(a)icann.org>, Marika Konings <marika.konings(a)icann.org>, Erika Randall <erika.randall(a)icann.org> Dear Heather ; Attached is the document mapping the Temporary Specification to existing agreements and policies. I have marked this document as “working draft” because we may need some refinements as we move forward. Best regards, David

2 1

Fwd: Letter from the GNSO Chairs/Co-Chairs on the GNSO Council – ICANN Board meeting to discuss next steps following the Board’s adoption of the temporary specification
by Heather Forrest June 12, 2018

June 12, 2018

Dear Council colleagues, Picking up on Pam's query to the list last week, we followed up by letter on 8 June with the Board in relation to the outstanding questions from our call. Please find responses sent through by David Olive below. I understand that #9 is in progress and the intention is to provide it to Council before our Extraordinary meeting (taking place in a matter of hours, so we won't have time to review it in depth, but hopefully will have it to hand to discuss). "See" you all later today at the Extraordinary Meeting. Best wishes, Heather ---------- Forwarded message ---------- From: David Olive <david.olive(a)icann.org> Date: Tue, Jun 12, 2018 at 6:35 AM Subject: Letter from the GNSO Chairs/Co-Chairs on the GNSO Council – ICANN Board meeting to discuss next steps following the Board’s adoption of the temporary specification To: Heather Forrest <haforrestesq(a)gmail.com>, Gnso-chairs < gnso-chairs-bounces(a)icann.org> Cc: Cherine Chalaby <cherine.chalaby(a)board.icann.org>, Chris Disspain < chris.disspain(a)board.icann.org>, Goran Marby <goran.marby(a)icann.org>, John Jeffrey <john.jeffrey(a)icann.org>, Marika Konings <marika.konings(a)icann.org>, Erika Randall <erika.randall(a)icann.org>, Wendy Profit < wendy.profit(a)icann.org> Dear Heather, On behalf of Cherine who is currently traveling, I would like to thank you for your letter dated 8 June 2018. In the interest of time, Chris Disspain has asked I respond to the outstanding questions as identified in your letter so that it is received in time for the upcoming GNSO Council meeting which has been scheduled for 12 June 2018. Hereby the responses to the outstanding questions identified: SCOPE: *(5) The Temporary Specification reasoning for including WHOIS as a security and stability issue is based on the new ICANN Bylaws; at time of contract signing, that wasn’t the case. Doesn’t that open a possible avenue to challenge it altogether? Wouldn’t phasing the EPDP allowing a quick Consensus Policy made of uncontroversial parts of the Temp Spec increase the assurances that this wouldn’t hamper ICANN Org’s compliance ability? * The Board has not had time yet to discuss this question but once it does, it will provide its feedback to the GNSO Council. *(8) The Temporary Specification covers a number of additional policies that go beyond the requirements of the RA and RAA as they relate to Registration Data Directory Services. How does the Board believe the GNSO Council should handle these areas of overlap? * The GNSO Council may want to consider taking the same approach that it currently uses in policy development processes for considering existing consensus policies that may be impacted by a proposed new consensus policy. However, the Board and ICANN Org stand ready to work with the GNSO Council on these issues as needed and if/when they arise. *(9) Does ICANN have/will ICANN develop a list of policies and contractual clauses that are impacted by the temporary specification (beyond what is currently identified in the Annex)? This would help with scoping the work. * ICANN Org is preparing a document that will show which areas of the existing agreements and consensus policies are changed as a result of the GDPR. It is expected that this document will be shared with the GNSO Council prior to its meeting. *(11) How does the Board expect the EPDP to follow and/or to incorporate ICANN ́s ongoing legal strategy and the decisions of EU country courts? * Ongoing discussions and pending court cases could have an impact on issues such as these, but the PDP on the temporary specification is not expected to deliberate on these issues, unless these are reflected in modifications that are made by the ICANN Board to the temporary specification. *PARTICIPATION: * *(3) What is the Board's expectation with regard to the Council's ongoing communication with Board/involvement of Board during the scoping process? (In particular here the notes reflect our discussion on the need for instant two-way consultation between the Board and the GNSO Council. As follow-up questions, it would be helpful if the Board could consider its ability and willingness to appoint a liaison to the EPDP to facilitate this communication on ongoing basis, and further reflect on the role of the Board once the PDP is established and working.)* As suggested during the meeting, if welcomed by the GNSO Council, the Board would be more than happy to appoint one or two liaisons to the PDP Team to facilitate communication on an ongoing basis. I hope that this input will facilitate the upcoming extraordinary Council meeting. As noted above, I also expect to send you the list of policies and contractual clauses that are impacted by the temporary specification as soon as it is available. Best regards, David A. Olive Senior Vice President Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN)

1 0

REMINDER FOR REVIEW: Proposed Next Steps re: GNSO Council's New Roles and Responsibilities Outlined in the Post-Transition Bylaws
by Julie Hedlund June 11, 2018

June 11, 2018

Dear All, Per the message below, this is a reminder to review the proposed next steps to be taken as outlined in the attached table to ensure preparedness as well as facilitate the ability for the GNSO Council to act in relation to the new roles and responsibilities outlined in the post-transition Bylaws. Staff is seeking feedback on whether the Council is supportive of these proposed next steps or whether modifications should be considered. Please note also that unless there are objections, staff could begin to work on the various templates that are identified in the attached table. Best regards, Julie Julie Hedlund, Policy Director From: council <council-bounces(a)gnso.icann.org> on behalf of Julie Hedlund <julie.hedlund(a)icann.org> Date: Wednesday, May 16, 2018 at 10:34 AM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [council] FOR REVIEW: Proposed Next Steps re: GNSO Council's New Roles and Responsibilities Outlined in the Post-Transition Bylaws Dear All, Following the adoption by the GNSO Council of the revised GNSO Operating Procedures, as well as the proposed modifications to the ICANN Bylaws adopted by the ICANN Board of Directors on 13 May, staff has outlined in the attached table the additional proposed steps to be taken to ensure preparedness as well as facilitate the ability for the GNSO Council to act in relation to the new roles and responsibilities outlined in the post-transition Bylaws. The GNSO Council is requested to review the proposed next steps and to provide feedback whether it is supportive of these proposed next steps or whether modifications should be considered. Best regards, Julie Julie Hedlund, Policy Director

1 0

GNSO Council Abstention Notification Form [#276]
by ICANN June 11, 2018

June 11, 2018

1 0

Notes from GNSO Council - ICANN Board meeting to discuss next steps following the Board's adoption of the temporary specification for gTLD Registration Data
by Marika Konings June 9, 2018

June 9, 2018

Dear All, Please find below the notes from today’s GNSO Council – ICANN Board meeting to discuss next steps following the Board’s adoption of the temporary specification for gTLD Registration Data. Note that the recording and transcript of the meeting will be circulated shortly. These high-level notes are designed to help the Council navigate through the content of the call and are not meant as a substitute for the transcript and/or recording. Best regards, Marika ================== Board-GNSO Council Call Next steps following Board adoption of Temporary Specification 5 June 2018 Questions have been divided into three categories: * Scope * Timing * Participation This is unchartered territory so a degree of flexibility of all involved will be required. Nevertheless, the Council is the manager of the PDP and as such, the Board expects the Council to take on this role and has no intention to interfere. Aim to answer as many questions as possible today and for those for which it is not possible to provide an answer, identify who and when an answer can be provided. Number of questions overlap, including in the questions between the Council and the Board, so not every question may need an answer as it may already get answered in response to another question. (4) What is the intent of the EPDP? Is it simply to confirm the Temporary Specification, or something more? What room is there in scoping to anticipate that the EPDP may conclude that the Temporary Specification cannot be confirmed “as is”, and make changes in order to achieve consensus policy? * Key is flexibility, need to work collegially and flexible. Not set things in stone - deal with issues and problems as they arise. In the Board's view there is room for various outcomes: confirming temporary specification; developing a different approach from what is established in the temporary specification; addressing additional issues that are not specifically identified in the temporary specification but for example, the annex. Is for the GNSO Council to manage, but Board stands ready to assist as needed. Any outcome will obviously need to comply with the law. * 12 month deadline needs to inform the scoping. Need to understand whether some of the additional items called out in the annex could be dealt with differently. (5) The Temporary Specification reasoning for including WHOIS as a security and stability issue is based on the new ICANN Bylaws; at time of contract signing, that wasn’t the case. Doesn’t that open a possible avenue to challenge it altogether? Wouldn’t phasing the EPDP allowing a quick Consensus Policy made of uncontroversial parts of the Temp Spec increase the assurances that this wouldn’t hamper ICANN Org’s compliance ability? * Response to this question needs to be further discussed. (6) What happens should the Board decide to either modify the Temporary Specification or completely replace the temporary specification by a new one at a later point in time? Does this change the scope of the ongoing EPDP (note: Council does not intend to run multiple EPDPs simultaneously), and if so, how is the EPDP expected to deal with such changes while it may be half way through its process? * Need to be flexible. If there is an amendment to the temporary spec, the circumstances need to be considered. An amendment in month 1 may be dealt with differently compared to one in month 11. Similarly the type of amendment - minor or substantial. It may also be possible that a new temporary spec is triggered on a certain issue that in theory would trigger a new PDP, although it might be possible to fold this into the existing PDP. Flexibility is key, need timely communication to ensure that the appropriate approach can be considered factoring in all circumstances. Board does not want to use the temporary specification approach unless absolutely necessary, for example when guidance is received from DPAs that certain elements would need to be changed. * Need some boundaries around how changes are dealt with as that may provide some needed clarity, especially to (E)PDP Team in case changes occur. The more that can be reached agreement on in the early stages, the better. Ensure common understanding of possible scenarios. * Consider parking lot approach to park issues that need to be dealt with, but which may not be urgent. (9) Does ICANN have/will ICANN develop a list of policies and contractual clauses that are impacted by the temporary specification (beyond what is currently identified in the Annex)? This would help with scoping the work. * ICANN Org is in the process of preparing a list which should be ready for sharing shortly. Once published, all input is welcome. ICANN Org to follow up with the Council on the expected timing within 24 hours. If possible, would be helpful to have this document prior to the upcoming Council meeting (12 June). (8) The Temporary Specification covers a number of additional policies that go beyond the requirements of the RA and RAA as they relate to Registration Data Directory Services. How does the Board believe the GNSO Council should handle these areas of overlap? * How does the GNSO currently deal with this? In unchartered territory here as we are working of a temporary specification, that is normally not the scenario in a normal PDP. For example, the temp spec refers to SLAs for RDS services - that would normally be an implementation matter, not a policy matter. Need to consider this question further. (10) What happens if the GNSO is not able to reach consensus at the end of the 1 year period? (see also Timing) * Board to explore other ways forward. Absent another way forward there are things that automatically occur at the end of the 12 month period - temp spec would no longer be in force. Review throughout the 12 month period how things are going, would allow Board to explore alternative ways forward which could potentially buy more time. The longer it takes, the greater the likelihood is that decisions are taken outside of ICANN. If community wants to be in control, needs to work in a timely manner. (11) How does the Board expect the EPDP to follow and/or to incorporate ICANN´s ongoing legal strategy and the decisions of EU country courts? (12) As evidenced by the recent legal action involving EPAG, there are parties who believe aspects of the Temporary Specification as written are not compliant with the GDPR. How does the Board think the GNSO Council should approach this matter when structuring and scoping the PDP? * Ongoing court cases may have an impact on issues, but the (E)PDP Team is not expected to deliberate on these issues unless these are reflected in the temporary specification. (4) Does the initial 90-day (and maximum one-year) period - and thus the maximum timeline for the GNSO’s policy work - commence on 17 May (date of Board resolution) or 25 May (effective date of the temporary specification)? We note that the operative language from the RAA/RA specifies that “In establishing any Temporary Policy, the Board shall state the period of time for which the Temporary Policy is adopted and shall immediately implement the Consensus Policy development process set forth in ICANN's Bylaws”, and the Board resolution is clear that the specification is effective beginning on 25 May. This could be interpreted to mean that the one-year clock starts from the effective date of the specification rather than Board action via resolution, which is a difference of 8 days. * 25 May 2018 is the starting point, so 1 year period would end on 24 May 2019. Up to the Council to decide when to start, but regardless, process has to complete by 24 May 2019. (5) What happens should the Board decide to either modify the temporary specification or completely replace the temporary specification by a new one at a later point in time? Does the amended temporary specification become a new temporary specification, effectively re-starting the clock on the Temp Spec and the ongoing EPDP? If changes to the Temporary Specification as it is today are certain to occur, and the amended temporary specification becomes a new temporary specification, why not delay starting the ePDP (assuming clock re-starts)? Note Council’s intention is not running multiple EPDP, but rather revising scope of the one ongoing EPDP. * Will depend on facts and circumstances. Board wants to continue to consult, could include appointing a liaison to the (E)PDP Team, small Board caucus to liaise with the Council, etc. Board wants to help without seeking to impose views. * Need the ability for instant consultation noting the possible moving parts and the need to be flexible. What does "consult" mean? Council weighing in on decision-making? More looking from the perspective of the Council being able to consult with the Board as needed. Board would talk to different parties and factor in input - if a particular way or structure is preferred, this can be discussed. (1) Participation of the GAC: How will the EPDP take into account GAC advice? Should the Board facilitate a session between the GNSO and the GAC on this issue, and when? * Would be good to discuss with GAC what is possible and feasible. Need to open up channels of discussion, recognising that the GNSO is in charge and leading. (6) How is the re-confirmation process expected to occur as the temporary policy is only valid for 90 day intervals? * Board will hold meetings at 90 day intervals and review prior to each meeting whether there is any new guidance that may require changes, followed by renewal of temporary specification for another 90 days. Changes may need to happen outside of that cycle. (7) Has the Board considered what actions it may take in the event that, at the end of the one-year period, the Temporary Specification is not confirmed as a Consensus Policy and no other Consensus Policy has been developed to replace it? * See previous response to similar question. ======== If more discussion is helpful, Board is willing and available. Need to determine which questions need to be followed up on and timeline for those. Develop task list as a result. Could include request for further calls. Council holding extraordinary meeting on 12 June to further discuss next steps. 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<http://learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-…>.

4 3

GNSO2 Review Working Group Progress & Implementation Status Report
by Julie Hedlund June 8, 2018

June 8, 2018

Dear GNSO Council members, On behalf of the GNSO Review Working Group (WG) please find the attached GNSO Review Progress & Implementation Status Report and slides for the update to the GNSO Council at ICANN62. The GNSO Review WG requests 15 minutes on the agenda of the GNSO Council meeting at ICANN62 on Wednesday, 27 June for this brief update by the GNSO Review WG Chair, Jen Wolfe. As you may know, the GNSO Review WG is executing and overseeing the implementation of the GNSO Review 2 (GNSO2) recommendations. This Report is a required periodic update to the GNSO Council and the Operational Effectiveness Committee (OEC) of the ICANN Board of Directors. The Working Group was initiated on 15 March 2017 and has been meeting bi-weekly. The original suggested timeline for implementation has been adjusted to reflect the fact that the Implementation Plan was not adopted by the ICANN Board until 03 February 2017, and to reflect the Working Group’s progress, but the overall goal for the implementation of all recommendations is unchanged. The Working Group expects to complete the implementation of all of the recommendations within the original timeline, not later than September 2018. This is the second Program & Implementation Status Report provided to the GNSO Council and the OEC. The first Report was submitted to the GNSO Council and the OEC in November 2017 at ICANN60. Please note that due to the deadline for documents to be considered at ICANN62, the OEC has requested that the Report be submitted to them by Friday, 08 June, and staff has submitted it accordingly. Kind regards, Julie Julie Hedlund, Policy Director

1 0

Final Proposed Agenda GNSO Council Meeting - 12 June 2018 at 12:00 UTC
by Nathalie Peregrine June 7, 2018

June 7, 2018

Dear all, Please below find the updated final proposed agenda for the extraordinary GNSO Council Meeting on 12 June 2018 at 12:00 UTC. Draft proposed agenda 12 June 2018 – Extraordinary GNSO Council Meeting Please note that all documents referenced in the agenda have been gathered on a Wiki page for convenience and easier access: https://community.icann.org/x/AygFBQ This agenda was established according to the GNSO Operating Procedures<https://gnso.icann.org/en/council/op-procedures-30jan18-en.pdf> v3.3, updated on 30 January 2018 For convenience: * An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda. * An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda. Coordinated Universal Time: 12:00 UTC: https://tinyurl.com/yb9ydjth [tinyurl.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__tinyurl.com_yb9ydjth&d…> 05:00 Los Angeles; 08:00 Washington; 13:00 London; 17:00 Islamabad; 21:00 Tokyo; 22:00 Hobart GNSO Council Meeting Audio Cast Listen in browser: http://stream.icann.org:8000/stream01 [stream.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> Listen in application such as iTunes: http://stream.icann.org:8000/stream01.m3u[stream.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call. ___________________________________ Item 1. Administrative Matters (5 mins) 1.1 - Roll Call 1.2 - Updates to Statements of Interest 1.3 - Review / Amend Agenda 1.4 - Opening Remarks Item 2. COUNCIL DISCUSSION – Next steps following adoption of ICANN Board Temporary Specification (115 minutes) On 11 May 2018, ICANN released the Temporary Specification<https://www.icann.org/resources/pages/approved-with-specs-2013-09-17-en#con…> on gTLD Registration Data, which served as the main agenda topic for the subsequent Board Workshop in Vancouver. This proposed Temporary Specification provides an interim solution until the community completes a policy development process on the temporary specification which is expected to complete within a one year period. On 14 May 2018, ICANN released a revised Temporary Specification<https://www.icann.org/en/system/files/files/proposed-gtld-registration-data…> and scheduled a webinar on 15 May 2018 to discuss the topic. The Board passed a resolution<https://www.icann.org/resources/board-material/resolutions-2018-05-13-en>, noting their intent to adopt the Temporary Specification on or around 17 May 2018. On 17 May 2017, the ICANN Board approved<https://www.icann.org/resources/board-material/resolutions-2018-05-17-en> the proposed Temporary Specification for gTLD Registration Data<https://www.icann.org/resources/pages/gtld-registration-data-specs-en>, which establishes temporary requirements for how ICANN and its Contracted Parties will comply with both ICANN contractual requirements and the European Union’s General Data Protection Regulation (GDPR). On 21 May 2018, the Council and SG/C chairs met to discuss possible next steps for the ICANN Board adoption of the Temporary Specification. On its 24 May 2018 meeting, the Council discussed possible next steps following ICANN Board adoption of the Temporary Specification. On 5 June 2018, the Council met with the ICANN Board to discuss a set of questions the Council developed, as well as overall next steps. Subsequently, Council leadership and staff developed a Mindmap<https://gnso.icann.org/sites/default/files/file/field-file-attach/temporary…> to help understand the elements around a potential Expedited Policy Development Process, such as timing, team composition, and planning for ICANN62 Here, the Council will continue its discussion from its 24 May 2018 meeting to discuss and plan for its next steps to begin work on the policy development process related to the Temporary Specification. 7.1 – Update (Council Leadership) 7.2 – Council discussion 7.3 – Next steps Item 3: ANY OTHER BUSINESS (0 minutes) ________________________________ Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article 11, Section 11.3(i)) See https://www.icann.org/resources/pages/governance/bylaws-en/#article11. Appendix 2: GNSO Council Absentee Voting Procedures (GNSO Operating Procedures, Section 4.4) See https://gnso.icann.org/sites/default/files/file/field-file-attach/op-proced… References for Coordinated Universal Time of 12:00 UTC Local time between March and October Summer in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PDT) UTC-7 05:00 San José, Costa Rica (CST) UTC-6 06:00 New York/Washington DC, USA (EDT) UTC-4 08:00 Buenos Aires, Argentina (ART) UTC-3 09:00 Rio de Janeiro, Brazil (BRST) UTC-3 09::00 London, United Kingdom (GMT) UTC+1 013:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 13:00 Paris, France (CEST) UTC+2 14:00 Islamabad, Pakistan (PKT) UTC+5 17:00 Singapore (SGT) UTC+8 20:00 Tokyo, Japan (JST) UTC+9 21:00 Sydney/Hobart, Australia (AEDT) UTC+10 22:00 ---------------------------------------------------------------------------- DST starts/ends on Sunday 28 of October 2018, 2:00 or 3:00 local time (with exceptions) for EU countries and on Sunday 4 of November 2018 for the US. ---------------------------------------------------------------------- For other places see http://www.timeanddate.com<http://www.timeanddate.com/> and : https://tinyurl.com/yb9ydjth

1 0

Fwd: [soac-chairs] Update for SO/AC Chairs: Second Security, Stability, and Resiliency (SSR2) Review -- Next Steps
by Heather Forrest June 7, 2018

June 7, 2018

Dear Council colleagues, Below, an update from ICANN Org on SSR2. If you have any questions, I'll be happy to channel them to Larisa. Best wishes, Heather ---------- Forwarded message ---------- From: Larisa B. Gurnick <larisa.gurnick(a)icann.org> Date: Wed, Jun 6, 2018 at 7:12 AM Subject: [soac-chairs] Update for SO/AC Chairs: Second Security, Stability, and Resiliency (SSR2) Review -- Next Steps To: "soac-chairs(a)icann.org" <soac-chairs(a)icann.org> Cc: SSR2 <ssr2-review(a)icann.org>, Theresa Swinehart < theresa.swinehart(a)icann.org>, David Olive <david.olive(a)icann.org> Dear SO/AC Chairs, We are pleased to inform you that the ICANN organization has engaged an external professional to facilitate the transition process and help the SSR2 review team in restarting and moving forward with its work. The SSR2 Review Team members have been notified of the appointment of the facilitator and efforts undertaken to support their work, confirming the official restart of the SSR2. After reviewing facilitator profiles and guidance from SO/AC chairs, ICANN organization has identified Phil Khoury, Cameron. Ralph. Khoury Consulting Services <http://crkhoury.com.au/>, to assist the review team in relaunching its activities. Phil Khoury’s 15 years of experience facilitating discussions, his solid understanding of the ICANN multistakeholder model, and consensus building expertise, distinguished him as an appropriate resource to address the scope and focus areas you have identified. Based on your 13 March note <https://www.icann.org/en/system/files/correspondence/soac-to-koubaa-13mar18…>, we understand that you would like to share the results of the survey you conducted after ICANN60 with the facilitator, to inform preparatory work leading up to the facilitated face-to-face meeting. Phil Khoury will reach out to you to receive the relevant material. He will also contact each of the SSR2 members to get their input in preparation for the next steps and proposed Review team’s upcoming face-to-face meeting. We are planning the meeting at ICANN’s office in Belgium or another identified location, in coordination with the review team, aiming for a time that can accommodate the majority of review team members. Thank you again for your dedication and collaboration in ensuring the success of this review. Best regards, Larisa *Larisa B. Gurnick* Vice President Multistakeholder Strategy and Strategic Initiatives ICANN larisa.gurnick(a)icann.org Skype: larisa.gurnick 1-310-383-8995 _______________________________________________ soac-chairs mailing list soac-chairs(a)icann.org https://mm.icann.org/mailman/listinfo/soac-chairs

4 3

ICANN62: GNSO Sessions How to Get Organized and Remote Participation Details
by Nathalie Peregrine June 6, 2018

June 6, 2018

Dear all, The one-stop wiki page for all your Remote Participation queries is now available. This wiki page covers remote participation details for all GNSO open and public meetings. In addition to this, ICANN meetings’ team has put together an updated ICANN meeting website which allows you to download all GNSO-related meetings to your inbox calendar in one go. 2 LINKS TO BOOKMARK NOW: ICANN62 Meeting Schedule<https://62.schedule.icann.org/> GNSO Remote Participation wiki page<https://community.icann.org/x/6QQFBQ> Step 1 – Create a profile and your personalized ICANN62 schedule Go to the Meeting Schedule webpage and create a profile and login. Every session on the schedule can be selected and added to your individual schedule by clicking the Add box to the bottom right of each meeting, this adds it to your individual schedule which you can then email to yourself or add to your calendar. See next step. Step 2 - There are two ways to import your schedule into Outlook: once you’ve added all your chosen meetings to “My Schedule” go to Export. 1. Importing creates a one-time snapshot of your schedule and copies it into Outlook. If you subsequently make changes to your Pathable calendar, they will not be reflected in Outlook. 2. Subscribing creates a live feed of your schedule in Outlook. Outlook checks for changes every few hours and updates your calendar appropriately. * For Outlook calendars: http://support.pathable.com/knowledgebase/articles/81449-moving-your-schedu…<https://urldefense.proofpoint.com/v2/url?u=http-3A__support.pathable.com_kn…> * For Google calendars: http://support.pathable.com/knowledgebase/articles/1313-moving-your-schedul…<https://urldefense.proofpoint.com/v2/url?u=http-3A__support.pathable.com_kn…> Step 3 All Adobe Connect rooms (which can be found on the session information on the Meeting Schedule<https://62.schedule.icann.org/> and on the GNSO Remote Participation wiki page<https://community.icann.org/x/6QQFBQ>) will provide audio streaming only Adobe Connect room microphones will not be enabled. If you cannot join an Adobe Connect room for a session, and will need to dial in with your phone, please refer to the GNSO Remote Participation wiki page<https://community.icann.org/x/6QQFBQ> for the audio pass codes and dial in numbers. Please also follow the previous steps if you wish to take part in the session over the phone. Step 4 Please download the mobile app by searching for “ICANN62” in your app stores. Nathalie Peregrine and Terri Agnew will be onsite in Panama to assist you directly. For all GNSO meeting related queries (RP or others), please email us at: gnso-secs(a)icann.org<applewebdata://FB60497E-61D8-4FE9-BF9C-EB238191E416/gnso-secs@icann.org> and we will be more than happy to assist! Kind regards, GNSO SO/AC Support team 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

New gTLD Subsequent Procedures PDP WG newsletter - June 2018
by Emily Barabas June 6, 2018

June 6, 2018

Dear all, On behalf of the leadership team of the New gTLD Subsequent Procedures PDP Working Group, I am writing to share the latest edition of the Working Group newsletter: http://go.icann.org/SubPro [go.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__go.icann.org_SubPro&d=D…>. Please feel free to share this newsletter with individuals and groups who may be interested in the Working Group’s activities. An archive of previous editions of the newsletter is available on the WG wiki [community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_pa…> and on the GNSO website [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_news…>. Kind regards, Emily Emily Barabas | Senior Policy Specialist ICANN | Internet Corporation for Assigned Names and Numbers Email: emily.barabas(a)icann.org | Phone: +31 (0)6 84507976

1 0

ICANN62 GNSO Policy Briefing Available for Download
by Ariel Liang June 6, 2018

June 6, 2018

Dear All, On behalf of the GNSO Team, I am happy to report that the GNSO Policy Briefing for ICANN62 is now available for download at http://go.icann.org/gnsobriefing If you prefer to download individual sections, you can do so by visiting this page<http://go.icann.org/policybriefing>. The policy briefing is intended to facilitate your preparation for ICANN62 – if you have any comments and/or suggestions on how we can further facilitate your preparation, let me know. Please feel free to share the link with your respective groups and anyone else that may be interested. If you have a twitter account, you may also retweet this post to help spread the word: https://twitter.com/ICANN_GNSO/status/1004338899634868225 Happy reading! Best Regards, Ariel Ariel Xinyue Liang Policy Analyst | Washington, DC Internet Corporation for Assigned Names and Numbers (ICANN)

1 0

GNSO Council Abstention Notification Form [#275]
by ICANN June 6, 2018

June 6, 2018

1 0

FW: ICANN Contracted Parties e-Briefing - June 2018
by Marika Konings June 5, 2018

June 5, 2018

For your information. [cid:image001.jpg@01D3FC1D.ED5973B0] 4 June 2018 Greetings, The ICANN Global Domains Division (GDD) Services & Engagement team would like to highlight some recent, more notable, community-impacting activities and projects below. We are preparing for the ICANN62 Policy Forum<https://meetings.icann.org/en/panamacity62> in Panama City, Panama and look forward to your participation. New & Noteworthy Temporary Specification for gTLD Registration Data The General Data Protection Regulation (GDPR) was adopted by the European Union (EU) in April 2016 and took full effect on 25 May 2018. On 17 May 2018, ICANN published the Temporary Specification for gTLD Registration Data<https://www.icann.org/resources/pages/gtld-registration-data-specs-en> (Temporary Specification). This Temporary Specification establishes temporary requirements to allow ICANN and gTLD registry operators and registrars to continue to comply with existing ICANN contractual requirements and community-developed policies in light of the GDPR. The Temporary Specification applies to all of ICANN’s contracted parties and is now in effect as of 25 May 2018. GDPR and Temporary Specification Webinar To offer further guidance and to learn how your organization may be affected by the Temporary Specification, we have scheduled a one-hour, interactive webinar on 6 June 2018. This will be a live webinar, held in English with live interpretation in Arabic, Chinese, French, Russian, and Spanish, and we encourage you to email your questions ahead of time to globalsupport(a)icann.org<mailto:globalsupport@icann.org> with “GDD Temp Spec Webinar” in the email’s subject line. A recording of the webinar will be posted as soon as possible on icann.org<http://icann.org>. Webinar Details & How to Attend Date: 6 June 2018 Time: 16:00 - 17:00 UTC (click here<https://www.timeanddate.com/worldclock/fixedtime.html?msg=NSp+Roadmap+for+R…> to view time zone converter) Join via Adobe Connect meeting here<https://participate.icann.org/tempspec06june2018> View dial-in information here<https://www.myrcplus.com/cnums.asp?bwebid=8369444&ppc=8021705257&num=1-605-…> Participant Code: 802 170 5257 Contracted Parties Encouraged to Prepare for RDAP As indicated in Section 1 of Appendix A<https://www.icann.org/resources/pages/gtld-registration-data-specs-en/#appe…> of the Temporary Specification for gTLD Registration Data<https://www.icann.org/resources/pages/gtld-registration-data-specs-en> (Temporary Specification), the ICANN organization intends to invoke the requirements in the registry and registrar agreements for implementation of the Registration Data Access Protocol<https://www.icann.org/rdap> (RDAP) service. Currently, several contracted parties are participating in an RDAP pilot program<https://www.icann.org/news/announcement-2017-09-05-en> to gain operational experience with RDAP and to define the appropriate operating profile(s) for the service. This pilot program is available to all community members. ICANN urges all registries and registrars to begin preparing to operate an RDAP service as the technical development of the service may take several months. Please see the RDAP page<https://www.icann.org/rdap> for more information. Privacy Policy Notification to Contracted Parties On Friday, 25 May 2018, the ICANN org updated its privacy policies and certain website terms of service to provide greater transparency, promote simplification, and align with recent changes in privacy laws applicable to ICANN org under the GDPR. To learn more, please visit https://www.icann.org/privacy. 2018 GDD Industry Summit The fourth annual Global Domains Division Industry Summit<https://www.icann.org/gddsummit> was held in Richmond, British Columbia, Canada, from 14-17 May. Over 400 stakeholders attended from 32 countries. The primary purpose of the summit is to provide a forum for ICANN’s contracted parties to discuss issues of mutual interest and importance, share best practices, and meet one-on-one with members of the ICANN org. This year, a multiple track format was added with one track dedicated to technical operations. The ICANN org is currently scouting an appropriate location in the Asia-Pacific region for the 2019 summit. In 2020, the GDD Industry Summit will be held in Europe. Domain Name Marketplace Indicators ICANN org concluded its assessment of the draft V1.0 indicator schema, jointly developed with the project Advisory Panel, for all vendor proposals received. The project was awarded to ZookNIC, Inc<http://www.zooknic.com/>. In April, the project team presented its proposed design approach and methodology to the Advisory Panel. The schema evaluation effort will conclude by the end of August 2018. Upon completion of the evaluation, ICANN org intends to procure the external data sources necessary to finalize the V1.0 Indicators for publication prior to the end of the calendar year. Final Proposed Draft Version 4.0 of the IDN Guidelines Now Published The Internationalized Domain Name (IDN) Implementation Guidelines<https://www.icann.org/resources/pages/implementation-guidelines-2012-02-25-…> relate to IDN registration policies and practices and are designed to minimize the risk of cybersquatting and consumer confusion. Once approved by the ICANN Board, these guidelines are contractually binding for most gTLD registries and registrars offering IDN registrations. After multiple public consultations and review of current IDN Guidelines version 3.0<https://www.icann.org/resources/pages/idn-guidelines-2011-09-02-en>, the IDN Guidelines Working Group<https://community.icann.org/display/IDN/IDN+Implementation+Guidelines> has published<https://www.icann.org/news/announcement-2018-05-10-en> the updated Final Proposed Draft version 4.0<https://www.icann.org/en/system/files/files/idn-guidelines-10may18-en.pdf> of the IDN Guidelines. This draft is pending approval from the ICANN Board of Directors. After approval, version 4.0 of the guidelines will become applicable to the relevant registries and registrars. Contracted Parties Satisfaction Survey In April 2018, the annual contracted parties satisfaction survey concluded. The objective of this survey was to understand and track feedback on the GDD’s work with contracted parties on an annual basis, based on the following dimensions: integrity, dependability, competence, commitment, and satisfaction. The published results<https://www.icann.org/resources/pages/metrics-gdd-2015-01-30-en> include a slide presentation with aggregated answers to each of the 12 survey questions and an executive summary. Naming Services Portal Terms of Use On 11 May 2018, changes to the Naming Services portal’s Terms of Use were deployed. Users who have not yet activated their accounts received an activation email. Please activate your account as soon as possible. For additional information regarding the features and functionality of the portal, please visit the Registry Resources<https://www.icann.org/resources/pages/registry-resources-2017-09-22-en> or Naming Services portal for Registrars<https://www.icann.org/resources/pages/nsp-registrars-2018-03-26-en> pages on icann.org<http://icann.org>. These pages include webinar recordings, user guides, and additional resources. Please email globalsupport(a)icann.org<mailto:globalsupport@icann.org> or contact your engagement manager with any questions. ICANN to Publish Semi-Annual Report on WHOIS Accuracy In mid-June, the ICANN org will publish the Phase 2 Cycle 6 WHOIS Accuracy Reporting System (ARS) Report. This report is a follow-up to previous ARS reports which have been published semi-annually since December 2015 and explores the syntax and operability accuracy of WHOIS records in gTLDs in light of the requirements of the 2009 and 2013 Registrar Accreditation Agreements (RAAs). It also examines the leading types of nonconformance, trends, and comparisons of WHOIS accuracy across gTLD types, ICANN regions, and RAA versions. Additional information about the project is available at whois.icann.org/whoisars<http://whois.icann.org/whoisars>. ICANN Finance Department to Annually Publish Tax Residency Certificate Effective this year and annually thereafter, the ICANN org will publish<https://www.icann.org/resources/pages/payments-2012-02-25-en>: (1) the lCANN certification letter stating it is a tax resident of United States; and (2) Form 6166 - U.S. Tax Residency Certification for the relevant year. We expect the certificates from the U.S. Internal Revenue Service will be published annually by ICANN org in the month of March. Tax residency forms for the years 2016, 2017 and 2018 are available on the ICANN Billing and Payments page<https://www.icann.org/resources/pages/payments-2012-02-25-en>. If you have questions, please submit a general inquiry case via the Naming Service portal or email globalsupport(a)icann.org<mailto:globalsupport@icann.org>. The 2018 Contractual Compliance Quarter One Performance Report In March 2018, the ICANN org published a blog<https://www.icann.org/resources/pages/compliance-reports-2018> on Enhancing Transparency in Contractual Compliance. As described in the report and blog<https://www.icann.org/resources/pages/compliance-reports-2018>, Contractual Compliance completed its work on enhanced metrics and performance reports<https://features.icann.org/compliance>. Contractual Compliance team members will be attending the ICANN62 Policy Forum and available for a limited number of one-on-one sessions with contracted parties, which can be requested by emailing compliance(a)icann.org<mailto:compliance@icann.org>. Policy Implementation Updates Protection of IGO and INGO Identifiers for All gTLDs On 16 January 2018, the Implementation of the Protection of IGO and INGO Identifiers for all gTLDs Policy was published<https://www.icann.org/resources/pages/igo-ingo-protection-policy-2018-01-16…>. Contracted parties have until 1 August 2018 to complete implementation of the new requirements for specified names of IGOs, the International Olympic Committee (IOC), and the Red Cross/Red Crescent Movement (RCRC). For INGOs, the implementation period will be 12 months from the release of the INGO Claims Systems Specification, which is currently under development. Thick WHOIS Transition Consensus Policy On 13 May 2018, the ICANN Board passed a Resolution<https://www.icann.org/resources/board-material/resolutions-2018-05-13-en#1.e> to defer contractual compliance enforcement of the Thick WHOIS transition policy in consideration of the European Union's General Data Protection Regulation (GDPR). ICANN Contractual Compliance will defer enforcing the following milestones until the dates listed below: • 30 November 2018: The registry operator must begin accepting Thick WHOIS data from registrars for existing registrations in .COM, .NET and .JOBS. • By 30 April 2019: All registrars must send Thick WHOIS data to the registry operator for all new registrations in .COM, .NET and .JOBS. • By 31 January 2020: All registrars are required to complete the transition to Thick WHOIS data for all registrations in .COM, .NET and .JOBS. For more information, please refer to the published Thick WHOIS Transition Policy available here<https://www.icann.org/resources/pages/thick-whois-transition-policy-2017-02…>. Privacy/Proxy Service Provider Accreditation Program ICANN org continues to work with the volunteer Implementation Review Team (IRT) on implementing the generic names supporting organization’s (GNSO) recommendations for a proxy/privacy service provider accreditation<https://www.icann.org/resources/pages/ppsai-2016-08-18-en> program. The ICANN org received a request from the RrSG on 4 May 2018<https://www.icann.org/en/system/files/correspondence/bunton-to-atallah-04ma…> to pause the IRT’s work, and a communication opposing this from the Coalition for Online Accountability<https://www.icann.org/en/system/files/correspondence/marks-metalitz-to-atal…> on 10 May 2018. These requests are currently under consideration. Registrars Naming Services Portal – Registrar ICANN recently launched the Naming Services portal for Registrars, an application built to streamline the way registrars conduct business with the ICANN org. This recent launch is a step towards in making the Naming Services portal the primary system of record and replacing legacy systems. As part of this release, all registrar primary contacts now have access to the portal with the ability to view the compliance tickets for the relevant IANA IDs. The ICANN org is continuing to work with a registrar portal planning group to gather input on the future feature enhancements to the portal. Webinar Announcement: Naming Services Portal Roadmap ICANN org will hold a webinar scheduled on 13 June 2018 to discuss the Naming Service portal for registrars, its current capabilities, and the roadmap for future releases. Participants have an opportunity to provide feedback and ask questions directly from the product team. A recording of the webinar will be made available following the session. Webinar Details & How to Attend Date: 13 June 2018 Time: 14:00 - 15:00 UTC (click here<https://www.timeanddate.com/worldclock/fixedtime.html?msg=NSp+Roadmap+for+R…> to view time zone converter) Join Via Adobe Connect<https://participate.icann.org/nspwebinar/> Via Dial-In Information<https://www.myrcplus.com/cnums.asp?bwebid=8369444&ppc=2897077927&num=1-605-…> Participant Code: 289 707 7927 2013 Registrar Accreditation Agreement (RAA) Renewal The initial set of early adopters that executed the 2013 RAA are nearing the auto-renewal process. The steps for the RAA auto-renewal process are detailed here<https://www.icann.org/resources/pages/renewing-2013-07-08-en>. Registrars who meet the criteria will have their agreements auto-renewed for a new five-year term of accreditation. Additional ICANN-designated Registrar Data Escrow Agent ICANN org announced<https://www.icann.org/news/announcement-3-2018-05-15-en> DENIC eG as an additional ICANN-designated Registrar Data Escrow Agent. Registrars wishing to change their escrow agent should follow the Registrar Data Escrow Agent Change<https://www.icann.org/resources/pages/registrar-data-escrow-agent-change-20…> process. Registries New Registry Resources Available on icann.org<http://icann.org> One of the Registry Services & Engagement team’s goals in the coming year is to review and update the registry resources<https://www.icann.org/resources/pages/registry-resources-2017-09-22-en> available on icann.org<http://icann.org>. We recently published the GDD Handbook<https://www.icann.org/en/system/files/files/gdd-ops-handbook-registry-opera…>, and the Registry Billing Frequently Asked Questions<https://www.icann.org/en/system/files/files/registry-operator-billing-faqs-…>. If you have feedback or suggestions regarding registry resources, please submit a general inquiry via the Naming Services portal or email globalsupport(a)icann.org<mailto:globalsupport@icann.org>. Procedure for Community gTLD Change Requests The ICANN org and the Community gTLD Change Request Working Group discussed updates to the draft procedure based on the comments received during Public Comment<https://www.icann.org/public-comments/community-gtld-change-procedure-2018-…> and finalized an updated version available here<https://www.icann.org/resources/pages/community-gtld-change-requests-proced…>. The ICANN org is preparing to offer this service for community gTLD registry operators with an expected launch date in July 2018. Registry Service and Evaluation Policy (RSEP) Process Improvements Representatives from the Registries Stakeholder Group (RySG) and ICANN org are reviewing the RSEP submission and review process. The objective is to find ways to improve timelines from the initial RSEP request through ICANN approval while providing more clarity to registries in each stage of the process. Following a review of proposed updates to the operational process at the GDD Industry Summit in Richmond, British Columbia, the RySG will provide feedback to staff, and this will be discussed in more detail at ICANN62. We hope this information provides you with additional insight and transparency into our ongoing activities and look forward to your feedback. Best Regards, Cyrus Namazi Vice President, Domain Name Services & Industry Engagement ICANN Global Domains Division [cid:image001.jpg@01D3FC23.2C1C3F60]

1 0

MP3, Adobe Connect recording and chat transcript/ GNSO Council with the ICANN Board meeting to discuss next steps following the adoption of ICANN Board of the temporary specification on Tuesday 5 June 2018 at 13:00 UTC.
by Terri Agnew June 5, 2018

June 5, 2018

Dear GNSO Council, Please find below the MP3, Adobe Connect recording and chat of the GNSO Council with the ICANN Board meeting to discuss next steps following the adoption of ICANN Board of the temporary specification held on Tuesday 5 June 2018 at 13:00 UTC. MP3: <https://audio.icann.org/gnso/gnso-council-icann-board-05jun18-en.mp3> https://audio.icann.org/gnso/gnso-council-icann-board-05jun18-en.mp3 Adobe Connect Recording URL: <https://participate.icann.org/p6ai9gt1qeg/> https://participate.icann.org/p6ai9gt1qeg/ Adobe Connect chat at: <https://gnso.icann.org/en/meetings/transcript-chat-council-icann-board-05ju…> https://gnso.icann.org/en/meetings/transcript-chat-council-icann-board-05ju… All on page: <https://gnso.icann.org/en/group-activities/calendar> 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: <mailto:terri.agnew@icann.org> terri.agnew(a)icann.org Skype ID: terri.agnew.icann Find out more about the GNSO by taking our interactive courses and visiting the <https://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy…> GNSO Newcomer pages Follow @GNSO on Twitter: <https://twitter.com/ICANN_GNSO> https://twitter.com/ICANN_GNSO Follow the GNSO on Facebook: <https://www.facebook.com/icanngnso/> https://www.facebook.com/icanngnso/ <http://gnso.icann.org/en/> http://gnso.icann.org/en/

1 0

GNSO Council Action Item - WHOIS conflicts
by Heather Forrest June 5, 2018

June 5, 2018

Dear Council colleagues, In reviewing the Action Items at the start of our May Council meeting the outstanding action item on the "Drafting Team on charter related to the next steps for the ICANN Procedure of Handling Whois conflicts with Privacy" was noted: - *ICANN Staff* to circulate a call for volunteers on or after 1 June 2018 to the GNSO Stakeholder Groups, with the request for each Stakeholder Group to appoint up to 3 members to the Implementation Advisory Group (IAG). The call for volunteers should also be more widely circulated to seek volunteers to serve as participants and observers to the IAG. We said we'd come back to this one on the list in light of the ongoing temporary specification next steps discussions. Would it be preferable to delay this call for volunteers until after we have progressed the next steps discussions further? Your thoughts much appreciated! Heather

3 2

REMINDER TO REGISTER IN ADVANCE : Announcement: Pre-ICANN62 Policy Webinar
by Terri Agnew June 4, 2018

June 4, 2018

https://www.icann.org/news/announcement-2018-05-23-en Register Now: Pre-ICANN62 Policy Webinar – 12 June 2018 The Policy Development Support Team is pleased to announce two webinar sessions to assist with the community's preparations for the ICANN62 Policy Forum: Pre-ICANN62 Policy Webinar Tuesday, 12 June 2018 10:00 and 19:00 Coordinated Universal Time (UTC) The webinar will run in English with simultaneous Spanish interpretation. The presentation materials will be translated into Spanish, and posted following the Webinar with the recordings of the sessions <https://www.icann.org/resources/pages/presentations-2012-08-27-en> here. Please register via <https://goo.gl/vZw8kM> this form by 11 June 2018! In this 90-minute webinar, the Policy Development Support Team will summarize the key policy activities taking place across the ICANN community. The Team will also answer your questions about ongoing community policy and advisory work and discuss what to expect at the ICANN62Policy Forum. To ensure that your questions about policy activities are addressed during the session, the Policy Team invites you to submit your questions through the <https://goo.gl/forms/dVbmhQOT8sakSsmg2> registration form or by email to <mailto:policyinfo@icann.org> policyinfo(a)icann.org. To assist with your preparation for this webinar and for ICANN62, the "Pre-ICANN62 Policy Report" and "Generic Names Supporting Organization Policy Briefing: ICANN62 Edition" will be published by Tuesday, 5 June 2018. Please be sure to download and review these materials beforehand for helpful background on policy activities and topics that the Policy Development Support Team will cover during the webinar, such as: * The cross-community discussions that will take place at ICANN62: * Geographic Names at the Top-Level (Work Track 5) * Update from the Registration Directory Service-WHOIS2 Review Team * General Data Protection Regulation (GDPR) Compliance, Access to WHOIS and Accreditation * The expected Initial Report from the New generic Top-Level Domain (gTLD) Auction Proceeds Cross Community Working Group * Presentation of the Final CCWG-Accountability Work Stream 2 Recommendations * The various policy development processes underway in the Country Code Names Supporting Organization (ccNSO), the Generic Names Supporting Organization (GNSO) and the Address Supporting Organization (ASO): * Retirement of Country Code Top-Level Domains * Review of All Rights Protection Mechanisms in All gTLDs * Next steps in relation to Registration Directory Services policy work * Curative Rights Protections for International Governmental Organizations and International Non-Governmental Organizations * New gTLD Subsequent Procedures * Regional Internet Registry policy development activities * Advisory Committee activities within the At Large Advisory Committee (ALAC), Governmental Advisory Committee (GAC), Root Server System Advisory Committee (RSSAC) and Security & Stability Advisory Committee (SSAC): * Organizational Review of the At-Large community: Next steps, implementation, and ALACsessions during ICANN62 * GDPR and Key Signing Key (KSK) Rollover discussions * At-Large discussion on new gTLDs and Work Tracks 1-5 * Regional At-Large Organization (RALO) Policy Hot Topics * GAC discussions on .amazon, IGO protections and 2-character codes at the second level * Board-GAC GDPR consultations * RSSAC statement on the distinction between RSSAC and Root-Ops (RSSAC033) * SSAC work concerning name collisions * Other topics of note: * Organizational Review of the ASO * ccNSO sessions on disaster and recovery and business continuity, ccNSO members meeting sessions, and Tech Day. * GAC onboarding initiatives * Report from the RSSAC May 2018 Workshop (RSSAC034) To complement this Pre-ICANN62 Policy Webinar, the GNSO Policy Development Support Team will host, with the Council leadership and Policy Development Process (PDP) working group chairs, a GNSOpolicy-focused webinar on Monday, 18 June 2018 at 21:00 UTC for 90 minutes. This webinar is intended to serve as a replacement for the previously-offered GNSO PDP updates provided during the GNSO weekend sessions and will assist the community in preparing for GNSO policy-related discussions at ICANN62. If you would like to participate in the GNSO Policy Webinar, please register <https://docs.google.com/forms/d/1Z5ENBC3wa2IOvAeYr27-pGU0lJIEeZCmgZkpAo2l0S…> here. The Policy Development Support Team looks forward to helping the ICANN community prepare for ICANN62!

1 0

Draft minutes of the GNSO Council meeting Thursday 24 May 2018
by Nathalie Peregrine June 4, 2018

June 4, 2018

Dear Councilors, Attached, please find the draft minutes of the GNSO Council meeting on Thursday 24 May 2018 for your review. If there are no comments, these minutes will be published on the website as approved, according to the GNSO Rules of Procedure [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> section 3.5 "If no objections are received within 10 days, the minutes will be deemed to have been approved for posting" on 14 June 2018. Thank you very much. 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

REMINDER - Re: For your input - questions for the ICANN Board following the adoption of the temporary specification
by Marika Konings June 4, 2018

June 4, 2018

Reminder, please provide your input no later than tomorrow, Friday 1 June by 23.00 UTC so that these questions can be shared with the ICANN Board ahead of the meeting that is planned for next Tuesday. Best regards, Marika From: council <council-bounces(a)gnso.icann.org> on behalf of Marika Konings <marika.konings(a)icann.org> Date: Thursday, May 24, 2018 at 16:55 To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [council] For your input - questions for the ICANN Board following the adoption of the temporary specification Dear All, As discussed during the Council meeting earlier today, please include your input as well as that of your respective SG/C with regards to which questions / issues that should be discussed with the ICANN Board following the adoption of the temporary policy specification in this google doc: https://docs.google.com/document/d/1I5fyQTqYmcKft-4yiOKP6WMcCST0a1sZGtAY1jo… [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…>. A number of initial questions that have come up in the various conversations have been included as a starting point. Best regards, Marika 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 [learn.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__learn.icann.org_courses…> and visiting the GNSO Newcomer pages [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>.

3 2

Agenda for Council meeting
by Heather Forrest June 2, 2018

June 2, 2018

Colleagues, Without the AC room, we'll be relying on the agenda and links as posted in the ICANN61 meeting schedule, here: https://61.schedule.icann.org/meetings/647702 Many thanks and best wishes, Heather

5 6

Fwd: Secretary's Notice to Empowered Community of Board Approval of FY19 Operating Plan and Budget and Secretary's Notice to Empowered Community of Board Approval of Updates to Five Year Operating Plan 2019
by Heather Forrest June 2, 2018

June 2, 2018

Dear Council colleagues, Please see below and attached announcing the Board's approval of the FY19 budget. Best wishes, Heather ---------- Forwarded message ---------- From: John Jeffrey <john.jeffrey(a)icann.org> Date: Sat, Jun 2, 2018 at 7:47 AM Subject: Secretary's Notice to Empowered Community of Board Approval of FY19 Operating Plan and Budget and Secretary's Notice to Empowered Community of Board Approval of Updates to Five Year Operating Plan 2019 To: "ecadmin(a)icann.org" <ecadmin(a)icann.org>, "chair(a)nro.net" <chair(a)nro.net>, Alan Greenberg <alan.greenberg(a)mcgill.ca>, "katrina(a)nic.lv" <katrina(a)nic.lv>, Heather Forrest <haforrestesq(a)gmail.com>, Manal Ismail <manal(a)tra.gov.eg> Greetings, Attached please find the Secretary’s Notice of Board Approval of FY19 Operating Plan and Budget and Secretary’s Notice of Board Approval of Updates to Five Year Operating Plan 2019 sent on behalf of John Jeffrey. 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 Skype: peg.rettino Direct: 310-301-3868

1 0

Fwd: [ECAdmin] Secretary's Notice to Empowered Community of Board Approval of FY19 Operating Plan and Budget and Secretary's Notice to Empowered Community of Board Approval of Updates to Five Year Operating Plan 2019
by Heather Forrest June 2, 2018

June 2, 2018

Dear colleagues, Please note the announcement below regarding the 21-day Rejection Action Petition Period following the Board's approval of the FY19 budget. Best wishes, Heather ---------- Forwarded message ---------- From: Mary Wong <mary.wong(a)icann.org> Date: Sat, Jun 2, 2018 at 12:14 PM Subject: Re: [ECAdmin] Secretary's Notice to Empowered Community of Board Approval of FY19 Operating Plan and Budget and Secretary's Notice to Empowered Community of Board Approval of Updates to Five Year Operating Plan 2019 To: "ecadmin(a)icann.org" <ecadmin(a)icann.org> Dear Empowered Community Administration members, The delivery of notice of the Board’s approval of the FY19 Operating Plan and Budget (dated 1 June 2018) initiated the 21-day Rejection Action Petition Period under the ICANN Bylaws. For this action and purpose, this *Rejection Action Petition Period will end at* *11.59 p.m. US Pacific time on 22 June 2018 (or 06.59 UTC on 23 June 2018*). Should a rejection petition be submitted to a Decisional Participant within the petition period *and* should that Decisional Participant accept that petition (in accordance with its own internal rules and processes), this will trigger a further 7-day Rejection Action Petition Support Period (ending at 11.59 p.m. US Pacific time on 29 June 2018 (or 06.59 UTC on 30 June 2018), during which time that Decisional Participant will need to seek the support of at least one other Decisional Participant. If support for the petition is obtained from at least one other Decisional Participant and the requisite notice provided to the Empowered Community Administration (among others), the Bylaws provide that “ICANN shall, *at the direction of the EC Administration*, convene a forum at which the Decisional Participants and interested parties may discuss the Rejection Action Supported Petition”. This Community Forum must be conducted within a 21-day period beginning upon the expiration of the Rejection Action Petition Support Period – for present purposes, and assuming all of the above steps have been fulfilled, the requisite *Community Forum period will commence at 11.59 p.m. US Pacific time on 29 June 2018 (06.59 UTC on 30 June 2018) and end at 11.59 p.m. US Pacific time on 20 July 2018 (06.59 UTC, 21 July 2018).* Please note that Section 2.3(c) of Annex D of the Bylaws states that, “notwithstanding any statement in the Rejection Action Supported Petition, a Rejection Action Community Forum to discuss a Rejection Action Supported Petition relating to an ICANN Budget or IANA Budget may only be held at a scheduled ICANN public meeting if such Rejection Action Community Forum occurs during the Rejection Action Community Forum Period, without any extension of such Rejection Action Community Forum Period” - this means that, for the FY19 Operating Plan and Budget, any Community Forum that may need be scheduled will *not* take place face-to-face or at an ICANN meeting but will, instead, be *conducted via remote participation methods such as teleconference, web-based meeting room and/or such other form of remote participation as the EC Administration selects*” (Section 2.3(d), Annex D). Please see Annex D of the Bylaws for the full text describing all the various criteria and steps applicable to a Rejection Action process ( https://www.icann.org/resources/pages/governance/bylaws-en/#annexD) including some specific criteria applicable to petitions to reject an ICANN budget. Please also do not hesitate to let me know if you or any of your community groups and members have questions about the process. Thanks and cheers Mary (for the staff team supporting the Empowered Community) *From: *ECAdmin <ecadmin-bounces(a)icann.org> on behalf of John Jeffrey < john.jeffrey(a)icann.org> *Date: *Saturday, June 2, 2018 at 05:47 *To: *"ecadmin(a)icann.org" <ecadmin(a)icann.org>, "chair(a)nro.net" < chair(a)nro.net>, Alan Greenberg <alan.greenberg(a)mcgill.ca>, "katrina(a)nic.lv" <katrina(a)nic.lv>, Heather Forrest <haforrestesq(a)gmail.com>, Manal Ismail < manal(a)tra.gov.eg> *Subject: *[ECAdmin] Secretary's Notice to Empowered Community of Board Approval of FY19 Operating Plan and Budget and Secretary's Notice to Empowered Community of Board Approval of Updates to Five Year Operating Plan 2019 Greetings, Attached please find the Secretary’s Notice of Board Approval of FY19 Operating Plan and Budget and Secretary’s Notice of Board Approval of Updates to Five Year Operating Plan 2019 sent on behalf of John Jeffrey. 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 Skype: peg.rettino Direct: 310-301-3868 _______________________________________________ ECAdmin mailing list ECAdmin(a)icann.org https://mm.icann.org/mailman/listinfo/ecadmin

1 0

Strategic Planning Session 2019
by Heather Forrest June 1, 2018

June 1, 2018

Dear Council colleagues, I write with some welcome good news, for the GNSO generally and next year's GNSO Council in particular. I have just received notice that our Additional Budget Request for holding a Strategic Planning Session in 2019 has been approved. You may recall that the request built in flexibility as to a 2 or 3 day schedule, in view of the FY19 budget and the 2018 SPS schedule (taking into account that the day we had on Bylaws review was a one-off). From our request, I understand that ICANN org has recommended that the Board approve a full 2-day face-to-face meeting of the Council, to be held separately from an ICANN Public Meeting. I also understand that the ABR process was highly competitive, with 55 applications received, and that most requests were scaled back to some degree. I personally believe we've done well here to get the 2 full days, and I'm confident that the next Council leadership team and Council can make good use of this to continue the professionalisation and learning process. We have too much on our collective plates right now to begin planning, but I would suggest that Rafik, Donna and I give some preliminary thought to the logistics as our term ends, to hand over to the 2018-19 Council when it is seated in Barcelona. Best wishes, Heather

7 24