(unknown)

unsubscribe

Re:

+----------------------------------------------------+

Panda GateDefender has detected malicious content (Virus) in the following file: [Garry.cpl]
W32/Bagle.AH.worm

The file has been deleted to protect the network.
07/18/2005 08:07 +0100

www.pandasoftware.com

+----------------------------------------------------+

WG Action: Conclusion of Message Tracking Protocol (msgtrk)

The Message Tracking Protocol (msgtrk) in the Applications Area has concluded.

The IESG contact persons are Ted Hardie and Scott Hollenbeck.

The mailing list will remain active.

+++

The Message Tracking Protocol (msgtrk) working group in the Applications
area has concluded. This working group was chartered to design a diagnostic
protocol for a message originator to request information about the submission, 
transport, and delivery of a message regardless of its delivery status.

The working group produced one Informational RFC and three Proposed Standard
RFCs. Informational RFC 3888 describes requirements and a model for message
tracking. Standards track RFC 3887 describes a message tracking query
protocol. Standards track RFC 3886 describes an extensible message format
for message tracking responses. Standards track RFC 3885 describes an SMTP
service extension for message tracking.

RFC 3888 on Message Tracking Model and Requirements

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

         RFC 3888

         Title:      Message Tracking Model and Requirements
         Author(s):  T. Hansen
         Status:     Informational
         Date:       September 2004
         Mailbox:    tony+msgtrk <at> maillennium.att.com
         Pages:      11
         Characters: 20950
         Updates/Obsoletes/SeeAlso:    None

         I-D Tag:    draft-ietf-msgtrk-model-07.txt

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

Customers buying enterprise message systems often ask: Can I track the
messages?  Message tracking is the ability to find out the path that a
particular message has taken through a messaging system and the
current routing status of that message.  This document provides a
model of message tracking that can be used for understanding the
Internet-wide message infrastructure and to further enhance those
capabilities to include message tracking, as well as requirements for
proposed message tracking solutions.

This document is a product of the Message Tracking Protocol Working
Group of the IETF.

RFC 3887 on Message Tracking Query Protocol

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

        RFC 3887

        Title:      Message Tracking Query Protocol
        Author(s):  T. Hansen
        Status:     Standards Track
        Date:       September 2004
        Mailbox:    tony+msgtrk <at> maillennium.att.com
        Pages:      23
        Characters: 42763
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-msgtrk-mtqp-12.txt

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

Customers buying enterprise message systems often ask: Can I track the
messages?  Message tracking is the ability to find out the path that a
particular message has taken through a messaging system and the
current routing status of that message.  This document describes the
Message Tracking Query Protocol that is used in conjunction with
extensions to the ESMTP protocol to provide a complete message
tracking solution for the Internet.

This document is a product of the Message Tracking Protocol Working
Group of the IETF.

This is now a Proposed Standard Protocol.

RFC 3886 on An Extensible Message Format for Message Tracking Responses

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

        RFC 3886

        Title:      An Extensible Message Format for Message Tracking
                    Responses
        Author(s):  E. Allman
        Status:     Standards Track
        Date:       September 2004
        Mailbox:    eric <at> Sendmail.COM
        Pages:      11
        Characters: 21746
        Updates:    3463

        I-D Tag:    draft-ietf-msgtrk-trkstat-05.txt

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

Message Tracking is expected to be used to determine the
status of undelivered e-mail upon request.  Tracking is used in
conjunction with Delivery Status Notifications (DSN) and Message
Disposition Notifications (MDN); generally, a message tracking request
will be issued only when a DSN or MDN has not been received within a
reasonable timeout period.

This memo defines a MIME content-type for message tracking
status in the same spirit as RFC 3464, "An Extensible Message Format
for
Delivery Status Notifications".  It is to be issued upon a request as

RFC 3885 on SMTP Service Extension for Message Tracking

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

        RFC 3885

        Title:      SMTP Service Extension for Message Tracking
        Author(s):  E. Allman, T. Hansen
        Status:     Standards Track
        Date:       September 2004
        Mailbox:    eric <at> Sendmail.COM, tony+msgtrk <at> maillennium.att.com
        Pages:      9
        Characters: 17458
        Updates:    3461

        I-D Tag:    draft-ietf-msgtrk-smtpext-05.txt

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

This memo defines an extension to the SMTP service whereby a
client may mark a message for future tracking.

This document is a product of the Message Tracking Protocol Working
Group of the IETF.

This is now a Proposed 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

MSGTRK Closing

All:

The msgtrk documents are now in RFC Editor "auth48" status.  That means that
they are in the final stage of review before being published as RFCs.  That
being the case, I intend to close the working group after the RFCs are
announced.  Speak now if you believe there is any reason to *not* close.

The working group mailing list can remain open once the group has closed.
You all can decide to close the list if you wish to do so, but there's no
harm (and there's often benefit) in leaving the list open after a group has
been closed.

Congratulations on a job almost completed!

-Scott-

RE: Has IANA gone mad?

--On 2004-7-20 8:32 AM -0400 Scott Hollenbeck <sah <at> 428cobrajet.net> 
wrote:

> Among any of those umpteen times, did you happen to mention the
> situation to the IETF Secretariat?  If brought to their attention I'm
> sure they'd be willing to put a link to the tracker in an obvious
> place.

Yes (via the AD (Ned), and to the RFC Editor). (And I suspect via 
ietf <at> , although it has been long enough that I no longer remember.)

--lyndon

Has IANA gone mad?

Sent to ietf-822 and ietf-msgtrk mailing lists, cc to iana <at> iana.og, responses
default to ietf-822

Yesterday, "message/tracking-status" appeared in the IANA registry for MIME
message media types (http://www.iana.org/assignments/media-types/message/).
It lists "RFC-ietf-msgtrk-trkstat-05.txt" as the reference document -- of
course there is no such document.  The closest existing document is a draft
dated March 2003, more than a year old ("Internet drafts are valid for six
months").

Why on Earth did this suddenly appear yesterday?

The ietf-msgtrk mailing list appears to be dormant; in the last three months
the only message to appear on that mailing list's archive are spam messages
(http://www.imc.org/ietf-msgtrk/mail-archive/maillist.html).  There are fewer
than a dozen message in the mailing list archive in the past year, spam
included.

What's going on?!?

Changes..