[rfc-dist] RFC 3798 on Message Disposition Notification

rfc-editor at rfc-editor.org rfc-editor at rfc-editor.org
Thu May 13 16:39:27 PDT 2004


A new Request for Comments is now available in online RFC libraries.


        RFC 3798

        Title:      Message Disposition Notification
        Author(s):  T. Hansen, Ed., G. Vaudreuil, Ed.
        Status:     Standards Track
        Date:       May 2004
        Mailbox:    tony+rfc3798 at maillennium.att.com, GregV at ieee.org
        Pages:      30
        Characters: 64049
        Updates:    3461, 2046
        Obsoletes:  2298

        I-D Tag:    draft-vaudreuil-mdnbis-05.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3798.txt


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 headers 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 is now a Draft Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative


More information about the rfc-dist mailing list