draft-ietf-eai-rfc5335bis-04.txt   draft-ietf-eai-rfc5335bis-05.txt 
Email Address Internationalization A. Yang Email Address Internationalization Y. Abel
(EAI) TWNIC (EAI) TWNIC
Internet-Draft S. Steele Internet-Draft S. Steele
Obsoletes: 5335 (if approved) Microsoft Obsoletes: 5335 (if approved) Microsoft
Updates: 2045,5321,5322 December 03, 2010 Updates: 2045,5321,5322 December 04, 2010
(if approved) (if approved)
Intended status: Standards Track Intended status: Standards Track
Expires: June 6, 2011 Expires: June 7, 2011
Internationalized Email Headers Internationalized Email Headers
draft-ietf-eai-rfc5335bis-04 draft-ietf-eai-rfc5335bis-05
Abstract Abstract
Full internationalization of electronic mail requires not only the Full internationalization of electronic mail requires not only the
capabilities to transmit non-ASCII content, to encode selected capabilities to transmit non-ASCII content, to encode selected
information in specific header fields, and to use non-ASCII information in specific header fields, and to use non-ASCII
characters in envelope addresses. It also requires being able to characters in envelope addresses. It also requires being able to
express those addresses and the information based on them in mail express those addresses and the information based on them in mail
header fields. This document specifies a variant of Internet mail header fields. This document specifies a variant of Internet mail
that permits the use of Unicode encoded in UTF-8, rather than ASCII, that permits the use of Unicode encoded in UTF-8, rather than ASCII,
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 June 6, 2011. This Internet-Draft will expire on June 7, 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 2, line 30 skipping to change at page 2, line 30
2. Background and History . . . . . . . . . . . . . . . . . . . . 3 2. Background and History . . . . . . . . . . . . . . . . . . . . 3
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Changes on Message Header Fields . . . . . . . . . . . . . . . 5 4. Changes on Message Header Fields . . . . . . . . . . . . . . . 5
4.1. UTF-8 Syntax and Normalization . . . . . . . . . . . . . . 5 4.1. UTF-8 Syntax and Normalization . . . . . . . . . . . . . . 5
4.2. Changes on MIME Headers . . . . . . . . . . . . . . . . . 5 4.2. Changes on MIME Headers . . . . . . . . . . . . . . . . . 5
4.3. Syntax Extensions to RFC 5322 . . . . . . . . . . . . . . 6 4.3. Syntax Extensions to RFC 5322 . . . . . . . . . . . . . . 6
4.4. Change on addr-spec Syntax . . . . . . . . . . . . . . . . 8 4.4. Change on addr-spec Syntax . . . . . . . . . . . . . . . . 8
4.5. Trace Field Syntax . . . . . . . . . . . . . . . . . . . . 9 4.5. Trace Field Syntax . . . . . . . . . . . . . . . . . . . . 9
4.6. message/global . . . . . . . . . . . . . . . . . . . . . . 9 4.6. message/global . . . . . . . . . . . . . . . . . . . . . . 9
5. Security Considerations . . . . . . . . . . . . . . . . . . . 11 5. Security Considerations . . . . . . . . . . . . . . . . . . . 11
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12
8. Edit history . . . . . . . . . . . . . . . . . . . . . . . . . 12 8. Edit history . . . . . . . . . . . . . . . . . . . . . . . . . 12
8.1. draft-ietf-eai-rfc5335bis-00 . . . . . . . . . . . . . . . 12 8.1. draft-ietf-eai-rfc5335bis-00 . . . . . . . . . . . . . . . 12
8.2. draft-ietf-eai-rfc5335bis-01 . . . . . . . . . . . . . . . 13 8.2. draft-ietf-eai-rfc5335bis-01 . . . . . . . . . . . . . . . 12
8.3. draft-ietf-eai-rfc5335bis-02 . . . . . . . . . . . . . . . 13 8.3. draft-ietf-eai-rfc5335bis-02 . . . . . . . . . . . . . . . 12
8.4. draft-ietf-eai-rfc5335bis-03 . . . . . . . . . . . . . . . 13 8.4. draft-ietf-eai-rfc5335bis-03 . . . . . . . . . . . . . . . 12
8.5. draft-ietf-eai-rfc5335bis-04 . . . . . . . . . . . . . . . 13 8.5. draft-ietf-eai-rfc5335bis-04 . . . . . . . . . . . . . . . 13
8.6. draft-ietf-eai-rfc5335bis-05 . . . . . . . . . . . . . . . 13
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13
9.1. Normative References . . . . . . . . . . . . . . . . . . . 13 9.1. Normative References . . . . . . . . . . . . . . . . . . . 13
9.2. Informative References . . . . . . . . . . . . . . . . . . 14 9.2. Informative References . . . . . . . . . . . . . . . . . . 14
1. Introduction 1. Introduction
1.1. Role of This Specification 1.1. Role of This Specification
Full internationalization of electronic mail requires several Full internationalization of electronic mail requires several
capabilities: capabilities:
skipping to change at page 7, line 14 skipping to change at page 7, line 14
uText = %d1-9 / ; all UTF-8 characters except uText = %d1-9 / ; all UTF-8 characters except
%d11-12 / ; US-ASCII NUL, CR, and LF %d11-12 / ; US-ASCII NUL, CR, and LF
%d14-127 / %d14-127 /
UTF8-non-ascii UTF8-non-ascii
uQuoted-Pair = ("\" (VCHAR / WSP / UTF8-non-ascii )) / obs-qp uQuoted-Pair = ("\" (VCHAR / WSP / UTF8-non-ascii )) / obs-qp
VCHAR = <See appendix B.1 of RFC 5234> VCHAR = <See appendix B.1 of RFC 5234>
WSP = <See appendix B.1 of RFC 5234> WSP = <See appendix B.1 of RFC 5234>
uQcontent = uQtext / uQuoted-Pair uQcontent = uQtext / uQuoted-Pair
uQuoted-Pair = ("\" uText) / obs-qp uQuoted-Pair = ("\" uText) / obs-qp
DQUOTE = <See appendix B.1 of RFC 5234> DQUOTE = <See appendix B.1 of RFC 5234>
uCcontent = ctext / uQuoted-Pair / comment uCcontent = ctext / uQuoted-Pair / comment
uQtext = qtext / UTF8-non-ascii uQtext = qtext / UTF8-non-ascii
skipping to change at page 7, line 50 skipping to change at page 7, line 50
uDot-Atom = [CFWS] uDot-Atom-text [CFWS] uDot-Atom = [CFWS] uDot-Atom-text [CFWS]
uDot-Atom-text = 1*uAtext *("." 1*uAtext) uDot-Atom-text = 1*uAtext *("." 1*uAtext)
qcontent =/ uQcontent qcontent =/ uQcontent
To allow the use of UTF-8 in a Content-Description header field To allow the use of UTF-8 in a Content-Description header field
[RFC2045], the following syntax is used: [RFC2045], the following syntax is used:
description = "Content-Description" ":" *uText description = "Content-Description" ":" *uText
; Replace description in Section 8 of [RFC2045] ; Replace description in Section 8 of [RFC2045]
The <uText> syntax is extended above to allow UTF-8 in all The <uText> syntax is extended above to allow UTF-8 in all
<description> header fields. <description> header fields.
Note, however, this does not remove any constraint on the character Note, however, this does not remove any constraint on the character
set of protocol elements; for instance, all the allowed values for set of protocol elements; for instance, all the allowed values for
timezone in the "Date:" header fields are still expressed in ASCII. timezone in the "Date:" header fields are still expressed in ASCII.
And also, none of this revised syntax changes what is allowed in a And also, none of this revised syntax changes what is allowed in a
<msg-id>, which will still remain in pure ASCII. <msg-id>, which will still remain in pure ASCII.
4.4. Change on addr-spec Syntax 4.4. Change on addr-spec Syntax
Internationalized email addresses are represented in UTF-8. Thus, Internationalized email addresses are represented in UTF-8. Thus,
all header fields containing <mailbox>es are updated from [RFC5321] all header fields containing <mailbox>es are updated from [RFC5321]
Section 4.1.2 to permit UTF-8 addresses. Section 4.1.2 to permit UTF-8 addresses.
mailbox = name-addr / addr-spec / uAddr-Spec mailbox = name-addr / addr-spec / uAddr-Spec
; Replace mailbox in Section 3.4 of RFC 5322 ; Replace mailbox in Section 3.4 of RFC 5322
angle-addr =/ [CFWS] "<" uAddr-Spec ">" [CFWS]
; Replace angle-addr in Section 3.4 of RFC 5322
uAddr-Spec = uLocal-Part "@" ( uDomain / address-literal )
address-literal = <See Section 4.1.2 of RFC 5321>
uLocal-Part = uDot-String / uQuoted-String / obs-Local-Part
; Replace Local-Part in Section 4.1.2 of RFC 5321
uDot-string = uAtom *("." uAtom)
; Replace Dot-string in RFC 5321, Section 4.1.2
uDomain = (sub-udomain 1*("." sub-uDomain)) / angle-addr =/ [CFWS] "<" uAddr-Spec ">" [CFWS]
dot-atom / domain-literal / obs-domain ; Replace angle-addr in Section 3.4 of RFC 5322
; Replace Domain in Section 4.1.2 of RFC 5321
sub-udomain = uLet-dig [uLdh-str] uAddr-Spec = uLocal-Part "@" uDomain
; Replace sub-domain in Section 4.1.2 of RFC 5321
uLet-dig = Let-dig / UTF8-non-ascii uLocal-Part = uDot-Atom / uQuoted-String / obs-local-part
; Replace uLet-dig in Section 4.1.2 of RFC 5321 ; Replace Local-Part in Section 3.4.1 of RFC 5322
Let-dig = <See Section 4.1.2 of RFC 5321> uDomain = uDot-Atom / domain-literal / obs-domain
uLdh-str = *( ALPHA / DIGIT / "-" / UTF8-non-ascii) uLet-dig domain-literal = <See Section 3.4.1 of RFC 5322>
; Replace Ldh-str Section 4.1.2 of RFC 5321
Below are a few examples of possible <mailbox> representations. Below are a few examples of possible <mailbox> representations.
"DISPLAY_NAME" <ASCII@ASCII> "DISPLAY_NAME" <ASCII@ASCII>
; traditional mailbox format ; traditional mailbox format
"DISPLAY_NAME" <non-ASCII@non-ASCII> "DISPLAY_NAME" <non-ASCII@non-ASCII>
; message will be rejected if UTF8SMTPbis extension is not supported ; message will be rejected if UTF8SMTPbis extension is not supported
<non-ASCII@non-ASCII> <non-ASCII@non-ASCII>
skipping to change at page 9, line 36 skipping to change at page 9, line 24
of <angle-addr> in Section 4.4 of this document). This will not of <angle-addr> in Section 4.4 of this document). This will not
break the rule of trace field integrity, because the header field is break the rule of trace field integrity, because the header field is
added at the last MTA and described in [RFC5321]. added at the last MTA and described in [RFC5321].
The <received-token> on "Received:" field ( described in Section The <received-token> on "Received:" field ( described in Section
3.6.7 of [RFC5322]) syntax is augmented to allow UTF-8 email address 3.6.7 of [RFC5322]) syntax is augmented to allow UTF-8 email address
in the "For" field. <angle-addr> is augmented to include UTF-8 email in the "For" field. <angle-addr> is augmented to include UTF-8 email
address. In order to allow UTF-8 email addresses in an <addr-spec>, address. In order to allow UTF-8 email addresses in an <addr-spec>,
<uAddr-Spec> is added to <received-token>. <uAddr-Spec> is added to <received-token>.
received-token =/ uAddr-Spec received-token =/ uAddr-Spec
4.6. message/global 4.6. message/global
Internationalized messages MUST only be transmitted as authorized by Internationalized messages MUST only be transmitted as authorized by
[I-D.ietf-eai-rfc5336bis] or within a non-SMTP environment which [I-D.ietf-eai-rfc5336bis] or within a non-SMTP environment which
supports these messages. A message is a "message/global message", if supports these messages. A message is a "message/global message", if
o it contains UTF-8 header values as specified in this document, or o it contains UTF-8 header values as specified in this document, or
o it contains UTF-8 values in the headers fields of body parts. o it contains UTF-8 values in the headers fields of body parts.
skipping to change at page 13, line 18 skipping to change at page 13, line 4
8.3. draft-ietf-eai-rfc5335bis-02 8.3. draft-ietf-eai-rfc5335bis-02
1. ABNF revised. 1. ABNF revised.
8.4. draft-ietf-eai-rfc5335bis-03 8.4. draft-ietf-eai-rfc5335bis-03
1. Fix typos 1. Fix typos
2. ABNF revised 2. ABNF revised
3. Improve sentence 3. Improve sentence
8.5. draft-ietf-eai-rfc5335bis-04 8.5. draft-ietf-eai-rfc5335bis-04
1. improve sentences and ABNF revised based on AD and Co-chairs 1. improve sentences and ABNF revised based on AD and Co-chairs
8.6. draft-ietf-eai-rfc5335bis-05
1. ABNF revised in Section 4.4 based on AD comments
9. References 9. References
9.1. Normative References 9.1. Normative References
[I-D.ietf-eai-5378bis] Resnick, P., Newman, C., and S. Shen, [I-D.ietf-eai-5378bis] Resnick, P., Newman, C., and S. Shen,
"IMAP Support for UTF-8", "IMAP Support for UTF-8",
draft-ietf-eai-5378bis-00 (work in draft-ietf-eai-5378bis-00 (work in
progress), November 2010. progress), November 2010.
[I-D.ietf-eai-frmwrk-4952bis] Klensin, J. and Y. Ko, "Overview and [I-D.ietf-eai-frmwrk-4952bis] Klensin, J. and Y. Ko, "Overview and
 End of changes. 19 change blocks. 
38 lines changed or deleted 26 lines changed or added

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