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

PICs/RVCs
by Lars Hoffmann Feb. 12, 2025

Feb. 12, 2025

Dear IRT members, Per my email<https://lists.icann.org/hyperkitty/list/subpro-irt@icann.org/thread/PGLC3NT…> from earlier, please see below links to the PICs/RVCs language that we will put out for public comment on Friday 14 February 2025. You find links to the redline version that shows edits and responses to comments and a clean version that will be published. A pdf of the clean version is also attached. Please note: feel free to share this document with your respective community groups, in case you’d like to start working already on the public comment. Best wishes, Lars Redline: https://docs.google.com/document/d/1H3IH5OZpV9q2JcMCI08Gd5tqTsI073sZbA_Wjs-… Clean https://docs.google.com/document/d/1Q72p72UHI_orulTfSOzfRrldQwEQT112evyN13s…

1 0

Contention Resolution
by Lars Hoffmann Feb. 12, 2025

Feb. 12, 2025

Dear IRT members, Per my email<https://lists.icann.org/hyperkitty/list/subpro-irt@icann.org/thread/PGLC3NT…> from earlier, please see below links to the Contention Resolution language that we will put out for public comment on Friday 14 February 2025. You find links to the redline version that shows edits and responses to comments and a clean version that will be published. A pdf of the clean version is also attached. Please note: feel free to share this document with your respective community groups, in case you’d like to start working already on the public comment. Best wishes, Lars Redline: https://docs.google.com/document/d/1WVOyH5lFZvppYkMw_LjVEliidbHfhj_-VfOCgaE… Clean: https://docs.google.com/document/d/1N5scLQJ9pas4O8Ze6NE2Qw_zNvKL9SA3DYdsBfN…

1 0

Material Impact
by Lars Hoffmann Feb. 12, 2025

Feb. 12, 2025

Dear IRT members, Per my email<https://lists.icann.org/hyperkitty/list/subpro-irt@icann.org/thread/PGLC3NT…> from earlier, please see below links to the Material Impact language that we will put out for public comment on Friday 14 February 2025. You find links to the redline version that shows edits and responses to comments and a clean version that will be published. A pdf of the clean version is also attached. Please note: feel free to share this document with your respective community groups, in case you’d like to start working already on the public comment. Best wishes, Lars Redline: https://docs.google.com/document/d/1qbxrnE-71jmzwfDwMMTGbqnuHU3WkUQXibZsXGb… Clean: https://docs.google.com/document/d/1z6BHdKj-ZwLQE8nBMfCrlA3B-NgkZdrUTfaiEpo…

1 0

CPE
by Lars Hoffmann Feb. 12, 2025

Feb. 12, 2025

Dear IRT members, Per my email<https://lists.icann.org/hyperkitty/list/subpro-irt@icann.org/thread/PGLC3NT…> from earlier, please see below links to the CPE language that we will put out for public comment on Friday 14 February 2025. You find links to the redline version that shows edits and responses to comments and a clean version that will be published. A pdf of the clean version is also attached. Please note: feel free to share this document with your respective community groups, in case you’d like to start working already on the public comment. Best wishes, Lars Redline: https://docs.google.com/document/d/1QLlUr21xxaZL2AK3zykg129o4YlVVwPI9tNzbmd… Clean: https://docs.google.com/document/d/13RA4Dp27OOMVyk4t7vYNTH-FITIdBj7yOiNZQ6W…

1 0

Application Change Request
by Lars Hoffmann Feb. 12, 2025

Feb. 12, 2025

Dear IRT members, Per my email<https://lists.icann.org/hyperkitty/list/subpro-irt@icann.org/thread/PGLC3NT…> from earlier, please see below links to the Application Change Request language that we will put out for public comment on Friday 14 February 2025. You find links to the redline version that shows edits and responses to comments and a clean version that will be published. A pdf of the clean version is also attached. Please note: feel free to share this document with your respective community groups, in case you’d like to start working already on the public comment. Best wishes, Lars Redline: https://docs.google.com/document/d/1xn8_wTInFG3n-Zx6n_JHW0nb26soPplsgTSZWxU… Clean: https://docs.google.com/document/d/1r3yOz5u9wDRd15_hy788qgLfZ0w9mfoSmFL5S09…

1 0

Fees
by Lars Hoffmann Feb. 12, 2025

Feb. 12, 2025

Dear IRT members, Per my email<https://lists.icann.org/hyperkitty/list/subpro-irt@icann.org/thread/PGLC3NT…> from earlier, please see below links to the Fees language that we will put out for public comment on Friday 14 February 2025. You find links to the redline version that shows edits and responses to comments and a clean version that will be published. A pdf of the clean version is also attached. We made the following updates were made in response to IRT input – as reflected in the redline: * Changed business days to calendar days * Clarified that payment is due upon receipt of invoice * Added ‘normally’ to provide discretion to ICANN org to accept late payment as an exception, if circumstances warrant * Removed section on terminations of applications from previous round * Added which strings were not approved in 2012 round due to risk of high risk of name collision We have left the term of “7 calendar days” following close of the application window as the deadline to receive payment as this payment is not the same as a fee for ongoing service for which different standards may apply. We also note that in the 2012 round, fees were due on the day of the close of the application window which did not seem to cause significant issues. We also confirmed that the sooner payment is confirmed, the sooner the next steps in the process can be completed, namely reveal day as payment for all strings needs to be confirmed before that can take place. Best wishes, Lars Redline: https://docs.google.com/document/d/1StflMJFVTXvgT_YcSeX5zoTcT825hoZCcD480zo… Clean: https://docs.google.com/document/d/1M-oDCjpa25d3G5jvwd_IKErmGJuQ47epcGCCPpn…

1 0

Path to Public Comment
by Lars Hoffmann Feb. 12, 2025

Feb. 12, 2025

Dear IRT members, First, I’d like to thank you all for the incredible workload you have put in over the past 20 months, and especially over the past few weeks with the high cadence of meetings and documents shared – it really has been an incredible lift by all! As discussed during today’s call, we will share updated documents with you on the mailing list today and tomorrow that show how we addressed your input. We will also share a clean version alongside it that will be posted for public comment on Friday. In a short while, I will share the following topics – all on separate emails so they are easy to track/search for on the mailing list and for you to respond to where needed: 1. PICs/RVCs 2. Contention Resolution 3. CPE 4. Material Impact (re: Predictability) 5. Application Change Request 6. Name Collison – including a separate response to Anne’s email<https://lists.icann.org/hyperkitty/list/subpro-irt@icann.org/thread/TJAGBWD…>. 7. RSP Selection [we made some addition edits to the document which we will also go through tomorrow]. 8. Fees No later than tomorrow (12 Feb) COB, Central European Time, we will share 1. Application Journey Following tomorrow’s IRT call (12 Feb 13:00 UTC) we will make updates to the documents discussed and then share by COB Pacific time, these documents as well as the other remaining documents, which are: 1. RSP Selection (again) 2. Code of Conduct 3. Brand Eligibility 4. Application Questions Unrelated to the IRT call we will also share by COB Pacific tomorrow (Wednesday 12 Feb): 1. Terms and Conditions I hope this all makes sense – this will allow us to publish the final public comment on Friday 14 February – which will close after 46 days on 1 April 2025. Again, thank you all very much for all the work you put into this to get us to this point. Very best. Lars

1 0

Re: [Ext] Re: Next Steps + Language on Fees and Application Questions
by Mike Rodenbaugh Feb. 12, 2025

Feb. 12, 2025

Thanks Lars for pointing me to the slide. Why do any of the other Activities listed in Window #2 need to happen, if the name collision wizard deems the string High Risk? If/when that happens, most applicants likely would drop out rather than deal with a minimum six month delay and hundreds of thousands of dollars to create a Mitigation Plan that could easily be rejected. [image: Logo] Mike Rodenbaugh *Rodenbaugh Law LLC* email: mike(a)rodenbaugh.com phone: +1 (415) 738-8087 On Tue, Feb 11, 2025 at 3:39 AM Lars Hoffmann <lars.hoffmann(a)icann.org> wrote: > Thanks, Mike. > > I know it’s not a great time, I am on pacific time this week as well so I > have two of those to cover … Marika will present on fees again today, and I > think slide 3 of the deck (link below) explains what is covered by the 35% > - I hope this helps. > > Very best. Lars > > > > > > Link to today’s deck on fees: > https://community.icann.org/pages/viewpage.action?pageId=472842248&preview=…) > > > > > > > > > *From: *Mike Rodenbaugh <mike(a)rodenbaugh.com> > *Date: *Monday, 10 February 2025 at 16:14 > *To: *Lars Hoffmann <lars.hoffmann(a)icann.org> > *Subject: *[Ext] Re: [SubPro-IRT] Next Steps + Language on Fees and > Application Questions > > > > I cannot make the call tomorrow at 5a.m. Pacific. I still see no > justification for ICANN keeping 35% of the application fee if a string is > deemed high risk of name collision. What will ICANN have done at that > point, other than intake of the application and review by the name > collision wizard? > > > > I also fully support Christa's comments and analysis re fee structure and > transparency. > > > > [image: Image removed by sender. Logo] > > *Mike Rodenbaugh* > > *Rodenbaugh Law LLC* > > *email:* > > mike(a)rodenbaugh.com > > *phone:* > > +1 (415) 738-8087 > > > > > > > > On Fri, Feb 7, 2025 at 8:36 AM Lars Hoffmann via SubPro-IRT < > subpro-irt(a)icann.org> wrote: > > Dear IRT members, > > > > Key points: > > 1. New Draft AGB language on fees [docs.google.com] > <https://urldefense.com/v3/__https:/docs.google.com/document/d/1icxkmmXmbT-x…> > that includes updates based on feedback received to-date (see more details > below) > 2. New Draft language for Application Questions [docs.google.com] > <https://urldefense.com/v3/__https:/docs.google.com/document/d/1icxkmmXmbT-x…> > 3. Email from Michael [lists.icann.org] > <https://urldefense.com/v3/__https:/lists.icann.org/hyperkitty/list/subpro-i…> > with updated draft language on CPE [docs.google.com] > <https://urldefense.com/v3/__https:/docs.google.com/document/d/1QLlUr21xxaZL…> > sent today > 4. 2 IRT calls next week covering: Tuesday > <https://community.icann.org/x/CAAvH>: fees, RA; Wednesday > <https://community.icann.org/x/DoBnHg>: Application questions, Spec 9 > and Spec 13 evaluation, and RSP selection. > 5. Public comment to open on 14 February for all remaining topics – > with a reminder that we will review all topics again and everything will go > out for comment again at the end of May. > > > > > > All the points: > > > > I wanted to thank you for all the hours you spent on calls, and helped to > improve the AGB language that we shared with you – *thank you*!! We > shared a lot of documents this week (and some more coming on Monday next > week), and so I wanted to end the week like I started, with an overview > email, please, bear with me. > > > > 1. We have currently *2 IRT sessions planned next week* (Tuesday and > Wednesday); a third is on the calendars (Thursday) but we will use that > only if we need to circle back to anything before the public comment. > Topics for these sessions are indicated below, and the wiki page has been > updated accordingly: https://community.icann.org/x/rAM5Dg > > > > a. *On Tuesday <https://community.icann.org/x/CAAvH>*, we will focus *on > Fees [docs.google.com] > <https://urldefense.com/v3/__https:/docs.google.com/document/d/1StflMJFVTXvg…> > and the RA*. You can now review the draft AGB *language on fees > [docs.google.com] > <https://urldefense.com/v3/__https:/docs.google.com/document/d/1StflMJFVTXvg…>,* > which includes updates based on the feedback we have received to-date, > including an additional refund window, refund options for strings that are > determined to be of high risk of collision, and refunds in case of material > changes to the AGB. Draft AGB Language: Application Fees [docs.google.com] > <https://urldefense.com/v3/__https:/docs.google.com/document/d/1StflMJFVTXvg…> > > b. *On Wednesday > <https://community.icann.org/pages/viewpage.action?pageId=510099470>*, we > will focus on three new documents: *Application Questions > [docs.google.com] > <https://urldefense.com/v3/__https:/docs.google.com/document/d/1icxkmmXmbT-x…>, > RSP Selection, Spec 9 and Spec 13* evaluations. The application > questions you can review as of now, the remaining three (much shorter) > documents we will share Monday morning (Pacific time). Please note: for > these topics we are just looking for a common-sense review. They do not > pertain to particular recommendations but are an important part of the AGB > and the application process. We will address any immediate concerns and > review these again in more detail after the public comment period. > > 2. *On Monday morning (PST) 10 February, we will close** the > following documents for comments in the run-up to the public comment, > meaning we will address input off-list as best as we cann and then revisit > these in the context of public comments received in April/early May: > > > > a. Material Impact for Predictability [docs.google.com] > <https://urldefense.com/v3/__https:/docs.google.com/document/d/1jbuangX5oMbG…> > > b. Application Change Request [docs.google.com] > <https://urldefense.com/v3/__https:/docs.google.com/document/d/1xn8_wTInFG3n…> > > c. CPE [docs.google.com] > <https://urldefense.com/v3/__https:/docs.google.com/document/d/1QLlUr21xxaZL…> > (Michael just shared an email [lists.icann.org] > <https://urldefense.com/v3/__https:/lists.icann.org/hyperkitty/list/subpro-i…> > and updated language taking into account recent IRT input) > > d. RVCs/PICs [docs.google.com] > <https://urldefense.com/v3/__https:/docs.google.com/document/d/1H3IH5OZpV9q2…> > > e. Terms and Conditions [docs.google.com] > <https://urldefense.com/v3/__https:/docs.google.com/document/d/1SX83JLEMJwG7…> > > f. Contention Resolution, including “no private resolution” > [docs.google.com] > <https://urldefense.com/v3/__https:/docs.google.com/document/d/1WVOyH5lFZvpp…> > > g. Applicant Journey [docs.google.com] > <https://urldefense.com/v3/__https:/docs.google.com/document/d/1jbuangX5oMbG…> > (we will share an updated document reflecting changes from yesterday’s > discussion <https://community.icann.org/x/AQAvH> on Monday 10 Feb) > > > *Any comments received, we will address in the document, either by > amending the text or providing a rationale why, for now, we will not make > any changes. The document will then be cleaned up and prepared for public > comment. We will revisit all items that are not closed out together with > any public comments received in April/early May. > > > > 3. We are working on an update to the Draft AGB text on *Name > Collision* – we expect to share that with the group on *Tuesday* 11 Feb. > We recognize that not all concerns that were raised will be fully addressed > in the document – still, I have asked the team to put the document out for > public comment on Friday, so that we can gather more input and also start > working on incorporating some of the feedback that we have heard from the > IRT already while the document is out for comment. I appreciate that this > is not idea, but I think we will make it work and of course this will be > part of the May public comment, too. > > > > 4. If need be, we can have another IRT call on Thursday 13 February > (in case not everything can be resolved on list or any of the topics > discussed Monday and Tuesday require additional time). However, our goal > remains to publish the *fourth public comment on Friday 14 February*. > Therefore, the Thursday call is strictly optional as making significant > changes to documents this late will impact the timeline. > > > > If you have any questions, please do not hesitate to reach out. And, > again, thank you so much for all your hard work and flexibility that you > have shown to help us get all of this across the public comment line. > > > > Very best. > Lars > > > > > > > > > > _______________________________________________ > SubPro-IRT mailing list -- subpro-irt(a)icann.org > To unsubscribe send an email to subpro-irt-leave(a)icann.org > > _______________________________________________ > By submitting your personal data, you consent to the processing of your > personal data for purposes of subscribing to this mailing list accordance > with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and > the website Terms of Service (https://www.icann.org/privacy/tos) You can > visit the Mailman link above to change your membership status or > configuration, including unsubscribing, setting digest-style delivery or > disabling delivery altogether (e.g., for a vacation), and so on. > >

2 1

Application Change Requests
by Elisa Busetto Feb. 11, 2025

Feb. 11, 2025

Dear IRT members, Please find here<https://docs.google.com/document/d/1xn8_wTInFG3n-Zx6n_JHW0nb26soPplsgTSZWxU…> the updated Application Change Requests (ACRs) language, which we will discuss during meeting #112<https://community.icann.org/x/AQAvH>, on 6 February at 19:00 UTC. We have made some changes since we last discussed the topic with the objective to streamline the process and provide as much information as possible to applicants regarding the different scenarios. We hope that these updates are helpful. What proved most difficult was finding ways to make sure that the community has the opportunity to provide their input on RVCs and community registration policies at the right time without delaying the processing of applications, which is why we developed a separate workflow for such changes. In summary, we propose that the ACRs that include RVCs and community registration policies will be published for application comments after the Registry Commitment Evaluation (RCE) is concluded. This proposed approach allows the community to provide their input on the ‘near final’ version of RVC/community registration policy that reflects the agreed to changes following negotiations between the applicant and ICANN during the RCE, and not just on the originally submitted version by the applicant that might not be approved by ICANN and have to undergo substantive changes. Nevertheless, for transparency and to ensure that community views are informed by any changes that occurred during the RCEn, ICANN will also publish the originally submitted RVC/ community registration policy for the community to review and provide comments. While we considered implementing this process like other types of ACRs (i.e., open a comment period before the RCE), we believe that the proposed approach is the most efficient path forward that will avoid the expenditure of community attention and resources to only review and comment on originally submitted commitments/policies that may not meet the criteria and, as such, would not be approved for inclusion in the applicable Registry Agreement if the application proceeds to delegation. ICANN will review the comments on both the ‘near final’ and originally submitted versions of commitments/policies and may re-initiate negotiations with the applicant based on input received during the comment period. However, if an RVC or community registration policy is submitted as part of the initial application, we propose to open the comment period before the RCE. This is to ensure transparency by publishing all relevant materials submitted during the initial application on the reveal day (e..g, RVC/community registration policy may only be a small part of the initial application). If the applicant and ICANN agree to certain changes to the commitment/policy during the RCE, the applicant will have to submit an ACR to reflect those agreed to changes. If the changes are material, another comment period will be opened, giving the chance to the community to provide their input on the ‘near final’ version of policy/commitment. Looking forward to going through the document tomorrow! Best, Ariel and Elisa

3 3

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

Feb. 11, 2025

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