draft-ietf-appsawg-mdn-3798bis-13.txt   draft-ietf-appsawg-mdn-3798bis-14.txt 
Network Working Group T. Hansen, Ed. Network Working Group T. Hansen, Ed.
Internet-Draft AT&T Laboratories Internet-Draft AT&T Laboratories
Obsoletes: 3798 (if approved) A. Melnikov, Ed. Obsoletes: 3798 (if approved) A. Melnikov, Ed.
Updates: 2046, 3461 (if approved) Isode Ltd Updates: 2046, 3461 (if approved) Isode Ltd
Intended status: Standards Track October 16, 2016 Intended status: Standards Track October 16, 2016
Expires: April 19, 2017 Expires: April 19, 2017
Message Disposition Notification Message Disposition Notification
draft-ietf-appsawg-mdn-3798bis-13.txt draft-ietf-appsawg-mdn-3798bis-14.txt
Abstract Abstract
This memo defines a MIME content-type that may be used by a mail user This memo defines a MIME content-type that may be used by a mail user
agent (MUA) or electronic mail gateway to report the disposition of a agent (MUA) or electronic mail gateway to report the disposition of a
message after it has been successfully delivered to a recipient. message after it has been successfully delivered to a recipient.
This content-type is intended to be machine-processable. Additional This content-type is intended to be machine-processable. Additional
message header fields are also defined to permit Message Disposition message header fields are also defined to permit Message Disposition
Notifications (MDNs) to be requested by the sender of a message. The Notifications (MDNs) to be requested by the sender of a message. The
purpose is to extend Internet Mail to support functionality often purpose is to extend Internet Mail to support functionality often
skipping to change at page 2, line 42 skipping to change at page 2, line 42
1.3. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4 1.3. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
2. Requesting Message Disposition Notifications . . . . . . . . 5 2. Requesting Message Disposition Notifications . . . . . . . . 5
2.1. The Disposition-Notification-To Header . . . . . . . . . 5 2.1. The Disposition-Notification-To Header . . . . . . . . . 5
2.2. The Disposition-Notification-Options Header . . . . . . . 7 2.2. The Disposition-Notification-Options Header . . . . . . . 7
2.3. The Original-Recipient Header Field . . . . . . . . . . . 8 2.3. The Original-Recipient Header Field . . . . . . . . . . . 8
2.4. Use with the Message/Partial Media Type . . . . . . . . . 9 2.4. Use with the Message/Partial Media Type . . . . . . . . . 9
3. Format of a Message Disposition Notification . . . . . . . . 10 3. Format of a Message Disposition Notification . . . . . . . . 10
3.1. The message/disposition-notification Media Type . . . . . 11 3.1. The message/disposition-notification Media Type . . . . . 11
3.2. Message/disposition-notification Content Fields . . . . . 14 3.2. Message/disposition-notification Content Fields . . . . . 14
3.3. Extension-fields . . . . . . . . . . . . . . . . . . . . 20 3.3. Extension-fields . . . . . . . . . . . . . . . . . . . . 20
4. Timeline of events . . . . . . . . . . . . . . . . . . . . . 21 4. Timeline of events . . . . . . . . . . . . . . . . . . . . . 20
5. Conformance and Usage Requirements . . . . . . . . . . . . . 22 5. Conformance and Usage Requirements . . . . . . . . . . . . . 22
6. Security Considerations . . . . . . . . . . . . . . . . . . . 23 6. Security Considerations . . . . . . . . . . . . . . . . . . . 22
6.1. Forgery . . . . . . . . . . . . . . . . . . . . . . . . . 23 6.1. Forgery . . . . . . . . . . . . . . . . . . . . . . . . . 23
6.2. Privacy . . . . . . . . . . . . . . . . . . . . . . . . . 23 6.2. Privacy . . . . . . . . . . . . . . . . . . . . . . . . . 23
6.3. Non-Repudiation . . . . . . . . . . . . . . . . . . . . . 24 6.3. Non-Repudiation . . . . . . . . . . . . . . . . . . . . . 24
6.4. Mail Bombing . . . . . . . . . . . . . . . . . . . . . . 24 6.4. Mail Bombing . . . . . . . . . . . . . . . . . . . . . . 24
7. Collected ABNF Grammar . . . . . . . . . . . . . . . . . . . 25 7. Collected ABNF Grammar . . . . . . . . . . . . . . . . . . . 24
8. Guidelines for Gatewaying MDNs . . . . . . . . . . . . . . . 27 8. Guidelines for Gatewaying MDNs . . . . . . . . . . . . . . . 27
8.1. Gatewaying from other mail systems to MDNs . . . . . . . 27 8.1. Gatewaying from other mail systems to MDNs . . . . . . . 27
8.2. Gatewaying from MDNs to other mail systems . . . . . . . 28 8.2. Gatewaying from MDNs to other mail systems . . . . . . . 27
8.3. Gatewaying of MDN-requests to other mail systems . . . . 28 8.3. Gatewaying of MDN-requests to other mail systems . . . . 28
9. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 9. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29
10.1. Disposition-Notification-Options header field 10.1. Disposition-Notification-Options header field
disposition-notification-parameter names . . . . . . . . 31 disposition-notification-parameter names . . . . . . . . 30
10.2. Disposition modifier names . . . . . . . . . . . . . . . 32 10.2. Disposition modifier names . . . . . . . . . . . . . . . 31
10.3. MDN extension field names . . . . . . . . . . . . . . . 32 10.3. MDN extension field names . . . . . . . . . . . . . . . 31
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 32 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 31
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 33 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 32
12.1. Normative References . . . . . . . . . . . . . . . . . . 33 12.1. Normative References . . . . . . . . . . . . . . . . . . 32
12.2. Informative References . . . . . . . . . . . . . . . . . 34 12.2. Informative References . . . . . . . . . . . . . . . . . 33
Appendix A. Changes from RFC 3798 . . . . . . . . . . . . . . . 35 Appendix A. Changes from RFC 3798 . . . . . . . . . . . . . . . 34
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 36 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 35
1. Introduction 1. Introduction
This memo defines a media type [RFC2046] for message disposition This memo defines a media type [RFC2046] for message disposition
notifications (MDNs). An MDN can be used to notify the sender of a notifications (MDNs). An MDN can be used to notify the sender of a
message of any of several conditions that may occur after successful message of any of several conditions that may occur after successful
delivery, such as display of the message contents, printing of the delivery, such as display of the message contents, printing of the
message, deletion (without display) of the message, or the message, deletion (without display) of the message, or the
recipient's refusal to provide MDNs. The "message/disposition- recipient's refusal to provide MDNs. The "message/disposition-
notification" content-type defined herein is intended for use within notification" content-type defined herein is intended for use within
skipping to change at page 13, line 22 skipping to change at page 13, line 22
more "fields" formatted according to the ABNF of RFC-MSGFMT [RFC5322] more "fields" formatted according to the ABNF of RFC-MSGFMT [RFC5322]
header "fields". The syntax of the message/disposition-notification header "fields". The syntax of the message/disposition-notification
content is as follows: content is as follows:
disposition-notification-content = [ reporting-ua-field CRLF ] disposition-notification-content = [ reporting-ua-field CRLF ]
[ mdn-gateway-field CRLF ] [ mdn-gateway-field CRLF ]
[ original-recipient-field CRLF ] [ original-recipient-field CRLF ]
final-recipient-field CRLF final-recipient-field CRLF
[ original-message-id-field CRLF ] [ original-message-id-field CRLF ]
disposition-field CRLF disposition-field CRLF
*( failure-field CRLF )
*( error-field CRLF ) *( error-field CRLF )
*( extension-field CRLF ) *( extension-field CRLF )
extension-field = extension-field-name ":" *([FWS] text) extension-field = extension-field-name ":" *([FWS] text)
extension-field-name = field-name extension-field-name = field-name
Note that the order of the above fields is recommended, but not Note that the order of the above fields is recommended, but not
fixed. Extension fields can appear anywhere. fixed. Extension fields can appear anywhere.
skipping to change at page 26, line 14 skipping to change at page 26, line 4
"Original-Recipient" ":" OWS address-type OWS ";" OWS generic-address OWS CRLF "Original-Recipient" ":" OWS address-type OWS ";" OWS generic-address OWS CRLF
Report content: Report content:
disposition-notification-content = disposition-notification-content =
[ reporting-ua-field CRLF ] [ reporting-ua-field CRLF ]
[ mdn-gateway-field CRLF ] [ mdn-gateway-field CRLF ]
[ original-recipient-field CRLF ] [ original-recipient-field CRLF ]
final-recipient-field CRLF final-recipient-field CRLF
[ original-message-id-field CRLF ] [ original-message-id-field CRLF ]
disposition-field CRLF disposition-field CRLF
*( failure-field CRLF )
*( error-field CRLF ) *( error-field CRLF )
*( extension-field CRLF ) *( extension-field CRLF )
address-type = atom address-type = atom
mta-name-type = atom mta-name-type = atom
reporting-ua-field = "Reporting-UA" ":" OWS ua-name OWS [ ";" OWS ua-product OWS ] reporting-ua-field = "Reporting-UA" ":" OWS ua-name OWS [ ";" OWS ua-product OWS ]
ua-name = *text-no-semi ua-name = *text-no-semi
skipping to change at page 35, line 30 skipping to change at page 34, line 35
Removed discussion of using source routes with MDNs, as source route Removed discussion of using source routes with MDNs, as source route
is a deprecated Email feature. is a deprecated Email feature.
The values of "dispatched" and "processed" were lost from the ABNF The values of "dispatched" and "processed" were lost from the ABNF
for "disposition-type". (Erratum #691) for "disposition-type". (Erratum #691)
Because the warning disposition modifier was previously removed, Because the warning disposition modifier was previously removed,
warning-field has also been removed. (Erratum #692) warning-field has also been removed. (Erratum #692)
Because the failed disposition type was previously removed, failure-
field has also been removed.
The ABNF for ua-name and ua-product included semi-colon, which could The ABNF for ua-name and ua-product included semi-colon, which could
not be distinguished from *text in the production. The ua-name was not be distinguished from *text in the production. The ua-name was
restricted to not include semi-colon. Semi-colon can still appear in restricted to not include semi-colon. Semi-colon can still appear in
the ua-product. the ua-product.
Removed recommendation to include the MUA DNS host name in the Removed recommendation to include the MUA DNS host name in the
"Reporting-UA" MDN field. "Reporting-UA" MDN field.
The ABNF did not indicate all places that whitespace was allowable, The ABNF did not indicate all places that whitespace was allowable,
in particular folding whitespace, although all implementations allow in particular folding whitespace, although all implementations allow
 End of changes. 10 change blocks. 
18 lines changed or deleted 19 lines changed or added

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