<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:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" 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 Mincho";
        panose-1:2 2 6 9 4 2 5 8 3 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:Consolas;
        panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
        {font-family:"\@MS Mincho";
        panose-1:2 2 6 9 4 2 5 8 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:#0563C1;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:#954F72;
        text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
        {mso-style-priority:99;
        mso-style-link:"Plain Text Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;}
span.PlainTextChar
        {mso-style-name:"Plain Text Char";
        mso-style-priority:99;
        mso-style-link:"Plain Text";
        font-family:"Calibri",sans-serif;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-family:"Calibri",sans-serif;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
/* List Definitions */
@list l0
        {mso-list-id:1027023171;
        mso-list-type:hybrid;
        mso-list-template-ids:-2079420798 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
        {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 lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoPlainText">I refer to <b><span style="font-family:Consolas">ASCII@xn--something</span></b><o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Here’s an example:<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText" style="margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>I send an email to a pair of recipients: <b><span style="font-family:Consolas">A-label@U-label
</span></b>and <b><span style="font-family:Consolas">ASCII@ASCII.</span></b><o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo1">
<a name="_MailEndCompose"><![if !supportLists]><span style="mso-list:Ignore">a.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>(The former is EAI and the latter is non-EAI).<o:p></o:p></a></p>
<p class="MsoPlainText" style="margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Let’s assume that ASCII@ASCII is using the default email client on an iPhone.<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style="mso-list:Ignore">3.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Both recipients Reply All.<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style="mso-list:Ignore">4.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>The iPhone email app does not reply to A-label@U-label – it replies to A-label@xn--something. That just happens to be how that app is currently designed.<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo1">
<![if !supportLists]><span style="mso-list:Ignore">a.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Now my mailbox contains 2 replies. The reply from the EAI user is to the same addresses that I originally used. The reply from the iPhone user contains a different address than I used.<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style="mso-list:Ignore">5.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>These addresses may be searched and sorted in my mailbox differently. That depends on how my mailbox app is coded.
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo1">
<![if !supportLists]><span style="mso-list:Ignore">a.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>AFAIK there is no requirement that these addresses be treated as equivalent. Email is not DNS.<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style="mso-list:Ignore">6.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>In fact, one of these formats does not even have a name, which means that discussing this scenario requires the use of new terminology. I’ve been calling this format “IDN email”.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Does that make sense.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">-----Original Message-----<br>
From: Andrew Sullivan [mailto:ajs@anvilwalrusden.com] <br>
Sent: Wednesday, February 17, 2016 6:46 PM<br>
To: Mark Svancarek<br>
Cc: ua-discuss@icann.org<br>
Subject: Re: [UA-discuss] Review of UASG Charter</p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">On Wed, Feb 17, 2016 at 11:32:19PM +0000, Mark Svancarek wrote:<o:p></o:p></p>
<p class="MsoPlainText">> I still think it's important to distinguish between EAI and addresses in "local@punycode" formats, since many email clients treat those different in various scenarios. What would you call that format?<o:p></o:p></p>
<p class="MsoPlainText">> <o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">"Email address"?<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">I'm not quite sure what you mean by "local@" above, so two possible<o:p></o:p></p>
<p class="MsoPlainText">interpretations:<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">An address of the form [utf-8]@xn--something is just user-hostile. In order for the local-part to be in utf-8, the EAI extensions need to be in place anyway; otherwise it won't work. So refusing to handle the IDNA server-part portion
is really just poor implementation (a polite way of saying "broken" ;-)).<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">If you mean the case where you have a non-EAI localpart with a server-part that has at least one A-label, well, that's just old-fashioned email. It's certainly true that the target server name is mystifying. That is frustrating, but
basically it's just an IDNA-unaware client. We designed IDNA the way we did precisely because there are so many clients out there that couldn't accept anything but LDH in a domain name slot (thats what the server-part is<o:p></o:p></p>
<p class="MsoPlainText">-- see RFC 5890).<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">There are also clients -- the version of mutt I'm sending this mail with, IIRC -- that have IDNA-awareness compiled in, and they can display the server part as IDNA U-labels as opposed to A-labels. So if I registered crânkycanuck.ca
(which under CIRA's rules I think I could), you could send me mail at <a href="mailto:ajs@xn--crnkycanuck-x7a.ca">
<span style="color:windowtext;text-decoration:none">ajs@xn--crnkycanuck-x7a.ca</span></a> and (assuming I configured my MTA to take it) I'd see
<a href="mailto:ajs@crânkycanuck.ca"><span style="color:windowtext;text-decoration:none">ajs@crânkycanuck.ca</span></a>.<o:p></o:p></p>
<p class="MsoPlainText">_This_ use case is definitely different to EAI, because the SMTP extensions aren't needed. But it's just ordinary IDNA, I think -- all the transformations have to happen in the client at display time. I suppose there's an issue in
that such a client might try EAI when it attempts to send mail, and get a failure.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Best regards,<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">A<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">> -----Original Message-----<o:p></o:p></p>
<p class="MsoPlainText">> From: <a href="mailto:ua-discuss-bounces@icann.org"><span style="color:windowtext;text-decoration:none">ua-discuss-bounces@icann.org</span></a>
<o:p></o:p></p>
<p class="MsoPlainText">> [<a href="mailto:ua-discuss-bounces@icann.org"><span style="color:windowtext;text-decoration:none">mailto:ua-discuss-bounces@icann.org</span></a>] On Behalf Of Andrew Sullivan<o:p></o:p></p>
<p class="MsoPlainText">> Sent: Monday, February 15, 2016 8:01 PM<o:p></o:p></p>
<p class="MsoPlainText">> To: <a href="mailto:ua-discuss@icann.org"><span style="color:windowtext;text-decoration:none">ua-discuss@icann.org</span></a><o:p></o:p></p>
<p class="MsoPlainText">> Subject: Re: [UA-discuss] Review of UASG Charter<o:p></o:p></p>
<p class="MsoPlainText">> <o:p></o:p></p>
<p class="MsoPlainText">> I agree with the comment in the doc that "IDN email" isn't a thing.<o:p></o:p></p>
<p class="MsoPlainText">> "Email using EAI" or "Email using address internationalization" or just "EAI" are correct.<o:p></o:p></p>
<p class="MsoPlainText">> <o:p></o:p></p>
<p class="MsoPlainText">> Otherwise, no comment.<o:p></o:p></p>
<p class="MsoPlainText">> <o:p></o:p></p>
<p class="MsoPlainText">> A<o:p></o:p></p>
<p class="MsoPlainText">> <o:p></o:p></p>
<p class="MsoPlainText">> On Tue, Feb 16, 2016 at 03:43:21AM +0000, Don Hollander wrote:<o:p></o:p></p>
<p class="MsoPlainText">> > Further to the face-to-face meeting of the UASG Coordination group in January, the charter has been reviewed some fundamental changes are proposed.<o:p></o:p></p>
<p class="MsoPlainText">> > <o:p></o:p></p>
<p class="MsoPlainText">> > Instead of having a community of volunteers supported by a professional body, we’re proposing shifting to a professional body supported by volunteers. The UASG Coordination group will shift more toward governance than operation,
though volunteers are still very highly encouraged.<o:p></o:p></p>
<p class="MsoPlainText">> > <o:p></o:p></p>
<p class="MsoPlainText">> > Please find attached a red-lined revision to the Charter.<o:p></o:p></p>
<p class="MsoPlainText">> > <o:p></o:p></p>
<p class="MsoPlainText">> > Your comments would be welcome through the 22nd of February.<o:p></o:p></p>
<p class="MsoPlainText">> > <o:p></o:p></p>
<p class="MsoPlainText">> > <o:p></o:p></p>
<p class="MsoPlainText">> > Don<o:p></o:p></p>
<p class="MsoPlainText">> > <o:p></o:p></p>
<p class="MsoPlainText">> > <o:p></o:p></p>
<p class="MsoPlainText">> <o:p></o:p></p>
<p class="MsoPlainText">> <o:p></o:p></p>
<p class="MsoPlainText">> <o:p></o:p></p>
<p class="MsoPlainText">> --<o:p></o:p></p>
<p class="MsoPlainText">> Andrew Sullivan<o:p></o:p></p>
<p class="MsoPlainText">> <a href="mailto:ajs@anvilwalrusden.com"><span style="color:windowtext;text-decoration:none">ajs@anvilwalrusden.com</span></a><o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">--<o:p></o:p></p>
<p class="MsoPlainText">Andrew Sullivan<o:p></o:p></p>
<p class="MsoPlainText"><a href="mailto:ajs@anvilwalrusden.com"><span style="color:windowtext;text-decoration:none">ajs@anvilwalrusden.com</span></a><o:p></o:p></p>
</div>
</body>
</html>