Revised Draft Charter

Message Tracking Working Group (msgtrk)
---------------------------------------

   Charter

   Chair(s):

       Gordon B. Jones  <[email protected]>

   Applications Area Director(s)

        Keith Moore  [email protected]
        Patrik Falstrom [email protected]

   Mailing lists:

       General Discussion: [email protected]
       To Subscribe: [email protected]
       In Body: subscribe msgmib-list <email address> <your name>
       Archive: sloop-1.esinet.org/pub/msgmib-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 independently 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 (e.g., MTAs, “trace servers”), define how and when
     message tracking requests are issued and answered, define
     approaches for inter-domain message tracking, and address security
     issues. The types of messages to be tracked include RFC 822bis
     messages, and optionally others. Messages will be tracked from the
     time they enter the messaging network up until the time they are
     delivered (e.g. 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:

     Oct  15 Post an Internet Draft of the message tracking model

     Nov 15 Post revised draft of message tracking model

     43rd IETF discuss protocol, finish model

     Jan 1 post final draft of model, post Internet Draft of protocol

     Feb 15 Post revised draft of protocol

     44 th IETF discuss protocol

     May 1 Post final draft of protocol