Re: MIME message management, etc.

[gbjones@xxxxxxxxx (Gordon B. Jones)]

Hello,

Here is the PROPOSED charter. We're still waiting to hear from the IETF on the
definitive status of the charter. If you're interested, please subscribe to the
mailing list and be on the lookout for a meeting entitled msgtrk at the next
IETF. I gave Malcom detailed instructions for getting on the list. We also need
volunteers to help write the documents.


Gordon

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

   Charter

   Chair(s):

       Gordon B. Jones  <gbjones@xxxxxxxxx>

   Applications Area Director(s)

        Harald Alvestrand  <harald.alvestrand@xxxxxxxxxx>
        Keith Moore  <moore@xxxxxxxxxx>

   Area Advisor

        Keith Moore  <moore@xxxxxxxxxx>

    Mailing lists:

       General Discussion: msgmib-list@xxxxxxxxxxxxxxxx
       To Subscribe: listserv@xxxxxxxxx
       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 message originator, message recipient, and
     administrative access to information about the submission,
     transport, and delivery of a message. For each of these classes
     of users there will be different requirements and security
     implications.

     The group will produce two standards track documents: a message
     tracking model document and a protocol document. The model  will
     describe the message tracking problem by identifying the entities
     involved (e.g., message relays or "MTAs", management agents),
     define relationships between the entities, 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.

     The protocol will contain variables and elements of procedure to
     implement the message tracking model. The protocol will provide
     the necessary security and privacy features, and will exclude
     services provided by existing mail systems. The resulting protocol
     will be useful for fault, performance, and security purposes.
     Using the message tracking protocol it will be possible to issue
     queries about messages that were previously sent and obtain
     responses containing information about those messages. For instance,
     a query might contain a unique message ID or an originator name,
     and the response might contain the disposition time and disposition
     status (delivered/non-delivered) of the message.


     Goals and Milestones:

     Jun 1 Post an Internet Draft of the message tracking model

     Aug 1 Post revised draft of message tracking model

     42nd IETF discuss protocol, finish model

     Oct 15 post final draft of model, post Internet Draft of protocol

     Nov 25 Post revised draft of protocol

     43rd IETF discuss protocol

     Feb 1 Post final draft of protocol