Surety is performing system maintenance this weekend. Electronic date stamps on new Prior Art Database disclosures may be delayed.
Browse Prior Art Database

Message Disposition Notification (RFC8098)

IP.com Disclosure Number: IPCOM000249490D
Original Publication Date: 2017-Feb-01
Included in the Prior Art Database: 2017-Mar-01
Document File: 74 page(s) / 81K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

T. Hansen: AUTHOR [+4]


This memo defines a media type [RFC2046] for Message Disposition Notifications (MDNs). An MDN can be used to notify the sender of a message of any of several conditions that may occur after successful delivery, such as display of the message contents, printing of the message, deletion (without display) of the message, or the recipient's refusal to provide MDNs. The "message/disposition- notification" content type defined herein is intended for use within the framework of the "multipart/report" content type defined in RFC-REPORT [RFC6522].

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 3% of the total text.

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


   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 stat...