<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body dir="auto">
Sam,
<div><br>
</div>
<div>Can you clarify what you mean by “sealed bids”? Are you suggesting applications submit sealed bids for their application fees?<br>
<div>
<div dir="ltr">
<div><br>
</div>
<div>Best Regards,</div>
<b>
<div><b><br>
</b></div>
Marc H.Trachtenberg</b>
<div>
<div>Shareholder</div>
<div>Greenberg Traurig, LLP</div>
<div>77 West Wacker Drive</div>
<div>Chicago, IL 60601</div>
<div>Office (312) 456-1020</div>
<div>Mobile (773) 677-3305</div>
</div>
</div>
<div dir="ltr"><br>
<blockquote type="cite">On Jun 14, 2024, at 11:23 AM, Sam Lanfranco <samlanfranco@gmail.com> wrote:<br>
<br>
</blockquote>
</div>
<blockquote type="cite">
<div dir="ltr">
<div><font color="#0e0e3f"><b>*EXTERNAL TO GT*</b><br>
<br>
</font></div>
<div dir="auto">As an economist too prefer a refund to a credit, which only applies if an applcation is going forward.<br>
<br>
</div>
<div dir="auto">I also support sealed bids. No strategic gaming. Applicants give it there best shot, and the envelopes are opened. No drama, full stop.<br>
<br>
</div>
<div dir="auto">Sam Lanfranco<br>
<br>
<br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->Internet Elder, Internet Ecologist, 416 816-2852<!-- tmjah_g_1299e --></div>
<div class="gmail_quote">On Jun 13, 2024, at 1:25 p.m., Justine Chew <<a href="mailto:justine.chew.icann@gmail.com" target="_blank">justine.chew.icann@gmail.com</a>> wrote:
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div dir="auto">
<div>Perhaps, give applicants a choice depending on their respective circumstances? Or to waive the refund as someone suggested earlier.</div>
<div><br>
</div>
<div data-smartmail="gmail_signature"><br>
Justine<br>
---------</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, 13 Jun 2024, 16:48 Jeff Neuman, <<a href="mailto:jeff@jjnsolutions.com">jeff@jjnsolutions.com</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
Just to add to the notion of a "Credit" vs. "Refund". A significant number of applicants either withdraw their applications or be eliminated through contention, lack of success in the application process, advice, etc. A credit does no good for these applicants
because they will have nothing to credit against. </div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
I do not see a way around making this a refund as opposed to a credit.</div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div id="m_6711655957347727450Signature">
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<span><img style="max-width:429px" src="cid:c194eb95-d749-4172-93ed-9474feec59e1" data-unique-identifier=""></span></div>
</div>
<div id="m_6711655957347727450appendonsend"></div>
<hr style="display:inline-block;width:98%">
<div id="m_6711655957347727450divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> SubPro-IRT <<a href="mailto:subpro-irt-bounces@icann.org" target="_blank" rel="noreferrer">subpro-irt-bounces@icann.org</a>>
on behalf of Christa Taylor <<a href="mailto:Christa@tldz.com" target="_blank" rel="noreferrer">Christa@tldz.com</a>><br>
<b>Sent:</b> Thursday, June 13, 2024 12:35 AM<br>
<b>To:</b> Rubens Kuhl <<a href="mailto:rubensk@nic.br" target="_blank" rel="noreferrer">rubensk@nic.br</a>>; Next Round Policy Implementation <<a href="mailto:NextRound_PolicyImplementation@icann.org" target="_blank" rel="noreferrer">NextRound_PolicyImplementation@icann.org</a>>;
<a href="mailto:subpro-irt@icann.org" target="_blank" rel="noreferrer">subpro-irt@icann.org</a> <<a href="mailto:subpro-irt@icann.org" target="_blank" rel="noreferrer">subpro-irt@icann.org</a>><br>
<b>Subject:</b> Re: [SubPro-IRT] Application Fee FAQ</font>
<div> </div>
</div>
<div lang="EN-CA" link="blue" vlink="purple" style="word-wrap:break-word">
<div>
<p>Thank you Elisa and Lars,</p>
<p><span style="font-size:11.0pt"> </span></p>
<p>I apologize for not being able to attend due to time zone differences. </p>
<p> </p>
<p>I want to support the requests for more detailed costing information along with some concerns.</p>
<p> </p>
<p>In November 2016, Work Track 1 was tasked with evaluating the accuracy of cost estimates and reviewing the methodology used to develop the cost model. However, after months of requests, ICANN was unable to provide any information on the costs and methodology
used in the 2009 application fees. Consequently, we could not properly address the Implementation Guideline B regarding the concept of differing application fees for different applicants and the potential creation of new application types, which may have necessitated
a new costing analysis based on recommended changes (section 4.2.17 at <a href="https://urldefense.com/v3/__https://community.icann.org/download/attachments/58735931/Section*204.2.17.pdf?version=1&modificationDate=1460741334000&api=v2__;JQ!!DUT_TFPxUQ!CHBYFV8IeuKPCgkAVpqVASCDCaXFuAchjwSdiWHKD_eV9yCOTnJALBJ4vWkxn7zNwkt7rLCK8eDfsYKS0_V-ALPg$" target="_blank" rel="noreferrer">
https://community.icann.org/download/attachments/58735931/Section%204.2.17.pdf?version=1&modificationDate=1460741334000&api=v2</a> ).</p>
<p> </p>
<p>Since we were unable to attain the information, the working group wanted to ensure the scenario would not occur in the future rounds and emphasized the need for detailed and transparent disclosure of fees and methodologies to the community. The Final Report
reflects this:</p>
<ul type="disc" style="margin-top:0cm">
<li style="margin-left:0cm">Top 15: Application Fees: “<i>The development of the application fee must be fully transparent, with all cost assumptions explained and documented</i>” (p. 66).</li><li style="margin-left:0cm">Working Group Emphasis: <i>ICANN should be fully transparent about how the application fee is developed, explaining and documenting all cost assumptions (</i>p. 69).</li><li style="margin-left:0cm">Summary of Outputs: “<i>The development of the application fee must be fully transparent, with all cost assumptions explained and documented</i>” (p. 249).</li></ul>
<p> </p>
<p>Two additional points:</p>
<p> </p>
<p>1. Application Fees and Deterrence: I understand wanting to be conservative approach to ensure costs are recovered however, this should be based on probabilities not extreme cases as provided with the 500 and 1,000 volume levels. Also, the scenarios presented
suggest providing excess fees as a ‘credit’, but we recommended the option of a refund if the amount exceeded $1,000 (or another nominal amount) with a disbursement schedule based on milestones to avoid delays. This would ensure that applicants don't prepay
their yearly ICANN fees, for an extended period, during a critical time when those funds could be utilized to launch and support the operation of their TLD(s).</p>
<p> </p>
<p>2. The working group noted that only historical costs directly related to implementing the New gTLD Program should be part of the cost structure for determining application fees.
</p>
<p><i>“The Working Group believes, however, that for subsequent procedures the only historical costs that should be part of the cost structure in determining application fees are those actual costs directly related to the implementation of the New gTLD Program”.</i>
(p. 65). "Org Shared Services" do not align with this, as they are “<i>not directly attributable to a program or project</i>”. Additionally, it would be helpful to determine whether the $70k per application in implementation fees also includes past shared
services amounts and, if they do, the amount included within the $70k.</p>
<p> </p>
<p>Without relevant details and transparency on the costs, it becomes difficult to understand the full picture, hinders analysis, and prevents the attainment of useful insights that can be utilized in future rounds and in the development of future policies.</p>
<p> </p>
<p>Apologies for the length, it was supposed to be a short email! </p>
<p> </p>
<p><span style="font-size:11.0pt">Kind regards,</span></p>
<p><span style="font-size:11.0pt"> </span></p>
<p><span style="font-size:11.0pt">Christa</span></p>
<p><span style="font-size:11.0pt"> </span></p>
<div>
<div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> SubPro-IRT <<a href="mailto:subpro-irt-bounces@icann.org" target="_blank" rel="noreferrer">subpro-irt-bounces@icann.org</a>>
<b>On Behalf Of </b>Rubens Kuhl via SubPro-IRT<br>
<b>Sent:</b> Wednesday, June 12, 2024 8:00 PM<br>
<b>To:</b> Next Round Policy Implementation <<a href="mailto:NextRound_PolicyImplementation@icann.org" target="_blank" rel="noreferrer">NextRound_PolicyImplementation@icann.org</a>>;
<a href="mailto:subpro-irt@icann.org" target="_blank" rel="noreferrer">subpro-irt@icann.org</a><br>
<b>Subject:</b> Re: [SubPro-IRT] Application Fee FAQ</span></p>
</div>
</div>
<p> </p>
<p> </p>
<div>
<p><br>
<br>
</p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p>Em 12 de jun. de 2024, à(s) 09:01, Next Round Policy Implementation <<a href="mailto:NextRound_PolicyImplementation@icann.org" target="_blank" rel="noreferrer">NextRound_PolicyImplementation@icann.org</a>> escreveu:</p>
</div>
<p> </p>
<div>
<div>
<p><span style="font-size:11.0pt">Dear IRT members,<span> </span></span></p>
</div>
<div>
<p><span style="font-size:11.0pt"> </span></p>
</div>
<div>
<p><span style="font-size:11.0pt">In preparation for<span> </span><a href="https://urldefense.com/v3/__https://community.icann.org/x/zIBAEw__;!!DUT_TFPxUQ!CHBYFV8IeuKPCgkAVpqVASCDCaXFuAchjwSdiWHKD_eV9yCOTnJALBJ4vWkxn7zNwkt7rLCK8eDfsYKS0_Z_151V$" target="_blank" rel="noreferrer"><span style="color:#467886">tomorrow's
IRT meeting</span></a>, ICANN org has prepared the attached FAQ which aims to address the various questions that have been raised both in relation to the RSP fee as well as the gTLD evaluation fee</span><span lang="EN-GB" style="font-size:11.0pt">.</span><span style="font-size:11.0pt"></span></p>
</div>
<div>
<p><span lang="EN-GB" style="font-size:11.0pt"> </span><span style="font-size:11.0pt"></span></p>
</div>
<div>
<p><span lang="EN-GB" style="font-size:11.0pt">Best regards,</span><span style="font-size:11.0pt"></span></p>
</div>
<div>
<p><span lang="EN-GB" style="font-size:11.0pt">Elisa</span><span style="font-size:11.0pt"></span></p>
</div>
<div>
<p><span style="font-size:11.0pt"> </span></p>
</div>
<div>
<p><span lang="EN-GB" style="font-size:11.0pt"> </span><span style="font-size:11.0pt"></span></p>
</div>
</div>
</blockquote>
<p> </p>
</div>
<div>
<p>Some comments about the FAQ:</p>
</div>
<div>
<p> </p>
</div>
<div>
<p>- In the RSP fee, it lacks a comparison to the USD 14k required for an unknown RSP to be evaluated for serving 2012 gTLDs. </p>
</div>
<div>
<p>- It’s not mentioned whether applicants will be allowed to commit to use an evaluated RSP or can only choose already evaluated ones</p>
</div>
<div>
<p>- In item 3, it’s mentioned that TMCH fees are not included. In 2012, registries got their TMCH fees back after being initially charged, so in effect, there was no additional payment of TMCH fees beyond the application fee. Changing that is not supported
by any SubPro recommendation. </p>
</div>
<div>
<p>- As mentioned by Seb during the session, some organizations might have challenges receiving the excess funding. So while it’s good to be the default to return the excess, giving applicants the option to not get that excess back solves for corner cases regarding
tax or foreign exchange regulations. Applicants would only have to say they want it or not want it (no lingering). </p>
</div>
<div>
<p> </p>
</div>
<div>
<p> </p>
</div>
<div>
<p>About the fee for joint venture review, if joint venture ends up playing a role in auctions, perhaps auction proceeds should pay for those. </p>
</div>
<div>
<p> </p>
</div>
<div>
<p>About the fee for lingering applications, I support the idea. Currently there is an asymmetrical relationship between letting it linger (Cranberries song playing in the background) and the Org costs. The hard issue, though, is defining it, since there should
be no prevention of the use of accountability mechanisms or limited appeal processes created by that cost, but that can’t also trigger an excessive use of such mechanisms only to avoid the lingering fee. </p>
</div>
<div>
<p> </p>
</div>
<div>
<p>About the IDN Variant subsidy, agree with Edmon on changing its name, but I also add that this could be funded from fee leftovers (either from previous round or forecast of this round) or even Auctions leftovers. This would be aligned with guidelines to
such expenditures, I believe. While this won’t change the application fee by any significant amount either way (circa 1%), this would simplify the fee determination and also could back ICANN claims to support multilingual development of the Internet. </p>
</div>
<div>
<p> </p>
</div>
<div>
<p> </p>
</div>
<div>
<p>Rubens</p>
</div>
<div>
<p> </p>
</div>
<div>
<p> </p>
</div>
<div>
<p> </p>
</div>
</div>
</div>
</div>
_______________________________________________<br>
SubPro-IRT mailing list<br>
<a href="mailto:SubPro-IRT@icann.org" target="_blank" rel="noreferrer">SubPro-IRT@icann.org</a><br>
<a href="https://urldefense.com/v3/__https://mm.icann.org/mailman/listinfo/subpro-irt__;!!DUT_TFPxUQ!CHBYFV8IeuKPCgkAVpqVASCDCaXFuAchjwSdiWHKD_eV9yCOTnJALBJ4vWkxn7zNwkt7rLCK8eDfsYKS03J772pv$" rel="noreferrer noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/subpro-irt</a><br>
<br>
_______________________________________________<br>
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 (<a href="https://urldefense.com/v3/__https://www.icann.org/privacy/policy__;!!DUT_TFPxUQ!CHBYFV8IeuKPCgkAVpqVASCDCaXFuAchjwSdiWHKD_eV9yCOTnJALBJ4vWkxn7zNwkt7rLCK8eDfsYKS0_Cpg7eY$" rel="noreferrer noreferrer" target="_blank">https://www.icann.org/privacy/policy</a>)
and the website Terms of Service (<a href="https://urldefense.com/v3/__https://www.icann.org/privacy/tos__;!!DUT_TFPxUQ!CHBYFV8IeuKPCgkAVpqVASCDCaXFuAchjwSdiWHKD_eV9yCOTnJALBJ4vWkxn7zNwkt7rLCK8eDfsYKS0_BjC2KL$" rel="noreferrer noreferrer" target="_blank">https://www.icann.org/privacy/tos</a>).
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.</blockquote>
</div>
<pre class="blue"><hr><br>SubPro-IRT mailing list<br>SubPro-IRT@icann.org<br><a href="https://urldefense.com/v3/__https://mm.icann.org/mailman/listinfo/subpro-irt__;!!DUT_TFPxUQ!CHBYFV8IeuKPCgkAVpqVASCDCaXFuAchjwSdiWHKD_eV9yCOTnJALBJ4vWkxn7zNwkt7rLCK8eDfsYKS03J772pv$">https://mm.icann.org/mailman/listinfo/subpro-irt</a><br><br><hr><br>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 (<a href="https://urldefense.com/v3/__https://www.icann.org/privacy/policy__;!!DUT_TFPxUQ!CHBYFV8IeuKPCgkAVpqVASCDCaXFuAchjwSdiWHKD_eV9yCOTnJALBJ4vWkxn7zNwkt7rLCK8eDfsYKS0_Cpg7eY$">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://urldefense.com/v3/__https://www.icann.org/privacy/tos__;!!DUT_TFPxUQ!CHBYFV8IeuKPCgkAVpqVASCDCaXFuAchjwSdiWHKD_eV9yCOTnJALBJ4vWkxn7zNwkt7rLCK8eDfsYKS0_BjC2KL$">https://www.icann.org/privacy/tos</a>). 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.</pre>
</blockquote>
</div>
<span>_______________________________________________</span><br>
<span>SubPro-IRT mailing list</span><br>
<span>SubPro-IRT@icann.org</span><br>
<span>https://urldefense.com/v3/__https://mm.icann.org/mailman/listinfo/subpro-irt__;!!DUT_TFPxUQ!CHBYFV8IeuKPCgkAVpqVASCDCaXFuAchjwSdiWHKD_eV9yCOTnJALBJ4vWkxn7zNwkt7rLCK8eDfsYKS03J772pv$
</span><br>
<span></span><br>
<span>_______________________________________________</span><br>
<span>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://urldefense.com/v3/__https://www.icann.org/privacy/policy__;!!DUT_TFPxUQ!CHBYFV8IeuKPCgkAVpqVASCDCaXFuAchjwSdiWHKD_eV9yCOTnJALBJ4vWkxn7zNwkt7rLCK8eDfsYKS0_Cpg7eY$
) and the website Terms of Service (https://urldefense.com/v3/__https://www.icann.org/privacy/tos__;!!DUT_TFPxUQ!CHBYFV8IeuKPCgkAVpqVASCDCaXFuAchjwSdiWHKD_eV9yCOTnJALBJ4vWkxn7zNwkt7rLCK8eDfsYKS0_BjC2KL$ ). 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.</span></div>
</blockquote>
</div>
</div>
<HR>If you are not an intended recipient of confidential and privileged information in this email, please delete it, notify us immediately at postmaster@gtlaw.com, and do not use or disseminate the information.<BR>
</body>
</html>