Dear all, Please find below the updated final agenda for GNSO Council's 10 April 2025 meeting, followed by my summary report on Matters of Interest. Happy to answer and questions on this thread or during the next ALAC Monthly Call on 16 April, and apologies in advance for the lengthiness of my report. You can navigate between the windows for the April 2025 entry on my Liaison wiki space at this link <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/99708540/GNS...> . *GNSO Council Meeting #4 of 2025 held on 10 Apr 2025 * *Full Agenda <https://icann-community.atlassian.net/wiki/x/EKafBg> | Documents <https://icann-community.atlassian.net/wiki/x/yKefBg> | Motions <https://icann-community.atlassian.net/wiki/x/GaifBg>* - *Item 1: Administrative Matters* - 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 <https://gnso.icann.org/en/council/project> and Action Item List <https://community.icann.org/x/RgZlAg> - *Item 3: Consent Agenda* - GNSO Review of the GAC Communiqué - *Recommendations Report for the Transfer Policy Review PDP* - *Item 4: COUNCIL VOTE - Confirmation of EPDP on Temporary Specification Team’s Intent to Modify RAA Requirements Related to Billing Contact* - Item 5: COUNCIL DISCUSSION - Aspirational Statement Review - Council will discuss the draft aspirational statement <https://gnso.icann.org/sites/default/files/policy/2024/draft/draft-gnso-coun...> and determine next steps. - *Item 6: COUNCIL DISCUSSION - Han Script Single Character gTLDs (Recommendation 3.17)* - *Item 7: COUNCIL UPDATE: Registration Data Request Service* - *Item 8: COUNCIL DISCUSSION: Next Steps for Whois Implementation Advisory Group* - *Item 9: Any Other Business* - 9.1 - Update on ICANN83 Planning and GNSO Draft Schedule - 9.2 - WSIS+20 <https://docs.google.com/document/d/1fM5b8tZX1APSUhEovc0qHWXc_wg3HzJ8__mJuvZN...> and internet governance discussions - *9.3 - Latin Diacritics PDP Working Group - Review of Project Plan <https://gnso.icann.org/sites/default/files/policy/2025/presentation/project-...> * - 9.4 - Standing Committee on Continuous Improvements - Review of Project Plan - *9.5 - Council review of Assignment Forms for DNS Abuse and Accuracy Small Teams* - 9.6 - Transfer Policy Review HRIA Update *Special Summary Report of 10 Apr 2025 Meeting to ALAC* For brevity, I will just highlight a few things here. For some of the issues, you can glean a wider perspective from GNSO Council Apr 2025 Matters of Interest and/or from GNSO Council Apr 2025 Meeting Records. *1. Consent Agenda* - Council unanimously approved a GNSO Council Recommendations Report <https://gnso.icann.org/sites/default/files/policy/2025/draft/gnso-council-re...> regarding the Final Recommendations from the Transfer Policy Review Policy Development Process Working Group for transmission to the ICANN Board. *2. DNS Abuse Mitigation* - Council continues to consider the GNSO Council DNS Abuse Small Team Assignment Form <https://gnso.icann.org/sites/default/files/policy/2025/draft/assignment-form...> *3. Registration Data Accuracy* - Council continues to consider the GNSO Council Registration Data Accuracy Small Team Assignment Form <https://gnso.icann.org/sites/default/files/policy/2025/draft/assignment-form...> *4. Han Script Single Character gTLDs (IDNs EPDP Phase 1 Recommendation 3.17)* - Council spent significant time discussing next steps on this topic. See: Slides <https://gnso.icann.org/sites/default/files/policy/2025/presentation/han-scri...> - The New gTLD Subsequent Procedures (SubPro) PDP provided Recommendation 25.4 (approved by the ICANN Board) to allow single character gTLDs for ideographic scripts in the next round, *provided that they do not introduce confusion risks that rise above commonplace similarities*. The IDNs EPDP Phase 1 Final Report put forth important additional detail and limitations on 25.4, prescribing that the single character gTLDs be limited to the Han script and that *applications must not be accepted until relevant guidelines are developed and put in place by the Chinese, Japanese, and Korean (CJK) Generation Panels (GPs)*. Alternatively, the IDN EPDP concluded that if the CJK GPs determine that additional guidelines beyond the RZ-LGR are not needed, then the single character applications should proceed. - The matter was put out for public comment by the CJK Generation Panels. Although the CJK GPs stated <https://www.icann.org/en/system/files/files/proposed-han-script-single-chara...> that the work done in the Root Zone Label Generation Rules (RZ-LGRs <https://www.icann.org/resources/pages/root-zone-lgr-2015-06-21-en>) sufficiently addresses the concerns around the risk of confusion for single character Han script gTLDs, the majority of the public comments <https://www.icann.org/en/public-comment/proceeding/seeking-input-on-han-scri...> on the CJK GPs’ statements opposed moving forward. Some commenters from the Chinese community expressed concerns about the lack of alignment with China’s linguistic laws and regulations, the complexities of Chinese character ideographs, and end-user confusion due to multiple meanings of many single characters. One such comment received from a co-Chair of the CGP argues that the CGP should not be and was not involved in "risk of confusion" policy considerations related to single Han characters as TLDs. Many of the comments call for further community work prior to proceeding. Similar concerns were received through the public comment <https://www.icann.org/en/public-comment/proceeding/second-proceeding-for-pro...> on the relevant draft AGB sections. - This public comment was discussed with the Sub Pro IRT IDN Sub-Track which referred the matter to the main SubPro IRT. The main SubPro IRT was asked by ICANN staff whether Recommendation 25.4 should be modified as not implementable or whether the issue should be reviewed with Council for possible further work. It was agreed that the Liaisons should raise this with Council for direction on next steps. A background document <https://gnso.icann.org/sites/default/files/policy/2025/presentation/irt-pape...> prepared by Lars Hoffman was shared with the Council on December 9. - It is generally understood by Council that any resolution this issue should not hold up the next round and GNSO staff had been requested to provide an analysis of the two potential options to address this issue: a a GNSO Guidance Process (GGP) and an Expert Working Group (EWG), as an alternative to the GGP. - During Council's discussion it was clarified that instead of an EWG, GNSO staff was to examine the option of an Expert Advisory Panel (EAP) and present to Council, a comparison of a GGP vs. EAP. - Council Leadership will refine the options, namely 4 non-mutually exclusive options: (1) GGP, (2) EAP, (3) an informal mechanism to identify experts who can perform the work to develop the necessary guidelines, and (4) decline to act on the public comments; for SG/C further input. *5. Registration Data Request Service (RDRS)* - Council received an update from Sebastien Ducos, Chair of RDRS Standing Committee. See: Slides <https://gnso.icann.org/sites/default/files/policy/2025/presentation/rdrs-upd...> - The Standing Committee has been reviewing monthly data since the inception of the RDRS in November 2023. After one year of reviewing RDRS metrics, the Standing Committee determined it had enough information to begin compiling its Findings Report to the Council, and it began work on its report in January 2025. - Work on the Findings Report continues. *6. EPDP Phase 1 on the Temporary Specification - Implementation Question re: Billing Contact* - The best and most accurate summary of this issue is captured in the preamble of Council's Motion to confirm EPDP on Temporary Specification Team’s Intent to Modify RAA Requirements Related to Billing Contact <https://icann-community.atlassian.net/wiki/x/JKifBg> - After much deliberations on this topic during its meetings on 19 December 2024 <https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...> , 13 February 2025 <https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>, and 12 March 2025 <https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>, Council concluded as follows: - Council acknowledges that the role of Council during policy implementation is to “serve as a resource for staff who have questions about the background or intent of the policy recommendations during its implementation. Council may continue to provide input on the implementation of a policy, for example, if Council believes that the implementation is inconsistent with the policy.” - Council also acknowledges that unless in conflict with or otherwise modified by a policy recommendation, current contractual requirements and consensus policy requirements remain in place following the implementation of a new ICANN Consensus Policy. - Council agreed that the EPDP Team did intend to eliminate the requirement for registrars to collect and retain billing contact data under an ICANN purpose for processing; however, the GNSO Council acknowledged that there is no corresponding policy recommendation that states this. - Council further acknowledges that it is not the role of Council nor the IRT to create policy, as policy is created per the GNSO Policy Development Process in the ICANN Bylaws, Annex A <https://www.icann.org/en/governance/bylaws#annexA>. - Council acknowledges that the EPDP Phase 1 Team was working under an exceptional timeline due to the Board’s adoption of a Temporary Specification (the first of its kind), and for that reason, the Recommendations fail to comprehensively capture the Working Group’s intent related to the collection and escrow of billing contact data. - With this exceptional circumstance in mind, Council confirms that the EPDP Team intended to eliminate the current requirements in the Registrar Accreditation Agreement related to Billing Contact. This intention was demonstrated in the Final Report, which did not include a recommendation for registrars to collect and retain billing contact data and which was delivered pursuant to the EPDP Team Charter which directed the EPDP Team to consider the collection and retention of billing contact data. - And therefore, Council resolved <https://icann-community.atlassian.net/wiki/x/JKifBg> as follows: - Council confirms its guidance to ICANN org that the EPDP Team did intend to modify the current Registrar Accreditation Agreement requirements related to billing contact, and the current RAA requirements for the collection, retention, and escrow of billing contact have been eliminated by the Registration Data Policy. For the avoidance of doubt, the modified sections include section 3.6 (as it relates to 3.4.1.3), 3.4.1.3, and 1.1.2 - 1.1.5 of the Data Retention Specification; and - Council confirms and commits that, going forward, it will be specified in Working Group Charters that if the Working Groups intend to modify a requirement within the Registry Agreement, Registrar Accreditation Agreement, or Consensus Policy via Consensus Policy recommendations, the policy recommendations must explicitly and specifically identify which requirements are intended to be modified and how such requirements are recommended to be modified per their Consensus Policy recommendations. - BC placed on the record that this incident should not become a precedent. IPC provided a statement to support their vote against the motion <https://icann-community.atlassian.net/wiki/x/JKifBg>. *7. Whois Implementation Advisory Group* - Council received an introduction on this topic. See: Slides <https://gnso.icann.org/sites/default/files/policy/2025/presentation/whois-ia...> - The ICANN Procedure For Handling WHOIS Conflicts with Privacy Law Implementation Advisory Group (WHOIS Procedure IAG) is tasked to provide the GNSO Council with recommendations on how to address the comments and input that has been received in response to the public comment forum on the Revised ICANN Procedure for Handling WHOIS Conflicts with Privacy Law: Process and Next Steps. - The project has been on hold since September 2021, when ICANN org informed <https://gnso.icann.org/sites/default/files/file/field-file-attach/swinehart-...> the GNSO Council that it mutually agreed with Contracted Parties to focus on the completion of data processing agreements associated with the EPDP on the Temporary Specification before further developing the Whois Conflicts Procedure. ICANN org published the Data Processing Specification <https://www.icann.org/resources/pages/data-processing-specification-requests...> in January 2025. - After a brief discussion, it was acknowledged that SG/C would be consulted further by email on questions around where there is still a need to continue the work of the advisory group given that developments arising from GDPR coming into effect and the ensuing Temporary Specification and Data Processing Policy. *8. Latin Diacritics Policy Development Process* - Council received an update on the Latin Diacritics PDP Working Group Project Plan <https://gnso.icann.org/sites/default/files/policy/2025/presentation/project-...> . *9. WSIS+20* - SG/C were requested to provide input to the GNSO Participation in WSIS+20 and Action Lines – Overview. Justine Chew ALAC Liaison to the GNSO GNSO Liaison Report Workspace <https://icann-community.atlassian.net/wiki/x/fG7xBQ?atlOrigin=eyJpIjoiNDI1Yj...> ------ On Sun, 30 Mar 2025 at 10:40, Justine Chew <justine.chew.icann@gmail.com> wrote:
Dear all,
Just a note to inform you that the agenda for the GNSO Council meeting on 10 April 2025 is out.
For a curated version of the highlighted agenda items, please visit the *MATTERS OF INTEREST* sub-menu at this link <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/99708540/GNS...> .
*GNSO Council Meeting #4 of 2025 held on 10 Apr 2025 <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/99708540/GNSO+Liaison+Report+post-Oct+2021#GNSOLiaisonReport,post-Oct2021-A-25-04>*
*Full Agenda <https://icann-community.atlassian.net/wiki/x/EKafBg> | Documents <https://icann-community.atlassian.net/wiki/x/yKefBg> | Motions <https://icann-community.atlassian.net/wiki/x/GaifBg>*
- *Item 1: Administrative Matters* - 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 <https://gnso.icann.org/en/council/project> and Action Item List <https://community.icann.org/x/RgZlAg> - *Item 3: Consent Agenda* - GNSO Review of the GAC Communiqué - *Recommendations Report for the Transfer Policy Review PDP* - *Item 4: COUNCIL VOTE - Confirmation of EPDP on Temporary Specification Team’s Intent to Modify RAA Requirements Related to Billing Contact* - Item 5: COUNCIL DISCUSSION - Aspirational Statement Review - *Item 6: COUNCIL DISCUSSION - Han Script Single Character gTLDs (Recommendation 3.17)* - *Item 7: COUNCIL UPDATE: Registration Data Request Service* - *Item 8: COUNCIL DISCUSSION: Next Steps for Whois Implementation Advisory Group* - *Item 9: Any Other Business* - 9.1 - Update on ICANN83 Planning and GNSO Draft Schedule - 9.2 - WSIS+20 <https://docs.google.com/document/d/1fM5b8tZX1APSUhEovc0qHWXc_wg3HzJ8__mJuvZN...> and internet governance discussions - *9.3 - Latin Diacritics PDP Working Group - Review of Project Plan <https://gnso.icann.org/sites/default/files/policy/2025/presentation/project-plan-latin-script-diacritics-26mar25-en.pdf>*
- 9.4 - Standing Committee on Continuous Improvements - Review of Project Plan - *9.5 - Council review of Assignment Forms for DNS Abuse and Accuracy Small Teams*
This Council meeting will take place on *10 Apr 2025 **at 21:00 UTC*: https://tinyurl.com/5bsuykt5 for 2 hours and is open to observers remotely in listen-only mode via Zoom. To access the Zoom link for this meeting, please visit the *MEETING DETAILS* sub-menu at this link <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/99708540/GNS...> .
Thanks for reading / considering.
Justine Chew ALAC Liaison to the GNSO GNSO Liaison Report Workspace <https://icann-community.atlassian.net/wiki/x/fG7xBQ?atlOrigin=eyJpIjoiNDI1Yj...> ------