Message Disposition Notification
draft-ietf-appsawg-mdn-3798bis-16

Document Type Active Internet-Draft (appsawg WG)
Last updated 2016-12-09 (latest revision 2016-12-01)
Replaces draft-hansen-mdn-3798bis
Stream IETF
Intended RFC status Internet Standard
Formats plain text xml pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication May 2016
Document shepherd Murray Kucherawy
Shepherd write-up Show (last changed 2016-04-02)
IESG IESG state RFC Ed Queue
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
RFC Editor RFC Editor state EDIT
Network Working Group                                     T. Hansen, Ed.
Internet-Draft                                         AT&T Laboratories
Obsoletes: 3798 (if approved)                           A. Melnikov, Ed.
Updates: 2046, 3461 (if approved)                              Isode Ltd
Intended status: Standards Track                        December 1, 2016
Expires: June 4, 2017

                    Message Disposition Notification
                 draft-ietf-appsawg-mdn-3798bis-16.txt

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 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 multi-
   protocol 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 obsoletes RFC 3798, moving it to Internet Standard.  It
   also updates RFC 2046 (message/partial Media Type handling) and RFC
   3461 (Original-Recipient header field generation requirement).

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

Hansen & Melnikov         Expires June 4, 2017                  [Page 1]
Internet-Draft                     MDN                     December 2016

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on June 4, 2017.

Copyright Notice

   Copyright (c) 2016 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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Purposes  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Requirements  . . . . . . . . . . . . . . . . . . . . . .   4
     1.3.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Requesting Message Disposition Notifications  . . . . . . . .   5
     2.1.  The Disposition-Notification-To Header  . . . . . . . . .   5
     2.2.  The Disposition-Notification-Options Header . . . . . . .   7
     2.3.  The Original-Recipient Header Field . . . . . . . . . . .   8
     2.4.  Use with the Message/Partial Media Type . . . . . . . . .   9
   3.  Format of a Message Disposition Notification  . . . . . . . .  10
     3.1.  The message/disposition-notification Media Type . . . . .  11
     3.2.  Message/disposition-notification Content Fields . . . . .  14
     3.3.  Extension-fields  . . . . . . . . . . . . . . . . . . . .  21
   4.  Timeline of events  . . . . . . . . . . . . . . . . . . . . .  21
   5.  Conformance and Usage Requirements  . . . . . . . . . . . . .  22
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  23
Show full document text