draft-ietf-eai-dsn-05.txt   draft-ietf-eai-dsn-06.txt 
Network Working Group C. Newman Network Working Group C. Newman
Internet-Draft Sun Microsystems Internet-Draft Sun Microsystems
Updates: 3461,3464,3798 A. Melnikov, Ed. Updates: 3461,3464,3798 A. Melnikov, Ed.
(if approved) Isode Ltd (if approved) Isode Ltd
Intended status: Experimental November 16, 2007 Intended status: Experimental January 21, 2008
Expires: May 19, 2008 Expires: July 24, 2008
International Delivery and Disposition Notifications Internationalized Delivery Status and Disposition Notifications
draft-ietf-eai-dsn-05.txt draft-ietf-eai-dsn-06.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 36 skipping to change at page 1, line 36
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on May 19, 2008. This Internet-Draft will expire on July 24, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2008).
Abstract Abstract
Delivery status notifications (DSNs) are critical to the correct Delivery status notifications (DSNs) are critical to the correct
operation of an email system. However, the existing draft standard operation of an email system. However, the existing draft standard
is presently limited to US-ASCII text in the machine readable is presently limited to US-ASCII text in the machine readable
portions of the protocol. This specification adds a new address type portions of the protocol. This specification adds a new address type
for international email addresses so an original recipient address for international email addresses so an original recipient address
with non-US-ASCII characters can be correctly preserved even after with non-US-ASCII characters can be correctly preserved even after
downgrading. This also provides updated content return media types downgrading. This also provides updated content return media types
skipping to change at page 2, line 18 skipping to change at page 2, line 18
This document experimentally extends RFC 3461, RFC 3464 and RFC 3798. This document experimentally extends RFC 3461, RFC 3464 and RFC 3798.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions Used in this Document . . . . . . . . . . . . . . 3 2. Conventions Used in this Document . . . . . . . . . . . . . . 3
3. UTF-8 Address Type . . . . . . . . . . . . . . . . . . . . . . 3 3. UTF-8 Address Type . . . . . . . . . . . . . . . . . . . . . . 3
4. UTF-8 Delivery Status Notifications . . . . . . . . . . . . . 6 4. UTF-8 Delivery Status Notifications . . . . . . . . . . . . . 6
4.1. Additional requirements on SMTP servers . . . . . . . . . 8 4.1. Additional requirements on SMTP servers . . . . . . . . . 8
5. UTF-8 Message Disposition Notifications . . . . . . . . . . . 8 5. UTF-8 Message Disposition Notifications . . . . . . . . . . . 8
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
6.1. UTF-8 Mail Address Type Registration . . . . . . . . . . . 10 6.1. UTF-8 Mail Address Type Registration . . . . . . . . . . . 9
6.2. Update to 'smtp' Diagnostic Type Registration . . . . . . 11 6.2. Update to 'smtp' Diagnostic Type Registration . . . . . . 10
6.3. message/global-headers . . . . . . . . . . . . . . . . . . 11 6.3. message/global-headers . . . . . . . . . . . . . . . . . . 11
6.4. message/global-delivery-status . . . . . . . . . . . . . . 12 6.4. message/global-delivery-status . . . . . . . . . . . . . . 12
6.5. message/global-disposition-notification . . . . . . . . . 13 6.5. message/global-disposition-notification . . . . . . . . . 13
7. Security Considerations . . . . . . . . . . . . . . . . . . . 14 7. Security Considerations . . . . . . . . . . . . . . . . . . . 14
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
8.1. Normative References . . . . . . . . . . . . . . . . . . . 15 8.1. Normative References . . . . . . . . . . . . . . . . . . . 15
8.2. Informative References . . . . . . . . . . . . . . . . . . 16 8.2. Informative References . . . . . . . . . . . . . . . . . . 16
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 17 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 16
Appendix B. Changes from -04 . . . . . . . . . . . . . . . . . . 17 Appendix B. Changes from -05 . . . . . . . . . . . . . . . . . . 16
Appendix C. Changes from -03 . . . . . . . . . . . . . . . . . . 17 Appendix C. Changes from -04 . . . . . . . . . . . . . . . . . . 17
Appendix D. Changes from -02 . . . . . . . . . . . . . . . . . . 17 Appendix D. Changes from -03 . . . . . . . . . . . . . . . . . . 17
Appendix E. Changes from -01 . . . . . . . . . . . . . . . . . . 17 Appendix E. Changes from -02 . . . . . . . . . . . . . . . . . . 17
Appendix F. Changes from -00 . . . . . . . . . . . . . . . . . . 18 Appendix F. Changes from -01 . . . . . . . . . . . . . . . . . . 17
Appendix G. Changes from -00 . . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 18 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 18
Intellectual Property and Copyright Statements . . . . . . . . . . 19 Intellectual Property and Copyright Statements . . . . . . . . . . 19
1. Introduction 1. Introduction
When an email message is transmitted using the UTF8SMTP When an email message is transmitted using the UTF8SMTP
[I-D.ietf-eai-smtpext] extension and Internationalized Email Headers [I-D.ietf-eai-smtpext] extension and Internationalized Email Headers
[I-D.ietf-eai-utf8headers], it is sometimes necessary to return that [I-D.ietf-eai-utf8headers], it is sometimes necessary to return that
message or generate a Message Disposition Notification [RFC3798] message or generate a Message Disposition Notification [RFC3798]
(MDN). As a message sent to multiple recipients can generate a (MDN). As a message sent to multiple recipients can generate a
status and disposition notification for each recipient, it is helpful status and disposition notification for each recipient, it is helpful
if a client can correlate these returns based on the recipient if a client can correlate these notifications based on the recipient
address it provided, thus preservation of the original recipient is address it provided, thus preservation of the original recipient is
important. This specification describes how to preserve the original important. This specification describes how to preserve the original
recipient and updates the MDN and DSN formats to support the new recipient and updates the MDN and DSN formats to support the new
address types. address types.
2. Conventions Used in this Document 2. Conventions Used in this Document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
skipping to change at page 5, line 5 skipping to change at page 4, line 48
by removal of the 'unitext' encoding. However, if an address is by removal of the 'unitext' encoding. However, if an address is
labeled with the UTF-8 address type but does not conform to utf-8 labeled with the UTF-8 address type but does not conform to utf-8
syntax, then it MUST be copied into the message/ syntax, then it MUST be copied into the message/
global-delivery-status field without alteration. global-delivery-status field without alteration.
The ability to encode characters with the EmbeddedUnicodeChar The ability to encode characters with the EmbeddedUnicodeChar
encodings should be viewed as a transitional mechanism. It is hoped encodings should be viewed as a transitional mechanism. It is hoped
that as systems lacking support for UTF8SMTP become less common over that as systems lacking support for UTF8SMTP become less common over
time, these encodings can eventually be phased out. time, these encodings can eventually be phased out.
In the ABNF below all productions not defined in this document are
defined in Appendix B of [RFC4234], in section 4 of [RFC3629] or in
[RFC3464].
utf-8-type-addr = "utf-8;" utf-8-enc-addr utf-8-type-addr = "utf-8;" utf-8-enc-addr
utf-8-address = uMailbox [ 1*WSP "<" Mailbox ">" ] utf-8-address = uMailbox [ 1*WSP "<" Mailbox ">" ]
; 'uMailbox' is defined in [I-D.ietf-eai-smtpext]. ; 'uMailbox' is defined in [I-D.ietf-eai-smtpext].
; 'Mailbox' is defined in [RFC2821]. ; 'Mailbox' is defined in [RFC2821].
utf-8-enc-addr = utf-8-addr-xtext / utf-8-enc-addr = utf-8-addr-xtext /
utf-8-addr-unitext / utf-8-addr-unitext /
utf-8-address utf-8-address
skipping to change at page 7, line 5 skipping to change at page 6, line 35
convert the utf-8-addr-xtext or the utf-8-addr-unitext form of a convert the utf-8-addr-xtext or the utf-8-addr-unitext form of a
UTF-8 address type in the ORCPT parameter to the utf-8-address form UTF-8 address type in the ORCPT parameter to the utf-8-address form
of a UTF-8 address type in the Original-Recipient field. Third, a of a UTF-8 address type in the Original-Recipient field. Third, a
new optional field called Localized-Diagnostic is added. Each new optional field called Localized-Diagnostic is added. Each
instance includes a language tag [LANGTAGS] and contains text in the instance includes a language tag [LANGTAGS] and contains text in the
specified language. This is equivalent to the text part of the specified language. This is equivalent to the text part of the
Diagnostic-Code field. All instances of Localized-Diagnostic MUST Diagnostic-Code field. All instances of Localized-Diagnostic MUST
use different language tags. The ABNF for message/ use different language tags. The ABNF for message/
global-delivery-status is specified below: global-delivery-status is specified below:
In the ABNF below all productions not defined in this document are
defined in Appendix B of [RFC4234], in section 4 of [RFC3629] or in
[RFC3464].
utf-8-delivery-status-content = per-message-fields utf-8-delivery-status-content = per-message-fields
1*( CRLF utf-8-per-recipient-fields ) 1*( CRLF utf-8-per-recipient-fields )
; "per-message-fields" remains unchanged from the definition ; "per-message-fields" remains unchanged from the definition
; in RFC 3464, except for the "extension-field" ; in RFC 3464, except for the "extension-field"
; which is updated below. ; which is updated below.
utf-8-per-recipient-fields = utf-8-per-recipient-fields =
[ original-recipient-field CRLF ] [ original-recipient-field CRLF ]
final-recipient-field CRLF final-recipient-field CRLF
action-field CRLF action-field CRLF
skipping to change at page 7, line 34 skipping to change at page 7, line 19
; and "extension-field" remain unchanged from ; and "extension-field" remain unchanged from
; the definition in RFC 3464. ; the definition in RFC 3464.
generic-address =/ utf-8-enc-addr generic-address =/ utf-8-enc-addr
; Only allowed with the "utf-8" address-type. ; Only allowed with the "utf-8" address-type.
; ;
; This indirectly updates "original-recipient-field" ; This indirectly updates "original-recipient-field"
; and "final-recipient-field" ; and "final-recipient-field"
diagnostic-code-field = diagnostic-code-field =
"Diagnostic-Code" ":" diagnostic-type ";" *text "Diagnostic-Code" ":" diagnostic-type ";" *text-fixed
localized-diagnostic-text-field = localized-diagnostic-text-field =
"Localized-Diagnostic" ":" Language-Tag ";" *utf8-text "Localized-Diagnostic" ":" Language-Tag ";" *utf8-text
; "Language-Tag" is a language tag as defined in [LANGTAGS]. ; "Language-Tag" is a language tag as defined in [LANGTAGS].
extension-field =/ extension-field-name ":" *utf8-text extension-field =/ extension-field-name ":" *utf8-text
text-fixed = %d1-9 / ; Any Unicode character except for NUL, text-fixed = %d1-9 / ; Any Unicode character except for NUL,
%d11 / ; CR and LF, encoded in UTF-8 %d11 / ; CR and LF, encoded in UTF-8
%d12 / %d12 /
%d14-127 %d14-127
; Same as <text> from RFC 2822, but without <obs-text>. ; Same as <text> from RFC 2822, but without <obs-text>.
; If/when RFC 2822 to disallow <obs-text>, this should become ; If/when RFC 2822 is updated to disallow <obs-text>,
; just <text> ; this should become just <text>
; Also, if/when RFC 2822 is updated to disallow control characters
; this should become a reference to RFC 2822upd instead.
utf8-text = text-fixed / UTF8-non-ascii utf8-text = text-fixed / UTF8-non-ascii
UTF8-non-ascii = UTF2 / UTF3 / UTF4 UTF8-non-ascii = UTF8-2 / UTF8-3 / UTF8-4
The second type, used for returning the content, is message/global The second type, used for returning the content, is message/global
which is similar to message/rfc822, except it contains a message with which is similar to message/rfc822, except it contains a message with
UTF-8 headers. This media type is described in UTF-8 headers. This media type is described in
[I-D.ietf-eai-utf8headers]. [I-D.ietf-eai-utf8headers].
The third type, used for returning the headers, is message/ The third type, used for returning the headers, is message/
global-headers and contains only the UTF-8 header fields of a message global-headers and contains only the UTF-8 header fields of a message
(all lines prior to the first blank line in a UTF8SMTP message). (all lines prior to the first blank line in a UTF8SMTP message).
Unlike message/global, this body part provides no difficulties for Unlike message/global, this body part provides no difficulties for
present infrastructure. present infrastructure.
skipping to change at page 16, line 20 skipping to change at page 16, line 4
10646", STD 63, RFC 3629, November 2003. 10646", STD 63, RFC 3629, November 2003.
[RFC3798] Hansen, T. and G. Vaudreuil, "Message Disposition [RFC3798] Hansen, T. and G. Vaudreuil, "Message Disposition
Notification", RFC 3798, May 2004. Notification", RFC 3798, May 2004.
[RFC4234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax [RFC4234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", RFC 4234, October 2005. Specifications: ABNF", RFC 4234, October 2005.
[I-D.ietf-eai-utf8headers] [I-D.ietf-eai-utf8headers]
Yang, A., "Internationalized Email Headers", Yang, A., "Internationalized Email Headers",
draft-ietf-eai-utf8headers-07 (work in progress), draft-ietf-eai-utf8headers-08 (work in progress),
April 2007. April 2007.
[I-D.ietf-eai-smtpext] [I-D.ietf-eai-smtpext]
Yao, J. and W. Mao, "SMTP extension for internationalized Yao, J. and W. Mao, "SMTP extension for internationalized
email address", draft-ietf-eai-smtpext-09 (work in email address", draft-ietf-eai-smtpext-10 (work in
progress), November 2007. progress), November 2007.
[LANGTAGS] [LANGTAGS]
Phillips, A. and M. Davis, "Tags for Identifying Phillips, A. and M. Davis, "Tags for Identifying
Languages", RFC 4646, September 2006. Languages", RFC 4646, September 2006.
[DEFAULTLANG] [DEFAULTLANG]
Alvestrand, H., "IETF Policy on Character Sets and Alvestrand, H., "IETF Policy on Character Sets and
Languages", RFC 2277, January 1998. Languages", RFC 2277, January 1998.
skipping to change at page 16, line 49 skipping to change at page 16, line 33
Extensions (MIME) Part One: Format of Internet Message Extensions (MIME) Part One: Format of Internet Message
Bodies", RFC 2045, November 1996. Bodies", RFC 2045, November 1996.
[RFC2046] Freed, N. and N. Borenstein, "Multipurpose Internet Mail [RFC2046] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
Extensions (MIME) Part Two: Media Types", RFC 2046, Extensions (MIME) Part Two: Media Types", RFC 2046,
November 1996. November 1996.
[I-D.ietf-eai-downgrade] [I-D.ietf-eai-downgrade]
Yoneya, Y. and K. Fujiwara, "Downgrading mechanism for Yoneya, Y. and K. Fujiwara, "Downgrading mechanism for
Email Address Internationalization (EAI)", Email Address Internationalization (EAI)",
draft-ietf-eai-downgrade-04 (work in progress), Mar 2007. draft-ietf-eai-downgrade-05 (work in progress), Mar 2007.
Appendix A. Acknowledgements Appendix A. Acknowledgements
Many thanks for input provided by Pete Resnick, James Galvin, Ned Many thanks for input provided by Pete Resnick, James Galvin, Ned
Freed, John Klensin, Harald Alvestrand, Frank Ellermann and members Freed, John Klensin, Harald Alvestrand, Frank Ellermann, SM and
of the EAI WG to help solidify this proposal. members of the EAI WG to help solidify this proposal.
Appendix B. Changes from -04 Appendix B. Changes from -05
Minor ABNF fixed discovered while examining Bill Fenner's ABNF parser
output.
Minor editorial changes from SM.
Appendix C. Changes from -04
Restructured <utf8-text> to be more clear about how it relates to RFC Restructured <utf8-text> to be more clear about how it relates to RFC
2822 <text>. 2822 <text>.
Appendix C. Changes from -03 Appendix D. Changes from -03
Addressed editorial comments from Frank Ellermann and Addressed editorial comments from Frank Ellermann and
sm+ietf@elandsys.com. sm+ietf@elandsys.com.
Moved EAI-downgrade to the Informative References. Moved EAI-downgrade to the Informative References.
Updated references. Updated references.
Deleted the list of open issues. Deleted the list of open issues.
Fixed IDnits. Fixed IDnits.
Appendix D. Changes from -02 Appendix E. Changes from -02
Make the space between UTF-8 and ASCII address mandatory. Make the space between UTF-8 and ASCII address mandatory.
Changed all MIME types to be message/global-*. Changed all MIME types to be message/global-*.
Clarified that new message/global-* MIME types are semantically Clarified that new message/global-* MIME types are semantically
equivalent to the corresponding RFC 3464 MIME types. equivalent to the corresponding RFC 3464 MIME types.
Added a requirement not to downgrade non-delivery reports. Added a requirement not to downgrade non-delivery reports.
Deleted unused RFC 3501 reference and updated other references. Deleted unused RFC 3501 reference and updated other references.
Appendix E. Changes from -01 Appendix F. Changes from -01
Cleaned up and tightened ABNF, in particular HEXPOINT. Cleaned up and tightened ABNF, in particular HEXPOINT.
Extended DSN report syntax to allow for localized version of Extended DSN report syntax to allow for localized version of
diagnostic-code-field. diagnostic-code-field.
Added ABNF for the EAI DSN and EAI MDN. Added ABNF for the EAI DSN and EAI MDN.
Appendix F. Changes from -00 Appendix G. Changes from -00
Added paragraph about use of 8bit Content-Transfer-Encoding for new Added paragraph about use of 8bit Content-Transfer-Encoding for new
message sub-types. message sub-types.
Updated the list of open issues. Updated the list of open issues.
Clarified that this document is targeted to become an Experimental Clarified that this document is targeted to become an Experimental
RFC. RFC.
Made the EAI downgrade document a normative reference. Made the EAI downgrade document a normative reference.
skipping to change at page 19, line 7 skipping to change at page 19, line 7
Isode Ltd Isode Ltd
5 Castle Business Village 5 Castle Business Village
36 Station Road 36 Station Road
Hampton, Middlesex TW12 2BX Hampton, Middlesex TW12 2BX
UK UK
Email: Alexey.Melnikov@isode.com Email: Alexey.Melnikov@isode.com
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
 End of changes. 22 change blocks. 
31 lines changed or deleted 50 lines changed or added

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