[apps-discuss] Moving ahead with draft-ietf-appsawg-mdn-3798bis

Colleagues,

The authors, ADs, and I have discussed this newest version and feel there
have not been enough material changes to the draft since Working Group Last
Call completed to warrant a second WGLC.  Accordingly, this will progress
shortly toward IETF Last Call and IESG evaluation.  A diff to the version
that was WGLC'd:

https://www.ietf.org/rfcdiff?url1=draft-ietf-appsawg-mdn-3798bis-02&url2=draft-ietf-appsawg-mdn-3798bis-10

If you have any final comments please provide them to the list, the chair,
or the authors ASAP.

-MSK

---------- Forwarded message ----------
From: <internet-drafts@ietf.org>
Date: Sun, Jul 31, 2016 at 10:23 AM
Subject: I-D Action: draft-ietf-appsawg-mdn-3798bis-09.txt
To: i-d-announce@ietf.org
Cc: apps-discuss@ietf.org

A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the ART Area General Applications Working
Group of the IETF.

        Title           : Message Disposition Notification
        Authors         : Tony Hansen
                          Alexey Melnikov
        Filename        : draft-ietf-appsawg-mdn-3798bis-09.txt
        Pages           : 35
        Date            : 2016-07-31

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.

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-appsawg-mdn-3798bis/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-appsawg-mdn-3798bis-09

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-appsawg-mdn-3798bis-09

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft
<https://www.ietf.org/mailman/listinfo/i-d-announce%0AInternet-Draft>
directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt