<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
Hi all,
<div><br>
</div>
<div>In my opinion it is outside the scope of WT5 to judge anything else than geographic terms. <span style="background-color: rgb(255, 255, 255);"><font face="Trebuchet MS, sans-serif">In terms of 2 character (ie F1 and 3M etc) those, in my mind, aren’t geo
terms and thus out of scope.</font></span>
<div><span style="background-color: rgb(255, 255, 255);"><font face="Trebuchet MS, sans-serif"><br>
</font></span></div>
<div><span style="background-color: rgb(255, 255, 255);"><font face="Trebuchet MS, sans-serif">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. </font></span>
<div><font face="Trebuchet MS, sans-serif"><span style="background-color: rgb(255, 255, 255);"><br>
</span></font>
<div><font face="Trebuchet MS, sans-serif"><span style="background-color: rgb(255, 255, 255);"><br>
</span></font></div>
<div><font face="Trebuchet MS, sans-serif"><span style="background-color: rgb(255, 255, 255);">Best,</span></font></div>
<div><font face="Trebuchet MS, sans-serif"><span style="background-color: rgb(255, 255, 255);">Ann-Cathrin</span></font></div>
<div><font face="Trebuchet MS, sans-serif"><span style="background-color: rgb(255, 255, 255);"><br>
</span></font></div>
<div><br>
<div apple-content-edited="true">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></div>
</div>
</div>
</div>
<div>
<div>On 18 Jan 2018, at 17:16, Alexander Schubert <<a href="mailto:alexander@schubert.berlin">alexander@schubert.berlin</a>> wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div lang="EN-US" link="blue" vlink="purple" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
<div class="WordSection1" style="page: WordSection1;">
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;">Hi Rosalia,<o:p></o:p></span></div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;"> </span></div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;">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”?<o:p></o:p></span></div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;"> </span></div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;">Thanks,<o:p></o:p></span></div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;"> </span></div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;">Alexander<o:p></o:p></span></div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;"> </span></div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;"><br>
<br>
<o:p></o:p></span></div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;"> </span></div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;"> </span></div>
<div>
<div style="border-style: solid none none; border-top-color: rgb(225, 225, 225); border-top-width: 1pt; padding: 3pt 0cm 0cm;">
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<b><span style="font-size: 11pt; font-family: Calibri, sans-serif;">From:</span></b><span style="font-size: 11pt; font-family: Calibri, sans-serif;"><span class="Apple-converted-space"> </span>Gnso-newgtld-wg-wt5 [<a href="mailto:gnso-newgtld-wg-wt5-bounces@icann.org" style="color: purple; text-decoration: underline;">mailto:gnso-newgtld-wg-wt5-bounces@icann.org</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" style="color: purple; text-decoration: underline;">Gnso-newgtld-wg-wt5@icann.org</a>><br>
<b>Subject:</b><span class="Apple-converted-space"> </span>Re: [Gnso-newgtld-wg-wt5] Conclusion of CWG-UCTN on 2-character codes<o:p></o:p></span></div>
</div>
</div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<o:p> </o:p></div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
Dear All,<o:p></o:p></div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<o:p> </o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; 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></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<o:p> </o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
Best,<o:p></o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
Rosalía<o:p></o:p></div>
</div>
<div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span><image001.png></span><o:p></o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<br>
<br>
<o:p></o:p></div>
<blockquote style="margin-top: 5pt; margin-bottom: 5pt;">
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
On Jan 18, 2018, at 8:43 AM, Timo Võhmar <<a href="mailto:timo.vohmar@internet.ee" style="color: purple; text-decoration: underline;">timo.vohmar@internet.ee</a>> wrote:<o:p></o:p></div>
</div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<o:p> </o:p></div>
<div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
Some may know that I represent a bit different view on things than Alexander<o:p></o:p></div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<o:p> </o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; 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></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<o:p> </o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; 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></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<o:p> </o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; 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></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<o:p> </o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; 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></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<o:p> </o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; 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></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<o:p> </o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
Best Regards,<o:p></o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
Timo Võhmar<o:p></o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
Representing Estonian internet community, government and ccTLD .ee registry<o:p></o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<o:p> </o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<o:p> </o:p></div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; 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" style="color: purple; text-decoration: underline;">gregshatanipc@gmail.com</a>> wrote:<o:p></o:p></div>
<blockquote style="border-style: none none none solid; border-left-color: rgb(204, 204, 204); border-left-width: 1pt; padding: 0cm 0cm 0cm 6pt; margin-left: 4.8pt; margin-right: 0cm;">
<div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="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.<o:p></o:p></span></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-family: Verdana, sans-serif;"> </span></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="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. <o:p></o:p></span></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-family: Verdana, sans-serif;"> </span></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="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.<o:p></o:p></span></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-family: Verdana, sans-serif;"> </span></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="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.<o:p></o:p></span></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-family: Verdana, sans-serif;"> </span></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-family: Verdana, sans-serif;">Greg<o:p></o:p></span></div>
</div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<o:p> </o:p></div>
<div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; 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" style="color: purple; text-decoration: underline;">alexander@schubert.berlin</a>> wrote:<o:p></o:p></div>
</div>
<blockquote style="border-style: none none none solid; border-left-color: rgb(204, 204, 204); border-left-width: 1pt; padding: 0cm 0cm 0cm 6pt; margin-left: 4.8pt; margin-right: 0cm;">
<div>
<div>
<p class="MsoNormal" style="margin: 0cm 0cm 12pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;">I think the two character TLD question is rather simplistic:</span><o:p></o:p></p>
<p class="m8363799439097236901m3354933718473043495msolistparagraph" style="margin-right: 0cm; margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Symbol;">·</span><span style="font-size: 7pt;"> <span class="Apple-converted-space"> </span></span><span style="font-size: 11pt; font-family: Calibri, sans-serif;">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><o:p></o:p></p>
<p class="m8363799439097236901m3354933718473043495msolistparagraph" style="margin-right: 0cm; margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Symbol;">·</span><span style="font-size: 7pt;"> <span class="Apple-converted-space"> </span></span><span style="font-size: 11pt; font-family: Calibri, sans-serif;">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><o:p></o:p></p>
<p class="m8363799439097236901m3354933718473043495msolistparagraph" style="margin-right: 0cm; margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Symbol;">·</span><span style="font-size: 7pt;"> <span class="Apple-converted-space"> </span></span><span style="font-size: 11pt; font-family: Calibri, sans-serif;">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" style="color: purple; text-decoration: underline;">3m.com</a>)
or “.f1” (<a href="http://f1.com/" target="_blank" style="color: purple; text-decoration: underline;">f1.com</a>). How many would that be? A dozen?</span><o:p></o:p></p>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;"> </span><o:p></o:p></div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;">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><o:p></o:p></div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;"> </span><o:p></o:p></div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;">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><o:p></o:p></div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;"><br>
Thanks,</span><o:p></o:p></div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;"> </span><o:p></o:p></div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;">Alexander</span><o:p></o:p></div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;"> </span><o:p></o:p></div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;"> </span><o:p></o:p></div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;"> </span><o:p></o:p></div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;"> </span><o:p></o:p></div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<b><span style="font-size: 11pt; font-family: Calibri, sans-serif;">From:</span></b><span style="font-size: 11pt; font-family: Calibri, sans-serif;"><span class="Apple-converted-space"> </span>Gnso-newgtld-wg-wt5 [mailto:<a href="mailto:gnso-newgtld-wg-wt5-bounces@icann.org" target="_blank" style="color: purple; text-decoration: underline;">gnso-newgtld-wg-wt5-bounces@icann.org</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" style="color: purple; text-decoration: underline;">Gnso-newgtld-wg-wt5@icann.org</a><br>
<b>Subject:</b><span class="Apple-converted-space"> </span>[Gnso-newgtld-wg-wt5] Conclusion of CWG-UCTN on 2-character codes</span><o:p></o:p></div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<o:p></o:p></div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
Dear colleagues,<o:p></o:p></div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<o:p></o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; 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></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<o:p></o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; 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></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<o:p></o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; 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></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<o:p></o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; 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" style="color: purple; text-decoration: underline;">https://ccnso.icann.org/sites/default/files/field-attached/ccwg-ctn-final-paper-15jun17-en.pdf</a><o:p></o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<o:p></o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
Kind regards,<o:p></o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<o:p></o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
Heather Forrest<o:p></o:p></div>
</div>
</div>
</div>
</div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<o:p> </o:p></div>
</div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; 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" style="color: purple; text-decoration: underline;">Gnso-newgtld-wg-wt5@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5" target="_blank" style="color: purple; text-decoration: underline;">https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5</a><o:p></o:p></div>
</blockquote>
</div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<o:p> </o:p></div>
</div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<br>
_______________________________________________<br>
Gnso-newgtld-wg-wt5 mailing list<br>
<a href="mailto:Gnso-newgtld-wg-wt5@icann.org" style="color: purple; text-decoration: underline;">Gnso-newgtld-wg-wt5@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5" target="_blank" style="color: purple; text-decoration: underline;">https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5</a><o:p></o:p></div>
</blockquote>
</div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<o:p> </o:p></div>
</div>
</div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
_______________________________________________<br>
Gnso-newgtld-wg-wt5 mailing list<br>
<a href="mailto:Gnso-newgtld-wg-wt5@icann.org" style="color: purple; text-decoration: underline;">Gnso-newgtld-wg-wt5@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5" style="color: purple; text-decoration: underline;">https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5</a><o:p></o:p></div>
</div>
</blockquote>
</div>
<div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<o:p> </o:p></div>
</div>
</div>
_______________________________________________<br>
Gnso-newgtld-wg-wt5 mailing list<br>
<a href="mailto:Gnso-newgtld-wg-wt5@icann.org" style="color: purple; text-decoration: underline;">Gnso-newgtld-wg-wt5@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5" style="color: purple; text-decoration: underline;">https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5</a></div>
</blockquote>
</div>
<br>
</div>
</body>
</html>