August 2025 - SubPro-IRT - lists.icann.org

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