draft-ietf-eai-dsn-04.txt   draft-ietf-eai-dsn-05.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 September 28, 2007 Intended status: Experimental November 16, 2007
Expires: March 31, 2008 Expires: May 19, 2008
International Delivery and Disposition Notifications International Delivery and Disposition Notifications
draft-ietf-eai-dsn-04.txt draft-ietf-eai-dsn-05.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 March 31, 2008. This Internet-Draft will expire on May 19, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
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
skipping to change at page 2, line 29 skipping to change at page 2, line 29
6.1. UTF-8 Mail Address Type Registration . . . . . . . . . . . 10 6.1. UTF-8 Mail Address Type Registration . . . . . . . . . . . 10
6.2. Update to 'smtp' Diagnostic Type Registration . . . . . . 11 6.2. Update to 'smtp' Diagnostic Type Registration . . . . . . 11
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 . . . . . . . . . . . . . . . . . . 17
Appendix B. Changes from -02 . . . . . . . . . . . . . . . . . . 17 Appendix B. Changes from -04 . . . . . . . . . . . . . . . . . . 17
Appendix C. Changes from -01 . . . . . . . . . . . . . . . . . . 17 Appendix C. Changes from -03 . . . . . . . . . . . . . . . . . . 17
Appendix D. Changes from -00 . . . . . . . . . . . . . . . . . . 17 Appendix D. Changes from -02 . . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17 Appendix E. Changes from -01 . . . . . . . . . . . . . . . . . . 17
Appendix F. Changes from -00 . . . . . . . . . . . . . . . . . . 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
skipping to change at page 4, line 12 skipping to change at page 4, line 12
the utf-8-address form MUST NOT be used in the ORCPT parameter when the utf-8-address form MUST NOT be used in the ORCPT parameter when
the SMTP server doesn't advertise support for UTF8SMTP or the SMTP the SMTP server doesn't advertise support for UTF8SMTP or the SMTP
server supports UTF8SMTP, but the address contains US-ASCII server supports UTF8SMTP, but the address contains US-ASCII
characters not permitted in the ORCPT parameter (e.g. the ORCPT characters not permitted in the ORCPT parameter (e.g. the ORCPT
parameter forbids unencoded SP and the = character); or in a 7-bit parameter forbids unencoded SP and the = character); or in a 7-bit
transport environment including a message/delivery-status Original- transport environment including a message/delivery-status Original-
Recipient or Final-Recipient field. In the former case the utf-8- Recipient or Final-Recipient field. In the former case the utf-8-
addr-xtext form (see below) MUST be used instead, in the latter case addr-xtext form (see below) MUST be used instead, in the latter case
the utf-8-addr-unitext form MUST be used. The utf-8-address form MAY the utf-8-addr-unitext form MUST be used. The utf-8-address form MAY
be used in the ORCPT parameter when the SMTP server also advertises be used in the ORCPT parameter when the SMTP server also advertises
support for UTF8SMTP and the address doesn't contains any US-ASCII support for UTF8SMTP and the address doesn't contain any US-ASCII
characters not permitted in the ORCPT parameter. It SHOULD be used characters not permitted in the ORCPT parameter. It SHOULD be used
in a message/global-delivery-status Original-Recipient or Final- in a message/global-delivery-status Original-Recipient or Final-
Recipient DSN field; or in an Original-Recipient header field Recipient DSN field; or in an Original-Recipient header field
[RFC3798] if the message is a UTF8SMTP message. [RFC3798] if the message is a UTF8SMTP message.
In addition, the utf-8-addr-unitext form can be used anywhere where In addition, the utf-8-addr-unitext form can be used anywhere where
the utf-8-address form is allowed. the utf-8-address form is allowed.
When using in the ORCPT parameter, the UTF-8 address type requires When using in the ORCPT parameter, the UTF-8 address type requires
that US-ASCII CTLs, SP, \, + and = be encoded using xtext encoding as that US-ASCII CTLs, SP, \, + and = be encoded using xtext encoding as
skipping to change at page 5, line 15 skipping to change at page 5, line 15
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
///Add comment about which where each type is used
utf-8-addr-xtext = xtext utf-8-addr-xtext = xtext
; xtext is defined in [RFC3461]. ; xtext is defined in [RFC3461].
; When xtext encoding is removed, ; When xtext encoding is removed,
; the syntax MUST conform to ; the syntax MUST conform to
; 'utf-8-addr-unitext'. ; 'utf-8-addr-unitext'.
utf-8-addr-unitext = 1*(QUCHAR / EmbeddedUnicodeChar) utf-8-addr-unitext = 1*(QUCHAR / EmbeddedUnicodeChar)
; MUST follow 'utf-8-address' ABNF when ; MUST follow 'utf-8-address' ABNF when
; dequoted ; dequoted
skipping to change at page 7, line 42 skipping to change at page 7, line 42
diagnostic-code-field = diagnostic-code-field =
"Diagnostic-Code" ":" diagnostic-type ";" *text "Diagnostic-Code" ":" diagnostic-type ";" *text
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
utf8-text = %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
UTFMB ; Same as <text> from RFC 2822, but without <obs-text>.
; If/when RFC 2822 to disallow <obs-text>, this should become
; just <text>
UTFMB = UTF2 / UTF3 / UTF4 utf8-text = text-fixed / UTF8-non-ascii
UTF8-non-ascii = UTF2 / UTF3 / UTF4
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 10, line 49 skipping to change at page 10, line 49
US-ASCII characters not permitted in the ORCPT parameter (e.g. US-ASCII characters not permitted in the ORCPT parameter (e.g.
the ORCPT parameter forbids SP and the = characters); the ORCPT parameter forbids SP and the = characters);
3. or in a 7-bit transport environment including a message/ 3. or in a 7-bit transport environment including a message/
delivery-status Original-Recipient or Final-Recipient field. delivery-status Original-Recipient or Final-Recipient field.
The utf-8-addr-xtext form MUST be used instead in the first case, the The utf-8-addr-xtext form MUST be used instead in the first case, the
utf-8-addr-unitext form MUST be used in the other two cases. The utf-8-addr-unitext form MUST be used in the other two cases. The
utf-8-address form MAY be used in the ORCPT parameter when the SMTP utf-8-address form MAY be used in the ORCPT parameter when the SMTP
server also advertises support for UTF8SMTP and the address doesn't server also advertises support for UTF8SMTP and the address doesn't
contains any US-ASCII characters not permitted in the ORCPT contain any US-ASCII characters not permitted in the ORCPT parameter;
parameter; in a message/global-delivery-status Original-Recipient or in a message/global-delivery-status Original-Recipient or Final-
Final-Recipient DSN field; or in an Original-Recipient header field Recipient DSN field; or in an Original-Recipient header field
[RFC3798] if the message is a UTF8SMTP message. [RFC3798] if the message is a UTF8SMTP message.
In addition, the utf-8-addr-unitext form can be used anywhere where In addition, the utf-8-addr-unitext form can be used anywhere where
the utf-8-address form is allowed. the utf-8-address form is allowed.
6.2. Update to 'smtp' Diagnostic Type Registration 6.2. Update to 'smtp' Diagnostic Type Registration
The mail diagnostic type registry was created by RFC 3464. The The mail diagnostic type registry was created by RFC 3464. The
registration for the 'smtp' diagnostic type should be updated to registration for the 'smtp' diagnostic type should be updated to
reference RFC XXXX in addition to RFC 3464. reference RFC XXXX in addition to RFC 3464.
skipping to change at page 16, line 25 skipping to change at page 16, line 25
[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-07 (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-08 (work in email address", draft-ietf-eai-smtpext-09 (work in
progress), April 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.
8.2. Informative References 8.2. Informative References
skipping to change at page 17, line 11 skipping to change at page 17, line 11
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-04 (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 and members
of the EAI WG to help solidify this proposal. of the EAI WG to help solidify this proposal.
Appendix B. Changes from -02 Appendix B. Changes from -04
Restructured <utf8-text> to be more clear about how it relates to RFC
2822 <text>.
Appendix C. Changes from -03
Addressed editorial comments from Frank Ellermann and
sm+ietf@elandsys.com.
Moved EAI-downgrade to the Informative References.
Updated references.
Deleted the list of open issues.
Fixed IDnits.
Appendix D. Changes from -02
Make the space between UTF-8 and ASCII address mandatory. Make the space between UTF-8 and ASCII address mandatory.
Appendix C. Changes from -01 Changed all MIME types to be message/global-*.
Clarified that new message/global-* MIME types are semantically
equivalent to the corresponding RFC 3464 MIME types.
Added a requirement not to downgrade non-delivery reports.
Deleted unused RFC 3501 reference and updated other references.
Appendix E. 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 D. Changes from -00 Appendix F. 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.
 End of changes. 15 change blocks. 
23 lines changed or deleted 53 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/