<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:x="urn:schemas-microsoft-com:office:excel" 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=us-ascii"><meta name=Generator content="Microsoft Word 14 (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;}
/* 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;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{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:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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 lang=EN-US link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>slide 12 MSA should be defined on previous slide. And I know it is ridiculously picky but it should be sending/receiving or sender/recipient MTAs.<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><p class=MsoNormal><span style='color:#1F497D'>slide 14 the info about single and multiple scripts seems irrelevant.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>The process of relating characters to values a computer can use is not mapping but character encoding.<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'>slide 15 is correct that mapping relates characters to numbers. That is a different statement than the previous slide. (Those numbers are in turn encoded.)<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'>slide 17 should explain the U+hhhh nomenclature as a way of indicating the number assigned to a unicode character consisting of 4 to 6 hex digits appended to U+.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Alternatively remove the U+ references and just cite the numeric values assigned to the characters shown.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Perhaps also mention that U+hhhh has nothing to do with U-labels.<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'>slide 21. remove the comment that bidi text is often confusing to users. Seems pejorative.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>it isn’t confusing if it is displayed correctly and the user can read it. (Yes there are some cases that are ambiguous, just as there are in other languages.)<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'>slide 22- i dont understand the intent of saying domain can contain any TLD. Any part of the domain can be unicode. Maybe you mean any IDN.<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'>23 – Is there a recommended practice for validating user parts?<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'>What should MUA do with a failed message? Anything different from other failures?<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'>24- fuzzy matching seems like a bad idea. Even case mapping is a bad idea when multiple languages are introduced, as the case rules can change, even for ascii characters.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>If fuzzy matching is to be recommended, the rules should be specific.<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'>what is the scenario where mail is sent from an mta to an mta that doesn't support EAI?<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>If this is going to an intermediate MTA wouldnt it be better to attempt to route to a different intermediate mta?<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>If the mta is the destination mta, then why wouldnt it accept the email for the domain that it represents?<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'>Perhaps, the scenario is I send an email to 2 people one uses an EAI, the other not. The non-EAI recipient rejects the mail because of the EAI address in the to-field, and the SMTPUTF8 commands, even if it isn’t the local destination address? <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><p class=MsoNormal><span style='color:#1F497D'>27- avoiding easily confused characters seems too vague. We want to prevent “One” vs “0ne” (the letter vs the digit) but we don’t want to eliminate the use of zeroes.<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'>Also, names that differ only in accents is too limiting. And by restricting accents, it implicitly makes the names ascii equivalents. If this is the recommendation then it undermines the benefit of EAI.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>This also seems like a latin based viewpoint. What does this mean for languages that heavily use modifiers?<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'>It would be better to insist on exact matches.<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'>Slide 29 Should discuss mailbox or address downgrading not message downgrading<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'>32 the summary talks about non-latin support, but EAI is about supporting languages that are latin-based too.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Perhaps refer to languages that require characters outside of ascii.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p></div></body></html>