2.1.10 Message Tracking Protocol (msgtrk)

NOTE: This charter is a snapshot of the 43rd IETF Meeting in Orlando, Florida. It may now be out-of-date. Last Modified: 25-Nov-98


Gordon Jones <tmorrowsys@yahoo.com>

Applications Area Director(s):

Keith Moore <moore@cs.utk.edu>
Patrik Faltstrom <paf@swip.net>

Applications Area Advisor:

Keith Moore <moore@cs.utk.edu>

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:

Nov 98


Post an Internet Draft of the message tracking model

Nov 98


Post revised draft of message tracking model

Dec 98


Meet at Orlando IETF to discuss I-Ds

Jan 99


post final draft of model, post Internet Draft of protocol

Feb 99


Post revised draft of protocol

Mar 99


Meet at 44th IETF

May 99


Post final draft of protocol

No Current Internet-Drafts
No Request For Comments

Current Meeting Report

None received.


None received.