draft-ietf-eai-frmwrk-4952bis-04.txt   draft-ietf-eai-frmwrk-4952bis-05.txt 
Email Address Internationalization J. Klensin Email Address Internationalization J. Klensin
(EAI) (EAI)
Internet-Draft Y. Ko Internet-Draft Y. Ko
Obsoletes: RFCs 4952, 5504, 5825 ICU Obsoletes: RFCs 4952, 5504, 5825 ICU
(if approved) August 20, 2010 (if approved) August 22, 2010
Intended status: Informational Intended status: Informational
Expires: February 21, 2011 Expires: February 23, 2011
Overview and Framework for Internationalized Email Overview and Framework for Internationalized Email
draft-ietf-eai-frmwrk-4952bis-04 draft-ietf-eai-frmwrk-4952bis-05
Abstract Abstract
Full use of electronic mail throughout the world requires that Full use of electronic mail throughout the world requires that
(subject to other constraints) people be able to use close variations (subject to other constraints) people be able to use close variations
on their own names (written correctly in their own languages and on their own names (written correctly in their own languages and
scripts) as mailbox names in email addresses. This document scripts) as mailbox names in email addresses. This document
introduces a series of specifications that define mechanisms and introduces a series of specifications that define mechanisms and
protocol extensions needed to fully support internationalized email protocol extensions needed to fully support internationalized email
addresses. These changes include an SMTP extension and extension of addresses. These changes include an SMTP extension and extension of
skipping to change at page 1, line 44 skipping to change at page 1, line 44
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on February 21, 2011. This Internet-Draft will expire on February 23, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 49 skipping to change at page 3, line 49
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
13. Security Considerations . . . . . . . . . . . . . . . . . . . 18 13. Security Considerations . . . . . . . . . . . . . . . . . . . 18
14. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 20 14. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 20
15. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20 15. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20
15.1. Normative References . . . . . . . . . . . . . . . . . . . 20 15.1. Normative References . . . . . . . . . . . . . . . . . . . 20
15.2. Informative References . . . . . . . . . . . . . . . . . . 22 15.2. Informative References . . . . . . . . . . . . . . . . . . 22
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 26 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 26
A.1. Changes between -00 and -01 . . . . . . . . . . . . . . . 26 A.1. Changes between -00 and -01 . . . . . . . . . . . . . . . 26
A.2. Changes between -01 and -02 . . . . . . . . . . . . . . . 26 A.2. Changes between -01 and -02 . . . . . . . . . . . . . . . 26
A.3. Changes between -02 and -03 . . . . . . . . . . . . . . . 27 A.3. Changes between -02 and -03 . . . . . . . . . . . . . . . 27
A.4. Changes between -02 and -03 . . . . . . . . . . . . . . . 28 A.4. Changes between -03 and -04 . . . . . . . . . . . . . . . 28
A.5. Changes between -04 and -05 . . . . . . . . . . . . . . . 28
1. Introduction 1. Introduction
Note in Draft and to RFC Editor: The keyword represented in this Note in Draft and to RFC Editor: The keyword represented in this
document by "UTF8SMTPbis" (and in the XML source by &EAISMTPkeyword;) document by "UTF8SMTPbis" (and in the XML source by &EAISMTPkeyword;)
is a placeholder. The actual keyword will be assigned when the is a placeholder. The actual keyword will be assigned when the
standards track SMTP extension in this series [RFC5336bis-SMTP] is standards track SMTP extension in this series [RFC5336bis-SMTP] is
approved for publication and should be substituted here. This approved for publication and should be substituted here. This
paragraph should be treated as normative reference to that SMTP paragraph should be treated as normative reference to that SMTP
extension draft, creating a reference hold until it is approved by extension draft, creating a reference hold until it is approved by
skipping to change at page 10, line 42 skipping to change at page 10, line 42
[RFC1652] and that the client support 8-bit transmission so that [RFC1652] and that the client support 8-bit transmission so that
header information can be transmitted without using a special header information can be transmitted without using a special
content-transfer-encoding. content-transfer-encoding.
Some general principles affect the development decisions underlying Some general principles affect the development decisions underlying
this work. this work.
1. Email addresses enter subsystems (such as a user interface) that 1. Email addresses enter subsystems (such as a user interface) that
may perform charset conversions or other encoding changes. When may perform charset conversions or other encoding changes. When
the left hand side of the address includes characters outside the the left hand side of the address includes characters outside the
US-ASCII character repertoire, use of ASCII-compatible (ACE) US-ASCII character repertoire, use of ASCII-compatible encoding
encoding [RFC3492] [RFC5890] on the right hand side is (ACE) [RFC3492] [RFC5890] on the right hand side is discouraged
discouraged to promote consistent processing of characters to promote consistent processing of characters throughout the
throughout the address. address.
2. An SMTP relay must 2. An SMTP relay must
* Either recognize the format explicitly, agreeing to do so via * Either recognize the format explicitly, agreeing to do so via
an ESMTP option, or an ESMTP option, or
* Reject the message or, if necessary, return a non-delivery * Reject the message or, if necessary, return a non-delivery
notification message, so that the sender can make another notification message, so that the sender can make another
plan. plan.
3. If the message cannot be forwarded because the next-hop system 3. If the message cannot be forwarded because the next-hop system
cannot accept the extension it MUST be rejected or a non-delivery cannot accept the extension it MUST be rejected or a non-delivery
message generated and sent. message MUST be generated and sent.
4. In the interest of interoperability, charsets other than UTF-8 4. In the interest of interoperability, charsets other than UTF-8
are prohibited in mail addresses and message headers being are prohibited in mail addresses and message headers being
transmitted over the Internet. There is no practical way to transmitted over the Internet. There is no practical way to
identify multiple charsets properly with an extension similar to identify multiple charsets properly with an extension similar to
this without introducing great complexity. this without introducing great complexity.
Conformance to the group of standards specified here for email Conformance to the group of standards specified here for email
transport and delivery requires implementation of the SMTP Extension transport and delivery requires implementation of the SMTP Extension
specification and the UTF-8 Header specification. If the system specification and the UTF-8 Header specification. If the system
skipping to change at page 28, line 5 skipping to change at page 28, line 5
aside to a separate section, Section 6. aside to a separate section, Section 6.
o Rewrote the discussion of configuration errors in MX setups to o Rewrote the discussion of configuration errors in MX setups to
make it clear that they are an issue with forward-pointing make it clear that they are an issue with forward-pointing
addresses only and improved the discussion of backward-pointing addresses only and improved the discussion of backward-pointing
addresses. addresses.
o Removed some now-obsolete placeholder notes and resolved the o Removed some now-obsolete placeholder notes and resolved the
remaining one to a dangling reference. remaining one to a dangling reference.
A.4. Changes between -02 and -03 A.4. Changes between -03 and -04
o Several minor editorial changes. o Several minor editorial changes.
o Added a discussion of the relationship to the base email, MIME, o Added a discussion of the relationship to the base email, MIME,
and IDNA specifications. and IDNA specifications.
A.5. Changes between -04 and -05
o Several more minor editorial changes.
Authors' Addresses Authors' Addresses
John C KLENSIN John C KLENSIN
1770 Massachusetts Ave, #322 1770 Massachusetts Ave, #322
Cambridge, MA 02140 Cambridge, MA 02140
USA USA
Phone: +1 617 491 5735 Phone: +1 617 491 5735
EMail: john-ietf@jck.com EMail: john-ietf@jck.com
 End of changes. 9 change blocks. 
11 lines changed or deleted 16 lines changed or added

This html diff was produced by rfcdiff 1.38. The latest version is available from http://tools.ietf.org/tools/rfcdiff/