- SubPro-IRT - lists.icann.org

CPE Scoring Spreadsheet
by Kathy Kleiman May 6, 2025

May 6, 2025

Hi All, I've put together a spreadsheet for CPE scoring. I offer it to you (attached) to test groups that you think /should pass/ and those you think /should not pass. / (Quick note: some scoring skips numbers.) I share Elaine Pruis' email of February and borrow her example of the Coin Family in my spreadsheet as a test. I am concerned that our newest version of the scoring puts the community scoring almost entirely in the evaluation of the community itself and not the larger world. Is that fair to larger communities using the same name? Won't there be gaming? Best, Kathy *----------------------------------* *From: *"Pruis, Elaine via SubPro-IRT" <subpro-irt(a)icann.org> *Reply-To: *"Pruis, Elaine" <epruis(a)verisign.com> *Date: *Friday, 7 February 2025 at 23:51 *To: *Michael Karakash <michael.karakash(a)icann.org>, "subpro-irt(a)icann.org" <subpro-irt(a)icann.org> *Subject: *[SubPro-IRT] Re: Updated Draft AGB Section for Topic 34: Community Applications Hello IRT, I had hoped to discuss this on a call, but have been asked to share to the list for discussion. Please read and provide feedback as CPE is about to go to public comment. There is a scenario where Community Priority could be gained by a very small group for a super generic string, which I don’t think aligns with the intention of providing this great advantage of avoiding ICANN auction via designation as a community. For ease of reference, here is the overall scoring section: 1.6.1 Criterion 1: Community Establishment This criterion relates to the community as explicitly identified according to statements in the application. The panel will seek to answer the following core questions in evaluating the application against this criterion: * Organization (2 points): Is the applicant the organizing body for the community? If not, is the applicant able to demonstrate that the community is organized, with an organizing body(ies) relevant to the community or to each member category of the community? * Engagement (1 point): Is the applicant able to demonstrate that there is active engagement with community members? * Awareness (1 point): Is the applicant able to demonstrate awareness among and between community members of the identified community? * Longevity (1 point): Is the applicant able to demonstrate the longevity of the community's pursuits, showing that they are enduring and sustainable rather than temporary? Here is the scenario. The application is for .coin, and the applicant represents a multigenerational family with the surname “Coin” . The applicant Mr. Coin Sr. has created an LLC and that LLC “Coin TLD” is the organizing body /for the community “as defined by the applicant/” (“My family, the Coin Klan is a community” says Mr. Coin). Mr. Coin Sr. can claim the family including Ms. Coin, Mr. Coin Jr. and Sister Coin have appointed him and the LLC as the organizing body for their Coin community. They are actively engaged with each other, even on a daily basis (“Dad can I have a ride to the movies?” says Sister Coin. They then spend lots of time in the car interacting. They text each other every day). Clearly the entire family is fully aware of their community and know they are part of the Coin Klan. The Coin community was established generations ago and since Mr. Coin Jr. has two kids and is expecting a baby soon, they can demonstrate longevity, sustainability, and prove they are not merely a temporary Klan. The opportunity for the Coin Klan to win .coin over any other applicant is real, but the delegation of a super generic string to a community such as The Coin Klan over any other applicant seems counter to the spirit of the recommendation. Can we add some language that prevents this sort of opportunism? Should there be extra scrutiny or higher points required when a super generic string is in play? Elaine

2 3

REMINDER | SubPro IRT Meeting #137 | 6 May 2025, 12:00-14:00 UTC
by Next Round Policy Implementation May 6, 2025

May 6, 2025

Dear All, Meeting #137 of the SubPro IRT will be held in one hour on 6 May 2025 at 12:00-14:00 UTC [local time [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/yka7wcpc__;!!PtGJab4!-VLDs72…>]. Planned topics: Planned topics: 9. PICs/RVCs; CPE The final agenda can be consulted here [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/KAD…>. 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

Overview of topics
by Lars Hoffmann May 6, 2025

May 6, 2025

Dear IRT members, As we are nearing the final public comment, Ilana has kindly put together a very helpful overview table (at least I think so) that provides easy access to the different topics/documents; a pdf version is attached. We will replicate the table on the wiki<https://icann-community.atlassian.net/wiki/x/B4CeDw> as soon as practicable, too. Please note, that the table reflects current planning. Similarly, we know that on several topics, such as RSP selection, Name Collision, Application Journey, etc., Fees, etc., we are still working on redline updates to reflect recent IRT input. We will share these as soon as they become available, but we do not believe, at this stage, that additional meetings are necessary. Thank you and best wishes, Lars

2 2

REMINDER | SubPro IRT Meeting #137 | 6 May 2025, 12:00-14:00 UTC
by Next Round Policy Implementation May 5, 2025

May 5, 2025

Dear All, Meeting #137 of the SubPro IRT will be held on 6 May 2025 at 12:00-14:00 UTC [local time [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/yka7wcpc__;!!PtGJab4!-VLDs72…>]. Planned topics: 9. PICs/RVCs; CPE The final agenda can be consulted here [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/KAD…>. 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

EARLIER TIME | SubPro IRT Meeting #138 | 8 May 2025, 12:00-14:00 UTC
by Next Round Policy Implementation May 5, 2025

May 5, 2025

WE ARE MOVING THIS MEETING TO AN EARLIER TIME, NOW STARTING AT 12:00 UTC. PLEASE DO NOT FORGET TO ADJUST YOUR CALENDARS Dear All, Meeting #138 of the SubPro IRT will be held on 8 May 2025 at 12:00-14:00 UTC [local time<https://tinyurl.com/mr2jnwhr>]. Planned topics: Contention Sets – No Collusion Language; Terms & Conditions The final agenda can be consulted here<https://icann-community.atlassian.net/wiki/x/TwDMCg?atlOrigin=eyJpIjoiYWU4Y…>. 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: IMPORTANT: PLEASE READ!
by Lars Hoffmann May 4, 2025

May 4, 2025

Thanks, Marc. We will work with the team to bring this call forwarded by a few hours. Likely we will change it to the 12-14 UTC slot – but I need to confer with the team on Monday before changing invites, etc. I wanted to set expectations for the call, that I believe we are unlikely to require the full 2h and hope to share updated redlines in advance to ensure the discussion can proceed as smoothly as feasible. Best. Lars From: "trachtenbergm(a)gtlaw.com" <trachtenbergm(a)gtlaw.com> Date: Friday, 2 May 2025 at 11:14 To: Lars Hoffmann <lars.hoffmann(a)icann.org>, "subpro-irt(a)icann.org" <subpro-irt(a)icann.org> Subject: [Ext] Re: IMPORTANT: PLEASE READ! Thanks Lars. But the problem with the May 8 call is that as I mentioned on the last call many are leaving CPS that day including me. The call on May 8 will be at 11pm Hanoi time which is when my flight is and I would like to participate in the discussion of contention set resolution and the anti-collision rules. Best regards, Marc Trachtenberg Chair, Internet, Domain Name, eCommerce, and Social Media Practice Greenberg Traurig, LLP 77 West Wacker Drive Chicago,IL 60613 (O) +1.312.456.1020 (M) +1.773.677.3305 Trac(a)gtlaw.com ________________________________ From: Lars Hoffmann via SubPro-IRT <subpro-irt(a)icann.org> Sent: Friday, May 2, 2025 5:43:56 PM To: Anne ICANN via SubPro-IRT <subpro-irt(a)icann.org> Subject: [SubPro-IRT] IMPORTANT: PLEASE READ! *EXTERNAL TO GT* Dear IRT members, Due to the contracted parties’ summit that many of you are attending, we are making an important change to next week’s agenda: We will now have the meeting on CPE and RVCs/PICs on Tuesday, 6 May, from 12:00-14:00 UTC. [cid:image001.png@01DBBCD9.D5279DB0] This will hopefully allow as many of you as possible to participate. I’d like to thank our LA-based team for being extremely flexible and able to present and lead the discussion at 5am local time. In return, on Thursday 8 May we will have a follow up on Terms and Condition and Contention Resolution. I am planning to post updated redline language on-list before the meeting. Calendar invites, wiki pages, etc. will be updated accordingly. Thank you and best wishes, Lars

2 1

Updated Topic 9 AGB Text: PICs/RVCs/Community Registration Policies
by Ariel Liang May 2, 2025

May 2, 2025

Dear IRT Members, Please find here the updated Topic 9 AGB text in preparation for our call on 8 May. * Clean version: https://docs.google.com/document/d/1v150Usag-3uYRH2e8pSjWa49k9nWcytM963JSTM… - heading=h.ri1736pcfxf1<https://docs.google.com/document/d/1v150Usag-3uYRH2e8pSjWa49k9nWcytM963JSTM…> * Redline version (compared to the version published for Public Comment – see v05_2025-05-08): https://icann-community.atlassian.net/wiki/spaces/SPIR/pages/112200175/1.+W… - :~:text=Proposed AGB Language_v05_2025-05-08 %5BRedlines%5D.pdf<https://icann-community.atlassian.net/wiki/spaces/SPIR/pages/112200175/1.+W…> Please note that the updates reflect input received from public comments, which we discussed during the 16 April<https://icann-community.atlassian.net/wiki/spaces/SPIR/pages/112203289/2025…> meeting. In addition, there are substantive updates for footnote 11 (pp.10-11), Section 3.2.4 (pp.15), footnote 13 (p.16), and first paragraph of Section 4 and footnote 19 (p.21). These updates intend to address input from the IRT during our 16 April meeting. Look forward to our discussion next week! Best Regards, Ariel

4 7

CANCELLED | SubPro IRT Meeting #139a | 14 May 2025, 06:00-07:00 UTC
by Next Round Policy Implementation May 2, 2025

May 2, 2025

Dear All, Meeting #139a of the SubPro IRT of 14 May 2025 at 06:00-07:00 UTC [local time<https://tinyurl.com/42bkn7vp>] has been cancelled. Best regards, Renate

1 0

IMPORTANT: PLEASE READ!
by Lars Hoffmann May 2, 2025

May 2, 2025

Dear IRT members, Due to the contracted parties’ summit that many of you are attending, we are making an important change to next week’s agenda: We will now have the meeting on CPE and RVCs/PICs on Tuesday, 6 May, from 12:00-14:00 UTC. [cid:image001.png@01DBBB4F.1A4FF5E0] This will hopefully allow as many of you as possible to participate. I’d like to thank our LA-based team for being extremely flexible and able to present and lead the discussion at 5am local time. In return, on Thursday 8 May we will have a follow up on Terms and Condition and Contention Resolution. I am planning to post updated redline language on-list before the meeting. Calendar invites, wiki pages, etc. will be updated accordingly. Thank you and best wishes, Lars

2 1

Implementation of Sub Pro Final Report Recommendation 36.4
by Anne ICANN May 1, 2025

May 1, 2025

Hi Karla, Susan and I will need to meet the Council deadline of May 5 to get the issue of implementation of Recommendation 36.4 on the agenda. Accordingly, we need your redline of this section in the existing Base Registry RA and explanation of the ICANN Org position on this language no later than* May 2* since we will need to provide a cover memo to Leadership. It may be best to copy the full IRT on your response, but we leave that to your discretion. Thank you, Anne and Susan Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso(a)gmail.com

2 4