[UA-discuss] ICANN EAI infrastructure
edmon at registry.asia
Tue Mar 29 05:51:41 UTC 2016
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".
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.
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...
> -----Original Message-----
> From: ua-discuss-bounces at icann.org [mailto:ua-discuss-bounces at icann.org] On
> Behalf Of Don Hollander
> Sent: Saturday, 26 March 2016 01:31 AM
> To: Andre Schappo <A.Schappo at lboro.ac.uk>
> Cc: UA-discuss at icann.org
> Subject: Re: [UA-discuss] ICANN EAI infrastructure
> We know that EAI fails with ICANN - and I suspect many many other organisations.
> The good news is that they are working on it - basically waiting for their supplier (I
> > On 26/03/2016, at 4:48 AM, Andre Schappo <A.Schappo at lboro.ac.uk> wrote:
> > Thanks to Raed I now have a cool new arabic script email address.
> > Works fine with gmail
> > So what of ICANN's mail system.
> > I sent a test email to ua-international using my arabic email address and
> subsequently received the error message
> > ➤ SMTPUTF8 is required, but was not offered by host
> > So, #fail for ICANN wrt EAI
> > André Schappo
More information about the UA-discuss