<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:"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:Garamond;
panose-1:2 2 4 4 3 3 1 1 8 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></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 bgcolor="white" lang="EN-NZ" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:windowtext;mso-fareast-language:EN-US">The ccNSO is a membership body of ccTLDs. The gNSO has a variety of participants – including registries – but not generally ccTLDs.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext;mso-fareast-language:EN-US">D<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="color:windowtext">From:</span></b><span lang="EN-US" style="color:windowtext"> UA-discuss <ua-discuss-bounces@icann.org>
<b>On Behalf Of </b>Asmus Freytag<br>
<b>Sent:</b> Sunday, 12 May 2019 8:58 AM<br>
<b>To:</b> ua-discuss@icann.org<br>
<b>Subject:</b> Re: [UA-discuss] GNSO requested deferral of IDN Guidelines 4.0 Vote - CPH / Registrants impact<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Delaying the IDN Guidelines will just mean more registries will register more "non-standard" labels and make it harder to implement something that's reasonably secure for everyone.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Anytime you change the registration policies for an existing registry, you will have to figure out how to grandfather existing, delegated labels (if any).<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">My understanding was that the guidelines were intended primarily for newly established registries, but I'd love to find out whether this understanding is wrong for some reason.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">The GNSO represents the "ccTLDs" and they would just love to continue with "innovations" like emoji domain names. I would love to see some concrete cases of existing registrations for ccTLDs that are reasonable labels that would be impacted.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Anyone know?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">A./<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">On 5/10/2019 2:31 PM, Roberto Gaetano wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Hi all. <o:p></o:p></p>
<div>
<p class="MsoNormal">This email from Jothan makes a good point about the impact caused by changing the standard about managing variants.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">I was wondering whether we have a report on how variants are managed by different IDN registries.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Somebody can point me to such a source?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Roberto<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 30.04.2019, at 23:27, Jothan Frakes <<a href="mailto:jothan@gmail.com">jothan@gmail.com</a>> wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:18.0pt;font-family:"Garamond",serif">The GNSO just sent a letter to request that the vote on adoption of the IDN Guidelines 4.0 be deferred <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:18.0pt;font-family:"Garamond",serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:18.0pt;font-family:"Garamond",serif">There is some UA pain that will come from these Guidelines we should be completely aware of.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:18.0pt;font-family:"Garamond",serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:18.0pt;font-family:"Garamond",serif">It is important to identify the manner in which standards can impact the contracted parties, such as the Registries and Registrars, but getting even further out the supply chain
into registrants and Internet users, there are some impacts to them as well as their audiences.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:18.0pt;font-family:"Garamond",serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:18.0pt;font-family:"Garamond",serif">If the new standard causes something that was a separate registration to become a variant of another registration, or invalidates an existing registration, this is a bad outcome
for the innovators, developers, and early patrons that supported the internationalization of the namespace.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:18.0pt;font-family:"Garamond",serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:18.0pt;font-family:"Garamond",serif">Part of what the objective of UA is, to my reckoning, is to increase engagement and support of coding projects that will require adoption of standards that may not immediately
hold levels of RoI to them, and they are looking for reasons not to do them.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:18.0pt;font-family:"Garamond",serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:18.0pt;font-family:"Garamond",serif">These new guidelines are good - and needed - they are the result of many people's hard work, time and wisdom, and address many solutions. The approach of pushing these out is
problematic. Further, there seems no recourse for those (even if statistically small) who may be impacted adversely, lose their domain, or have it be invalidated (and thus REVERSE their UA experience)<br>
<br>
There is potential impact to existing TLDs, and most notably to registrants of second level names where there are registrations using former standards that become unsupported or invalidated.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:18.0pt;font-family:"Garamond",serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:18.0pt;font-family:"Garamond",serif">A very important challenge we face with the UA effort is inspiring developers to implement IDN and EAI as we help globalize the Internet through our work.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:18.0pt;font-family:"Garamond",serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:18.0pt;font-family:"Garamond",serif">IF the approach on standards will be to invalidate some portion of the community of registrations like this, there must be attention to how this impacts existing innovators. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:18.0pt;font-family:"Garamond",serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:18.0pt;font-family:"Garamond",serif">Innovators worked to drive the standards and increase awareness - and the invalidation or deprecation of a registration that someone has carried for a number of years (some are
15+ years) is the precise opposite of a reward for early support, and it is going to send a very loud message to developers.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:18.0pt;font-family:"Garamond",serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:18.0pt;font-family:"Garamond",serif">I believe that further review is needed by registries on the technical impacts of the changes, but any delay can help ICANN and the community address the disenfranchisement factor.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:18.0pt;font-family:"Garamond",serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:18.0pt;font-family:"Garamond",serif">This should be important to UASG - we need developers to embrace the additional effort that they have to invest in their work to consider IDN, EAI and other things.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:18.0pt;font-family:"Garamond",serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:18.0pt;font-family:"Garamond",serif">-Jothan<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:18.0pt;font-family:"Garamond",serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:18.0pt;font-family:"Garamond",serif"><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal">Jothan Frakes<br>
+1.206-355-0230 tel<br>
+1.206-201-6881 fax<o:p></o:p></p>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</blockquote>
<p><o:p> </o:p></p>
</div>
</body>
</html>