- SubPro-IRT - lists.icann.org

Follow-up on Registration Polices, RCE, and CPE
by Jared Erwin Feb. 4, 2025

Feb. 4, 2025

Dear IRT members, I’m following up on our discussion regarding Community Registration Policies, Registry Commitment Evaluation (RCE), and Community Priority Evaluation (CPE). Please see attached emails for some background on this discussion as well as the recording of our call (from 23 Jan 2025) here: https://community.icann.org/x/HQDTGg. During our discussion on 23 January, ICANN heard divergent views on how it should evaluate the registration policies of an applicant applying for a community TLD and opting to participate in CPE. On the one hand, there seemed to be a call for ICANN to award more points for registration policies that would potentially limit content, which ICANN could not enforce per the Bylaws. On the other hand, there seemed to be a call to remove registration policies altogether as a sub-criterion because they may in some way relate to content. ICANN agrees that there may be policies that a community applicant wishes to have in place that would not or could not go into the RA and that these may be used to garner support for a community TLD. However, if these are not in Specification 12 of the Registry Agreement, or do not pass RCE, then they could not be enforced by ICANN and these would be between the applicant and the community or any other third party. As noted in the proposed AGB language on PICs/RVCs<https://community.icann.org/display/SPIR/1.+Working+Documents?preview=/3154…> (pdf<https://community.icann.org/download/attachments/315490346/Proposed%20AGB%2…>): “ICANN will only evaluate community registration policies that are proposed by applicants for inclusion in the applicable RA. Registry operators may implement any other community registration policies outside of the RA which are desired, so long as the policies otherwise comply with the applicable ICANN agreements and policies. Community registration policies that are not evaluated and approved for inclusion in the RA are not subject to ICANN contractual compliance oversight because they are not included in the applicable RA” ICANN would also like to remind the IRT that CPE is an optional evaluation used for resolving contention. For that reason, CPE sets a high bar, which would include Community Registration Policies that are enforceable by ICANN. As noted in the proposed AGB language for CPE<https://docs.google.com/document/d/1JEnYgVuRwXR_x8I59hpe8MNLBmjsgOK3hivz-1K…> (pdf<https://community.icann.org/download/attachments/315490346/CLEAN_EXT_Topic%…>): “It should be noted that a qualified community application receives priority over all directly contending applications. This is a fundamental reason for very stringent requirements for qualification of a community-based application, as embodied in the criteria below. Accordingly, a finding by the panel that an application does not meet the scoring threshold to prevail in a community priority evaluation is not an indication the community itself is in some way inadequate, invalid, or does not exist, but rather that it does not qualify to receive priority over all other applications in the contention set.” As Lars noted in his email to the IRT yesterday (3 February 2025), at this stage, we are looking to identify issues where proposed language does not align with wording or intent of the recommendations. Given this array of input and based on previous discussions regarding CPE and RCE more generally, ICANN has not identified any changes to the language that should be made at this time related to Community Registration Policies and CPE prior to moving to public comment. ICANN can commit to revisiting this issue further after we have received public comments on these topics (PICs/RVCs and Community Applications). Please note, I plan to send out the updated proposed AGB language for CPE by Thursday, 6 February. Thank you again for your time and dedication to these topics. 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>

1 0

Post call | SubPro IRT Meetings #110 | 4 February 2025
by Next Round Policy Implementation Feb. 4, 2025

Feb. 4, 2025

Dear All, The recording for Meeting #110 of the SubPro IRT held on Tuesday, 4 February 2025 at 13:00-15:00 UTC are published on the meeting wiki page<https://community.icann.org/x/AoAsH>. 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

CHANGE OF TIME | SubPro IRT Meeting #113a | 12 February 2025, 13:00-15:00 UTC
by Next Round Policy Implementation Feb. 4, 2025

Feb. 4, 2025

PLEASE NOTE THAT THIS CALL WILL NOW TAKE PLACE AT 13:00 UTC Dear All, Meeting #113a of the SubPro IRT will be held on 12 February 2025 at 13:00-15:00 UTC [local time<https://tinyurl.com/4kt63ukh>]. The agenda can be consulted here<https://community.icann.org/x/DoBnHg>. 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

Name Collision
by Elisa Busetto Feb. 4, 2025

Feb. 4, 2025

Dear all, Happy New Year! Please find the proposed language<https://docs.google.com/document/d/17VZM1Jx9Waw7qKnkSZ5Hx8CeRwosFiSlB_ZGXrV…> 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

1 3

REMINDER | SubPro IRT Meeting #110 | 4 February 2025, 13:00-15:00 UTC
by Next Round Policy Implementation Feb. 4, 2025

Feb. 4, 2025

PLEASE NOTE THAT THIS CALL HAS BEEN EXTENDED TO TWO HOURS Dear All, Meeting #110 of the SubPro IRT will be held in one hour on 4 February 2025 at 13:00-15:00 UTC [local time<https://tinyurl.com/yhtcjkz4>]. The agenda can be consulted here<https://community.icann.org/x/AoAsH>. 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 #111 | 5 February 2025, 05:00-07:00 UTC
by Next Round Policy Implementation Feb. 4, 2025

Feb. 4, 2025

PLEASE NOTE THAT THIS CALL HAS BEEN EXTENDED TO TWO HOURS Dear All, Meeting #111 of the SubPro IRT will be held on 5 February 2025 at 05:00-07:00 UTC [local time<https://tinyurl.com/5n7ehe7t>]. The agenda can be consulted here<https://community.icann.org/x/CYAsH>. 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

Material Impact: Review before Feb 2025 public comment
by Lars Hoffmann Feb. 3, 2025

Feb. 3, 2025

Dear IRT members, Per my earlier email<https://lists.icann.org/hyperkitty/list/subpro-irt@icann.org/thread/ZPAAKQS…> today, here is the link to the AGB draft text on Material Impact: https://docs.google.com/document/d/1qbxrnE-71jmzwfDwMMTGbqnuHU3WkUQXibZsXGb… Please review the document by Monday 10 February 2024 at 2359 UTC, focus on issues that do not align with the language or intent of relevant recommendations. As reminder, we plan to publish this document for public comment on Friday 14 February 2025. Following the public comment, we will discuss comments received, and publish this text as part of the full AGB by the end of May and then we will discuss this issue again as part of the review of the comments on the entire draft AGB in Q3 of 2025. Many thanks and best wishes, Lars PS: PDF attached

1 0

PICs/RVCs: Review before Feb 2025 public comment
by Lars Hoffmann Feb. 3, 2025

Feb. 3, 2025

Dear IRT members, Per my earlier email<https://lists.icann.org/hyperkitty/list/subpro-irt@icann.org/thread/ZPAAKQS…> today, here is the link to the AGB draft text on PICs/RVCs: https://docs.google.com/document/d/1H3IH5OZpV9q2JcMCI08Gd5tqTsI073sZbA_Wjs-… Please review the document by Monday 10 February 2024 at 2359 UTC, focus on issues that do not align with the language or intent of relevant recommendations. As reminder, we plan to publish this document for public comment on Friday 14 February 2025. Following the public comment, we will discuss comments received, and publish this text as part of the full AGB by the end of May and then we will discuss this issue again as part of the review of the comments on the entire draft AGB in Q3 of 2025. Many thanks and best wishes, Lars PS: PDF attached

1 0

Terms and Conditions: Review before Feb 2025 public comment
by Lars Hoffmann Feb. 3, 2025

Feb. 3, 2025

Dear IRT members, Per my earlier email<https://lists.icann.org/hyperkitty/list/subpro-irt@icann.org/thread/ZPAAKQS…> today, here is the link to the AGB draft text on Terms and Conditions: https://docs.google.com/document/d/1SX83JLEMJwG7Ja-qiTCJDm2v7je_717cQTppwXJ… Please, note that I will address some initial feedback received during Tuesday’s or Wednesday’s call this week (subject to time availability). Please review the document by Monday 10 February 2024 at 2359 UTC, focus on issues that do not align with the language or intent of relevant recommendations. As reminder, we plan to publish this document for public comment on Friday 14 February 2025. Following the public comment, we will discuss comments received, and publish this text as part of the full AGB by the end of May and then we will discuss this issue again as part of the review of the comments on the entire draft AGB in Q3 of 2025. Many thanks and best wishes, Lars PS: PDF attached

1 0

Contention resolution: Review before Feb 2025 public comment
by Lars Hoffmann Feb. 3, 2025

Feb. 3, 2025

Dear IRT members, Per my earlier email<https://lists.icann.org/hyperkitty/list/subpro-irt@icann.org/thread/ZPAAKQS…> today, here is the link to the AGB draft text on Contention Resolution*: https://docs.google.com/document/d/1WVOyH5lFZvppYkMw_LjVEliidbHfhj_-VfOCgaE… Please review the document by Monday 10 February 2024 at 2359 UTC, focus on issues that do not align with the language or intent of relevant recommendations. As reminder, we plan to publish this document for public comment on Friday 14 February 2025. Following the public comment, we will discuss comments received, and publish this text as part of the full AGB by the end of May and then we will discuss this issue again as part of the review of the comments on the entire draft AGB in Q3 of 2025. Many thanks and best wishes, Lars PS: PDF attached *Please note, the language on ‘no private resolution’ has not been shared yet. This topic will be subject to a walkthrough on Wednesday 5 February (5:00 UTC)

1 0