Deployment Issues for Internationalized Email
draft-elkchow-iea-deploy-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Nalini Elkins , हरीश चौधरी | ||
Last updated | 2017-04-07 (Latest revision 2016-10-04) | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
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
International Email Addresses (IEA) are far from the global reality. The current de-facto language of the Internet is English. Even today, many of the users of the Internet do not speak English as their primary language. The next billion users of the Internet are likely to be even less familiar with English. IEA is probably the first application needed in a truly internationalized Internet. The Email Address Internationalization (EAI) Working Group defined the RFCs to support internationalized email. The time may now finally have come to develop best practices and to discuss the deployment challenges for IEA.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)