Message Disposition Notification
RFC 8098
| Document | Type |
RFC - Internet Standard
(February 2017; No errata)
Obsoletes RFC 3798
Also known as STD 85
|
|
|---|---|---|---|
| Authors | Tony Hansen , Alexey Melnikov | ||
| Last updated | 2018-12-20 | ||
| Replaces | draft-hansen-mdn-3798bis | ||
| Stream | IETF | ||
| Formats | plain text html pdf htmlized bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Murray Kucherawy | ||
| Shepherd write-up | Show (last changed 2016-04-02) | ||
| IESG | IESG state | RFC 8098 (Internet Standard) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Ben Campbell | ||
| IESG note | Please note that this draft intends to move MDN to Internet Standard. | ||
| Send notices to | Barry Leiba <barryleiba@computer.org> | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | RFC-Ed-Ack | ||
Internet Engineering Task Force (IETF) T. Hansen, Ed.
Request for Comments: 8098 AT&T Laboratories
STD: 85 A. Melnikov, Ed.
Obsoletes: 3798 Isode Ltd
Updates: 2046, 3461 February 2017
Category: Standards Track
ISSN: 2070-1721
Message Disposition Notification
Abstract
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
message after it has been successfully delivered to a recipient.
This content type is intended to be machine processable. Additional
message header fields are also defined to permit Message Disposition
Notifications (MDNs) to be requested by the sender of a message. The
purpose is to extend Internet Mail to support functionality often
found in other messaging systems, such as X.400 and the proprietary
"LAN-based" systems, and are often referred to as "read receipts,"
"acknowledgements," or "receipt notifications." The intention is to
do this while respecting privacy concerns, which have often been
expressed when such functions have been discussed in the past.
Because many messages are sent between the Internet and other
messaging systems (such as X.400 or the proprietary "LAN-based"
systems), the MDN protocol is designed to be useful in a
multiprotocol messaging environment. To this end, the protocol
described in this memo provides for the carriage of "foreign"
addresses, in addition to those normally used in Internet Mail.
Additional attributes may also be defined to support "tunneling" of
foreign notifications through Internet Mail.
This document is an Internet Standard. It obsoletes RFC 3798 and
updates RFC 2046 (message/partial media type handling) and RFC 3461
(Original-Recipient header field generation requirement).
Hansen & Melnikov Standards Track [Page 1]
RFC 8098 MDN February 2017
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc8098.
Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Hansen & Melnikov Standards Track [Page 2]
RFC 8098 MDN February 2017
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. Purposes . . . . . . . . . . . . . . . . . . . . . . . . 4
1.2. Requirements . . . . . . . . . . . . . . . . . . . . . . 4
1.3. Terminology . . . . . . . . . . . . . . . . . . . . . . . 5
2. Requesting Message Disposition Notifications . . . . . . . . 5
2.1. The Disposition-Notification-To Header . . . . . . . . . 5
2.2. The Disposition-Notification-Options Header . . . . . . . 8
2.3. The Original-Recipient Header Field . . . . . . . . . . . 9
2.4. Use with the Message/Partial Media Type . . . . . . . . . 10
3. Format of a Message Disposition Notification . . . . . . . . 10
3.1. The Message/Disposition-Notification Media Type . . . . . 12
3.2. Message/Disposition-Notification Content Fields . . . . . 15
3.3. Extension-Fields . . . . . . . . . . . . . . . . . . . . 21
4. Timeline of Events . . . . . . . . . . . . . . . . . . . . . 22
5. Conformance and Usage Requirements . . . . . . . . . . . . . 23
6. Security Considerations . . . . . . . . . . . . . . . . . . . 24
6.1. Forgery . . . . . . . . . . . . . . . . . . . . . . . . . 24
6.2. Privacy . . . . . . . . . . . . . . . . . . . . . . . . . 24
6.2.1. Disclosure of Product Information . . . . . . . . . . 25
Show full document text