Dear all, Please find below the resolutions from the GNSO Council meeting on Thursday 20 May 2021 which will be posted shortly on the GNSO resolutions<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_counc...> page. 20210520-1 CONSENT AGENDA * Appointment of the GNSO Council liaison to the System for Standardized Access/Disclosure Operational Design Phase - Janis Karklins Vote results<https://gnso.icann.org/sites/default/files/policy/2021/presentation/gnso-cou...> 20210520 – 2 Adoption of the GNSO Review of the GAC ICANN70 Virtual Community Forum Communiqué for submission to the ICANN Board Whereas, 1. The Governmental Advisory Committee advises the ICANN Board on issues of public policy, and especially where there may be an interaction between ICANN's activities or policies and national laws or international agreements. It usually does so as part of a Communiqué, which is published towards the end of every ICANN meeting. 2. The GNSO is responsible for developing and recommending to the ICANN Board substantive policies relating to generic top-level domains. 3. The GNSO has expressed a desire to provide feedback to the ICANN Board on issues in the GAC Communiqué as these relate to generic top-level domains to inform the ICANN Board as well as the broader community of past, present or future gTLD policy activities that may directly or indirectly relate to advice provided by the GAC. 4. The GNSO hopes that the input provided through its review of the GAC Communiqué will further enhance the co-ordination and promote the sharing of information on gTLD related policy activities between the GAC, Board and the GNSO. Resolved, 1. The GNSO Council adopts the GNSO Review of the ICANN70 Virtual Community Forum GAC Communiqué<https://gac.icann.org/contentMigrated/icann70-gac-communiqu> and requests that the GNSO Council Chair communicate the GNSO Review of the ICANN70 Virtual Community Forum GAC Communiqué to the ICANN Board. 2. The GNSO Council requests that the GNSO Council Chair also informs the GAC Chair of the communication between the GNSO Council and the ICANN Board. Vote results<https://gnso.icann.org/sites/default/files/policy/2021/presentation/gnso-cou...> 20210520 – 3 Motion to initiate the Expedited Policy Development Process on Internationalized Domain Names and adoption of the EPDP on IDNs Charter Whereas, 1. On 14 March 2019, the ICANN Board approved a set of recommendations<https://www.icann.org/resources/pages/idn-variant-tld-implementation-2018-07...> developed by ICANN org on how to allocate Internationalized Domain Name (IDN) variant TLD labels. The ICANN Board requested that the GNSO and ccNSO take into account those IDN variant TLD recommendations while developing their respective policies to define and manage IDN variant TLDs for the current TLDs and future TLD applications, while keeping each other informed of the progress in developing the relevant details of their policies and procedures to ensure a consistent solution for IDN variant gTLDs and IDN variant ccTLDs. 2. On 26 June 2019, the GNSO Council established a Scoping Team<https://community.icann.org/display/IDNST> to develop recommendations for the GNSO Council’s consideration on how to address the IDN variant TLD recommendations, as well as issues in the Final Proposed Draft version 4.0 of Internationalized Domain Name ("IDN") Implementation Guidelines<https://www.icann.org/news/announcement-2018-05-10-en> (“IDN Guidelines v. 4.0”), for which the ICANN Board had agreed<https://www.icann.org/en/system/files/correspondence/chalaby-to-drazek-04jun...> to the GNSO Council request [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/f...> to defer its adoption. The Scoping Team met between 15 August 2019 and 12 December 2019. 3. On 23 January 2020, the GNSO Council discussed the Final Report [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/f...> from the Scoping Team, which suggested tackling IDN related issues in two tracks: Operational Track and Policy Track. The Policy Track would be tasked to deliberate on: i) the definition and management of IDN variant TLDs, and ii) the change process of the IDN Guidelines and any policy issues related to the IDN Guidelines v. 4.0 identified by the Operational Track Team (consisted of members in the GNSO Contracted Parties House) and agreed upon by the IDN Guidelines Working Group. 4. On 26 January 2020, the ICANN Board approved the Recommendations for the Technical Utilization of the RZ-LGR<https://www.icann.org/en/system/files/files/rz-lgr-technical-utilization-rec...> on how to employ the RZ-LGR<https://www.icann.org/resources/pages/root-zone-lgr-2015-06-21-en> to determine valid IDN TLDs and their variant labels. The ICANN Board requested that the GNSO and ccNSO take into account those RZ-LGR Technical Utilization recommendations while developing their respective policies to define and manage IDN variant TLDs for the current TLDs and future TLD applications. 5. On 21 October 2020, the GNSO Council agreed to establish a Drafting Team<https://community.icann.org/x/CYAmCQ> to develop both a draft charter and an Initiation Request for an EPDP on IDNs. The GNSO Council agreed with the Scoping Team’s suggestion that an Issue Report is likely not needed in order to initiate the Policy Track work, and an EPDP is the desired approach. The Drafting Team met between 8 December 2020 and 4 May 2021. 6. On 10 May 2021, the Drafting Team submitted the draft EPDP charter<https://gnso.icann.org/sites/default/files/file/field-file-attach/idns-epdp-...> and the Initiation Request<https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-initi...> for the GNSO Council’s consideration. 7. On 20 May 2021, the Drafting Team Chair provided a briefing to the GNSO Council on the content of the draft charter prior to the Council vote to initiate the EPDP and adopt the charter. RESOLVED, 1. The GNSO Council hereby approves the Initiation Request<https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-initi...> for the EPDP on IDNs and as such initiates the EPDP. 2. The GNSO Council approves the Charter<https://gnso.icann.org/sites/default/files/file/field-file-attach/idns-epdp-...> of the EPDP on IDNs. 3. The GNSO Council directs staff to: (a) communicate the results of this motion to the GNSO SG/Cs as well as ICANN SO/ACs and invite them to identify Members for the working group following the working group composition described in the Charter; (b) communicate the results of this motion to the ICANN Org GDS Team and invite them to identify at least one (1) staff liaison for the working group; (c) launch a call for expressions of interest seeking interested candidates to Chair the EPDP on IDNs; and (d) solicit candidates for the GNSO Council liaison to the EPDP on IDNs. Vote results<https://gnso.icann.org/sites/default/files/policy/2021/presentation/gnso-cou...> Thank you, Kind regards, Nathalie