Full Agenda |  Documents | Motions

• Item 1: Administrative Matters

  • 1.1 - Roll Call

  • 1.2 - Updates to Statements of Interest

  • 1.3 - Review / Amend Agenda

  • 1.4 - Minutes

    • Minutes of the GNSO Council Meeting on 11 March 2026 were posted on 29 March 2026.

    • Minutes of the GNSO Council Meeting on 16 April 2026 were posted on 30 April 2026.

• Item 2: Opening Remarks / Review of Projects  Action List

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

• Item 3: COUNCIL VOTE - Board Un-Adoption Process in Updated GGP and PDP Manuals

• Item 4: COUNCIL VOTE DISCUSSION - Council Process for Response to SPIRT Request Forwarding an issue to the SPIRT (updated 19 May)

• Item 5: Council Discussion - GNSO Mechanism for Work Prioritization

• Item 6: Any other business

  • 6.1 - ICANN86 Planning

    • GNSO Prep Week Webinar - 28 May 2026 at 13:00 UTC

    • GNSO Council members will be panelists and expected to join, unless apologies given in advance. Questions will be taken from GNSO Council only

  • 6.2 - DNS Abuse PDP2 Charter Drafting

  • 6.3 - SPIRT Issue regarding RSP RSP Issue Consideration for Potential Change Request (updated 19 May)

  • 6.4 - Leadership Team Update on Call with Kurtis Lindqvist, ICANN CEO (added 19 May)

  • 6.5 - ICANN Community Participant Code of Conduct regarding Statements of Interest (added 19 May)

  • 6.6 - Topic Leads for Discussions with the GAC (added 19 May)

Summary Report to the ALAC on GNSO Council Meeting #05 held on 21 May 2026 (click on 'Report to the ALAC' tab)

For brevity, I will just highlight outcomes on key issues here. You may get more information under the Matters of Interest and/or Meeting Records tabs.

1. GNSO Process for Board to Reverse Adoption of GNSO Policy Recommendations

• Council adopted the updated GNSO PDP Manual and the updated GGP Manual.

2. Council Process for Forwarding an issue to the SPIRT

• The Standing Predictability Implementation Review Team (SPIRT) was chartered by the GNSO Council to utilize the Predictability Framework outlined in the New gTLD Program: 2026 Round Applicant Guidebook to collaborate with ICANN org on all non-minor changes to the New gTLD Program (including policy changes) when issues arise during the course of the New gTLD Program. Council is responsible for oversight of the SPIRT.

• Key to this discussion is the fact that per its Charter, SPIRT cannot refer an issue raised by a SPIRT member to itself. Therefore the issue has to be raised with Council for Council’s decision whether to refer the issue to the SPIRT.

• After much discussion over how an earlier proposed mechanism ought to be implemented, Council came to the conclusion that issues raised by a SPIRT member should be referred to the SG/C whom the SPIRT member “belongs”, to then put the issue on Council’s agenda for deliberation and decision by vote on whether to refer the issue to SPIRT.

  • Once a Council decision is made, per the New gTLD Subsequent Procedures Final Report, the Council can forward an issue to the SPIRT by a letter from the GNSO Chair or his/her designee. The New gTLD Subsequent Procedures Final Report stipulates that “Every item that is referred to the SPIRT should contain an expected turnaround time in the referral request, allowing for certain items to be handled in an expedient fashion when required and others to have a longer time where speed may not be needed.”

  • Should the issue be marked as requiring urgent attention, then Council leadership can determine if a decision of Council needs to be established before the next Council meeting and take steps to acquire such a decision.

• Council discussed Issue #1 under SPIRT Issues Consideration Process - RSP Evaluation Change Request Jeff Neuman SPIRT Issue Submission Form - Google Forms.pdf as raised by the RySG, and will decide at its June 2026 meeting whether to refer this issue to SPIRT for next steps.

3. GNSO Mechanism for Work Prioritization

• Council deliberated on a briefing document which sets out various potential mechanisms Council might use in order to prioritise its work, and agreed to test use of the Multi-Criteria model (Option 1).

4. DNS Abuse PDP2 Charter Drafting

• As this was raised during Council’s March 2026 meeting, Council leadership informed that staff will engage councilors in a review of the draft PDP2 Charter with possible proposed updates based on learning from PDP 1.

5. ICANN Community Participant Code of Conduct regarding Statements of Interest

• RySG flagged their draft 2026-05-14 Operations, Finance and Budget Working Group (OFB-WG) Call around the enforcement on SOI requirements; and invited Council input once the finalized draft is ready.

6. GNSO Discussions with GAC on Registration Data Accuracy

• Council was informed that after discussing with GAC leadership, it is understood that:

  • an earlier proposed pre-ICANN86 GAC Webinar to discuss the 15-day timeline for registrars to validate and verify registrants contact information, has now been moved to ICANN86 and will be more informational in nature; and

  • the GAC-proposed GAC-Board-GNSO Trilateral will take place after ICANN86.

• Council leadership will consider a need to write to the GAC to clarify opportunities during ICANN86 on this.