draft-ietf-eai-rfc5335bis-06.txt   draft-ietf-eai-rfc5335bis-07.txt 
Email Address Internationalization Y. Abel 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 06, 2010 Updates: 2045,5321,5322 December 08, 2010
(if approved) (if approved)
Intended status: Standards Track Intended status: Standards Track
Expires: June 9, 2011 Expires: June 11, 2011
Internationalized Email Headers Internationalized Email Headers
draft-ietf-eai-rfc5335bis-06 draft-ietf-eai-rfc5335bis-07
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 9, 2011. This Internet-Draft will expire on June 11, 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 31 skipping to change at page 2, line 31
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 . . . . . . . . . . . . . . . . . . . . . 11 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 11
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 . . . . . . . . . . . . . . . 12 8.2. draft-ietf-eai-rfc5335bis-01 . . . . . . . . . . . . . . . 12
8.3. draft-ietf-eai-rfc5335bis-02 . . . . . . . . . . . . . . . 12 8.3. draft-ietf-eai-rfc5335bis-02 . . . . . . . . . . . . . . . 12
8.4. draft-ietf-eai-rfc5335bis-03 . . . . . . . . . . . . . . . 12 8.4. draft-ietf-eai-rfc5335bis-03 . . . . . . . . . . . . . . . 12
8.5. draft-ietf-eai-rfc5335bis-04 . . . . . . . . . . . . . . . 13 8.5. draft-ietf-eai-rfc5335bis-04 . . . . . . . . . . . . . . . 12
8.6. draft-ietf-eai-rfc5335bis-05 . . . . . . . . . . . . . . . 13 8.6. draft-ietf-eai-rfc5335bis-05 . . . . . . . . . . . . . . . 12
8.7. draft-ietf-eai-rfc5335bis-06 . . . . . . . . . . . . . . . 13 8.7. draft-ietf-eai-rfc5335bis-06 . . . . . . . . . . . . . . . 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
skipping to change at page 7, line 45 skipping to change at page 7, line 45
"|" / "}" / "|" / "}" /
"~" / "~" /
UTF8-non-ascii UTF8-non-ascii
uAtom = [CFWS] 1*uAtext [CFWS] uAtom = [CFWS] 1*uAtext [CFWS]
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
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 RFC 2045, Section 8 ; Replace description in RFC 2045, Section 8
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
skipping to change at page 11, line 32 skipping to change at page 11, line 32
Because UTF-8 often requires several octets to encode a single Because UTF-8 often requires several octets to encode a single
character, internationalized local parts and header value may cause character, internationalized local parts and header value may cause
mail addresses to become longer. As specified in [RFC5322], each mail addresses to become longer. As specified in [RFC5322], each
line of characters MUST be no more 998 octets, excluding the CRLF. line of characters MUST be no more 998 octets, excluding the CRLF.
On the other hand, MDA (Mail Delivery Agent) processes that parse, On the other hand, MDA (Mail Delivery Agent) processes that parse,
store, or handle email addresses or local parts must take extra care store, or handle email addresses or local parts must take extra care
not to overflow buffers, truncate addresses, or exceed storage not to overflow buffers, truncate addresses, or exceed storage
allotments. Also, they must take care, when comparing, to use the allotments. Also, they must take care, when comparing, to use the
entire lengths of the addresses. entire lengths of the addresses.
In this specification, a user could provide an ASCII alternative
address for a non-ASCII address. However, it is possible these two
addresses go to different mailboxes, or even different people. This
configuration may be based on a user's personal choice or on
administration policy. We recognize that if ASCII and non-ASCII
email is delivered to two different destinations, based on MTA
capability, this may violate the principle of least astonishment, but
this is not a "protocol problem".
The security impact of UTF-8 headers on email signature systems such The security impact of UTF-8 headers on email signature systems such
as Domain Keys Identified Mail (DKIM), S/MIME, and OpenPGP is as Domain Keys Identified Mail (DKIM), S/MIME, and OpenPGP is
discussed in [I-D.ietf-eai-frmwrk-4952bis], Section 14. discussed in [I-D.ietf-eai-frmwrk-4952bis], Section 14.
6. IANA Considerations 6. IANA Considerations
IANA is requested to update the registration of the message/global IANA is requested to update the registration of the message/global
MIME type using the registration form contained in Section 4.6. MIME type using the registration form contained in Section 4.6.
7. Acknowledgements 7. Acknowledgements
 End of changes. 8 change blocks. 
18 lines changed or deleted 7 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/