<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=utf-8" http-equiv=Content-Type>
<STYLE>
BLOCKQUOTE {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; MARGIN-LEFT: 2em
}
OL {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
UL {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
BODY {
LINE-HEIGHT: 1.5; FONT-FAMILY: 宋 COLOR: #000000; FONT-SIZE: 10.5pt; 20307:
}
P {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</STYLE>
<META name=GENERATOR content="MSHTML 9.00.8112.16684"></HEAD>
<BODY style="MARGIN: 10px">
<DIV> </DIV>
<DIV>I share some discussions in IETF EAI WG about downgrading.</DIV>
<DIV>This WG did not design the downgrading mechanism based on the assumption
that if most email service providers support EAI, EAI downgrade is not
necessary.</DIV>
<DIV>So my suggestion is that call more email service providers to upgrade their
service to support EAI and announce it to support EAI almost together.</DIV>
<DIV>if google, microsoft, yahoo, qq.com, 163.com and more support EAI almost
together, the downgrade will not become a problem.</DIV>
<DIV> </DIV>
<DIV>let UASG call all email service providers to form a group and announce it
to support EAI on some day together?</DIV>
<DIV> </DIV>
<DIV> </DIV>
<HR style="WIDTH: 210px; HEIGHT: 1px" align=left color=#b5c4df SIZE=1>
<DIV><SPAN>Jiankang Yao</SPAN></DIV>
<DIV> </DIV>
<DIV
style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<DIV
style="PADDING-BOTTOM: 8px; PADDING-LEFT: 8px; PADDING-RIGHT: 8px; BACKGROUND: #efefef; COLOR: #000000; FONT-SIZE: 12px; PADDING-TOP: 8px">
<DIV><B>From:</B> <A href="mailto:edmon@registry.asia">Edmon
Chung</A></DIV>
<DIV><B>Date:</B> 2016-03-29 13:51</DIV>
<DIV><B>To:</B> <A href="mailto:don.hollander@icann.org">'Don
Hollander'</A>; <A href="mailto:A.Schappo@lboro.ac.uk">'Andre Schappo'</A></DIV>
<DIV><B>CC:</B> <A href="mailto:UA-discuss@icann.org">UA-discuss</A></DIV>
<DIV><B>Subject:</B> Re: [UA-discuss] ICANN EAI
infrastructure</DIV></DIV></DIV>
<DIV>
<DIV>jumping on this discussion to rekindle an earlier thread with Brent and others about the implementation challenge for EAI, especially with the lack of "downgrading" and some "backwards compatibility".</DIV>
<DIV> </DIV>
<DIV>At the meeting in Marrakech, we explored this a bit further and thought maybe some sort of service discovery mechanism to retrieve an alternate address be developed for situations such as mailing lists or forwarded/replied/cc-ed emails especially where additional emails were added to a thread who are not EAI ready.</DIV>
<DIV> </DIV>
<DIV>I wonder if anyone on the list is interested to further look into the issue and propose such mechanism(s)... or at least produce some document for what to do in such cases, which could help in the EAI implementation...</DIV>
<DIV> </DIV>
<DIV>Edmon</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>> -----Original Message-----</DIV>
<DIV>> From: ua-discuss-bounces@icann.org [mailto:ua-discuss-bounces@icann.org] On</DIV>
<DIV>> Behalf Of Don Hollander</DIV>
<DIV>> Sent: Saturday, 26 March 2016 01:31 AM</DIV>
<DIV>> To: Andre Schappo <A.Schappo@lboro.ac.uk></DIV>
<DIV>> Cc: UA-discuss@icann.org</DIV>
<DIV>> Subject: Re: [UA-discuss] ICANN EAI infrastructure</DIV>
<DIV>> </DIV>
<DIV>> Andre,</DIV>
<DIV>> </DIV>
<DIV>> We know that EAI fails with ICANN - and I suspect many many other organisations.</DIV>
<DIV>> </DIV>
<DIV>> The good news is that they are working on it - basically waiting for their supplier (I</DIV>
<DIV>> think).</DIV>
<DIV>> </DIV>
<DIV>> D</DIV>
<DIV>> </DIV>
<DIV>> </DIV>
<DIV>> > On 26/03/2016, at 4:48 AM, Andre Schappo <A.Schappo@lboro.ac.uk> wrote:</DIV>
<DIV>> ></DIV>
<DIV>> ></DIV>
<DIV>> > Thanks to Raed I now have a cool new arabic script email address.</DIV>
<DIV>> ></DIV>
<DIV>> > Works fine with gmail</DIV>
<DIV>> ></DIV>
<DIV>> > So what of ICANN's mail system.</DIV>
<DIV>> ></DIV>
<DIV>> > I sent a test email to ua-international using my arabic email address and</DIV>
<DIV>> subsequently received the error message</DIV>
<DIV>> ></DIV>
<DIV>> > ➤ SMTPUTF8 is required, but was not offered by host</DIV>
<DIV>> pechora5.icann.org[192.0.46.71]</DIV>
<DIV>> ></DIV>
<DIV>> > So, #fail for ICANN wrt EAI</DIV>
<DIV>> ></DIV>
<DIV>> > André Schappo</DIV>
<DIV>> ></DIV>
<DIV> </DIV></DIV></BODY></HTML>