Message Tracking Protocol (msgtrk)

Last Modified: 2004-03-15

Chair(s):

Steve Hole <steve.hole@messagingdirect.com>

Applications Area Director(s):

Ted Hardie <hardie@qualcomm.com>
Scott Hollenbeck <sah@428cobrajet.net>

Applications Area Advisor:

Scott Hollenbeck <sah@428cobrajet.net>

Mailing Lists:

General Discussion: ietf-msgtrk@imc.org
To Subscribe: ietf-msgtrk-request@imc.org
In Body: subscribe
Archive: http://www.imc.org/ietf-msgtrk/mail-archive/

Description of Working Group:

The Message Tracking Working Group will 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 group will produce two standards track documents: a message tracking model document and a protocol document. The model will state how message tracking is enabled, identify the entities involved, define how and when message tracking requests are issued and answered, define approaches for inter-domain message tracking, and address security issues. The submission, transport, and delivery of RFC 822bis messages will be tracked from the time such messages enter the messaging network up until the time they are discharged (e.g. to an IMAP server, to an end-user's mailbox, or a proprietary mail system).

The group will design one or more protocols to implement message tracking as described above.

Goals and Milestones:

Done    Post an Internet Draft of the message tracking model
Done    Post revised draft of message tracking model
Done    Post initial drafts of protocol documents
Done    Last call for model document
Done    Post revised draft of protocol documents
Done    Meet at 49th IETF - review protocol documents
Done    Last call for protocol documents

No Current Internet-Drafts

Request For Comments:

SMTP Service Extension for Message Tracking (RFC 3885) (0 bytes)
An Extensible Message Format for Message Tracking Responses (RFC 3886) (0 bytes)
Message Tracking Query Protocol (RFC 3887) (0 bytes)
Message Tracking Model and Requirements (RFC 3888) (0 bytes)