<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)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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:0in;
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.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
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:12.0pt;
font-family:"Times New Roman",serif;}
p.msonormal00, li.msonormal00, div.msonormal00
{mso-style-name:msonormal0;
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;}
p.msochpdefault, li.msochpdefault, div.msochpdefault
{mso-style-name:msochpdefault;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:10.0pt;
font-family:"Times New Roman",serif;}
span.emailstyle19
{mso-style-name:emailstyle19;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.emailstyle21
{mso-style-name:emailstyle21;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.apple-tab-span
{mso-style-name:apple-tab-span;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle27
{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:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1505196828;
mso-list-type:hybrid;
mso-list-template-ids:-652587448 135462933 135462937 135462939 135462927 135462937 135462939 135462927 135462937 135462939;}
@list l0:level1
{mso-level-number-format:alpha-upper;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@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:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@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:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@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:0in;}
ul
{margin-bottom:0in;}
--></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-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">That’s great to hear!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;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 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Sebastien Pensis [mailto:Sebastien.Pensis@eurid.eu]
<br>
<b>Sent:</b> Monday, March 13, 2017 6:11 AM<br>
<b>To:</b> Mark Svancarek <marksv@microsoft.com>; Shawn Steele <Shawn.Steele@microsoft.com>; Richard Merdinger <rmerdinger@godaddy.com>; Edmon Chung <edmon@registry.asia><br>
<b>Cc:</b> UA-discuss@icann.org<br>
<b>Subject:</b> RE: [UA-discuss] FW: I-D Action: draft-klensin-idna-rfc5891bis-00.txt<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Dear All,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">If I may, I’d like to add something to follow up on Shawn’s message about character confusion. At EURid, the .eu registry, we implemented IDNA2008 in early 2015
and did notice to possibility of user confusion with homoglyphs such as ü = ue or ß = ss. We therefore decided to offer homoglyph bundling.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">This entails:<o:p></o:p></span></p>
<ol style="margin-top:0in" start="1" type="A">
<li class="MsoListParagraphCxSpFirst" style="color:#1F497D;margin-left:0in;mso-add-space:auto;mso-list:l0 level1 lfo2">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Visually similar characters across different scripts are bundled.<o:p></o:p></span>
<ol style="margin-top:0in" start="1" type="a">
<li class="MsoListParagraphCxSpMiddle" style="color:#1F497D;margin-left:0in;mso-add-space:auto;mso-list:l0 level2 lfo2">
<span lang="FR-BE" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Latin e versus Cyrillic
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">е</span><span lang="FR-BE" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li><li class="MsoListParagraphCxSpLast" style="color:#1F497D;margin-left:0in;mso-add-space:auto;mso-list:l0 level2 lfo2">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Latin a versus Greek α (uppercase)<o:p></o:p></span></li></ol>
</li></ol>
<p class="MsoNormal" style="margin-left:35.4pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">There are exceptions to this rule. Below you will be able to find a non-exhaustive list. (More detailed information can be found on
our site):<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:35.4pt;text-indent:35.4pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Latin ß and Latin ss,<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:70.8pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Latin ss and Greek β: these are characters from 2 different scripts, which are not visually similar, Greek ς and Greek σ, Greek α and
Greek ἀ ἁ ἂ ἃ ἄ ἅ and Greek ᾀ ᾁ ᾂ ᾃ ᾄ ᾅ and Greek αi and Greek ἀi ἁi ἂi ἃi ἄi ἅi.<o:p></o:p></span></p>
<ol style="margin-top:0in" start="2" type="A">
<li class="MsoListParagraph" style="color:#1F497D;margin-left:0in;mso-add-space:auto;mso-list:l0 level1 lfo2">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">B) If one domain name in a homoglyph bundle exists, none of the other domain names in that bundle can be registered. The word “exists” should be interpreted in the previous sentence as having either
one of the following .eu domain name statuses: in use, registered (on hold, suspended, seized), withdrawn, quarantine. When querying a domain name that is in a bundle via the WHOIS, it will return the status “homoglyph blocked”.<o:p></o:p></span></li></ol>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">This application on the registry-side allows for a reduction in the risks of user confusion, and takes into account the characters in various scripts which are
read in a similar manner. Of course this becomes more complicated as the quantity of languages in play increases, but I think this is one way to address the concerns Shawn raised.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><br>
More info one this is available on EURid site here: <a href="https://eurid.eu/en/register-a-eu-domain/domain-names-with-special-characters-idns/">
https://eurid.eu/en/register-a-eu-domain/domain-names-with-special-characters-idns/</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Sincerely,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Sebastien<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">
<a href="mailto:ua-discuss-bounces@icann.org">ua-discuss-bounces@icann.org</a> [<a href="mailto:ua-discuss-bounces@icann.org">mailto:ua-discuss-bounces@icann.org</a>]
<b>On Behalf Of </b>Mark Svancarek via UA-discuss<br>
<b>Sent:</b> maandag 13 maart 2017 13:15<br>
<b>To:</b> Shawn Steele <<a href="mailto:Shawn.Steele@microsoft.com">Shawn.Steele@microsoft.com</a>>; Richard Merdinger <<a href="mailto:rmerdinger@godaddy.com">rmerdinger@godaddy.com</a>>; Edmon Chung <<a href="mailto:edmon@registry.asia">edmon@registry.asia</a>>;
<a href="mailto:UA-discuss@icann.org">UA-discuss@icann.org</a><br>
<b>Subject:</b> Re: [UA-discuss] FW: I-D Action: draft-klensin-idna-rfc5891bis-00.txt<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="NL-BE"><o:p> </o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">At igf this year John basically argued that no one should use EAI because it's confusing for non-ascii users, and people in other zones might as well just get on the bus and
use ascii for their email addresses, too. It was odd, though educational.<br>
<br>
So I am not especially surprised to see John proposing more restrictions.<br>
<br>
Sent from my Windows Phone<o:p></o:p></span></p>
</div>
</div>
<div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="3" width="100%" align="center">
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:
</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><a href="mailto:Shawn.Steele@microsoft.com">Shawn Steele</a></span><br>
<b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Sent: </span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">3/12/2017 7:33 PM</span><br>
<b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">To: </span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><a href="mailto:rmerdinger@godaddy.com">Richard Merdinger</a>;
<a href="mailto:edmon@registry.asia">Edmon Chung</a>; <a href="mailto:marksv@microsoft.com">
Mark Svancarek</a>; <a href="mailto:UA-discuss@icann.org">UA-discuss@icann.org</a></span><br>
<b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Subject: </span>
</b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">RE: [UA-discuss] FW: I-D Action: draft-klensin-idna-rfc5891bis-00.txt</span><o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">My concern is John’s emphasis on creating very restrictive character rule sets.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The most restrictive rules created by IDNA2008 have been ignored because of user demand and backwards compatibility. Eg: no-emoji in labels. People want emoji, but IDNA2008
doesn’t permit it. Part of that is compatibility with the permitted IDNA2003 emoji, however there has also been demand for emoji characters newly added to Unicode.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">I think that it is appropriate to remind registrars that they are responsible for creating sane rules for their spaces, but it is clear that users do not want to be tied to
the most restrictive demands of IDNA2008. Implementations appear to be settling on the Unicode provided idna data and I would much prefer to see the IETF standards point to the IDNA character sets provided by Unicode (while still encouraging registrars to
do sane things that make sense for their domains).</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">A good example of something a registrar might want to consider could be something like ü. Some spaces may allow ü without much restriction, however for .de, .ch, .at, etc.
it might make sense to recognize that ü has an alternate ue spelling and to provide bundling or blocking of domains like müller.ch and mueller.ch. That kind of rule is very domain/language specific. Though it is not called out as some of the bidi rules are,
the RFCs allow registrars to implement such a policy if it fits their purposes. Of course many other behaviors are called out by the IDNA2008 rules.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Pretty much all of the concerns regarding the character repertoire can be resolved and the registrar level if the registrars would ensure that they did not allow registrations
of multiple domain variations that might confuse their users. Or if they bundled those registrations.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">-Shawn</span><o:p></o:p></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span></a><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Richard Merdinger [<a href="mailto:rmerdinger@godaddy.com">mailto:rmerdinger@godaddy.com</a>]
<br>
<b>Sent:</b> Saturday, March 11, 2017 11:35 PM<br>
<b>To:</b> Edmon Chung <<a href="mailto:edmon@registry.asia">edmon@registry.asia</a>>; Mark Svancarek <<a href="mailto:marksv@microsoft.com">marksv@microsoft.com</a>>;
<a href="mailto:UA-discuss@icann.org">UA-discuss@icann.org</a><br>
<b>Cc:</b> Shawn Steele <<a href="mailto:Shawn.Steele@microsoft.com">Shawn.Steele@microsoft.com</a>><br>
<b>Subject:</b> Re: [UA-discuss] FW: I-D Action: draft-klensin-idna-rfc5891bis-00.txt</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Agree, thanks for forwarding Mark This was a very cogent statement of affairs relative to the closing out of known IDN issues (or our current inability to do so).</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">I agree with Edmon in that I think the UA effort should strive to be a catalyst here.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">--Rich</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-family:"Calibri",sans-serif;color:black">From:
</span></b><span style="font-family:"Calibri",sans-serif;color:black"><<a href="mailto:ua-discuss-bounces@icann.org">ua-discuss-bounces@icann.org</a>> on behalf of Edmon Chung <<a href="mailto:edmon@registry.asia">edmon@registry.asia</a>><br>
<b>Date: </b>Sunday, March 12, 2017 at 7:11 AM<br>
<b>To: </b>'Mark Svancarek' <<a href="mailto:marksv@microsoft.com">marksv@microsoft.com</a>>, "<a href="mailto:UA-discuss@icann.org">UA-discuss@icann.org</a>" <<a href="mailto:UA-discuss@icann.org">UA-discuss@icann.org</a>><br>
<b>Cc: </b>'Shawn Steele' <<a href="mailto:Shawn.Steele@microsoft.com">Shawn.Steele@microsoft.com</a>><br>
<b>Subject: </b>Re: [UA-discuss] FW: I-D Action: draft-klensin-idna-rfc5891bis-00.txt</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Thanks for forwarding this Mark,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">This seems to be something useful for UA, perhaps we should work with the IDN team at ICANN (along with the communities networked from the LGR work) to see where we can best support.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Edmon<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0in 0in 0in 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt" id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<p class="MsoNormal" style="margin-left:.5in">-----Original Message-----<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">From: <a href="mailto:ua-discuss-bounces@icann.org">
ua-discuss-bounces@icann.org</a> [<a href="mailto:ua-discuss-bounces@icann.org">mailto:ua-discuss-bounces@icann.org</a>] On<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Behalf Of Mark Svancarek via UA-discuss<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Sent: Sunday, 12 March 2017 12:58 PM<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">To: <a href="mailto:UA-discuss@icann.org">
UA-discuss@icann.org</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Cc: Shawn Steele <<a href="mailto:Shawn.Steele@microsoft.com">Shawn.Steele@microsoft.com</a>><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Subject: [UA-discuss] FW: I-D Action: draft-klensin-idna-rfc5891bis-00.txt<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">FYI, too much stuff from John for me to dig into this a.m.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">-----Original Message-----<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">From: Idna-update [<a href="mailto:idna-update-bounces@alvestrand.no">mailto:idna-update-bounces@alvestrand.no</a>] On Behalf Of John<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">C Klensin<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Sent: Saturday, March 11, 2017 8:25 AM<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">To: <a href="mailto:idna-update@alvestrand.no">
idna-update@alvestrand.no</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Subject: FWD: I-D Action: draft-klensin-idna-rfc5891bis-00.txt<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Hi.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">For the information of those who may be watching this list but not the IETF<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">announcement one...<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Asmus Freytag and I have started to put together a draft that addresses a problem<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">with the IDNA2008 specs, specifically that we failed to make the responsibility of<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">registries to define code point and label acceptability rules that were considerably<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">more narrow (and better understood by them) than the full set of labels allowed by<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">RFC 5891-5893. It doesn't actually change anything because that requirement is in<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">the existing specs; it just makes (or tries to make) the requirements painfully clear to<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">those who have been missing or misreading them.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">It also provides an explicit link between IDNA2008 requirements and ICANN work on<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">repertoires and label generation rules without endorsing that work as more than one<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">thoughtful approach that might be examined for either reference or inspiration.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Comments (obviously) welcome.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">For anyone who might wonder, this document avoids the more controversial<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">IDNA2008 issues including:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">* Multiple suggestions that we should add emoji, a subset of code points with<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">General Category "So", to the list of code<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">points allowed by IDNA. There are many reasons to not do that<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">but it seems clear that, at some point, the IETF will need to either document those<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">reasons or make the change. Volunteers to put together or work on a document<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">would be welcome.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">* The non-decomposing code point problem, formerly (and<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">incorrectly) known as the Hamza problem. There has been no<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">discernable activity on this since the IAB Statement and LUCID BOF almost exactly<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">two years ago. I've further updated the working copy of draft-klensin-idna-5892upd-<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">unicode70 to cover additional cases and issues, but, in part because it is clearly<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">inappropriate for a quick-patch individual submission, have been advised to not post<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">it until we have a plan to make progress.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">So far, there is no such plan.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">* The (IMO, growing) problem of multiple and inconsistent specifications for IDNs<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">and IDN handling, with different ones being used in different higher-level protocols<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">and areas of the Internet. The use of different specifications and definitions creates<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">opportunities for user and implementer confusion, interoperability difficulties, domain<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">names that cannot be resolved under some circumstances, and various sorts of<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">attacks.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">The specifications involved include IDNA2008, IDNA2003, assorted local "updates"<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">to IDNA2003 that use versions of Stringprep locally updated to assorted versions of<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Unicode, and the various versions of UTR#46. The latest version of the latter<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">explicitly<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">allows emoji along with other symbols. A few months ago, I<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">suggested to the IAB I18N program that a document be produced that at least<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">pointed out the problems associated with multiple divergent specifications, but the<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">idea got no traction.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">It appears to me that, although almost everyone agrees that IDNs, and well- and<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">clearly-functional IDNs, are important, virtually no one is willing to do the hard work,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">at least unless they are being supported by ICANN (disclosure: I am not) or<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">organizations whose interests lie in selling names, preferably as many of them as<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">possible (I have no support from any of them either). Until and unless that changes,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">I don't see much prospect for getting those other issues addressed in a way that<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">might lead to consensus documents.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> john<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">---------- Forwarded Message ----------<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Date: Saturday, March 11, 2017 07:22 -0800<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">From: <a href="mailto:internet-drafts@ietf.org">
internet-drafts@ietf.org</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">To: <a href="mailto:i-d-announce@ietf.org">
i-d-announce@ietf.org</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Subject: I-D Action: draft-klensin-idna-rfc5891bis-00.txt<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">A New Internet-Draft is available from the on-line Internet-Drafts directories.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> Title : Internationalized Domain Names in<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Applications (IDNA): Registry Restrictions and Recommendations<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Authors : John C Klensin<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> Asmus Freytag<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span class="apple-tab-span">
</span>Filename : draft-klensin-idna-rfc5891bis-00.txt<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span class="apple-tab-span">
</span>Pages : 10<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span class="apple-tab-span">
</span>Date : 2017-03-11<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Abstract:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> The IDNA specifications for internationalized domain names<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">combine rules that determine the labels that are allowed in<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">the DNS without violating the protocol itself and an<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">assignment of responsibility, consistent with earlier<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">specifications, for determining the labels that are allowed<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">in particular zones. Conformance to IDNA by registries and<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">other implementations requires both parts. Experience strongly suggests that the<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">language describing those<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">responsibility was insufficiently clear to promote safe and<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">interoperable use of the specifications and that more details<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">and some specific examples would have been helpful. This<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">specification updates the earlier ones to provide that<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">guidance and to correct some technical errors in the descriptions. It does not alter<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">the protocols and rules<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">themselves in any way.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">The IETF datatracker status page for this draft is:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><a href="https://datatracker.ietf.org/doc/draft-klensin-idna-rfc5891bis/">https://datatracker.ietf.org/doc/draft-klensin-idna-rfc5891bis/</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">There's also a htmlized version available at:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><a href="https://tools.ietf.org/html/draft-klensin-idna-rfc5891bis-00">https://tools.ietf.org/html/draft-klensin-idna-rfc5891bis-00</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Please note that it may take a couple of minutes from the time of submission until<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">the htmlized version and diff are available at tools.ietf.org.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Internet-Drafts are also available by anonymous FTP at:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><a href="ftp://ftp.ietf.org/internet-drafts/">ftp://ftp.ietf.org/internet-drafts/</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">_______________________________________________<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">I-D-Announce mailing list<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><a href="mailto:I-D-Announce@ietf.org">I-D-Announce@ietf.org</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><a href="https://www.ietf.org/mailman/listinfo/i-d-announce">https://www.ietf.org/mailman/listinfo/i-d-announce</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Internet-Draft directories: <a href="http://www.ietf.org/shadow.html">
http://www.ietf.org/shadow.html</a> or<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><a href="ftp://ftp.ietf.org/ietf/1shadow-sites.txt">ftp://ftp.ietf.org/ietf/1shadow-sites.txt</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">---------- End Forwarded Message ----------<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">_______________________________________________<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Idna-update mailing list<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><a href="mailto:Idna-update@alvestrand.no">Idna-update@alvestrand.no</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><a href="http://www.alvestrand.no/mailman/listinfo/idna-update">http://www.alvestrand.no/mailman/listinfo/idna-update</a><o:p></o:p></p>
</div>
</blockquote>
<div>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
</div>
</div>
</div>
<p class="MsoNormal"><span lang="NL-BE"><br>
<b>Disclaimer:</b> <o:p></o:p></span></p>
<div>
<p class="MsoNormal"><i><span lang="NL-BE">This email and any attachment hereto is intended solely for the person to which it is addressed and may contain confidential and/or privileged information. If you are not the intended recipient or if you have received
this email in error, please delete it and immediately contact the sender by telephone or email, and destroy any copies of this information. You should not use or copy it, nor disclose its content to any other person or rely upon this information. Please note
that any views presented in the email and any attachment hereto are solely those of the author and do not necessarily represent those of EURid. While all care has been taken to avoid any known viruses, the recipient is advised to check this email and any attachment
for presence of viruses.</span></i><span lang="NL-BE"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="NL-BE">Other languages:<o:p></o:p></span></p>
</div>
<div align="center">
<table class="MsoNormalTable" border="0" cellspacing="1" cellpadding="0" width="500" style="width:375.0pt">
<tbody>
<tr>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal"><a href="http://www.eurid.eu/en/legal-disclaimer">English</a><o:p></o:p></p>
</td>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal"><a href="http://www.eurid.eu/et/legal-disclaimer">Estonian</a><o:p></o:p></p>
</td>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal"><a href="http://www.eurid.eu/it/legal-disclaimer">Italian</a><o:p></o:p></p>
</td>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal"><a href="http://www.eurid.eu/mt/legal-disclaimer">Maltese</a><o:p></o:p></p>
</td>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal"><a href="http://www.eurid.eu/ro/legal-disclaimer">Romanian</a><o:p></o:p></p>
</td>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal"><a href="http://www.eurid.eu/sv/legal-disclaimer">Swedish</a><o:p></o:p></p>
</td>
</tr>
<tr>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal"><a href="http://www.eurid.eu/cs/legal-disclaimer">Czech</a><o:p></o:p></p>
</td>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal"><a href="http://www.eurid.eu/es/legal-disclaimer">Spanish</a><o:p></o:p></p>
</td>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal"><a href="http://www.eurid.eu/lv/legal-disclaimer">Latvian</a><o:p></o:p></p>
</td>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal"><a href="http://www.eurid.eu/nl/legal-disclaimer">Dutch</a><o:p></o:p></p>
</td>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal"><a href="http://www.eurid.eu/sk/legal-disclaimer">Slovak</a><o:p></o:p></p>
</td>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal"><a href="http://www.eurid.eu/el/legal-disclaimer">Greek</a><o:p></o:p></p>
</td>
</tr>
<tr>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal"><a href="http://www.eurid.eu/da/legal-disclaimer">Danish</a><o:p></o:p></p>
</td>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal"><a href="http://www.eurid.eu/fr/legal-disclaimer">French</a><o:p></o:p></p>
</td>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal"><a href="http://www.eurid.eu/lt/legal-disclaimer">Lithuanian</a><o:p></o:p></p>
</td>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal"><a href="http://www.eurid.eu/pl/legal-disclaimer">Polish</a><o:p></o:p></p>
</td>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal"><a href="http://www.eurid.eu/sl/legal-disclaimer">Slovenian</a><o:p></o:p></p>
</td>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal"><a href="http://www.eurid.eu/bg/legal-disclaimer">Bulgarian</a><o:p></o:p></p>
</td>
</tr>
<tr>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal"><a href="http://www.eurid.eu/de/legal-disclaimer">German</a><o:p></o:p></p>
</td>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal"><a href="http://www.eurid.eu/ga/legal-disclaimer">Gaelic</a><o:p></o:p></p>
</td>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal"><a href="http://www.eurid.eu/hu/legal-disclaimer">Hungarian</a><o:p></o:p></p>
</td>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal"><a href="http://www.eurid.eu/pt/legal-disclaimer">Portuguese</a><o:p></o:p></p>
</td>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal"><a href="http://www.eurid.eu/fi/legal-disclaimer">Finnish</a><o:p></o:p></p>
</td>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal"><a href="http://www.eurid.eu/hr/legal-disclaimer">Croatian</a><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
</div>
<p class="MsoNormal"><span lang="NL-BE"> <o:p></o:p></span></p>
</div>
</body>
</html>