"IMAP Support for UTF-8", Pete Resnick, Chris Newman, 25-Jun-09. ( bytes)
This specification extends the Internet Message Access Protocol version 4rev1 (IMAP4rev1) to support unencoded international characters in user names, mail addresses and message headers. This is an early draft and intended as a framework for discussion. Please do not deploy implementations of this draft.
"POP3 Support for UTF-8", Randall Gellens, Chris Newman, 23-Jun-09. ( bytes)
This specification extends the Post Office Protocol version 3 (POP3) to support un-encoded international characters in user names, passwords, mail addresses, message headers, and protocol-level textual error strings.
"An update to the mailto URI scheme for Email Address Internationalization", Martin Duerst, 9-Mar-09. ( bytes)
This document updates the definition of the mailto: URI Scheme for use with internationalized email addresses.
"Displaying Downgraded Messages for Email Address Internationalization", Kazunori Fujiwara, 9-Mar-09. ( bytes)
This document describes how to display downgraded messages which originally contain internationalized E-mail addresses or internationalized header fields.
"Internationalized Delivery Status and Disposition Notifications", Chris Newman, Alexey Melnikov, 13-Jul-09. ( bytes)
Delivery status notifications (DSNs) are critical to the correct operation of an email system. However, the existing Draft Standards (RFC 3461, RFC 3462, RFC 3464) are presently limited to US-ASCII text in the machine-readable portions of the protocol. This specification adds a new address type for international email addresses so an original recipient address with non-US-ASCII characters can be correctly preserved even after downgrading. This also provides updated content return media types for delivery status notifications and message disposition notifications to support use of the new address type. This document experimentally extends RFC 3461, RFC 3464, and RFC 3798.
"Guidelines for Internationalized Email Clients", Ernie Dainow, Kazunori Fujiwara, 10-Jul-09. ( bytes)
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.

IETF Secretariat - Please send questions, comments, and/or suggestions to ietf-web@ietf.org.

Return to Internet-Draft directory.

Return to IETF home page.