[UA-EAI] List of EAI Ready Software

[Tan Tanaka, Dennis]

Don,

Just a quick comment. I suggest replacing the RFC links with their HTML equivalent. TXT versions are static whereas HTML versions offer additional information as updates, errata, obsolete information, etc. Also, we should use, whenever possible, authoritative sources (i.e. IETF.org vs rfc-editor.org). Here are the links for your convenience:

IDN:
Framework: https://tools.ietf.org/html/rfc5890 
IDNA Protocol: https://tools.ietf.org/html/rfc5891
Unicode Code Points: https://tools.ietf.org/html/rfc5892
Right-To-Left Scripts: https://tools.ietf.org/html/rfc5893

EAI:
Framework: https://tools.ietf.org/html/rfc6530
SMTP Extension: https://tools.ietf.org/html/rfc6531
Email Headers: https://tools.ietf.org/html/rfc6532
Delivery Status and Disposition Notification: https://tools.ietf.org/html/rfc6533
IMAP Support for UTF-8: https://tools.ietf.org/html/rfc6855
POP3 Support for UTF-8: https://tools.ietf.org/html/rfc6856

-Dennis



On 6/8/16, 6:01 AM, "ua-eai-bounces at icann.org on behalf of Don Hollander" <ua-eai-bounces at icann.org on behalf of don.hollander at icann.org> wrote:

>Further to discussions last month, I’ve drafted a ROUGH document that outlines criteria for being deemed EAI ready and started a list of EAI ready software.
>
>A link to an editable version of the document is https://docs.google.com/document/d/1OVzd7QBZGV6bxBVG24Uul-Webkt3r-v815UXZXtWhjA/edit?usp=sharing  (PDF Attached)
>
>We have a project in our work plan to evaluate the most common email software and services to determine if they are EAI ready.
>
>I would like something in ‘plain english’ to more easily evaluate whether the software or service is indeed compliant.   I would also like to have a Quick Guide to EAI so that mail software developers (and there are hundreds) can easily see what they need to do to become EAI ready.
>
>I would welcome your thoughts and comments.
>
>Don