- SubPro-IRT - lists.icann.org

Blog & Topic Overviews for the AGB
by Lars Hoffmann May 21, 2025

May 21, 2025

Dear members of the IRT, Please see today’s blog post<https://www.icann.org/en/blogs/details/icann-materials-provide-prospective-…> announcing the launch of Topic Overviews, which we are developing to help applicants better understand some of the more complex aspects of the Applicant Guidebook (AGB). You can find the initial set of Topic Overviews on the AGB resource page<https://newgtldprogram.icann.org/en/application-rounds/round2/agb/resources>. Best wishes, Lars

1 0

SubPro IRT Meeting #147 | 11 June 2025, 13:30-15:00 UTC / 15:30-17:00 CET | ICANN83
by Next Round Policy Implementation May 21, 2025

May 21, 2025

Dear All, Meeting #147 of the SubPro IRT will be held on 11 June 2025 at 13:30-15:00 UTC / 15:30-17:00 CET [local time<https://tinyurl.com/2pskwaa8>] during ICANN83 in Prague, Czech Republic, in a hybrid format. Up-to-date information on the session will be published here<https://icann83.sched.com/event/246Zc/gds-subpro-irt-work-session-2-of-2>, and the agenda here<https://icann-community.atlassian.net/wiki/x/AYByCw>. More information on ICANN82 can be found here<https://meetings.icann.org/en/meetings/icann83/>. Before the meeting, please ensure you have read the ICANN Expected Standards of Behavior<https://www.icann.org/resources/pages/expected-standards-2016-06-28-en> and the ICANN Community Anti-Harassment Policy<https://www.icann.org/resources/pages/community-anti-harassment-policy-2017…>. In addition, we would like to remind participants that to ensure transparency of participation in ICANN's multistakeholder model, we ask that you sign in to Zoom sessions using your full name. For example, First Name and Last Name or Surname. You may be removed from the session if you do not sign in using your full name. Please let us know ahead of time should you be unable to attend the meeting. A recording will be made available. We remain at your disposal should you have any questions. Best regards, Renate

1 0

SubPro IRT Meeting #146 | 9 June 2025, 0700-08:15 UTC / 09:00-10:15 CET | ICANN83
by Next Round Policy Implementation May 21, 2025

May 21, 2025

Dear All, Meeting #146 of the SubPro IRT will be held on 9 June 2025 at 07:00-08:15 UTC / 09:00-10:015 CET [local time<https://tinyurl.com/bdzdkuec>] during ICANN83 in Prague, Czech Republic, in a hybrid format. Up-to-date information on the session will be published here<https://icann83.sched.com/event/246Qx/gds-subpro-irt-work-session-1-of-2>, and the agenda here<https://icann-community.atlassian.net/wiki/x/AQByCw>. More information on ICANN82 can be found here<https://meetings.icann.org/en/meetings/icann83/>. Before the meeting, please ensure you have read the ICANN Expected Standards of Behavior<https://www.icann.org/resources/pages/expected-standards-2016-06-28-en> and the ICANN Community Anti-Harassment Policy<https://www.icann.org/resources/pages/community-anti-harassment-policy-2017…>. In addition, we would like to remind participants that to ensure transparency of participation in ICANN's multistakeholder model, we ask that you sign in to Zoom sessions using your full name. For example, First Name and Last Name or Surname. You may be removed from the session if you do not sign in using your full name. Please let us know ahead of time should you be unable to attend the meeting. A recording will be made available. We remain at your disposal should you have any questions. Best regards, Renate

1 0

Press Release: New Research Reveals Marketing Leaders See Strong Potential in gTLDs Despite Knowledge Gap
by Bob Ochieng May 20, 2025

May 20, 2025

Dear IRT members, As we indicated in past calls, the ICANN Global Communications team is preparing to launch a series of integrated global media campaigns to raise awareness and interest in new generic top-level domains and the New gTLD Program: Next Round. A key objective is to reach audiences beyond Europe and North America. The first of these campaigns titled: New Research Reveals Marketing Leaders See Strong Potential in gTLDs Despite Knowledge Gap<https://www.icann.org/resources/press-material/release-2025-05-20-en> launched today, 20 May 2025. The primary aim of the campaign is to increase understanding of new gTLDs and the Next Round among brand and marketing leaders, a key audience for the program. Just wanted to flag this here and we look forward to discussing these with you during our Thursday call this week. Thank you. -- Kind Regards Bob.

1 0

Fwd: Standing Rock Resolution banning Lakota Language Consortium
by Anne ICANN May 18, 2025

May 18, 2025

Dear Jared and to the full IRT, Just to explain further why I continue to express concern regarding indigenous language communities in the Community Priority Evaluation process, please see an example in the public Tribal Resolution of the Standing Rock Sioux Tribe linked below. https://www.documentcloud.org/documents/22048660-standing-rock-banishment-r… This concern is not an isolated incident and many tribes have similar issues. These issues are not limited to the U.S. Please see a brief excerpt from the UNESCO Declaration on the International Decade of Indigenous Languages (2022-2032) here: 24. Proclaims the period 2022–2032 as the International Decade of Indigenous Languages, to draw attention to the critical loss of indigenous languages and the urgent need to preserve, revitalize and promote indigenous languages and to take urgent steps at the national and international levels, and invites the United Nations Educational, Scientific and Cultural Organization to serve as the lead agency for the International Decade, in collaboration with the Department of Economic and Social Affairs of the Secretariat, and other relevant agencies, within existing resources; Fortunately, our CPE policy work takes account of these non-formal linguistic communities who self-identify. Of course external recognition makes sense as long as such recognition can be localized in the case of indigenous language communities and can be provided by experts as contemplated by the Final Report. The examples in the draft presented by Jared on the last CPE call are helpful. We may or may not see applications from these communities in the 2026 round but the guidelines we are implementing now are likely to stay in place for a very long time. Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso(a)gmail.com

5 7

CANCELLED | SubPro IRT Meeting #141 | 20 May 2025, 12:00-14:00 UTC
by Next Round Policy Implementation May 16, 2025

May 16, 2025

Dear All, Meeting #141 of the SubPro IRT of 20 May 2025 at 12:00-14:00 UTC [local time [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/bddx2xr5__;!!PtGJab4!-4mtBWS…>] has been cancelled. Best regards, Renate

1 0

Post call | SubPro IRT Meeting #140 | 15 May 2025
by Next Round Policy Implementation May 16, 2025

May 16, 2025

Dear All, The recordings for Meeting #140 of the SubPro IRT held on Thursday, 15 May 2025 are published on the meeting wiki page<https://icann-community.atlassian.net/wiki/x/KwDLCg>. These include: * Audio recording * Zoom recording (including audio, visual, rough transcript, chat) * Attendance * Deck For additional information, you may consult the mailing list archives<https://mm.icann.org/pipermail/subpro-irt/> and the main wiki page<https://community.icann.org/x/pQM5Dg>. Best regards, Renate

1 0

Re: Community Input & Dispute Resolution
by Elisa Busetto May 15, 2025

May 15, 2025

Dear All, We have made some more changes to the Community Input, Objections, and Appeals language (highlighted in yellow): 1. Added a paragraph regarding applicants subject to String Confusion objections that decide to accept that their string will be part of a contention set: https://docs.google.com/document/d/16HK37AMl3VtfmhzPSoiidyqMYRrKzNRCYArbp7A… 2. Added a Quick Look Review for appeals: https://docs.google.com/document/d/16HK37AMl3VtfmhzPSoiidyqMYRrKzNRCYArbp7A… In addition, we would like to confirm that since it constitutes an Expert Determination, the outcome of the Quick Look Review for objections can be appealed against. With this, we hope we have addressed all the concerns raised by the IRT and note that the procedures will have to be updated accordingly. Please let us know of any questions. Many thanks! Elisa On Tue, 29 Apr 2025, 18:58 Lars Hoffmann via SubPro-IRT, <subpro-irt(a)icann.org<mailto:subpro-irt@icann.org>> wrote: Dear IRT members, Please see here the redline for the Community Input and Dispute Resolution language: https://docs.google.com/document/d/16HK37AMl3VtfmhzPSoiidyqMYRrKzNRCYArbp7A… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/16HK37AMl3Vtf…> Please note, this topic includes language on: * Application Comments * GAC early warning * GAC advice * Singular/Plural notification * Objections * Standing * Filing and Processing * Appeals If you’d like to provide further input, please use the comment function on the google document. At this time, we have not more discussion on this topic scheduled. Very best. Lars _______________________________________________ SubPro-IRT mailing list -- subpro-irt(a)icann.org<mailto:subpro-irt@icann.org> To unsubscribe send an email to subpro-irt-leave(a)icann.org<mailto:subpro-irt-leave@icann.org> _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos) You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

2 1

REMINDER | SubPro IRT Meeting #140 | 15 May 2025, 18:00-20:00 UTC
by Next Round Policy Implementation May 15, 2025

May 15, 2025

Dear All, Meeting #140 of the SubPro IRT will be held in one hour on 15 May 2025 at 18:00-20:00 UTC [local time<https://tinyurl.com/mrxx94n7>]. Planned topics: 18. Terms & Conditions The final agenda can be consulted here<https://icann-community.atlassian.net/wiki/x/KwDLCg?atlOrigin=eyJpIjoiNjcwZ…>. Before the meeting, please be sure you have read the ICANN Expected Standards of Behavior<https://www.icann.org/resources/pages/expected-standards-2016-06-28-en> and the ICANN Community Anti-Harassment Policy<https://wecann.icann.org/external-link.jspa?url=https%3A%2F%2Fwww.icann.org…>. We would like to remind participants that to ensure transparency of participation in ICANN's multistakeholder model, we ask that you sign in to Zoom sessions using your full name. For example, First Name and Last Name or Surname. You may be removed from the session if you do not sign in using your full name. Zoom information: Join the Zoom Webinar directly (recommended): https://icann.zoom.us/j/97063459905?pwd=VUVsd0J0RnNtRXkyNXJFZW9vdTEzZz09 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/j/97063459905?pwd=VUVsd0J0…> Meeting ID: 970 6345 9905 Passcode: DQ#0L.9x5e Zoom Audio only: One tap mobile +13462487799,,97063459905#,,,,*5806401747# US (Houston) +16699006833,,97063459905#,,,,*5806401747# US (San Jose) Meeting ID: 970 6345 9905 Passcode: 5806401747 Should you be unable to attend the meeting, please let us know in advance. A recording will be made available. Please do not hesitate to contact us should you have any questions. Best regards, Renate

1 0

High level webinars on the AGB June 2 and June 3
by Anne ICANN May 15, 2025

May 15, 2025

Hi Elisa, Are the above two webinars both same content and choose one? Or are different AGB sections covered and we should view both? Thank you, Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso(a)gmail.com

3 3

Community Input & Dispute Resolution
by Lars Hoffmann May 15, 2025

May 15, 2025

Dear IRT members, Please see here the redline for the Community Input and Dispute Resolution language: https://docs.google.com/document/d/16HK37AMl3VtfmhzPSoiidyqMYRrKzNRCYArbp7A… Please note, this topic includes language on: * Application Comments * GAC early warning * GAC advice * Singular/Plural notification * Objections * Standing * Filing and Processing * Appeals If you’d like to provide further input, please use the comment function on the google document. At this time, we have not more discussion on this topic scheduled. Very best. Lars

6 8

High-level Guide to the Draft AGB Webinar (2 of 2) | 3 June 2025, 16:30-18:00 UTC
by Next Round Policy Implementation May 15, 2025

May 15, 2025

Dear All, As announced on one of the SubPro IRT calls and ICANN announcement (here<https://www.icann.org/en/announcements/details/icann-webinar-will-introduce…>), please find the details for joining the second of two webinars on the High-level Guide to the Draft Applicant Guidebook. Please do not share the zoom link outside of the SubPro IRT to avoid zoom bombing. High-level Guide to the Draft Applicant Guidebook Webinar (2 of 2) Tuesday, 3 June 2025 at 16:30-18:00 UTC Join Zoom Meeting directly (recommended): https://icann.zoom.us/j/97804323630?pwd=3iAkHAL6xazbk3O7ElwyHSfkkrD4lw.1 Meeting ID: 978 0432 3630 Passcode: =SG7J*VFi# Audio only: One tap mobile +12532158782,,97804323630#,,,,*0557715010# US (Tacoma) +13017158592,,97804323630#,,,,*0557715010# US (Washington DC) Meeting ID: 978 0432 3630 Passcode: 0557715010 Find your local number: https://icann.zoom.us/u/abQbe1ODs Before joining the call: Please be sure you have read the ICANN Expected Standards of Behavior: https://www.icann.org/resources/pages/expected-standards-2016-06-28-en and the ICANN Community Anti-Harassment Policy<https://wecann.icann.org/external-link.jspa?url=https%3A%2F%2Fwww.icann.org…> Time conversion link: https://tinyurl.com/4tjdtvyx Please do not hesitate to contact us should you have any questions. Best regards, Renate

1 0

High-level Guide to the Draft AGB Webinar (1 of 2) | 3 June 2025, 04:00-05:30 UTC
by Next Round Policy Implementation May 15, 2025

May 15, 2025

Dear All, As announced on one of the SubPro IRT calls and in the ICANN announcement (here<https://www.icann.org/en/announcements/details/icann-webinar-will-introduce…>), please find the details for joining the first of two webinars on the High-level Guide to the Draft Applicant Guidebook. Please do not share the zoom link outside of the SubPro IRT to avoid zoom bombing. High-level Guide to the Draft Applicant Guidebook Webinar (1 of 2) Tuesday, 3 June 2025 at 04:00-05:30 UTC Join Zoom Meeting directly (recommended): https://icann.zoom.us/j/97804323630?pwd=3iAkHAL6xazbk3O7ElwyHSfkkrD4lw.1 Meeting ID: 978 0432 3630 Passcode: =SG7J*VFi# Audio only: One tap mobile +12532158782,,97804323630#,,,,*0557715010# US (Tacoma) +13017158592,,97804323630#,,,,*0557715010# US (Washington DC) Meeting ID: 978 0432 3630 Passcode: 0557715010 Find your local number: https://icann.zoom.us/u/abQbe1ODs Before joining the call: Please be sure you have read the ICANN Expected Standards of Behavior: https://www.icann.org/resources/pages/expected-standards-2016-06-28-en and the ICANN Community Anti-Harassment Policy<https://wecann.icann.org/external-link.jspa?url=https%3A%2F%2Fwww.icann.org…> Time conversion link: https://tinyurl.com/bdef2ks7 Please do not hesitate to contact us should you have any questions. Best regards, Renate

1 0

REMINDER | SubPro IRT Meeting #140 | 15 May 2025, 18:00-20:00 UTC
by Next Round Policy Implementation May 14, 2025

May 14, 2025

Dear All, Meeting #140 of the SubPro IRT will be held on 15 May 2025 at 18:00-20:00 UTC [local time<https://tinyurl.com/mrxx94n7>]. Planned topics: 18. Terms & Conditions The final agenda can be consulted here<https://icann-community.atlassian.net/wiki/x/KwDLCg?atlOrigin=eyJpIjoiNjcwZ…>. Before the meeting, please be sure you have read the ICANN Expected Standards of Behavior<https://www.icann.org/resources/pages/expected-standards-2016-06-28-en> and the ICANN Community Anti-Harassment Policy<https://wecann.icann.org/external-link.jspa?url=https%3A%2F%2Fwww.icann.org…>. We would like to remind participants that to ensure transparency of participation in ICANN's multistakeholder model, we ask that you sign in to Zoom sessions using your full name. For example, First Name and Last Name or Surname. You may be removed from the session if you do not sign in using your full name. Zoom information: Join the Zoom Webinar directly (recommended): https://icann.zoom.us/j/97063459905?pwd=VUVsd0J0RnNtRXkyNXJFZW9vdTEzZz09 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/j/97063459905?pwd=VUVsd0J0…> Meeting ID: 970 6345 9905 Passcode: DQ#0L.9x5e Zoom Audio only: One tap mobile +13462487799,,97063459905#,,,,*5806401747# US (Houston) +16699006833,,97063459905#,,,,*5806401747# US (San Jose) Meeting ID: 970 6345 9905 Passcode: 5806401747 Should you be unable to attend the meeting, please let us know in advance. A recording will be made available. Please do not hesitate to contact us should you have any questions. Best regards, Renate

1 0

Re: [Ext] RE: Recommendation 36.4 re: Fraudulent and Deceptive Practices
by Lars Hoffmann May 14, 2025

May 14, 2025

Thanks, Susan. Section 4.3(f) in full is as follows (bolded is what was shared yesterday) and it is the same language shared on 25 April. 1. ICANN may, upon notice to Registry Operator, terminate this Agreement if (i) Registry Operator knowingly employs any officer who is convicted of a misdemeanor related to financial activities or of any felony, or is judged by a court of competent jurisdiction to have committed fraud or breach of fiduciary duty, or is the subject of a judicial determination that ICANN reasonably deems as the substantive equivalent of any of the foregoing and such officer is not terminated within thirty (30) calendar days of Registry Operator’s knowledge of the foregoing, (ii) any member of Registry Operator’s board of directors or similar governing body is convicted of a misdemeanor related to financial activities or of any felony, or is determined by a court of competent jurisdiction or by an arbitrator to have committed fraud or breach of fiduciary duty, or is the subject of a judicial or arbitral determination that ICANN reasonably deems as the substantive equivalent of any of the foregoing and such member is not removed from Registry Operator’s board of directors or similar governing body within thirty (30) calendar days of Registry Operator’s knowledge of the foregoing, or (iii) the Registry Operator is determined by a court of competent jurisdiction or by an arbitrator to have committed fraud or deceptive practices in the provision of Registry Services under this Agreement for the TLD, or is the subject of a judicial or arbitral determination that ICANN reasonably deems as the substantive equivalent. Best, Jamie From: Susan Payne <susan.payne(a)comlaude.com> Date: Wednesday, 14 May 2025 at 11:30 To: Lars Hoffmann <lars.hoffmann(a)icann.org>, Jamie Hedlund <jamie.hedlund(a)icann.org> Cc: Karla Hakansson <karla.hakansson(a)icann.org>, Anne ICANN <anneicanngnso(a)gmail.com>, Jared Erwin via SubPro-IRT <subpro-irt(a)icann.org> Subject: [Ext] RE: Recommendation 36.4 re: Fraudulent and Deceptive Practices Thanks Lars (and Jamie) In order that the IRT can properly review this, please would you provide the whole of what is now proposed as section 4.3(f). The language for (iii) needs to be seen in context with the rest of the clause. Based on the text Karla shared in her note as the then latest proposal on 4.3(f) (reproduced below) I’m struggling to see how (iii) is supposed to fit: 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. Is the proposed text for 4.3(f)(iii) meant to replace some or all of this (and so is not in fact (iii)), or is it an additional subclause, following on from (ii), and in which case is this “and” or “or” (either of which seem to lack coherence). As you know, we have a Council meeting at 0500UTC Thursday, where Anne and I have referred this matter. Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 Ext 255 [cid:image001.png@01DBC4F7.9F67D570] [comlaude.com]<https://urldefense.com/v3/__https:/comlaude.com/__;!!PtGJab4!_2vy3wWhHjna8i…> Follow us on LinkedIn [t-uk.xink.io]<https://urldefense.com/v3/__https:/t-uk.xink.io/Tracking/Index/pRkAAGVfAADw…> and YouTube [t-uk.xink.io]<https://urldefense.com/v3/__https:/t-uk.xink.io/Tracking/Index/bhkAAGVfAADw…> From: Lars Hoffmann via SubPro-IRT <subpro-irt(a)icann.org> Sent: 14 May 2025 09:20 To: Jared Erwin via SubPro-IRT <subpro-irt(a)icann.org> Cc: Jamie Hedlund <jamie.hedlund(a)icann.org>; Karla Hakansson <karla.hakansson(a)icann.org> Subject: [SubPro-IRT] Recommendation 36.4 re: Fraudulent and Deceptive Practices Dear all, Please, find below a message from Jamie Hedlund, SVP Contractual Compliance and U.S. Government Engagement Best wishes. Lars Dear IRT, Attached please find a revised org proposal for implementation of SubPro Recommendation 36.4. I am sharing this revised proposal as Karla is out this week. As you will see, the proposal would: * add a PIC to RA Spec. 11, Section 3 to prohibit a registry operator from engaging in fraudulent or deceptive business practices in performing any Critical Function under this Agreement. By narrowly defining the scope of registry conduct subject to a PIC, it limits the extent to which ICANN org would be placed in the role of enforcing substantive areas of law that are outside ICANN’s mission and bylaws. * amend RA Section 4.3(f) to allow ICANN to terminate an agreement if a registry operator is determined by a court of competent jurisdiction or by an arbitrator to have committed fraud or deceptive practices in the provision of Registry Services under this Agreement for the TLD, or is the subject of a judicial or arbitral determination that ICANN reasonably deems as the substantive equivalent. We look forward to discussing this proposal at the next IRT meeting following Karla’s return from vacation. Thank you. Best, Jamie Hedlund Jamie Hedlund Senior Vice President, Contractual Compliance and U.S. Government Engagement Internet Corporation for Assigned Names and Numbers (ICANN) Office Telephone: +1 310 301 5800 www.icann.org<http://www.icann.org/> ________________________________ 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 [comlaude.com]<https://urldefense.com/v3/__https:/comlaude.com/__;!!PtGJab4!_2vy3wWhHjna8i…>

2 2

Recommendation 36.4 re: Fraudulent and Deceptive Practices
by Lars Hoffmann May 14, 2025

May 14, 2025

Dear all, Please, find below a message from Jamie Hedlund, SVP Contractual Compliance and U.S. Government Engagement Best wishes. Lars Dear IRT, Attached please find a revised org proposal for implementation of SubPro Recommendation 36.4. I am sharing this revised proposal as Karla is out this week. As you will see, the proposal would: * add a PIC to RA Spec. 11, Section 3 to prohibit a registry operator from engaging in fraudulent or deceptive business practices in performing any Critical Function under this Agreement. By narrowly defining the scope of registry conduct subject to a PIC, it limits the extent to which ICANN org would be placed in the role of enforcing substantive areas of law that are outside ICANN’s mission and bylaws. * amend RA Section 4.3(f) to allow ICANN to terminate an agreement if a registry operator is determined by a court of competent jurisdiction or by an arbitrator to have committed fraud or deceptive practices in the provision of Registry Services under this Agreement for the TLD, or is the subject of a judicial or arbitral determination that ICANN reasonably deems as the substantive equivalent. We look forward to discussing this proposal at the next IRT meeting following Karla’s return from vacation. Thank you. Best, Jamie Hedlund Jamie Hedlund Senior Vice President, Contractual Compliance and U.S. Government Engagement Internet Corporation for Assigned Names and Numbers (ICANN) Office Telephone: +1 310 301 5800 www.icann.org<http://www.icann.org>

3 2

Re: [Ext] Re: Updated AGB Language for PICs/RVCs, CPE, Application Questions
by Pruis, Elaine May 13, 2025

May 13, 2025

Thank you Jared Perhaps adding this sentence from your explanation “As noted in the Application Change Request section, if an applicant does not pass CPE, it must remain a community applicant/application, and the community registration policies must remain in their Registry Agreement.” At the end of “If the community-based applications (as there could be more than one) in a contention set do not meet the criteria set forth below, then all of the applications in the contention set will proceed to an ICANN auction. [See Section X.X Contention Resolution for more information.]” Would make it abundantly clear to everyone reading that section of the AGB. Thanks! Elaine From: Jared Erwin <jared.erwin(a)icann.org> Date: Tuesday, May 13, 2025 at 11:44 AM To: Elaine Pruis <epruis(a)verisign.com> Cc: Anne ICANN <anneicanngnso(a)gmail.com>, "subpro-irt(a)icann.org" <subpro-irt(a)icann.org> Subject: [EXTERNAL] Re: [SubPro-IRT] Re: [Ext] Re: Updated AGB Language for PICs/RVCs, CPE, Application Questions 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. Dear Elaine and IRT Members, As a reminder, CPE does not determine the community status of an applicant/application. It determines whether a community application can achieve priority in the contention set, based on meeting the criteria. In that sense, the community status is not variable based on whether an application passes CPE. An applicant that marks its application as a community application cannot change that (as noted in the Application Change Request section). So, even if an applicant does not pass CPE, it must remain a community applicant/application, and the community registration policies (which must have already passed RCE), must remain in their Registry Agreement. Please let me know of any further questions. Thank you Jared From: "Pruis, Elaine" <epruis(a)verisign.com> Date: Monday, May 12, 2025 at 21:02 To: Jared Erwin <jared.erwin(a)icann.org> Cc: Anne ICANN <anneicanngnso(a)gmail.com>, "subpro-irt(a)icann.org" <subpro-irt(a)icann.org> Subject: Re: [SubPro-IRT] Re: [Ext] Re: Updated AGB Language for PICs/RVCs, CPE, Application Questions Hi, In the following scenario, “If the community-based applications (as there could be more than one) in a contention set do not meet the criteria set forth below, then all of the applications in the contention set will proceed to an ICANN auction. [See Section X.X Contention Resolution for more information.]” Can the community based applicant “change” to a “generic” application or are they still evaluated on the community specific items (registration polices) ? In other words are they held to the application commitments even if they don’t get CP? Elaine On May 8, 2025, at 6:25 PM, Jared Erwin via SubPro-IRT <subpro-irt(a)icann.org> wrote: 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. Hi Anne, Apologies. Too many links. Here is the correct one for CPE: https://docs.google.com/document/d/1q3jkjyTkhwU6wMzTq55oIEc5p-w6vVy5p1v3ywO… [secure-web.cisco.com] Thank you Jared From: Anne ICANN <anneicanngnso(a)gmail.com> Date: Thursday, May 8, 2025 at 17:23 To: Jared Erwin <jared.erwin(a)icann.org> Cc: "subpro-irt(a)icann.org" <subpro-irt(a)icann.org> Subject: [Ext] Re: [SubPro-IRT] Updated AGB Language for PICs/RVCs, CPE, Application Questions Thanks Jared. I clicked on the CPE link. It says "Access Denied" - the organization doesn't permit me to access this doc etc. Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso(a)gmail.com On Thu, May 8, 2025 at 2:39 PM Jared Erwin via SubPro-IRT <subpro-irt(a)icann.org> wrote: Dear IRT Members, Please find here the updated AGB Language for the following topics: PICs/RVCs: https://docs.google.com/document/d/1vOzVd93nws_0Sbp6-UPw8IVsvA2CeEOMgcfm5tZ… [docs.google.com] [secure-web.cisco.com] Updates to Community Registration Policies based on discussion on Tuesday CPE: https://docs.google.com/document/d/18B4fInk87eU8gpCFZrLur8v6SokM4ZG3HPAbQUM… [docs.google.com] [secure-web.cisco.com] This version addresses comments from our discussion on Tuesday, as well as addresses comments submitted by Kathy and Anne today on the previous version [docs.google.com] [secure-web.cisco.com] Please note Footnote 12 re: community experts which is intended to be a general statement to apply to all criteria and is no longer isolated just under awareness On Footnote 7, we have opted to refer to the criteria for more information re: “majority” vs “minority” and the determination for that, as opposed to having that definition in multiple places Application Questions: https://docs.google.com/document/d/13h1K-Pa0Z8JeKtacOAaGnQM9KnvJOuSTfnNhXUM… [docs.google.com] [secure-web.cisco.com] Includes updates to question 47 based on a comment from Jeff on the previous version [docs.google.com] [secure-web.cisco.com] We have also added question 156 related to the new “established presence” sub-criterion for CPE as well as made some adjustments to other CPE questions related to organization to more closely align with the criteria/guidelines Thank you, Jared -- Jared Erwin Director, New gTLD Program Global Domains & Strategy Internet Corporation for Assigned Names and Numbers (ICANN) jared.erwin(a)icann.org _______________________________________________ SubPro-IRT mailing list -- subpro-irt(a)icann.org To unsubscribe send an email to subpro-irt-leave(a)icann.org _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy [secure-web.cisco.com] and the website Terms of Service (https://www.icann.org/privacy/tos [secure-web.cisco.com] You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. _______________________________________________ SubPro-IRT mailing list -- subpro-irt(a)icann.org To unsubscribe send an email to subpro-irt-leave(a)icann.org _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://secure-web.cisco.com/13xj6T9lWb4rXq96nTOdPE8P56hEhxAuD57susqbBXQSj3…) and the website Terms of Service (https://secure-web.cisco.com/1dFwWWTB4cLNOA7t-V7Q-iF30SoAA8kI4KkQqyHVsM-xrv…) You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

2 1

Updated AGB Language for PICs/RVCs, CPE, Application Questions
by Jared Erwin May 13, 2025

May 13, 2025

Dear IRT Members, Please find here the updated AGB Language for the following topics: * PICs/RVCs: https://docs.google.com/document/d/1vOzVd93nws_0Sbp6-UPw8IVsvA2CeEOMgcfm5tZ… * Updates to Community Registration Policies based on discussion on Tuesday * CPE: https://docs.google.com/document/d/18B4fInk87eU8gpCFZrLur8v6SokM4ZG3HPAbQUM… * This version addresses comments from our discussion on Tuesday, as well as addresses comments submitted by Kathy and Anne today on the previous version<https://docs.google.com/document/d/1gVDvbjPEdwzxmBI96yLZ7yN0FKQvccBFmWCg2-t…> * Please note Footnote 12 re: community experts which is intended to be a general statement to apply to all criteria and is no longer isolated just under awareness * On Footnote 7, we have opted to refer to the criteria for more information re: “majority” vs “minority” and the determination for that, as opposed to having that definition in multiple places * Application Questions: https://docs.google.com/document/d/13h1K-Pa0Z8JeKtacOAaGnQM9KnvJOuSTfnNhXUM… * Includes updates to question 47 based on a comment from Jeff on the previous version<https://docs.google.com/document/d/1FZ7NaLUaQ67DWeSoUHgUhTaa0s5y5hmwup0-nXI…> * We have also added question 156 related to the new “established presence” sub-criterion for CPE as well as made some adjustments to other CPE questions related to organization to more closely align with the criteria/guidelines Thank you, Jared -- Jared Erwin Director, New gTLD Program Global Domains & Strategy Internet Corporation for Assigned Names and Numbers (ICANN) jared.erwin(a)icann.org<mailto:jared.erwin@icann.org>

3 4

Contention Resolution
by Lars Hoffmann May 13, 2025

May 13, 2025

Dear IRT, Please see here for a link to the updated document on Contention Set Resolution (Topic 35): https://docs.google.com/document/d/1bIu1lRxe4zr-lKRlfoQzd9dayoysItb4-AtvXUz… This version shows only the redlines from the previous version we shared (and reviewed) during last week’s call. The document will go for public comment as part of the full AGB at the end of this month. Best wishes, Lars

1 0

ASP Bid Credit Proposed Revisions
by Kristy Buckley May 8, 2025

May 8, 2025

Greetings IRT and ASP-IRT members (please forgive the cross-post), Further to our discussion today during Meeting #138<https://icann-community.atlassian.net/wiki/spaces/SPIR/pages/181141583/2025…>, we are sharing the proposed revisions to the ASP bid credit on the EXT drive<https://docs.google.com/document/d/1bIu1lRxe4zr-lKRlfoQzd9dayoysItb4-AtvXUz…>. As noted during the meeting, we are proposing these revisions for two reasons: 1. The edits intend to clarify that the bid credit indeed acts as a credit as well as a discount. The credit allows supported applicants to bid higher than they might otherwise, thereby increasing their chance of winning (per the stated rationale for policy Rec 17.15<https://gnso.icann.org/sites/default/files/file/field-file-attach/final-rep…>). The bid credit also provides a discount by reducing the amount due by the winning supported applicant. 2. These revisions aim to further mitigate risks associated with ICANN providing undue financial benefits to private parties (in the case that the winning price paid by the supported applicant exceeds the financial thresholds needed to qualify for support). Many thanks for your initial review during the meeting. Please let us know if you have any further questions or comments. Kind regards, Kristy

1 0

Re: [Ext] CPE Comments Slide Deck
by Jared Erwin May 8, 2025

May 8, 2025

Dear all, Apologies, I’m not sure those links came through. Let me try again: You can find that link here: https://icann-community.atlassian.net/wiki/spaces/SPIR/pages/262045703/5.+A…. The CPE deck can be found here (also on the link above): https://icann-community.atlassian.net/wiki/download/attachments/112200175/2…. Thank you Jared On 5/8/25, 09:51, "Jared Erwin via SubPro-IRT" <subpro-irt(a)icann.org <mailto:subpro-irt@icann.org>> wrote: Dear Kathy and all, As a reminder, we have recently created this page with links to all the topic documents as well as the slide decks where we talked through the public comments/our responses. You can find that link here: https://urldefense.com/v3/__https://icann-community.atlassian.net/wiki/spac… <https://urldefense.com/v3/__https://icann-community.atlassian.net/wiki/spac…>.*AGB*Topics*Overview*Log__;KysrKw!!PtGJab4!5x1lTLmTJ3s0jpSMPO0cPd9ZJT1ix8oiYYTVseq6sKRb_CvJJY8bZ2iBAJ07Cw0MywSy7xeb4rHMxiQ4HM59mxU9nfM$ [icann-community[.]atlassian[.]net]. The CPE deck can be found here (also on the link above): https://urldefense.com/v3/__https://icann-community.atlassian.net/wiki/down… <https://urldefense.com/v3/__https://icann-community.atlassian.net/wiki/down…>*20IRT_Meeting*20*23130_Deck.pdf?api=v2__;JSUl!!PtGJab4!5x1lTLmTJ3s0jpSMPO0cPd9ZJT1ix8oiYYTVseq6sKRb_CvJJY8bZ2iBAJ07Cw0MywSy7xeb4rHMxiQ4HM59pbpAizU$ [icann-community[.]atlassian[.]net]. Thank you, Jared On 5/8/25, 09:45, "Kathy Kleiman" <Kathy(a)KathyKleiman.com <mailto:Kathy@KathyKleiman.com> <mailto:Kathy@KathyKleiman.com <mailto:Kathy@KathyKleiman.com>>> wrote: Hi Lars, Jared, and Elisa, May I ask you to share the slide deck of comments we received on the CPE, and the ICANN Org responses? It might be useful for everyone, so I write and include the SubPro WG. Best and tx, Kathy _______________________________________________ SubPro-IRT mailing list -- subpro-irt(a)icann.org <mailto:subpro-irt@icann.org> To unsubscribe send an email to subpro-irt-leave(a)icann.org <mailto:subpro-irt-leave@icann.org> _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy <https://www.icann.org/privacy/policy>) and the website Terms of Service (https://www.icann.org/privacy/tos <https://www.icann.org/privacy/tos>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

1 0

CPE Comments Slide Deck
by Kathy Kleiman May 8, 2025

May 8, 2025

Hi Lars, Jared, and Elisa, May I ask you to share the slide deck of comments we received on the CPE, and the ICANN Org responses? It might be useful for everyone, so I write and include the SubPro WG. Best and tx, Kathy

2 1

Post call | SubPro IRT Meeting #138 | 8 May 2025
by Next Round Policy Implementation May 8, 2025

May 8, 2025

Dear All, The recordings for Meeting #138 of the SubPro IRT held on Thursday, 8 May 2025 are published on the meeting wiki page<https://icann-community.atlassian.net/wiki/x/TwDMCg>. These include: * Audio recording * Zoom recording (including audio, visual, rough transcript, chat) * Attendance * Deck For additional information, you may consult the mailing list archives<https://mm.icann.org/pipermail/subpro-irt/> and the main wiki page<https://community.icann.org/x/pQM5Dg>. Best regards, Renate

1 0

CANCELLED | SubPro IRT Meeting #139 | 13 May 2025, 12:00-14:00 UTC
by Next Round Policy Implementation May 8, 2025

May 8, 2025

Dear All, Meeting #139 of the SubPro IRT scheduled for Tuesday, 13 May 2025 at 12:00-14:00 UTC is cancelled. Best regards, Renate

1 0

Updates and Materials
by Lars Hoffmann May 8, 2025

May 8, 2025

Dear IRT members, Following recent discussions, we have prepared redline updates to a number of topics – details and links below. Please note, the first to topics in the list: Terms and Conditions and Contention Resolution, will be the subject of tomorrow’s call. During tomorrow’s call we will also go over some of the conditional fee issues, I hope to share materials prior to the call on that, too. As always, please reach out with any questions/comments etc. Best. Lars 1. Terms and Conditions [https://docs.google.com/document/d/1EfnA02C5lc-PXQUgukerFJ2rkSzLDFCbZ4jiZFO…] o Paragraph 1: We modified the language to make more clear which kinds of changes applicants are required to provide notice to ICANN, and this clarity also goes to the question about “material” since the requirement is that applicants must tell ICANN about changes with this Application that could adversely affect impact the results of the evaluation of this Application * Paragraph 9: in response to questions about the ability to assign an application, we deleted the final section of the last clause because the intent is that an applicant cannot resell/assign/transfer an application. 1. Contention Resolution / No Collusion [https://docs.google.com/document/d/1bIu1lRxe4zr-lKRlfoQzd9dayoysItb4-AtvXUz…] · We updated section 2 (Prohibition of Private Resolution) as follows: o Made clear that applicants are only prohibited from communication on strings they are in contention with. Meaning that applicants can speak to other applicants/consultants etc. whose are not apply for a string they are in contention with. o Made clear that applicants prevailing in an auction may speak to other applicants they were in contention with, once these applicants have withdrawn from the program. o Added language that makes clear that ICANN reserves the right to take appropriate action to address false claims of violations of the no-collusion rules. · We did not further elaborate/explain the term ‘other things of value’. While Anne’s point from our previous discussion is well made, we have intentionally left this language broad to cover a variety of situations/things. 1. Application Journey [https://docs.google.com/document/d/1lXSaBBAHP1S57nxjHNvpRzrQrOoscCY_vN1QXp0…] · We made updates to the RSP Selection language, reflecting input from the previous IRT discussion. · We added more information regarding “expected duration” of the different stages of the application process 1. Name Collision [https://docs.google.com/document/d/14lo8OPG80PVJnQQs0wlxafC07CC9YNyhzad5yvJ…] · We made one substantive update following your feedback, adding “However, as permanent delegations take precedence over temporary delegations, this number may vary from month to month.” At the end of the first paragraph in section 4 (top of page 4). · We also added a new footnote 1, referencing section 2.2 of the NCAP Study report.

5 18