<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: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:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Trebuchet MS";
panose-1:2 11 6 3 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
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:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
p.m8363799439097236901m3354933718473043495msolistparagraph, li.m8363799439097236901m3354933718473043495msolistparagraph, div.m8363799439097236901m3354933718473043495msolistparagraph
{mso-style-name:m8363799439097236901m3354933718473043495msolistparagraph;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle21
{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:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><a name="_MailEndCompose">Liz,<o:p></o:p></a></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose">To respond only to your last point, Work Track 2 is handling the issue of reserved names at the top level and second level generally. To the extent they are not “geographic names”, Work Track
2 is discussing and has some initial thoughts on those.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose">With respect to single or 2 character IDNs, to the extent that they are not “geographic”, work track 4 is working on that issue. Work Track 4 I believe is coming to the conclusion that in general
certain 1 character IDNs can be used as top level domains. But that is oversimplifying the conclusion. For more information on that go to Work Track 4.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><b><span lang="EN-GB" style="font-family:"Verdana",sans-serif;color:#0F9347">Jeffrey J. Neuman</span></b></span><span style="mso-bookmark:_MailEndCompose"><span lang="EN-GB" style="color:#1F497D"><o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><b><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#0F9347">Senior Vice President </span></b></span><span style="mso-bookmark:_MailEndCompose"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#4F4F4F">|</span></span><span style="mso-bookmark:_MailEndCompose"><b><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#C39209">Valideus
USA</span></b></span><span style="mso-bookmark:_MailEndCompose"><b><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#C32830">
</span></b></span><span style="mso-bookmark:_MailEndCompose"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#4F4F4F">| </span></span><span style="mso-bookmark:_MailEndCompose"><b><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#C32830">Com
Laude USA</span></b></span><span style="mso-bookmark:_MailEndCompose"><span lang="EN-GB" style="color:#1F497D"><o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#4F4F4F">1751 Pinnacle Drive, Suite 600<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#4F4F4F">Mclean, VA 22102, United States<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#4F4F4F">E:
</span></span><span style="mso-bookmark:_MailEndCompose"></span><a href="mailto:jeff.neuman@valideus.com"><span style="mso-bookmark:_MailEndCompose"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#00B050">jeff.neuman@valideus.com</span></span></a><span style="mso-bookmark:_MailEndCompose"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#595959">
or </span></span><span style="mso-bookmark:_MailEndCompose"></span><a href="mailto:jeff.neuman@comlaude.com"><span style="mso-bookmark:_MailEndCompose"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#00B050">jeff.neuman@comlaude.com</span></span></a><span style="mso-bookmark:_MailEndCompose"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#00B050">
<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#4F4F4F">T: +1.703.635.7514<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#4F4F4F">M: +1.202.549.5079<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#4F4F4F">@Jintlaw<o:p></o:p></span></span></p>
</div>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></span></p>
<span style="mso-bookmark:_MailEndCompose"></span>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Gnso-newgtld-wg-wt5 [mailto:gnso-newgtld-wg-wt5-bounces@icann.org]
<b>On Behalf Of </b>Liz Williams<br>
<b>Sent:</b> Friday, January 19, 2018 7:44 AM<br>
<b>To:</b> Ann-Cathrin Marcussen <ann-cathrin.marcussen@norid.no><br>
<b>Cc:</b> Icann Gnso Newgtld Wg Wt5 <Gnso-newgtld-wg-wt5@icann.org><br>
<b>Subject:</b> Re: [Gnso-newgtld-wg-wt5] Conclusion of CWG-UCTN on 2-character codes<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hello everyone <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Ann-Cathrin has raised some interesting points which are all mixed together.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">1. ASCII two letter combinations are currently used to define country codes which are commonly used geographic identifiers for ccTLD operators. It seems we all agree on that if I read the sentiment on the list correctly. And we would
maintain the policy recommendation to use the ISO3166 lists to define what those two character combinations are.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">2. Other combinations of 2 characters could easily be IDN scripts (for example using the two characters for Osaka) would be a 2 character geographic term and there are many other examples in many different scripts. We need to find consensus
on how to treat two characters (IDNs) in the context of our work here. Should they be treated in the same way as ASCII characters?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">3. And then the much more difficult proposition that a gTLD “should" be 3 characters or more. Of course, we already have examples where two character country codes (for example, .la, .co & .tv) are used generically to register names which
have nothing to do with a geographic term or a country code. I would have to question the assumption that a gTLD of, say, F1, would be anything other than generic, not confusable with a country code but I do think we need clarification on this interesting
point.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">4. And then the most difficult line which is that “gTLDs need to be at least three characters”. This presumes that we continue with the two character ASCII limitation and that many potential new geographic identifiers (for short hand
geo names) should be at least three characters…in ASCII and IDN? If we follow this logic it means that any new TLD that is a geographic identifier (and then it would be evaluated and implemented as such) could be both a geo name and a generic TLD (for registry
agreement purposes with all the conditions that attach to that agreement).<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">5. And finally, do we put out of scope number/letter, letter/number and number/number combinations as they may not be geographic identifiers? That is a question which I think needs further examination quite broadly before we decide if,
for the purposes of this group, if it is indeed out of scope. If it is, then what other work track is dealing with it because the issue is open.<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>
<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>
<div>
<p class="MsoNormal"><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 19 Jan 2018, at 12:03 pm, Ann-Cathrin Marcussen <<a href="mailto:ann-cathrin.marcussen@norid.no">ann-cathrin.marcussen@norid.no</a>> wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">Hi all, <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">In my opinion it is outside the scope of WT5 to judge anything else than geographic terms. <span style="font-family:"Trebuchet MS",sans-serif;background:white">In terms of 2 character (ie F1 and 3M etc) those, in my mind, aren’t geo terms
and thus out of scope.</span> <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Trebuchet MS",sans-serif;background:white">I am also of the opinion that we should keep the system that the requirement is that a gTLD needs to be at least 3 characters. </span>
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Trebuchet MS",sans-serif;background:white">Best,</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Trebuchet MS",sans-serif;background:white">Ann-Cathrin</span><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>
<p class="MsoNormal">Best regards / Med vennlig hilsen <br>
<br>
Ann-Cathrin Marcussen<br>
Head of Legal<br>
<br>
<br>
UNINETT Norid AS<br>
7465 Trondheim<br>
<br>
Oslokontor<br>
St Olavs Plass 2<br>
0165 Oslo <br>
<br>
Mobil +47 920 14 282<br>
<a href="mailto:acm@uninett.no">acm@uninett.no</a><o:p></o:p></p>
</div>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal">On 18 Jan 2018, at 17:16, Alexander Schubert <<a href="mailto:alexander@schubert.berlin">alexander@schubert.berlin</a>> wrote:<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>
<div>
<p class="MsoNormal">Hi Rosalia,<span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"> <span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal">Do you support to reserve only the 2 LETTER codes, or all ASCII two CHARACTER codes? E.g.: Would you be OK with a gTLD “.f1” or “.3m”?<span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"> <span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal">Thanks,<span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"> <span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal">Alexander<span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"> <span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><br>
<br>
<br>
<span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"> <span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"> <span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
</div>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<div>
<p class="MsoNormal"><b>From:</b><span class="apple-converted-space"> </span>Gnso-newgtld-wg-wt5 [<a href="mailto:gnso-newgtld-wg-wt5-bounces@icann.org"><span style="color:purple">mailto:gnso-newgtld-wg-wt5-bounces@icann.org</span></a>]<span class="apple-converted-space"> </span><b>On
Behalf Of<span class="apple-converted-space"> </span></b>Rosal?a Morales<br>
<b>Sent:</b><span class="apple-converted-space"> </span>Thursday, January 18, 2018 5:47 PM<br>
<b>Cc:</b><span class="apple-converted-space"> </span>Icann Gnso Newgtld Wg Wt5 <<a href="mailto:Gnso-newgtld-wg-wt5@icann.org"><span style="color:purple">Gnso-newgtld-wg-wt5@icann.org</span></a>><br>
<b>Subject:</b><span class="apple-converted-space"> </span>Re: [Gnso-newgtld-wg-wt5] Conclusion of CWG-UCTN on 2-character codes<span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">Dear All,<o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">As a member of the already closed CWG-UCTN, I support the consensus that the group came about regarding 2-letter TLDs: reserving 2-letter codes for ccTLDs should be maintained.
The effort and many years of discussion of the CWG-UCTN should serve as a great stepping sone for this working group to build on. Opening this for debate once again, will lead to lengthy discussions and we will be reinventing the wheel once again. I strongly
recommend supporting reserving 2-letter codes for ccTLDs as concluded by CWG-UCTN.<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">Best,<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">Rosalía<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><image001.png><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
<br>
<br>
<o:p></o:p></span></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">On Jan 18, 2018, at 8:43 AM, Timo Võhmar <<a href="mailto:timo.vohmar@internet.ee"><span style="color:purple">timo.vohmar@internet.ee</span></a>> wrote:<o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> <o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">Some may know that I represent a bit different view on things than Alexander<o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">We do not need to do anything ie reserve anything to anyone and least of all does the rfc say anything about that. The RFC sets out closed list of what is generic tld and
we know that has not been true for a long time. So what we have here in case of two letters is just an agreement between different communities saying that all two letter combinations are reserved for use under ccTLD policy. We also have renewed this agreement
multiple times and there seems to be no strong demand in changing this. But at the same time that does not mean that ccTLD cannot be anything else than some two letter combination.<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">cc in ccTLD stands for country code. Country code can mean any type of label, name, letter combination that represents some country. Unfortunately we do not have community
wide agreement on how to treat 3-letter ISO country codes and country names. There is a demand to make these available for use under ccTLD policy as well as gTLD policy. This need to find a compromise seems to be one of the reasons we have gathered.<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">Of course the question at hand is wider - anything that represents anything with geographical meaning. And we are here by invitation of gNSO with the new gTLD round in mind
but I do believe that it is not possible to change the current status quo disregarding the interests of countries to protect and develop their identity. One way to separate generics from country codes is who runs the delegation and perhaps on what purpose.<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">And I would once again like to argue that anyone outside our community has or even should have any notion about meaning of generic and country code TLDs in the ICANNs policy
context. It's all about what the TLD stands for ie there are few people that associate .tv with Tuvalu nor do I see that there could be anything generic about .usa. So we are speaking here about how these TLDs are delegated, regulated and how much control
does registry/government have on how to run the TLD. Noone in the real world will get confused when suddenly there are n letter TLDs given out under ccTLD nor 2 character TLDs under gTLD policy - these are just TLDs. <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">Lets leave the emotional arguments aside and try to find better solution for geographic terms for the next gTLD round and see if we can find a way to lift the ban from country
labels.<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">Best Regards,<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">Timo Võhmar<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">Representing Estonian internet community, government and ccTLD .ee registry<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> <o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">On Thu, Jan 18, 2018 at 8:12 AM, Greg Shatan <<a href="mailto:gregshatanipc@gmail.com" target="_blank"><span style="color:purple">gregshatanipc@gmail.com</span></a>> wrote:<o:p></o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Verdana",sans-serif">I don't disagree with the idea that all two-letter combinations should be reserved for potential ccTLD use. I thought it was worth raising the question on our recent call
so that we could actively test the status quo on this point. (Also, nobody was speaking up....) It appears that this concept retains broad support.</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Verdana",sans-serif"> </span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Verdana",sans-serif">That said, I would like to take Alexander's invitation to correct him if his statements are factually incorrect or illogical. Specifically, it is both factually incorrect
and illogical to couch this in terms of "brands." There's absolutely no basis or evidence for the proposition that brands have a particular interest in or desire for two letter TLDs (or that other applicants have less or more interest or desire). Intentionally
or not, using that scenario stirs up tensions and creates an adversarial atmosphere that could be quite counterproductive. There's no reason to invent a disagreement or rift that doesn't exist. </span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Verdana",sans-serif"> </span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Verdana",sans-serif">I would therefore suggest that the LAST thing the ccNSO should do is ask themselves the question posed by Alexander above. There's no good reason to pose that question or
to approach this issue in that way, and there are plenty of good reasons not to do so.</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Verdana",sans-serif"> </span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Verdana",sans-serif">Instead, we should approach this as one point on which we have broad support from all sectors, including many from the brand community.</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Verdana",sans-serif"> </span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Verdana",sans-serif">Greg</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> <o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">On Wed, Jan 17, 2018 at 10:45 AM, Alexander Schubert <<a href="mailto:alexander@schubert.berlin" target="_blank"><span style="color:purple">alexander@schubert.berlin</span></a>>
wrote:<o:p></o:p></span></p>
</div>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">I think the two character TLD question is rather simplistic:<span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
<p class="m8363799439097236901m3354933718473043495msolistparagraph"><span style="font-family:Symbol">·</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif"> <span class="apple-converted-space"> </span></span>We need to reserve ALL
two letter combinations – RFP 1591 says so. Or we need to revise RFC 1591: GOOD LUCK with that one! Easier to revise the Bible – or the Bill of Rights!<span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
<p class="m8363799439097236901m3354933718473043495msolistparagraph"><span style="font-family:Symbol">·</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif"> <span class="apple-converted-space"> </span></span>We can’t assign two number
combinations as they could be confused with IP addresses: Example 4<sup>th</sup><span class="apple-converted-space"> </span>level domain “44.33.22.11” based on the gTLD “.11”!<span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
<p class="m8363799439097236901m3354933718473043495msolistparagraph"><span style="font-family:Symbol">·</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif"> <span class="apple-converted-space"> </span></span>What remains are number-letter
combinations! That’s 2 times 10 numbers by 26 letters = 520 combinations. With almost NONE of them really desirable for anybody. The rare desirable ones would be likely BRANDS, such as “.3m” (<a href="http://3m.com/" target="_blank"><span style="color:purple">3m.com</span></a>)
or “.f1” (<a href="http://f1.com/" target="_blank"><span style="color:purple">f1.com</span></a>). How many would that be? A dozen?<span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
<div>
<p class="MsoNormal"> <span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal">On the other hand: Outside of the U.S. (96% of the world population is non-American) EVERYBODY knows that a two letter TLD is “something different”. And that is the one and only distinction the ccNSO world owns: they are the arbiters of
the two character namespace on the top-level! Two-characters = ccTLD. Everything else = gTLD.<span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"> <span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal">If I were the ccNSO I would ask myself: Just so that a handful of brands COULD (and nobody knows IF they WOULD want) grab a two character number-letter gTLD: do we have to give up the old order? As ccNSO member and as GAC member I would
clearly draw a line here and say: “NO WAY”. 2 characters is the namespace-characterization of the ccNSO (even when they only use two letter combinations). Outside of the U.S. it would very much confuse the Internet User if suddenly SOME 2-character were gTLDs
– or 3-letter TLDs were ccTLDs. That would destroy the old order.<span class="apple-converted-space"> </span><br>
<br>
If this is factual incorrect or illogical: please correct me. If you support this notion: please voice your support!<span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><br>
Thanks,<span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"> <span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal">Alexander<span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"> <span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"> <span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"> <span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"> <span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><b>From:</b><span class="apple-converted-space"> </span>Gnso-newgtld-wg-wt5 [mailto:<a href="mailto:gnso-newgtld-wg-wt5-bounces@icann.org" target="_blank"><span style="color:purple">gnso-newgtld-wg-wt5-bounces@icann.org</span></a>]<span class="apple-converted-space"> </span><b>On
Behalf Of<span class="apple-converted-space"> </span></b>Heather Forrest<br>
<b>Sent:</b><span class="apple-converted-space"> </span>Wednesday, January 17, 2018 8:42 AM<br>
<b>To:</b><span class="apple-converted-space"> </span><a href="mailto:Gnso-newgtld-wg-wt5@icann.org" target="_blank"><span style="color:purple">Gnso-newgtld-wg-wt5@icann.org</span></a><br>
<b>Subject:</b><span class="apple-converted-space"> </span>[Gnso-newgtld-wg-wt5] Conclusion of CWG-UCTN on 2-character codes<span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> <o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">Dear colleagues,<o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">Following up on Jeff's reference at the end of the WT5 call ended just now to the conclusions of the Cross-Community WG on the Use of Country and Territory Names (CWG-UCTN)- <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">The conclusion of the CWG-UCTN on 2-character codes, and the rationale for that conclusion, was:<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">"The CWG recommends that the existing ICANN policy of reserving 2-letter codes for ccTLDs should be maintained, primarily on the basis of the reliance of this policy, consistent
with RFC 1591, on a standard established and maintained independently of and external to ICANN and widely adopted in contexts outside of the DNS (ISO 3166-1)."<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">Full report here: <a href="https://ccnso.icann.org/sites/default/files/field-attached/ccwg-ctn-final-paper-15jun17-en.pdf" target="_blank"><span style="color:purple">https://ccnso.icann.org/sites/default/files/field-attached/ccwg-ctn-final-paper-15jun17-en.pdf</span></a><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">Kind regards,<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">Heather Forrest<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> <o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">_______________________________________________<br>
Gnso-newgtld-wg-wt5 mailing list<br>
<a href="mailto:Gnso-newgtld-wg-wt5@icann.org" target="_blank"><span style="color:purple">Gnso-newgtld-wg-wt5@icann.org</span></a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5" target="_blank"><span style="color:purple">https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5</span></a><o:p></o:p></span></p>
</div>
</blockquote>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> <o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
_______________________________________________<br>
Gnso-newgtld-wg-wt5 mailing list<br>
<a href="mailto:Gnso-newgtld-wg-wt5@icann.org"><span style="color:purple">Gnso-newgtld-wg-wt5@icann.org</span></a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5" target="_blank"><span style="color:purple">https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5</span></a><o:p></o:p></span></p>
</div>
</blockquote>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> <o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">_______________________________________________<br>
Gnso-newgtld-wg-wt5 mailing list<br>
<a href="mailto:Gnso-newgtld-wg-wt5@icann.org"><span style="color:purple">Gnso-newgtld-wg-wt5@icann.org</span></a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5"><span style="color:purple">https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5</span></a><o:p></o:p></span></p>
</div>
</div>
</blockquote>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> <o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif">_______________________________________________<br>
Gnso-newgtld-wg-wt5 mailing list<br>
<a href="mailto:Gnso-newgtld-wg-wt5@icann.org"><span style="color:purple">Gnso-newgtld-wg-wt5@icann.org</span></a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5"><span style="color:purple">https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5</span></a><o:p></o:p></span></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>
</body>
</html>