- SubPro-IRT - lists.icann.org

NxR Base RA: SubPro Meeting #135
by Karla Hakansson April 29, 2025

April 29, 2025

Hello SubPro IRT, We will cover the following topics regarding the Next Round Base RA in meeting #135 tomorrow, 29 April: 1. Name Collision Report Handling, Spec 6, Sec 6.3.1 & 6.3.2, 2. Specification 13 3. Specification 14 Attached please find the redlines we will review. Also, the incorrect document is posted on the SubPro IRT wiki from our discussion on Recommendation 36.4. Until we resolve, please fine the correct redline we reviewed in meeting #134 on Thursday, 24 April. Regards, Karla

4 4

REMINDER | SubPro IRT Meeting #135 | 29 April 2025, 18:00-20:00 UTC
by Next Round Policy Implementation April 29, 2025

April 29, 2025

Dear All, Meeting #135 of the SubPro IRT will be held in one hour on 29 April 2025 at 18:00-20:00 UTC [local time [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/284xy8xx__;!!PtGJab4!6uDolAS…>]. Planned topics: 29. Name Collisions; 36. Base Registry Agreement The final agenda can be consulted here [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/IgD…>. 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: REMINDER | SubPro IRT Meeting #135 | 29 April 2025, 18:00-20:00 UTC
by Jared Erwin April 29, 2025

April 29, 2025

Dear IRT Members, Please find here the updated AGB Language for Name Collision. The edits therein reflect the responses to the public comments, which can be found in the deck<https://icann-community.atlassian.net/wiki/spaces/SPIR/pages/180879394/2025…> on the wiki page. * Google doc: https://docs.google.com/document/d/14lo8OPG80PVJnQQs0wlxafC07CC9YNyhzad5yvJ… * PDF: https://icann-community.atlassian.net/wiki/spaces/SPIR/pages/112200175/1.+W… Talk to you soon. 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> From: Next Round Policy Implementation via SubPro-IRT <subpro-irt(a)icann.org> Reply-To: Next Round Policy Implementation <NextRound_PolicyImplementation(a)icann.org> Date: Monday, April 28, 2025 at 11:00 To: "subpro-irt(a)icann.org" <subpro-irt(a)icann.org> Subject: [SubPro-IRT] REMINDER | SubPro IRT Meeting #135 | 29 April 2025, 18:00-20:00 UTC Dear All, Meeting #135 of the SubPro IRT will be held on 29 April 2025 at 18:00-20:00 UTC [local time [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/284xy8xx__;!!PtGJab4!6uDolAS…>]. Planned topics: 29. Name Collisions; 36. Base Registry Agreement The final agenda can be consulted here [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/IgD…>. 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: String Similarity
by Lars Hoffmann April 29, 2025

April 29, 2025

Thanks, for the question, Ashely. This is hopefully just a question of clarification: Reserved names, if applied-for, are considered for string similarity, like all other applied-for strings. But they are not like blocked names from a string similarity perspective. So, given: A – reserved name B – any other applied-for string (not a reserved name) if A and B are applied-for, and A and B are found similar, they will be put in contention. If A is not applied-for, then B will proceed without any issue (reserved names are not considered as a special category like Blocked Names or existing gTLDs for sting similarity). If this is not clear from the text, we can try to update it further. Best. Lars From: Ashley Roberts <ashley.roberts(a)comlaude.com> Date: Monday, 28 April 2025 at 12:29 To: Lars Hoffmann <lars.hoffmann(a)icann.org>, Anne ICANN via SubPro-IRT <subpro-irt(a)icann.org> Subject: [Ext] RE: String Similarity Thanks Lars. I’m a little by confused by the sentence “Further if a Reserved Name is not applied for, a string similar to it may proceed without contention as it applied first.” May I ask where that conclusion has come from? I thought Reserved Names were still subject to string similarity review, notwithstanding the ability of a relevant IGO/INGO to apply for their own string. Not sure if I may have missed a discussion on this topic, but would you please be able to clarify? Kind regards, Ashley Ashley Roberts Head of New TLD Consultancy Com Laude T +44 (0) 20 7421 8250 Ext 264 [cid:image001.png@01DBB917.958158B0] [comlaude.com]<https://urldefense.com/v3/__https:/comlaude.com/__;!!PtGJab4!8eI8Yan4-DVee8…> Follow us on LinkedIn [t-uk.xink.io]<https://urldefense.com/v3/__https:/t-uk.xink.io/Tracking/Index/pRkAAGVfAADD…> and YouTube [t-uk.xink.io]<https://urldefense.com/v3/__https:/t-uk.xink.io/Tracking/Index/bhkAAGVfAADD…> From: Lars Hoffmann via SubPro-IRT <subpro-irt(a)icann.org> Sent: 28 April 2025 09:29 To: Anne ICANN via SubPro-IRT <subpro-irt(a)icann.org> Subject: [SubPro-IRT] String Similarity Dear IRT members, Based on our discussions and your feedback, we have clarified that only the relevant subset of Blocked Names will be used for comparison with applied-for strings during string similarity evaluation, and that Reserved Names are not part of this list. Reserved Names are subject to string similarity evaluation (like other applied-for strings) and may end up in contention sets if found similar to another applied-for string. Further if a Reserved Name is not applied for, a string similar to it may proceed without contention as it applied first. Kindly review the changes in redline [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/19SBv5Mwxt5iZ…>. Our working assumption is that this update incorporates all remaining IRT feedback, and we will prepare this document for public comment – as part of the collated draft AGB. Many thanks and best wishes. Lars https://docs.google.com/document/d/19SBv5Mwxt5iZQcJ0LTAlhe6_un7tJ77opbpVyo2… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/19SBv5Mwxt5iZ…> ________________________________ 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!8eI8Yan4-DVee8…>

2 2

TODAY's IRT meeting
by Lars Hoffmann April 29, 2025

April 29, 2025

Dear members of the IRT, For TODAY’S meeting (18-20 UTC), please see the documents pertaining to the RA discussion on the wiki: https://icann-community.atlassian.net/wiki/x/IgDICg, The wiki page also contains the deck for today’s meeting, which contains ICANN’s responses to the public comments received re: Name Collision. As a reminder, we will start today’s call with the RA discussion, with a hard stop at 19:10 UTC when we will switch to Name Collision. In case the RA discussion will conclude earlier, we will of course move on to Name Collision right away. Very best. Lars

1 0

Re: Updated CPE AGB Language
by Jared Erwin April 29, 2025

April 29, 2025

Hi all, As a reminder, following our discussion on Tuesday, please review the CPE draft and provide any comments on the google (redline) document linked below. We will also begin work on updating based on the IRT’s feedback ahead of our next call on this topic on 29 April 2025. I understand there were also questions on CPE/Community Registration Policies on the call yesterday, and we will make sure any updates made in relation to Topic 9 will also be reflected in the CPE section, as needed/relevant. Thank you Jared From: Jared Erwin via SubPro-IRT <subpro-irt(a)icann.org> Reply-To: Jared Erwin <jared.erwin(a)icann.org> Date: Tuesday, April 15, 2025 at 10:40 To: "subpro-irt(a)icann.org" <subpro-irt(a)icann.org> Subject: [SubPro-IRT] Updated CPE AGB Language Dear IRT Members, For our call today, 15 April 2025, at 18:00 UTC, here are the links to the updated CPE Language: * Google doc: EXT_Topic 34_Community Priority Evaluation_Draft AGB Language_v3 [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/16Hopw-yFMbU3…> * PDF: https://icann-community.atlassian.net/wiki/spaces/SPIR/pages/112200175/1.+W… [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/space…> Thank you and speak with you soon. Best 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>

5 11

Next Round Sourcing Timeline
by Lars Hoffmann April 29, 2025

April 29, 2025

Dear IRT members, My emails are like London busses today … As previously discussed, here is the recently published website on the procurement planning for the next round: https://newgtldprogram.icann.org/en/resources/sourcingtimeline. Best. Lars

3 3

REMINDER | SubPro IRT Meeting #135 | 29 April 2025, 18:00-20:00 UTC
by Next Round Policy Implementation April 28, 2025

April 28, 2025

Dear All, Meeting #135 of the SubPro IRT will be held on 29 April 2025 at 18:00-20:00 UTC [local time [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/284xy8xx__;!!PtGJab4!6uDolAS…>]. Planned topics: 29. Name Collisions; 36. Base Registry Agreement The final agenda can be consulted here [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/IgD…>. 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

String Similarity
by Lars Hoffmann April 28, 2025

April 28, 2025

Dear IRT members, Based on our discussions and your feedback, we have clarified that only the relevant subset of Blocked Names will be used for comparison with applied-for strings during string similarity evaluation, and that Reserved Names are not part of this list. Reserved Names are subject to string similarity evaluation (like other applied-for strings) and may end up in contention sets if found similar to another applied-for string. Further if a Reserved Name is not applied for, a string similar to it may proceed without contention as it applied first. Kindly review the changes in redline<https://docs.google.com/document/d/19SBv5Mwxt5iZQcJ0LTAlhe6_un7tJ77opbpVyo2…>. Our working assumption is that this update incorporates all remaining IRT feedback, and we will prepare this document for public comment – as part of the collated draft AGB. Many thanks and best wishes. Lars https://docs.google.com/document/d/19SBv5Mwxt5iZQcJ0LTAlhe6_un7tJ77opbpVyo2…

2 1

Application Fees
by Lars Hoffmann April 25, 2025

April 25, 2025

Dear IRT members, In preparation for the call on Tuesday 30 April, 12-14 UTC, please see below (and here<https://icann-community.atlassian.net/wiki/x/AQDMCg>) a link to respective wiki page, to which we just uploaded the preliminary slide deck, which contains ICANN’s responses to the public comment on Topic 15 (Fees), as well as a link to the corresponding google doc redline of the draft AGB language. Thank you and best wishes, Lars https://icann-community.atlassian.net/wiki/x/AQDMCg

1 0