<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><br><div>Nick,</div><div><br></div><div>Did not know or remember that interesting fact about Scotland (GB-SCT) under 3166-2. Seeing <a href="https://en.m.wikipedia.org/wiki/ISO_3166-2">https://en.m.wikipedia.org/wiki/ISO_3166-2</a> which reports that ISO-2 list, I just realized that it indirectly differentiates between independent countries and non-sovereign territories that possess 3166-1 country codes: those with subdivisions are independent countries and those without are not. Thanks a lot!</div><div><br><div>Javier Rúa-Jovet</div><div id="AppleMailSignature">ALAC<br><div><br></div><div><div><span style="background-color: rgba(255, 255, 255, 0);">+1-787-396-6511</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">twitter: @javrua</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">skype: javier.rua1</span></div><div><font color="#000000" style="background-color: rgba(255, 255, 255, 0);"><a href="https://www.linkedin.com/in/javrua" style="background-color: rgba(255, 255, 255, 0);">https://www.linkedin.com/in/javrua</a> </font></div><div><br></div></div></div><div><br>On Jan 11, 2018, at 7:20 AM, Nick Wenban-Smith <<a href="mailto:Nick.Wenban-Smith@nominet.uk">Nick.Wenban-Smith@nominet.uk</a>> wrote:<br><br></div><blockquote type="cite"><div>
<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:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@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;}
@font-face
{font-family:BookAntiqua;
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:CenturyGothic;
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:ArialMT;
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:ArialNarrow;
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-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.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.apple-tab-span
{mso-style-name:apple-tab-span;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1234001026;
mso-list-template-ids:2037780762;}
@list l1
{mso-list-id:1506358848;
mso-list-template-ids:4883654;}
@list l1:level1
{mso-level-number-format:roman-lower;
mso-level-tab-stop:36.0pt;
mso-level-number-position:right;
text-indent:-18.0pt;}
@list l1:level2
{mso-level-number-format:roman-lower;
mso-level-tab-stop:72.0pt;
mso-level-number-position:right;
text-indent:-18.0pt;}
@list l1:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:108.0pt;
mso-level-number-position:right;
text-indent:-18.0pt;}
@list l1:level4
{mso-level-number-format:roman-lower;
mso-level-tab-stop:144.0pt;
mso-level-number-position:right;
text-indent:-18.0pt;}
@list l1:level5
{mso-level-number-format:roman-lower;
mso-level-tab-stop:180.0pt;
mso-level-number-position:right;
text-indent:-18.0pt;}
@list l1:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:216.0pt;
mso-level-number-position:right;
text-indent:-18.0pt;}
@list l1:level7
{mso-level-number-format:roman-lower;
mso-level-tab-stop:252.0pt;
mso-level-number-position:right;
text-indent:-18.0pt;}
@list l1:level8
{mso-level-number-format:roman-lower;
mso-level-tab-stop:288.0pt;
mso-level-number-position:right;
text-indent:-18.0pt;}
@list l1:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:324.0pt;
mso-level-number-position:right;
text-indent:-18.0pt;}
@list l2
{mso-list-id:1681859453;
mso-list-template-ids:1805915352;}
@list l2:level1
{mso-level-start-at:3;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></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]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">This is an interesting discussion, but I am getting confused now!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">I had thought that the first piece of work for WT5 is a discussion of the definition of what constitutes a geographic name for the purposes of new gTLDs – hence looking initially at the 2012 Applicant
Guidebook collectively to see whether those are fit for purpose. The use of 3166 – the standard for codes for the representation of countries and their subdivisions – is not perfect but has historically always been used as reference going right back to RFC
1591 in 1994 “IANA is not in the business of deciding what is and what is not a country”.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Personally while I think use of 3166 produces some odd results I have not (yet) heard of a credible alternative as regards country names and the 2 and 3 letter codes which represent country names.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">If the definition of a geographic term is going to be extended beyond the 3166 standard – to include rivers and mountains etc or even the currency codes as Christopher suggests then that is a whole
new discussion which analysis of the 2012 round will not help much with since those sorts of terms were not defined as geo names per those rules.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">I think we will be a bit better informed once we have seen the range of feedback on the existing rules as helpfully listed by Martin below.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Best wishes<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Nick <o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">PS Christopher whilst Scotland does not have its own 3166-1 codes, it is recognised and protected as a geographic term as a country subdivision of the UK on the 3166-2 list with the code GB-SCT and
the hypothetical use of the name ‘Scotland’ as a new generic TLD would require suitable governmental approval / non-objection under 2.2.1.4.2 (3)
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="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="EN-US">From:</span></b><span lang="EN-US"> Gnso-newgtld-wg-wt5 [<a href="mailto:gnso-newgtld-wg-wt5-bounces@icann.org">mailto:gnso-newgtld-wg-wt5-bounces@icann.org</a>]
<b>On Behalf Of </b><a href="mailto:lists@christopherwilkinson.eu">lists@christopherwilkinson.eu</a><br>
<b>Sent:</b> 10 January 2018 19:09<br>
<b>To:</b> Liz Williams <<a href="mailto:liz.williams@auda.org.au">liz.williams@auda.org.au</a>>; Martin Sutton <<a href="mailto:martin@brandregistrygroup.org">martin@brandregistrygroup.org</a>><br>
<b>Cc:</b> <a href="mailto:gnso-newgtld-wg-wt5@icann.org">gnso-newgtld-wg-wt5@icann.org</a><br>
<b>Subject:</b> Re: [Gnso-newgtld-wg-wt5] Action for WT5 Members - Definition of Geographic Terms<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Dear Liz, Dear Martin:<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">A few comments meanwhile:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">1.<span class="apple-tab-span"> </span>ISO 3166 is very useful as far as it goes, but it has its own intrinsic biases and lacunae.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span class="apple-tab-span"> </span>For instance, ISO 3166 privileges entities that are islands (‘territories’) whereas very many, more important, geographical regions are not recognised.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span class="apple-tab-span"> </span>To take a local example: The Isle of Man has its own 3166 code, but the whole of Scotland does not!<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">2.<span class="apple-tab-span"> </span>I think that we should make it quite clear that whatever the final definition of Geo-Names becomes, those Geographical terms that are not included are excluded from Delegation.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span class="apple-tab-span"> </span>Also, personally, I have not taken on board the idea that if there is no agreement on a new definition, it is the 2012 AGB that prevails. I think that is politically unrealistic. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <span class="apple-tab-span"> </span>If there is no agreement on a new definition, I would rather expect the whole new round to be deferred until we do.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">3.<span class="apple-tab-span"> </span>I strongly support Liz’ proposal to analyse the outcome of the 2012 round for Geo-Names. In the past 24 hours staff have released a lot of new data that I had not seen before. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <span class="apple-tab-span"> </span>I may revert to that matter when I have had time to review what we have now got. Martin has already requested that all that information be posted to the WT5 wiki. Thankyou.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Regards<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">CW<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>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">On 9 Jan 2018, at 19:24, Liz Williams <<a href="mailto:liz.williams@auda.org.au">liz.williams@auda.org.au</a>> wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">Hello Martin <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thanks for giving the WT5 members the chance to start re-thinking about definitions of geographic terms to be used as policy elements of any potential update to an Applicant Guidebook. One thing that concerns me is the ever expanding notions
around what geographic terms may be as they relate to top level domains. This is not a catch all exercise of prohibition. We must be able to ground any review of the current definitions and then any amendments to those definitions in external and objective
lists of names or rules around the use of geographic terms which is “steady state” and not subject to arbitrary interpretation and capricious change. That is why, for example, the use of ISO3166 lists are so helpful. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">And then I wanted to make another suggestion about additional work that might help us understand the implications of any definitions. It is an academic exercise without great practical value if we think about the definition of names in
the abstract. I suggest that we put some effort into really understanding the impact of those definitions by doing some analysis of a) the 2012 application process; b) the lengthy evaluation process and c) the ongoing implementation of geographic terms so
that we can see what happens in a real life. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I am happy to put together that schematic, in tandem with anyone else who is interested and, perhaps, with the help of the WG staff. I think it is a similar process to your “risk” analysis” that you had proposed. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Best wishes.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Liz<o:p></o:p></p>
<div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">On 8 Jan 2018, at 10:11 pm, Martin Sutton <<a href="mailto:martin@brandregistrygroup.org">martin@brandregistrygroup.org</a>> wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<p class="MsoNormal"><span style="background:white">Dear WT5 Members,</span><o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal" style="background:white"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal" style="background:white">One of the key areas identified during the WT5 TOR discussions related to the definition of geographic terms. This will be a priority focus for us as we begin the substantive work in WT5 and has been highlighted
in recent exchanges on the PDP WG mailing list. Defining geographic terms for the purpose of top-level domains will help us to frame our overall work within WT5. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="background:white">To ensure that all WT5 members are working from the same set of assumptions, we would like to have discussions about the working definition of geographic names at our next meeting on 17 Jan and request input from
members prior to the call.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="background:white">If you are not familiar with the history and context of how the GNSO policies and Applicant Guidebook evolved in relation to geographic terms, the final report of the Cross Community Working Group Framework for
the Use of Country and Territory Names as TLDs (CCWG-UCTN) provides a good background <a href="https://ccnso.icann.org/sites/default/files/field-attached/ccwg-ctn-final-paper-15jun17-en.pdf">https://ccnso.icann.org/sites/default/files/field-attached/ccwg-ctn-final-paper-15jun17-en.pdf</a>.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="background:white"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="background:white">The 2012 Applicant Guidebook states the following in relation to geographic terms:<o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="background:white"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b><i><span style="font-size:12.0pt;font-family:"BookAntiqua",serif;color:gray">2.2.1.4 Geographic Names Review</span></i></b><o:p></o:p></p>
</div>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;background:white">
<span style="font-size:10.0pt;font-family:"CenturyGothic",serif">Applications for gTLD strings must ensure that appropriate consideration is given to the interests of governments or public authorities in geographic names. The requirements and procedure ICANN
will follow in the evaluation process are described in the following paragraphs. Applicants should review these requirements even if they do not believe their intended gTLD string is a geographic name. All applied-for gTLD strings will be reviewed according
to the requirements in this section, regardless of whether the application indicates it is for a geographic name.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;background:white">
<b><i><span style="font-size:12.0pt;font-family:"BookAntiqua",serif;color:gray">2.2.1.4.1 Treatment of Country or Territory Names</span></i></b><b><i><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:gray;position:relative;top:-6.0pt;mso-text-raise:6.0pt">6</span></i></b><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;background:white">
<span style="font-size:10.0pt;font-family:"CenturyGothic",serif">Applications for strings that are country or territory names will not be approved, as they are not available under the New gTLD Program in this application round. A string shall be considered
to be a country or territory name if:</span><o:p></o:p></p>
<ol start="1" type="i">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1;background:white">
<span style="font-size:10.0pt;font-family:"CenturyGothic",serif">it is an alpha-3 code listed in the ISO 3166-1 standard.<o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1;background:white">
<span style="font-size:10.0pt;font-family:"CenturyGothic",serif">it is a long-form name listed in the ISO 3166-1 standard, or a translation of the long-form name in any language.<o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1;background:white">
<span style="font-size:10.0pt;font-family:"CenturyGothic",serif">it is a short-form name listed in the ISO 3166-1 standard, or a translation of the short-form name in any language.<o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1;background:white">
<span style="font-size:10.0pt;font-family:"CenturyGothic",serif">it is the short- or long-form name association with a code that has been designated as “exceptionally reserved” by the ISO 3166 Maintenance Agency.<o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1;background:white">
<span style="font-size:10.0pt;font-family:"CenturyGothic",serif">it is a separable component of a country name designated on the “Separable Country Names List,” or is a translation of a name appearing on the list, in any language. See the Annex at the end of
this module.<o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1;background:white">
<span style="font-size:10.0pt;font-family:"CenturyGothic",serif">it is a permutation or transposition of any of the names included in items (i) through (v). Permutations include removal of spaces, insertion of punctuation, and addition or removal of grammatical
articles like “the.” A transposition is considered a change in the sequence of the long or short–form name, for example, “RepublicCzech” or “IslandsCayman.”<o:p></o:p></span></li></ol>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:36.0pt;background:white">
<span style="font-size:10.0pt;font-family:"CenturyGothic",serif">vii. it is a name by which a country is commonly known, as demonstrated by evidence that the country is recognized by that name by an intergovernmental or treaty organization. <o:p></o:p></span></p>
</div>
</div>
</div>
</div>
<div>
<p class="MsoNormal" style="background:white"><b><i><span style="font-size:12.0pt;font-family:"BookAntiqua",serif;color:gray">2.2.1.4.2</span></i></b><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"><b><i><span style="font-size:12.0pt;font-family:"BookAntiqua",serif;color:gray">Geographic Names Requiring Government Support</span></i></b><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;font-family:"CenturyGothic",serif">The following types of applied-for strings are considered geographic names and must be accompanied by documentation of support or non-objection from
the relevant governments or public authorities:</span><o:p></o:p></p>
</div>
</div>
<ol style="margin-top:0cm" start="1" type="1">
<li class="MsoNormal" style="mso-list:l0 level1 lfo2;background:white"><span style="font-size:10.0pt;font-family:"CenturyGothic",serif">An application for any string that is a representation, in any language, of the <i>capital city name </i>of any country or
territory listed in the ISO 3166-1 standard.</span><o:p></o:p></li><li class="MsoNormal" style="mso-list:l0 level1 lfo2;background:white"><span style="font-size:10.0pt;font-family:"CenturyGothic",serif">An application for a <i>city name</i>, where the applicant declares that it intends to use the gTLD for purposes associated
with the city name.</span><o:p></o:p></li></ol>
<div style="margin-left:36.0pt">
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;font-family:"CenturyGothic",serif">City names present challenges because city names may also be generic terms or brand names, and in many cases city names are not unique. Unlike other
types of geographic names, there are no established lists that can be used as objective references in the evaluation process. Thus, city names are not universally protected. However, the process does provide a means for cities and applicants to work together
where desired.</span><o:p></o:p></p>
</div>
</div>
<div style="margin-left:36.0pt">
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;font-family:"CenturyGothic",serif">An application for a city name will be subject to the geographic names requirements (i.e., will require documentation of support or non-objection
from the relevant governments or public authorities) if:</span><o:p></o:p></p>
</div>
</div>
<div style="margin-left:36.0pt">
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;font-family:"CenturyGothic",serif">(a) It is clear from applicant statements within the application that the applicant will use the TLD primarily for purposes associated with the city
name; and</span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;font-family:"CenturyGothic",serif"> (b) The applied-for string is a city name as listed on official city documents.</span><span style="font-size:6.0pt;font-family:"ArialMT",serif">7</span><o:p></o:p></p>
</div>
</div>
<ol style="margin-top:0cm" start="3" type="1">
<li class="MsoNormal" style="mso-list:l2 level1 lfo3;background:white"><span style="font-size:10.0pt;font-family:"CenturyGothic",serif">An application for any string that is an exact match of a <i>sub-national place name</i>, such as a county, province, or
state, listed in the ISO 3166-2 standard.</span><o:p></o:p></li><li class="MsoNormal" style="mso-list:l2 level1 lfo3;background:white"><span style="font-size:10.0pt;font-family:"CenturyGothic",serif">An application for a string listed as a UNESCO region</span><span style="font-size:6.0pt;font-family:"ArialMT",serif">8 </span><span style="font-size:10.0pt;font-family:"CenturyGothic",serif">or
appearing on the “Composition of macro geographical (continental) regions, geographical sub-regions, and selected economic and other groupings” list.</span><span style="font-size:6.0pt;font-family:"ArialMT",serif">9</span><o:p></o:p></li></ol>
<div style="margin-left:36.0pt">
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;font-family:"CenturyGothic",serif">In the case of an application for a string appearing on either of the lists above, documentation of support will be required from at least 60% of
the respective national governments in the region, and there may be no more than one written statement of objection to the application from relevant governments in the region and/or public authorities associated with the continent or the region.</span><o:p></o:p></p>
</div>
</div>
<div style="margin-left:36.0pt">
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;font-family:"CenturyGothic",serif">Where the 60% rule is applied, and there are common regions on both lists, the regional composition contained in the “Composition of macro geographical
(continental) regions, geographical sub-regions, and selected economic and other groupings” takes precedence.</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;font-family:"CenturyGothic",serif">An applied-for gTLD string that falls into any of 1 through 4 listed above is considered to represent a geographic name. In the event of any doubt,
it is in the applicant’s interest to consult with relevant governments and public authorities and enlist their support or non-objection prior to submission of the application, in order to preclude possible objections and pre-address any ambiguities concerning
the string and applicable requirements.</span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;font-family:"CenturyGothic",serif">Strings that include but do not match a geographic name (as defined in this section) will not be considered geographic names as defined by section
2.2.1.4.2, and therefore will not require documentation of government support in the evaluation process.</span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:5.0pt;font-family:"ArialMT",serif;position:relative;top:-4.0pt;mso-text-raise:4.0pt">6 </span><span style="font-size:9.0pt;font-family:"ArialNarrow",serif">Country and territory names are
excluded from the process based on advice from the Governmental Advisory Committee in recent communiqués providing interpretation of Principle 2.2 of the GAC Principles regarding New gTLDs to indicate that strings which are a meaningful representation or
abbreviation of a country or territory name should be handled through the forthcoming ccPDP, and other geographic strings could be allowed in the gTLD space if in agreement with the relevant government or public authority. </span> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:6.0pt;font-family:"ArialNarrow",serif">7 </span><span style="font-size:9.0pt;font-family:"ArialNarrow",serif">City governments with concerns about strings that are duplicates, nicknames or
close renderings of a city name should not rely on the evaluation process as the primary means of protecting their interests in a string. Rather, a government may elect to file a formal objection to an application that is opposed by the relevant community,
or may submit its own application for the string.</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:5.0pt;font-family:"ArialMT",serif">8 </span><i><span style="font-size:9.0pt;font-family:"ArialNarrow",serif">See </span></i><span style="font-size:9.0pt;font-family:"ArialNarrow",serif;color:blue"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.unesco.org_new_en_unesco_worldwide_&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=UAy6fqdE7uFkRCc7uzN4yui8bwTtqofadZHiQEIO1vw&m=xkyKkaMrpFHC2Y7bYkg2dZgFxuTEPoPOyK6Gp8VdOjo&s=BFlNnYVG3cWU8E7WYL8IM3sAhljIgoJIlNXg7FOY0ZE&e="><span style="color:purple">http://www.unesco.org/new/en/unesco/worldwide/[unesco.org]</span></a></span><span style="font-size:9.0pt;font-family:"ArialNarrow",serif">.<br>
</span><span style="font-size:5.0pt;font-family:"ArialMT",serif">9 </span><i><span style="font-size:9.0pt;font-family:"ArialNarrow",serif">See </span></i><span style="font-size:9.0pt;font-family:"ArialNarrow",serif;color:blue"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__unstats.un.org_unsd_methods_m49_m49regin.htm&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=UAy6fqdE7uFkRCc7uzN4yui8bwTtqofadZHiQEIO1vw&m=xkyKkaMrpFHC2Y7bYkg2dZgFxuTEPoPOyK6Gp8VdOjo&s=OUphKkFDZowCxK0Owp9DX4kk3oafMaWuFbNFUpKV-CE&e="><span style="color:purple">http://unstats.un.org/unsd/methods/m49/m49regin.htm[unstats.un.org]</span></a></span><span style="font-size:9.0pt;font-family:"ArialNarrow",serif">. </span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"><b><u>WT5 ACTION</u></b><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white">For a potential new applicant guidebook, we need a consensus driven common understanding of geographic identifiers to provide clarity to potential applicants. We would like to gather input from WT5 members, specifically
whether the current definition is fit for purpose or not. If you think there should be changes, specify what these would be (additions, deletions) and the rationale for adding or removing any elements of the definition.<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"><b>Please submit your comments, ideally by 15 Jan, to provide an opportunity to discuss the input during our next call. </b><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="background:white">To submit your comment, please use the following link to the document or submit via email specifying:<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal" style="background:white"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="background:white">1. Contributor name<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="background:white">2. Addition/deletion/amendment to definition<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="background:white">3. Rationale to support the change<o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="background:white">This will then be added to the google doc which is available here (<a href="https://docs.google.com/spreadsheets/d/1ooKmb576MQJvpHyDYOlJE3M2-Ssnv-SSgVfroT3D7Fc/edit?usp=sharing">https://docs.google.com/spreadsheets/d/1ooKmb576MQJvpHyDYOlJE3M2-Ssnv-SSgVfroT3D7Fc/edit?usp=sharing</a>)
for those that may wish to populate the document directly. Please do not amend any other entries as this document will not track changes.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="background:white">We look forward to receiving your input.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="background:white">Kind regards<o:p></o:p></p>
</div>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><b>WT5 Co-Leaders</b> <o:p></o:p></p>
<div>
<p class="MsoNormal">Annebeth Lange<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Christopher Wilkinson<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Martin Sutton<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Olga Cavalli<o:p></o:p></p>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif"><o:p> </o:p></span></p>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<p class="MsoNormal">_______________________________________________<br>
Gnso-newgtld-wg-wt5 mailing list<br>
<a href="mailto:Gnso-newgtld-wg-wt5@icann.org">Gnso-newgtld-wg-wt5@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5">https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5</a><o:p></o:p></p>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<p class="MsoNormal">_______________________________________________<br>
Gnso-newgtld-wg-wt5 mailing list<br>
<a href="mailto:Gnso-newgtld-wg-wt5@icann.org">Gnso-newgtld-wg-wt5@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5">https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5</a><o:p></o:p></p>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Gnso-newgtld-wg-wt5 mailing list</span><br><span><a href="mailto:Gnso-newgtld-wg-wt5@icann.org">Gnso-newgtld-wg-wt5@icann.org</a></span><br><span><a href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5">https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5</a></span></div></blockquote></div></body></html>