<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=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
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="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoPlainText>Hi,<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Page 21 the three preferences how alpha-3 codes could be handled:<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>1) support for opening all ISO 3166-1 alpha-3 codes to <span style='color:red'>eligiblity </span>as gTLDs (eligibility is misspelled - and the sentence makes no sense! Probably meant as: "...... to be eligible as gTLDs"?)<o:p></o:p></p><p class=MsoPlainText><br>I do not see any more the option that has already garnered a LOT of support: Treating the 3 letter ISO 3166 alpha 3 codes like ALL other designators in the ISO 3166 (e.g. “BAR” or “TATA”): In the existing AG for ALL 3166 listed elements there is a requirement that the relevant Government authority has to sign a letter of non-objection! <br><br>So I suggest we either add to 1) that OF COURSE the already established AG requirement for a letter of non-objection would be triggered for alpha-3 codes as well!<o:p></o:p></p><p class=MsoPlainText>Or we have a 4<sup>th</sup> preference.<br>Indeed: Annex D provides for FOUR possibilities discussed by the SOs/ACs. <br><br><br>On page 22 it says:<o:p></o:p></p><p class=MsoPlainText>“Supporting to open all 3-character codes as gTLDs:<br>• There is no sovereign or other ownership right of governments in country or territory names, including ISO 3166-1 codes, <span style='color:red'>so there is no legal basis for government veto power on allocation of these codes as gTLDs”</span><o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Not true! The AG has a provision whereby ALL ISO 3166 elements need a letter of non-objection of the Government! See “.bar” or “.tata”! Obviously if already a tiny mini municipality like the TATA region (15,000 people, all desert, no industry, but listed in ISO 3166) requires such a letter then OF COURSE a 3 letter ISO 3166 alpha 3 code requires it as well!<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Thanks,<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Alexander Schubert<br><br><br><o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>-----Original Message-----<br>From: ctn-crosscom-bounces@icann.org [mailto:ctn-crosscom-bounces@icann.org] On Behalf Of Emily Barabas<br>Sent: Wednesday, January 25, 2017 10:26 PM<br>To: Jaap Akkerhuis <jaap@NLnetLabs.nl><br>Cc: ctn-crosscom@icann.org<br>Subject: Re: [Ctn-crosscom] [Ext] Re: Interim Paper for public comment</p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Dear Jaap,<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Thank you for your review and feedback. Staff will review the formatting and content of the frames. <o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Kind regards,<o:p></o:p></p><p class=MsoPlainText>Emily<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>On 25/01/17 04:48, "Jaap Akkerhuis" <<a href="mailto:jaap@NLnetLabs.nl"><span style='color:windowtext;text-decoration:none'>jaap@NLnetLabs.nl</span></a>> wrote:<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText> Emily Barabas writes:<o:p></o:p></p><p class=MsoPlainText> <o:p></o:p></p><p class=MsoPlainText> > Please find attached a revised version of the CWG-UCTN Interim Paper.<o:p></o:p></p><p class=MsoPlainText> > This version incorporates language to reflect a lack of consensus on<o:p></o:p></p><p class=MsoPlainText> > recommendation 3.<o:p></o:p></p><p class=MsoPlainText> > <o:p></o:p></p><p class=MsoPlainText> > <o:p></o:p></p><p class=MsoPlainText> > Kindly provide any final revisions or comments on the Interim Paper by<o:p></o:p></p><p class=MsoPlainText> > Friday 3 February.<o:p></o:p></p><p class=MsoPlainText> <o:p></o:p></p><p class=MsoPlainText> Dear Emily,<o:p></o:p></p><p class=MsoPlainText> <o:p></o:p></p><p class=MsoPlainText> I did a quick scan and noticed that something went with the two<o:p></o:p></p><p class=MsoPlainText> "Frames" about the ISO 3166. They now look as a single one to me. But<o:p></o:p></p><p class=MsoPlainText> apart from that, the first one seemed to have a garbled sentences here<o:p></o:p></p><p class=MsoPlainText> and there. Note the start of the second section, to quote:<o:p></o:p></p><p class=MsoPlainText> <o:p></o:p></p><p class=MsoPlainText> The ISO body responsible for the standard 3166 is the<o:p></o:p></p><p class=MsoPlainText> Technical Committee 46, systems etc. and as non-current,<o:p></o:p></p><p class=MsoPlainText> dependencies, and other areas of particular geopolitical<o:p></o:p></p><p class=MsoPlainText> interest (ISO/TC 46/WG2).<o:p></o:p></p><p class=MsoPlainText> <o:p></o:p></p><p class=MsoPlainText> And there are more of these.<o:p></o:p></p><p class=MsoPlainText> <o:p></o:p></p><p class=MsoPlainText> I will have a nore close read later, but these things really needs to<o:p></o:p></p><p class=MsoPlainText> be clean up.<o:p></o:p></p><p class=MsoPlainText> <o:p></o:p></p><p class=MsoPlainText> Regards,<o:p></o:p></p><p class=MsoPlainText> <o:p></o:p></p><p class=MsoPlainText> jaap<o:p></o:p></p><p class=MsoPlainText> <o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>_______________________________________________<o:p></o:p></p><p class=MsoPlainText>Ctn-crosscom mailing list<o:p></o:p></p><p class=MsoPlainText><a href="mailto:Ctn-crosscom@icann.org"><span style='color:windowtext;text-decoration:none'>Ctn-crosscom@icann.org</span></a><o:p></o:p></p><p class=MsoPlainText><a href="https://mm.icann.org/mailman/listinfo/ctn-crosscom"><span style='color:windowtext;text-decoration:none'>https://mm.icann.org/mailman/listinfo/ctn-crosscom</span></a><o:p></o:p></p></div></body></html>