Dear all, Please find below the resolutions and council vote from the GNSO Council at its meeting on Wednesday 6 November 2019 which will be posted on the GNSO resolutions<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_counc...> page. 20191106 – 1 Consent Agenda Reappointment of GNSO Council Liaison to the Governmental Advisory Committee Whereas: 1. As part of the discussions within ICANN between the GNSO and GAC on how to facilitate early engagement of the GAC in GNSO policy development activities, the option of appointing a GNSO liaison to the GAC was initially piloted in FY15 and F16, and subsequently confirmed by the GNSO Council as a permanent role at the start of FY17. 2. The GNSO Council appointed Julf Helsingius to the role of GNSO Liaison to the Governmental Advisory Committee on 24 October 2018, until the end of the ICANN AGM 2019. 3. The GNSO Council has an obligation to review the role annually and reconfirm the appointment unless the review indicates otherwise and/or the Liaison has indicated that he/she is no longer available to continue in this role, in which case a new selection process will take place. 4. The GNSO Council leadership has met with Julf Helsingius to discuss his experience and to confirm that he is willing to continue in this role. 5. The GNSO Council has reviewed the annual report prepared by the GNSO Liaison to the GAC (see https://gnso.icann.org/sites/default/files/file/field-file-attach/gac-liaiso...). Resolved: 1. The GNSO Council hereby reappoints Julf Helsingius to the role of GNSO Liaison to the Governmental Advisory Committee until the end of the ICANN AGM 2020. 2. The GNSO Council leadership team will inform the GAC leadership team accordingly, and will co-ordinate with Julf Helsingius as well as the GAC leadership team and GAC Secretariat on next steps and the continued successful implementation of this role. Vote results<https://gnso.icann.org/sites/default/files/file/field-file-attach/%20gnso-co...> 20191106-1 Consent agenda Approval of new IANA Naming Function SLA: Publication of LGRs Whereas, 1. The Customer Standing Committee (CSC) and Public Technical Identifiers (PTI) recently agreed on a procedure to amend SLAs (see: https://www.icann.org/en/system/files/files/iana-naming-function-sla-amendme...). 2. Recently, the CSC and PTI have agreed to establish a set of new SLAs for the publication of the Internationalized Domain Name (IDN) tables and Label Generation Rulesets (LGRs) in the IDN Practices Repository (see https://gnso.icann.org/sites/default/files/file/field-file-attach/new-slas-p... for the SLA change request: new SLA for Publication of LGRs). 3. The GNSO Council was notified on 18 October 2019 (see https://gnso.icann.org/en/correspondence/new-slas-publication-lgr-idn-change...) that this change request is now ready for approval by the ccNSO and GNSO Councils, which is required before implementation will start. 4. The GNSO Council has reviewed the proposed SLA change request and discussed the proposed SLA change with the ccNSO Council during its joint session at ICANN66. Resolved, 1. The GNSO Council approves the SLA change request: new SLA for publication of LGRs (https://gnso.icann.org/sites/default/files/file/field-file-attach/new-slas-p...) and will inform the ccNSO accordingly. 2. The GNSO Chair will work on a joint communication with the ccNSO Council to inform the CSC that the SLA change request: new SLA for publication of LGRs has been approved and should now be implemented. Vote results<https://gnso.icann.org/sites/default/files/file/field-file-attach/%20gnso-co...> Consent agenda Council vote: Approval of Tomslin Samme-Nlar to serve as the GNSO Co-Chair for the IANA Naming Function Review. 20191106 – 3 MOTION TO APPROVE GUIDELINES & MOTION TEMPLATES FOR GNSO ROLE IN THE EMPOWERED COMMUNITY WHEREAS: 1. On 27 May 2016 the ICANN Board adopted a set of new ICANN Bylaws, as revised on 26 May 2016, that aimed to reflect changes needed to implement the IANA Stewardship Transition Proposal and such adoption is contingent on the proposed transition away of remaining United States Government oversight of ICANN. 2. Per the motion adopted on 30 June 2016, the GNSO sought volunteers for a Bylaws Implementation Drafting Team to provide the GNSO Council with recommendations for any necessary updates to the GNSO Operating Procedures, or possibly the Bylaws as they relate to the GNSO, arising as a result of the revised ICANN Bylaws that were adopted in May 2016. 3. In addition, the GNSO Council requested that the Drafting Team should determine what (if any) existing GNSO processes can be used to address any new or additional obligation, and if there are none, whether an existing process can be modified or if a new process needs to be created. 4. Following the adoption by the GNSO Council of the revised GNSO Operating Procedures resulting from the Drafting Team’s recommendations, as well as the proposed modifications to the ICANN Bylaws adopted by the ICANN Board of Directors on 13 May 2018, staff sought guidance from the GNSO Council as to how to proceed with the next steps relating to 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. 5. At ICANN63 in October 2018 the GNSO Council agreed that a Call for Volunteers should be issued to reconstitute the Drafting Team to develop guidance and principles for the GNSO to complete a particular action(s) that fall within the GNSO’s existing processes and procedures, but where additional details and steps are deemed to be helpful, relating to participation of the GNSO within the Empowered Community. 6. In January 2019, the Drafting Team was established to develop guidelines, including any recommendations for changes to GNSO Operating Procedures if applicable, that clarify additional details or steps related to a particular action to be completed by the GNSO that falls within its existing process or procedure. These guidelines are meant to help the GNSO effectively participate as a Decision Participant in the Empowered Community in accordance with the post-transition ICANN Bylaws. 7. For consideration by the GNSO Council at its meetings on 24 October 2019 and 06 November 2019, the Drafting Team provided the following guidelines and motion templates 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: Approval Action Community Forum & Decision Whether to Approve an Approval Action<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_documen...> Petition Process for Specific Actions & Rejection Action Community Forum<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_documen...> Nominating Committee Director Removal Process<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_documen...> SO/AC Director Removal Process<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_documen...> Board Recall Process<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_documen...> Independent Review Process (IRP) for Covered ICANN Actions & Community IRP<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_documen...> Guidelines for GNSO-ccNSO Joint Consultation on Initiation of a Special IFR<https://docs.google.com/document/d/1NnaaoWKJWUu0Cw3pphuvT0wycmMIXhQmYyy0daPm...> Section 18.12 Special IANA Function Reviews (IFRs) - Guideline for GNSO Internal Review Process<https://docs.google.com/document/d/1A05Mo8mvL4BxdX63M7zQKAyLQwwjcUe5cIW7cWrs...> 8. The guidelines and motion templates fall within the GNSO’s existing processes and procedures, and thus do not require any changes to the GNSO Operating Procedures or its Annexes. RESOLVED: 1. The GNSO Council adopts the guidelines and motion templates 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 ICANN Bylaws. 2. The GNSO Council recognizes that as a consequence of the review by ICANN Legal, non-substantive technical updates or corrections may be provided for the guidelines and motion templates after adoption. 3. The GNSO Council instructs ICANN staff to post the guidelines and motion templates on the GNSO’s website effective immediately upon adoption after the technical update has been completed. 4. The GNSO Council requests that after an action of the GNSO as a Decisional Participant has been completed, the GNSO Council shall review the respective guidelines and motion templates relating to that action, or on an annual basis if no action is initiated for all guidelines and motions. Vote results<https://gnso.icann.org/sites/default/files/file/field-file-attach/%20gnso-co...>