Council Resolutions 2020

Last Updated: 26 May 2020

2020 | 2019-1999

January | February | May




Consent Agenda

  • Approval of the PTI SLA for the ccTLD Creation and Transfer Process
  • Reappointment of Matthew Shears to seat 14 on the ICANN Board. The NCPH has reappointed Matthew Shears for Seat 14 on the ICANN Board of Directors. This agenda item is intended to acknowledge the selection and confirm that the notification process as outlined in Section 7.25 of the ICANN Bylaws has been completed.

Vote results


Adoption of the PDP 3.0 Implementation Final Report


  1. GNSO Policy Development Process (PDP) 3.0 is a GNSO Council initiative aimed at introducing incremental improvements to enhance the efficiency and effectiveness of GNSO PDPs.
  2. On 24 October 2018, the GNSO Council resolved to adopt the GNSO PDP 3.0 Proposed Improvements Paper and provided full support for fourteen (14) improvements.
  3. In January 2019 during the GNSO Council's Strategic Planning Session (SPS), the GNSO Council decided that a Small Team of Councilors should be convened to support the implementation efforts in collaboration with the GNSO support staff. Led by Rafik Dammak, a GNSO Council Vice Chair, the Small Team met regularly between April 2019 and February 2020, with designated leads working with staff to advance the implementation of each improvement.
  4. To facilitate the GNSO Council's review, the Small Team delivered four packages to the GNSO Council in an incremental manner: Package one, on improvements 1, 2, 3, and 6 was delivered on 13 August 2019; Package two, on improvements 11, 12, 14, and 16 was delivered on 25 September 2019; Package three, on improvements 5 and 13 was delivered on 22 October 2019; and Package four, on improvements 9 and 15 was delivered on 21 November 2019.
  5. During the process of developing and finalizing the proposed implementation, the ICANN community and the ICANN org were consulted for input and suggestions via various mechanisms, including but not limited to: interviews and small group discussions, GNSO Council mailing lists and meetings, invitation to provide written input, and a public webinar on 9 December 2019.
  6. While the PDP 3.0 precedes ICANN's Evolution of the Multistakeholder Model (MSM) project, the implementation is nevertheless connected. The GNSO Council commented on the Evolution of the MSM's initial report and engaged with Brian Cute, the project's facilitator, before and during the ICANN66 meeting in Montréal. In Appendix C of ICANN's Draft FY21-25 Operating & Financial Plans and Draft FY21 Operating Plan & Budget, which documents the outcome of Phase 1 and Phase 2 of the project, three (3) out of the six (6) workstreams align with the PDP 3.0 implementation; the GNSO is being proposed to lead the "Issue A: Consensus + representation and Inclusivity" workstream.
  7. In January-February 2020, the Small Team conducted additional activities, including: 1) revising the GNSO PDP working group charter template; 2) identifying sections in the current GNSO Operating Procedures that could be revised after the GNSO Council reviews the effectiveness of PDP 3.0 implementation; and 3) discussing "Parking Lot" items that might benefit from future work.
  8. In January 2020 during GNSO Council's SPS, the GNSO Council dedicated several sessions to the discussion of PDP 3.0 and agreed on several action items as the next steps for the implementation efforts.
  9. On 10 February 2020, the Small Team completed thirteen (13) out of fourteen (14) PDP 3.0 improvements and delivered its Final Report to the GNSO Council for its consideration. The Final Report provides an overview of the PDP 3.0 implementation process and outcomes, a consolidation of all of the work products incorporating community feedback as appropriate, and suggested effective time frame for deployment of the improvements.
  10. The last remaining work product related, the Consensus Playbook, is originated from PDP 3.0 Improvement #4 and not complete. While, the Consensus Playbook is not strictly a PDP 3.0 product, it is intended to be utilized by the broader ICANN community beyond the GNSO. Its pending status should not prevent the GNSO Council adoption of the Implementation Final Report from the PDP 3.0 Small Team. Adoption of the Consensus Playbook will be voted upon by the GNSO Council at a later date.


  1. The GNSO Council hereby adopts the GNSO PDP 3.0 Implementation Final Report and instructs GNSO Support Staff to work with the GNSO Council leadership on the deployment of improvements based on the effective time frame proposed by the PDP 3.0 Small Team.
  2. The GNSO Council requests future charter drafting teams of the GNSO Council to commence chartering for upcoming PDP efforts by utilizing the revised GNSO working group charter template and other related PDP 3.0 work products, and report to the GNSO Council on whether they help achieve the intended outcomes.
  3. The GNSO Council requests that after all PDP 3.0 improvements are in effect, the GNSO Council conducts a review of the implementation effectiveness in a timely manner.
  4. The GNSO Council requests that following the GNSO Council review of the PDP 3.0 implementation effectiveness, the GNSO Council considers any necessary updates to the GNSO Operating Procedures and uses the relevant work product in the PDP 3.0 Implementation Final Report as a starting point.
  5. The GNSO Council confirms that none but one (1) "Parking Lot" item (Statement of Interest Review) identified by the PDP 3.0 Small Team should be moved forward until the GNSO Council has the opportunity to evaluate the PDP 3.0 implementation effectiveness.
  6. The GNSO Council thanks to the PDP 3.0 Small Team, GNSO support staff, and others who have contributed to the implementation of GNSO PDP 3.0 improvements as well as the proposed implementation work products to enhance the efficiency and effectiveness of GNSO PDPs.

Vote results


Consent agenda: 2 items

  • Nomination of a Mentor for the ICANN Fellowship Program


    1. On 13 November 2019, the ICANN Fellowship Program invited ICANN's Supporting Organizations and Advisory Committees to nominate one individual each (total of 7) to serve on the capacity of Fellowship Program mentor for three consecutive ICANN meetings, beginning with ICANN68 (see
    2. On 3 December 2019, the GNSO launched an Expression of Interest (EOI) process to solicit volunteers for the GNSO-nominated mentor position (see
    3. The GNSO Council tasked the GNSO Standing Selection Committee (SSC) with reviewing applications and recommending one individual for the GNSO to nominate.
    4. The SSC reviewed the applications received, taking into account the criteria outlined in the EOI announcement.
    5. The SSC submitted its full consensus recommendation to the GNSO Council on 13 January 2020, by way of submission of the relevant motion.
    6. The GNSO Council considered the recommendations of the SSC.


    1. The GNSO nominates Amr Elsadr to serve as a ICANN Fellowship Program mentor for three consecutive ICANN meetings, beginning with ICANN68.
    2. The GNSO Council instructs the GNSO Secretariat to communicate resolved #1 to staff supporting the ICANN Fellowship Program.
    3. The GNSO Council instructs the GNSO Secretariat to inform the nominated candidate that he or she has been selected.
    4. The GNSO Council requests the GNSO Secretariat to send a response to those applicants who were not nominated, thanking them for their interest and encouraging them to apply for future opportunities as they arise.

    Confirmation of Johan Helsingius as the Chair and Carlton Samuels as Vice-Chair for the GNSO Standing Selection Committee (SSC).

    Vote results


Addendum to the Review of All Rights Protection Mechanisms in All gTLDs Charter to Integrate Recommendation 5 From IGO-INGO Access to Curative Rights Protection Mechanisms Final Report


  1. On 9 July 2018, the Policy Development Process (PDP) Working Group on International Governmental Organizations (IGO) and International Non-Governmental Organizations (INGO) Access to Curative Rights Protection Mechanisms submitted its Final Report to the GNSO Council. The Final Report contains five policy recommendations on which the Working Group reached consensus.
  2. On 19 July 2018, the GNSO Council acknowledged receipt of the PDP Final Report, noted that, "[i]n view of the need to consider the topic of curative rights protections for IGOs in the broader context of appropriate overall scope of protection for all IGO identifiers (including IGO acronyms), the GNSO Council intends to review this Final Report … with a view toward developing a possible path forward that will also facilitate the resolution of the outstanding inconsistencies between GAC advice and prior GNSO policy recommendations on the overall scope of IGO protections";
  3. Between July 2018 and March 2019, the GNSO Council discussed the PDP Final Report at various meetings and considered the procedural options available to it under the GNSO's Operating Rules and ICANN Bylaws
  4. On 18 April 2019, the GNSO Council resolved to approve, and recommend that the ICANN Board adopt, Recommendations 1, 2, 3 & 4 of the PDP Final Report.
  5. The GNSO Council elected not to approve Recommendation 5 of the PDP Final Report and directed the Review of All Rights Protection Mechanisms in All gTLDs (RPM) PDP to consider, as part of its Phase 2 work, whether an appropriate policy solution can be developed that is generally consistent with Recommendations 1, 2, 3 & 4 of the PDP Final Report and:
    1. accounts for the possibility that an IGO may enjoy jurisdictional immunity in certain circumstances;
    2. does not affect the right and ability of registrants to file judicial proceedings in a court of competent jurisdiction;
    3. preserves registrants' rights to judicial review of an initial UDRP or URS decision; and
    4. recognizes that the existence and scope of IGO jurisdictional immunity in any particular situation is a legal issue to be determined by a court of competent jurisdiction.
  6. The GNSO Council had engaged with the GAC on several occasions during its deliberations on the PDP Final Report, including at the joint GAC-GNSO meeting at ICANN65 in Kobe, Japan, where the GNSO Council had sought the GAC's feedback on the GAC's willingness to participate in a targeted effort focusing on the issue of curative rights for IGOs and possibly drawing on the community's recent experiences with the Expedited PDP on the Temporary Specification and Work Track 5 of the GNSO New gTLD Subsequent Procedures PDP
  7. At ICANN65 in Marrakech, members of the GNSO Council met with certain members of the GAC and IGOs, where there appeared to be agreement from the GAC/IGOs to support the chartering of this separate work. On 20 August, the GAC sent a letter to the ICANN Board, affirming, "its willingness to participate in such chartering effort." Dialogue between the GNSO Council, GAC, and IGOs continued at ICANN66 in Montreal, followed by further discussions within the Council.
  8. The GNSO Council, in consultation with the GAC and IGOs, has prepared the necessary amendments to the RPMs Charter, in the form of an Addendum to that Charter ("Addendum").


  1. The GNSO Council adopts the amendments to the RPMs Charter to create an IGO Work Track, as reflected in the Addendum.
  2. The GNSO shall collaborate with each GNSO Stakeholder Group, Constituency, SO and AC to expeditiously issue a call for Members and Observers to join the IGO Work Track, each in accordance with its own rules. The GNSO Council specifically notes that Members and Observers, although appointed by community groups, must nevertheless meet the Membership Criteria as defined in the Addendum.
  3. In accordance with the Addendum, the GNSO Council shall conduct an Expressions of Interest process as soon as is reasonably possible, in order to identify and confirm a single, qualified Work Track Chair, consistent with the criteria as defined in the Addendum.
  4. The GNSO Council directs the Work Track Chair and Members to conduct its work in as efficient and effective a manner as possible; and as such, monthly written updates shall be submitted to the GNSO Council by the IGO Work Track Chair and/or Council liaison to the Work Track. These updates must include a report as to the progress of the Work Track according to the timeline and milestones identified in its Work Plan.
  5. The GNSO Council further directs the Work Track Chair and Members to develop a Work Plan and timeline for its work as a matter of priority and as its first order of business. To facilitate this effort, the GNSO Council instructs ICANN staff to prepare a draft Work Plan and timeline for the Work Track, based on the model adopted for the Expedited Policy Development Process on gTLD Registration Data. The GNSO Council requests that the Work Track Chair submit a proposed Work Plan and timeline to the GNSO Council within four (4) weeks of the first meeting of the Work Track.
  6. To facilitate communications between the GNSO and the GAC on this topic, the GNSO Council directs the GNSO liaison to the GAC to provide regular progress reports to the GAC.
  7. The GNSO Council thanks the members of the GNSO Council, as well as those from the GAC and IGOs, for their contributions in developing the Addendum.

Vote results