draft-ietf-appsawg-mdn-3798bis-08.txt   draft-ietf-appsawg-mdn-3798bis-09.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 June 25, 2016 Intended status: Standards Track July 31, 2016
Expires: December 27, 2016 Expires: February 1, 2017
Message Disposition Notification Message Disposition Notification
draft-ietf-appsawg-mdn-3798bis-08.txt draft-ietf-appsawg-mdn-3798bis-09.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 7 skipping to change at page 2, line 7
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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."
This Internet-Draft will expire on December 27, 2016. This Internet-Draft will expire on February 1, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 41 skipping to change at page 2, line 41
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 . . . . . . . . . . . . . . . . . . . . . 21
5. Conformance and Usage Requirements . . . . . . . . . . . . . 22 5. Conformance and Usage Requirements . . . . . . . . . . . . . 22
6. Security Considerations . . . . . . . . . . . . . . . . . . . 22 6. Security Considerations . . . . . . . . . . . . . . . . . . . 23
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 . . . . . . . . . . . . . . . . . . . 24 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 . . . . . . . 27 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 9. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29 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 . . . . . . . . 30
10.2. Disposition modifier names . . . . . . . . . . . . . . . 31 10.2. Disposition modifier names . . . . . . . . . . . . . . . 31
10.3. MDN extension field names . . . . . . . . . . . . . . . 31 10.3. MDN extension field names . . . . . . . . . . . . . . . 31
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 31 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 32
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 32 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 32
12.1. Normative References . . . . . . . . . . . . . . . . . . 32 12.1. Normative References . . . . . . . . . . . . . . . . . . 32
12.2. Informative References . . . . . . . . . . . . . . . . . 33 12.2. Informative References . . . . . . . . . . . . . . . . . 33
Appendix A. Changes from RFC 3798 . . . . . . . . . . . . . . . 34 Appendix A. Changes from RFC 3798 . . . . . . . . . . . . . . . 34
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 35 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
skipping to change at page 18, line 15 skipping to change at page 18, line 15
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
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. Unless prescribed otherwise in performed action. (This might include the case
a particular mail environment, in order to when the user has manually configured her MUA to
preserve user's privacy, this is the default for automatically respond to valid MDN requests.)
MUAs. Unless prescribed otherwise in a particular mail
environment, in order to preserve user's privacy,
this MUST be the default for MUAs.
"automatic-action" The disposition described by the disposition type "automatic-action" The disposition described by the disposition type
was a result of an automatic action, rather than was a result of an automatic action, rather than
an explicit instruction by the user for this an explicit instruction by the user for this
message. For example, this might be set if the message. This is typically generated by a Mail
user configured her MUA to always respond to MDN Delivery Agent (e.g. MDN generations by Sieve
requests without asking for confirmation. Other reject action [RFC5429], Fax-over-Email
examples include MDN generations by Sieve reject [RFC3249], Voice Messaging System (VPIM)
action [RFC5429], Fax-over-Email [RFC3249] or [RFC3801] or upon delivery to a mailing list).
Voice Messaging System (VPIM) [RFC3801].
"Manual-action" and "automatic-action" are mutually exclusive. One "Manual-action" and "automatic-action" are mutually exclusive. One
or the other MUST be specified. or the other MUST be specified.
The following sending modes are defined: The following sending modes are defined:
"MDN-sent-manually" The user explicitly gave permission for this "MDN-sent-manually" The user explicitly gave permission for this
particular MDN to be sent. Unless prescribed particular MDN to be sent. Unless prescribed
otherwise in a particular mail environment, in otherwise in a particular mail environment, in
order to preserve user's privacy, this is the order to preserve user's privacy, this MUST be
default for MUAs. the default for MUAs.
"MDN-sent-automatically" The MDN was sent because the MUA had "MDN-sent-automatically" The MDN was sent because the MUA had
previously been configured to do so previously been configured to do so
automatically. automatically.
"MDN-sent-manually" and "MDN-sent-automatically" are mutually "MDN-sent-manually" and "MDN-sent-automatically" are mutually
exclusive. One or the other MUST be specified. exclusive. One or the other MUST be specified.
3.2.6.2. Disposition types 3.2.6.2. Disposition types
skipping to change at page 21, line 12 skipping to change at page 21, line 12
fields should begin with an indication of the MUA implementation fields should begin with an indication of the MUA implementation
that produced the MDN (e.g., Foomail-information). that produced the MDN (e.g., Foomail-information).
4. Timeline of events 4. Timeline of events
The following timeline shows when various events in the processing of The following timeline shows when various events in the processing of
a message and generation of MDNs take place: a message and generation of MDNs take place:
-- User composes message -- User composes message
-- User tells MUA to send message -- User tells MUA to send message.
-- MUA passes message to MTA (original recipient information passed -- MUA passes message to Mail Submission Agent (MSA), original
along) recipient information passed along.
-- MTA sends message to next MTA -- MSA sends message to next MTA.
-- Final MTA receives message -- Final MTA receives message.
-- Final MTA delivers message to MUA (possibly generating a Delivery -- Final MTA delivers message to recipient's mailbox (possibly
Status Notification (DSN)) generating a Delivery Status Notification (DSN)).
-- (Recipient's) MUA discovers a new message in recipient's mailbox
and decides whether an MDN should be generated. If the MUA has
information that an MDN has been generated for this message, no
further MDN processing described below is performed. If MUA
decides that no MDN can be generated, no further MDN processing
described below is performed.
-- MUA performs automatic processing and might generate corresponding -- MUA performs automatic processing and might generate corresponding
MDNs ("dispatched", "processed" or "deleted" disposition type with MDNs ("dispatched", "processed" or "deleted" disposition type with
"automatic-action" and "MDN-sent-automatically" disposition modes) "automatic-action" and "MDN-sent-automatically" disposition
modes). The MUA remembers that an MDN was generated.
-- MUA displays list of messages to user -- MUA displays list of messages to user.
-- User selects a message and requests that some action be performed -- User selects a message and requests that some action be performed
on it. on it.
-- MUA performs requested action; if an automatic MDN has not already -- MUA performs requested action; if an automatic MDN has not already
been generated, with user's permission, sends an appropriate MDN been generated, with user's permission, sends an appropriate MDN
("displayed", "dispatched", "processed", or "deleted" disposition ("displayed", "dispatched", "processed", or "deleted" disposition
type, with "manual-action" and "MDN-sent-manually" or "MDN-sent- type, with "manual-action" and "MDN-sent-manually" or "MDN-sent-
automatically" disposition mode). automatically" disposition mode). The MUA remembers that an MDN
was generated.
-- User possibly performs other actions on message, but no further -- User possibly performs other actions on message, but no further
MDNs are generated. MDNs are generated.
5. Conformance and Usage Requirements 5. Conformance and Usage Requirements
An MUA or gateway conforms to this specification if it generates MDNs An MUA or gateway conforms to this specification if it generates MDNs
according to the protocol defined in this memo. It is not necessary according to the protocol defined in this memo. It is not necessary
to be able to generate all of the possible values of the Disposition to be able to generate all of the possible values of the Disposition
field. field.
 End of changes. 19 change blocks. 
32 lines changed or deleted 42 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/