September 2024 - SubPro-IRT

Today's meetings
by Lars Hoffmann Sept. 19, 2024

Sept. 19, 2024

Hi everyone – In my earlier message I mentioned the wrong time for today/s IRT call – I am very sorry. To avoid any confusion, these are the times for today’s calls: 18-19 UTC: IRT ASP Sub-Track 19-20 UTC: Main IRT; topic: Registry Agreement Formal reminders for these will go out later today. Best. Lars

1 0

REMINDER | SubPro IRT Meeting #72 | 19 September 2024, 19:00-20:00 UTC
by Next Round Policy Implementation Sept. 18, 2024

Sept. 18, 2024

Dear All, Meeting #72 of the SubPro IRT will be held on 19 September 2024 at 19:00-20:00 UTC [local time<https://tinyurl.com/y46hsvp6>]. The agenda can be consulted here<https://community.icann.org/x/aoBVFQ>. 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) 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

Picking and Choosing Recommendations to Follow and not to Follow
by Jeff Neuman Sept. 17, 2024

Sept. 17, 2024

First, apologies I was not able to attend the meeting last night, earlier this morning. But in listening to the conversation, it sounds like ICANN is picking and choosing which SubPro Recommendations it is following and which they are not. On the call Elaine was absolutely correct. Yes, the PDP did not want people to change their strings. But the PDP also did not state that people could list alternate strings and that they could be switched prior to reveal day. This is a new factor introduced into the equation by ICANN. With this new factor being introduced, we now need to develop the best comprehensive solution or applicants and the community. If the PDP knew that you would be allowed to list alternate strings and changes would be made prior to reveal day, it is not a given that the PDP would have stuck to its recommendation to not allow the changing of strings after reveal day. Applicants are going to be investing a LOT of money and resources applying for a new TLD. The amount of their investment cannot be overstated. I talk to potential applicants every day. They are thoughtful, innovative, entrepreneurial, and take this extremely seriously. But when the ICANN Board/Org sits in its silo trying to come up with rules, it does not have the benefit of considering the real practical business implications. (And by business, I also include non-profits). For example, If I am electing to put in an application, I am committed to that string and that is one I know I can make work regardless of what anyone else applies for. If, however, I list an alternate string, I may be able to make that work, but not if someone else gets the primary string, and not if someone else has a separate but competing string, and therefore ICANN switching me automatically to the secondary string may not make sense for me or my business model. For example, Lets say I apply for .musicals. And then I list as an alternate .musicaltheater (with the er). Sure, perhaps I can make .musicaltheater work if there is contention with .musicals. But if I knew that someone else applied for .musicaltheatre (with the "re" as opposed to the "er"), then there is no way I would want .musicaltheater (with the "er"). Yet, under the ICANN new rule, I would be forced into the alternate string. NOTE: .theater and .theatre were BOTH allowed in the last round and were NOT found to be similar. If I had known that there was a .musicaltheatre application (with the "re"), then perhaps I would rather stick to the original contention set. But if there was not a .musicaltheatre application, then I would want to go to my alternate .musicaltheater. And it is not a satisfactory answer for ICANN to say, well that's just the way it is or then you shouldnt have listed an alternate. Applicants should not be treated like they are buying a $25 toy. They are spending $200k+ to apply, not to mention the time and money to draft the application, build a team, hire, get financing, etc. So, if we agree to change the process to allow alternate strings, then we need to adjust to best possible solution and not Pidgeon hole in an old recommendation that did not have this important new change. Sincerely, Jeff [cid:64ff4145-4c0c-4eab-b5b5-270b5119a3a1]

2 1

Post call | SubPro IRT Meeting #71 | 17 September 2024
by Next Round Policy Implementation Sept. 17, 2024

Sept. 17, 2024

Dear All, The recordings for Meeting #71 of the SubPro IRT held on Tuesday, 17 September 2024 at 04:00-05:00 UTC are published on the meeting wiki page<https://community.icann.org/x/X4BVFQ>. 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

Post call | SubPro IRT Meeting #70 | 17 September 2024
by Next Round Policy Implementation Sept. 17, 2024

Sept. 17, 2024

Dear All, The recordings for Meeting #71 of the SubPro IRT held on Tuesday, 17 September 2024 at 04:00-05:00 UTC are published on the meeting wiki page<https://community.icann.org/x/X4BVFQ>. 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 | CHANGE OF TIME | SubPro IRT Meeting #71 | 17 September 2024, 04:00-05:00 UTC
by Next Round Policy Implementation Sept. 17, 2024

Sept. 17, 2024

PLEASE NOTE THE CHANGE OF TIME – NEW TIME IS 04:00 UTC Dear All, Meeting #71 of the SubPro IRT will be held in one hour on 17 September 2024 at 04:00-05:00 UTC [local time<https://tinyurl.com/thacw2jk>]. The agenda can be consulted here<https://community.icann.org/x/X4BVFQ>. 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) 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

Board communication on Contention resolution
by Lars Hoffmann Sept. 16, 2024

Sept. 16, 2024

Dear all, Please find a link to today’s Blog<https://www.icann.org/en/blogs/details/a-path-forward-contention-set-resolu…> from Tripti on contention resolution. And also her letter to the GNSO Council<https://gnso.icann.org/sites/default/files/policy/2024/correspondence/sinha…> on the same topic. I suggest we spend some time discussing the content during tomorrow’s IRT Call<https://community.icann.org/x/X4BVFQ>. Pease note the call takes place 16 Sep 04:00 UTC [local time<https://www.timeanddate.com/worldclock/fixedtime.html?msg=SubPro+IRT+Meetin…>]. Very best. Lars Letter: https://gnso.icann.org/sites/default/files/policy/2024/correspondence/sinha… Blog: https://www.icann.org/en/blogs/details/a-path-forward-contention-set-resolu…

2 1

REMINDER | CHANGE OF TIME | SubPro IRT Meeting #71 | 17 September 2024, 04:00-05:00 UTC
by Next Round Policy Implementation Sept. 16, 2024

Sept. 16, 2024

PLEASE NOTE THE CHANGE OF TIME – NEW TIME IS 04:00 UTC Dear All, Meeting #71 of the SubPro IRT will be held on 17 September 2024 at 04:00-05:00 UTC [local time<https://tinyurl.com/thacw2jk>]. The agenda can be consulted here<https://community.icann.org/x/X4BVFQ>. 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) 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

Re: Updated Fee FAQ
by Pruis, Elaine Sept. 13, 2024

Sept. 13, 2024

Thanks Marika, One clarification that isn’t super obvious in the FAQ- “The RSP evaluation fee has been established at a maximum of USD $92,000 per RSP applicant.” “For this evaluation fee, an organization may be evaluated as one or more types of RSP1: 1) Main (including support for optional additional Registry Services and IDN tables), 2) DNS, 3) DNSSEC, and 4) Proxy. A successfully evaluated RSP may provide services to more than one gTLD.“ The intention is to say the organization (is this the same as an RSP applicant?) only pays one (max $92k) fee regardless of how many “Types” for which an RSP applicant is trying to be evaluated (main RSP + DNS + Proxy) ? Thanks for clarifying. Elaine From: Marika Konings via SubPro-IRT <subpro-irt(a)icann.org> Reply-To: Marika Konings <marika.konings(a)icann.org> Date: Friday, August 23, 2024 at 12:49 AM To: "subpro-irt(a)icann.org" <subpro-irt(a)icann.org> Subject: [EXTERNAL] [SubPro-IRT] Updated Fee FAQ Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Dear IRT, Please find attached the updated fee FAQ. Following further input from the Board, it was agreed to use the 1,500 applications scenario to set the gTLD evaluation fee. As you are aware, there are still two placeholders that need to be resolved before the final gTLD evaluation fee can be determined, namely the pending IDN EPDP Phase 1 recommendations as well as the SSAC advice on NCAP2. It is the expectation that the Board will address these two topics during its September workshop which would allow us to confirm the final gTLD evaluation fee following that. Note that in addition to confirming the 1,500 applications scenario, the FAQ also includes some further updates to address the different questions that were received during the ICANN80 sessions and/or mailing list. If there are further questions that need clarification in the FAQ, please feel free to flag those. We expect to come back to the IRT with further details once the ICANN Board has addressed the two placeholder items. Best regards, Marika

6 6

Post call | SubPro IRT Meeting #70 | 12 September 2024
by Next Round Policy Implementation Sept. 13, 2024

Sept. 13, 2024

Dear All, The recordings for Meeting #70 of the SubPro IRT held on Thursday, 12 September 2024 at 19:00-20:00 UTC are published on the meeting wiki page<https://community.icann.org/x/UoBVFQ>. 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