April 2019 - council - lists.icann.org

Timeline - GNSO Drafting Team to Further Develop Guidelines and Principles for the GNSO’s Roles and Obligations as a Decisional Participant in the Empowered Community
by Rafik Dammak 10 Apr '19

10 Apr '19

Hi all, Heather as chair of the GNSO Drafting Team to Further Develop Guidelines and Principles for the GNSO’s Roles and Obligations as a Decisional Participant shared the attached timeline in order to inform the GNSO Council the timeline for completing the work. Best Regards. Rafik

1 0

EPDP Phase 2 Chair Update
by Drazek, Keith 10 Apr '19

10 Apr '19

Dear Mr. LaHatte, The GNSO Council Leadership Team and Standing Selection Committee (SSC) Leadership Team have concluded our review and assessment of applications received for the EPDP Phase 2 Chair role and we have elected to recommend Mr. Janis Karklins for the position. The GNSO Council will next meet on 18 April 2019 to vote on this recommendation. I would like to sincerely thank you for your willingness to volunteer and serve in the ICANN community. We are genuinely grateful for your engagement in ICANN and in the GNSO -- past, present and future. Please contact me directly if you have any questions. Best regards, Keith Drazek, GNSO Chair

1 0

EPDP Phase 2 Chair Update
by Drazek, Keith 10 Apr '19

10 Apr '19

Hi all, This is an important update concerning the EPDP Phase 2 Chair Expressions of Interest (EOI) process. As you know, the extended call for EOIs closed on Monday, 8 April. We received a total of two EOIs, one from Chris LaHatte, former ICANN Ombudsman, and another from Janis Karklins, former GAC Chair and current Latvian Ambassador to the United Nations in Geneva. The GNSO Council Leadership Team and the Standing Selection Committee (SSC) Leadership Team met on Tuesday after conducting individual scoring assessments for each candidate. After approximately one hour of discussion and deliberation, we agreed to unanimously recommend that the Council appoint Janis Karklins as EPDP Phase 2 Chair. We are confident in Janis' ability and commitment to perform the EPDP Phase 2 Chair duties in a neutral manner and consistent with the GNSO PDP Operating Procedures. We are also confident Janis will ensure the work is performed efficiently, effectively, and in a timely manner. Therefore, we will now update the 18 April 2019 GNSO Council agenda to reflect this recommendation and to add Janis Karklins' name to the Consent Agenda item on this topic. If anyone has questions, please raise them prior to the GNSO Council meeting. We thank both candidates for their willingness to serve. Regards, Keith Drazek GNSO Chair (on behalf of the GNSO Council Leadership Team and SSC Leadership Team)

1 1

Final Proposed Agenda GNSO Council Meeting - 18 April 2019 at 21:00 UTC
by Terri Agnew 09 Apr '19

09 Apr '19

Dear all, Please below find the final proposed agenda for the GNSO Council Meeting on 18 April 2019 at 21:00 UTC. Final GNSO Council Agenda 18 April 2019 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/uhBIBg 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: 21:00 UTC: https://tinyurl.com/y6jqgg5p 14:00 Los Angeles; 17:00 Washington; 22:00 London; (Friday) 02:00 Islamabad; 06:00 Tokyo; 07:00 Melbourne GNSO Council Meeting Audio Cast Listen in browser: <https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> http://stream.icann.org:8000/stream01<https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> Listen in application such as iTunes: <https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> http://stream.icann.org:8000/stream01.m3u<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 - Note the status of minutes for the previous Council meetings per the GNSO Operating Procedures: Minutes<https://gnso.icann.org/en/meetings/minutes-special-council-04mar19-en.pdf> of the GNSO Council meeting on the 4th March were posted on the 18 March 2019 Minutes<https://gnso.icann.org/sites/default/files/file/field-file-attach/minutes-c…> of the GNSO Council meeting on the 13th March were posted on the 30 March 2019 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 (15 minutes) * Motion<https://community.icann.org/display/gnsocouncilmeetings/Motions+18+April+20…> to adopt the GNSO Council response to the GAC Communique<https://gac.icann.org/contentMigrated/icann64-kobe-communique> * Confirmation of the Recommendations Report to the ICANN Board regarding adoption of the Final Report from the Expedited PDP on the Temporary Specification for gTLD Registration Data PDP WG, Phase 1. * Approval of the appointment of [NAME] as Chair for the Expedited Policy Development Process Team on the Temporary Specification for gTLD Registration Data. * Approval of the suggested amendments to the GNSO’s Fellowship Selection criteria. Item 4: COUNCIL VOTE – IGO-INGO Access to Curative Rights Protection Mechanisms (20 minutes) The IGO-INGO Access to Curative Rights Protection Mechanisms PDP WG worked to resolve a final recommendation relating to IGO jurisdictional immunity and registrants’ rights to file court proceedings. The WG reached agreement on a single recommendation amongst several options for their final recommendation on this area, as well as for all other recommendations. The WG Chair proposed his determination of consensus levels for all recommendations, which the WG has affirmed. On 27 June 2018, the GNSO Council passed a <https://gnso.icann.org/en/council/resolutions#201806> resolution<https://gnso.icann.org/en/council/resolutions#201806>, thanking the PDP WG for its efforts and requesting that it submit its <https://gnso.icann.org/sites/default/files/file/field-file-attach/igo-ingo-…> Final Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/igo-ingo-…> 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 <https://gnso.icann.org/sites/default/files/file/field-file-attach/igo-ingo-…> Final Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/igo-ingo-…> to the GNSO Council for its consideration, which contains five consensus recommendations, along with three Working Group member minority statements, documenting their disagreement either with one or more of the final recommendations or other parts of the Final Report. On its 19 July Council meeting, the Council resolved<https://gnso.icann.org/en/council/resolutions#201806> to accept the Final Report from the IGO-INGO Access to Curative Rights Mechanisms PDP Working Group, where it noted that it would consider the topic of curative rights protections for IGOs in the broader context of the 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? A motion to consider the Final Report was originally submitted on the 24 October 2018 Council meeting agenda but was withdrawn due to concerns around both the process followed by the PDP, as well as the substance of the PDP WG’s recommendations. Council leadership and staff have developed a summary document (Summary Paper<https://gnso.icann.org/en/drafts/igo-ingo-crp-access-final-28nov18-en.pdf> and Slide Deck<https://gnso.icann.org/en/drafts/igo-ingo-crp-procedural-options-council-29…>) that lists issues raised by Councilors, options available, and potential considerations. During the November meeting, the Council considered a set of available options and briefly discussed possible next steps. On 20 December 2018, Council leadership circulated a proposal<https://mm.icann.org/pipermail/council/2018-December/022153.html> for next steps. Council leadership has since sent a reply<https://gnso.icann.org/en/correspondence/gnso-council-to-ismail-14jan19-en.…> to the GAC, in response to a letter received during ICANN63. On the 24 January 2018 Council meeting, the Council discussed the proposal prepared by Council leadership. On 14 February 2019, the Council further discussed next steps and agreed to consult with the Governmental Advisory Committee, both before and at ICANN64. The GNSO Council and GAC had productive discussions, where the Council discussed procedural options that it is considering. The GAC’s Kobe Communique<https://gac.icann.org/contentMigrated/icann64-kobe-communique> noted the GAC’s “fruitful exchanges with the GNSO Council regarding the possibility of restarting the PDP on curative protections, under conditions amenable to all interested parties, including IGOs and interested GAC members, with a view to achieving mutually acceptable results [with] a timeline with a targeted date associated with such a course of action.” Based on the Council discussions and consultation with the GAC, the Council believes that it has thoroughly considered the available options. Here, the Council will vote to approve the set of actions as detailed in the relevant motion<https://community.icann.org/display/gnsocouncilmeetings/Motions+18+April+20…>. 4.1 – Presentation of motion<https://community.icann.org/display/gnsocouncilmeetings/Motions+18+April+20…> (Council Leadership) 4.2 – Council discussion 4.3 – Council vote (voting threshold: simple majority for recommendations 1-4) 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: GNSO Policy Development Process of the ICANN Bylaws. Item 5: COUNCIL DISCUSSION – Managing IDN Variants TLDs (15 minutes) The ICANN Board resolved in 2010 that IDN variant TLDs will not be delegated until relevant work is completed and directed ICANN org to develop a report identifying what needs to be done with the evaluation, possible delegation, allocation and operation of generic top-level domains (gTLDs) containing variant characters IDNs, in order to facilitate the development of workable approaches to the deployment of gTLDs containing variant characters IDNs. Based on analysis, ICANN org and the community identified two gaps to address: 1) that there is no definition of IDN variant TLDs, and; 2) that there is no IDN variant TLD management mechanism. The Procedure to Develop and Maintain the Label Generation Rules for the Root Zone in Respect of IDNA Labels<https://www.icann.org/en/system/files/files/lgr-procedure-20mar13-en.pdf> (RZ-LGR Procedure) has been developed by the community to define the IDN variant TLDs and, following the Board resolution<https://www.icann.org/resources/board-material/resolutions-2013-04-11-en#2.a> in 2013 which approved the RZ-LGR Procedure, has been implemented to incrementally develop the Root Zone Label Generation Rules to address the first gap. ICANN org has developed the Recommendations for Managing IDN Variant TLDs<https://www.icann.org/public-comments/managing-idn-variant-tlds-2018-07-25-…> (the Variant TLD Recommendations), a collection of six documents finalized after incorporating the public comment feedback and published them as mechanisms for addressing the second gap identified by the community in the implementation of IDN variant TLDs. On 14 March 2019, the ICANN Board resolved<https://www.icann.org/resources/board-material/prelim-report-2019-03-14-en#…>: The Board approves the Variant TLD Recommendations and requests that the ccNSO and GNSO take into account the Variant TLD Recommendations while developing their respective policies to define and manage the IDN variant TLDs for the current TLDs as well as for future TLD applications. The Board requests that the ccNSO and GNSO keep each other informed of the progress in developing the relevant details of their policies and procedures to ensure a consistent solution, based on the Variant TLD Recommendations, is developed for IDN variant ccTLDs and IDN variant gTLDs. Here, the Council will receive an update and consult with Sarmad Hussain, managing director of ICANN’s IDN Program, to better understand its responsibilities as dispensed by the ICANN Board. 5.1 – Introduction of topic (Council leadership) 5.2 – Update and council discussion (Sarmad Hussain, ICANN staff) 5.3 – Next steps Item 6: COUNCIL UPDATE – Status of the EPDP on the Temporary Specification for gTLD Registration Data Phase 1 Informal Implementation Review Team (15 minutes) On 11 May 2018, ICANN released the <https://www.icann.org/resources/pages/approved-with-specs-2013-09-17-en#con…> 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 17 May 2017, the ICANN Board <https://www.icann.org/resources/board-material/resolutions-2018-05-17-en> approved<https://www.icann.org/resources/board-material/resolutions-2018-05-17-en> the proposed <https://www.icann.org/resources/pages/gtld-registration-data-specs-en> 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). The EPDP Team held its first meeting on 1 August 2018 and on 21 November 2018, the EPDP published its Initial Report for public comment<https://www.icann.org/public-comments/epdp-gtld-registration-data-specs-ini…>. After taking into account public comment received, the EPDP Team worked to deliver its Final Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-gtld…> to the GNSO Council for its consideration on 20 February 2019. Due to the unique circumstances concerning the deadline for implementation, and in order to minimize the transition period, the EPDP Leadership and Team informally recommended that discussion around implementation deliverables be initiated immediately. This preliminary work will inform the deliberations of the formal Implementation Recommendation Team upon Board approval of the Policy Recommendations. The EPDP team Final Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-gtld…> was adopted by the GNSO Council on 2 March 2019 and resolved to recommend that implementation efforts begin in an informal fashion. Here, the Council will receive a status update on the progress of the informal implementation efforts. 6.1 – Update (Dennis Chang, ICANN staff) 6.2 – Council discussion 6.3 – Next steps Item 7: COUNCIL DISCUSSION - Updated Timeline for the PDP on the Review of All Rights Protection Mechanisms in All gTLDS (15 minutes) At the GNSO Council’s working session at ICANN64, on 10 March 2019, the Council welcomed updates from the chairs of the various GNSO PDPs underway, including the Review of All Rights Protection Mechanisms in All gTLDS (RPMs). The Council, amongst other questions, asked the Co-chairs about the likelihood of the RPMs PDP completing its work by February of 2020. The responses from the three co-chairs expressed varying levels of confidence in meeting that deadline and it was agreed that an updated timeline for the RPMs PDP would help the Council better carry out its role as manager of the PDP. Here, the Council will review and discuss the updated timeline. 7.1 – Introduction of topic (Paul McGrady, GNSO Council Liaison to the PDP) 7.2 – Council discussion 7.3 – Next steps Item 8: ANY OTHER BUSINESS (10 minutes) 8.1 - Review of status assignment of the GNSO Project list. 8.2 - Reminder for funded travelers to book their travel for ICANN65 ________________________________ 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 21:00 UTC Local time between March and October Summer in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PDT) UTC-7 14:00 San José, Costa Rica (CST) UTC-6 15:00 New York/Washington DC, USA (EDT) UTC-4 17:00 Buenos Aires, Argentina (ART) UTC-3 18:00 Rio de Janeiro, Brazil (BRT) UTC-3 18:00 London, United Kingdom (GMT) UTC+0 22:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 22:00 Paris, France (CET) UTC+2 23:00 Moscow, Russia (MSK) UTC +3 (+1 day) 00:00 Islamabad, Pakistan (PKT) UTC+5 (+1 day) 02:00 Singapore (SGT) UTC+8 (+1 day) 05:00 Tokyo, Japan (JST) UTC+9 (+1 day) 06:00 Melbourne, Australia (AEDT) UTC+11 07:00 ---------------------------------------------------------------------------- DST starts/ends on Sunday 27 of October 2019, 2:00 or 3:00 local time (with exceptions) for EU countries and on Sunday 03 of November 2019 for the US. ---------------------------------------------------------------------- For other places see http://www.timeanddate.com<http://www.timeanddate.com/> and https://tinyurl.com/y6jqgg5p

1 0

Proposed Motion on IGO-INGO Curative Rights Protections Final Report
by Drazek, Keith 09 Apr '19

09 Apr '19

Hi all, Attached is the proposed motion language for addressing the IGO-INGO CRP Final Report, which also includes rationale language in support of this course of action. The Council Leadership Team feels this is the best compromise solution to this issue. We will be happy to discuss further on our next call. In summary, we continue to recommend a vote to approve Recommendations 1-4 and to not accept Recommendation 5. We believe the best course of action is to refer Recommendation 5 to the RPM PDP WG for a re-chartered Phase 2, rather than initiating a new and separate EPDP. If Recommendations 1-4 are approved, then Recommendation 5 is to be revisited within existing Dispute Resolution Procedures, rather than creating a new one, so it appropriately belongs in the RPM PDP WG for Phase 2 work on UDRP. Please socialize this with your respective SGs and Cs so we can conduct a vote on April 18. I am available to discuss this with anyone who has questions. Thanks and regards, Keith

3 2

Recommendations Report on EPDP
by Caitlin Tubergen 08 Apr '19

08 Apr '19

Dear Councilors: Attached, please find the draft GNSO Council Report to the ICANN Board on the EPDP recommendations for your consideration. Following the customary practice, this report will be added to the Council’s 18 April consent agenda, unless there are any comments or concerns with this approach. If you have any proposed edits or comments on the report, please kindly submit them by the document deadline of Monday, 8 April 2018. Thank you. Kind regards, Caitlin -- Caitlin Tubergen Policy Senior Manager - GNSO ICANN

6 11

Re: [council] Draft Motion Council Response GAC Communique
by Nathalie Peregrine 08 Apr '19

08 Apr '19

Dear Michele, Thank you for your email. Your motion has been posted on the GNSO Council wiki space: https://community.icann.org/display/gnsocouncilmeetings/Motions+18+April+20… Kind regards, Nathalie On 4/7/19, 2:41 PM, "council on behalf of Michele Neylon - Blacknight" <council-bounces(a)gnso.icann.org on behalf of michele(a)blacknight.com> wrote: All Please find attached a draft motion on the Council response to the Kobe GAC Communique. Regards Michele -- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains https://urldefense.proofpoint.com/v2/url?u=https-3A__www.blacknight.com&d=D… https://urldefense.proofpoint.com/v2/url?u=https-3A__blacknight.blog&d=DwIG… / https://urldefense.proofpoint.com/v2/url?u=http-3A__ceo.hosting_&d=DwIGaQ&c… Intl. +353 (0) 59 9183072 Direct Dial: +353 (0)59 9183090 ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow, R93 X265, Ireland Company No.: 370845

3 2

Letter from ICANN CEO on Next Steps for TSG, EPDP, and DPA Consultations
by Drazek, Keith 08 Apr '19

08 Apr '19

FYI: https://www.icann.org/en/system/files/correspondence/marby-to-drazek-05apr1…

1 0

Deadline today: Document and Motion deadline Monday 8 April 2019 at 23:59 UTC for GNSO Council Meeting 18 April 2019 at 21:00 UTC
by Nathalie Peregrine 08 Apr '19

08 Apr '19

Dear all, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Monday 8 April 2019 at 23:59 UTC) of the GNSO Council Meeting on Thursday 18 April 2019 at 21: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/uBBIBg Thank you very much. With kind regards, Nathalie

1 0

Draft Motion Council Response GAC Communique
by Michele Neylon - Blacknight 07 Apr '19

07 Apr '19

All Please find attached a draft motion on the Council response to the Kobe GAC Communique. Regards Michele -- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains https://www.blacknight.com https://blacknight.blog / http://ceo.hosting/ Intl. +353 (0) 59 9183072 Direct Dial: +353 (0)59 9183090 ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow, R93 X265, Ireland Company No.: 370845

1 0