- SubPro-IRT - lists.icann.org

Deck Meeting #154
by Elisa Busetto Aug. 21, 2025

Aug. 21, 2025

Hello IRT members, Just a quick note to let you know that we have published the deck for the call today: https://icann-community.atlassian.net/wiki/x/AYCPEw Best, Elisa

1 0

Post call | SubPro IRT Meeting #153a | 20 August 2025
by Next Round Policy Implementation Aug. 21, 2025

Aug. 21, 2025

Dear All, The recordings for Meeting #153a of the SubPro IRT held on Wednesday, 20 August 2025 are published on the meeting wiki page<https://icann-community.atlassian.net/wiki/x/AQDTFw>. 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

Requested edits on independent research deemed necessary to evaluate the application
by Kathy Kleiman Aug. 20, 2025

Aug. 20, 2025

Hi Jared and All, Thank you for the robust discussion on Thursday and review of comments and concerns about independent research. As you noted in the slides of Thursday and our discussion, SubPro Rec 34.21 provides for “*independent research deemed necessary to evaluate the application.*” That’s true. /How else can the Panel best evaluate the application, and the letters of opposition and support, as the Panel must? How else can they prepare and evaluate the “*CPE Clarifying Questions*” of 4.4.5.1?/ We appreciate your closing comment at the end of the call asking for specific wording input. We also appreciate Cheryl’s edits to the text below. The proposed wording does not change scoring, but opens it to the broader research we discussed last Thursday and that the SubPro WG recommended. We follow the closing comment of Thursday’s slides (p58):“/ICANN suggests that changes could be made to clarify the role of the panel as well as the role of the applicant’s claims. Further ICANN can clarify the language regarding ‘independent research’ and expectations for what the means.”/ We have worked hard, as requested, to help. ----------------- 1. First, the SubPro Recommendations: *Recommendation 34.21: “If the Community Priority Evaluation Panel conducts independent research while evaluating an application, limitations on this research and additional requirements must apply. The Working Group recommends including the following text in the Applicant Guidebook: “The Community Priority Evaluation Panel may perform independent research deemed necessary to evaluate the application (the “Limited Research”), provided, however, that the evaluator shall disclose the results of such Limited Research to the applicant and the applicant shall have an opportunity to respond. The applicant shall be provided 30 days to respond before the evaluation decision is rendered. When conducting any such Limited Research, panelists are cautioned not to assume an advocacy role either for or against the applicant or application.”*(Note: Implementation guidance 34.22 further strengthens this requirement) *Recommendation 34.19:* *“Letters of opposition to a community-based application, if any, /must be considered in balance with documented support for the application/.” *(emphasis added) II. Our recommendations for additions, clarifications, and a few edits are consistent with these recommendations, Jared’s invitation, and we think, the many comments received. 1. Recommend inserting into the broad language of 4.4.5 Community Priority Evaluation Outcomes, the specific language from SubPro Rec 34.21“The Working Group recommends including the following text in the Applicant Guidebook: *The Community Priority Evaluation Panel may perform independent research deemed necessary to evaluate the application (the Limited Research”), provided however that the evaluator shall disclose the result of such Limited Research to the applicant and the applicant shall have the opportunity to respond*.” 2. We note that many of the changes below will help the Panel in *4.4.5.1 CPE Clarifying Questions*. This section empowers the panel to issue questions not only to the CPE applicant but to those writing letters of opposition. Clearly, the panel will need to do the independent research it deems necessary to ask the right questions, and balance and weigh the answers (as required by Rec. 34.19) *(Referencing: 4.4.5.1: “The panel may issue CPE Clarifying Questions to applicants for applications participating in CPE. Clarifying Questions may also be directed to a person or entity that submitted a letter of opposition to a CPE applicant.”)* We further note SubPro WG’s /Rationale for Recommendations 34.17 and 34.18: /“The Working Group believes, however, that evaluators should have additional resources at their disposal to gather information about a CPE application and any opposition to that application.” 3. As requested, we share the following edits /to the CPE Scoring Criteria/ of 4.4.6, as necessary ways toimplement the broad direction and important tasks given to the CPE Panel 4.4.5.Broad language is good, but the “rubber hits the road” in the specifics of CPE Scoring in 4.4.6. Thus: *III. Specific CPE Scoring Guidelines Edits* 4. 4.4.7.1.1 Organization To Guidelines d. We recommend adding (consistent with 34.19 and 34.21 above & comments): ●“and other independent research deemed necessary to evaluate this section of the application in light of the materials presented by the applicant *and in letters of opposition and support.” * 5. 4.4.7.1.2 Engagement To Guidelines e. We recommend adding (consistent with 34.19 and 34.21 above & comments): => “and other independent research deemed necessary to evaluate this section of the application in light of the materials*presented by the applicant and in letters of opposition and support.*** 6. 4.4.7.1.3 Awareness To Guidelines b. We recommend adding (consistent with 34.19 and 34.21 above & comments): ●“and other independent research deemed necessary to evaluate this section of the application in light of the materials *presented by the applicant and in letters of opposition and support.** * 7. 4.4.7.1.4Established Presence To Guidelines c. We recommend adding (consistent with 34.19 and 34.21 above & comments): ●A new sentence: ”The Panel is expressly empowered to engage in the independent research it deems necessary to evaluate therecognition of the identified community by those outside of the identified community, includingthrough appropriate Internet searches, and evaluation of those submitting letters of opposition and supportfor the application.” 8. 4.4.7.1.5 Longevity To Guidelines c. We recommend adding (consistent with 34.19 and 34.21 above & comments): ●A new sentence: “The Panel is expressly empowered to engage in the independent research it deems necessary to evaluate the longevity of the applicant, including appropriate Internet searches, and review of letters of opposition and support for the application.” 9. 4.4.7.2 Nexus Note: Nexus has been described by ICANN Staff as a critical place in which outside input may join the evaluation of this CPE application. We agree, and to that end, offer the following language to clarify the independent research in which the panel may engage, should it seem necessary. To Guidelines, after e. (consistent with 34.19 and 34.21 above & comments): we suggest addition of subsection f: ●The Panel may perform the independent research it deems necessary to evaluate the evidence provided by the community in its letters of opposition and support and to assist in properly consider, in balance, the “letters of opposition to a community-based application, if any,” with the “documented support for the application.” 10. 4.4.7.4Criterion 4: Community Endorsement This CPE Scoring Criterion, as ICANN Staff has pointed out, is particularly important for public input and clarifying the role of the SubPro Recommendations on independent research will help.. To Guidelines for the scoring of support and opposition, consistent with policy and comments, we recommend adding: 1. In subsection a: After “does not have any relevant opposition,” to meet Rec 34.19 and 34.21 requirements and to truly evaluate and weigh the letters of support and opposition, add:=> “Letters of opposition to a community-based application must be considered *in balance* with documented support for the application.” 2. Subsection b, to meet the call of Rec 34.19 and 34.21, in this limited case, we recommend a change to the language, specifically:To subsection b: ●Change:“The panel should consider any objections or comments from this application round noting opposition. While these will be assessed, they do not automatically influence the Opposition score.” ●To: The panel may perform the independent research it deems necessary to evaluate this section of the application, and it *must consider *letters of opposition to the application, if any, in balance with the documented support for the application. 3. To subsection e, we propose an edit to not unduly limit the scope of the panel assessment: ●“The panel should assess whether reputable organizations… oppose the proposal and such opposition “must be considered in balance with the documented support for the application.” [Rec 34.19] IV. Finally, and pursuant to the SubPro Recs and implementation guidance, we think additional wording should be added to more clearly guide the Panel on how it communicates its limited research results to the applicant and writers of letters of opposition as required by policy. We defer to ICANN Staff for this procedural language. —------------------ Thank you for your review and consideration for the protection of vulnerable communities, indigenous peoples, linguistic groups, minorities and non-commercialorganizations that rely on fair andculturally competent evaluation processes. Best regards, Kathy and Juan Attachment:This doc in Word format

4 5

REMINDER | SubPro IRT Meeting #154 | 21 August 2025, 18:00-20:00 UTC
by Next Round Policy Implementation Aug. 20, 2025

Aug. 20, 2025

Dear All, Meeting #154 of the SubPro IRT will be held on 21 August 2025 at 18:00-20:00 UTC [local time [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/ye38cv4n__;!!PtGJab4!6_MCFsZ…>]. Planned topics: 15. Application Fees; 21. Reserved Names; 21a. Geographic Names The final agenda can be consulted here [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/AYC…>. 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://www.icann.org/en/governance/documents/icann-community-anti-harassme…>. 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

CPE Request for Proposal is now live
by Jared Erwin Aug. 20, 2025

Aug. 20, 2025

Dear IRT Members, Please find here the announcement for the opening of the CPE Request for Proposal process: https://www.icann.org/en/announcements/details/icann-request-for-proposal-c…. Speak to you all in 30 min. Best Jared -- Jared Erwin Senior 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>

1 0

REMINDER | SubPro IRT Meeting #153a | 20 August 2025, 18:30-20:00 UTC
by Next Round Policy Implementation Aug. 20, 2025

Aug. 20, 2025

Dear All, Meeting #153a of the SubPro IRT will be held in one hour on 20 August 2025 at 18:30-20:00 UTC [local time [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/2vpa3f82__;!!PtGJab4!6BzTgr7…>]. Planned topics: Module 4: CPE; Module 6: Name Collisions The final agenda can be consulted here [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/AQD…>. 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://www.icann.org/en/governance/documents/icann-community-anti-harassme…>. 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

"General Public" and Objections
by Juan Manuel Rojas Aug. 20, 2025

Aug. 20, 2025

Dear all, Regarding the objection process language discussed in our last meeting: The evolution from 'The General Public' to 'Parties with Standing' creates an unintended barrier. While 'standing' is legally precise, it's opaque to the very communities who may need objection procedures most. We are proposing hybrid language that maintains legal requirements while providing clear invitation and explanation: 'The General Public, provided they meet the requirements to file ("standing") [with a footnote to Table 3-1: Overview of the Objection Grounds, Parties with Standing [that we discussed last week]] Best, Juan JUAN MANUEL ROJAS, M.Sc. Director - MINKA DIGITAL ColombiaNPOC Chair - NCSG/GNSO M.Sc. Information Technology Registered Linux User No.533108. http://www.jmanurojas.com -----BEGIN GEEK CODE BLOCK-----Version: 3.1 GIT d- s: a+ C+++ UL P+ L+++ !E !W+++ !N !o K+++ w-- !O M- V PS+ PE-- Y+ PGP+ t+ 5 X++ R tv+ b+ DI D G e+++(+++)>+++ h+ r++ y+ ------END GEEK CODE BLOCK------

2 1

Deck for IRT Call #153a on 20 August 2025 at 18:30 UTC
by Jared Erwin Aug. 19, 2025

Aug. 19, 2025

Dear IRT Members, The deck for tomorrow’s call can be found on the meeting page here<https://icann-community.atlassian.net/wiki/spaces/SPIR/pages/399704065/2025…>. * The relevant language for Name Collision can be found in the Module 6 document: https://docs.google.com/document/d/1bNMs0Uve0CsSFjGDgbgIUs4nJj1gEjowKXWrNXr… * The relevant language for CPE can be found in the Module 4 document: https://docs.google.com/document/d/1rH19XrXglbfYj-TyioFsj4siNECKeR5J7Gfdvk3… Regarding CPE, and based on the NCSG’s input from today, we have made several updates to the guidelines to reflect this, as I believe it aligns with the general discussion on independent research from last week. Also, as noted, I’ve added a few summary slides regarding the comments to help facilitate our conversation tomorrow. I’d like to focus more on the AGB language/changes made based on comments. Thank you, Jared -- Jared Erwin Senior 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>

1 0

REMINDER | SubPro IRT Meeting #153a | 20 August 2025, 18:30-20:00 UTC
by Next Round Policy Implementation Aug. 19, 2025

Aug. 19, 2025

Dear All, Meeting #153a of the SubPro IRT will be held on 20 August 2025 at 18:30-20:00 UTC [local time [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/2vpa3f82__;!!PtGJab4!6BzTgr7…>]. Planned topics: Module 4: CPE; Module 6: Name Collisions The final agenda can be consulted here [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/AQD…>. 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://www.icann.org/en/governance/documents/icann-community-anti-harassme…>. 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

Auction RFI
by Lars Hoffmann Aug. 19, 2025

Aug. 19, 2025

Dear members of the IRT, Please feel free to share the announcement re: RFI for ICANN’s Next Round Auctions https://www.icann.org/en/announcements/details/icann-rfi-new-gtld-program-n… Many thanks and best wishes, Lars

1 0