April 2024 - council - lists.icann.org

**Starting in 15 minutes | Meeting Invitation | GNSO Council Meeting | Thursday, 18 April 2024
by Terri Agnew 18 Apr '24

18 Apr '24

**Starting in 15 minutes Dear all, The GNSO Council meeting is scheduled on Thursday, 18 April 2024 at 21:00 UTC for 2 hours. Before joining the call: Please be sure you have read the Expected Standards of Behavior <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> Visit the Wiki Agenda page: https://community.icann.org/x/_oAvEQ Check your time zone: https://tinyurl.com/2xcnuymd [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/2xcnuymd__;!!PtGJab4!8imzQGH…> Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call, gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Please click the link below to join the webinar: https://icann.zoom.us/j/92283565389?pwd=QnlHK1JSbzdiSFFZSjRjamxMTkNGdz09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/92283565389?pwd=QnlHK1JS…> Passcode: f!Ym9!npfN If joining Zoom via Zoom App the following will be required: Webinar ID: 922 8356 5389 Passcode: 6981311025 Or One tap mobile : +13462487799,,92283565389#,,,,*6981311025# US (Houston) +16699006833,,92283565389#,,,,*6981311025# US (San Jose) If you are joining via audio only: International numbers available: https://icann.zoom.us/u/adGHfYeA3T [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/u/adGHfYeA3T__;!!PtGJab4!9…> Observers are welcome to join, they will be in a read-only and listen-only mode. Please note that all documents<https://community.icann.org/x/A4DyEg> referenced in the agenda will be gathered on a Wiki page for convenient and easy access. Thank you. Kind regards, Terri Policy Team Supporting the GNSO

1 0

UPDATE Proposed Agenda | GNSO Council Meeting | Thursday, 18 April 2024
by Terri Agnew 18 Apr '24

18 Apr '24

Dear all, The following has been updated on the GNSO Council Agenda, see updated agenda here<https://community.icann.org/x/_oAvEQ>. Agenda item 4 went from a council vote to a COUNCIL DISCUSSION - Deferral of Policy Status Report Request - Expiration Policies (10 minutes) Presentation slides were added to: Item 8: COUNCIL DISCUSSION - Review of Action Decision Radar (15 minutes) Item 9: Update on Status of Privacy and Proxy Services Accreditation Implementation (15 minutes) Adjustment to AOB items: Item 10: Any Other Business (10 minutes) 10.1 - IPC’s RFR decision<https://www.icann.org/en/system/files/files/reconsideration-23-2-ipc-reques…> and Council’s subsequent letter<https://gnso.icann.org/sites/default/files/policy/2024/correspondence/dibia…> (Damon Ashcraft) 10.2 - Update on ICANN80 planning and GNSO Draft schedule<https://gnso.icann.org/sites/default/files/policy/2024/draft/icann80-gnso-d…> 10.3 - Replacement of Council representative to the Continuous Improvement Program Community Coordination Group (CIP-CCG) 10.4 - Upcoming Sessions/Updates on the Registration Data Request System (RDRS) * Prep Week Session on RDRS: Wednesday, 29 May at 16:30 UTC * RDRS Standing Committee Meeting at ICANN80: Monday, 10 June at 10:45 - 12:15 local time (UTC+2) Thank you. Kind regards, Terri ************* Dear all, Please find below the final proposed agenda for the GNSO Council Meeting taking place on Thursday, 18 April 2024 at 21:00 UTC for 2 hours This has been posted on the agenda wiki page<https://community.icann.org/x/_oAvEQ>. Thank you. Kind regards, Terri Policy Team Supporting the GNSO Draft GNSO Council Agenda: 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/A4DyEg. This agenda was established according to the GNSO Operating Procedures [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…> v3.5, updated on 15 March 2023. 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 on Thursday, 18 April 2024 at 21:00 UTC: https://tinyurl.com/2xcnuymd [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/2xcnuymd__;!!PtGJab4!72Ceiu6…> 14:00 Los Angeles; 17:00 Washington DC; 22:00 London; 23:00 Paris; 00:00 Moscow (Friday); 07:00 Melbourne (Friday) GNSO Council Meeting Remote Participation: https://icann.zoom.us/j/92283565389?pwd=QnlHK1JSbzdiSFFZSjRjamxMTkNGdz09 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/j/92283565389?pwd=QnlHK1JS…> 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 (5 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 [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> of the GNSO Council Meeting on 15 February 2024 were posted on 02 March 2024 Minutes [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> of the GNSO Council Meeting on 06 March 2024 were posted on 23 March 2024. Item 2: Opening Remarks / Review of Projects & Action List (0 minutes) 2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/en/council/project__;!!Pt…> and Action Item List. <https://community.icann.org/x/RgZlAg> Item 3: Consent Agenda (5 minutes) * GNSO Council Review of the GAC Communiqué [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> * GNSO Council Small Team Guidance Document [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> * Confirmation of Standing Predictability Implementation Review Team (SPIRT) Charter Drafting Team Leadership (Chair - Nitan Walia; Vice-chair - Alan Greenberg; GNSO Council liaison - Anne Aikman-Scalese) Item 4: COUNCIL VOTE - Deferral of Policy Status Report Request - Expiration Policies (10 minutes) The GNSO Council previously considered when to request a Policy Status Report (“PSR”) for the purpose of conducting a review of the two Expiration Policies, the Expired Domain Name Deletion Policy (“EDDP”) and the Expired Registration Recovery Policy (“ERRP”). In November 2020, given concerns about its capacity and no known issues with the policies, the Council agreed to delay the request for the Policy Status Report (PSR) for a period of 24 months. After 24 months had passed, the Council reconsidered whether it was an appropriate time to request a Policy Status Report. To that end, in July 2022, the Council agreed that it would be helpful to consult with both registrars and ICANN org to help determine if there are any known issues or concerns with either of the two Expiration Policies which could warrant requesting a PSR. In making its decision whether to request to a PSR at this time, the Council consulted: 1. Registrars, who were asked to flag substantial issues with the policies that would warrant a near team request for policy status report and did not note any issues 2. ICANN Compliance, who provided a write-up<https://mm.icann.org/pipermail/council/2022-November/026164.html>, noting confusion with key terms in the policy and persistent registrant confusion with the auto-renew grace period and aftermarket activities, et.al. 3. ICANN org Registrant Program, which provided a catalog of the available educational resources on domain name expiration and renewal (Brian Gutterman’s update at Council) In reviewing these materials, the Council determined that the EDDP and ERRP seem to have been implemented as intended and imminent policy work is not needed at this time. Accordingly, the GNSO Council will reconsider a PSR on the Expiration Policies in five years time, or earlier, if requested. Here, the Council will vote to consider a PSR on the Expiration Policies in five years. 4.1 - Presentation of motion<https://community.icann.org/display/gnsocouncilmeetings/Motions+2024-04-18> (Greg DiBiase, Chair) 4.2 - Council Discussion 4.3 - Council vote (voting threshold: simple majority) Item 5: COUNCIL DISCUSSION - Diacritics in Latin Script (20 minutes) Several parties raised an issue to the GNSO Council’s attention with regard to the challenge affecting future applied-for strings in the Latin script containing diacritics that may be confusingly similar to ASCII strings, and are non-variants. For background, an applied-for IDN gTLD string in the Latin script containing diacritics, which is NOT an allocatable variant label of the base ASCII string (existing or applied-for) according to RZ-LGR, are sometimes seen as equivalents. In some instances however, the base ASCII string is seen as a workaround and not necessarily “correct”. The base ASCII string and the Latin diacritic string may be determined to be confusingly similar (i.e., in which case, the strings would be placed in a contention set or if an existing gTLD is involved, the applied-for label would not pass the String Similarity Review). During the GNSO Council Meeting at ICANN78 in Hamburg on 25 October 2023 [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…>, the GNSO Council received a detailed briefing on this issue and agreed to request a study from ICANN org to help inform the GNSO Council on the issue of diacritics in Latin Script. Prior to the request being made to ICANN org, the org volunteered to investigate what mechanism or mechanisms might be appropriate to address this issue. Here, the Council will receive an update from ICANN org on the status of the research and analysis. 5.1 - Introduction of Topic (Greg DiBiase, GNSO Chair) 5.2 - Council Discussion 5.3 - Next Steps Item 6: COUNCIL VOTE - SubPro Supplemental Recommendations (20 minutes) In March 2023, the ICANN Board approved the majority of the recommendations contained in the Final Report on the new gTLD Subsequent PDP, but also placed some recommendations into a pending status. The Council convened a small team that worked collaboratively with the ICANN Board to resolve all pending recommendations. While the majority of the pending recommendations were able to be adopted by the ICANN Board, recommendations across six Topics were non adopted by the ICANN Board. With the primary task of addressing the pending recommendations now complete, the Council tasked the Small Team Plus with an updated assignment form [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1yDgWIwKZqKk0…>. The Small Team Plus has committed to a work plan [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1IhxKi0dvkS-a…> to address the recommendations not adopted by the Board. Following that plan, the Small Team agreed to Supplemental Recommendations [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> on five of the six Topics, e.g., Registry Voluntary Commitments / Public Interest Commitments, Applicant Support, Terms and Conditions, String Similarity Evaluations, and Limited Challenge/Appeal Mechanisms. Based on the expected implementation as it relates to the Continued Operations Instrument (COI), the Small Team Plus determined it was unnecessary to develop a Supplemental Recommendation for Topic 22: Registrant Protections. On 1 April, an “Explainer” document [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…>was shared with the Council that consolidates all of the Supplemental Recommendations and provides a brief explanation for each of them. Here, the Council will vote on the SubPro Supplemental Recommendations developed by the Small Team Plus. 6.1 - Presentation of motion<https://community.icann.org/display/gnsocouncilmeetings/Motions+2024-04-18> (Paul McGrady, Small Team Plus Lead) 6.2 - Council Discussion 6.3 - Council vote (voting threshold: GNSO Supermajority in order to trigger the threshold that “the Board shall adopt the recommendation unless more than two-thirds (2/3) of the Board determines that such policy is not in the interests of the ICANN community or ICANN.”) Item 7: COUNCIL DISCUSSION - New gTLD Auction Proceeds Cross Community Working Group - Auction Proceeds (CCWG-AP) - Proposed Update to Recommendation 7 (20 minutes) The CCWG-AP’s Recommendation 7 sets out limitations on the use of ICANN accountability mechanisms (namely, the Independent Review Process, IRP, and Reconsideration process) to challenge decisions made on individual applications within the Grant Program. The CCWG-AP offered this recommendation to minimize use of the proceeds for purposes other than grants, such as administrative costs or legal fees. The Board has noted it continues to support the CCWG-AP’s goal in making this recommendation. Recommendation 7 currently provides, “Existing ICANN accountability mechanisms such as IRP or other appeal mechanisms cannot be used to challenge a decision from the Independent Project Applications Evaluation Panel to approve or not approve an application. Applicants not selected should receive further details about where information can be found about the next round of applications as well as any educational materials that may be available to assist applicants. The CCWG recognizes that there will need to be an amendment to the Fundamental Bylaws to eliminate the opportunity to use the Request for Reconsideration and Independent Review Panel to challenge grant decisions.” (emphasis added) In its 2 March 2024 letter, the Board notes it “has been considering whether there are further ways to meet the community’s broader intention with Recommendation 7. If the phrase ‘from the Independent Project Applications Panel’ is removed from Recommendation 7, many of the Board’s concerns that supported the October 2023 action would be addressed. The Board also notes that removal of that phrase would support what it has always understood to be the intention of the CCWG-AP in making Recommendation 7 - to preserve the auction proceeds for funding projects, not challenges. Therefore, the Board asks for the Chartering Organizations’ support in considering an update to the recommendation. Specifically, the Board asks for each Chartering Organization to the CCWG-AP to approve an update to Recommendation 7 that would remove the phrase ‘from the Independent Project Applications Evaluation Panel’ from the text of the recommendation. If the Chartering Organizations approve this update, the Board believes that there is a path to full implementation of the CCWG-AP’s Recommendation 7, including the ability to apply the restriction to third parties.” The Board is asking for feedback by 17 May 2024. It may be helpful to consider this requested amendment to Recommendation 7 separately from the public comment<https://www.icann.org/en/public-comment/proceeding/proposed-bylaws-updates-…> on the Proposed Bylaws Updates to Limit Access to Accountability Mechanisms. Here, the Council will discuss the proposed update to CCWG-AP Recommendation 7. 7.1 - Introduction of Topic (Greg DiBiase, GNSO Chair) 7.2 - Council Discussion 7.3 - Next Steps Item 8: COUNCIL DISCUSSION - Review of Action Decision Radar (15 minutes) During the GNSO Council’s most recent strategic planning session, the Council discussed the topic of how to be an effective manager of the GNSO’s Policy Development Process (PDP). In recognition of the importance of regularly reviewing the Council’s portfolio of work, the Council agreed to the following action item, “During a session at ICANN79, Council to prepare for a careful review of the work captured in the Program Management Tool (PMT) that will conclude or initiate prior to the next AGM, or continue beyond the next AGM[.]” The Council conducted this inaugural review of the Projects List during its Working Session at ICANN79<https://community.icann.org/display/gnsocouncilmeetings/GNSO+Council+Workin…> on Sunday, 3 March 2024. The review also intended to include an overview of the Action Decision Radar<https://community.icann.org/display/gnsocouncilmeetings/Action+Decision+Rad…> (“ADR”); however, due to timing constraints, the Council agreed to review the ADR at an upcoming Council meeting. The ADR is a tool designed to assist the Council by highlighting imminent decisions or actions that need to be taken by the GNSO Council. The ADR contains a series of range markers, e.g., 0-1 month, 1-3 months, etc., to alert the Council to the timing of the upcoming action or decision. Here, the Council will review the contents of the ADR and discuss next steps. 8.1 - Introduction of Topic (Greg DiBiase, GNSO Chair) 8.2 - Council Discussion 8.3 - Next Steps Item 9: Update on Status of Privacy and Proxy Services Accreditation Implementation (15 minutes) The Privacy and Proxy Services Accreditation Issues PDP achieved full consensus on its recommendations and delivered its Final Report [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/filef…> on 8 December 2015, with subsequent Council adoption [gnso.icann.org]<https://urldefense.com/v3/__http:/gnso.icann.org/en/council/resolutions*201…> of the Final Report on 21 January 2016. On 9 August 2016, the ICANN Board adopted<https://www.icann.org/resources/board-material/resolutions-2016-08-09-en#2.e> all recommendations of the PPSAI PDP, directing ICANN org to begin implementation. After some initial preparatory work, the Implementation Review Team (IRT) first met on 18 October 2016. Subsequently, as a result of potential conflicts and/or overlap of work between the PPSAI IRT and GDPR-related work, especially the EPDP on the Temporary Specification for gTLD Registration Data, ICANN org, in its letter to the GNSO Council, proposed to delay the implementation of PPSAI until the EPDP completes. In its 4 March 2019 letter<https://www.icann.org/en/system/files/correspondence/namazi-to-drazek-et-al…> to GNSO Council leadership, ICANN org posed the following question to the GNSO Council, “whether ICANN org should continue to delay public comment and implementation of PPSAI or take additional steps pending completion of the EPDP in consultation with the PPSAI Implementation Review Team (IRT).” GNSO Council Leadership responded, “given the divergent views among Councilors and considering the respective roles of ICANN Org in leading implementation work of consensus policy recommendations and the PPSAI IRT in overseeing the implementation work, the GNSO Council considers it appropriate to defer the decision on this issue to ICANN org and the PPSAI IRT, taking into account the various views of the SOs and ACs.” On 2 March 2021, ICANN org delivered the Wave 1.5 Report<https://mm.icann.org/pipermail/council/2021-March/024506.html> to the GNSO Council, which included a detailed analysis of the extent to which the EPDP Phase 1 recommendations may require modification to the PPSAI and Translation & Transliteration policies, which are in the policy implementation phase. Following review of the Wave 1.5 Report, the Council observed the following in its 1 July 2021 letter [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…>: * The decision to pause the implementation of the PPSAI and Translation & Transliteration policy recommendations was a decision that was made by ICANN org, not the GNSO Council. As such, the Council is of the view that a decision to restart the implementation activities is not within the remit of the GNSO Council but for ICANN org to make. The Council would also like to point to its letter of February 2019 in which it also concluded that “considering the respective roles of ICANN Org in leading implementation work of consensus policy recommendations and the PPSAI IRT in overseeing the implementation work, the GNSO Council considers it appropriate to defer the decision on this issue to ICANN org and the PPSAI IRT, taking into account the various views of the SOs and ACs”. * Should any policy issues arise during the implementation of these policy recommendations, there are processes and procedures that allow the Council to further consider these, but the Council is of the view that the respective Implementation Review Teams (IRTs) will be best placed to identify such possible issues. * The Council would also like to point to the letter<https://www.icann.org/en/system/files/correspondence/namazi-to-drazek-et-al…> that was sent to the Council in September 2019 in which it was noted that “following the completion of relevant EPDP work, ICANN org will reassess the existing draft PP materials in consultation with the PPSAI IRT and determine how to proceed with implementation of the Privacy and Proxy Services Accreditation Program”. From a Council’s perspective this still seems a relevant and timely next step. During its wrap-up session at ICANN79 [icann79.sched.com]<https://urldefense.com/v3/__https:/icann79.sched.com/event/1a1Cl/gnso-counc…>, the GNSO Council appointed two liaisons, Paul McGrady and Stephanie Perrin, to serve as GNSO Council liaisons to the PPSAI IRT. Here, the Council will receive an update on the recent meeting. 9.1 - Introduction of Topic (Greg DiBiase, GNSO Chair) 9.2 - Council Discussion 9.3 - Next Steps Item 10: Any Other Business (10 minutes) 10.1 - Update on ICANN80 planning and GNSO Draft schedule [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> 10.2 - Replacement of Council representative to the Continuous Improvement Program Community Coordination Group (CIP-CCG) 10.3 - Upcoming Sessions/Updates on the Registration Data Request System (RDRS) _______________________________ Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article 11, Section 11.3(i)) See https://www.icann.org/resources/pages/governance/bylaws-en/#article11. Appendix 2: GNSO Council Absentee Voting Procedures (GNSO Operating Procedures, Section 4.4) See https://gnso.icann.org/sites/default/files/file/field-file-attach/op-proced… [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…> References for Coordinated Universal Time of 21:00 UTC Local time between March and November in the NORTHERN hemisphere See https://www.timeanddate.com/time/change/ [timeanddate.com]<https://urldefense.com/v3/__https:/www.timeanddate.com/time/change/__;!!PtG…> for Dates for Daylight Saving Time and Clock Changes ---------------------------------------------------------------------------- California, USA (PDT) UTC-7 14:00 San José, Costa Rica (CST) UTC-6 15:00 New York/Washington DC, USA (EDT) UTC-4 17:00 Buenos Aires, Argentina (ART) UTC-3 18:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 22:00 Paris, France (CEST) UTC+2 23:00 Moscow, Russia (MSK) UTC+3 00:00 (Friday) Singapore (SGT) UTC+8 05:00 (Friday) Melbourne, Australia (AEST) UTC+10 07:00 (Friday) ---------------------------------------------------------------------- For other places see http://www.timeanddate.com [timeanddate.com]<https://urldefense.com/v3/__http:/www.timeanddate.com/__;!!PtGJab4!72Ceiu66…> and https://tinyurl.com/2xcnuymd [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/2xcnuymd__;!!PtGJab4!72Ceiu6…>

1 0

FYI | FW: [Ext] NEW: ICANN Launches a Diversity and Inclusion Toolkit
by Terri Agnew 18 Apr '24

18 Apr '24

FYI [https://danh45uab.cc.rs6.net/on.jsp?ca=c932fcb4-8955-4510-9efc-2bfc82bf0a53…] Thursday, 18 April 2024 ICANN Community Digest [https://files.constantcontact.com/304b3fd3501/31f30ab5-1445-45c3-aef7-c0ea4…] The ICANN organization Policy Development Support function publishes this twice-weekly digest to help ICANN community groups track requests and follow updates. How Domain Name System Policy is Developed, and How You Can Get Involved [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=00138THoQH…> Do you have any ideas for improving the ICANN Community Digest? Write to us at policyinfo(a)icann.org!<mailto:policyinfo@icann.org> Table of Contents ICANN80 · NEXT WEEK: Design and Translation Deadline · ICANN80 Community Childcare Grants Program Now Accepting Applications Information Sharing · NEW: ICANN Launches a Diversity and Inclusion Toolkit · Update: ICANN’s Emergency Assistance Program for Continued Internet Access Webinars · Preview the ICANN and IANA FY25 Operating Plans and Budget Action Item · TOMORROW 🔥 ACTION ITEM: ICANN81 Fellowship Application Round Now Open · 🔥 ACTION ITEM: Call for NextGen@ICANN81 Applications Public Comment · NEW SUMMARY REPORT: Review of the Draft Applicant Support Program (ASP) Handbook-New gTLD Program · NEW SUMMARY REPORT: Proposed Top-Level Domain String for Private Use · NEXT WEEK: Review of the Draft Registry Service Provider (RSP) Handbook - New gTLD Program · Proposed Renewal of the Registry Agreement for the .XXX top-level domain (TLD) · Review of the Registry System Testing 2.0 Test Specifications and API · Phase 2 Initial Report of the EPDP on Internationalized Domain Names ICANN80 NEXT WEEK: 24 APRIL 2024: DESIGN DEADLINE: If you require design assistance for your publication, you need to provide all the text, images, layout, and publication type/size requirements (i.e. one-pager vs. trifold, etc.). You will receive a maximum of 2 iterations of the publication. Please provide everything by 24 APRIL. Due to budget constraints, please keep in mind that all materials, new or updated, need to be evergreen. 6 MAY 2024: TRANSLATION DEADLINE: If your publication requires translation, please provide the final material(s) by 6 MAY. This ensures that there is enough time to translate the publication by the start of the meeting, with the possibility of potential changes. If your materials require design assistance (outlined above), please note that the final materials will have to be complete, including the edit/approval processes, by this deadline to be translated If you have any questions please email andrea.glandon(a)icann.org<mailto:andrea.glandon@icann.org> ICANN80 Community Childcare Grants Program Now Accepting Applications The program facilitates in-person participation of community members with children 12 years old or younger at ICANN Public Meetings and other eligible ICANN events. Deadline: Friday, 3 May 2024, at 23:59 UTC Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=00138THoQH…> Information Sharing NEW: ICANN Launches a Diversity and Inclusion Toolkit By following the guidance provided in the toolkit, we collectively contribute to the evolution and strengthening of ICANN's multistakeholder model, fostering an inclusive community that reflects the diversity of the global Internet governance landscape. We would like to thank the WS2-CCG for their assistance. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=00138THoQH…> Update: ICANN’s Emergency Assistance Program for Continued Internet Access ICANN has signed master service agreements with three qualifying organizations that stand ready to support Internet accessibility when operators or other relevant actors might otherwise not have the resources to do so. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=00138THoQH…> Webinars Preview the ICANN and IANA FY25 Operating Plans and Budget ICANN will be hosting two public webinars on 25 April 2024 for the community to preview the proposed-for-adoption plans prior to the Board meeting. 25 April 2024 | 14:30 - 1600 UTC | Register [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=00138THoQH…> 26 April 2024 | 00:00 - 01:30 UTC | Register [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=00138THoQH…> Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=00138THoQH…> Action Items TOMORROW 🔥 ACTION ITEM: ICANN81 Fellowship Application Round Now Open ICANN is opening the application round for the ICANN Fellowship Program for the ICANN81 Annual General Meeting, which will take place in Istanbul, Türkiye, from 9-14 November 2024. Deadline: 19 April 2024, 23:59 UTC. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=00138THoQH…> 🔥 ACTION ITEM: Call for NextGen@ICANN81 Applications ICANN wants to hear from university students ages 18-30 living and studying in the Asia Pacific region who are interested in the future of the Internet and participating in the ICANN81 Annual General Meeting. ICANN81 is scheduled to be held in Istanbul, Türkiye, from 9–14 November 2024. Deadline: 17 May 2024 Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=00138THoQH…> Public Comment NEW SUMMARY REPORT: Review of the Draft Applicant Support Program (ASP) Handbook-New gTLD Program [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=00138THoQH…> NEW SUMMARY REPORT: Proposed Top-Level Domain String for Private Use [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=00138THoQH…> NEXT WEEK: Review of the Draft Registry Service Provider (RSP) Handbook - New gTLD Program [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=00138THoQH…> Open for Submissions: 13 March 2024 Closed for Submissions: 22 April 2024 Proposed Renewal of the Registry Agreement for the .XXX top-level domain (TLD) [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=00138THoQH…> Open for Submissions: 18 March 2024 Closed for Submissions: 29 April 2024 Review of the Registry System Testing 2.0 Test Specifications and API [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=00138THoQH…> Open for Submissions: 26 March 2024 Closed for Submissions: 06 May 2024 Phase 2 Initial Report of the EPDP on Internationalized Domain Names [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=00138THoQH…> Open for Submissions: 11 April 2024 Closed for Submissions: 21 May 2024 See upcoming proceedings [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=00138THoQH…>. See other public consultations [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=00138THoQH…>. Volume 6, Issue 29 | Archive [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=00138THoQH…> | Next Issue: Monday, 22 April 2024 STAY INFORMED: Subscribe here [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=00138THoQH…>

1 0

Additional Considerations Regarding Supplemental Recommendations 24.3A, 24.3B, and 24.3C (Singular/Plural)
by DiBiase, Gregory 18 Apr '24

18 Apr '24

Hi All, Thanks to everyone for the initial feedback on the new proposals regarding Latin Diacritics and Singulars vs. Plurals. I would like to clarify that the new question before Council at April’s meeting is: should we defer consideration of the Topic 24 Supplemental Recommendation in order to evaluate these new proposals (and consider modifying this Supplemental Recommendation based on Org’s proposal or a different version of Org’s proposal). To that end, the below link has a proposed amendment to Paul’s motion to accept the SubPro Supplemental Recommendations. The amendment removes the Topic 24 Supplemental Recommendation so it can be further considered. I’ve also proposed an amendment to the Explainer Doc which follows the same logic. Amended Motion: https://docs.google.com/document/d/1B-OYl6PvxQA1wSG3y9rXrQfwDWFfNZ7DXow1PXS… Amended Explainer Document: https://docs.google.com/document/d/1YwInQ8hSaosKDBbXMyPbmbChGoGyRBGqzjOQmg_… If Council decides deferral of the Topic 24 Supplemental Recommendation is warranted, I’ll propose these amendments. If not, we can proceed with Paul’s original motion. I hope this is clear. I look forward to the discussion. Thanks, Greg From: council <council-bounces(a)gnso.icann.org> On Behalf Of Tomslin Samme-Nlar via council Sent: Tuesday, April 16, 2024 9:06 PM To: kurt kjpritz.com <kurt(a)kjpritz.com> Cc: GNSO Council List <council(a)gnso.icann.org> Subject: RE: [EXTERNAL] [council] Additional Considerations Regarding Supplemental Recommendations 24.3A, 24.3B, and 24.3C (Singular/Plural) CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. Hi all, I agree with Kurt's points. NCSG discussed this as well yesterday and would like clarity whether the diacritics issue is a technical issue or a policy issue. Especially considering the fact that it was the LGR panel that decided that Latin diacritics were not variants, not a PDP. Warmly, Tomslin On Wed, 17 Apr 2024, 12:49 kurt kjpritz.com<http://kjpritz.com> via council, <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> wrote: Hi Everyone: I think the diacritics issue is complex and should not be placed on the critical path for the next round. 1. As indicated by others, the identification and handling of both variants and diacritics has been considered and there is a well-settled set of rules governing them. 2. After careful consideration, the Latin LGR Group decided that Latin diacritics were not variants and, therefore their co-existence in the root was effectively banned (even if variants were permitted). Before deciding whether to re-visit the issue, I’d want the Council to understand why the LGR group arrived at those conclusions. 3. I think we should not delay in any way, the completion of the five-year sub-pro policy development process and subsequent multi-year implementation process for this issue. This could have been raised at any time during the sub-pro policy process, 4. If, after understanding why the Latin LGR is written the way is has been, a policy process similar to the recently completed IDN EPDP could be initiated. For example, the .quebec registry could use its RySG membership (or some other means) as an appropriate avenue to raise a well-defined broad policy issue. As I think we all agree, the policy issue does not concern one specific TLD, it is the reconsideration of the Latin LGR. I believe we should put Latin LGR consideration in line with our other works and assign it a priority according to the wishes of the Council. That said I’m uncertain whether there is a specified process for changing the RZ-LGRs that have been developed through a community process and ratified by the ICANN Board. As usual, my mind can be changed and I hope there are responses to this. Best regards, Kurt On 14 Apr 2024, at 4:57 am, Anne ICANN via council <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> wrote: Many thanks Steve, Definitely the appropriate way forward from my point of view as a member of the Sub Pro Small Team Plus. This would hopefully also give us more time to consider the issue in relation to diacritics and the suggestion by Board and Org that the diacritics issue could be addressed in a further modification to the String Similarity Supplemental Recommendations. Reminder that I am non-voting, but I think the Council should vote to send all other Sub Pro Supplemental Recommendations to the Board, but should amend the Small Team Plus assignment form to conduct further work on String Similarity with a rapid timeline for a return recommendation from the Small Team Plus to the Council. Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2024 anneicanngnso(a)gmail.com<mailto:anneicanngnso@gmail.com> On Fri, Apr 12, 2024 at 1:46 PM Steve Chan via council <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> wrote: Dear Councilors, I have another update that the Council may want to factor into its plans for considering Supplemental Recommendations 24.3A, 24.3B, and 24.3C. The Board Caucus on New gTLD on Subsequent Procedures, with the assistance of ICANN org, has looked into the feasibility of implementing Supplemental Recommendations 24.3A, 24.3B, and 24.3C. Some concerns remain, so the Caucus has worked with ICANN org to try and identify a potential approach that would accomplish the intent of the recommendations (i.e., no singulars/plurals of existing gTLDs in the same language and applied-for singulars/plurals in the same language placed into a contention set) while minimizing remaining concerns. The Caucus and org have identified an approach that they believe can achieve the objective of the Supplemental Recommendations. While further work is needed to fully document the approach (note, the approach will also need to be discussed with the full Board), my org colleagues are working on first drafting a high-level overview of the approach to be shared with the Council. If after considering the high-level overview, the Council wishes to work further on the relevant Supplemental Recommendations, I understand that the Caucus remains available and willing to continue building upon the collaborative relationship it shares with the Council. Best, Steve Steven Chan  VP, Policy Development Support & GNSO Relations Internet Corporation for Assigned Names and Numbers (ICANN) 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536  Email: steve.chan(a)icann.org<mailto:steve.chan@icann.org> Skype: steve.chan55 Mobile: +1.310.339.4410 Find out more about the GNSO by visiting: https://learn.icann.org/<https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…> _______________________________________________ council mailing list council(a)gnso.icann.org<mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. _______________________________________________ council mailing list council(a)gnso.icann.org<mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. _______________________________________________ council mailing list council(a)gnso.icann.org<mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

4 3

Motion to defer PSR on Expiration Policies
by DiBiase, Gregory 17 Apr '24

17 Apr '24

Dear Councilors, Please see the attached motion to defer a request for a Policy Status Report on Expiration Policies. We will vote on this motion during our April meeting. Thanks, Greg

2 3

Re: [council] [Ext] Re: Update re: GAC Liaison Role | GNSO Council meeting 06 March 2024 and GNSO Council Wrap-Up meeting 07 March 2024
by Julie Hedlund 17 Apr '24

17 Apr '24

Thank you Jeff for confirming. Kind regards, Julie From: Jeff Neuman <jeff(a)jjnsolutions.com> Date: Tuesday, April 16, 2024 at 7:05 PM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org>, Julie Hedlund <julie.hedlund(a)icann.org> Subject: [Ext] Re: Update re: GAC Liaison Role | GNSO Council meeting 06 March 2024 and GNSO Council Wrap-Up meeting 07 March 2024 Thanks Julie. Yes, after this version is approved, we must run it by the GAC as it is a joint document. Sincerely, Jeff [cid:image001.png@01DA90B7.DAE3AD60] ________________________________ From: council <council-bounces(a)gnso.icann.org> on behalf of Julie Hedlund via council <council(a)gnso.icann.org> Sent: Tuesday, April 16, 2024 5:01 PM To: council(a)gnso.icann.org <council(a)gnso.icann.org> Subject: [council] Update re: GAC Liaison Role | GNSO Council meeting 06 March 2024 and GNSO Council Wrap-Up meeting 07 March 2024 Dear Councilors, On behalf of the GNSO Council leadership, thank you to all who commented per the action item below on the GAC Liaison role document at: https://docs.google.com/document/d/1jYOMd0RIYPqo7EHjLEXgw78AxjRx693sO30sXI1… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1jYOMd0RIYPqo…>. Since the suggested changes and comments were not substantive, and the April Council meeting agenda is quite full, Council leadership suggests adding the final version of the document to the Consent Agenda for the 16 May Council meeting for a vote to adopt, following which staff can initiate the Expression of Interest for the GAC Liaison role. Also, staff notes that the original document was created via the GNSO-GAC Consultation Group, so Leadership suggests that we could socialize the revised document to GAC leadership for their information, since the changes are just clarifications. Kind regards, Julie Hedlund On behalf of GNSO Council Leadership From: council <council-bounces(a)gnso.icann.org> on behalf of Julie Hedlund via council <council(a)gnso.icann.org> Reply-To: Julie Hedlund <julie.hedlund(a)icann.org> Date: Monday, April 1, 2024 at 2:12 PM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [council] REMINDER re: GAC Liaison Role | GNSO Council meeting 06 March 2024 and GNSO Council Wrap-Up meeting 07 March 2024 Dear Councilors, Please see the reminder below. Kind regards, Julie From: council <council-bounces(a)gnso.icann.org> on behalf of Julie Hedlund via council <council(a)gnso.icann.org> Reply-To: Julie Hedlund <julie.hedlund(a)icann.org> Date: Tuesday, March 19, 2024 at 5:30 PM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [council] REMINDER re: GAC Liaison Role | GNSO Council meeting 06 March 2024 and GNSO Council Wrap-Up meeting 07 March 2024 Dear Councilors, This is a reminder that with respect to the following Action Item GNSO Councilors are requested to complete their review prior to Monday, 08 April, the Document and Motion Deadline for the 18 April GNSO Council meeting: Item 8: Selection and Timeline of Next GNSO Liaison to the Governmental Advisory Committee (10 minutes) Action Items: GNSO Councilors to review the GAC Liaison role at: https://docs.google.com/document/d/1jYOMd0RIYPqo7EHjLEXgw78AxjRx693sO30sXI1… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1jYOMd0RIYPqo…> and be prepared to finalize it at the Council meeting on 18 April 2024. When reviewing this document, kindly add feedback in comment form only. Best regards, Julie From: council <council-bounces(a)gnso.icann.org> on behalf of Terri Agnew via council <council(a)gnso.icann.org> Reply-To: Terri Agnew <terri.agnew(a)icann.org> Date: Wednesday, March 13, 2024 at 4:39 PM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [council] Action Items | GNSO Council meeting 06 March 2024 and GNSO Council Wrap-Up meeting 07 March 2024 Dear Councilors, Please find the action items, as stated during the meeting, below arising from the GNSO Council meeting held on Wednesday, 06 March 2024 and the GNSO Council Wrap-up held on Thursday, 07 March 2024. Please refer to the Action Item page<https://community.icann.org/display/gnsocouncilmeetings/Action+Items> for updates on item completion progress. Please take note of the action items coming out of the Council meeting and the proposed timing for delivering on these actions. Please refer to this page for the recent status updates on the Action items. Please note that actions for all councilors are highlighted below. GNSO Council meeting on 06 March 2024 Item 3: Consent Agenda Motion to Adopt the Communications Small Team Final Report Action Items: On behalf of the GNSO Council, the GNSO Secretariat notifies the Communications Small Team that the GNSO Council accepts the recommendations as outlined in the Final Report, requests that the leadership of the small team works with Council leadership on developing the respective communications as foreseen under recommendations 6.2.1 and 6.2.2, and thanks the small team for its efforts as well as the ICANN org communications function for their contributions. Item 4: COUNCIL DISCUSSION - Reaction to Program Management Tools Discussion Action Items: 1. Outcome: GNSO Council agreed to review the Program Management Tools at least twice a year. Staff to ensure that the second review of the year takes place at the AGM. 2. Leadership and staff to provide a summary by 08 April of the outcomes and action items from the discussion at the ICANN79 GNSO Council working session. Item 5: COUNCIL DISCUSSION - Council Engagement with PDP Working Group Chairs (15 minutes) Action Items: GNSO Support Staff to organize a pre-ICANN80 dedicated GNSO Council webinar, similar to pre-ICANN79 webinar, where Councilors are invited to engage directly with PDP WG Chairs. Note: as discussed during the Council meeting, Councilors have other avenues to engage with PDP WG Chairs if the need arises, including through the appointed Council liaisons to the WGs. Item 7: COUNCIL DISCUSSION - Response to Update from ICANN org Implementation Update and interaction with ICANN Board (25 minutes) Action Items: IGOs/INGOs: GNSO Council leadership to continue to ask ICANN org for a timeline until it is delivered. Item 8: Selection and Timeline of Next GNSO Liaison to the Governmental Advisory Committee (10 minutes) Action Items: GNSO Councilors to review the GAC Liaison role at: https://docs.google.com/document/d/1jYOMd0RIYPqo7EHjLEXgw78AxjRx693sO30sXI1… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1jYOMd0RIYPqo…> and be prepared to finalize it at the Council meeting on 18 April 2024. Item 9: ANY OTHER BUSINESS 9.2 - Updated Small Team Guidelines Action Items: GNSO Councilors to review the updated Small Team Guidelines document at: https://gnso.icann.org/sites/default/files/policy/2024/draft/updated-small-… [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> and consider for adoption on the Consent Agenda at the meeting on 18 April 2024. GNSO Support Staff to send a reminder to review and make edits by Monday, 25 March. 9.4 - Aspirational Statement Action Items: GNSO Councilors to review the draft Aspirational Statement at: https://gnso.icann.org/sites/default/files/policy/2024/draft/draft-aspirati… [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> and provide any suggestions for edits in the document by Monday, 25 March for discussion on the list. GNSO Support Staff to send a reminder to the list. GNSO Council Wrap-up on Thursday, 07 March 2024 1. GNSO review of the GAC Communique - identify volunteers to support Jeff. Action Items: Volunteers – Manju Chen, Susan Payne, Paul McGrady, Damon Ashcraft, Desiree Milosevic, and Jen Chung. 2. PPSAI next steps - determination if anything further is needed beyond “wait and see.” Action Items: 1. Volunteers for IRT Liaison – Paul McGrady, Stephanie Perrin. Options: 1. Greg DiBiase, Paul McGrady and Stephanie Perrin to meet with GDS staff who support the PPSAI IRT and report back to the full Council during the April meeting. 3. CCWG-AP next steps * Rec 7 amendment - how to approach. * Bylaws public comment - determination if Council comment is needed. Action Items: Rec 7 Amendment: GNSO Councilors to volunteer to convene a small team to see if there is a unified Council position. Bylaws public comment: GNSO Councils to determine by consulting with their SGs and Cs if the Council should comment. 4. GAC concerns about the SOI - next steps for the Council, if any Action Items: Jeff Neuman to draft a letter on the SOI to the GAC pointing to the relevant section of the CCOICI’s report. 5. Review of the GNSO liaison to the GAC position – Workback timeline to assign a new representative by Kigali. Action Items: GNSO Councilors to review the guidelines at: https://docs.google.com/document/d/1jYOMd0RIYPqo7EHjLEXgw78AxjRx693sO30sXI1… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1jYOMd0RIYPqo…> and provide comments, if any, on the list by 21 March 2024. Staff to prepare the SSC for the selection process, but timing is dependent on whether there are changes to the guidelines. 6. ATRT4 - feedback on whether this needs to proceed per the Bylaw or it should be deferred. Action Items: GNSO Councilors to consult with their SGs/Cs as to whether ATRT4 should be deferred by Monday, 18 March; depending on the response the Council leadership will draft a unified response to ICANN org by 22 March. Thank you. Kind regards, Terri Policy Team Supporting the GNSO

1 0

GNSO Council Absence Notification Form: Kurt Pritz
by GNSO Council via ICANN 17 Apr '24

17 Apr '24

Full Name of Officer: Samantha Demetriou Officer Email Address: sdemetriou(a)verisign.com Date Prepared: 17 April 2024 GNSO Organization: Registries Stakeholder Group Officer Position or Title: Chair Name of Absent Councilor: Kurt Pritz Voting Remedy: Proxy Proxy Information Reason(s) for or condition(s) leading to the remedy: Kurt will be in transit during the 18 April 2024 GNSO Council meeting. In the event that he loses connectivity or has to drop from the call, Nacho Amadoz will hold his proxy for any votes held during the meeting. Specific subject(s)/measure(s)/motion(s)/action(s) of the Council for which the remedy is being exercised: All motions requiring a vote during the 18 April 2024 meeting. Date upon which the remedy will expire or terminate: 19 April 2024 I affirm that a voting position has been established on the matter(s) at issue pursuant to provisions contained in our Charter or Bylaws. Yes Our GNSO Councilor has been instructed on how to vote on the matter(s). Yes Full Name of GNSO Councilor Serving as Voting Proxy: Nacho Amadoz By submitting my personal data, I agree that my personal data will be processed in accordance with the ICANN Privacy Policy [1], and agree to abide by the website Terms of Service [2]. I Agree [1] https://www.icann.org/privacy/policy [2] https://www.icann.org/privacy/tos

1 0

Please read: Upcoming GNSO Council meeting prep 18 April 2024 at 21:00 UTC
by Terri Agnew 17 Apr '24

17 Apr '24

Dear all, A few reminders of prep for the Council meeting 18 April 2024 at 21:00 UTC. 1. Please review the GNSO Council meeting Cheat Sheet <https://urldefense.com/v3/__https:/docs.google.com/document/d/1lQ9fqEjD-inZ…> in order to help you prepare for the session and also provide your input in suggestion mode. It is also attached to this email for your convenience. 1. All documents mentioned on the Council agenda<https://community.icann.org/x/_oAvEQ> will be listed on the Document wiki page<https://community.icann.org/x/A4DyEg> for easy referral. If there are any topics you would like to see appear on future Council agendas, please do not hesitate to add them to the Council Topics Google doc. <https://urldefense.com/v3/__https:/docs.google.com/document/d/1FSNlAHTjbWAz…> 1. Please consult the Project Management Portfolio<https://community.icann.org/pages/viewpage.action?pageId=150178769>, in particular the Action Decision Radar<https://community.icann.org/x/14vzC> and the Project List<https://community.icann.org/x/1YvzC> . 1. If you fear you may run into connectivity issues or may not make it on the call, please have an officer of your SG/C fill in the Council Absence Notification form<https://www.icann.org/forms/gnso_notification>. Thank you! Kind regards, Terri Policy Team Supporting the GNSO

1 0

REMINDER | Meeting Invitation | GNSO Council Meeting | Thursday, 18 April 2024
by Terri Agnew 17 Apr '24

17 Apr '24

Dear all, The GNSO Council meeting is scheduled on Thursday, 18 April 2024 at 21:00 UTC for 2 hours. Before joining the call: Please be sure you have read the Expected Standards of Behavior <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> Visit the Wiki Agenda page: https://community.icann.org/x/_oAvEQ Check your time zone: https://tinyurl.com/2xcnuymd [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/2xcnuymd__;!!PtGJab4!8imzQGH…> Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call, gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Please click the link below to join the webinar: https://icann.zoom.us/j/92283565389?pwd=QnlHK1JSbzdiSFFZSjRjamxMTkNGdz09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/92283565389?pwd=QnlHK1JS…> Passcode: f!Ym9!npfN If joining Zoom via Zoom App the following will be required: Webinar ID: 922 8356 5389 Passcode: 6981311025 Or One tap mobile : +13462487799,,92283565389#,,,,*6981311025# US (Houston) +16699006833,,92283565389#,,,,*6981311025# US (San Jose) If you are joining via audio only: International numbers available: https://icann.zoom.us/u/adGHfYeA3T [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/u/adGHfYeA3T__;!!PtGJab4!9…> Observers are welcome to join, they will be in a read-only and listen-only mode. Please note that all documents<https://community.icann.org/x/A4DyEg> referenced in the agenda will be gathered on a Wiki page for convenient and easy access. Thank you. Kind regards, Terri Policy Team Supporting the GNSO

1 0

Additional Considerations Regarding Supplemental Recommendations 24.3A, 24.3B, and 24.3C (Singular/Plural)
by Steve Chan 17 Apr '24

17 Apr '24

Dear Councilors, I have another update that the Council may want to factor into its plans for considering Supplemental Recommendations 24.3A, 24.3B, and 24.3C. The Board Caucus on New gTLD on Subsequent Procedures, with the assistance of ICANN org, has looked into the feasibility of implementing Supplemental Recommendations 24.3A, 24.3B, and 24.3C. Some concerns remain, so the Caucus has worked with ICANN org to try and identify a potential approach that would accomplish the intent of the recommendations (i.e., no singulars/plurals of existing gTLDs in the same language and applied-for singulars/plurals in the same language placed into a contention set) while minimizing remaining concerns. The Caucus and org have identified an approach that they believe can achieve the objective of the Supplemental Recommendations. While further work is needed to fully document the approach (note, the approach will also need to be discussed with the full Board), my org colleagues are working on first drafting a high-level overview of the approach to be shared with the Council. If after considering the high-level overview, the Council wishes to work further on the relevant Supplemental Recommendations, I understand that the Caucus remains available and willing to continue building upon the collaborative relationship it shares with the Council. Best, Steve Steven Chan  VP, Policy Development Support & GNSO Relations Internet Corporation for Assigned Names and Numbers (ICANN) 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536  Email: steve.chan(a)icann.org<mailto:steve.chan@icann.org> Skype: steve.chan55 Mobile: +1.310.339.4410 Find out more about the GNSO by visiting: https://learn.icann.org/<https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…>

4 3