draft-ietf-eai-dsn-01.txt   draft-ietf-eai-dsn-02.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 June 12, 2007 Intended status: Experimental July 1, 2007
Expires: December 14, 2007 Expires: January 2, 2008
International Delivery and Disposition Notifications International Delivery and Disposition Notifications
draft-ietf-eai-dsn-01.txt draft-ietf-eai-dsn-02.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 December 14, 2007. This Internet-Draft will expire on January 2, 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 15 skipping to change at page 2, line 15
for delivery status notifications and message disposition for delivery status notifications and message disposition
notifications to support use of the new address type. notifications to support use of the new address type.
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 . . . . . . . . . . . . . 5 4. UTF-8 Delivery Status Notifications . . . . . . . . . . . . . 6
5. UTF-8 Message Disposition Notifications . . . . . . . . . . . 6 5. UTF-8 Message Disposition Notifications . . . . . . . . . . . 8
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
6.1. UTF-8 Mail Address Type Registration . . . . . . . . . . . 7 6.1. UTF-8 Mail Address Type Registration . . . . . . . . . . . 9
6.2. Update to 'smtp' Diagnostic Type Registration . . . . . . 8 6.2. Update to 'smtp' Diagnostic Type Registration . . . . . . 10
6.3. message/utf-8-headers . . . . . . . . . . . . . . . . . . 8 6.3. message/utf-8-headers . . . . . . . . . . . . . . . . . . 10
6.4. message/utf-8-delivery-status . . . . . . . . . . . . . . 9 6.4. message/utf-8-delivery-status . . . . . . . . . . . . . . 11
6.5. message/utf-8-disposition-notification . . . . . . . . . . 10 6.5. message/utf-8-disposition-notification . . . . . . . . . . 13
7. Security Considerations . . . . . . . . . . . . . . . . . . . 12 7. Security Considerations . . . . . . . . . . . . . . . . . . . 14
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
8.1. Normative References . . . . . . . . . . . . . . . . . . . 12 8.1. Normative References . . . . . . . . . . . . . . . . . . . 15
8.2. Informative References . . . . . . . . . . . . . . . . . . 13 8.2. Informative References . . . . . . . . . . . . . . . . . . 16
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 14 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 16
Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 14 Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 16
Appendix C. Changes from -00 . . . . . . . . . . . . . . . . . . 14 Appendix C. Changes from -01 . . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14 Appendix D. Changes from -00 . . . . . . . . . . . . . . . . . . 17
Intellectual Property and Copyright Statements . . . . . . . . . . 16 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17
Intellectual Property and Copyright Statements . . . . . . . . . . 18
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 returns based on the recipient
skipping to change at page 4, line 15 skipping to change at page 4, line 15
characters not permitted in the ORCPT parameter (e.g. the ORCPT characters not permitted in the ORCPT parameter (e.g. the ORCPT
parameter forbids SP and =); or in a 7-bit transport environment parameter forbids SP and =); or in a 7-bit transport environment
including a message/delivery-status Original-Recipient or Final- including a message/delivery-status Original-Recipient or Final-
Recipient field. The utf-8-addr-xtext form (see below) MUST be used Recipient field. The utf-8-addr-xtext form (see below) MUST be used
instead in the former case, the utf-8-addr-unitext form MUST be used instead in the former case, the utf-8-addr-unitext form MUST be used
in the latter case. The utf-8-address form MAY be used in the ORCPT in the latter case. The utf-8-address form MAY be used in the ORCPT
parameter when the SMTP server also advertises support for UTF8SMTP parameter when the SMTP server also advertises support for UTF8SMTP
and the address doesn't contains any US-ASCII characters not and the address doesn't contains any US-ASCII characters not
permitted in the ORCPT parameter. It SHOULD be used in a message/ permitted in the ORCPT parameter. It SHOULD be used in a message/
utf-8-delivery-status Original-Recipient or Final-Recipient DSN utf-8-delivery-status Original-Recipient or Final-Recipient DSN
field; or an Original-Recipient header field [RFC3798] if the message field; or in an Original-Recipient header field [RFC3798] if the
is a UTF-8 header message. message is a UTF-8 header 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
described in [RFC3461]. This is described by the utf-8-addr-xtext described in [RFC3461]. This is described by the utf-8-addr-xtext
form in the ABNF below. Plane 1 Unicode characters MAY be included form in the ABNF below. Unicode characters MAY be included in a
in a utf-8 address type using a "%u####" syntax (QMIDCHAR, where # is utf-8 address type using a "\x{HEXPOINT}" syntax, where HEXPOINT is 2
a hexadecimal digit) and other Unicode characters MAY be encoded to 6 hexadecimal digits. When sending data to a UTF8SMTP capable
using "%U########" syntax (QHIGHCHAR). When sending data to a server, native UTF-8 characters SHOULD be used instead of the
UTF8SMTP capable server, native UTF-8 characters SHOULD be used QMIDCHAR and QHIGHCHAR encodings described below. When sending data
instead of the QMIDCHAR and QHIGHCHAR encodings described below. to an SMTP server which does not advertise UTF8SMTP, then the
When sending data to an SMTP server which does not advertise QMIDCHAR and QHIGHCHAR encodings MUST be used instead of UTF-8.
UTF8SMTP, then the QMIDCHAR and QHIGHCHAR encodings MUST be used
instead of UTF-8.
When the ORCPT parameter is placed in a message/utf-8-delivery-status When the ORCPT parameter is placed in a message/utf-8-delivery-status
Original-Recipient field, the utf-8-addr-xtext form of the utf-8 Original-Recipient field, the utf-8-addr-xtext form of the utf-8
address type SHOULD be converted to the 'utf-8-address' form (see the address type SHOULD be converted to the 'utf-8-address' form (see the
ABNF below) by removing all xtext encoding first (which will result ABNF below) by removing all xtext encoding first (which will result
in the 'utf-8-addr-unitext' form), followed by removal of the in the 'utf-8-addr-unitext' form), followed by removal of the
'unitext' encoding. However, if an address is labeled with the utf-8 'unitext' encoding. However, if an address is labeled with the utf-8
address type but does not conform to utf-8 syntax, then it MUST be address type but does not conform to utf-8 syntax, then it MUST be
copied into the message/utf-8-delivery-status field without copied into the message/utf-8-delivery-status field without
alteration. alteration.
The ability to encode characters with the QMIDCHAR or QHIGHCHAR 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.
utf-8-type-addr = "utf-8;" utf-8-enc-addr utf-8-type-addr = "utf-8;" utf-8-enc-addr
utf-8-address = uMailbox [ *WSP "<" Mailbox ">" ] utf-8-address = uMailbox [ *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].
skipping to change at page 5, line 27 skipping to change at page 5, line 27
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
///Exclude '\'? QUCHAR = %x21-2a / %x2c-3c / %x3e-5b / %x5d-7e /
QUCHAR = %x21-2a / %x2c-3c / %x3e-7e /
UTF8-2 / UTF8-3 / UTF8-4 UTF8-2 / UTF8-3 / UTF8-4
; Printable except CTLs, SP, + and = ; Printable except CTLs, SP, '\', '+' and '='
EmbeddedUnicodeChar = %x5C.78 "{" HEXPOINT "}" EmbeddedUnicodeChar = %x5C.78 "{" HEXPOINT "}"
; starts with "\x" ; starts with "\x"
HEXPOINT = "5C" / ( NZHEXDIG 2*4HEXDIG ) / ( "10" 4*HEXDIG ) HEXPOINT = "5C" / (HEXDIG8 HEXDIG) / ; 2 digit forms
( NZHEXDIG 2(HEXDIG) ) / ; 3 digit forms
( NZDHEXDIG 3(HEXDIG) ) /
( "D" %x30-37 2(HEXDIG) ) /
; 4 digit forms excluding surrogate
( NZHEXDIG 4(HEXDIG) ) / ; 5 digit forms
( "10" 4*HEXDIG ) ; 6 digit forms
; represents either "\" or a Unicode code point outside the ; represents either "\" or a Unicode code point outside the
; US-ASCII repertoire ; US-ASCII repertoire
HEXDIG8 = %x38-39 / "A" / "B" / "C" / "D" / "E" / "F"
; HEXDIG excluding 0-7
NZHEXDIG = %x31-39 / "A" / "B" / "C" / "D" / "E" / "F" NZHEXDIG = %x31-39 / "A" / "B" / "C" / "D" / "E" / "F"
; HEXDIG excluding "0" ; HEXDIG excluding "0"
NZDHEXDIG = %x31-39 / "A" / "B" / "C" / "E" / "F"
; HEXDIG excluding "0" and "D"
4. UTF-8 Delivery Status Notifications 4. UTF-8 Delivery Status Notifications
A traditional delivery status notification [RFC3464] comes in a A traditional delivery status notification [RFC3464] comes in a
three-part multipart/report [RFC3462] container, where the first part three-part multipart/report [RFC3462] container, where the first part
is human readable text describing the error, the second part is a is human readable text describing the error, the second part is a
7-bit-only message/delivery-status and the optional third part is 7-bit-only message/delivery-status and the optional third part is
used for content (message/rfc822) or header (text/rfc822-headers) used for content (message/rfc822) or header (text/rfc822-headers)
return. An SMTP server which advertises both UTF8SMTP and DSN SHOULD return. An SMTP server which advertises both UTF8SMTP and DSN SHOULD
return an undeliverable UTF8SMTP message without downgrading it return an undeliverable UTF8SMTP message without downgrading it
(assuming the return SMTP server supports UTF8SMTP). As the present (assuming the return SMTP server supports UTF8SMTP). As the present
DSN format does not permit this, three new media types are needed. DSN format does not permit this, three new media types are needed.
The first type, message/utf-8-delivery-status has the syntax of The first type, message/utf-8-delivery-status has the syntax of
message/delivery-status with two modifications. First, the charset message/delivery-status with three modifications. First, the charset
for message/utf-8-delivery-status is UTF-8 and thus any field MAY for message/utf-8-delivery-status is UTF-8 and thus any field MAY
contain UTF-8 characters when appropriate. (In particular, the contain UTF-8 characters when appropriate (see the ABNF below). In
Diagnostic-Code field MAY contain UTF-8 as described in UTF8SMTP particular, the Diagnostic-Code field MAY contain UTF-8 as described
[I-D.ietf-eai-smtpext].) Second, systems generating a message/ in UTF8SMTP [I-D.ietf-eai-smtpext]; the Diagnostic-Code field SHOULD
utf-8-delivery-status body part SHOULD use the utf-8-address form of be in i-default language [LANGTAGS]. Second, systems generating a
the utf-8 address type for all addresses containing characters message/utf-8-delivery-status body part SHOULD use the utf-8-address
outside the US-ASCII repertoire. These systems SHOULD up-convert the form of the utf-8 address type for all addresses containing
utf-8-addr-xtext or the utf-8-addr-unitext form of a utf-8 address characters outside the US-ASCII repertoire. These systems SHOULD up-
type in the ORCPT parameter to the utf-8-address form of a utf-8 convert the utf-8-addr-xtext or the utf-8-addr-unitext form of a
address type in the Original-Recipient field. 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
new optional field called Localized-Diagnostic is added. Each
instance includes a language tag [LANGTAGS] and contains text in the
specified language. This is equivalent to the text part of the
Diagnostic-Code field. All instances of Localized-Diagnostic MUST
use different language tags. The ABNF for message/
utf-8-delivery-status is specified below:
utf-8-delivery-status-content = per-message-fields
1*( CRLF utf-8-per-recipient-fields )
; "per-message-fields" remains unchanged from the definition
; in RFC 3464, except for the "extension-field"
; which is updated below.
utf-8-per-recipient-fields =
[ original-recipient-field CRLF ]
final-recipient-field CRLF
action-field CRLF
status-field CRLF
[ remote-mta-field CRLF ]
[ diagnostic-code-field CRLF
*(localized-diagnostic-text-field CRLF) ]
[ last-attempt-date-field CRLF ]
[ will-retry-until-field CRLF ]
*( extension-field CRLF )
; All fields except for "original-recipient-field",
; "final-recipient-field", "diagnostic-code-field"
; and "extension-field" remain unchanged from
; the definition in RFC 3464.
generic-address =/ utf-8-enc-addr
; Only allowed with the "utf-8" address-type.
;
; This indirectly updates "original-recipient-field"
; and "final-recipient-field"
diagnostic-code-field =
"Diagnostic-Code" ":" diagnostic-type ";" *text
localized-diagnostic-text-field =
"Localized-Diagnostic" ":" Language-Tag ";" *utf8-text
; "Language-Tag" is a language tag as defined in [LANGTAGS].
extension-field =/ extension-field-name ":" *utf8-text
utf8-text = %d1-9 / ; Any Unicode character except for NUL,
%d11 / ; CR and LF, encoded in UTF-8
%d12 /
%d14-127 /
UTFMB
UTFMB = UTF2 / UTF3 / UTF4
The second type, used for content return, is message/utf-8 which is The second type, used for content return, is message/utf-8 which is
similar to message/rfc822, except it contains a message with UTF-8 similar to message/rfc822, except it contains a message with UTF-8
headers. This media type is described in [I-D.ietf-eai-utf8headers]. headers. This media type is described in [I-D.ietf-eai-utf8headers].
The third type, used for header return, is message/utf-8-headers and The third type, used for header return, is message/utf-8-headers and
contains only the UTF-8 headers of a message (all lines prior to the contains only the UTF-8 headers of a message (all lines prior to the
first blank line in a UTF8SMTP message). Unlike message/utf-8, this first blank line in a UTF8SMTP message). Unlike message/utf-8, this
body part provides no difficulties for present infrastructure. body part provides no difficulties for present infrastructure.
skipping to change at page 6, line 47 skipping to change at page 8, line 29
5. UTF-8 Message Disposition Notifications 5. UTF-8 Message Disposition Notifications
Message Disposition Notifications [RFC3798] have a similar design and Message Disposition Notifications [RFC3798] have a similar design and
structure to DSNs. As a result, they use the same basic return structure to DSNs. As a result, they use the same basic return
format. When generating a MDN for a UTF-8 header message, content or format. When generating a MDN for a UTF-8 header message, content or
header return is the same as for DSNs. The second part of the header return is the same as for DSNs. The second part of the
multipart/report uses a new media type, message/ multipart/report uses a new media type, message/
utf-8-disposition-notification, which has the syntax of message/ utf-8-disposition-notification, which has the syntax of message/
disposition-notification with two modifications. First, the charset disposition-notification with two modifications. First, the charset
for message/utf-8-disposition-notification is UTF-8 and thus any for message/utf-8-disposition-notification is UTF-8 and thus any
field MAY contain UTF-8 characters when appropriate. Second, systems field MAY contain UTF-8 characters when appropriate (see the ABNF
generating a message/utf-8-disposition-notification body part below). (In particular, the failure-field, the error-field and the
(typically a mail user agent) SHOULD use the utf-8 address type for warning-field MAY contain UTF-8. These fields SHOULD be in i-default
all addresses containing characters outside the US-ASCII repertoire. language [LANGTAGS].) Second, systems generating a message/
utf-8-disposition-notification body part (typically a mail user
agent) SHOULD use the utf-8 address type for all addresses containing
characters outside the US-ASCII repertoire.
The MDN specification also defines the Original-Recipient header The MDN specification also defines the Original-Recipient header
field which is added with a copy of the contents of ORCPT at delivery field which is added with a copy of the contents of ORCPT at delivery
time. When generating an Original-Recipient header field, a delivery time. When generating an Original-Recipient header field, a delivery
agent writing a UTF-8 header message in native format SHOULD convert agent writing a UTF-8 header message in native format SHOULD convert
the utf-8-addr-xtext or the utf-8-addr-unitext form of a utf-8 the utf-8-addr-xtext or the utf-8-addr-unitext form of a utf-8
address type in the ORCPT parameter to the corresponding utf-8- address type in the ORCPT parameter to the corresponding utf-8-
address form. address form.
The MDN specification also defines the Disposition-Notification-To The MDN specification also defines the Disposition-Notification-To
header which is an address header and thus follows the same 8-bit header which is an address header and thus follows the same 8-bit
rules as other address headers such as "From" and "To" when used in a rules as other address headers such as "From" and "To" when used in a
UTF-8 header message. UTF-8 header message.
; ABNF for "original-recipient-header", "original-recipient-field"
; and "final-recipient-field" from RFC 3798 is implicitly updated
; as they use the updated "generic-address" as defined in
; section 4 of this document.
failure-field = "Failure" ":" *utf8-text
; "utf8-text" is defined in section 4 of this document.
error-field = "Error" ":" *utf8-text
; "utf8-text" is defined in section 4 of this document.
warning-field = "Warning" ":" *utf8-text
; "utf8-text" is defined in section 4 of this document.
6. IANA Considerations 6. IANA Considerations
This specification does not create any new IANA registries. However This specification does not create any new IANA registries. However
the following items are registered as a result of this document: the following items are registered as a result of this document:
6.1. UTF-8 Mail Address Type Registration 6.1. UTF-8 Mail Address Type Registration
The mail address type registry was created by RFC 3464. The The mail address type registry was created by RFC 3464. The
registration template response follows: registration template response follows:
skipping to change at page 13, line 42 skipping to change at page 15, line 49
[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-05 (work in email address", draft-ietf-eai-smtpext-05 (work in
progress), April 2007. progress), April 2007.
[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-03 (work in progress), Mar 2007. draft-ietf-eai-downgrade-03 (work in progress), Mar 2007.
[LANGTAGS]
Phillips, A. and M. Davis, "Tags for Identifying
Languages", RFC 4646, September 2006.
8.2. Informative References 8.2. Informative References
[RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail [RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
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.
skipping to change at page 14, line 31 skipping to change at page 16, line 41
Potential issue: an SMTP server can't deliver an EAI DSN to the next Potential issue: an SMTP server can't deliver an EAI DSN to the next
hop - need to use a 7bit encoding, downgrade or discard? Need to hop - need to use a 7bit encoding, downgrade or discard? Need to
describe choices. describe choices.
Tracker issue #1485: UTF8HDR 4.6/DSN: Choice of body part for Tracker issue #1485: UTF8HDR 4.6/DSN: Choice of body part for
transport of UTF8SMTP messages transport of UTF8SMTP messages
Tracker issue #1483: SMTPEXT 2.7: Non-ASCII in response texts Tracker issue #1483: SMTPEXT 2.7: Non-ASCII in response texts
Appendix C. Changes from -00 Appendix C. Changes from -01
Cleaned up and tightened ABNF, in particular HEXPOINT.
Extended DSN report syntax to allow for localized version of
diagnostic-code-field.
Added ABNF for the EAI DSN and EAI MDN.
Appendix D. 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. 19 change blocks. 
53 lines changed or deleted 143 lines changed or added

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