draft-ietf-appsawg-mdn-3798bis-09.txt   draft-ietf-appsawg-mdn-3798bis-10.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 July 31, 2016 Intended status: Standards Track July 31, 2016
Expires: February 1, 2017 Expires: February 1, 2017
Message Disposition Notification Message Disposition Notification
draft-ietf-appsawg-mdn-3798bis-09.txt draft-ietf-appsawg-mdn-3798bis-10.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 3, line 6 skipping to change at page 3, line 6
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 . . . . . . . . . . . . . . . . . . . 25
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 . . . . . . . 28
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30
10.1. Disposition-Notification-Options header field 10.1. Disposition-Notification-Options header field
disposition-notification-parameter names . . . . . . . . 30 disposition-notification-parameter names . . . . . . . . 31
10.2. Disposition modifier names . . . . . . . . . . . . . . . 31 10.2. Disposition modifier names . . . . . . . . . . . . . . . 32
10.3. MDN extension field names . . . . . . . . . . . . . . . 31 10.3. MDN extension field names . . . . . . . . . . . . . . . 32
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 32 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 32
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 32 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 33
12.1. Normative References . . . . . . . . . . . . . . . . . . 32 12.1. Normative References . . . . . . . . . . . . . . . . . . 33
12.2. Informative References . . . . . . . . . . . . . . . . . 33 12.2. Informative References . . . . . . . . . . . . . . . . . 34
Appendix A. Changes from RFC 3798 . . . . . . . . . . . . . . . 34 Appendix A. Changes from RFC 3798 . . . . . . . . . . . . . . . 35
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 35 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 36
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 18, line 10 skipping to change at page 18, line 10
disposition-modifier = "error" / disposition-modifier-extension disposition-modifier = "error" / disposition-modifier-extension
disposition-modifier-extension = atom disposition-modifier-extension = atom
The disposition-mode, disposition-type, and disposition-modifier The disposition-mode, disposition-type, and disposition-modifier
values may be spelled in any combination of upper and lower case US- values may be spelled in any combination of upper and lower case US-
ASCII characters. ASCII characters.
3.2.6.1. Disposition modes 3.2.6.1. Disposition modes
Disposition mode consists of 2 parts: action mode and sending mode.
The following action modes are defined: The following action modes are defined:
"manual-action" The disposition described by the disposition type "manual-action" The disposition described by the disposition type
was a result of an explicit instruction by the was a result of an explicit instruction by the
user rather than some sort of automatically user rather than some sort of automatically
performed action. (This might include the case performed action. (This might include the case
when the user has manually configured her MUA to when the user has manually configured her MUA to
automatically respond to valid MDN requests.) automatically respond to valid MDN requests.)
Unless prescribed otherwise in a particular mail Unless prescribed otherwise in a particular mail
environment, in order to preserve user's privacy, environment, in order to preserve user's privacy,
skipping to change at page 23, line 47 skipping to change at page 24, line 5
If the Disposition-Notification-To header field is passed on If the Disposition-Notification-To header field is passed on
unmodified when a message is distributed to the subscribers of a unmodified when a message is distributed to the subscribers of a
mailing list, the subscribers to the list may be revealed to the mailing list, the subscribers to the list may be revealed to the
sender of the original message by the generation of MDNs. sender of the original message by the generation of MDNs.
Headers of the original message returned in part 3 of the multipart/ Headers of the original message returned in part 3 of the multipart/
report could reveal confidential information about host names and/or report could reveal confidential information about host names and/or
network topology inside a firewall. network topology inside a firewall.
Disposition mode (Section 3.2.6.1) can leak information about
recipient's MUA configuration, in particular whether MDNs are
acknowledged manually or automatically. If this is a concern, MUAs
can return "manual-action/MDN-sent-manually" disposition mode in
generated MDNs.
An unencrypted MDN could reveal confidential information about an An unencrypted MDN could reveal confidential information about an
encrypted message, especially if all or part of the original message encrypted message, especially if all or part of the original message
is returned in part 3 of the multipart/report. Encrypted MDNs are is returned in part 3 of the multipart/report. Encrypted MDNs are
not defined in this specification. not defined in this specification.
In general, any optional MDN field may be omitted if the Reporting In general, any optional MDN field may be omitted if the Reporting
MUA site or user determines that inclusion of the field would impose MUA site or user determines that inclusion of the field would impose
too great a compromise of site confidentiality. The need for such too great a compromise of site confidentiality. The need for such
confidentiality must be balanced against the utility of the omitted confidentiality must be balanced against the utility of the omitted
information in MDNs. information in MDNs.
 End of changes. 5 change blocks. 
9 lines changed or deleted 17 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/