Guidelines for Internationalized Email Clients
draft-ietf-eai-email-clients-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Ernie Dainow , Kazunori Fujiwara | ||
| Last updated | 2009-07-10 | ||
| Replaces | draft-dainow-eai-email-clients | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document provides some guidelines for email clients that support Email Address Internationalization (EAI) as outlined in RFC 4952. A number of interoperability cases between different versions of email components are reviewed. Recommendations are made to improve interoperability and usability and to minimize discrepancies between the display of composed and received email in different language environments.
Authors
Ernie Dainow
Kazunori Fujiwara
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)