- SubPro-IRT - lists.icann.org

Relationship of CPE and RCE
by Jeff Neuman 23 Jan '25

23 Jan '25

All, In preparation for a conversation on the relationship of the Community Priority Evaluation (CPE) process and its relationship to the Registry Commitments Evaluation process (RCE), I have prepared the following Google Doc: https://docs.google.com/document/d/1E0PDEIFuzRC180gEgj5hUYl4IgFuL7l_j79_E5h… which looks at certain registration policies of applicants that applied in the last round as community TLDs that became registries. Most of them did not go through CPE, but all of them had to propose their registration policies in their application as if they would be going through CPE and all of them have contractual requirements in their Agreements in Specification 12. Context for Discussion - 1. We now know that the ICANN Agreement in the future will no longer contain contractual provisions governing the use of content as this is not something that ICANN can enforce. 2. ICANN org has interpreted that to mean (I believe incorrectly) that registration policies submitted for CPE must not contain any provisions that govern the use of content (as those commitments will not pass RCE. 3. However, I believe that CPE is a separate and distinct process than RCE and that in order to qualify as a community many registries will still want to propose commitments not for inclusion in the ICANN Agreement, but rather to get endorsements from their community members and to run their registries. Again, these commitments would not be for ICANN to enforce, but rather for the Registry to implement and through its own set up enforcement mechanisms. 4. But the current language says that if a commitment does not pass RCE (meaning ICANN cannot enforce the commitment), then it cannot even be considered as part of CPE, which again I believe is wrong. Overall Points: The current language in proposed text states that any commitments in a registry policy (regardless of who is enforcing it) must pass RCE (ie, be enforceable by ICANN) in order to be considered in the CPE process. However, CPE should be able to consider commitments made by a registry regardless of whether they are intended to be in the ICANN Registry Agreement or not. Just because ICANN is not able to regulate content does not mean that the registries themselves cannot have policies (which they enforce privately) that do. And those policies are important for the community to see and evaluate. Take the following two examples: A. From .Bank (did not go through CPE because ended up uncontested): Registrants may not use its domain name for " any purposes prohibited by the bank’s charter or license." - Now we all know this is not something that ICANN can enforce and would unlikely pass RCE. But that does not mean that this requirement is not crucial to be contained in a registration policy and would be expected to be in an applicant's application for comment and for the purposes of getting community support. Therefore, to say that this should not be even considered in CPE does not make sense. B. From .sport (which passed CPE): "Registrant will not use the .Sport domain name for "Promoting and advocating any conduct and/or activity that constitutes or may constitute an anti-doping rule violation under the World Anti-Doping Code." - Again, we all know this is not intended for ICANN to enforce and would not be intended in the future to be contained within the ICANN Registry Agreement. It would not pass RCE. But to say that therefore it should not even be considered in CPE seems wrong. This policy may be critical to the Sport Community, and they would expect to see it in the registration policies. It may be required to get appropriate endorsements and support (which is evaluated under CPE). I am still looking for other community TLD policies and will update the Google Doc: https://docs.google.com/document/d/1E0PDEIFuzRC180gEgj5hUYl4IgFuL7l_j79_E5h… If anyone wants to help, please....... Sincerely, Jeff [cid:f2d6c99c-0808-4900-8afb-44cbfcd767ec]

4 5

REMINDER | SubPro IRT Meeting #106 | 23 January 2025, 19:00-20:00 UTC
by Next Round Policy Implementation 23 Jan '25

23 Jan '25

Dear All, Meeting #106 of the SubPro IRT will be held in one hour on 23 January 2025 at 19:00-20:00 UTC [local time [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/3nndkxku__;!!PtGJab4!5RmXIiB…>]. The agenda can be consulted here<https://community.icann.org/x/HQDTGg>. 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

REMINDER | SubPro IRT Meeting #106 | 23 January 2025, 19:00-20:00 UTC
by Next Round Policy Implementation 22 Jan '25

22 Jan '25

Dear All, Meeting #106 of the SubPro IRT will be held on 23 January 2025 at 19:00-20:00 UTC [local time [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/3nndkxku__;!!PtGJab4!5RmXIiB…>]. The agenda can be consulted here<https://community.icann.org/x/HQDTGg>. 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

Post call | SubPro IRT Meetings #105 | 21 January 2025
by Next Round Policy Implementation 21 Jan '25

21 Jan '25

Dear All, The recording for Meeting #105 of the SubPro IRT held on Tuesday, 21 January 2025 at 13:00-14:30 UTC are published on the meeting wiki page<https://community.icann.org/x/KABCGQ> 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 #105 | 21 January 2025, 13:00-14:30 UTC
by Next Round Policy Implementation 21 Jan '25

21 Jan '25

Dear All, Meeting #105 of the SubPro IRT will be held in one hour on 21 January 2025 at 13:00-14:30 UTC [local time [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/bdzh8x5c__;!!PtGJab4!-ZVFNuG…>]. The agenda can be consulted here<https://community.icann.org/x/KABCGQ>. 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>. 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

REMINDER | SubPro IRT Meeting #105 | 21 January 2025, 13:00-14:30 UTC
by Next Round Policy Implementation 20 Jan '25

20 Jan '25

Dear All, Meeting #105 of the SubPro IRT will be held on 21 January 2025 at 13:00-14:30 UTC [local time [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/bdzh8x5c__;!!PtGJab4!-ZVFNuG…>]. The agenda can be consulted here<https://community.icann.org/x/KABCGQ>. 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>. 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

Fwd: [Ext] Re: Re: Name Collision
by Mike Rodenbaugh 17 Jan '25

17 Jan '25

Hi All, Section 3 of this document re Initial Assessment needs to be fleshed out, a lot, please. The prefaces are important: Sec. 1 - The delegation of almost any new generic top-level domain carries some risk of Name Collision... Sec. 2 - Applicants should note that the metrics for an applied-for string are only one of several factors, both quantitative and qualitative in nature, that will be considered when assessing the risk associated with that string. Applicants should not assume that if the datasets indicate a low volume of name collision occurrences that the string will be assessed as safe to be delegated. Then, INITIAL ASSESSMENT: Sec. 3 - Each applied-for string will undergo an initial risk assessment by an expert evaluator using relevant data sets [examples given] ... and additional qualitative evidence data that can help deduce the severity of harm. The purpose of this assessment is to preliminarily identify *high-risk strings*. Strings assessed to be high-risk will be placed on the Collision String List (see Section 5 [docs.google.com] <https://urldefense.com/v3/__https:/docs.google.com/document/d/17VZM1Jx9Waw7…>) and any applications for these strings will not proceed until a High-Risk String Mitigation Plan has been completed. Initial Assessment will take place following the [String Confirmation Day]. ICANN will publish a report describing the assessment, its methodology, and findings, once completed. ________________ And that's it. This seems incredibly arbitrary on its face, and likely will result in a very significant expense and delay for any application identified as high-risk. So again I have some questions (some repeated, some new)... What specific and objective criteria will be used by the sole "expert evaluator" to decide whether any string is high-risk? How will anyone be a competent expert at this anyway, and how will they be chosen? How will any decision be challenged? How will any Risk Mitigation Plan be monitored if it is kept secret by ICANN? What really is the risk of undetectable malicious interference, which is the only purported reason to keep these Plans secret? Also, 3 months to come up with an acceptable Risk Mitigation Plan may not be enough. There appears to be very few people who understand any of this, much less can competently come up with a plan acceptable to whatever panel of experts ICANN hires, based on who knows what criteria. Those few people are likely to be in very high demand. There needs to be either a longer deadline, or at least an opportunity for an extension if applicant is making reasonable efforts towards developing a Plan. [image: Image removed by sender. Logo] *Mike Rodenbaugh* *Rodenbaugh Law LLC* *email:* mike(a)rodenbaugh.com *phone:* +1 (415) 738-8087 On Tue, Jan 14, 2025 at 10:15 AM Elisa Busetto via SubPro-IRT < subpro-irt(a)icann.org> wrote: Hi everybody, We have updated the Name Collision language [docs.google.com] <https://urldefense.com/v3/__https:/docs.google.com/document/d/17VZM1Jx9Waw7…> based on your feedback and will go through the changes during meeting #104 <https://community.icann.org/x/UACcG>. Best, Elisa *From: *Elisa Busetto <elisa.busetto(a)icann.org> *Date: *Wednesday, 8 January 2025 at 10:39 *To: *"subpro-irt(a)icann.org" <subpro-irt(a)icann.org> *Subject: *Name Collision Dear all, Happy New Year! Please find the proposed language [docs.google.com] <https://urldefense.com/v3/__https:/docs.google.com/document/d/17VZM1Jx9Waw7…> for Topic 29: Name Collision, which we will discuss today <https://community.icann.org/x/BgBWGQ>, 8 January at 13:00 UTC. Best regards, Elisa _______________________________________________ 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) 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.

3 3

Language for IRT Consideration - String Contention Procedures (Topic 35: Auctions) - 21 January 2025 Meeting
by Peter Eakin 17 Jan '25

17 Jan '25

Dear IRT Members, We are pleased to share proposed AGB language on “String Contention and Contention Resolution Procedures” for discussion at our upcoming meeting on Tuesday, 21 January 2025. The link to the language can be found here <https://docs.google.com/document/d/11IfWmW5NssmlTQimcsE6ttw3o42SPYdC5vlLVtw…> and relates to issues discussed in ‘Topic 35: Auctions’ of the Final Report. A PDF<https://community.icann.org/pages/viewpage.action?pageId=423755816&preview=…> version of this document is also available on the meeting page<https://community.icann.org/x/KABCGQ>. This draft does not contain language on procedures relating to Brand TLD String Change or resolving contention between Geographic Names – these issues are still being discussed internally and will be published and shared with the IRT as soon as possible in advance of our final meeting to discuss this topic, which is scheduled to take place on 5 February 2025. Should you have any questions or problems accessing the above links, please reach out in advance of the meeting. Thanks and best wishes, Peter Peter Eakin Policy Research Specialist, Policy Research & Stakeholder Programs Internet Corporation for Assigned Names and Numbers (ICANN) Office: 6 Rond Point Schuman, Bt. 1, Brussels B-1040, Belgium

1 0

LONGER CALL | SubPro IRT Meeting #107 | 28 January 2025, 13:00-15:00 UTC
by Next Round Policy Implementation 17 Jan '25

17 Jan '25

PLEASE NOTE THAT THIS CALL HAS BEEN EXTENDED BY AN HOUR, FROM 13:00 TO 15:00 UTC Dear All, Meeting #107 of the SubPro IRT will be held on 28 January 2025 at 13:00-15:00 UTC [local time<https://tinyurl.com/3mtttz96>]. The agenda can be consulted here<https://community.icann.org/x/JwDTGg>. 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

Post call | SubPro IRT Meetings #104 | 16 January 2025
by Next Round Policy Implementation 17 Jan '25

17 Jan '25

Dear All, The recording for Meeting #104 of the SubPro IRT held on Thursday, 16 January 2025 at 19:00-21:00 UTC are published on the meeting wiki page<https://community.icann.org/x/UACcG> 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