<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:"MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
@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:"Microsoft JhengHei";
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"\@Microsoft JhengHei";}
@font-face
{font-family:"\@MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
@font-face
{font-family:"Nirmala UI";
panose-1:2 11 5 2 4 2 4 2 2 3;}
@font-face
{font-family:"Segoe UI Emoji";
panose-1:2 11 5 2 4 2 4 2 2 3;}
/* 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: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:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
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;}
span.m-747807835945705418hoenzb
{mso-style-name:m_-747807835945705418hoenzb;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.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;}
/* List Definitions */
@list l0
{mso-list-id:804154790;
mso-list-template-ids:-2057383814;}
@list l1
{mso-list-id:1490904475;
mso-list-type:hybrid;
mso-list-template-ids:474654180 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l1:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l1:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l1:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l1:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l1:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l1: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]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>Excuse me, I need some clearance on this. <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>For example, I am owner of </span><span lang=SR-LATN-RS style='color:#1F497D'>domain name </span><span style='color:#1F497D'>стојичевић</span><span lang=SR-CYRL-RS style='color:#1F497D'>.срб</span><span lang=SR-LATN-RS style='color:#1F497D'>, and nothing else.<o:p></o:p></span></p><p class=MsoNormal><span lang=SR-LATN-RS style='color:#1F497D'>My primary would be </span><span lang=SR-CYRL-RS style='color:#1F497D'><a href="mailto:душан@стојичевић.срб">душан<span lang=EN-US>@</span>стојичевић.срб</a></span><span lang=SR-LATN-RS style='color:#1F497D'>, and my alias would be <a href="mailto:dusan@stojicevic.rs">dusan<span lang=EN-US>@stojicevic.rs</span></a></span><span style='color:#1F497D'> and it would be pointing to the same mailbox.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Q1> Do I need to be owner of the ascii domain name stojicevic.rs, in order to get ascii alias?<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Q2> If not, how do I get alias, and what I can choose? Just user part?<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Thanks,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Dusan<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><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>From:</b> ua-discuss-bounces@icann.org [mailto:ua-discuss-bounces@icann.org] <b>On Behalf Of </b>Andre Schappo<br><b>Sent:</b> Thursday, February 23, 2017 4:16 PM<br><b>To:</b> ua-discuss <UA-discuss@icann.org><br><b>Subject:</b> Re: [UA-discuss] [ajay.uasg@data.in] [UA-EAI] Revised UASG013 - Quick Guide to EAI<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt'><o:p> </o:p></span></p></div><div><p class=MsoNormal>I have my DataMail account setup using the same method and it works well.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>So I have, <span style='font-family:"MS Gothic"'><a href="mailto:小山@电邮.在线">小山<span style='font-family:"Calibri",sans-serif'>@</span><span style='font-family:"Microsoft JhengHei",sans-serif'>电邮</span><span style='font-family:"Calibri",sans-serif'>.</span>在<span style='font-family:"Microsoft JhengHei",sans-serif'>线</span></a></span> as my primary and the ascii alias <a href="mailto:i18n@datamail.in">i18n@datamail.in</a> as my ascii secondary. Thus the aliasing is on the whole email address.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I consider the local-part should have it's own aliasing. So, taking Ajay's email address, local-part aliasing would give<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><span style='font-family:"Nirmala UI",sans-serif'><a href="mailto:अजय@डाटामेल.भारत">अजय<span style='font-family:"Calibri",sans-serif'>@</span>डाटामेल<span style='font-family:"Calibri",sans-serif'>.</span>भारत</a></span><o:p></o:p></p></div><div><p class=MsoNormal><a href="mailto:ajay@डाटामेल.भारत">ajay@<span style='font-family:"Nirmala UI",sans-serif'>डाटामेल</span>.<span style='font-family:"Nirmala UI",sans-serif'>भारत</span></a><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>and we retain the same domain name.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Both whole email address aliasing and local-part aliasing could co-exist<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>André Schappo<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal>On 23 Feb 2017, at 07:04, Ajay Data <<a href="mailto:ajay@data.in">ajay@data.in</a>> wrote:<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:12.0pt;font-family:"Times New Roman",serif'>This is what we are doing as of now.. we are calling it Alias. <br><br>One mail box: <br>My unicode id is - </span><span style='font-size:12.0pt;font-family:"Nirmala UI",sans-serif'><a href="mailto:अजय@डाटामेल.भारत">अजय<span style='font-family:"Times New Roman",serif'>@</span>डाटामेल<span style='font-family:"Times New Roman",serif'>.</span>भारत</a></span><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><br>Alias - <a href="mailto:aj@datamail.in">aj@datamail.in</a><br><br>And it is working well. <br><br>Best Wishes<br><br>Ajay Data<o:p></o:p></span></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'>On February 23, 2017 11:30:02 AM GMT+05:30, Mark Svancarek via UA-discuss <<a href="mailto:ua-discuss@icann.org">ua-discuss@icann.org</a>> wrote: <o:p></o:p></span></p><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm'><p class=MsoNormal>Andre’s suggestion is a good one and we should probably add it to the “things to consider” portion of the document as an option for email service providers.<o:p></o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'> <o:p></o:p></span></p></div><p class=MsoNormal>Regarding Joseph’s comments:<o:p></o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div><p class=MsoNormal style='margin-left:36.0pt;text-indent:-18.0pt;mso-list:l1 level1 lfo3'><![if !supportLists]><span style='mso-list:Ignore'>1)<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>I don’t actually recall when we made this suggestion. It will certain work and may improve compatibility with some systems. Perhaps we should make this a consideration rather than a best practice. <o:p></o:p></p><div><p class=MsoNormal style='margin-left:36.0pt'><o:p> </o:p></p></div><p class=MsoNormal style='margin-left:36.0pt;text-indent:-18.0pt;mso-list:l1 level1 lfo3'><![if !supportLists]><span style='mso-list:Ignore'>2)<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>It’s true that use of IDNA will restrict the mailbox name strings available. I posit that the number of valid strings will still be huge and that the trade-off is acceptable. <o:p></o:p></p><div><p class=MsoNormal style='margin-left:36.0pt'><o:p> </o:p></p></div><p class=MsoNormal style='margin-left:36.0pt;text-indent:-18.0pt;mso-list:l1 level1 lfo3'><![if !supportLists]><span style='mso-list:Ignore'>3)<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>If an ASCII mailbox alias is offered, then this suggestion is less interesting. <o:p></o:p></p><div><p class=MsoNormal style='margin-left:36.0pt'><o:p> </o:p></p></div><p class=MsoNormal style='margin-left:36.0pt;text-indent:-18.0pt;mso-list:l1 level1 lfo3'><![if !supportLists]><span style='mso-list:Ignore'>4)<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>Move to the mail service provider section. <o:p></o:p></p><div><p class=MsoNormal style='margin-left:36.0pt'><o:p> </o:p></p></div><p class=MsoNormal style='margin-left:36.0pt;text-indent:-18.0pt;mso-list:l1 level1 lfo3'><![if !supportLists]><span style='mso-list:Ignore'>5)<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>I no longer remember why we suggested normalizing… sorry <o:p></o:p></p><div><p class=MsoNormal style='margin-left:36.0pt'><o:p> </o:p></p></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><a name="_MailEndCompose"><span style='font-size:12.0pt;font-family:"Times New Roman",serif'> <o:p></o:p></span></a></p><div><p class=MsoNormal><span style='mso-bookmark:_MailEndCompose'><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></span></p></div><span style='mso-bookmark:_MailEndCompose'></span><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b>From:</b> <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>Andre Schappo<br><b>Sent:</b> Wednesday, February 22, 2017 7:50 AM<br><b>To:</b> Joseph Yee <<a href="mailto:jyee@afilias.info">jyee@afilias.info</a>>; ua-discuss <<a href="mailto:UA-discuss@icann.org">UA-discuss@icann.org</a>><br><b>Subject:</b> Re: [UA-discuss] [UA-EAI] Revised UASG013 - Quick Guide to EAI<o:p></o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div></div></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'> <o:p></o:p></span></p></div><div><p class=MsoNormal>When I read the Quick Guide to EAI a few days ago I was somewhat surprised to see punycode/A-Label used with respect to the local-part/mailbox name. Joseph's email has prompted me to respond.<o:p></o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'> <o:p></o:p></span></p></div></div><div><p class=MsoNormal>There are many issues to having the local-part as punycode but in this email I will focus on a practical working practice that encompasses both the (huge) transition problem and the long term. I think a Best (Compromise) Practice could be:-<o:p></o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'> <o:p></o:p></span></p></div></div><div><p class=MsoNormal>Registration of an internationalised email address would involve registration of both a primary unicode local-part and a secondary ASCII local-part. The ASCII local-part does not need to be a conversion from Unicode to ASCII. Choice of both the Unicode and the ASCII being the choice of the registrant. Both the Unicode and the ASCII would name the same mailbox.<o:p></o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'> <o:p></o:p></span></p></div></div><div><p class=MsoNormal>So, for example, I could register<o:p></o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'> <o:p></o:p></span></p></div></div><div><p class=MsoNormal><span style='font-family:"MS Gothic"'><a href="mailto:%E5%B0%8F%E5%B1%B1@xn--7ovo13by0g.xn--3ds443g"><span lang=JA style='mso-fareast-language:JA'>小山</span><span style='font-family:"Calibri",sans-serif'>@</span><span lang=JA style='mso-fareast-language:JA'>秋月茶</span><span style='font-family:"Calibri",sans-serif'>.</span><span lang=JA style='mso-fareast-language:JA'>在</span><span lang=JA style='font-family:"Microsoft JhengHei",sans-serif;mso-fareast-language:JA'>线</span></a></span><o:p></o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div></div><div><p class=MsoNormal><a href="mailto:andre@xn--7ovo13by0g.xn--3ds443g">andre@<span lang=JA style='font-family:"MS Gothic";mso-fareast-language:JA'>秋月茶</span>.<span lang=JA style='font-family:"MS Gothic";mso-fareast-language:JA'>在</span><span lang=JA style='font-family:"Microsoft JhengHei",sans-serif;mso-fareast-language:JA'>线</span></a><o:p></o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'> <o:p></o:p></span></p></div></div><div><p class=MsoNormal>where <span lang=JA style='font-family:"MS Gothic";mso-fareast-language:JA'>小山</span><span lang=JA> </span>is my primary local-part and andre is my secondary local-part.<o:p></o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'> <o:p></o:p></span></p></div></div><div><p class=MsoNormal>Local-part aliasing already exists on some mail servers. Using the above working practice would enforce an EAI aliasing at the registration stage.<o:p></o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'> <o:p></o:p></span></p></div></div><div><p class=MsoNormal>Using such a methodology would not restrict the Unicode (mostly) that could be used for the local-part. So, for example, <span style='font-family:"Segoe UI Emoji",sans-serif'>🐓</span>@<span lang=JA style='font-family:"MS Gothic";mso-fareast-language:JA'>秋月茶</span>.<span lang=JA style='font-family:"MS Gothic";mso-fareast-language:JA'>在</span><span lang=JA style='font-family:"Microsoft JhengHei",sans-serif;mso-fareast-language:JA'>线</span> would be a valid email address<o:p></o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'> <o:p></o:p></span></p></div></div><div><p class=MsoNormal>I think this working practice could be applied retrospectively. All the mail servers with ASCII only local-parts could allow users to create Unicode local-part aliases thus resulting in both a Unicode local-part and an ASCII local-part. This would be offered to users after the mail server software has been updated to support EAI<o:p></o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'> <o:p></o:p></span></p></div></div><div><p class=MsoNormal>André Schappo<o:p></o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'> <o:p></o:p></span></p></div><div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal>On 13 Feb 2017, at 21:41, Joseph Yee <<a href="mailto:jyee@afilias.info">jyee@afilias.info</a>> wrote:<o:p></o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'> <o:p></o:p></span></p></div><div><div><div><div><p class=MsoNormal style='margin-bottom:12.0pt'>Forwarded this to UA-discuss list for broader feedback on the EAI Quick Guide.<o:p></o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div></div><p class=MsoNormal>Best,<o:p></o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div></div><p class=MsoNormal style='margin-bottom:12.0pt'>Joseph<o:p></o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div><div><div><div><div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'> <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>---------- Forwarded message ----------<br>From: <b>Joseph Yee</b> <<a href="mailto:jyee@afilias.info">jyee@afilias.info</a>><br>Date: Thu, Jan 26, 2017 at 5:14 PM<br>Subject: Re: [UA-EAI] Revised UASG013 - Quick Guide to EAI<br>To: Don Hollander <<a href="mailto:don.hollander@icann.org">don.hollander@icann.org</a>><br>Cc: "<a href="mailto:ua-eai@icann.org">ua-eai@icann.org</a>" <<a href="mailto:ua-eai@icann.org">ua-eai@icann.org</a>>, Mark Svancarek via UA-Coordination <<a href="mailto:ua-coordination@icann.org">ua-coordination@icann.org</a>><o:p></o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div><div><div><div><div><p class=MsoNormal style='margin-bottom:12.0pt'>Hi UA-EAI team,<o:p></o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div></div><p class=MsoNormal style='margin-bottom:12.0pt'>Few comments and questions regarding the quick guide for discussion:<br><br>(1)<br>Client Software (MUA – Mail User Agent)<br>- Should pass the domain name to the MTA (Mail Transport Agent) in A-Label format (RFC5890)<o:p></o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div></div><p class=MsoNormal>The idea of EAI is to allow native Unicode in UTF8 in all mail exchange, is there any rationale for this recommendation?<o:p></o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div></div><p class=MsoNormal>This also makes mailbox management more unnecessary complicated when the next recommendation is 'Should store and display the Mailbox in Unicode'. <o:p></o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'><br>(2)<br>Consider offering mailbox names which conform to the domain name label generation rules for the selected script.<br>- Such names are guaranteed to be compatible with the Punycode algorithm.<o:p></o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div></div><div><p class=MsoNormal>Punycode is one of many encoding solution, and it (assuming we are talking about punycode under IDNA2008) has drawback. This limits the characters allowed in mailbox name. While some may found it okay, it should be pointed out.<o:p></o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div></div><div><p class=MsoNormal style='margin-bottom:12.0pt'><br><br>(3)<br>Consider offering mailbox names which conform to the domain name label generation rules for the selected script.<br>- These email addresses can easily be shared by users with their friends and colleagues who do not use their same writing method; the colleague or friend can address email to such an address, or create an address book entry, using the A-label format.<o:p></o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div></div><div><p class=MsoNormal>Since there's a recommendation earlier to offer an all-ASCII email address, I think this recommendation is not necessary. If one isn't using the same writing method (or the same language/character), it might be better storing the all-ASCII name than than the 'A-label' name. It's easier to manage 'josephyee' than 'xn--qoqx77cy1a' which rely on mail client or backend to render it back properly.<br><br>(4)<br>Upon use, the client MUA software should convert the A-Label to the appropriate U-Label, at which point the friend or colleague will possess the EAI formatted email address despite not having a keyboard or IME which supports the target script.<o:p></o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'> <o:p></o:p></span></p></div></div><div><p class=MsoNormal>First, this one is more of a recommendation for mail client section than mail service provider section.<o:p></o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div></div><div><p class=MsoNormal>Second, please see below for a more in depth discussion on the whole encoding mailbox name.<br><br>(5)<br>How to ensure delivery to non-EAI ready mail systems<br>- Normalising mailbox names in non-ASCII scripts <o:p></o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'> <o:p></o:p></span></p></div></div><div><p class=MsoNormal>If the recipient is non-EAI ready mail systems, normalising mailbox names would not help. Non-ASCII characters still exist in the mailbox name after normalization.<br><br>*****<o:p></o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>(Note: I'm co-chair of EAI working group at IETF, but I speak as individual only)<o:p></o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>On Encoding (A-label, punycode, etc) mailbox name<o:p></o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>At EAI working group, the notion of encoding the UTF8 mailbox name into pure-ASCII mailbox had been discussed, and there is no recommendation made on it. Mailbox management is different from domain management, applying the same encoding algorithm may sound intuitive as domain name already used it and seeming of consistent because the same encoding was provided on both sides of the @ sign. The first drawback, as mentioned above, is the limitation of characters allowed in local part. There are legit ASCII characters/symbols (!#$_) for email that won't make it with A-label. The second drawback is that some characters being used in human name may be prohibited under IDNA2008. There are another category of concerns with pure punycode algorithm on mailbox name. Also, there are not enough coverage on ensuring various presentations of mail address to map to the same mailbox. <o:p></o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>I have serious concern on recommending this practice. This practice is neither mandatory standard nor best common practice, it probably would not be consistently implemented across mail clients, and I would not be surprise if some implementer were against this. While we can recommend to think-about/adopt encoding practice, I'm concern that we need to expand more writing to the quick guide.<o:p></o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>If there's a strong desire to push for an encoding practice, there's a need for another in depth writing on pros & cons, deployment and operation needs, what works & what doesn't.<o:p></o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div></div><div><p class=MsoNormal>Best,<o:p></o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div></div><div><p class=MsoNormal>Joseph<o:p></o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div></div><div><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div></div><div><div style='margin-bottom:12.0pt'><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'> <o:p></o:p></span></p></div></div><div><div style='margin-bottom:12.0pt'><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'> <o:p></o:p></span></p></div></div><div><div style='margin-bottom:12.0pt'><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'> <o:p></o:p></span></p></div></div></div><div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'> <o:p></o:p></span></p></div><div><div><div><p class=MsoNormal>On Sun, Jan 22, 2017 at 4:33 AM, Don Hollander <<a href="mailto:don.hollander@icann.org" target="_blank">don.hollander@icann.org</a>> wrote:<o:p></o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div></div></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt'><div><div><p class=MsoNormal style='margin-bottom:12.0pt'>Last month I sent out a formatted Quick Guide to EAI.<br><br>This resulted in a number of comments from Ajay, Stuart, Mark, Lars & Dennis.<br><br>These enhancements were mostly focused on the Email Service Provider.<br><br>I have revised the source document which is attached.<br><br>And for reference, I’m also including the formatted earlier draft.<br><br>Could I please get any final comments by the end of this week (25th)?<br><br>Thanks.<br><span style='color:#888888'><br><span class=m-747807835945705418hoenzb>Don</span><br><br></span><br><br><br><br><br><br><br><br><br><o:p></o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div></div></div><p class=MsoNormal style='margin-bottom:12.0pt'>Don Hollander<br>Universal Acceptance Steering Group<br>Skype: don_hollander<br><br><br><br><br>_______________________________________________<br>UA-EAI mailing list<br><a href="mailto:UA-EAI@icann.org" target="_blank">UA-EAI@icann.org</a><br><a href="https://mm.icann.org/mailman/listinfo/ua-eai" target="_blank">https://mm.icann.org/mailman/listinfo/ua-eai</a><o:p></o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div></blockquote></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'> <o:p></o:p></span></p></div></div></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'> <o:p></o:p></span></p></div></div></div></div></div></div></div></blockquote></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'> <o:p></o:p></span></p></div></blockquote></div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><br>-- <br>Sent from my Android device with K-9 Mail. Please excuse my brevity.<o:p></o:p></span></p></div></div></blockquote></div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div><br />
<table style="border-top: 1px solid #D3D4DE;">
<tr>
<td style="width: 55px; padding-top: 13px;"><a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=icon" target="_blank"><img src="https://ipmcdn.avast.com/images/icons/icon-envelope-tick-round-orange-animated-no-repeat-v1.gif" width="46" height="29" style="width: 46px; height: 29px;" /></a></td>
<td style="width: 470px; padding-top: 12px; color: #41424e; font-size: 13px; font-family: Arial, Helvetica, sans-serif; line-height: 18px;">Virus-free. <a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=link" target="_blank" style="color: #4453ea;">www.avast.com</a>
</td>
</tr>
</table></body></html>