Requirements for a filtering header

> There has been discussion back and forth on different aspects of this 
> problem. At this time, I want to get a feel from the members as to:
> 1. If there is a rough consensus that a standard filtering header would
> be  useful.

I think we have pretty clearly agreed that such a header would be useful.

> 2. If there is a rough consensus as to what issues need to be solved for
> such header to be useful.

Major existing issue:
Should the header appear only once, representing the results of the
last-acting (and therefore most trusted?) filter, or should it appear once
for each analysis action?

> If these are satisfied, than I would like to ask for some folks to
> volunteer to write up a requirements draft from which we can continue the
> discussion.

Please try not to be so document focused, at least until the point where 
we're actually writing a specification. If it's that important, I can throw 
this stuff in the wiki.

At any rate, once we have the above major issue resolved, I see the need for 
the following things to be determined:
1. Syntax of this header
2. Fields
    a) mandatory
    b) optional, but specified in the base spec
    c) IANA registration of new fields
3. Name of this header

My answers to the questions raised will follow shortly.

Philip Miller