2.1.10 Message Tracking Protocol (msgtrk)

NOTE: This charter is a snapshot of the 49th IETF Meeting in San Diego, California. It may now be out-of-date. Last Modified: 11-Oct-00


Steve Hole <steve.hole@messagingdirect.com>

Applications Area Director(s):

Ned Freed <ned.freed@innosoft.com>
Patrik Faltstrom <paf@cisco.com>

Applications Area Advisor:

Ned Freed <ned.freed@innosoft.com>

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:



Post an Internet Draft of the message tracking model



Post revised draft of message tracking model



Post initial drafts of protocol documents

Aug 00


Last call for model document

Oct 00


Post revised draft of protocol documents

Dec 00


Meet at 49th IETF - review protocol documents

Feb 01


Last call for protocol documents


No Request For Comments

Current Meeting Report

None received.


None received.