<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><font face="Times New Roman, Times, serif" color="#800000">Colleagues,</font></p>
<p><font face="Times New Roman, Times, serif" color="#800000">Is
there a middle ground here? Not only can it take time to get a
government to respond, the longer the period between that
endorsement and the submission date, the greater the possibility
that the governmental context can change. The process also wants
to be protected from an early endorsement that is no longer
valid. Would the following work?</font></p>
<p><font face="Times New Roman, Times, serif" color="#800000">The
initial request (and negotiations) for endorsement would contain
a proviso that the agreement would be
re-initialed/signed/verified just prior to the submission of the
proposal. The applicant would be responsible for making sure
that the contact person/office and context were such that the
re-initial/sign/verify process would go smoothly at submission,
and the evaluation process would be secure in the knowledge that
the context had not changed, risking making the endorsement
questionable. Also, there would be no need for a specified time
frame. <br>
</font></p>
<p><font face="Times New Roman, Times, serif" color="#800000">Sam
Lanfranco, NCSG<br>
</font></p>
<div class="moz-cite-prefix">On 10/13/2023 9:14 AM, trachtenbergm---
via SubPro-IRT wrote:<br>
</div>
<blockquote type="cite"
cite="mid:53B41A27-D82B-47EE-9FE3-1F382D771644@gtlaw.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
I agree as well but think 6 months is too short. It can be
difficult to get a government entity to do anything and I think
signing this letter will be low on the priority list. If an
applicant is investing significant time and money in applying they
shouldn’t have to scramble at the last minute to get the letter
signed (or re-signed) and have everything be for naught if the
government entity drags its feet. I think 12 or 18 months prior is
more reasonable. <br>
<br>
<div dir="ltr">
<div><br>
</div>
<div>Best Regards,</div>
<b>
<div><b><br>
</b></div>
Marc H.Trachtenberg</b>
<div>
<div>Chair, Internet, Domain Name, eCommerce, and Social Media
Practice</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 Oct 13, 2023, at 6:48 AM, Annebeth
Lange via SubPro-IRT <a class="moz-txt-link-rfc2396E" href="mailto:subpro-irt@icann.org"><subpro-irt@icann.org></a> 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="ltr">I agree with Alexander and Justine. It would be
a good idea to set a time line to avoid problems.</div>
<div dir="ltr"><br>
</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">Best regards </div>
<div dir="ltr">Annebeth </div>
<div dir="ltr"><br>
<blockquote type="cite">13. okt. 2023 kl. 12:35 skrev
Justine Chew <a class="moz-txt-link-rfc2396E" href="mailto:justine.chew.icann@gmail.com"><justine.chew.icann@gmail.com></a>:<br>
<br>
</blockquote>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">Thank you for bringing this up,
Alexander. <br>
<br>
I think what you alluded to is very relevant, and in
my personal capacity, I would urge Lars, Michael K.
and their colleagues to consider propagating some
language on this in the same way they proposed to
address the issue brought up by Susan regarding what
"a limited time frame to provide the documentation"
under para 2.4 could mean (noting also Ruben's remark
about Extended Evaluation).<br clear="all">
<div>
<div dir="ltr" class="gmail_signature">
<div dir="ltr"><br>
<font color="#000000">Kind regards,</font><br>
<font color="#000000">Justine</font><br>
<b><br>
</b></div>
</div>
</div>
<br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Fri, 13 Oct 2023
at 17:50, <a class="moz-txt-link-rfc2396E" href="mailto:alexander@schubert.berlin"><alexander@schubert.berlin></a> wrote:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div class="msg-3544156446432335871">
<div style="overflow-wrap: break-word;"
lang="EN-US">
<div class="m_-3544156446432335871WordSection1">
<p class="MsoNormal">Hi members,</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">I guess few of us have
ever dealt with the real-life issues of
obtaining “government support” for a geo
gTLD. I have: both in the last round, and
right now for the 2<sup>nd</sup> round. And
I urge us to remember one of the glaring
issues that actually created quite a
commotion in the 1<sup>st</sup> round:<br>
<br>
The total absence of any timeline for such
letter. In the last round one applicant had
government support that was literally ‘years
old’ – and allegedly even subsequently
withdrawn: .africa. Remember what hassle
that caused?<br>
<br>
So, I recommend introducing a simple
shelf-life requirement for the support
letter. It is of course laudable when such
support letter has been acquired years
before the application submission. But even
IF an applicant acquired such expression of
support very early out – would it be an
unbearable task for them to kindly ask the
applicable entity to re-sign the letter?
Because sometimes the responsible entity
changes (e.g., a new major in a city) and
shouldn’t they have a say, too? Or they
changed their mind – e.g., after having been
approached by a more suitable applicant. I
think the signature under the support letter
shouldn’t be older than e.g., 6 months
before the application submission. The exact
amount of time would of course be subject to
discussion. But I assume we could save
ourselves quite some troubles if we require
to either sign (or re-sign an already
signed) letter X months before the actual
application submission.<br>
<br>
I also urge to have the deadline requirement
stipulated in the letter itself: so that the
relevant Government entity is aware that
they will have to resign the letter later!
Something along the lines: “The signee is
aware that ICANN will require that this
letter of support (non-objection) has to be
authorized (or re-authorized) within 6
months to the actual application
submission.”<br>
<br>
Has the example support letter draft been
finalized already? Is the draft publicly
available for review?<br>
<br>
</p>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal"><span>Thanks,</span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span lang="DE">Alexander
</span></p>
<p class="MsoNormal"><span lang="DE">___________________________________</span></p>
<p class="MsoNormal"><span lang="DE">Alexander
Schubert</span></p>
<p class="MsoNormal"><span lang="DE"><a
href="https://urldefense.com/v3/__http://LinkedIn.com/in/alexanderschubert__;!!DUT_TFPxUQ!HZjzdcrlRTVfhwyGdwckC63DQ-xayhwPPVqJWZJhtXxtZSLd67kxakHnmedTHTiOu8qb7NG6LqCmOPQsreXQ4N4$"
moz-do-not-send="true">LinkedIn.com/in/alexanderschubert</a></span></p>
<p class="MsoNormal"><span>+1(202)684-6806</span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span> </span></p>
</div>
<p class="MsoNormal"> </p>
<div>
<div
style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0cm 0cm">
<p class="MsoNormal"><b><span>From:</span></b><span>
SubPro-IRT <<a
href="mailto:subpro-irt-bounces@icann.org" target="_blank"
moz-do-not-send="true"
class="moz-txt-link-freetext">subpro-irt-bounces@icann.org</a>>
<b>On Behalf Of </b>Michael Karakash<br>
<b>Sent:</b> Thursday, October 12,
2023 9:51 PM<br>
<b>To:</b> <a
href="mailto:subpro-irt@icann.org"
target="_blank"
moz-do-not-send="true"
class="moz-txt-link-freetext">subpro-irt@icann.org</a><br>
<b>Subject:</b> [SubPro-IRT] Topic
21.1: Geographic Names - Updated</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span style="color:black">Dear
IRT Members,</span></p>
<p class="MsoNormal"
style="font-variant-caps:normal;text-align:start;word-spacing:0px">
<span style="color:black"> </span></p>
<p class="MsoNormal"
style="font-variant-caps:normal;text-align:start;word-spacing:0px">
We’ve updated the <a
href="https://urldefense.com/v3/__https://docs.google.com/document/d/1N1iLzfPp4IeTuTyO46T7WSjww7kpe_fzJIVOaSQ5qwI/edit?usp=sharing__;!!DUT_TFPxUQ!HZjzdcrlRTVfhwyGdwckC63DQ-xayhwPPVqJWZJhtXxtZSLd67kxakHnmedTHTiOu8qb7NG6LqCmOPQseibaGJw$"
target="_blank" moz-do-not-send="true">
Geographic Names AGB section</a> based on
the discussions held on the 3 October IRT
call. As noted during that session, we will
not be having another dedicated call on this
topic but can continue to discuss this
on-list if there are any comments or
concerns.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">As a reminder, past
agenda items and video/audio recordings from
the previous session can be found on the
<a
href="https://urldefense.com/v3/__https://community.icann.org/pages/viewpage.action?pageId=273449325__;!!DUT_TFPxUQ!HZjzdcrlRTVfhwyGdwckC63DQ-xayhwPPVqJWZJhtXxtZSLd67kxakHnmedTHTiOu8qb7NG6LqCmOPQsGORs-tg$"
target="_blank" moz-do-not-send="true">
IRT Community Wiki.</a></p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Thank you!</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Best,</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Michael</p>
</div>
</div>
_______________________________________________<br>
SubPro-IRT mailing list<br>
<a href="mailto:SubPro-IRT@icann.org"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">SubPro-IRT@icann.org</a><br>
<a
href="https://urldefense.com/v3/__https://mm.icann.org/mailman/listinfo/subpro-irt__;!!DUT_TFPxUQ!HZjzdcrlRTVfhwyGdwckC63DQ-xayhwPPVqJWZJhtXxtZSLd67kxakHnmedTHTiOu8qb7NG6LqCmOPQseRS4M58$"
rel="noreferrer" target="_blank"
moz-do-not-send="true">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!HZjzdcrlRTVfhwyGdwckC63DQ-xayhwPPVqJWZJhtXxtZSLd67kxakHnmedTHTiOu8qb7NG6LqCmOPQsiWAS0WA$"
rel="noreferrer" target="_blank"
moz-do-not-send="true">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!HZjzdcrlRTVfhwyGdwckC63DQ-xayhwPPVqJWZJhtXxtZSLd67kxakHnmedTHTiOu8qb7NG6LqCmOPQs8QzHoZA$"
rel="noreferrer" target="_blank"
moz-do-not-send="true">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.</div>
</blockquote>
</div>
</div>
<span>_______________________________________________</span><br>
<span>SubPro-IRT mailing list</span><br>
<span><a class="moz-txt-link-abbreviated" href="mailto:SubPro-IRT@icann.org">SubPro-IRT@icann.org</a></span><br>
<span><a
href="https://urldefense.com/v3/__https://mm.icann.org/mailman/listinfo/subpro-irt__;!!DUT_TFPxUQ!HZjzdcrlRTVfhwyGdwckC63DQ-xayhwPPVqJWZJhtXxtZSLd67kxakHnmedTHTiOu8qb7NG6LqCmOPQseRS4M58$"
moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/subpro-irt</a></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 (<a
href="https://urldefense.com/v3/__https://www.icann.org/privacy/policy__;!!DUT_TFPxUQ!HZjzdcrlRTVfhwyGdwckC63DQ-xayhwPPVqJWZJhtXxtZSLd67kxakHnmedTHTiOu8qb7NG6LqCmOPQsiWAS0WA$"
moz-do-not-send="true">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!HZjzdcrlRTVfhwyGdwckC63DQ-xayhwPPVqJWZJhtXxtZSLd67kxakHnmedTHTiOu8qb7NG6LqCmOPQs8QzHoZA$"
moz-do-not-send="true">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.</span></div>
</blockquote>
<span>_______________________________________________</span><br>
<span>SubPro-IRT mailing list</span><br>
<span><a class="moz-txt-link-abbreviated" href="mailto:SubPro-IRT@icann.org">SubPro-IRT@icann.org</a></span><br>
<span><a class="moz-txt-link-freetext" href="https://urldefense.com/v3/__https://mm.icann.org/mailman/listinfo/subpro-irt__;!!DUT_TFPxUQ!HZjzdcrlRTVfhwyGdwckC63DQ-xayhwPPVqJWZJhtXxtZSLd67kxakHnmedTHTiOu8qb7NG6LqCmOPQseRS4M58$">https://urldefense.com/v3/__https://mm.icann.org/mailman/listinfo/subpro-irt__;!!DUT_TFPxUQ!HZjzdcrlRTVfhwyGdwckC63DQ-xayhwPPVqJWZJhtXxtZSLd67kxakHnmedTHTiOu8qb7NG6LqCmOPQseRS4M58$</a>
</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
(<a class="moz-txt-link-freetext" href="https://urldefense.com/v3/__https://www.icann.org/privacy/policy__;!!DUT_TFPxUQ!HZjzdcrlRTVfhwyGdwckC63DQ-xayhwPPVqJWZJhtXxtZSLd67kxakHnmedTHTiOu8qb7NG6LqCmOPQsiWAS0WA$">https://urldefense.com/v3/__https://www.icann.org/privacy/policy__;!!DUT_TFPxUQ!HZjzdcrlRTVfhwyGdwckC63DQ-xayhwPPVqJWZJhtXxtZSLd67kxakHnmedTHTiOu8qb7NG6LqCmOPQsiWAS0WA$</a>
) and the website Terms of Service
(<a class="moz-txt-link-freetext" href="https://urldefense.com/v3/__https://www.icann.org/privacy/tos__;!!DUT_TFPxUQ!HZjzdcrlRTVfhwyGdwckC63DQ-xayhwPPVqJWZJhtXxtZSLd67kxakHnmedTHTiOu8qb7NG6LqCmOPQs8QzHoZA$">https://urldefense.com/v3/__https://www.icann.org/privacy/tos__;!!DUT_TFPxUQ!HZjzdcrlRTVfhwyGdwckC63DQ-xayhwPPVqJWZJhtXxtZSLd67kxakHnmedTHTiOu8qb7NG6LqCmOPQs8QzHoZA$</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.</span></div>
</blockquote>
<hr>If you are not an intended recipient of confidential and
privileged information in this email, please delete it, notify us
immediately at <a class="moz-txt-link-abbreviated" href="mailto:postmaster@gtlaw.com">postmaster@gtlaw.com</a>, and do not use or disseminate
the information.<br>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
SubPro-IRT mailing list
<a class="moz-txt-link-abbreviated" href="mailto:SubPro-IRT@icann.org">SubPro-IRT@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/subpro-irt">https://mm.icann.org/mailman/listinfo/subpro-irt</a>
_______________________________________________
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 class="moz-txt-link-freetext" href="https://www.icann.org/privacy/policy">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a class="moz-txt-link-freetext" href="https://www.icann.org/privacy/tos">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>
<pre class="moz-signature" cols="72">--
Sam Lanfranco, Prof Emeritus, York University, Internet Ecologist & Farmer;
Web23.io; AshPiedmont Farm, South Bay, Prince Edward County, Ontario, Canada
P:613-476-0429 C:416-816-2852 E: <a class="moz-txt-link-abbreviated" href="mailto:samlanfranco@gmail.com">samlanfranco@gmail.com</a> <a class="moz-txt-link-abbreviated" href="mailto:Lanfran@yorku.ca">Lanfran@yorku.ca</a></pre>
</body>
</html>