Please note that all documents referenced in the agenda have been gathered on a Wiki page for convenience and easier access: https://community.icann.org/x/i4JJD.
This agenda was established according to the GNSO Operating Procedures v3.5, updated on 24 October 2019
- 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 in Kuala Lumpur, Malaysia 13:15-15:15 MYT: https://tinyurl.com/bdpud5r3
Coordinated Universal Time: 05:15-07:15 UTC
(Tuesday) 22:15 Los Angeles; (Wednesday) 01:15 Washington DC; 06:15 London; 07:15 Paris; 08:15 Moscow; 15:15 Melbourne
GNSO Council Meeting Remote Participation: https://75.schedule.icann.org/meetings/83izgwgonTkNzQX89
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 minutes)
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 21 July 2022 were posted on 05 August 2022.
Minutes of the GNSO Council meeting on 25 August 2022 were posted on 07 September 2022.
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.
Item 3: Consent Agenda (0 minutes)
Item 4: COUNCIL UPDATE - Update From Public Technical Identifiers (PTI) IANA (10 minutes)
As noted on the relevant webpage, “Public Technical Identifiers (PTI) is responsible for the operational aspects of coordinating the Internet’s unique identifiers and maintaining the trust of the community to provide these services in an unbiased, responsible and effective manner. Mainly, PTI is responsible for the operation of the IANA function,” as it relates to domain names, number resources, and protocol parameter assignments. As PTI performs the IANA functions on behalf of ICANN, it plays a critical role in the ICANN ecosystem.
The PTI Board collaborated with IANA staff, ICANN org, and members of the community to develop an inaugural strategic plan for July 2020 to June 2024, which as Lise Fuhr, Chair of the PTI Board of Directors notes in her blog post, provides “IANA-related strategic objectives that will help PTI continue to provide secure and accountable management of the Internet's unique identifier systems.”
Here, the Council will receive an update on PTI.
4.1 – Introduction of topic (Council leadership)
4.2 – Presentation (Lise Fuhr)
4.3 – Discussion
4.4 - Next steps
Item 5: COUNCIL DISCUSSION - Registration Data Accuracy Scoping Team - Assignments #1 (Enforcement and Reporting) and #2 (Measurement of Accuracy) Write Up & Process for Finding a New Chair (20 minutes)
The Registration Data Accuracy (RDA) Scoping Team was initiated by the GNSO Council in July 2021 per the formation instructions. The Scoping Team was tasked with considering a number of accuracy-related factors such as the current enforcement, reporting, measurement, and overall effectiveness of accuracy-related efforts. These considerations are expected to help inform its deliberations and the development of recommendations to the GNSO Council on whether any changes are recommended to improve accuracy levels, and, if so, how and by whom these changes would need to be developed (for example, if changes to existing contractual requirements are recommended, a PDP or contractual negotiations may be necessary to effect a change).
The RDA Scoping Team submitted a Project Change Request (PCR) to Council on 10 May 2022. The Scoping Team has since completed Assignment #1 (enforcement and reporting) and Assignment #2 (measurement of accuracy) and submitted its write up to the Council on 5 September 2022. In the write up, the group is suggesting moving forward with two proposals that would not require access to registration data, namely a registrar survey and a possible registrar audit that may help further inform the team’s work on assignment #3 (effectiveness) and #4 (impact & improvements), while it awaits the outcome of the outreach to the European Data Protection Board (EDPB) by ICANN org in relation to proposals that would require access to registration data.
As has been communicated previously, Michael Palage will be confirming his resignation as Chair of this group to the Council.
Here, the Council will discuss the write up and consider next steps, including the approach to identifying a new Chair.
5.1 – Introduction of topic (Michael Palage, Chair of the Registration Data Accuracy Scoping Team)
5.2 - Discussion
5.3 – Next steps
Item 6. COUNCIL DISCUSSION - Proposed updates to the GNSO Operating Procedures - Working Group Self-Assessment & GNSO Statement of Interest Procedures (15 minutes)
In order to perform work that is focused on structural, procedural, and process improvements, and specifically not policy development, the GNSO Council initiated the Council Committee for Overseeing and Implementing Continuous Improvement (CCOICI) pilot to focus on work that falls into these areas. The pilot specifically consists of two topics: a review of the Working Group Self-Assessment and a review of the GNSO Statements of Interest (SOI) requirements .
The CCOICI has reviewed the GNSO Working Group Self-Assessment (WGSA) survey and has proposed several recommendations and updates to the documentation. The CCOICI tasked the GNSO Statement of Interest (SOI) Task Force (TF) to review the current Statement of Interest (SOI) requirements and as a result of its review it is recommending a different structure. The CCOICI’s and Task Force proposed recommendations require amendments to the GNSO Operating Procedures, which requires a public comment proceeding.
Here, the Council will receive a briefing on the recommended changes and potential changes to the GNSO Operating Procedures.
6.1 – Introduction of topic (Olga Cavalli, Chair of the CCOICI and CCOICI liaison to the GNSO SOI TF) Slide Deck
6.2 – Council discussion
6.3 – Next steps
Item 7: COUNCIL DISCUSSION - PDP Improvements Tracker - Review of Format (10 minutes)
During the ICANN73 wrap up, the Council discussed a number of parallel conversations that have emerged since implementing PDP 3.0, identifying other aspects of the PDP where improvements could be considered. In addition, there are a number of projects on the Council’s Action Decision Radar (ADR) related to PDP improvements which will need to be addressed at some point in the future.
To provide the Council with a clear picture of these different parallel initiatives and projects, and to avoid overlap and ensure complementarity, the staff support team developed a discussion paper. In addition to an overview of the different initiatives and projects, the paper also suggests a possible approach for managing these different initiatives by focusing on 1) which elements could be implemented with relatively minimal effort, 2) which elements could be implemented with some effort, 3) which elements need careful planning and consideration before these can be implemented. After reviewing a draft of the PDP Improvements Tracker during a series of Council meetings, no objections were received to track and manage the work in the suggested manner.
As a first step towards the substantive review of the items in the tracker, Council leadership worked with the staff support team to develop a survey to obtain initial input from Council members as well as Stakeholder Group and Constituency leadership that will help inform the substantive review of the proposed improvements and next steps. A sample of the survey was circulated to the Council list in advance of the August meeting where the survey, approach, and next steps were discussed.
Having heard no disagreement, the survey was launched shortly after the Council meeting. The results of the survey are expected to be considered during the GNSO working session at ICANN75.
Here, the Council, having discussed the topic during the working session, will consider next steps.
7.1 – Introduction of topic (Council leadership)
7.2 – Council discussion
7.3 – Next steps
Item 8: COUNCIL DISCUSSION - Whois Disclosure System (15 minutes)
The proposed design of the Whois Disclosure System will have been published prior to ICANN75 and will be presented on Saturday of ICANN75, and the small team and Council will have had an initial discussion during the session immediately following the ICANN Org presentation in order to review the proposed design and consider next steps.
The Council is scheduled to discuss the Whois Disclosure System with the Board during its joint session on Tuesday.
Here, the Council will seek to distill and discuss the conversations with ICANN org, the small team, GAC, and the Board and determine next steps.
8.1 – Introduction of topic (Sebastien Ducos, Council vice-chair and lead of the EPDP Phase 2 small team)
8.2 – Council discussion
8.3 – Next steps
Item 9: COUNCIL DISCUSSION - Update from the UASG (15 minutes)
The mission of the Universal Acceptance Steering Group (UASG) is to promote and work towards a future where all domain names and all email addresses work in all software applications. With the GNSO’s work on enabling the application for new gTLDs and developing policy recommendations related to internationalized domain names, universal acceptance is an important factor for the work of the GNSO.
The UASG is planning a Universal Acceptance (UA) day in February 2023 and is seeking the participation of the various community groups. The UASG is hopeful that the GNSO will be able to contribute to the effort and help promote UA adoption.
Here, Dr. Ajay Data, Chair of the UASG, will provide an update on the progress of the UASG and discuss the ways in which the GNSO might be able to help support the planned UA day.
9.1 – Introduction of topic (Council leadership)
9.2 – Presentation (Dr. Ajay Data, Chair of the UASG) Slide deck
9.3 – Council discussion
9.4 – Next steps
Item 10: ANY OTHER BUSINESS (20 minutes)
10.1 – Confirmation of approach for term limits for the GNSO liaison to the GAC
10.2 – Update - Potential changes to the Standing Committee for ICANN Budget & Operations (SCBO)
10.3 – Farewell to outgoing Councilors (Flip Petillion, Juan Manuel Rojas, Maxim Alzoba, Olga Cavalli, Philippe Fouquart)
10.4 - Open microphone
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 05:15 UTC
Local time between March and November in the NORTHERN hemisphere
California, USA (PDT) UTC-7 (Tuesday) 22:15
San José, Costa Rica (CST) UTC-6 (Tuesday) 23:15
New York/Washington DC, USA (EDT) UTC-4 01:15
Buenos Aires, Argentina (ART) UTC-3 02:15
Rio de Janeiro, Brazil (BRT) UTC-3 02:15
London, United Kingdom (BST) UTC+1 06:15
Kinshasa, Democratic Republic of Congo (WAT) UTC+1 06:15
Paris, France (CEST) UTC+2 07:15
Moscow, Russia (MSK) UTC+3 08:15
Singapore (SGT) UTC+8 13:15
Melbourne, Australia (AEST) UTC+10 15:15
DST starts on Sunday 27 March 2022, 2:00 or 3:00 local time (with exceptions) for EU countries and on Sunday 13 March 2022 for the US.
DST ends on Sunday 30 October 2022 for EU countries, and on Sunday 06 November 2022 for the US.
For other places see http://www.timeanddate.com and https://tinyurl.com/bdpud5r3.