March 2025 - SubPro-IRT - lists.icann.org

REMINDER | SubPro IRT Meeting #125 | 27 March 2025, 12:00-14:00 UTC
by Renate De Wulf March 26, 2025

March 26, 2025

PLEASE NOTE THAT THIS MEETING HAS BEEN EXTENDED TO TWO HOURS, AND WILL START AN HOUR EARLIER AT 12:00 UTC Dear All, Meeting #125 of the SubPro IRT will be held on 27 March 2025 at 12:00-14:00 UTC [local time [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/22zfp8de__;!!PtGJab4!5IeuZZ7…>]. Planned topics: 18. Terms & Conditions; Legal Compliance; Privacy Policy The final agenda can be consulted here<https://community.icann.org/x/CgATIg>. 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

Treatment of Reserved Names under Topic 24: String Similarity Evaluations
by Justine Chew March 26, 2025

March 26, 2025

Dear Lars, Elise, Michael and Sarmad, At the SubPro IRT Meeting #121 <https://community.icann.org/x/NYDKGQ> during ICANN82, I had requested for the opportunity to review the part of the discussion where a change was proposed in respect of Topic 24: String Similarity Evaluations. Specifically, in Section 1.2 Scope of String Similarity Evaluation on page 3 of *Proposed AGB Language_String Similarity Evaluation_v06_2025-03-06.pdf *(linked on the SubPro IRT Meeting #121 <https://community.icann.org/x/NYDKGQ> wiki page) it was proposed that the reference to "Reserved Names" be changed to "Blocked Names". While I acknowledge that a change is warranted given ICANN org's effort to now re-classify (a) what was known as Reserved Names (in the 2012 AGB) to Blocked Names (in the NR AGB) and (b) what was known as "Strings Ineligible for Delegation (in the 2012 AGB) to Reserved Names (in the NR AGB), I would like to pose a few questions for resolution with the following context. *Context* 1. As detailed in the Phase 1 Final Report on the Internationalized Domain Names Expedited Policy Development Process <https://gnso.icann.org/sites/default/files/policy/2023/correspondence/epdp-…> which was put out for public comment by the Board <https://www.icann.org/ru/public-comment/proceeding/phase-1-final-report-of-…>, the EPDP working group did consider the treatment for (the 2012) Reserved Names separately to Strings Ineligible for Delegation, which resulted in Final Recommendations 3.18, 3.19, 3.20 and 3.21 at page 51. For present purposes, I would like to draw specific attention to: *"Final Recommendation 3.20: The list of Strings Ineligible for Delegation must not be expanded to include variant labels."*; and *"Final Recommendation 3.21: Only the protected organizations on the list of Strings Ineligible for Delegation are allowed to apply for the allocatable variant label(s) of their protected string(s) at the top-level. Consistent with Final Recommendation 3.1, an application for an allocatable variant label of a protected string cannot precede an application for the protected string, which serves as the primary label for generating the variant label." * And as a reminder, going forward, "Strings Ineligible for Delegation" are known as "Reserved Names". 2. In Section 2.1.8 Reserved Name Identification on page 6 of Applicant Journey (related to Topic 5: Application Submission Limits and Topic 16: Application Submission Period) <https://itp.cdn.icann.org/en/files/policy-development/applicant-journey-rel…> currently out for public comment through the Fourth Proceeding for Proposed Language for Draft Sections of Next Round AGB <https://www.icann.org/en/public-comment/proceeding/fourth-proceeding-for-pr…>, there is mention of treatment of Reserved Names. For convenience, I replicate the section below and highlighted in blue the portion of interest. *"2.1.8 Reserved Name IdentificationCertain strings, known as “Reserved Names”, are available as gTLD strings at the top level only through a validation process. These names are designated for specific entities, which are the only ones eligible to apply for them. ICANN org maintains a list of Reserved Names, compiled from various sources, and requires relevant entities to provide appropriate documentation, as outlined in the [Blocked and Reserved Names] section. During application drafting, the system will automatically verify whether the selected string and allocatable variants (where applicable) are a Reserved Name. If there is a positive match, the applicant will be requested to upload supporting documentation proving they are the entity for which the name is reserved, as described in [Reserved Name Identification]." * This seems to suggests that each applied-for string and its allocatable variants has to be compared with the list of Reserved Names and exact matches would not be allowed unless the applicant can demonstrate it is the entity for which the name is reserved. And we know that the list of Reserved Names are established separately through an examination of treaties and statutes across multiple jurisdictions. *Questions* Q1. Coming back to Section 1.2 Scope of String Similarity Evaluation on page 3 of *Proposed AGB Language_String Similarity Evaluation_v06_2025-03-06.pdf*, in apart from changing "Reserved Names" to "Blocked Names", should we not also make mention of the treatment of Reserved Names? If not, why? Q2. If we don't make mention per Q1, is section 2.1.8 of the Application Journey chapter then sufficiently clear to reconcile the treatment of Blocked Names versus the treatment of Reserved Names as presented in the Application Journey Chapter and in the chapter on String Similarity Evaluation? I suspect not. Q3. Could ICANN org propose a way to rectify any shortcomings I have attempted to highlight here, within the 2 chapters of String Similarity Evaluations and Applicant Journey, and elsewhere in the NR AGB as needed? Thank you, Justine

2 2

Re: RSP Selection
by Pruis, Elaine March 25, 2025

March 25, 2025

HI Lars, Thanks for the explanation, but I’m afraid that just won’t do. If the RSP evaluation window is to shut down on the last day that an application can be submitted, ICANN is unnaturally closing off the ability for new competitors to enter the RSP space/industry. I hope you all can find another way to provide certainty that ICANN have applied the same evaluation criteria to all RSP applicants. Elaine From: Lars Hoffmann via SubPro-IRT <subpro-irt(a)icann.org> Reply-To: Lars Hoffmann <lars.hoffmann(a)icann.org> Date: Wednesday, February 12, 2025 at 3:49 PM To: Cheryl Langdon-Orr via SubPro-IRT <subpro-irt(a)icann.org> Subject: [EXTERNAL] [SubPro-IRT] RSP Selection 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 IRT members, Following today’s (12 Feb 13 UTC) discussion, please, find attached the redline language and the clean language for RSP selection. In addition, there was a question from Elaine about the opening and closing of the RSP application window. Here is our explanation: ICANN org has developed internal evaluation guides for performing the RSP evaluation based on the criteria in the RSP handbook. The evaluation works by having a person with multiple years of industry experience doing the evaluation and another with similar skills doing quality assurance. Once all the evaluations are performed, the team will have multiple alignment sessions to confirm that the same criteria have been applied uniformly. This process provides certainty that we have applied the same evaluation criteria. If we don't close the application window, it's not possible to follow this process, as new entities could be joining at any time. Once the pre-evaluation period ends, we will publish the list of evaluated RSPs for the first time to provide the gTLD applicants an opportunity to start establishing business relationships with the RSPs. The RSP program was developed specifically for the NxR. Therefore, the second application window closes simultaneously with the gTLD application window. I hope this information is helpful. Please note, the clean document will post for public comment on Friday with the remainder of the materials. Best. Lars Redline: https://docs.google.com/document/d/13PCoLz3vBNB5dmuiACoIF6dI5Q9SMune-Ij5qIG… Clean: https://docs.google.com/document/d/1RHHRPGMs0XRStOpnoOgY_4PL_gn8MncSAXLRC3C… PDF attached

2 2

LONGER CALL | SubPro IRT Meeting #125 | 27 March 2025, 12:00-14:00 UTC
by Next Round Policy Implementation March 24, 2025

March 24, 2025

PLEASE NOTE THAT THIS MEETING HAS BEEN EXTENDED TO TWO HOURS, AND WILL START AN HOUR EARLIER AT 12:00 UTC Dear All, Meeting #125 of the SubPro IRT will be held on 27 March 2025 at 12:00-14:00 UTC [local time<https://tinyurl.com/22zfp8de>]. Planned topics: 18. Terms & Conditions; Legal Compliance; Privacy Policy The final agenda can be consulted here<https://community.icann.org/x/CgATIg>. 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

MEETING CANCELLED | SubPro IRT Meeting #124 | 25 March 2025, 19:00-21:00 UTC
by Next Round Policy Implementation March 24, 2025

March 24, 2025

PLEASE NOTE THAT THIS MEETING HAS BEEN CANCELLED Dear All, Meeting #124 of the SubPro IRT will be held on 25 March 2025 at 19:00-21:00 UTC [local time [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/5xx95v5v__;!!PtGJab4!8ONDmge…>]. Planned topics: 4. Different TLD Types; Legal Compliance; Privacy Policy. The final agenda can be consulted here<https://community.icann.org/x/AwATIg>. 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

Information re IRT Calls on CPE
by Jared Erwin March 21, 2025

March 21, 2025

Dear IRT Members, As noted on the call just now, we discussed changes to the CPE criteria over a few different meetings. You can find all the Wiki meeting pages for those meetings below. Note that the ones highlighted in yellow are where we discussed changes to the criteria since 2012. The ones highlighted in blue are where we went through the “stress test” exercise (for .GIG). * August 9, 2024: 2024-08-29 | SubPro IRT | Meeting #66<https://community.icann.org/pages/viewpage.action?pageId=351404135> * October 24, 2024: 2024-10-24 | SubPro IRT | Meeting #82<https://community.icann.org/pages/viewpage.action?pageId=370442246> * October 30, 2024: 2024-10-30 | SubPro IRT | Meeting #83a<https://community.icann.org/pages/viewpage.action?pageId=387153938> * November 13, 2024: 2024-11-13 | SubPro IRT | Meeting #90 | ICANN81<https://community.icann.org/pages/viewpage.action?pageId=369328153> * November 21, 2024: 2024-11-21 | SubPro IRT | Meeting #93<https://community.icann.org/pages/viewpage.action?pageId=371327335> * December 5, 2024: 2024-12-5| SubPro IRT | Meeting #96<https://community.icann.org/pages/viewpage.action?pageId=371327349> * January 23, 2025: 2025-01-23 | SubPro IRT | Meeting #106<https://community.icann.org/pages/viewpage.action?pageId=450035741> In terms of further changes to the criteria, we can also take the action to review for any other changes made since the October/November time frame and update the information for the IRT’s awareness. And of course, we will look at making updates based on the discussion today. Thank you again for the discussion. 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>

3 2

Post call | SubPro IRT Meeting #123a | 20 March 2025
by Next Round Policy Implementation March 21, 2025

March 21, 2025

Dear All, The recordings for Meeting #123a of the SubPro IRT held on Thursday, 20 March 2025 are published on the meeting wiki page<https://icann-community.atlassian.net/l/cp/Qh77bi2H>. These include: * Audio recording * Zoom recording (including audio, visual, rough transcript, chat) * Attendance 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

REMINDER | SubPro IRT Meeting #123a | 20 March 2025, 18:00-20:00 UTC
by Next Round Policy Implementation March 20, 2025

March 20, 2025

Dear All, Meeting #123a of the SubPro IRT will be held in one hour on 20 March 2025 at 18:00-20:00 UTC [local time [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/2tu7dksf__;!!PtGJab4!4g2gv-E…>]. Planned topics: 36. Base Registry Agreement, CPE The final agenda can be consulted here [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/l/cp/Qh77b…>. 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 #123a | 20 March 2025, 18:00-20:00 UTC
by Pruis, Elaine March 19, 2025

March 19, 2025

Hi, Are there background documents available please? Elaine 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: Wednesday, March 19, 2025 at 11:00 AM To: "subpro-irt(a)icann.org" <subpro-irt(a)icann.org> Subject: [EXTERNAL] [SubPro-IRT] REMINDER | SubPro IRT Meeting #123a | 20 March 2025, 18:00-20:00 UTC 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 All, Meeting #123a of the SubPro IRT will be held on 20 March 2025 at 18:00-20:00 UTC [local time [tinyurl.com]] Planned topics: 36. Base Registry Agreement, CPE The final agenda can be consulted here [icann-community.atlassian.net] Before the meeting, please be sure you have read the ICANN Expected Standards of Behavior and the ICANN Community Anti-Harassment Policy. 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] 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

3 4

REMINDER | SubPro IRT Meeting #123a | 20 March 2025, 18:00-20:00 UTC
by Next Round Policy Implementation March 19, 2025

March 19, 2025

Dear All, Meeting #123a of the SubPro IRT will be held on 20 March 2025 at 18:00-20:00 UTC [local time [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/2tu7dksf__;!!PtGJab4!4g2gv-E…>]. Planned topics: 36. Base Registry Agreement, CPE The final agenda can be consulted here [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/l/cp/Qh77b…>. 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