<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>New gTLD Program Draft Request for Proposals</title>
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0);">
<div>
<div style="font-size: 14px; font-family: 'Comic Sans MS', sans-serif;">Dear Alexander,</div>
<div style="font-size: 14px; font-family: 'Comic Sans MS', sans-serif;"><br>
</div>
<div style="font-size: 14px; font-family: 'Comic Sans MS', sans-serif;">I have followed the discussion with interest. First let me say, you guys have done a terrific job with .berlin – many times it must have felt like the never ending story. It was a really
good idea creating cityTLDs. The regime for them according to the AGB - which we must view as present policy as long as there hasn’t been decided otherwise – established this rule: </div>
<div style="font-size: 14px; font-family: 'Comic Sans MS', sans-serif;"><br>
</div>
<div style="font-size: 14px; font-family: 'Comic Sans MS', sans-serif;">
<div class="page" title="Page 17">
<div class="layoutArea">
<div class="column">
<p><span style="font-size: 12.000000pt; font-family: 'BookAntiqua'; font-weight: 700; font-style: italic; color: rgb(50.200000%, 50.200000%, 50.200000%)">2.2.1.4.2
</span></p>
</div>
<div class="column">
<p><span style="font-size: 12.000000pt; font-family: 'BookAntiqua'; font-weight: 700; font-style: italic; color: rgb(50.200000%, 50.200000%, 50.200000%)">Geographic Names Requiring Government Support</span></p>
</div>
</div>
<div class="layoutArea">
<div class="column">
<p><span style="font-size: 10.000000pt; font-family: 'CenturyGothic'">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></p>
<p><span style="font-size: 10.000000pt; font-family: 'CenturyGothic'"><br>
</span></p>
<p></p>
<div class="page" title="Page 17">
<div class="layoutArea">
<div class="column">
<ol>
<li style="font-size: 10.000000pt; font-family: 'CenturyGothic'">
<p><span style="font-size: 10.000000pt; font-family: 'CenturyGothic'">An application for any string that is a representation, in any language, of the
</span><span style="font-size: 10.000000pt; font-family: 'CenturyGothic'; font-style: italic">capital city name
</span><span style="font-size: 10.000000pt; font-family: 'CenturyGothic'">of any country or territory listed in the ISO 3166-1 standard.
</span></p>
</li><li style="font-size: 10.000000pt; font-family: 'CenturyGothic'">
<p><span style="font-size: 10.000000pt; font-family: 'CenturyGothic'">An application for a
</span><span style="font-size: 10.000000pt; font-family: 'CenturyGothic'; font-style: italic">city name</span><span style="font-size: 10.000000pt; font-family: 'CenturyGothic'">, where the applicant declares that it intends to use the gTLD for purposes associated
with the city name. </span></p>
</li></ol>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<div style="font-size: 14px; font-family: 'Comic Sans MS', sans-serif;"><br>
</div>
<div style="font-size: 14px; font-family: 'Comic Sans MS', sans-serif;">I read your input in such way that you think that the same rules could be applied for 3-letter codes? You even seem to imply that the respective ccTLD operator should have a say.</div>
<div style="font-size: 14px; font-family: 'Comic Sans MS', sans-serif;"><br>
</div>
<div style="font-size: 14px; font-family: 'Comic Sans MS', sans-serif;">I have a few questions regarding how you think that ISO 3166-3 letter codes should be applied in the future. I see that your plan is to establish them as 3-letter gTLDs. At the same time
you write that they will be marketed as alternative to the corresponding ccTLD.</div>
<div style="font-size: 14px; font-family: 'Comic Sans MS', sans-serif;">The will mean that a country will have one 2-letter code following local rules and local law and another 3-letter code following global law, read ICANN rules. Don’t you think that this
might lead to confusion for the user? </div>
<div style="font-size: 14px; font-family: 'Comic Sans MS', sans-serif;"><br>
</div>
<div style="font-size: 14px; font-family: 'Comic Sans MS', sans-serif;">If you take a look at my comments to the “Straw Man (Woman) Paper on 3-letter codes” you will see that I have serious doubts about the practicality of the “Starting point for Possible Framework”.
It would be useful if you could go through the document and comment directly there as well as your interesting thoughts in this mail exchange.</div>
<div style="font-size: 14px; font-family: 'Comic Sans MS', sans-serif;"><br>
</div>
<div style="font-size: 14px; font-family: 'Comic Sans MS', sans-serif;">As you also see from the comments from Panos, I think it is unthinkable to avoid political interest from governments in this question. As he says, a government’s duty is to serve public
interest first. </div>
<div style="font-size: 14px; font-family: 'Comic Sans MS', sans-serif;"><br>
</div>
<div style="font-size: 14px; font-family: 'Comic Sans MS', sans-serif;">Kind regards,</div>
<div style="font-size: 14px; font-family: 'Comic Sans MS', sans-serif;"><br>
</div>
<div>
<div style="font-size: 14px; font-family: 'Comic Sans MS', sans-serif;"><i>Annebeth</i></div>
<div style="font-size: 14px; font-family: 'Comic Sans MS', sans-serif;"><i><br>
</i></div>
<div>
<div>
<div style="font-size: 14px; font-family: 'Comic Sans MS', sans-serif;"><br>
</div>
<div>
<div>
<p class="MsoNormal"><font face="Comic Sans MS" size="2"><b><i><span style="color: rgb(40, 65, 187);">Annebeth B. Lange</span></i></b><o:p></o:p></font></p>
</div>
<div>
<p class="MsoNormal"><font face="Comic Sans MS" size="2"><i>Special Adviser International Policy</i><o:p></o:p></font></p>
</div>
<div>
<p class="MsoNormal"><font face="Comic Sans MS" size="2"><i>UNINETT Norid AS</i><o:p></o:p></font></p>
</div>
<div>
<p class="MsoNormal"><i><font face="Comic Sans MS" size="2">P.O.Box 6979 St. Olavs plass</font></i></p>
<p class="MsoNormal"><i><font face="Comic Sans MS" size="2">NO-0130 Oslo</font></i></p>
<p class="MsoNormal"><i><font face="Comic Sans MS" size="2"><br>
</font></i></p>
</div>
<div>
<p class="MsoNormal"><font face="Comic Sans MS" size="2"><i><a href="mailto:annebeth.lange@uninett.no">annebeth.lange@uninett.no</a> </i><o:p></o:p></font></p>
</div>
<div>
<p class="MsoNormal"><i><font face="Comic Sans MS" size="2">Mobile: +47 959 11 559</font></i></p>
</div>
</div>
<font size="2"><br>
</font></div>
</div>
<div style="font-size: 14px; font-family: 'Comic Sans MS', sans-serif;"><br>
</div>
</div>
</div>
<div style="font-size: 14px; font-family: 'Comic Sans MS', sans-serif;"><br>
</div>
<span id="OLK_SRC_BODY_SECTION" style="font-size: 14px; font-family: 'Comic Sans MS', sans-serif;">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span><<a href="mailto:ctn-crosscom-bounces@icann.org">ctn-crosscom-bounces@icann.org</a>> on behalf of Alexander Schubert <<a href="mailto:alexander@schubert.berlin">alexander@schubert.berlin</a>><br>
<span style="font-weight:bold">Reply-To: </span>"<a href="mailto:alexander@schubert.berlin">alexander@schubert.berlin</a>" <<a href="mailto:alexander@schubert.berlin">alexander@schubert.berlin</a>><br>
<span style="font-weight:bold">Date: </span>Monday 25 April 2016 01:12<br>
<span style="font-weight:bold">To: </span>"<a href="mailto:ctn-crosscom@icann.org">ctn-crosscom@icann.org</a>" <<a href="mailto:ctn-crosscom@icann.org">ctn-crosscom@icann.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [Ctn-crosscom] Updated StrawWoman Proposal on 3-character codes<br>
</div>
<div><br>
</div>
<div 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">
<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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
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 90.0pt 72.0pt 90.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:2040474969;
mso-list-type:hybrid;
mso-list-template-ids:-501960656 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.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 lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p><span style="font-size: 10pt; font-family: Arial, sans-serif;">Dear Panos,<o:p></o:p></span></p>
<p><span style="font-size: 10pt; font-family: Arial, sans-serif;">Thanks for your extensive and thoughtful response! You write:<o:p></o:p></span></p>
<p style="margin-left:36.0pt"><b><i><span style="font-size: 10pt; font-family: Arial, sans-serif; color: rgb(31, 78, 121);">Your case is interesting, but from your words is already implied that it's an ”edge case".<o:p></o:p></span></i></b></p>
<p class="MsoNormal"><span style="font-size: 10pt; font-family: Arial, sans-serif;">Well. “.berlin” in 2005 was perceived as “edge case” as well – now we have already 35 city gTLD’s and in the 2nd round some several hundred will follow. We actually had to lobby
A LOT to convince the relevant ICANN circles that city-TLD’s aren’t the end of the world.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 10pt; font-family: Arial, sans-serif;"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 10pt; font-family: Arial, sans-serif;">I just do not understand why we want to DENY Governments to create a certain TLD if they choose to. Why we would DENY a cTLD registry to market a TLD for WHATEVER purpose –
would they chose to. To protect whom? That Government and this ccTLD operator? We protect them from themselves? We can create whatever rule we want – Governments and ccTLD operators should have the power to overrule them if THEY WANT.<br>
<br>
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 10pt; font-family: Arial, sans-serif;">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 10pt; font-family: Arial, sans-serif;"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 10pt; font-family: Arial, sans-serif;">Alexander.berlin<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif;"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif;"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif;"><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 style="font-size: 11pt; font-family: Calibri, sans-serif;">From:</span></b><span style="font-size: 11pt; font-family: Calibri, sans-serif;">
<a href="mailto:ctn-crosscom-bounces@icann.org">ctn-crosscom-bounces@icann.org</a> [<a href="mailto:ctn-crosscom-bounces@icann.org">mailto:ctn-crosscom-bounces@icann.org</a>]
<b>On Behalf Of </b>Panagiotis Papaspiliopoulos<br>
<b>Sent:</b> Sunday, April 24, 2016 1:47 AM<br>
<b>To:</b> <a href="mailto:ctn-crosscom@icann.org">ctn-crosscom@icann.org</a><br>
<b>Subject:</b> Re: [Ctn-crosscom] Updated StrawWoman Proposal on 3-character codes<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p>Dear Alexander,<o:p></o:p></p>
<p>Your case is interesting, but from your words is already implied that it's an "edge case". However, generally speaking, I believe that a PDP should guarantee that we have a stable and at the same time fertile environment that, at the same time, will prevent
the creation of problems as much as possible. So, I think the safest solution is to have the ISO list protected and an Early Warning System activated.<o:p></o:p></p>
<p>Let me give you an example:<o:p></o:p></p>
<p>1. Greece has two ccTLDs: .gr (Latin, i.e. the ISO3166-1 alpha-2 code) and .ελ (IDN - live hopefully soon). Both of them are run by the same Registry in order to have policies implemented to avoid confusability issues, as well as trademark issues.<o:p></o:p></p>
<p>2. Someone is asking for .GRC (i.e. the ISO3166-1 alpha-3 code) for a new ccTLD. He has to have a letter of support from the Greek government. Let's think... who is this guy? <o:p></o:p></p>
<p> 2.1 Is the applicant someone that is a total stranger to the Greek government? Yes -> do we like him? If no, end of story / if yes -> so, we give him a letter of support. We can also be proud that we are in favour of the competition in the ccTLD market
of Greece! We also take money for selling a "licence" to a new company that wants to operate in the Greek domain market! But it is also our duty to protect citizens and businesses from any kind of confusion. Do we really want to create customers just by registering
their brand names and trademarks to another TLD? Too much mess, too much noise, not stable environment, too many complaints, too difficult to draw back...<o:p></o:p></p>
<p> 2.2 Is the applicant someone that is a total stranger to the Greek government? No -> so, it has taken government's support from the very beginning. That means that the government has taken into consideration all the above. It also adds a third ccTLD
in the Greek domain market and creates even more competition! Is the government ready to take this risk? What is there to gain apart from an amount of money for selling a "licence" to another company operating in the Greek domain name market? However, this
market is not at all similar to the mobile operators' market and, surely, the profit limit is in a different (much lower) level than the one in mobile operator's market, while the cons are too many, as described in 2.1 before...<o:p></o:p></p>
<p>3. Someone is asking for .GRC (i.e. the ISO3166-1 alpha-3 code) for a new gTLD. He doesn't need a letter of support because it's not a ccTLD, but... oops! this ISO code has been assigned to Greece! It's good that we have the Early Warning System to notify
us! Even if we say that in the previous occasion (i.e. .GRC as a new ccTLD) the Greek government would take some money for selling a new "licence", in this case (Alexander's "edge case") there is no profit for the government at all, while, at the same time,
it is government's duty to protect the interest of the local community and to do everything possible to avoid at least user confusion. And, above all, who is this guy that will use a 3-letter code that indicates Greece? Is a good guy or a bad guy? And what
if now it's a good guy, but in the future will sell .GRC to a bad guy for any reason? No, not at all, this is a kind of risk that no government will ever take! Can you imagine .USA run by a north-korean company as a gTLD? I cannot! <o:p></o:p></p>
<p>4.1 Someone is asking for .GRE (or .ELL) for a new ccTLD -> he needs a letter of support form the Greek government. Go to No.2 :)<o:p></o:p></p>
<p>4.2 Someone is asking for .GRE (or .ELL) for a new gTLD -> he doesn't legally need a letter of support, BUT, unfortunately, this 3-letter code has been used globally in order to indicate Greek athletes and even the Greek National Team in almost every sport!
Again, thanks God that we have the Early Warning System to notify us! If for any reason we are convinced that .ELL (for example) can be used without causing user confusion or any other problem, then we might come into some kind of agreement with the applicant.
But we are clear from the begining: a government's duty is to serve public interest first!<o:p></o:p></p>
<p>5.1 Someone is asking for .HELLAS (transliteration of the name of the country from the Greek) for a new ccTLD -> he needs a letter of support form the Greek government. Go to No.2 :)<o:p></o:p></p>
<p>5.2 Someone is asking for .HELLAS for a new gTLD -> Can he easily take it, because it's a larger-than-3-character string? -> Again, thanks God that we have the Early Warning System to notify us! Depending the string, we may or may not come into some negotiations
with the applicant, but, as mentioned before, a government's duty is to serve public interest first!<o:p></o:p></p>
<p>Finally, I would like to wish to all of our colleagues Happy Easter (the Greek-Orthodox Easter is on 1st May)! For this reason I'm taking some days off and I will be happy to discuss further with you during our conference call.<o:p></o:p></p>
<p>Best regards,<o:p></o:p></p>
<p>Panos<o:p></o:p></p>
<p>PS. Lars, can you please confirm the acceptance of the email? Thank you in advance!<o:p></o:p></p>
<p>---<o:p></o:p></p>
<div>
<pre>Panagiotis Papaspiliopoulos<o:p></o:p></pre>
<pre>Accredited Representative of Greece to the GAC of ICANN<o:p></o:p></pre>
<pre>Senior Policy Advisor - Telecommunications Expert<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Hellenic Ministry of Infrastructure, Transport & Networks<o:p></o:p></pre>
<pre>General Secretariat of Telecommunications & Post<o:p></o:p></pre>
<pre>General Directorate of Telecommunications & Post<o:p></o:p></pre>
<pre>tel: +30 210 650 8538<o:p></o:p></pre>
<pre>fax: +30 210 650 8533<o:p></o:p></pre>
<pre>email: p.papaspil[at]yme.gov.gr<o:p></o:p></pre>
</div>
<p>On 23/04/2016 21:40, Carlos Raúl Gutiérrez G. wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #1010FF 1.5pt;padding:0cm 0cm 0cm 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-bottom:5.0pt">
<pre>Dear Alexander<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>my comments inline and welcome to participate actively in the group!!!!<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Carlos Raúl Gutiérrez<o:p></o:p></pre>
<pre>+506 8837 7176<o:p></o:p></pre>
<pre>Skype: carlos.raulg<o:p></o:p></pre>
<pre>Current UTC offset: -6.00 (Costa Rica)<o:p></o:p></pre>
<pre>On 23 Apr 2016, at 12:06, Alexander Schubert wrote:<o:p></o:p></pre>
<blockquote style="border:none;border-left:solid #1010FF 1.5pt;padding:0cm 0cm 0cm 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Dear All, I have been following this group for quite some while but remained obviously silent. I have been engaged in geo-gTLD’s since November 2004; when Dirk and me started “.berlin”. I have also founded an applicant that went for a three
letter new gTLD (the community applicant for .gay). I am planning to create a true community multi stakeholder applicant for a three letter gTLD based on an ISO 3166 III code in the 2nd round;<o:p></o:p></p>
</blockquote>
<pre>In that case I strongly encourage you to support a definitive <o:p></o:p></pre>
<pre>pdp-process on the use of country and territory names based on ISO that <o:p></o:p></pre>
<pre>may or may not support your idea but make it mandatory for any <o:p></o:p></pre>
<pre>subsequent round. So far this is only a CWG exercise, and the draft text <o:p></o:p></pre>
<pre>shows that for the time being it is not possible to preclude any of the <o:p></o:p></pre>
<pre>ideas submitted so far to the Team about using 3-letter codes or not, <o:p></o:p></pre>
<pre>because we are far from any consensus (other that developing a true <o:p></o:p></pre>
<pre>policy process from my personal perspective).<o:p></o:p></pre>
<blockquote style="border:none;border-left:solid #1010FF 1.5pt;padding:0cm 0cm 0cm 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">and write here in that capacity. Reading your thoughts I can say that that string: * WILL be marketed as alternative to the corresponding ccTLD! And there is absolutely ZERO reason to deny<o:p></o:p></p>
</blockquote>
<pre>Who would deny?<o:p></o:p></pre>
<blockquote style="border:none;border-left:solid #1010FF 1.5pt;padding:0cm 0cm 0cm 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">such use, if: o The respective ccTLD operator is the RSP for the new string and<o:p></o:p></p>
</blockquote>
<pre>the previous ccNSO working group could have come to that conclusion, but <o:p></o:p></pre>
<pre>to the best of my knowledge they didn´t.<o:p></o:p></pre>
<blockquote style="border:none;border-left:solid #1010FF 1.5pt;padding:0cm 0cm 0cm 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">o Hence agrees into creating its own “competition”<o:p></o:p></p>
</blockquote>
<pre>The Swiss authorities did it to some degree by not allowing .ch to run <o:p></o:p></pre>
<pre>.swiss, but that was their own innovation without the need of any new <o:p></o:p></pre>
<pre>policy and .swiss is longer than 3 letters……..sometimes the DNS is <o:p></o:p></pre>
<pre>also about innovation.<o:p></o:p></pre>
<blockquote style="border:none;border-left:solid #1010FF 1.5pt;padding:0cm 0cm 0cm 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">o The relevant Government authorities agree in such usage as well<o:p></o:p></p>
</blockquote>
<pre>which relevant Gov Auth.??<o:p></o:p></pre>
<blockquote style="border:none;border-left:solid #1010FF 1.5pt;padding:0cm 0cm 0cm 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">I think the litmus test is: What if a nation WANTS another TLD?<o:p></o:p></p>
</blockquote>
<pre>another TLD or another ccTLD?<o:p></o:p></pre>
<blockquote style="border:none;border-left:solid #1010FF 1.5pt;padding:0cm 0cm 0cm 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">What if UK said they want .eng Domains (no, I am not building a .eng) – and they WANT them in direct competition with .uk?<o:p></o:p></p>
</blockquote>
<pre>not sure if eng is a 3 letter code under ISO………<o:p></o:p></pre>
<blockquote style="border:none;border-left:solid #1010FF 1.5pt;padding:0cm 0cm 0cm 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Who are we to deny them their wish?<o:p></o:p></p>
</blockquote>
<pre>So far, only the applicants guidebook of the last round<o:p></o:p></pre>
<blockquote style="border:none;border-left:solid #1010FF 1.5pt;padding:0cm 0cm 0cm 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Why not simply assigning the same principles as for geo-TLD’s: If the relevant Government authorities agree – then obviously they want it. Why would we DENY them that string? Same with the ccTLD competition: If the ccTLD operator is in
agreement (e.g. because they are the RSP for the new string or for whatever other reason) why not allowing them to market it as “competition”?<o:p></o:p></p>
</blockquote>
<pre>nice idea for the ccNSO<o:p></o:p></pre>
<blockquote style="border:none;border-left:solid #1010FF 1.5pt;padding:0cm 0cm 0cm 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Would a double opt-in by Government AND the ccTLD operator ease the concerns?<o:p></o:p></p>
</blockquote>
<pre>possible, if the local jurisdiction make such a deal possible. But <o:p></o:p></pre>
<pre>again, outside the realm of ICANN<o:p></o:p></pre>
<blockquote style="border:none;border-left:solid #1010FF 1.5pt;padding:0cm 0cm 0cm 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Does the GAC even REALIZE that the “perceived protection” amounts to restriction in the end?<o:p></o:p></p>
</blockquote>
<pre>GAC has its own WG on Geographic names. You could ask them<o:p></o:p></pre>
<blockquote style="border:none;border-left:solid #1010FF 1.5pt;padding:0cm 0cm 0cm 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Sincerely yours,<o:p></o:p></p>
</blockquote>
<pre>Recommended reading on the previous work by the ccNSO<o:p></o:p></pre>
<pre><a href="http://ccnso.icann.org/workinggroups/unct-framework-charter-27mar14-en.pdf">http://ccnso.icann.org/workinggroups/unct-framework-charter-27mar14-en.pdf</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><a href="http://ccnso.icann.org/workinggroups/ccwg-ctn-progress-23sep14-en.pdf">http://ccnso.icann.org/workinggroups/ccwg-ctn-progress-23sep14-en.pdf</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Recommended reading on the objectives of this ccNSO-GNSO CWgroup<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><a href="https://community.icann.org/pages/viewpage.action?pageId=48346463">https://community.icann.org/pages/viewpage.action?pageId=48346463</a><o:p></o:p></pre>
<blockquote style="border:none;border-left:solid #1010FF 1.5pt;padding:0cm 0cm 0cm 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Alexander.berlin<o:p></o:p></p>
</blockquote>
<pre>Cheers<o:p></o:p></pre>
<pre>Carlos Raul Gutierrez<o:p></o:p></pre>
<blockquote style="border:none;border-left:solid #1010FF 1.5pt;padding:0cm 0cm 0cm 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">From: <a href="mailto:ctn-crosscom-bounces@icann.org">ctn-crosscom-bounces@icann.org</a> [mailto:<a href="mailto:ctn-crosscom-bounces@icann.org">ctn-crosscom-bounces@icann.org</a>] On Behalf Of Lars Hoffmann Sent: Saturday, April 23, 2016
5:32 PM To: <a href="mailto:ctn-crosscom@icann.org">ctn-crosscom@icann.org</a> Subject: [Ctn-crosscom] FW: Updated StrawWoman Proposal on 3-character codes Der all, Here is Colin’s document for those who did not receive it. Best. Lars From: Colin O'Brien <<a href="mailto:colin@PartridgePartnersPC.com">colin@PartridgePartnersPC.com</a>
<mailto:<a href="mailto:colin@PartridgePartnersPC.com">colin@PartridgePartnersPC.com</a>> > Date: Thursday 21 April 2016 at 14:19 To: Lars HOFFMANN <<a href="mailto:lars.hoffmann@icann.org">lars.hoffmann@icann.org</a> <mailto:<a href="mailto:lars.hoffmann@icann.org">lars.hoffmann@icann.org</a>>
>, "<a href="mailto:ctn-crosscom@icann.org">ctn-crosscom@icann.org</a> <mailto:<a href="mailto:ctn-crosscom@icann.org">ctn-crosscom@icann.org</a>> " <<a href="mailto:ctn-crosscom@icann.org">ctn-crosscom@icann.org</a> <mailto:<a href="mailto:ctn-crosscom@icann.org">ctn-crosscom@icann.org</a>>
> Subject: RE: Updated StrawWoman Proposal on 3-character codes Hello Lars, Please find attached my comments and edits. Cordially, Colin From:
<a href="mailto:ctn-crosscom-bounces@icann.org">ctn-crosscom-bounces@icann.org</a> <mailto:<a href="mailto:ctn-crosscom-bounces@icann.org">ctn-crosscom-bounces@icann.org</a>> [mailto:<a href="mailto:ctn-crosscom-bounces@icann.org">ctn-crosscom-bounces@icann.org</a>]
On Behalf Of Lars Hoffmann Sent: Thursday, April 14, 2016 1:35 PM To: <a href="mailto:ctn-crosscom@icann.org">
ctn-crosscom@icann.org</a> <mailto:<a href="mailto:ctn-crosscom@icann.org">ctn-crosscom@icann.org</a>> Subject: [Ctn-crosscom] Updated StrawWoman Proposal on 3-character codes Dear all, Please find attached the updated version of the StrawWoman on 30-chacter
codes. The document contains redlined comments from Annebeth, Panos, Ørnulf, and Jaap. If you have any comments please use the attached documents and add them via track-changes and submit back to the list or forward just to me. I will collate all comments
and redistribute a master document prior to our next call. Speaking of … due to scheduling issues, the co-Chairs have decided to move the next call to Monday 2 May 2016, time TBD. Best wishes, Lars ______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service. For more information please visit
<a href="http://www.symanteccloud.com">http://www.symanteccloud.com</a> ______________________________________________________________________ ______________________________________________________________________ This email has been scanned by the Symantec
Email Security.cloud service. For more information please visit <a href="http://www.symanteccloud.com">
http://www.symanteccloud.com</a> ______________________________________________________________________ _______________________________________________ Ctn-crosscom mailing list
<a href="mailto:Ctn-crosscom@icann.org">Ctn-crosscom@icann.org</a> <a href="https://mm.icann.org/mailman/listinfo/ctn-crosscom">
https://mm.icann.org/mailman/listinfo/ctn-crosscom</a><o:p></o:p></p>
</blockquote>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Ctn-crosscom mailing list<o:p></o:p></pre>
<pre><a href="mailto:Ctn-crosscom@icann.org">Ctn-crosscom@icann.org</a><o:p></o:p></pre>
<pre><a href="https://mm.icann.org/mailman/listinfo/ctn-crosscom">https://mm.icann.org/mailman/listinfo/ctn-crosscom</a><o:p></o:p></pre>
</blockquote>
</div>
</div>
</div>
</span>
</body>
</html>