Please note that all documents referenced in the agenda have been gathered on a Wiki page for convenience and easier access:

This agenda was established according to the GNSO Operating Procedures 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.

GNSO Council meeting held at 21:00 UTC

Coordinated Universal Time: 21:00 UTC:

13:00 Los Angeles; 16:00 Washington DC; 21:00 London; (Friday) 02:00  Islamabad; (Friday) 06:00 Tokyo; (Friday) 08:00 Melbourne 

GNSO Council Meeting Audio Cast

Listen in browser:

Listen in application such as iTunes:

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 (10 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 of the GNSO Council meeting on the 19 December 2019 were posted on 02 January 2020

Minutes of the GNSO Council meeting on the 23 January 2020 were posted on 10 February 2020

Item 2: Opening Remarks / Review of Projects & Action List (5 minutes)

2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List and Action Item List.

Note, the review of the Projects List will be a substantive agenda item for this Council meeting.


Item 3: Consent Agenda (0 minutes) 

  • None

Item 4: COUNCIL VOTE - Adoption of the PDP 3.0 Implementation Final Report (15 minutes)

The PDP 3.0 Small Team has completed thirteen (13) out of fourteen (14) PDP 3.0 improvements and has delivered four packages to the GNSO Council. 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. Package four, on improvements 9 and 15 was delivered on 21 November 2019. The PDP 3.0 Small Team completed implementation of improvement 17, which is integrated into the small team’s final outputs.

On 10 February 2020, The PDP 3.0 Small Team delivered its Final Report to the GNSO Council for its consideration. The Final Report provides an overview of the effort and the outcomes, effective dates for deployment of the improvements, and a consolidation of all of the work products. One work product related to PDP 3.0, the Consensus Playbook (originating from improvement 4), is not complete, but is also not strictly a PDP 3.0 product, as it is intended to be utilized by the broader community beyond just the GNSO.

Here, the Council will vote to adopt the Final Report, signifying the completion of the PDP 3.0 implementation effort.

4.1 – Presentation of motion (Council Leadership)

4.2 – Council discussion

4.3 – Council vote (voting threshold: simple majority)

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). This action is intended to enhance the GNSO’s ability to carry out the functions within its remit.

Item 5: COUNCIL UPDATE – Review of All Rights Protection Mechanisms in All gTLDs PDP Project Change Request (15 minutes)

Chartered in March 2016 to review all the RPMs that have been developed by ICANN, the PDP is focused on RPMs developed for the 2012 New gTLD Program (i.e., Trademark Clearing House, Sunrise, Claims, and Uniform Rapid Suspension). The WG is tasked with considering the overarching issue as to whether or not the RPMs collectively fulfil their purposes or whether additional policy recommendations will be necessary.

The PDP has worked diligently since launch and is preparing to publish its Initial Report for public comment. As of ICANN64, the WG had expected to be able to publish its Initial Report at the beginning of 2020. The WG is currently revisiting sub team and individual URS proposals and, when completed, will proceed to the development of its Phase One Initial Report, with a plan to publish in March of 2020. As a result of this delay in timeline, the PDP submitted a Project Change Request (PCR) for the January 2020 Council meeting, intending to both inform and gain approval from the GNSO Council. The Council agreed that Council leadership and the PDP leadership should discuss the PCR and determine whether the dates are achievable and that the PDP leadership is able to commit to those dates. 

Here, the Council will consider the revised Project Change Request.

5.1 – Introduction of topic (Council leadership; John McElwaine, GNSO Council liaison to the PDP)

5.2 – Council discussion

5.3 – Next steps

Item 6: COUNCIL UPDATE – New gTLD Subsequent Procedures PDP Project Change Request (15 minutes)

The PDP was chartered in January 2016  to review the 2012 New gTLD Program round to determine what, if any changes may need to be made to the existing 2007 Introduction of New Generic Top-Level Domains policy recommendations.

The WG has relied on a number of creative mechanisms to seek to address the extensive topics contained within its charter, including setting up a number of sub teams to divide the work. The WG has already published its Initial Report, a Supplemental Initial Report, as well as a report specific to Work Track 5, focused on geographic names. The WG has reviewed public comments received to all of these reports, considered what should be integrated, and is now in the midst of developing and reviewing draft final recommendations. Concurrently, the WG is seeking to resolve open issues on a subset of topics.

As of ICANN66, the WG estimated that it could deliver its Final Report to the GNSO Council by the end of Q2 2020, which was based on the premise that an additional public comment period would be limited to a subset of topics. However, it has become clear to the Co-Chairs that there is an expectation of a public comment on the entire draft Final Report, even if comment is only sought on particular areas of that report. Given these changing dynamics, the WG is submitting a Project Change Request that commits to delivering a Final Report to the GNSO Council no later than 31 December 2020.

Here, the GNSO Council will consider the PCR from the SubPro PDP.

6.1 – Introduction of topic (Council leadership; Flip Petillion, GNSO Council liaison to the PDP)

6.2 – Council discussion

6.3 – Next steps

Item 7: COUNCIL DISCUSSION – GNSO Projects List Review (30 minutes)

During the GNSO Council’s Strategic Planning Session in January 2020, the Council agreed that close review of the GNSO Projects List is a critically important part of its job as manager of the PDP process. The Council acknowledged that with full agendas, careful consideration of the project list is often sacrificed.

With a pipeline full of additional new work and an already brimming current set of projects, ensuring that current work is as well positioned as possible to succeed, but also recognizing areas of concerns, are important areas of focus for the GNSO Council. 

Here, the Council will conduct a thorough and detailed review of the Projects List (with the exceptions of RPMs and SubPro, which are both substantive items on this agenda).

7.1 – Introduction of topic (Council leadership)

7.2 – Council discussion

7.3 – Next steps

Item 8: COUNCIL DISCUSSION – GNSO Work Prioritization (15 minutes)

Continuing the theme from item 7 of this agenda, the GNSO Council acknowledged that there is extent to which it can agree to perform additional work. This resource limitation means that the GNSO Council must efficiently complete its current work as noted in item 7, but already prioritize the new work waiting in its pipeline. At the Strategic Planning Session, Councilors participated in an informal and non-binding ranking survey, which was used as a “sense of the room.” This informational survey result was shared with Councilors to then share with their respective Stakeholder Groups and Constituencies, to gain a better sense of the various groups’ top priorities.

Here, the Council will continue its discussions on which new work should be prioritized for initiation, when capacity within the community becomes available. 

8.1 – Introduction of topic (Council leadership)

8.2 – Council discussion

8.3 – Next steps

Item 9: ANY OTHER BUSINESS (15 minutes)

9.1 - ICANN67 Planning / Questions for lunch with the ICANN Board

9.2 - Council consideration of the draft GNSO Council public comment to the Draft FY21-25 Operating & Financial Plan and Draft FY21 Operating Plan & Budget, due on 25 February.

9.3 - Council consideration of whether a response is needed to ICANN org's 5 December 2019 letter related to clarifications on data accuracy and EPDP Phase 2.


Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article 11, Section 11.3(i))


Appendix 2: GNSO Council Absentee Voting Procedures (GNSO Operating Procedures, Section 4.4)


References for Coordinated Universal Time of 21:00 UTC 

Local time between October and March Winter in the NORTHERN hemisphere


California, USA (PST) UTC-8 13:00

San José, Costa Rica (CST) UTC-6 15:00

New York/Washington DC, USA (EST) UTC-5 16:00

Buenos Aires, Argentina (ART) UTC-3 18:00

Rio de Janeiro, Brazil (BRST) UTC-2 20:00

London, United Kingdom (GMT) UTC+0 21:00

Kinshasa, Democratic Republic of Congo (WAT) UTC+1 22:00

Paris, France (CET) UTC+1 22:00

Islamabad, Pakistan (PKT) (+1 day) UTC+5 02:00 

Singapore (SGT) (+1 day) UTC+8  05:00 

Tokyo, Japan (JST) (+1 day) UTC+9 06:00 

Melbourne, Australia (AEDT) (+1 day) UTC+11 08:00  


DST starts/ends on Sunday 29 of March 2020, 2:00 or 3:00 local time (with exceptions) for EU countries and on Sunday 08 of March 2020 for the US.


For other places see and

  • No labels
For comments, suggestions, or technical support concerning this space, please email: ICANN Policy Department
© 2015 Internet Corporation For Assigned Names and Numbers