May 2025 - council - lists.icann.org

REMINDER | Meeting Invitation | GNSO Council Meeting | Thursday, 15 May2025
by Terri Agnew May 14, 2025

May 14, 2025

Dear all, The GNSO Council meeting is scheduled on Thursday, 15 May 2025 at 05: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…> and the ICANN Community Anti-Harassment Policy<https://www.icann.org/resources/pages/community-anti-harassment-policy-2017…> Visit the Wiki Agenda page: https://icann-community.atlassian.net/wiki/x/GKafBg Check your time zone: https://tinyurl.com/knke3w 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/91048235847?pwd=bmEHjk0uYT3sR2DIoE0c0yw4HKbM6O.1 Passcode: mkt7*ULa9b If joining Zoom via Zoom App the following will be required: Webinar ID: 910 4823 5847 Passcode: 9213420189 Or One tap mobile : +13462487799,,91048235847#,,,,*9213420189# US (Houston) +16699006833,,91048235847#,,,,*9213420189# US (San Jose) If you are joining via audio only: International numbers available: https://icann.zoom.us/u/a6JrPP2u5 Observers are welcome to join, they will be in a read-only and listen-only mode. Please note that all documents<https://icann-community.atlassian.net/wiki/x/0KefBg> 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

Council Agenda Item 7: Implementation of SubPro Rec 36.4
by Susan Payne May 14, 2025

May 14, 2025

Dear Council colleagues, This relates to agenda item 7 at our Council meeting of 15 May 2025. As the Co-Liaisons to the SubPro IRT, we need to raise a disagreement between staff and the IRT community group over the proposed implementation language in the Next Round Base Registry Agreement of one of the Board-adopted recommendations (SubPro Recommendation 36.4). ICANN's proposed language to implement Recommendation 36.4 is as follows: 4.3(f) ICANN may, upon notice to Registry Operator, terminate this Agreement if (i) ICANN receives a complaint, or ICANN otherwise becomes aware, that Registry Operator is engaging in fraudulent or deceptive business practices in provision of Registry Services under this Agreement for the TLD; and (ii) such fraudulent or deceptive business practices have resulted in an adverse action or decision and a failure to remediate finding against the Registry Operator by a relevant governmental consumer protection authority or authorities with jurisdiction over the matter, or Registry Operator is the subject of a determination that ICANN reasonably deems as the substantive equivalent of any of the foregoing; provided that, if ICANN receives a complaint related to the foregoing, all available relevant documentation from such adverse action or decision and a failure to remediate finding must be included as part of the complaint. Rec 36.4 had full consensus in the SubPro PDP WG, and was adopted by the ICANN Board. It provides as follows (in bold and divided into bullets by us for ease of reading). Our text in red explains why the IRT concluded that the above draft does NOT comply with the Board-adopted Recommendation: * ICANN must add a contractual provision [to the Next Round Registry Agreement] stating that the registry operator will not engage in fraudulent or deceptive practices. It is not disputed that such fraudulent or deceptive practices should be in the provision of Registry Services. The added contractual obligation is a key part of Rec 36.4, because the PICDRP Panel in the .Feedback case found that there was such conduct in the operation of the Registry, but that there was no contractual provision whereby the Registry Operator committed not to engage in such conduct. Consequently the Panel considered itself unable to apply a sanction against the Registry Operator. In spite of the ramifications of the .Feedback decision, which Rec 36.4 sought to remedy, ICANN proposes NOT to include such a provision in the RA. * In the event that ICANN receives an order from a court that a registry has engaged in fraudulent or deceptive practices, ICANN may issue a notice of breach for such practices and allow the registry to cure such breach in accordance with the Registry Agreement. ICANN proposes to comply but provides in its draft language that the court or other governmental consumer protection authority order must include a finding that the fraudulent or deceptive practice has not been remediated by the Registry Operator. As drafted (and this may simply be a drafting error) this is highly unlikely since no further order would normally follow in the event the Registry Operator remediates the problem. Of course the Registry Operator could prove up remediation to ICANN but a court "finding" of a lack of remediation should not be required here. Rec 36.4 envisages ICANN making the determination of lack of remediation, after having given the RO the opportunity to cure the breach. * Further, in the event that there is a credible allegation by any third party of fraudulent or deceptive practices, other than as set forth in above, ICANN may, at its discretion, either: o commence dispute resolution actions under the Registry Agreement (Currently Article 5 of the Registry Agreement), or o appoint a panel under the PICDRP. ICANN proposes NOT to utilise either of these alternative dispute resolution processes, where there is a credible allegation but no court order. Instead, ICANN proposes to treat such a situation as equivalent to there being a Court Order, and going straight to termination without allowing the registry Operator to defend themselves via a DRP. Sub Pro had full consensus on the alternatives to be pursued in the absence of a court order. The Recommendation provides for ICANN, in its discretion, to pursue enforcement either via (a) dispute resolution under Article 5 or (b) appointment of a PICDRP panel (the latter being possible only if the contractual provision not to engage, set out in bullet 1, is dealt with in the RA as a PIC/RVC). * For the purposes of a credible claim of fraudulent or deceptive practices the reporter (as defined by the PICDRP) must only specifically state the grounds of the alleged non-compliance, but not that it personally has been harmed as a result of the registry operator's act or omission. ICANN proposes NOT to include this language. By way of additional detail, we have (attached): * an explanation from Karla Hakansson of how staff propose to implement Rec 36.4 and why * a detailed note from Jeff Neuman, one of the SubPro Co-chairs, summarising what Rec 36.4 says, the rationale for this recommendation, and how the staff proposed implementation differs from what was recommended. Cheryl Langdon-Or, the other Co-chair, supports this note. Karla's attached note states that Rec 36.4 requires "ICANN (or ICANN with the assistance of a PICDRP panel) to make the substantive determinations as to whether a registry operator in fact engaged in fraudulent or deceptive practices", and that this is outside of ICANN's scope. The IRT disagrees with that interpretation. If there is a credible allegation (rather than an actual court finding) ICANN may proceed via its choice of dispute resolution process. In other words, ICANN merely needs to believe there is sufficient evidence to bring the case, which is in its discretion, it is the DR panel that makes the substantive determination. We believe it is the full consensus of the SubPro IRT that staff's proposed implementation does not meet Rec 36.4, in a number of ways (as set out in more detail above and in the Co-chairs note). IRT members have expressed this concern on multiple calls since last November, and (to the best of our recollection) no IRT members have expressed an opposing view. One member of the IRT has suggested that this issue needs to be addressed at the Board level. What action might Council take? We do not believe this is a situation where the PDP recommendation is unclear, and therefore this isn't a case where clarification or guidance would assist. Staff are aware of the meaning and intent of the recommendation, but do not intend to implement it as written. As per Karla's attached note, ICANN believes it has followed the "intent" of the Recommendation. The IRT disagrees. We believe that Council should provide input to ICANN Staff in charge of the IRT confirming Council's position that Rec 36.4 is clear, is designed to address an actual omission that has bearing on the Security and Stability of the Internet, and should be implemented as written. Accordingly, the current proposed implementation is unacceptable. We also believe it would be helpful for this communication to be copied to the Board, perhaps with a request to discuss this in Prague. Susan and Anne Joint Council Liaisons to SubPro IRT ________________________________ 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 28 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 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 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>

2 2

Discussion Paper on Mechanism to Address EPDP-IDNs Phase 1 Recommendation 3.17
by Steve Chan May 14, 2025

May 14, 2025

Dear Councilors, Pursuant to the Council’s April meeting, staff was tasked with providing a briefing document that helps evaluate several options on how to address the issues in implementing EPDP-IDNs Phase 1 Recommendation 3.17. Please find the proposed paper attached, which can be discussed during the Council’s May meeting (and on list of course). 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…>

3 10

Consent Agenda motion for 15 May 2025 GNSO Council meeting
by Caitlin Tubergen May 13, 2025

May 13, 2025

SENT ON BEHALF OF TOMSLIN SAMME-NLAR WHO IS CURRENTLY UNABLE TO SEND Dear Councilors, Please find attached the consent agenda motion (aspirational statement) for the upcoming May GNSO Council meeting. Thank you. Best regards, Caitlin

4 5

FW: ISPCP GNSO Councilor Election results
by Terri Agnew May 13, 2025

May 13, 2025

Dear all, Please see the information below on ISPCP GNSO Councilor Election results. Congratulations to Susan M! All the best, Kind regards, Terri Policy Team Supporting the GNSO From: "philippe.fouquart(a)orange.com" <philippe.fouquart(a)orange.com> Date: Tuesday, May 13, 2025 at 3:00 AM To: GNSO-Secs <gnso-secs(a)icann.org> Cc: Susan Mohr <susan.mohr(a)lumen.com>, "Novoa, Osvaldo via ISPCP-Leadership" <ispcp-leadership(a)icann.org> Subject: ISPCP GNSO Councilor Election results Dear GNSO Secretariat, It gives me great pleasure to announce the election of Susan Mohr as the new ISPCP GNSO Councilor after the ICANN84 AGM. Regards, Philippe Fouquart ISPCP Chair ____________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

1 0

FW: [Ext] NEW: ICANN Board Adopts FY26–30 Operating Plan and FY26 Operating Plan and Budget
by Julie Bisland May 12, 2025

May 12, 2025

FYI: From: ICANN Community Digest <digest(a)icann.ccsend.com> Reply-To: "policyinfo(a)icann.org" <policyinfo(a)icann.org> Date: Monday, May 12, 2025 at 10:07 AM To: Julie Bisland <julie.bisland(a)icann.org> Subject: [Ext] NEW: ICANN Board Adopts FY26–30 Operating Plan and FY26 Operating Plan and Budget [https://danh45uab.cc.rs6.net/on.jsp?ca=65b9bdb1-5dc1-4524-883a-7c5d49919956…] Monday, 12 May 2025 ICANN Community Digest [https://files.constantcontact.com/304b3fd3501/31f30ab5-1445-45c3-aef7-c0ea4…] Click here to learn more about the New gTLD Program [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ReNhKcg…> Applicant Support Program [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ReNhKcg…> Registry Service Provider Evaluation Program [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ReNhKcg…> The ICANN organization Policy Development Support function publishes this twice-weekly digest to help ICANN community groups track requests and follow updates. 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 ICANN83 · ICANN83 Prep Week Schedule Now Available Information Sharing · NEW: ICANN Board Adopts FY26–30 Operating Plan and FY26 Operating Plan and Budget · NEW: An Update From the 2025 Nominating Committee · REMINDER: ICANN RSP Pre-Evaluation Program Closes 20 May 2025 · Next Round Champions Toolkit Available in the Six ICANN Languages · ICANNWiki Seeking Volunteers 🚨 Action Items 🚨 · TOMORROW: Call for Expressions of Interest: ICANN 2026 NomCom Chair and Chair-Elect · ICANN Call for Nominations: Universal Acceptance Expert Working Group · Call for ASP Mentors Public Comment · TODAY: FY26-FY30 Middle East Regional Plan · ONE WEEK FROM TODAY: How We Meet: Reviewing the Implementation of the ICANN Public Meetings Strategy · Governance Document for the Recognition, Maintenance, and Derecognition of RIRs · Customer Standing Committee (CSC) changes Process for Amending the IANA SLAs · Africa Regional Plan for Fiscal Years 2026-2030 · Transfer Policy Review Working Group Final Report for ICANN Board Consideration Events · These events occur in May 2025. ICANN83 ICANN83 Prep Week Schedule Now Available ICANN83 Prep Week will be held Tuesday through Wednesday, 27–28 May 2025. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ReNhKcg…> Information Sharing NEW: ICANN Board Adopts FY26–30 Operating Plan and FY26 Operating Plan and Budget The FY26 Operating Plan and Budget sets forth the focus of efforts and organizational commitments for the fiscal year starting 1 July 2025 and ending 30 June 2026. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ReNhKcg…> NEW: An Update From the 2025 Nominating Committee Currently, the NomCom is in the assessment phase of the selection cycle. During this phase, NomCom delegates undertake a series of steps to evaluate the applications. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ReNhKcg…> REMINDER-ICANN RSP Pre-Evaluation Program Closes 20 May 2025 The pre-evaluation application submission period of the ICANN Registry Service Provider (RSP) Evaluation Program for the New Generic Top-level Domains (gTLD) Program: Next Round is set to close [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ReNhKcg…> at 18:00 UTC on 20 May 2025. Launched on 19 November 2024, the program streamlines gTLD applications by separately evaluating the technical aspects of operating the gTLD from the application for the gTLD label. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ReNhKcg…> Next Round Champions Toolkit Available in the Six ICANN Languages ICANN is working with the community to identify potential Applicant Support Program (ASP) applicants – especially in regions that are currently under-represented in ICANN. If you are interested in helping to raise awareness among your own contacts or communities, please use the materials in the Next Round Champions Toolkit [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ReNhKcg…>. To stay up to date on the New gTLD Program: Next Round and ASP, join the mailing list: nextroundinfo(a)icann.org. ASP leads, targets, and ideas can be sent to engagement.newgTLDprogram(a)icann.org<mailto:engagement.newgTLDprogram@icann.org>. ICANNWiki Seeking Volunteers ICANNWiki is seeking volunteers to assist with creating and editing articles and content for the site. Do you want to help? Getting started is as simple as requesting an account [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ReNhKcg…>. Then, make sure to read the short content guide [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ReNhKcg…> to get a feel for what belongs in the wiki. Also, feel free to take a look at some data source suggestions [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ReNhKcg…> on where to find reliable data. Happy editing! Action Items TOMORROW: Call for Expressions of Interest: ICANN 2026 NomCom Chair and Chair-Elect The NomCom Chair is responsible for organizing the NomCom in its activities to select certain ICANN Board members and individuals who will serve in key leadership positions within ICANN's SOs and ACs in accordance with ICANN's Bylaws. Deadline: 13 May 2025 Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ReNhKcg…> ICANN Call for Nominations: Universal Acceptance Expert Working Group ICANN is inviting the ALAC, ccNSO, GAC, GNSO, and SSAC to each submit one nomination by 25 June 2025. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ReNhKcg…> Call for ASP Mentors ICANN is seeking volunteer mentors who would like to offer their expertise to supported applicants as part of the ASP in the new gTLD Program: Next Round [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ReNhKcg…>. ICANN is looking for mentors who can share insights and experience across ICANN Languages (Arabic, Chinese, English, French, Russian, or Spanish) to support diverse gTLD applicants. Mentors may play a role in: advising applicants on navigating the gTLD application process and DNS industry; identifying resources; providing guidance; sharing experiences as appropriate; and helping supported applicants navigate the ICANN community and Public Meetings. If you or someone in your network might be interested, please refer to the mentor registration announcement [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ReNhKcg…> for more information. Questions about the ASP or becoming a supported applicant Mentor can be sent to globalsupport(a)icann.org<mailto:globalsupport@icann.org>. Public Comment TODAY: FY26-FY30 Middle East Regional Plan [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ReNhKcg…> Submissions Opening Date: Monday, 31 March 2025 Submissions Closing Date: Monday, 12 May 2025 ONE WEEK FROM TODAY: How We Meet: Reviewing the Implementation of the ICANN Public Meetings Strategy [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ReNhKcg…> Submissions Opening Date: Wednesday, 9 April 2025 Submissions Closing Date: Monday, 19 May 2025 Governance Document for the Recognition, Maintenance, and Derecognition of RIRs [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ReNhKcg…> Submissions Opening Date: 14 April 2025 Submissions Closing Date: 27 May 2025 Customer Standing Committee (CSC) changes Process for Amending the IANA SLAs [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ReNhKcg…> Submissions Opening Date: Tuesday, 22 April 2025 Submissions Closing Date: Monday, 02 June 2025 Africa Regional Plan for Fiscal Years 2026-2030 [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ReNhKcg…> Submissions Opening Date: Friday, 25 April 2025 Submissions Closing Date: Friday, 06 June 2025 Transfer Policy Review Working Group Final Report for ICANN Board Consideration [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ReNhKcg…> Submissions Opening Date: Monday, 28 April 2025 Submissions Closing Date: Monday, 16 June 2025 See upcoming proceedings [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ReNhKcg…>. See other public consultations [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ReNhKcg…>. Events These events occur in May 2025. To learn more, please visit our community engagement calendar [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ReNhKcg…>. · SALON OSIANE 2025 · The Africa Tech Policy Summit 2025 · Kenya Internet Governance Forum (Kenya IGF) 2025 · Meet & Greet with Kurtis Lindqvist: ICANN's President & CEO · East African Internet Governance Forum 2025 Volume 7, Issue 36 | Archive [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ReNhKcg…> | Next Issue: Thursday, 15 May 2025 STAY INFORMED: Subscribe here [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ReNhKcg…>

1 0

Fwd: Three Notices to Empowered Community on ICANN and IANA Plans
by Tomslin Samme-Nlar May 12, 2025

May 12, 2025

Dear councillors, FYI Remain blessed, Tomslin ---------- Forwarded message --------- From: John Jeffrey <john.jeffrey(a)icann.org> Date: Fri, 9 May 2025 at 06:48 Subject: Three Notices to Empowered Community on ICANN and IANA Plans To: ecadmin(a)icann.org <ecadmin(a)icann.org> Cc: Tripti Sinha <tripti.sinha(a)board.icann.org>, Kurtis Lindqvist < kurtis.lindqvist(a)icann.org>, jzuck(a)innovatorsnetwork.org < jzuck(a)innovatorsnetwork.org>, secretariat(a)nro.net <secretariat(a)nro.net>, alejandra.reynoso(a)gmail.com <alejandra.reynoso(a)gmail.com>, nicustkd(a)gmail.com <nicustkd(a)gmail.com>, mesumbeslin(a)gmail.com < mesumbeslin(a)gmail.com> Dear Empowered Community Administration, Attached please find the Secretary’s Notice of Board Approval of the IANA FY26 Operating Plan and Budget, Notice of Board Approval of the ICANN FY26 Operating Plan and Budget, and Notice of Board Approval of the ICANN FY26-30 Operating and Financial Plan. Thanks, John Jeffrey *John O. Jeffrey * *General Counsel and Secretary* *Internet Corporation for Assigned Names and Numbers (ICANN)* *12025 Waterfront Drive, Suite 300* *Los Angeles, CA 90094-2536* *Direct: (310) 404-6001* *John.jeffrey(a)icann.org <John.jeffrey(a)icann.org>* [image: signature_1204561708]

1 0

FW: [Ext] NEW: ICANN83 Prep Week Schedule Now Available
by Devan Reed May 8, 2025

May 8, 2025

FYI From: ICANN Community Digest <digest(a)icann.ccsend.com> Reply-To: "policyinfo(a)icann.org" <policyinfo(a)icann.org> Date: Thursday, May 8, 2025 at 10:05 AM To: Devan Reed <devan.reed(a)icann.org> Subject: [Ext] NEW: ICANN83 Prep Week Schedule Now Available [https://danh45uab.cc.rs6.net/on.jsp?ca=a0eda642-3cd0-4b81-b1f2-d3d0866a06d3…] Thursday, 08 May 2025 ICANN Community Digest [https://files.constantcontact.com/304b3fd3501/31f30ab5-1445-45c3-aef7-c0ea4…] Click here to learn more about the New gTLD Program [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BWaiSw0…> Applicant Support Program [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BWaiSw0…> Registry Service Provider Evaluation Program [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BWaiSw0…> The ICANN organization Policy Development Support function publishes this twice-weekly digest to help ICANN community groups track requests and follow updates. 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 ICANN83 · NEW: ICANN83 Prep Week Schedule Now Available Information Sharing · NEW: Approved Resolutions | Regular Meeting of the ICANN Board | 3 May 2025 · NEW: ICANN Call for Nominations: Universal Acceptance Expert Working Group · REMINDER: ICANN RSP Pre-Evaluation Program Closes 20 May 2025 · Next Round Champions Toolkit Available in the Six ICANN Languages · ICANNWiki Seeking Volunteers 🚨 Action Items 🚨 · TOMORROW: Call for Applications: NextGen@ICANN84 · TUESDAY: Call for Expressions of Interest: ICANN 2026 NomCom Chair and Chair-Elect · SUNDAY: ICANN Invites Applications for the Asia Pacific Internet Governance Academy 2025 · Call for ASP Mentors Public Comment · MONDAY: FY26-FY30 Middle East Regional Plan · How We Meet: Reviewing the Implementation of the ICANN Public Meetings Strategy · Governance Document for the Recognition, Maintenance, and Derecognition of RIRs · Customer Standing Committee (CSC) changes Process for Amending the IANA SLAs · Africa Regional Plan for Fiscal Years 2026-2030 · Transfer Policy Review Working Group Final Report for ICANN Board Consideration Events · These events occur in May 2025. ICANN83 NEW: ICANN83 Prep Week Schedule Now Available ICANN83 Prep Week will be held Tuesday through Wednesday, 27–28 May 2025. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BWaiSw0…> Information Sharing NEW: Approved Resolutions | Regular Meeting of the ICANN Board | 3 May 2025 Please find the Approved Resolutions from the 3 May 2025 Regular Meeting of the ICANN Board here [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BWaiSw0…>. NEW: ICANN Call for Nominations: Universal Acceptance Expert Working Group ICANN is inviting the ALAC, ccNSO, GAC, GNSO, and SSAC to each submit one nomination by 25 June 2025. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BWaiSw0…> REMINDER-ICANN RSP Pre-Evaluation Program Closes 20 May 2025 The pre-evaluation application submission period of the ICANN Registry Service Provider (RSP) Evaluation Program for the New Generic Top-level Domains (gTLD) Program: Next Round is set to close [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BWaiSw0…> at 18:00 UTC on 20 May 2025. Launched on 19 November 2024, the program streamlines gTLD applications by separately evaluating the technical aspects of operating the gTLD from the application for the gTLD label. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BWaiSw0…> Next Round Champions Toolkit Available in the Six ICANN Languages ICANN is working with the community to identify potential Applicant Support Program (ASP) applicants – especially in regions that are currently under-represented in ICANN. If you are interested in helping to raise awareness among your own contacts or communities, please use the materials in the Next Round Champions Toolkit [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BWaiSw0…>. To stay up to date on the New gTLD Program: Next Round and ASP, join the mailing list: nextroundinfo(a)icann.org. ASP leads, targets, and ideas can be sent to engagement.newgTLDprogram(a)icann.org<mailto:engagement.newgTLDprogram@icann.org>. ICANNWiki Seeking Volunteers ICANNWiki is seeking volunteers to assist with creating and editing articles and content for the site. Do you want to help? Getting started is as simple as requesting an account [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BWaiSw0…>. Then, make sure to read the short content guide [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BWaiSw0…> to get a feel for what belongs in the wiki. Also, feel free to take a look at some data source suggestions [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BWaiSw0…> on where to find reliable data. Happy editing! Action Items TOMORROW: Call for Applications: NextGen@ICANN84 ICANN wants to hear from university students living and studying in the Asia Pacific region who are interested in the future of the Internet and participating in the Public Meeting. Deadline: 09 May 2025 Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BWaiSw0…> TUESDAY: Call for Expressions of Interest: ICANN 2026 NomCom Chair and Chair-Elect The NomCom Chair is responsible for organizing the NomCom in its activities to select certain ICANN Board members and individuals who will serve in key leadership positions within ICANN's SOs and ACs in accordance with ICANN's Bylaws. Deadline: 13 May 2025 Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BWaiSw0…> SUNDAY: ICANN Invites Applications for the Asia Pacific Internet Governance Academy 2025 Launched in 2016, APIGA is a five-day capacity-development program focused on Internet governance (IG) targeting youths in the Asia-Pacific (APAC) region. Deadline: Sunday, 11 May, at 23:59 KST (14:00 UTC) Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BWaiSw0…> Call for ASP Mentors ICANN is seeking volunteer mentors who would like to offer their expertise to supported applicants as part of the ASP in the new gTLD Program: Next Round [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BWaiSw0…>. ICANN is looking for mentors who can share insights and experience across ICANN Languages (Arabic, Chinese, English, French, Russian, or Spanish) to support diverse gTLD applicants. Mentors may play a role in: advising applicants on navigating the gTLD application process and DNS industry; identifying resources; providing guidance; sharing experiences as appropriate; and helping supported applicants navigate the ICANN community and Public Meetings. If you or someone in your network might be interested, please refer to the mentor registration announcement [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BWaiSw0…> for more information. Questions about the ASP or becoming a supported applicant Mentor can be sent to globalsupport(a)icann.org<mailto:globalsupport@icann.org>. Public Comment MONDAY FY26-FY30 Middle East Regional Plan [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BWaiSw0…> Submissions Opening Date: Monday, 31 March 2025 Submissions Closing Date: Monday, 12 May 2025 How We Meet: Reviewing the Implementation of the ICANN Public Meetings Strategy [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BWaiSw0…> Submissions Opening Date: Wednesday, 9 April 2025 Submissions Closing Date: Monday, 19 May 2025 Governance Document for the Recognition, Maintenance, and Derecognition of RIRs [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BWaiSw0…> Submissions Opening Date: 14 April 2025 Submissions Closing Date: 27 May 2025 Customer Standing Committee (CSC) changes Process for Amending the IANA SLAs [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BWaiSw0…> Submissions Opening Date: Tuesday, 22 April 2025 Submissions Closing Date: Monday, 02 June 2025 Africa Regional Plan for Fiscal Years 2026-2030 [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BWaiSw0…> Submissions Opening Date: Friday, 25 April 2025 Submissions Closing Date: Friday, 06 June 2025 Transfer Policy Review Working Group Final Report for ICANN Board Consideration [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BWaiSw0…> Submissions Opening Date: Monday, 28 April 2025 Submissions Closing Date: Monday, 16 June 2025 See upcoming proceedings [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BWaiSw0…>. See other public consultations [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BWaiSw0…>. Events These events occur in May 2025. To learn more, please visit our community engagement calendar [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BWaiSw0…>. · APAC DNS Forum 2025 · SALON OSIANE 2025 · The Africa Tech Policy Summit 2025 · Kenya Internet Governance Forum (Kenya IGF) 2025 · Meet & Greet with Kurtis Lindqvist: ICANN's President & CEO · East African Internet Governance Forum 2025 Volume 7, Issue 35 | Archive [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BWaiSw0…> | Next Issue: Monday, 12 May 2025 STAY INFORMED: Subscribe here [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BWaiSw0…>

1 0

Re: Next steps for the Whois Accuracy Implementation Advisory Group
by Demetriou, Samantha May 8, 2025

May 8, 2025

Hi all, and apologies for the delay in providing our feedback. The RySG agrees with the RrSG and IPC that the best option at this time is to defer the review of the Procedure indefinitely. Thanks, Sam From: Susan Payne via council <council(a)icann.org> Reply-To: Susan Payne <susan.payne(a)comlaude.com> Date: Friday, May 2, 2025 at 8:17 PM To: "DiBiase, Gregory" <dibiase(a)amazon.com>, "Council(a)icann.org" <council(a)icann.org> Subject: [EXTERNAL] [council] Re: Next steps for the Whois Accuracy Implementation Advisory Group Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Thanks Greg. The IPC shares that view. We don’t believe we should retire the process, since there might still be a need for it in future, but don’t think this warrants community work at this time. Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 Ext 255 Follow us on LinkedIn and YouTube From: DiBiase, Gregory via council <council(a)icann.org> Sent: 01 May 2025 15:19 To: Council(a)icann.org Subject: [council] Re: Next steps for the Whois Accuracy Implementation Advisory Group Hi Councilors, The RrSG would like to defer indefinitely (see option 1 below). There may be a scenario that arises in which this procedure is needed, and we can revisit at that time, but at the moment, registrars do not believe this work constitutes a productive use of our resources. Thanks, Greg From: DiBiase, Gregory via council <council(a)icann.org> Sent: Monday, April 21, 2025 9:28 AM To: Council(a)icann.org Subject: [EXTERNAL] [council] Next steps for the Whois Accuracy Implementation Advisory Group 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. Dear Councilors, During our April meeting, we discussed potential next steps for the Whois Accuracy Implementation Advisory Group. Background and potential options are below (the meeting recording includes additional). Please discuss with your SGs and provide feedback by Friday, 2 May. What is this procedure? ICANN’s Procedure For Handling Registration Data Directory Services Conflicts with Privacy Law is a procedure that allows Contracted Parties to demonstrate when they are prevented by local laws from fully complying with the provisions of ICANN contracts regarding personal data in RDDS. After receiving a recommendation from the 2003 Whois Task Force, the GNSO launched a PDP on this topic in 2005, and ICANN org implemented a procedure in 2006. The procedure was updated in 2017 to include an alternative trigger. Why is the Council considering this now? Following the addition of the new alternative trigger to the procedure in 2017, the GNSO Council was set to review the procedure by launching a PDP. However, because the EPDP on the Temporary Specification was engaged in parallel work, the GNSO Council decided to pause the call for volunteers until the EPDP Team delivered its report. Following the publication of the Final Report, ICANN org and Contracted Parties agreed to prioritize their work on the Data Processing Specification prior to revisiting the Conflicts Procedure. ICANN org published the Data Processing Specification (DPS) in January 2025. Now that the DPS is complete, the Council is considering if/how it should proceed on reviewing the Conflicts Procedure. Questions to consider? As discussed during the Council meeting and brought up councilors, some of the factors to consider in determining how to proceed include: Do Contracted Parties (the parties who would use the procedure) believe this is an urgent need as no Contracted Parties have used the procedure in years? Does the new Registration Data Policy, which becomes effective in August, obviate the need for a modification to the procedure? Does the Council believe this should be a priority, which would require other work to be de-prioritized? Potential Options Defer/Leave procedure as is If Councilors (particularly Contracted Parties) do not believe this procedure needs an urgent modification, further work could be: Deferred indefinitely until the Community communicates a need to review (in other words, leave the procedure alone until the Community informs Council it needs to be reviewed.) Deferred for a finite amount of time (1 year, 2 years, etc.) to revisit if updates may be needed Proceed with original plan - ICANN org to draft modification in consultation with CPs If Councilors (particularly Contracted Parties) believe this work is urgent and important, the Council could request ICANN org to draft a modification to the procedure in consultation with Contracted Parties before sharing with the Council. (As noted above, due to resource constraints, the Council would need to determine what work can be de-prioritized in order to prioritize this work.) Terminate/Retire procedure During the meeting, some councilors noted it may be worth terminating/retiring this procedure due to flaws. It is important to note that the termination/retirement of the procedure would require further policy work as this procedure is the product of GNSO policy recommendations. If the Council does not want to extend resources on this procedure at this time, it may be worth exploring Option 1. Deadline for Feedback? Please socialize with your respective SG/Cs and let the Council know how you think it should proceed by Friday, 2 May. Thanks, Greg 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 28 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 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 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

2 1

FW: Urgent Requests for Disclosure of Registration Data [ ref:!00D1a0Y7OU.!500Qk0H49r9:ref ]
by Terri Agnew May 7, 2025

May 7, 2025

Hello GNSO Council, Please find a letter attached re: Urgent Requests for Disclosure of Registration Data This will be posted shortly on the GNSO Correspondence webpage: https://gnso.icann.org/en/council/correspondence/2025. Thank you. Kind regards, Terri Policy Team Supporting the GNSO From: Correspondence <correspondence(a)ces.icann.org> Date: Tuesday, May 6, 2025 at 12:03 PM To: "dibiase(a)amazon.com" <dibiase(a)amazon.com> Cc: Julia Charvolen <julia.charvolen(a)icann.org>, GNSO-Secs <gnso-secs(a)icann.org>, Theresa Swinehart <theresa.swinehart(a)icann.org>, Sherry Asaad <sherry.asaad(a)icann.org> Subject: Urgent Requests for Disclosure of Registration Data [ ref:!00D1a0Y7OU.!500Qk0H49r9:ref ] [Image removed by sender.] Dear Greg DiBiase, Please find attached a letter from Theresa Swinehart, Senior Vice President, Global Domains & Strategy, at ICANN. This letter will be posted shortly to the ICANN Correspondence page (https://www.icann.org/resources/pages/correspondence) Please submit any questions you may have about this message to correspondence(a)icann.org<mailto:correspondence@icann.org>. Best Regards, Michael Kovach The Correspondence Team Internet Corporation for Assigned Names and Numbers (ICANN) correspondence(a)icann.org www.icann.org ref:!00D1a0Y7OU.!500Qk0H49r9:ref [Image removed by sender.]

1 0