Thanks Lars.

Also, just want to reiterate my request for the proposed schedule or the selection of vendors including those providing evaluation services, the TMCH-related services, auction services, objection dispute, etc.

This will be helpful not just because it will give us an idea of when these things can be finalized, but also we may be able to help spread the word amongst interested vendors tp ensure ICANN gets a good competitive price for these services.

Sincerely,

Jeffrey J. Neuman
Founder & CEO
JJN Solutions, LLC
+1.202.549.5079
Jeff@jjnsolutions.com

From: Lars Hoffmann via SubPro-IRT <subpro-irt@icann.org>
Sent: Saturday, February 8, 2025 2:47 AM
To: Martin Sutton <martin@tldz.com>
Cc: Michael Karakash via SubPro-IRT <subpro-irt@icann.org>
Subject: [SubPro-IRT] Re: [Ext] Re: Re: Next Steps + Language on Fees and Application Questions
 

Thank you, Martin, for the clarification. After the IRT’s feedback on the unhelpfulness of t-shirt sizing the conditional evaluation fees during the call and on the list, Marika had indicated in her email to you on Wednesday, that we will take out these figures, which were based on our 2012 experiences. It seems more productive to continue discussing the conditional fees when we have some concrete offers from vendors on what the likely pass-through costs will be, by which time we should also have a more detailed understanding of the staff resources that may need to be involved in the admiration side of these evaluations.

Best wishes. Lars

 

 

From: Martin Sutton <martin@tldz.com>
Date: Saturday, 8 February 2025 at 08:23
To: Lars Hoffmann <lars.hoffmann@icann.org>
Cc: Rubens Kuhl <rubensk@nic.br>, Michael Karakash via SubPro-IRT <subpro-irt@icann.org>
Subject: [Ext] Re: [SubPro-IRT] Re: Next Steps + Language on Fees and Application Questions

 

Hi Lars,

 

I think Ruben’s may be referring to the additional fees on page 3, where these items remain blank.

 

Regards,

 

Martin

Martin Sutton


Co-Founder


E:  Martin@tldz.com



T:  +44 7774 556680




TLDz.com


Image removed by sender. image001.png



On 8 Feb 2025, at 07:12, Lars Hoffmann via SubPro-IRT <subpro-irt@icann.org> wrote:

Dear Rubens,

Thank you for kindly reaching out. When I checked the Google Doc just now, I could see the fee language. I also saw another external IRT member in the document. Version history seems to suggest the document had been available and not modified since before I sent the email yesterday. So perhaps the issue is at your end. In any case, attached is a PDF version that hopefully works.

Kind regards. Lars

 

 

 

From: Rubens Kuhl via SubPro-IRT <subpro-irt@icann.org>
Reply-To: Rubens Kuhl <rubensk@nic.br>
Date: Friday, 7 February 2025 at 20:48
To: Michael Karakash via SubPro-IRT <subpro-irt@icann.org>
Subject: [SubPro-IRT] Re: Next Steps + Language on Fees and Application Questions

 




1.      On Tuesday, we will focus on Fees [docs.google.com] and the RA. You can now review the draft AGB language on fees [docs.google.com], 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]

 

It would be nice to have the actual fees before the session. For now they are blank. 

 

 

Rubens

 

<EXT_Application Fees.pdf>

_______________________________________________
SubPro-IRT mailing list -- subpro-irt@icann.org
To unsubscribe send an email to subpro-irt-leave@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.