simple problem statement

The WG session in Orlando was largely a rehash of the BOF session in
Chicago.  I had the following summary in my notes from Chicago, and I
thought they might help the folks who will be revising the WG charter,
problem statement, and requirements document.

Dave Kristol
========================
How do you turn tracking on? 
	If it's always on, there's a considerable cost throughout the
	network to track messages that no one may ever ask about.  If
	you have to turn tracking on explicitly, which is much less
	resource-intensive, you'll probably always discover that you
	haven't asked for tracking for the message that got lost and
	that you therefore needed to track.
When do you find out what happened? 
	Is notification about the disposition of a message automatic,
	or do you have to ask what happened to it?  In the latter case,
	how long should the tracking information be retained?  (How much
	later can you ask about a message?)
Whom do you ask? 
	What is the protocol for querying about the disposition of a
	message?  At what points along the message's delivery path can
	you get tracking information? (Can you query the hops within a
	company's internal email system?)  Who is allowed to ask?  What
	security is in place to ensure that only authorized parties can
	ask about the disposition of a message?  How do you authenticate
	their identity?