April 2024 - council - lists.icann.org

High-Level Overview of Singular/Plural Compromise
by Steve Chan 17 Apr '24

17 Apr '24

Dear Councilors, In my email to you all on 12 April, I indicated that my colleagues were working on a high-level overview of a possible approach for singular/plurals. Please see the message below from Lars Hoffmann, which also includes that high-level overview at the end of his message. Best, Steve Dear Councilors, I hope this finds you well. I am reaching out about the supplemental recommendation 24.3 (singular/plurals). Following the Board non-adoption of the SubPro PDP’s recommendation, the Small Team Plus has proposed a supplemental recommendation. While I cannot speak on behalf of the Caucus nor the Board, I can share that the Caucus has asked us (staff) to look at possible alternative solutions that achieve the goal of the recommendation, without some of the concerns that the Board has previously expressed around recommendation 24.3. Therefore, we put on our thinking hats and drew up a very high-level proposal that was well received by the Caucus. This morning (LA time, which was extremely late in Australia), we discussed this approach with the IRT Council liaisons (Susan and Anne), the former PDP WG co-chairs (Cheryl and Jeff), and Greg in his role of Council chair. Steve Chan also attended the call. I think I am correct in saying that after a good discussion with a lot of excellent questions from everyone, there is a general feeling in that group that the compromise should work and would generally achieve the same outcome that the supplemental rec 24.3 is aiming for but with lower costs and doing so more quickly, too. Below you will find a high-level outline of the approach. I would be happy to provide more details on this week’s Council call or at any other opportunity that suits the Council. I would kindly ask you to read the high-level summary with an open mind and if you have any questions, I will be happy to answer any preliminary ones on-list and, of course, during Thursday’s call, if the Council thinks there would be a benefit for me to dial in. If the Council believes this proposal ‘has legs’, the Council may want to consider deferring a vote on 24.3 only (the other supplemental recs could move forward as planned) and then, in the interest of time, staff could prepare in the coming days some more detailed strawperson language for the Small Team Plus and the Council Liaisons and/or staff to discuss. And, a final note, as the staff lead for the IRT, I believe that if the Small Team Plus continues it work as efficiently as it has done in the past, and if they collaborate with the Council liaisons and/or staff, there will be no impact on the overall implementation timeline of the next round if the Council withdrew the current 24.3 and voted on a new version no later than its meeting in July. Thank you so much and I am looking forward to working together on this complex but important issue. Best wishes, Lars The Singular/Plural Compromise: High-Level Overview 1. String Similarity review will remain a review solely based on visual similarity - assessing whether the two or more strings are visually confusingly similar. 2. ICANN org and IRT will discuss during implementation what measures - if any (based on recommendations) could be put into place to increase consistency of reviews compared to the 2012 round. But it will remain a visually-confusing test only. 3. Policy would provide that singular/plurals in the same language of any word will be put into contention, if so requested by “anyone”. If one of these strings is already delegated, then the applied-for string cannot proceed, if so requested by “anyone” 4. This means that singular and plurals of the same word in the same language COULD be delegated. 5. It puts the onus of reviewing applied for and existing strings on the applicants and the community members (i.e., “anyone”) to make a request to ICANN, based on such policy, to verify that two strings are singular/plural of each other in a specific language (to be specified by the ‘requestor). 6. ICANN would simply look up the relevant dictionary - in the language that the requestor specified - and if the two strings are similar/plural of reach other would act accordingly (put them into contention or inform one applicant that their application cannot proceed if it is the singular/plural in the same language of an existing string). 7. The period of ‘requesting’ such action from ICANN could stretch from reveal day until the contention sets are finalized - bearing in mind that subject to the outcome of string similarity, other strings may join a singular/plural contention set. For example, .bank and .banks may be joined by .banh. Please note again: if no one requests that .bank and .banks will be in contention and they are not caught in string similarity, and there is no .banh, then both .bank and .banks could be delegated. 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…>

3 2

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

17 Apr '24

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<https://gnso.icann.org/sites/default/files/file/field-file-attach/op-proced…> 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 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 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<https://gnso.icann.org/sites/default/files/policy/2024/minutes/minutes-gnso…> of the GNSO Council Meeting on 15 February 2024 were posted on 02 March 2024 Minutes<https://gnso.icann.org/sites/default/files/policy/2024/minutes/minutes-gnso…> 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<https://gnso.icann.org/en/council/project> and Action Item List. <https://community.icann.org/x/RgZlAg> Item 3: Consent Agenda (5 minutes) * GNSO Council Review of the GAC Communiqué<https://gnso.icann.org/sites/default/files/policy/2024/correspondence/dibia…> * GNSO Council Small Team Guidance Document<https://gnso.icann.org/sites/default/files/policy/2024/draft/updated-small-…> * 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<https://gnso.icann.org/sites/default/files/policy/2023/minutes/minutes-gnso…>, 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<https://docs.google.com/document/d/1yDgWIwKZqKk0WY0q7CS2pf7aD4VupCWV/edit>. The Small Team Plus has committed to a work plan<https://docs.google.com/document/d/1IhxKi0dvkS-a3ot7w8YG0iFxw4LiZuLz/edit> to address the recommendations not adopted by the Board. Following that plan, the Small Team agreed to Supplemental Recommendations<https://gnso.icann.org/sites/default/files/policy/2024/agenda/new-gtld-subp…> 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 <https://gnso.icann.org/sites/default/files/policy/2024/agenda/new-gtld-subp…> 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<https://gnso.icann.org/sites/default/files/filefield_48305/ppsai-final-07de…> on 8 December 2015, with subsequent Council adoption<http://gnso.icann.org/en/council/resolutions#201601> 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<https://gnso.icann.org/sites/default/files/file/field-file-attach/fouquart-…>: * 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<https://icann79.sched.com/event/1a1Cl/gnso-council-wrap-up>, 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<https://gnso.icann.org/sites/default/files/policy/2024/draft/icann80-gnso-d…> 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… 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/ 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<http://www.timeanddate.com/> and https://tinyurl.com/2xcnuymd

2 1

Update re: GAC Liaison Role | GNSO Council meeting 06 March 2024 and GNSO Council Wrap-Up meeting 07 March 2024
by Julie Hedlund 16 Apr '24

16 Apr '24

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

2 1

Draft GNSO Comment on Proposed Bylaws Amendment
by Susan Payne 15 Apr '24

15 Apr '24

Hi all Please see below draft of a GNSO comment which we might submit on the proposed Fundamental Bylaws change. My proposal is to keep this short and simple. Individual SG/Cs may have additional points they wish to make, and will hopefully do so in their own submissions, but the more detailed a draft GNSO comment is the more challenging it will be for everyone to get sign-off. GNSO COUNCIL COMMENTS ON THE PROPOSED FUNDAMENTAL BYLAWS AMENDMENT TO LIMIT ACCESS TO ACCOUNTABILITY MECHANISMS The GNSO Council (the Council) appreciates the opportunity to comment on the Proposed Fundamental Bylaws amendment, which proposes to create a mechanism for limiting or removing access to accountability mechanisms, such as the Request for Reconsideration (RFR) or Independent Review Process (IRP), when certain criteria are met, without the need for further formal Fundamental Bylaws amendments on a case by case basis. We anticipate that individual GNSO SGs and Cs will also submit their own, potentially more detailed, comments. The Council is concerned that a Fundamental Bylaws amendment in this broad form, which goes substantially wider than addressing CCWG-AP Recommendation 7, vests undue power in CCWGs to disallow accountability mechanisms, and creates an alternate path to amending a Fundamental Bylaw without the key community safeguard of requiring Empowered Community affirmative approval. This could create an opportunity for abuse. Further, the Council does not believe that such a broad amendment is necessary, bearing in mind that this has been, and should remain, an exceptional event. CCWG-AP Recommendation 7 is the first instance in nearly 8 years where a recommendation has been made to restrict access to the accountability mechanisms. As such, a streamlined process for managing future such recommendations is premature, at best. For these reasons, the Council does not support any Bylaws change in substantially the form being proposed and likely would be instructed by its constituent SGs and Cs to reject any formal vote, should this be put to the Empowered Community. Comments/edits welcome. S Susan Payne Head of Legal Policy [cid:image001.png@01DA8699.026DA7B0]<https://comlaude.com/> 28 Little Russell Street, London WC1A 2HN, UK T +44 (0) 20 7421 8250 Ext 255 comlaude.com<http://comlaude.com> Follow us on Linkedin<https://t-uk.xink.io/Tracking/Index/pRkAAFJfAADw_RQA0> and YouTube<https://t-uk.xink.io/Tracking/Index/bhkAAFJfAADw_RQA0> [cid:image002.png@01DA8699.026DA7B0]<https://www.linkedin.com/company/com-laude> [cid:image003.png@01DA8699.026DA7B0] <https://twitter.com/comlaude?lang=en> [cid:image004.png@01DA8699.026DA7B0] <https://www.facebook.com/ComLaude/> [cid:image005.png@01DA8699.026DA7B0] <https://www.youtube.com/@comlaude> [cid:image006.jpg@01DA8699.026DA7B0] ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the "Com Laude Group") does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 30 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 30 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 30 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com>

6 12

FYI | FW: [Ext] NEW: Preview the ICANN and IANA FY25 Operating Plans and Budget
by Terri Agnew 15 Apr '24

15 Apr '24

FYI [https://danh45uab.cc.rs6.net/on.jsp?ca=1ecb3d60-ed9a-43a0-b610-001f99be492b…] Monday, 15 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=001a8bBjB0…> 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 · Design and Translation Deadline · ICANN80 Community Childcare Grants Program Now Accepting Applications Information Sharing · NEW: Seeking Feedback on Phase 2 Expedited Policy Development Process on Internationalized Domain Names Webinars · NEW: Preview the ICANN and IANA FY25 Operating Plans and Budget · REMINDER: WSIS+20 Outreach Network Interactive Webinar on GDC Zero Draft Action Item · FRIDAY 🔥 ACTION ITEM: ICANN81 Fellowship Application Round Now Open · 🔥 ACTION ITEM: Call for NextGen@ICANN81 Applications Public Comment · NEW: Phase 2 Initial Report of the EPDP on Internationalized Domain Names · TODAY: Proposed Bylaws Updates to Limit Access to Accountability Mechanisms · 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 ICANN80 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=001a8bBjB0…> Information Sharing NEW: Seeking Feedback on Phase 2 Expedited Policy Development Process on Internationalized Domain Names The Expedited Policy Development Process (EPDP) Team is seeking input on its 20 preliminary recommendations, which focus on Phase 2 questions included in the EPDP Team's charter. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001a8bBjB0…> Webinars NEW: 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=001a8bBjB0…> 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=001a8bBjB0…> Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001a8bBjB0…> WSIS+20 Outreach Network Interactive Webinar on GDC Zero Draft The WSIS+20 Outreach Network will host two interactive webinars to discuss the zero draft of the Global Digital Compact and its implications. Wednesday 17 April 2024 | 14:00 - 15:00 UTC | Register [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001a8bBjB0…> Thursday 18 April 2024 | 01:00 - 02:00 UTC | Register [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001a8bBjB0…> Action Items FRIDAY 🔥 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=001a8bBjB0…> 🔥 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=001a8bBjB0…> Public Comment NEW: 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=001a8bBjB0…> Open for Submissions: 11 April 2024 Closed for Submissions: 21 May 2024 TODAY: Proposed Bylaws Updates to Limit Access to Accountability Mechanisms [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001a8bBjB0…> Open for Submissions: 27 February 2024 Closed for Submissions: 15 April 2024 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=001a8bBjB0…> 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=001a8bBjB0…> 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=001a8bBjB0…> Open for Submissions: 26 March 2024 Closed for Submissions: 06 May 2024 See upcoming proceedings [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001a8bBjB0…>. See other public consultations [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001a8bBjB0…>. Volume 6, Issue 28 | Archive [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001a8bBjB0…> | Next Issue: Thursday, 18 April 2024 STAY INFORMED: Subscribe here [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001a8bBjB0…>

1 0

FYI | FW: [Ext] NEW: Update on the Next ICANN Strategic Plan
by Terri Agnew 11 Apr '24

11 Apr '24

FYI [https://danh45uab.cc.rs6.net/on.jsp?ca=a786028a-9596-4e6b-8626-451b74cc87d3…] Thursday, 11 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=001gUIRIf0…> 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 · ICANN80 Community Childcare Grants Program Now Accepting Applications · Design and Translation Deadline Information Sharing · NEW: Update on the Next ICANN Strategic Plan Action Item · 🔥 ACTION ITEM: ICANN81 Fellowship Application Round Now Open · 🔥 ACTION ITEM: Call for NextGen@ICANN81 Applications Public Comment · MONDAY: Proposed Bylaws Updates to Limit Access to Accountability Mechanisms · 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 ICANN80 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=001gUIRIf0…> Information Sharing NEW: Update on the Next ICANN Strategic Plan During the community engagement sessions at ICANN79, we shared working the draft vision statement and the major focus areas that are guiding the Board's strategy development, and we received valuable feedback from the community. Read More. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gUIRIf0…> Action Items 🔥 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=001gUIRIf0…> 🔥 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=001gUIRIf0…> Public Comment MONDAY: Proposed Bylaws Updates to Limit Access to Accountability Mechanisms [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gUIRIf0…> Open for Submissions: 27 February 2024 Closed for Submissions: 15 April 2024 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=001gUIRIf0…> 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=001gUIRIf0…> 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=001gUIRIf0…> Open for Submissions: 26 March 2024 Closed for Submissions: 06 May 2024 See upcoming proceedings [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gUIRIf0…>. See other public consultations [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gUIRIf0…>. Volume 6, Issue 27 | Archive [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gUIRIf0…> | Next Issue: Monday, 15 April 2024 STAY INFORMED: Subscribe here [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gUIRIf0…>

1 0

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

11 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 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

Interim Update on Mechanism(s) to Address Latin Diacritics
by Steve Chan 10 Apr '24

10 Apr '24

Dear Councilors, As you may have seen, the April Council meeting is scheduled to have an update on the research and analysis ICANN org has performed to understand the mechanism(s) that might be available to progress the work related to Latin diacritics. While we will provide a more comprehensive update during the Council meeting, we wanted to share an early preview of the update, as it may have implications on the Council’s vote on a subset of the SubPro Supplemental Recommendations. In brief, our recommended approach is for the Council to consider modifying/amending the non-adopted recommendations related to string similarity (i.e., Recommendations 24.3 and 24.5) if it wants to take up the issue of Latin diacritics. Under the ICANN Bylaws and GNSO Operating Procedures, there are two avenues to pursue this path, which are either Section 16 of the PDP Manual<https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-2-p…> (see page 10) or the Supplemental Recommendation process, as employed by the Small Team Plus. With the Council’s consideration and potential adoption of Supplemental Recommendations 24.3A, 24.3B, and 24.3C during its April meeting, there may be challenges to using either Section 16 or the Supplemental Recommendation process to progress the Latin diacritics issues: 1. Section 16: The PDP Manual states that, “approved GNSO Council policies may be modified or amended by the GNSO Council at any time prior to the final approval by the ICANN Board…”. If the Council approves Supplemental Recommendations 24.3A, 24.3B, and 24.3C AND they are adopted by the ICANN Board, this option would no longer be available (i.e., “final approval” will have occurred). 2. Supplemental Recommendations: If the Council approves Supplemental Recommendations 24.3A, 24.3B, and 24.3C, the Council would not be able to develop further Supplemental Recommendations related to Latin diacritics. We understand the Council has committed to taking action on the Supplemental Recommendations during its April meeting, so we believe it is important to provide you with this information in advance of your meeting for effective planning and decision-making. Please let us know if you have any questions. 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…>

7 6

GNSO Council Portfolio Management Tool Suite - 18 April 2024 Meeting
by Steve Chan 08 Apr '24

08 Apr '24

Dear Councilors, Please see links below to the latest version of the GNSO Council’s Portfolio Management Tool Suite for the meeting on 18 April 2024. Agenda: * https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+Agen… Motions: * https://community.icann.org/display/gnsocouncilmeetings/Motions+2024-04-18 Links to the Program Suite: * Program/Project Management Framework (PPMF): https://community.icann.org/x/0YvzC * Portfolio Management Tool (PMT): https://community.icann.org/x/04vzC * **Action/Decision Radar (ADR): https://community.icann.org/x/14vzC * **Project List (PL): https://community.icann.org/x/1YvzC * **Action Items (AIs): https://community.icann.org/x/RgZlAg * Council Small Teams (CSTs): https://community.icann.org/display/gnsocouncilmeetings/GNSO+Council+Small+… * ** denotes the required three work products for review by Councilors in preparation for monthly meetings Key Program Suite Structural Changes for this Period: * None for this period. Key Project Changes or Milestones for this Period: * GNSO Council Review of the GAC Communique * GNSO Council – Small Team Guidance Document * EDDP/ERRP – GNSO Council deferral of a Policy Status Report on the Expiration Policies * SubPro – GNSO Council consideration of the SubPro Supplemental Recommendations * GNSO_ADR – GNSO Council review of the Action Decision Radar * EPDP_IDN_P2 – Informational: EPDP on IDNs Phase 2 report publication for public comment * Active Project Packages: * EPDP_IDN: https://community.icann.org/x/cYbOCg * GNSO_TPR: https://community.icann.org/x/MQDQCQ * IRT Status Page: https://www.icann.org/policy/implementation Key Project Activities for May/June 2024: * IDN_Diacritics – GNSO Council to consider possible Issue Report. * CCOICI – GNSO Council to determine next steps on Continuous Improvements. * IRP-IoT – GNSO Council to consider submitting comments on the Independent Review Process rules and procedures Please let staff know if you have any questions. 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…>

1 0

REMINDER | Document and Motion deadline | Monday, 08 April 2024 at 23:59 UTC for GNSO Council Meeting 18 April 2024 at 21:00 UTC
by Terri Agnew 08 Apr '24

08 Apr '24

Dear all, Reports, motions, and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Monday, 08 April 2024 at 23:59 UTC) of the GNSO Council Meeting on Thursday, 18 April 2024 at 21:00 UTC. Motions should be sent to the Council mailing list by a councilor and will then be posted on the Motions Wiki at: https://community.icann.org/x/AYDyEg Thank you. Kind regards, Terri Policy Team Supporting the GNSO

1 2