October 2018 - council - lists.icann.org

Fwd: Recommendation to Terminate Next Gen RDS PDP
by Stephanie Perrin Oct. 17, 2018

Oct. 17, 2018

Please find attached a request from the Interim co-Chair of the gTLD RDS PDP to terminate the working group. I believe it is self explanatory. Also attached is a motion to terminate. Thanks to Marika and to RDS leadership for their help on this. And many many thanks to the volunteers, leaders, and staff who worked so hard on the RDS PDP. Stephanie Perrin -------- Forwarded Message -------- Subject: Recommendation to Terminate Next Gen RDS PDP Date: Fri, 12 Oct 2018 18:28:14 +0000 From: Anderson, Marc <mcanderson(a)verisign.com> To: stephanie.perrin(a)mail.utoronto.ca <stephanie.perrin(a)mail.utoronto.ca> CC: gnso-next-gen-rds-lead(a)icann.org <gnso-next-gen-rds-lead(a)icann.org> Stephanie, I’m writing you in my capacity as interim co-chair of the Next Generation gTLD RDS to replace Whois PDP Working Group. In light of the changed circumstances impacting the working group, the leadership team is of the unanimous opinion that the working group should be terminated in accordance with article 15 in Annex 2 of the GNSO operating procedures. Therefore, following those procedures, the leadership team is delivering to you as GNSO council liaison the attached Termination Summary on behalf of the working group for consideration by the GNSO council. Thank you, Marc Anderson

3 2

IDN Program Update to GNSO at ICANN63
by Steve Chan Oct. 17, 2018

Oct. 17, 2018

Dear Councilors, You may have seen in Nathalie’s email on 15 October, about the GNSO Working sessions, that one of the agenda items is IDN Variants. In preparation for that that session, Sarmad Hussain and Pitinan Kooarmornpatana (who manage the IDN Program here at ICANN) have prepared the attached materials, which includes 1) a brief summary update on the IDN program and 2) the full set of slides that Sarmad will strategically pick and choose from to try and ensure that the update fits into the allotted time. As there will not be sufficient time to go over the complete set of slides, you may want to review ahead of time and to the extent you have any questions leading up to the session, please feel free to reach out to Sarmad and Pitinan, both copied on this message. Thank you and see you all soon. Best, Steve Steven Chan  Policy Director, GNSO Support ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536  Mobile: +1.310.339.4410 Office Telephone: +1.310.301.5800 Office Fax: +1.310.823.8649 Find out more about the GNSO by taking our interactive courses and visiting the GNSO Newcomer pages. Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO Follow the GNSO on Facebook: https://www.facebook.com/icanngnso/ http://gnso.icann.org/en/

1 0

FW: About the FY19 Board Activities & Priorities - ICANN Board Chair
by Mary Wong Oct. 17, 2018

Oct. 17, 2018

Dear Councilors, You may be interested in Board Chair Cherine Chelaby’s latest blog post (reproduced below). In addition to updates on the Board’s governance activities on a range of priorities such as reviews and budget planning, there were several points that specifically noted GNSO policy development work which I’ve taken the liberty of highlighting in yellow for your easy reference. In relation to recent Council actions, the Board highlighted the Red Cross and Curative Rights PDPs. Wishing everyone who is joining ICANN63 in person safe travels and cheers to all, Mary Subject: [Team-Leaders] [So-ac-sg-cleaders] About the FY19 Board Activities & Priorities - ICANN Board Chair https://www.icann.org/news/blog/about-the-fy19-board-activities-priorities [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blo…> With ICANN63<https://meetings.icann.org/en/barcelona63> in Barcelona now on the horizon, the Board felt it appropriate to once again share our activities and priorities for FY19, much like we did last year [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blo…>. They continue to be divided into five key areas of responsibilities, or "blocks," that the Board uses to organize and think about its work. Within these blocks of responsibilities, the Board's substantive activities are most often community-driven. The Board has also identified operational priorities for itself, with associated deliverables, timelines, and measurements within each. For each block, (i) I provide a short overview of the Board's main duties, (ii) go over the various activities the Board is focusing on, and (iii) outline the priorities that we've laid out. Block 1 - Oversight Over Policy Development and Cross Community Initiatives The duties of the Board under this responsibility include: * Being well informed of the content, priority, and timing of all policies being developed by the community and being ready to approve these policies when submitted to the Board. * Providing timely Board comments to cross-community initiatives. * Responding to Supporting Organization/Advisory Committee (SO/AC) advice on a timely basis. FY19 Activities With respect to community-driven activities, in FY19 the Board is focusing on: European General Data Protection Regulation (GDPR) – The Board continues to work closely with ICANN org and the community on several fronts: * (a) Expedited Policy Development Process (EPDP) We are closely monitoring these discussions, with two Board members serving as liaisons to the EPDP. We acknowledge the progress that has been made so far and look forward to the group reaching timely consensus on a new policy to replace the Temporary Specification. * (b) Unified Access Model Developing a possible access model has been part of ICANN org's conversations regarding the GDPR from the start. The Board is closely following the ICANN org's efforts to seek more legal guidance and certainty for all parties with respect to a possible access model to reduce the legal risks for contracted parties who offer WHOIS services. The support and input from the community to seek that guidance from the Data Protection Authorities (DPAs) is important. New gTLD Subsequent Procedures PDP – The Board continues to follow the work being done in this PDP in preparation for reviewing the recommendations. The Board has responded to the request for feedback from the PDP working group. CCWG on Auction Proceeds – The Board continues to closely follow this work and has provided input on the disbursement mechanisms. Red Cross Names Protection – The Board monitored progress of the reconvened Red Cross PDP Working Group and noticed with interest that the GNSO Council recently approved, with a super majority vote, the consensus recommendations from that PDP, which modify a previously-adopted GNSO policy. IGO-INGO Curative Rights – The Board is monitoring progress of the IGO-INGO Access to Curative Rights Mechanisms PDP Working Group and wishes that a path forward is developed to facilitate the resolution of the outstanding inconsistencies between GAC advice and prior GNSO policy recommendations on the overall scope of IGO protections. FY19 Priorities With respect to operational priorities, in FY19 the Board continues to focus on alignment with and furthering ICANN's mission. In particular: 1.1 ICANN's Multistakeholder Model – The Board will facilitate a community discussion on how the ICANN's multistakeholder model should evolve to balance the need for increased inclusivity, transparency, and accountability with the need for effectiveness, timely delivery, and the efficient use of ICANN resources. Following the community discussion, the Board will develop a consultation paper on this topic before the end of FY19. 1.2 The Global Public Interest (GPI) – The Board will develop a consultation paper on this topic. In addition to the Articles of Association committing ICANN to serving the public Interest, there are several specific mentions in the Bylaws, including: "to ensure that the bottom-up, multistakeholder policy development process is used to ascertain the global public interest." However, our community has never reached consensus on what the GPI is as related to the specific issue of the policy development process. 1.3 Temporary Specification – The Board is planning on reviewing and renewing the Temporary Specification in November 2018 and in February 2019, before it expires on 25 May 2019. Block 2 - ICANN Org Oversight The duties of the Board under this responsibility include: * Ensuring that community-approved policies are implemented in a manner consistent with the adopted policies. * Overseeing the implementation of significant engineering projects undertaken by the ICANN org. * Overseeing that the ICANN org is delivering operational services to the community both effectively and efficiently. FY19 Activities With respect to community-driven activities, in FY19 the Board is focusing on: Domain Abuse Activity Reporting (DAAR) – The Board continues to oversee the development of this system, which currently holds almost 24 months of data. The ICANN org will soon start providing regular reports from that data to the Board and the community. Information Transparency Initiative (ITI) – The Board is overseeing the development of this system, which is in its ninth month of implementation work. The ITI project team continues to make progress on the technical architecture of the documentation management system (DMS) and content management system (CMS). Project Cost Support Team (PCST) – The entire ICANN ecosystem has taken on the challenge of managing resources more effectively. The Board and ICANN org will continue to promote the deployment of the now proven methodology of the PCST, in order to ensure that ICANN becomes more financially disciplined, and that decisions to start projects, reviews, and community initiatives must be based on clear needs, priorities, and affordability. The use of the PCST to support the GNSO EPDP is another good example that demonstrates its usefulness. Anti-Harassment Issues – The Board has created a new working group specifically focused on monitoring the implementation of its resolution to address anti-harassment issues. Accountability Workstream 2 (WS2) Implementation Plan – Once the chartering organizations approve the WS2 recommendations, the Board will work with the ICANN org to develop a cost-effective implementation plan. FY19 Priorities With respect to operational priorities, in FY19 the Board is focusing on improving cost awareness and financial stability, as well as strengthening security. In particular: 2.1 Cost Awareness and Financial Stability * ICANN Reserve Fund – The Board will continue with the process of replenishing the reserve fund, following the community's engagement in the two public comments processes that have now been completed on the target level and rationale and on the replenishment strategy. The Board is now adopting a replenishment strategy, based on community input, and is instructing the ICANN org to implement it. The next step is to develop a consultation paper on an updated governance of the reserve fund. * 2-Year Budgeting – The Board and ICANN org are working on a proposal for a 2-year budget cycle, aimed at providing more time for expanded engagement between the community, ICANN org and Board to plan for future activities and resource allocation. 2.2 Security * L- Root Strategy – The Board will work with ICANN org to finalize and implement the strategy. * Crisis Communication Plan – The Board and ICANN org will develop a communication plan for coordinating with other Root Operators during root server crises. * Key Signing Key (KSK) Rollover – The Board has approved a resolution to rollover the KSK on 11 October 2018, and will keep monitoring its progress closely. * DNS Evolution and Security – The Board will cooperate actively with the technical community on the evolution of the DNS and on improving its security. Block 3 - Strategic & Forward Thinking The duties of the Board under this responsibility include: * Monitoring the implementation of the Five-Year Strategic Plan. * Being aware of external forces and trends at work and anticipating how they might affect ICANN and the community. * Thinking ahead about any structural or organizational issues and assessing their impact on ICANN. * Ensuring that the ICANN org's globalization strategy evolves in furtherance of ICANN's mission. FY19 Activities With respect to strategic and forward-thinking activities, in FY19 the Board is focusing primarily on the completion of ICANN's new strategic plan for 2021to 2025: ICANN Strategic Plan – The approach to develop the next strategic plan consists of four phases: trends identification, prioritization and analysis, drafting, and finalization of the plan. The community, Board, and the ICANN org completed the process of identifying the trends in June 2018. The Board and ICANN org have since then conducted an analysis of key priority trends and their impacts on ICANN. The findings from the analysis will be shared with the community via webinars in October. This will help inform further community discussions during a session planned for ICANN63. A draft strategic plan will be assembled and posted for public comment following ICANN63. Read more about ICANN's strategic planning process in this blog [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blo…>. FY19 Priorities With respect to operational priorities, in FY19 the Board is focusing on: 3.1 Governance Model for the DNS Root Server System – The Board Technical Committee is working with the Office of ICANN's Chief Technology Officer (OCTO) in reviewing the recent advice received from the Root Server System Advisory Committee (RSSAC), in order to propose to the Board an action plan in response to the RSSAC037 & RSSAC038 recommendations regarding a Proposed Governance Model for the DNS Root Server System. 3.2 Board Skills Adequacy (deferred from FY18) – The Board continues to focus on ensuring that it has all of the skillsets needed to serve ICANN. We are finalizing the development of a three-year rolling skills plan to form a part of the Board Governance Committee's tool kit to guide Board training, committee slating, and information provided to Board nominating bodies. Block 4 - Governance & Fiduciary Responsibilities The duties of the Board under this responsibility include: * Proficiently handling ICANN's governance and accountability issues. * Discharging its fiduciary (legal and financial) responsibilities. * Monitoring organizational risks and mitigation actions. * Progressing the implementation (and understanding) of the Bylaws. * Improving Board transparency. FY19 Activities In FY19, the Board is focusing on progressing issues which are subject to accountability mechanisms: Specific & Organizational Reviews – Progress has been made on the issue of Specific and Organizational reviews. Our collective aim is to have a more sustainable and practical model that allows for effective participation without overwhelming our already heavily-taxed volunteer community. We received community input on an initial proposal, and recently finished a public comment period on a second paper on this issue. The Board appreciates the input provided by the community and, together with the ICANN org, we are now navigating through the comments. It is suffice to say at this stage that ATRT3 will start in early 2019, but we are still defining a path forward for the specific and organizational reviews. Independent Review Process (IRP) – The Board is following closely the work of the Implementation Oversight Team (IOT) regarding the development of Interim Supplementary Procedures for the ICANN IRP. The IOT is also responsible for recommending training materials for the panelists for the IRP, as well as updating the Cooperative Engagement Process leading up to a filing of IRPs. The Board has active liaisons to the IOT and will work to meet all of the Board's bylaws obligations in appointing standing panelists to hear IRPs. .HALAL & .ISLAM – The Board made progress on these two outstanding applications, and at its meeting on 3 October 2018, the Board resolved that the pending applications for .halal and .Islam not proceed. .PERSIANGULF – The Board made progress on this outstanding application, and at its meeting on 3 October 2018, the Board adopted the portion of the IRP Panel's recommendation that the application for .Persiangulf submitted in the current new gTLD round not proceed and directed the President and CEO, or his designee(s), to take all steps necessary to implement this decision. Pending Accountability Mechanisms – The Board was updated on the remaining new gTLD applications (including .WEB & .AMAZON) on hold due to pending accountability mechanisms that are in various stages of completion. Our keen interest in properly addressing all of the accountability mechanism matters was a key factor in our creating the new Board Accountability Mechanism Committee (BAMC), which has allowed for a deep understanding of the issues and allowed the committee to make recommendations to the Board for action. The BAMC has followed the progress and is making all efforts to promptly address each issue as they arise to the Board level. This year, in particular, we have begun to work through the Reconsideration Requests that were placed on hold during the pendency of the Community Priority Evaluation Process Review, and we have recently completed receiving oral presentations from those parties seeking reconsideration that chose to make such a presentation. FY19 Priorities With respect to operational priorities, in FY19 the Board is focusing on: 4.1 Annual Review Implementation Report – In line with article 4.5 of the Bylaws, the Board will develop a process for the preparation and publication of an "Annual Review Implementation Report" on the state of the accountability and transparency reviews. 4.2 Picket Fence – The Board will post a blog intended to provide clarity and a shared understanding of the 'picket fence' under the new Bylaws. 4.3 Board Effectiveness – The Board continues to improve its own operational effectiveness, through: * Implementing actions identified in the Board 360 review conducted in FY18. * Undertaking communications training for Board members. Block 5 - Community Engagement & External Relationships The duties of the Board under this responsibility include: * Reaching out and being present in the community during the ICANN Public meetings, as well as in-between ICANN Public meetings. * Supporting the ICANN org in meeting four strategic objectives of: * Serving ICANN's stakeholders effectively so that they participate more actively and meaningfully at ICANN. * Attracting new stakeholders globally to meet the needs of a globalized ICANN. * Developing effective relationships with key actors in the global Internet ecosystem, based on an insightful mapping of the roles they play, the dynamic between them, and the type of rapport ICANN wishes to have with each one of them. * Advocating ICANN's mission and its multistakeholder model of governance within the Internet Governance ecosystem. FY19 Activities With respect to community-driven activities, in FY19 the Board is focusing on: ICANN's Global Community – The Board continues its engagement activities with the ICANN global community with specific focus on the technical community. More recently, the Board has been in dialogue with the Regional Internet Registries (RIRs) to better understand their needs in an attempt to identify a more effective way for them to participate in the ICANN Empowered Community. Internet Governance (IG) Ecosystem – The Board continues to oversee the implementation of the plan it approved last year for ICANN's participation in the IG ecosystem. The Board wants to ensure that ICANN's participation in the IG ecosystem serves our mission and reflects the commitments and core values specified in the ICANN Bylaws. FY19 Priorities With respect to operational priorities, in FY19 the Board is focusing on: 5.1 Service Satisfaction (deferred from FY18) – The Board will review the findings of community surveys [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_search_-…> conducted over the past three years to understand whether ICANN (Board and ICANN org) activities actually lead to an overall improvement of service satisfaction within the community. 5.2 Relationships with External Bodies – The Board is developing a clear rationale for membership, alliances, and sponsorships with other international organizations and key actors in the global Internet governance space. Let me close by saying that the Board sincerely hopes that this blog will enable you to have a better understanding of the Board's responsibilities and its FY19 activities and priorities. The Board looks forward to engaging with you in Barcelona and answering any questions you may have about this blog. Author: Cherine Chalaby, Chair, ICANN Board of Directors David A. Olive | Senior Vice President Policy Development Support ICANN | Internet Corporation for Assigned Names and Numbers 801 17th Street NW, Suite 400 | Washington, DC 20006<x-apple-data-detectors://3>

1 0

Final Proposed Agenda GNSO Council Meetings part I and part II -24 October 2018 at 11:00 UTC
by Nathalie Peregrine Oct. 16, 2018

Oct. 16, 2018

Dear all, Please below find the final proposed agenda for the GNSO Council Meetings part I and part II on 24 October 2018 at 11:00 UTC. Final GNSO Council Agenda 24 October 2018 - Part I 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/HxlpBQ> https://community.icann.org/x/wRVpBQ 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: 11:00 UTC: https://tinyurl.com/y9663p2o 04:00 Los Angeles; 07:00 Washington; 10:00 London; 16:00 Islamabad; 20:00 Tokyo; 22:00 Hobart GNSO Council Meeting remote participation details: https://63.schedule.icann.org/meetings/901654 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<https://gnso.icann.org/en/meetings/minutes-council-16aug18-en.pdf> of the GNSO Council meeting on the 26 August 2018 were posted on the 03 September 2018 Minutes<https://gnso.icann.org/sites/default/files/file/field-file-attach/minutes-c…> of the GNSO Council meeting on the 25 September 2018 were posted on the 13 October 2018 Item 2. Opening Remarks / Review of Projects & Action List (15 minutes) 2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List <https://gnso.icann.org/en/council/project> and Action Item List<https://community.icann.org/x/RgZlAg> Item 3. Consent Agenda (5 minutes) * Reconfirmation of Julf Helsingius as GNSO Council Liaison to the Governmental Advisory Committee (motion<https://community.icann.org/x/yBVpBQ>) * Recommendations Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/reconvene…> to the ICANN Board regarding adoption of the Final Report from the Reconvened Working Group on Red Cross Names Policy Development Process (PDP) Working Group. Item 4: COUNCIL VOTE – Confirmation of Standing Committee on ICANN’s Budget and Operations Charter (10 minutes) Standing Committee on ICANN’s Budget and Operations Charter (SCBO) has operated under an interim charter since its adoption on 21 December 2017. In FY18 under this interim charter, the SCBO developed four public comments (IANA-PTI FY19 Budget, ICANN's Reserve Fund Target Level, ICANN's Draft FY19 Budget and Operating Plan, & ICANN Reserve Fund: Proposed Replenishment Strategy) on behalf of the GNSO Council that were later accepted and posted to ICANN's public forum On 17 September 2018, the SCBO delivered an After Action Report on the SCBO experiences and lessons learned where the report suggested that the SCBO charter did not warrant any change and that the SCBO become a permanent standing committee of the GNSO Council Here, the Council will vote to adopt the charter of the SCBO on a permanent basis. 4.1 – Presentation of motion<https://community.icann.org/x/yBVpBQ> (Ayden Férdeline) 4.2 – Council discussion 4.3 – Council vote (voting threshold: simple majority) Taking this action is within the GNSO’s remit, in respect of the financial impact on the GNSO’s responsibility “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.” Item 5: COUNCIL VOTE – GNSO Policy Development Process 3.0 (20 minutes) In January 2018, the GNSO Council held an inaugural three-day Strategic Planning Session. On Day 3 of this meeting, the GNSO Council reviewed the workload for the year ahead and identified potential milestones, noting that the current average timeline for delivery of an Initial Report has increased at least 2-4 times compared to previous PDPs. In addition to noting the increased duration of the PDP lifecycle, the Council began to identify challenges being encountered in PDPs, informed by a staff discussion paper on optimizing increased engagement and participation while ensuring efficient and effective policy development. The effort to increase the effectiveness and efficiency of the GNSO PDP process is called GNSO PDP 3.0. On 11 May 2018, a summary paper was shared with the Council, summarizing input received to date, as well as some proposed incremental improvements. The Council members and their respective Stakeholder Groups and Constituencies were invited to provide input, after which a summary report<https://gnso.icann.org/en/drafts/pdp-summary-feedback-10sep18-en.pdf> was prepared and shared with the Council on 10 September 2018, followed by a dedicated webinar<https://participate.icann.org/p1s5rcio69b/> on 11 September 2018. Based on the input received as well as the subsequent webinar, Council leadership developed a proposed GNSO Policy Development Process 3.0 How to increase the effectiveness and efficiency of the GNSO Policy Development Process <https://gnso.icann.org/sites/default/files/file/field-file-attach/pdp-incre…> document for Council consideration. The GNSO Council and broader community will have reviewed and discussed the GNSO PDP 3.0 Implementation Plan during the GNSO Weekend Session at ICANN63. Here, the Council will vote to adopt the GNSO PDP 3.0 Implementation Plan. 5.1 – Presentation of motion<https://community.icann.org/x/yBVpBQ> (TBD) 5.2 – Council discussion 5.3 – Council vote (voting threshold: simple majority) Taking this action is within the GNSO’s remit, in the GNSO’s pursuit to improve on its responsibility “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.” Item 6: COUNCIL VOTE – Termination of the Next-Generation gTLD Registration Directory Service (RDS) to replace WHOIS Policy Development Process (15 minutes) On 19 November 2015, the GNSO Council adopted the charter<https://community.icann.org/x/E4xlAw> for the next-generation gTLD Registration Directory Service (RDS) to replace WHOIS Policy Development Process Working group. Following ICANN61 (March 2018), the RDS PDP Leadership decided to put on hold WG meetings indefinitely. This decision was made in light of the uncertain status of GDPR-related work and the possible duplication of efforts as a result of the adoption by the ICANN Board of the Temporary Specification for gTLD Registration Data. Following the initiation by the GNSO Council of the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration data, Stephanie Perrin in her role as the GNSO Council Liaison to the RDS PDP WG, submitted the required Termination Summary on 17 July 2018 to recommend to the GNSO Council that the RDS PDP WG be terminated as per section 15 of the PDP Manual. Here, the Council will vote to terminate the Next-Generation gTLD Registration Directory Service (RDS) to replace WHOIS Policy Development Process. 6.1 – Presentation of motion<https://community.icann.org/x/yBVpBQ> (Stephanie Perrin) 6.2 – Council discussion 6.3 – Council vote (voting threshold: Supermajority) Taking this action is within the GNSO’s remit as indicated in section 11.3.i.vii of the ICANN Bylaws, where the Council may “Terminate a PDP: Once initiated, and prior to the publication of a Final Report, the GNSO Council may terminate a PDP only for significant cause, upon a motion that passes with a GNSO Supermajority Vote in favor of termination.” Item 7: COUNCIL VOTE – IGO-INGO Access to Curative Rights Protection Mechanisms (15 minutes) The IGO-INGO Access to Curative Rights Protection Mechanisms PDP WG had worked to resolve a final recommendation relating to IGO jurisdictional immunity and registrants’ rights to file court proceedings. The WG has determined consensus on a set of options for this final recommendation, as well as for all other recommendations. The WG Chair proposed his determination of consensus levels for all recommendations, which the WG affirmed. On 27 June 2018, the GNSO Council passed a resolution<https://gnso.icann.org/en/council/resolutions#201806>, thanking the PDP WG for its efforts and requesting that it submit its Final Report in time for the 19 July 2018 Council meeting. After having agreed on consensus levels for its final recommendations, the WG considered the text of its Final Report. On 9 July 2018, the PDP WG submitted its Final Report<https://gnso.icann.org/en/issues/igo-ingo-crp-access-final-17jul18-en.pdf> to the GNSO Council for its consideration, which contains five consensus recommendations and three minority statements, documenting their disagreement either with one or more of the final recommendations or other parts of the Final Report. There remain several inconsistencies between GAC advice and consensus recommendations from the IGO-INGO PDP WG, which have yet to be reconciled, including on the topic of appropriate protections for IGO acronyms (both preventative and curative). During its 19 July Council meeting, the Council resolved<https://gnso.icann.org/en/council/resolutions#201807> to accept the Final Report from the IGO-INGO Access to Curative Rights Mechanisms PDP Working Group and has begun considering the topic of curative rights protections for IGOs in the broader context of appropriate overall scope of protection for all IGO identifiers. On 9 October 2018, the Council held a question and answer webinar to review the recommendations and to ask itself a series of questions, 1) Does the Council believe that the PDP has addressed the issues that it was chartered to address (i.e. What questions/topics was the Working Group chartered to consider, did it consider those charter topics/questions, and did it do so in a legitimate way)?; 2) Has the PDP followed due process?; and 3) Did the PDP Working Group address GAC advice on the topic? Here, the Council will vote on to accept to recommendation and Final Report of the IGO-INGO Access to Curative Rights Protection Mechanisms PDP WG. 7.1 – Presentation of motion<https://community.icann.org/x/yBVpBQ> (TBD) 7.2 – Council discussion 7.2.1: Does the Council believe that the PDP has addressed the issues that it was chartered to address (i.e. What questions/topics was the Working Group chartered to consider, did it consider those charter topics/questions, and did it do so in a legitimate way)? 7.2.2: Has the PDP followed due process? 7.2.3: Did the PDP Working Group address GAC advice on the topic? 7.3 – Council vote (voting threshold: approval of PDP recommendations imposing contractual obligations on Contracted Parties: Supermajority; approval of other PDP recommendations: 50% of each House plus 1 Councilor from 3 out of 4 Stakeholder Groups in favor) Taking this action is within the GNSO’s remit as indicated in section 11.1 of the ICANN Bylaws, where it states that the GNSO is “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.” Item 8: COUNCIL UPDATE – Temporary Specification for Registration Data Expedited Policy Development Process - Recurring Update (15 minutes) On 19 July 2018, the GNSO Council resolved<https://gnso.icann.org/en/council/resolutions#20180719-2> to initiate the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data and adopt the EPDP Team Charter<https://gnso.icann.org/sites/default/files/file/field-file-attach/temp-spec…>. Given the challenging timeline for the EPDP and the GNSO Council’s role in managing the PDP process, the Council has agreed that including a recurring update on the EPDP for each Council meeting is prudent. Here, the Council will receive an update from the GNSO Council liaison to the EPDP. 8.1 – Update (Rafik Dammak, GNSO Council liaison to the EPDP and EPDP vice-chair) 8.2 – Council discussion 8.3 – Next steps Item 9: ANY OTHER BUSINESS (10 minutes) 9.1 - 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. 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 11:00 UTC Local time between March and October Summer in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PDT) UTC-7 04:00 San José, Costa Rica (CST) UTC-6 05:00 New York/Washington DC, USA (EDT) UTC-4 07:00 Buenos Aires, Argentina (ART) UTC-3 08:00 Rio de Janeiro, Brazil (BRST) UTC-3 08:00 London, United Kingdom (GMT) UTC+1 12:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 12:00 Paris, France (CEST) UTC+2 13:00 Islamabad, Pakistan (PKT) UTC+5 16:00 Singapore (SGT) UTC+8 19:00 Tokyo, Japan (JST) UTC+9 20:00 Sydney/Hobart, Australia (AEST) 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/y82s88vu<https://tinyurl.com/y9663p2o> Final GNSO Council Agenda 24 October 2018 - Part II (Admin) 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/1iIhB 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: 13:15 UTC: https://tinyurl.com/ycvf33wr GNSO Council Meeting Audio Cast GNSO Council Meeting remote participation details: https://63.schedule.icann.org/meetings/901655 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. Seating of the 2018 / 2019 Council (20 mins) 1.1 - Roll Call 1.2 - Statements of Interest Maxim Alzoba - SOI<https://community.icann.org/display/gnsosoi/Maxim+Alzoba+SOI> Registries Stakeholder Group Elsa Saade - SOI<https://community.icann.org/display/gnsosoi/Elsa+Saade+SOI> Non-Commercial Stakeholder Group Flip Petillion: SOI<https://community.icann.org/display/gnsosoi/Flip+Petillion+SOI> Intellectual Property Constituency Scott McCormick: SOI<https://community.icann.org/x/fA28BQ> Commercial and Business Users Constituency 1.3 - Review / Amend Agenda Item 2. Election of the Chair (30 mins) Two nomination were received for this position, Rafik Dammak from the Non-Contracted Parties House and Keith Drazek from the Contract Parties House. The GNSO reviewed the candidate statements<https://gnso.icann.org/en/council/elections> and held a question & answer session with both candidates on 21 October 2018. Here the GNSO Council will proceed to hold the election for its Chair for 2019-2020, according to the GNSO Operating Procedures (note Section 2.2 of the GNSO Operating Procedures on Officer Elections: Chair and Vice-Chairs (see Appendix 1 below)). Item 3: COUNCIL DISCUSSION - GNSO Empowered Community Roles and Responsibilities – GNSO Operating Procedures Templates and Guideline Development 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 2018, staff has outlined in a 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. In regards to the proposed next steps in the table, staff has developed first drafts of templates and possible guidelines for the Council’s consideration, but the Council could also consider setting up a dedicated committee / drafting team to take on this task and/or collaborate with staff, noting that any proposed templates and/or guidelines would still need to come back to the GNSO Council for approval. Here, the Council will discuss next steps and an action plan. 3.1 – Update (TBD) 3.2 – Council discussion 3.3 – Next steps Item 43. Any Other Business (010 min) None Appendix 1: Excerpt from GNSO Operating Procedures (Section 2.2) 2.2 https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf Officer Elections: Chair and Vice-Chairs The GNSO Council shall select the GNSO Chair and two Vice-Chairs as follows: 1. The GNSO Chair shall be elected by a 60 percent vote of each house. 2. Each house will be allowed to nominate one candidate for GNSO Council Chair. Each house is responsible for determining how to nominate its candidate. A candidate for GNSO Council Chair does not need to be a member of a house, but must be a current or incoming member of the GNSO Council. Should a Chair be elected from outside of the houses that Chair will be a non-voting Chair. a. All ballots will include the “none of the above” option. In the event that a 60 percent vote of each house selects the “none of the above” option, each house will commence a new nomination period of not longer than 15 days. An election for the new nominees will be scheduled for no sooner than 30 days after the unsuccessful vote. b. In the case of a tie for the most votes between the two candidates, or between a candidate and “none of above,” a second election will be held no sooner than 30 days. The candidates shall remain the same for this second election. In the case this second election also results in a tie, each house will commence a new nomination period of not longer than 15 days. An election for the new nominees will be rescheduled for no sooner than 30 days after the unsuccessful vote. c. The leading candidate will be defined as the one with the highest score. The score is calculated by adding together the voting percentages attained from each house. The highest percentage attainable in each house is 100. Thus, the maximum score a candidate can achieve is 200 as a result of attaining 100 percent of the votes from the contracted party house and 100 percent from the non-contracted party house (100 percent + 100 percent = score of 200). In case neither candidate reaches the 60 percent of each house threshold, a second ballot will be held between the leading candidate and “none of the above.” d. In case neither candidate reaches the 60 percent of each house threshold and the candidates do not tie, a second runoff ballot will be held between the leading candidate and “none of the above.” e. If the single candidate does not reach the 60 percent of each house threshold in the runoff ballot, then each house will commence a new nomination period of not longer than 15 days. An election for the new nominees will be rescheduled for no sooner than 30 days after the unsuccessful runoff ballot. 1. Each house shall select a Council Vice-Chair from within its respective house. 2. A Chair may not be a member of the same Stakeholder Group of either of the Vice-Chairs. 3. The Chair and Vice-Chairs shall retain their votes (if any) in their respective houses (if any). 4. In the event that the GNSO Council has not elected a GNSO Council Chair by the end of the previous Chair’s term, the Vice-Chairs will serve as Interim GNSO Co- Chairs to jointly oversee the new Chair election and conduct Council business until a successful election can be held. In the event that one or both Vice-Chairs’ terms ends concurrently with the term of the previous Chair, the procedures described in Section 2.2.1 below shall apply. 5. The Council shall inform the Board and the Community appropriately and post the election results on the GNSO website within 2 business days following each election and runoff ballot, whether successful or unsuccessful. Appendix 2: GNSO Council Voting Thresholds (ICANN Bylaws,<https://www.icann.org/resources/pages/governance/bylaws-en/#article11> Article 11, Section 3) (i) Except as otherwise specified in these Bylaws, Annex A, Annex A-1 or Annex A-2 hereto, or the GNSO Operating Procedures, the default threshold to pass a GNSO Council motion or other voting action requires a simple majority vote of each House. The voting thresholds described below shall apply to the following GNSO actions: (i) Create an Issues Report: requires an affirmative vote of more than one-fourth (1/4) vote of each House or majority of one House. (ii) Initiate a Policy Development Process ("PDP") Within Scope (as described in Annex A): requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. (iii) Initiate a PDP Not Within Scope: requires an affirmative vote of GNSO Supermajority (as defined in Section 11.3(i)(xix)). (iv) Approve a PDP Team Charter for a PDP Within Scope: requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. (v) Approve a PDP Team Charter for a PDP Not Within Scope: requires an affirmative vote of a GNSO Supermajority. (vi) Changes to an Approved PDP Team Charter: For any PDP Team Charter approved under (iv) or (v) above, the GNSO Council may approve an amendment to the Charter through a simple majority vote of each House. (vii) Terminate a PDP: Once initiated, and prior to the publication of a Final Report, the GNSO Council may terminate a PDP only for significant cause, upon a motion that passes with a GNSO Supermajority Vote in favor of termination. (viii) Approve a PDP Recommendation Without a GNSO Supermajority: requires an affirmative vote of a majority of each House and further requires that one GNSO Council member representative of at least 3 of the 4 Stakeholder Groups supports the Recommendation. (ix) Approve a PDP Recommendation With a GNSO Supermajority: requires an affirmative vote of a GNSO Supermajority, (x) Approve a PDP Recommendation Imposing New Obligations on Certain Contracting Parties: where an ICANN contract provision specifies that "a two-thirds vote of the council" demonstrates the presence of a consensus, the GNSO Supermajority vote threshold will have to be met or exceeded. (xi) Modification of Approved PDP Recommendation: Prior to Final Approval by the Board, an Approved PDP Recommendation may be modified or amended by the GNSO Council with a GNSO Supermajority vote. (xii) Initiation of an Expedited Policy Development Process ("EPDP"): requires an affirmative vote of a GNSO Supermajority. (xiii) Approve an EPDP Team Charter: requires an affirmative vote of a GNSO Supermajority. (xiv) Approval of EPDP Recommendations: requires an affirmative vote of a GNSO Supermajority. (xv) Approve an EPDP Recommendation Imposing New Obligations on Certain Contracting Parties: where an ICANN contract provision specifies that "a two-thirds vote of the council" demonstrates the presence of a consensus, the GNSO Supermajority vote threshold will have to be met or exceeded. (xvi) Initiation of a GNSO Guidance Process ("GGP"): requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. (xvii) Rejection of Initiation of a GGP Requested by the Board: requires an affirmative vote of a GNSO Supermajority. (xviii) Approval of GGP Recommendations: requires an affirmative vote of a GNSO Supermajority. (xix) A "GNSO Supermajority" shall mean: (A) two-thirds (2/3) of the Council members of each House, or (B) three-fourths (3/4) of the Council members of one House and a majority of the Council members of the other House. https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf Appendix 1 GNSO Council Voting Results table Absentee Voting Procedures https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf 4.4 Absentee Voting 4.1.1 Applicability Absentee voting is permitted for the following limited number of Council motions or measures. 1. Initiate a Policy Development Process (PDP); 2. Approve a PDP recommendation; 3. Recommend amendments to the GNSO Operating Procedures (GOP) or ICANN Bylaws; 4. Fill a Council position open for election. 4.1.2 Absentee ballots, when permitted, must be submitted within the announced time limit, which shall be 72 hours from the meeting’s adjournment. In exceptional circumstances, announced at the time of the vote, the Chair may reduce this time to 24 hours or extend the time to 7 calendar days, provided such amendment is verbally confirmed by all Vice-Chairs present. 4.1.3 The GNSO Secretariat will administer, record, and tabulate absentee votes according to these procedures and will provide reasonable means for transmitting and authenticating absentee ballots, which could include voting by telephone, e- mail, web-based interface, or other technologies as may become available. 4.1.4 Absentee balloting does not affect quorum requirements.

1 0

PLEASE READ & RSVP: GNSO Council drinks & tapas - Saturday 20 October 2018 from 19:00 - 20:30 Ultramarinos
by Nathalie Peregrine Oct. 16, 2018

Oct. 16, 2018

Dear seated and incoming councilors, Keith Drazek has very kindly offered to arrange the informal Council drinks and tapas on Saturday 20 October 2018 from 19:00 to 20:30 in Barcelona which will allow you to join other events afterwards. We’ll be having drinks and tapas at Ultramarinos<http://www.ultramarinosbarcelona.com/> (Rambla dels Caputxins, 31, 08002 Barcelona). We will be served an assortment of tapas with wine, there will also be an open bar serving beer and soft drinks for the duration. We have a private room booked for the event with a fixed end time to allow for an early night, or time to join a second social event. Please ensure to leave the Convention Centre immediately after meetings’ end to make the most of the event. The restaurant is a 15 - 20 min car ride from the convention centre. We advise cab sharing as Uber is not currently active in Barcelona. Cabs do tend to take credit cards, please ensure you check with the driver beforehand. It is also worthwhile asking if they take Amex, as not all cabs do. Please confirm attendance before Wednesday 17 October EOB UTC: cancellations and additional bookings will not be available after that time. Cancellations will be charged to Keith Drazek if over the deadline. Price is 35 euros a head, payment details to follow. Thank you so much. Safe travels, Nathalie Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <mailto:nathalie.peregrine@icann.org > Skype: nathalie.peregrine.icann

2 1

PDP 3.0 motion
by Rafik Dammak Oct. 16, 2018

Oct. 16, 2018

Hi all, Please find attached the Motion to recommend the implementation of certain improvements to enhance the efficiency and effectiveness of the GNSO Policy Development Process (PDP 3.0) Best Regards, Rafik

3 2

Reminder: PLEASE READ & RSVP: GNSO Council drinks & tapas - Saturday 20 October 2018 from 19:00 - 20:30 Ultramarinos
by Nathalie Peregrine Oct. 16, 2018

Oct. 16, 2018

Dear seated and incoming councilors, Keith Drazek has very kindly offered to arrange the informal Council drinks and tapas on Saturday 20 October 2018 from 19:00 to 20:30 in Barcelona which will allow you to join other events afterwards. We’ll be having drinks and tapas at Ultramarinos [ultramarinosbarcelona.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ultramarinosbarcelo…> (Rambla dels Caputxins, 31, 08002 Barcelona). We will be served an assortment of tapas with wine, there will also be an open bar serving beer and soft drinks for the duration. We have a private room booked for the event with a fixed end time to allow for an early night, or time to join a second social event. Please ensure to leave the Convention Centre immediately after meetings’ end to make the most of the event. The restaurant is a 15 - 20 min car ride from the convention centre. We advise cab sharing as Uber is not currently active in Barcelona. Cabs do tend to take credit cards, please ensure you check with the driver beforehand. It is also worthwhile asking if they take Amex, as not all cabs do. Please confirm attendance before Wednesday 17 October EOB UTC: cancellations and additional bookings will not be available after that time. Cancellations will be charged to Keith Drazek if over the deadline. Price is 35 euros a head, payment details to follow. Thank you so much. Safe travels, Nathalie Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <mailto:nathalie.peregrine@icann.org > Skype: nathalie.peregrine.icann

1 0

Re: [council] Motion - Reappointment of GNSO Council Liaison to the Governmental Advisory Committee
by Michele Neylon - Blacknight Oct. 15, 2018

Oct. 15, 2018

Donna Happy to second this motion if needed. Regards Michele -- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains https://www.blacknight.com/ https://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 "Austin, Donna via council" <council(a)gnso.icann.org> Reply-To: "Austin, Donna" <Donna.Austin(a)team.neustar> Date: Sunday 14 October 2018 at 18:35 To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [council] Motion - Reappointment of GNSO Council Liaison to the Governmental Advisory Committee Dear Councilors Attached is a motion for consideration at our next Council meeting regarding the reappointment of Julf as the Council Liaison to the GAC. Regards Donna

1 0

Draft agenda: GNSO Working session Sunday 21 October 2018
by Nathalie Peregrine Oct. 15, 2018

Oct. 15, 2018

Dear councilors, Please find the draft agenda for the GNSO Working session on Sunday 21 October 2018 in room 115 (GNSO room) posted here: https://community.icann.org/x/lhVpBQ Please note the new start time of 08:30 CET (06:30 UTC). 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

Fwd: FOR CIRCULATION TO COUNCIL: Recommendations Report on Reconvened Red Cross PDP
by Heather Forrest Oct. 14, 2018

Oct. 14, 2018

Dear Council colleagues, Please find attached for consideration in our October meeting a proposed GNSO COuncil Recommendations Report to the ICANN Board on the Reconvened PDP on Red Cross names, based on the template for such reports. This follows our unanimous approval of the reconvened WG's recommendations last month. Best wishes, Heather

1 0