- SubPro-IRT - lists.icann.org

REMINDER | SubPro IRT Meeting #150 | 7 August 2025, 12:00-14:00 UTC
by Next Round Policy Implementation Aug. 7, 2025

Aug. 7, 2025

Dear All, Meeting #150 of the SubPro IRT will be held in one hour on 7 August 2025 at 12:00-14:00 UTC [local time [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/3fzz56rz__;!!PtGJab4!_txXIJ0…>]. Planned topics: TBA The final agenda can be consulted here [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/AQC…>. 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

2 1

Post call | SubPro IRT Meeting #150 | 7 August 2025
by Next Round Policy Implementation Aug. 7, 2025

Aug. 7, 2025

Dear All, The recordings for Meeting #150 of the SubPro IRT held on Thursday, 7 August 2025 are published on the meeting wiki page<https://icann.zoom.us/rec/play/2Mq8Ps1zOpPJiqyHINKhhB5Ts5zRDuFHVbnL61qVTEUC…>. 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

Deck for IRT Meeting #150 (7 August 2025 @ 12 UTC)
by Jared Erwin Aug. 6, 2025

Aug. 6, 2025

Dear IRT Members, Please find attached the deck for tomorrow’s call. This deck includes the comments we will discuss and the relevant links to the updated language. As it relates to the comments that will be discussed tomorrow—recalling the request yesterday for information on comments that address “new” issues vs. previously discussed ones—in general, many of the comments received do address “new” issues. Most of the ones to be discussed tomorrow relate to typographical changes or request clarity of new text or things that may have changed since the previous comment. As we move forward to other topics, we will continue to provide this information, though in most cases, it does seem that the comments address issues not previously discussed. Thank you. 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 #150 | 7 August 2025, 12:00-14:00 UTC
by Next Round Policy Implementation Aug. 6, 2025

Aug. 6, 2025

Dear All, Meeting #150 of the SubPro IRT will be held on 7 August 2025 at 12:00-14:00 UTC [local time [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/3fzz56rz__;!!PtGJab4!_txXIJ0…>]. Planned topics: TBA The final agenda can be consulted here [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/AQC…>. 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

Post call | SubPro IRT Meeting #149 | 5 August 2025
by Next Round Policy Implementation Aug. 6, 2025

Aug. 6, 2025

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

Revised Spec 7, Section 1
by Jeffrey J. Neuman Aug. 5, 2025

Aug. 5, 2025

All, I have been working with Susan Payne, Susan Anthony, Katrin Ohlmer, Anne Aikman-Scalese, and Kathy Kleiman on the language for Specification 7. I can't say that everyone "approved" the language yet, but we wanted to get it out to the team with enough time for review. Below is the language followed by an explanation. Note: This includes incorporation of the IPC comment received during public comments (I hope ;)) * Rights Protection Mechanisms. Registry Operator shall implement and adhere to the rights protection mechanisms (“RPMs”) specified in this Specification. [and shall not restrict the ability of Trademark Holders to use the Sunrise Period (each as defined in the Trademark Clearinghouse Requirements) in contravention with the intent of such RPMs]. In addition to such RPMs, Registry Operator may develop and implement additional RPMs that discourage or prevent registration of domain names that violate or abuse another party’s legal rights. Registry Operator will include all RPMs required by this Specification 7 and any additional RPMs developed and implemented by Registry Operator in the Registry-Registrar Agreement entered into by ICANN accredited registrars authorized to register names in the TLD. Registry Operator shall implement in accordance with requirements set forth therein each of the mandatory RPMs set forth in the Trademark Clearinghouse as of the date hereof, as posted at https://www.icann.org/en/resources/registries/tmch-requirements [https://www.icann.org/en/resources/registries/tmch-requirements] (the “Trademark Clearinghouse Requirements”), which may be revised in immaterial respects by ICANN from time to time. Except as permitted by a Qualified Launch Program or an Approved Launch Program, Registry Operator shall not operate the TLD in such a way as to unfairly restrict the ability of Trademark Holders to use the Sunrise or to otherwise circumvent the purposes of the RPMs, which are set forth in paragraphs 1 and 2 of the Trademark Clearinghouse Requirements. Registry Operator shall not mandate that any owner of applicable intellectual property rights use any other trademark information aggregation, notification, or validation service in addition to or instead of the ICANN-designated Trademark Clearinghouse. If there is a conflict between the terms and conditions of this Agreement and the Trademark Clearinghouse Requirements, the terms and conditions of this Agreement shall control. Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar authorizing such registrar(s) to register domain names in the TLD as follows: [Rest of Provision ok] Rationale and How we got here 1) The text of Sunrise Recommendation #1 and Implementation Guidance in the Final RPM Phase 1 report states: "Sunrise Final Recommendation #1 The Working Group recommends that the Registry Agreement for future new gTLDs include a provision stating that a Registry Operator shall not operate its TLD in such a way as to have the effect of intentionally circumventing the mandatory RPMs imposed by ICANN or restricting brand owners’ reasonable use of the Sunrise RPM. Implementation Guidance: The Working Group agrees that this recommendation and its implementation are not intended to preclude or restrict a Registry Operator’s legitimate business practices that are otherwise compliant with ICANN policies and procedures." Despite it being called a "Sunrise Recommendation", the recommendation states that the RO shall not operate its TLD in such a way to to have the effect of intentionally circumventing the mandatory RPMs....or restricting brand owners' reasonable use of the Sunrise RPM." 2) ICANN staff has now come back and said we don't know how to implement this recommendation in the way it is worded because we don't know how to measure someone's intent. 3) In the version ICANN sent out for public comment it eliminated the "intentionally circumventing" language, and said simply that ROs may not restrict a TM owners ability to use the Sunrise. 4) ICANN's language has at least two problems which were pointed out in the comments the Registries (and Jeff) made and the comments made by the IPC. a) By removing the intent language, the words "reasonable use of the Sunrise", and ignoring the Implementation Guidance which talks about ROs legitimate business practices, the language creates a conflict between what is allowed in the TMCH documents (Separate from the Contracts). And all conflicts according to the provision state that the language in the Agreement control (meaning that even is something is allowed in the TMCH documents, if it is not allowed by the language in the agreement, ROs cannot do it. Therefore, the language in the Agreement would prevent ROs from delegating names through a Qualified Launch Plan prior to Sunrise. And this could prevent ROs from assigning names like subway.nyc, fire.miami, police.las vegas, beats.hiphop, Zoom.photo, etc. if it had to go through a Sunrise first as all of the terms are ones in which large companies own trademarks. This is why we have proposed making it clear that ROs CAN restrict trademark owners from using the Sunrise for these names IF they have been approved for use in a Qualified Launch Plan or an Approved Launch Plan. b) Our interpretation of the IPCs main comment is that the RPM Phase 1 recommendation includes all mandatory RPMs and not just Sunrise. And if you look at the language of the Recommendation, that appears to be true. The recommendation states ROs may not operate the TLD in a way that has the effect of intentionally circumventing the mandatory RPMs OR restricting brand owners' reasonable use of the Sunrise RPM. This is why we: (1) Made it apply to all mandatory RPMs, (2) exempted the QLPs and ALPs (which we believe was the intent for the Implementation Guidance), and added the word "unfairly" (as we believe was also the intent of the Recommendation. If you made it this far in reading the rationale, thank you for your attention ;) Sincerely, Jeff Neuman [a69ec41d-944e-42ca-8597-adbe54bf8f2e]

6 10

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

Aug. 5, 2025

Dear All, Meeting #149 of the SubPro IRT will be held in one hour on 5 August 2025 at 18:00-20:00 UTC [local time<https://tinyurl.com/54da932r>]. Planned topics: 36. Base Registry Agreement; Public Comment Overview and Work Plan. The final agenda can be consulted here<https://icann-community.atlassian.net/wiki/x/AYCNEw>. 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

FYI: RST Announcement
by Jared Erwin Aug. 5, 2025

Aug. 5, 2025

Dear IRT members, For your reference, please see the following announcement regarding Registry System Testing (RST) v2.0: https://www.icann.org/en/announcements/details/icann-launches-self-test-for…. Speak to you soon at 18:00 UTC. Thank you, Jared -- Jared Erwin Sr 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

SubPro IRT Meeting #149 - 5 August 2025
by Karla Hakansson Aug. 4, 2025

Aug. 4, 2025

Hello SubPro IRT members, The Next Round Base RA is the first topic on the agenda<https://icann-community.atlassian.net/wiki/spaces/SPIR/pages/328040449/2025…> for tomorrow’s SubPro IRT meeting #149. We have to topics to cover for the Next Round RA: 1. Recommendation 36.4- Fraudulent & Deceptive Practices: we will revisit the proposed language submitted by Chris Disspain on behalf of the RySG in meeting #148<https://icann.zoom.us/rec/share/rxmBLrvOw_2urNRwAq80AJPxBjwOLdrzuLNtp98npCh…> on 15 July (see the proposed language from 15 July and what was posted for public comment below). This is to confirm we have consensus among the SubPro IRT to post the latest draft language discussed on 15 July for the second public comment period on the Next Round Base RA in September. 2. We will review the proposed RPM language (Spec 7, Section 1) Jeff Neuman and a small team of SubPro IRT members (Susan Payne, Susan Anthony, Katrin Ohlmer, Anne Aikman-Scalese, and Kathy Kleiman) drafted. Jeff sent the proposed language earlier today. Best Regards, Karla Spec 11, Section 3 as proposed on 15 July: (e) Registry Operator shall not engage in the following fraudulent or deceptive business practices under this Agreement for the TLD: 1. Making false or misleading statements about registry services required by ICANN to be implemented by the registries where the false or misleading statement is material. 2. Implementing any Critical Function within the TLD with the effect of circumventing requirements under this Agreement or Consensus Policy or Temporary Policy. 3. Using deceptive advertising or marketing practices concerning the performance of Registry Services required by ICANN to be implemented by the registries; or 4. Any other fraudulent or deceptive conduct that ICANN determines in its reasonable discretion based on sufficient and verifiable evidence is a threat to the Security and Stability of registry services required by ICANN to be implemented by the registries or the DNS. Spec 11, Section 3(e) posted for the first of two public comments: e) Registry Operator shall not engage in the following fraudulent or deceptive business practices in performing any Critical Function as identified in Section 6 of Specification 10 under this Agreement for the TLD: 1. Making false or misleading statements about a Critical Function and the false or misleading statement is material; 2. Implementing any Critical Function within the TLD with the effect of circumventing requirements under this Agreement or Consensus Policy or Temporary Policy; 3. Using deceptive advertising or marketing practices concerning the performance of Critical Functions; or 4. Any other fraudulent or deceptive conduct that ICANN determines in its discretion based on sufficient evidence is a threat to the Security and Stability of Registry Services, Critical Functions, the Internet, or the DNS. A report filed by a Reporter (as defined in the PICDRP) pursuant to the PICDRP regarding this Section 3(e) of Specification 11 alleging actual harm as a result of noncompliance with this Section 3(e) of Specification 11 shall not fail the preliminary review under the PICDRP solely because the Reporter does not claim that it has been personally harmed.]

1 0

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

Aug. 4, 2025

Dear All, Meeting #149 of the SubPro IRT will be held on 5 August 2025 at 18:00-20:00 UTC [local time<https://tinyurl.com/54da932r>]. Planned topics: 36. Base Registry Agreement; Public Comment Overview and Work Plan. The final agenda can be consulted here<https://icann-community.atlassian.net/wiki/x/AYCNEw>. 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