May 2024 - SubPro-IRT - lists.icann.org

Cancellation IRT 4 June & upcoming topics
by Next Round Policy Implementation May 31, 2024

May 31, 2024

Dear IRT members, We would like to inform you that IRT meeting #46<https://community.icann.org/x/t4BREw> is canceled. We will discuss Terms and Conditions in Kigali or shortly after. We will finalize the agenda for meetings 47<https://community.icann.org/x/voBAEw>, 48<https://community.icann.org/x/xYBAEw> and 49<https://community.icann.org/x/zIBAEw>, which will be held during ICANN80, on Sunday 9 June, after the Board workshop in Kigali. Here is the list of topics in the pipeline for June: * Predictability (cont’d) * Application Queuing (cont’d) * Application Assessed in Rounds (cont’d) * Background Screening * Application Fees * Terms and Conditions We will make the materials available as soon as practical. Thank you for your patience! Best regards, Elisa

1 0

Post call | SubPro IRT Meeting #45 | 28 May 2024
by Renate De Wulf May 28, 2024

May 28, 2024

Dear All, The recordings for Meeting #45 of the SubPro IRT held on Tuesday, 28 May 2024 at 13:00-14:00 UTC are published on the meeting wiki page<https://community.icann.org/x/roBREw>. These include: * Attendance * Audio recording * Zoom recording (including audio, visual, rough transcript, chat) 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 #45 | 28 May 2024, 13:00-14:00 UTC
by Renate De Wulf May 28, 2024

May 28, 2024

Dear All, Meeting #45 of the SubPro IRT will be held in one hour on 28 May 2024 at 13:00-14:00 UTC [local time<https://tinyurl.com/28shc8cy>]. The agenda can be consulted here<https://community.icann.org/x/roBREw>. 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 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) Dial in directly with your local number: https://icann.zoom.us/u/abQbe1ODs 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

6 5

RSP fee
by Rubens Kuhl May 28, 2024

May 28, 2024

Having heard the RSP fee part of the May 21st meeting, I have to say I’m appalled by the proposed USD 92k RSP evaluation fee. Currently, the evaluation fee for a fully new, not known, RSP for 2012 gTLDs is USD 14,300. Source: https://www.icann.org/en/system/files/files/msa-change-guide-15dec21-en.pdf So if the RSP fee for 2026+ gTLDs is USD 92,000, this means that the self-regulating ICANN model is establishing a significant barrier of entry for new entrants to the gTLD market, which could raise anti-trust concerns with competition authorities. BTW, consultations from other Global South RSPs already indicate that we will have less, or none, such RSPs. And since there is no ASP for RSPs, we will likely cause ASP to fail again since ASP only provides for initial costs, and the running costs will be strongly-tied to the availability of RSPs willing to provide cheaper than usual services. Rubens

6 13

REMINDER | SubPro IRT Meeting #45 | 28 May 2024, 13:00-14:00 UTC
by Renate De Wulf May 28, 2024

May 28, 2024

Dear All, Meeting #45 of the SubPro IRT will be held on 28 May 2024 at 13:00-14:00 UTC [local time<https://tinyurl.com/28shc8cy>]. The agenda can be consulted here<https://community.icann.org/x/roBREw>. 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 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) Dial in directly with your local number: https://icann.zoom.us/u/abQbe1ODs 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

Status update on the new gTLD Program: Next Round is available
by Next Round Policy Implementation May 27, 2024

May 27, 2024

Dear all, Please note that the Pre-ICANN80 status update on the new gTLD Program: Next Round is now available for download: https://www.icann.org/en/system/files/files/status-update-new-gtld-program-…. A prep week session will take place on Tuesday 28 May at 18.00 UTC (see https://icann80.sched.com/event/1daZG/new-gtld-program-next-round-implement…) Best regards, Renate

1 0

Post call | SubPro IRT Meeting #44 | 23 May 2024
by Next Round Policy Implementation May 23, 2024

May 23, 2024

Dear All, The recordings for Meeting #44 of the SubPro IRT held on Thursday, 23 May 2024 at 14:00-15:00 UTC are published on the meeting wiki page<https://community.icann.org/x/poBREw>. These include: * Attendance * Audio recording * Zoom recording (including audio, visual, rough transcript, chat) 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

2 1

REMINDER | SubPro IRT Meeting #44 | 23 May 2024, 14:00-15:00 UTC
by Next Round Policy Implementation May 23, 2024

May 23, 2024

Dear All, Meeting #44 of the SubPro IRT will be held in one hour on 23 May 2024 at 14:00-15:00 UTC [local time<https://tinyurl.com/bddtsmc9>]. The agenda can be consulted here<https://community.icann.org/x/poBREw>. 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 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) Dial in directly with your local number: https://icann.zoom.us/u/abQbe1ODs 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

Awarding of Similar Strings to Same Entity operating prior TLD - Topic 24
by Anne ICANN May 23, 2024

May 23, 2024

Lars and Elisa, Regarding the section of the draft AGB shown below from Topic 24, could you please point me to the specific policy Recommendation that results in the conclusion that the only exception to the String Similarity ban on a subsequent application proceeding for a similar string is the Same Entity and RZ-LGR classified Variant determination? In other words, which PDP Policy Recommendation states that a similar string applied for by the same entity prior holder may not proceed unless the newly-applied for similar string is listed as an RZ-LGR variant? Was it formally deliberated on and determined in policy work that a similar string should not be awarded to the same entity operating a previously-awarded TLD unless the new similar string is a "variant"? Or are we saying that this question of a new application for a similar string to a previously-awarded TLD made by the "same entity" has not, in fact, been directly deliberated and addressed in policy work? (As you can imagine, this relates to the GNSO Council's recent request for an Issues Report in relation to the diacritics issues.) The AGB draft language re the only exception appears below. Thank you, Anne 1.4.1. Strings Similar With Existing gTLDs or their Variant Strings If any applied-for gTLD string or any of its variant strings is found to be Similar to any of the existing gTLDs or any of their variant strings, the gTLD application will not be able to proceed. *The exception is when the applied-for gTLD string is part of the same variant-strings-set as the existing gTLD it was found * *Similar to, and the applicant is the same registry operator, then the application can proceed with evaluation (as a variant gTLD). * Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2024 anneicanngnso(a)gmail.com

2 2

REMINDER | SubPro IRT Meeting #44 | 23 May 2024, 14:00-15:00 UTC
by Next Round Policy Implementation May 22, 2024

May 22, 2024

Dear All, Meeting #44 of the SubPro IRT will be held on 23 May 2024 at 14:00-15:00 UTC [local time<https://tinyurl.com/bddtsmc9>]. The agenda can be consulted here<https://community.icann.org/x/poBREw>. 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 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) Dial in directly with your local number: https://icann.zoom.us/u/abQbe1ODs 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