<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.m4058719395660026649gmail-msolistparagraph, li.m4058719395660026649gmail-msolistparagraph, div.m4058719395660026649gmail-msolistparagraph
{mso-style-name:m_4058719395660026649gmail-msolistparagraph;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.m4058719395660026649gmail-msohyperlink
{mso-style-name:m_4058719395660026649gmail-msohyperlink;}
span.E-MailFormatvorlage20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="DE-CH" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Dear Joe<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">First of all thanks very much for your valuable inputs.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">As you may have seen in the debates there are different views on the letter of non-objection. Some of us view it as a
valuable tool that, according to the facts at hand, worked very well for many people involved. The few cases where the letter of non-objection applied and problems arose would still need to be analyzed in order to work out fixes to address the potential issues…
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Part of this view is that the letter of non-objection is a requirement, not a right, which is open to any interested applicant
to comply with, be it a brand, a business, a community etc. And that the non-objection requirement allows for an early interaction of applicants with public authorities, which have rights, interests and responsibilities on what are regarded as identity signifiers
of their communities, avoiding costly conflicts at later stages of the process.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Looking forward to fruitful discussions here in Panama<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Jorge <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="DE" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Von:</span></b><span lang="DE" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Gnso-newgtld-wg-wt5 [mailto:gnso-newgtld-wg-wt5-bounces@icann.org]
<b>Im Auftrag von </b>Joe Alagna<br>
<b>Gesendet:</b> Sonntag, 24. Juni 2018 05:35<br>
<b>An:</b> Greg Shatan <gregshatanipc@gmail.com><br>
<b>Cc:</b> gnso-newgtld-wg-wt5@icann.org Work Track 5 <gnso-newgtld-wg-wt5@icann.org><br>
<b>Betreff:</b> Re: [Gnso-newgtld-wg-wt5] New gTLD Subsequent Procedures PDP: Work Track 5 Comments<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hi Greg,<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I would defer to your understanding of those things over mine. I appreciate you clarifying the differences. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I read that guidebook over and over through every iteration from the first version to the final one in 2012. I even created and updated an index for it which never existed. But I’ve not gone to law school. :-). <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Thanks,<o:p></o:p></p>
<div id="AppleMailSignature">
<p class="MsoNormal">- <o:p></o:p></p>
<div>
<div>
<p class="MsoNormal">Joe | <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">+1 (951) 313-7200 <span style="font-size:13.0pt">| </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:13.0pt"><br>
<br>
</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:13.0pt">Sent from (or dictated to) my iPhone; please excuse brevity & any typo/punc/cap errors. | </span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
On Jun 23, 2018, at 5:29 PM, Greg Shatan <<a href="mailto:gregshatanipc@gmail.com">gregshatanipc@gmail.com</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<div>
<p class="MsoNormal">Joe,<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thanks for weighing. I agree with a great deal of what you say. On your first point, I and a number of others have addressed the rights and concerns regarding trademark rights, the rights of businesses and individuals who are brandowners,
and the rights of consumers and other end-users; who rely on trademarks as signifiers of origin, quality and unique characteristics of the underlying businesses, products, goods and services. I’ve been consumed by other matters the last couple of weeks and
I haven’t been as active on the list as I would like, but I’ll rectify that.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I share your concerns about the idea that we could create hierarchies or preferences that would elevate one type of legitimate rights over another, whether it is between two applicants or between an applicant and a non-applicant.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">However, you group letters of non-objection/consent with curative rights, and state a preference for these over preventive rights. I would submit that letters of non-objection/consent ARE preventive rights and must be categorized as such.
They certainly fit the criteria: they stand in the way of an application or potential application, they require permission to be granted before the applicant can proceed, and the failure to grant (or decision not to grant) the consent/non-objection prevents
the applicant from moving forward. They also grant automatic preventive powers to ALL geonames (unless narrowed by this group), such that an applicant might have to get dozens of letters before they can move forward. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Requiring applicants to run a gantlet of governmental bodies who have been granted not only a right merely for existing but a remedy that is already invoked unless they actively move out of the way is distressing, inconsistent with larger
legal principles, inconsistent with permissionless innovation, and creates a hierarchy without basis in fact or law.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Curative rights, on the other hand, don’t have any effect until they are invoked by a challenger, and each challenger only represents their own interests. When invoked, there is no presumption in favor of the challenger. The rights of
the challenger vs. the applicant are evaluated on a case-by-case basis.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I share your preference for curative methods. However, there’s no basis for grouping letters of non-objection with curative rights when they function as preventive rights.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Greg<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal">On Sat, Jun 23, 2018 at 6:39 AM Annebeth Lange <<a href="mailto:annebeth.lange@norid.no">annebeth.lange@norid.no</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<p class="MsoNormal">Hi Joe <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thanks for your thoughtful comments. As I told you when you introduced them during my presentation at the LacTLD workshop yesterday, I think it is important that all view are put on the table. I do hope that you - and as many as possible
- will participate in the special sessions where WT5 issues will be discussed, including the cross community workshop on geonames.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Kindly<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Annebeth<o:p></o:p></p>
<div id="m_4058719395660026649AppleMailSignature">
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Annebeth B Lange<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Special Adviser International Policy<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">UNINETT Norid AS<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Phone: +47 959 11 559<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Mail: <a href="mailto:annebeth.lange@norid.no" target="_blank">
annebeth.lange@norid.no</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
22. jun. 2018 kl. 13:12 skrev Joe Alagna <<a href="mailto:jalagna@afilias.info" target="_blank">jalagna@afilias.info</a>>:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;line-height:115%">
<span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif;color:#0B5394">Hi All,<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;line-height:115%">
<span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif;color:#0B5394"><o:p> </o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;line-height:115%">
<span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif;color:#0B5394">Although, because of time obligations, I have not commented, I have been an observer of this track since the beginning and recently converted to member so I could
make a comment. <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;line-height:115%">
<span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif;color:#0B5394"><o:p> </o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;line-height:115%">
<span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif;color:#0B5394">I would like to pose several questions and considerations. Please accept my apologies if some of my comments have already been discussed since I have been unable
to join the telephonic discussions. I have perused the ongoing document you are developing within the limits of my time.
<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;line-height:115%">
<span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif;color:#0B5394"><o:p> </o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;line-height:115%">
<span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif;color:#0B5394">These questions and considerations are meant in the spirit of contributing and stimulating discussion, not necessarily advocating a position. The work you are doing
is important. Please note that these are my own observations and comments, not necessarily reflective of the company I work for:<o:p></o:p></span></p>
<p class="m4058719395660026649gmail-msolistparagraph" style="margin-bottom:12.0pt;line-height:115%">
<span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif;color:#0B5394">1.</span><span style="font-size:7.0pt;line-height:115%;color:#0B5394">
</span><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif;color:#0B5394">Some members are advocating to reserve city and territory names as rights or even as owned by the cities or territories. I’ve always understood city and territory
names as tools to be used by the public for geographic purposes. In fact, unless I missed it (I may have), the discussions seem to have only mildly addressed the thousands of business names around the world that are trademarked, that already contain geographic
names, cities and territories. You can look at any database of trademarks from any jurisdiction around the world and likely find hundreds of existing trademarks that contain geographic strings. Strings like this are highly important as parts of business
names, identifying the locations of service areas for example. These include names like Swiss Air and American Telephone and Telegraph. I use that second example to show how long-standing this tradition is. This fact seems unacknowledged so far in our discussions.
I fear that we are ignoring a hundred years + of tradition and precedence. It may be an important exercise to see how many trademarks already exist in various places that contain geo-type strings.<br>
<br>
The history of registries suggests that they may either be public or private, so it seems that the principal of neutrality is important when considering the type of entity applying for a string.<o:p></o:p></span></p>
<p class="m4058719395660026649gmail-msolistparagraph" style="margin-bottom:12.0pt;line-height:115%">
<span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif;color:#0B5394">2.</span><span style="font-size:7.0pt;line-height:115%;color:#0B5394">
</span><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif;color:#0B5394">There is a theme of debate about who gets preference regarding geographic indicators in new strings, government entities or private entities. My experience,
at least in the United States is that many government entities do not care about their geographic names (and for that matter, their email addresses). They seem to be perfectly happy using what I would consider seriously outdated URLs and email addresses.
<br>
<br>
These government entities already have the right to use a .gov (or a .edu) domain name and email address, a right that any private citizen or public company does not have. Yet they prefer not to use them.
<br>
<br>
The example I have in mind is the several thousand public schools across the United States who prefer to continue using long URLS and email addresses in the .edu or .us space. A very typical teacher or administrative email address looks like this:<br>
<br>
</span><span class="m4058719395660026649gmail-msohyperlink"><b><u><span style="font-family:"Calibri",sans-serif;color:#0563C1"><a href="mailto:MyKidTeachersFirstName.LastName@LaUnifiedSchoolDistrict.k12.ca.us" target="_blank"><span style="color:#0563C1">MyKidTeachersFirstName.LastName@LaUnifiedSchoolDistrict.k12.ca.us</span></a></span></u></b></span><b><span style="font-family:"Calibri",sans-serif;color:#0B5394"><br>
</span></b><span style="font-family:"Calibri",sans-serif;color:#0B5394"><br>
</span><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif;color:#0B5394">They don’t seem to want to change this. Wouldn’t it be better and more convenient for them to use something like:<br>
<br>
</span><span class="m4058719395660026649gmail-msohyperlink"><b><u><span style="font-family:"Calibri",sans-serif;color:#0563C1"><a href="mailto:MyKidsTeachersName@LAUnified.gov" target="_blank"><span style="color:#0563C1">MyKidsTeachersName@LAUnified.gov</span></a></span></u></b></span><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif;color:#0B5394">
(or .edu) anything less than a fourth level domain name? So…<o:p></o:p></span></p>
<p class="m4058719395660026649gmail-msolistparagraph" style="line-height:115%"><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif;color:#0B5394">3.</span><span style="font-size:7.0pt;line-height:115%;color:#0B5394">
</span><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif;color:#0B5394">Should not ICANN remain completely unbiased as to who gets the ability to apply for specific strings related to names in the DNS?
<o:p></o:p></span></p>
<p class="m4058719395660026649gmail-msolistparagraph" style="line-height:115%"><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif;color:#0B5394">a.</span><span style="font-size:7.0pt;line-height:115%;color:#0B5394">
</span><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif;color:#0B5394">Since many government, city, and territorial entities are not engaged nor involved in this process,
<o:p></o:p></span></p>
<p class="m4058719395660026649gmail-msolistparagraph" style="line-height:115%"><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif;color:#0B5394">b.</span><span style="font-size:7.0pt;line-height:115%;color:#0B5394">
</span><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif;color:#0B5394">Since both private and public entities can be good or evil, and
<o:p></o:p></span></p>
<p class="m4058719395660026649gmail-msolistparagraph" style="line-height:115%"><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif;color:#0B5394">c.</span><span style="font-size:7.0pt;line-height:115%;color:#0B5394">
</span><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif;color:#0B5394">Since ICANN has a charter of a bottom up, community driven, process, not the creation of laws or rights
<br>
<br>
Why should ICANN, in any way confer a preference to either type of entity? In fact, some in this discussion seem to be suggesting an assumed “ownership” of TLD strings, a right that I think can only be conferred on a hyper local level by the proper legal entities,
certainly not ICANN, therefore, <o:p></o:p></span></p>
<p class="m4058719395660026649gmail-msolistparagraph" style="line-height:115%"><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif;color:#0B5394">4.</span><span style="font-size:7.0pt;line-height:115%;color:#0B5394">
</span><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif;color:#0B5394">Shouldn’t we be careful not to try to confer preferences or “rights” at all? In fact, shouldn’t we not even try that? It seems that we do not, and probably
should not have that power.<o:p></o:p></span></p>
<p class="m4058719395660026649gmail-msolistparagraph" style="line-height:115%"><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif;color:#0B5394">5.</span><span style="font-size:7.0pt;line-height:115%;color:#0B5394">
</span><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif;color:#0B5394">There has been discussion that any applicant should comply with local laws in areas, cities, or territories where a string name where they would like to do
work is relevant. <i>I would agree with that general principal</i> since it respects local laws, makes sense, and doesn’t try to rule the world.<o:p></o:p></span></p>
<p class="m4058719395660026649gmail-msolistparagraph" style="line-height:115%"><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif;color:#0B5394">6.</span><span style="font-size:7.0pt;line-height:115%;color:#0B5394">
</span><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif;color:#0B5394">Shouldn’t we
<u>not</u> assume that every government entity around the world cares about what we are doing here. In fact, I am sure that most don’t care – at least as much as we do. If they did care, they would be involved.
<br>
<br>
We know that TLDs are important and we should care about and anticipate how geographic names affect cities and territories around the world. We should also care about how a country, city, or territory’s rights will affect any applicant in the future. But we
should not show a preference in our policy, therefore, four suggestions:<o:p></o:p></span></p>
<p class="m4058719395660026649gmail-msolistparagraph" style="line-height:115%"><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif;color:#0B5394">a.</span><span style="font-size:7.0pt;line-height:115%;color:#0B5394">
</span><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif;color:#0B5394">A general preference for non-objection from geo-entities and curative solutions in policy over preventive solutions for potential geographic strings; not assuming
preferences that more often than not, don't exist <o:p></o:p></span></p>
<p class="m4058719395660026649gmail-msolistparagraph" style="line-height:115%"><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif;color:#0B5394">b.</span><span style="font-size:7.0pt;line-height:115%;color:#0B5394">
</span><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif;color:#0B5394">A more conservative approach to our scope in terms of the places we define<o:p></o:p></span></p>
<p class="m4058719395660026649gmail-msolistparagraph" style="line-height:115%"><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif;color:#0B5394">c.</span><span style="font-size:7.0pt;line-height:115%;color:#0B5394">
</span><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif;color:#0B5394">Recognizing that our contracts are time limited – We should recognize that our contracts are for a specified period, at the end of which, a government entity
may have the option of becoming engaged and maybe add something to the contract that specifies this rather than an assumption of renewal for applicants. This would allow for worthwhile private investment (maybe a five or ten-year period) and allow review
by any public entity after a period of time, to become involved if they then care to.<o:p></o:p></span></p>
<p class="m4058719395660026649gmail-msolistparagraph" style="line-height:115%"><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif;color:#0B5394">d.</span><span style="font-size:7.0pt;line-height:115%;color:#0B5394">
</span><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif;color:#0B5394">There should be no limits on how many applications may be filed on behalf of a single entity (private, corporate, or government). If we do this, here also,
we limit the capital involved in the process and we limit the chances for success of applicants and of this program in general.<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;line-height:115%">
<span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif;color:#0B5394">Finally, thank you to all of you, on all sides, for your discussion and participation. I believe this discussion is an important one and I know the sacrifice you
are making in terms of your time. I only wish I was able to contribute near as much time as all of you have. Thank you!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#0B5394"><br clear="all">
<o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p><span style="font-size:10.0pt;color:#1F497D">Joe Alagna </span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
<div>
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><worktrack5-alagna.pdf><o:p></o:p></p>
</div>
</blockquote>
</div>
</div>
<div>
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">_______________________________________________<br>
Gnso-newgtld-wg-wt5 mailing list<br>
<a href="mailto:Gnso-newgtld-wg-wt5@icann.org" target="_blank">Gnso-newgtld-wg-wt5@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5</a><o:p></o:p></p>
</div>
</blockquote>
</div>
</div>
<p class="MsoNormal">_______________________________________________<br>
Gnso-newgtld-wg-wt5 mailing list<br>
<a href="mailto:Gnso-newgtld-wg-wt5@icann.org" target="_blank">Gnso-newgtld-wg-wt5@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5</a><o:p></o:p></p>
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</body>
</html>