Re: daily response Wednesday 17 mar

David Nicol wrote:
> I prefer one header with all the data crammed into it in a series
> of well-defined key=value pairs rather than many headers each with
> its own extension of the header name.
> 
>   NOT PREFERRED BY DN:
>   Filtered-By: foobarbazfilter
>   Filtered-By-Version: 1.2devel20070317build2
>   Filtered-By-Heuristic-Probability-Is-Ham: 93
>   Filtered-By-Heuristic-Probability-Is-Spam: 12
> 
>   PREFERRED BY DN:
>   Filtered-By: foobarbazfilter version=1.2devel20070317build2
>     spamp=12 spamq=93
> 
> The SMTP extension mechanisms to date have all taken the first approach,
> except for Received:.  Adding a spamp and a spamq to Received: might be
> a good thing for a heuristic analysis system to do instead of something 
> else.
> Configuring a MUA prefiler to look inside a particular header will be
> tricky.
> 

The approach taken by similar standards has been along the lines of 
"key=value; key1=value1; key2=value;" with the ";" separating tokens. 
The actual "key" values are stored in an IANA registry and people have 
freedom to define their own "x-key" extensions which do not interfere. 
At the same time it remains extensible by adding new "key" extensions to 
the IANA registry.

However, one particular point to keep in mind here is the limit of the 
header length (something like 900 bytes?, can't find the RFC reference). 
I know that some spam filters like SpamAssassin can generate a large 
large output, so we might want to consider an ability to split headers 
into multiples to get around the limit.

>> > keep [discussion] synchronized > between the list here and the Wiki. 
>> Do I now have to write the same > things both here and the Wiki? What 
>> if a new participant doesn't know > about the Wiki, or doesn't know 
>> about the list? The Wiki was simply a place to put some of the 
>> thoughts into. If anyone wants to make it into a document instead, 
>> please go ahead. I just used the Wiki as a shortcut for document 
>> writing. Yakov 
> 
> ignorant wishlist on wiki use:
> 
> * have ability to create new pages and link to 'em as well as editing
>  the pages that are there
> 
> * have ability to trivially create self-linking anchors and link to 'em
>   ( things like <a name="PARA7"></a><a href="#PARA7">(*)</a>     could 
> automatically appear every few lines, or could just do this
>     to any asterisk that is not inside a link already
> 
> * whenever you materialyl alter something on the wiki -- anything
> more substantial than corecting speling -- post a link to what
> you changed, to the list, or at least send the link to whoever else
> is working on that little bit to discuss it.
> 
> * add paragraph anchors to list archive presentation system so
> you can link to a paragraph in the list archive instead of just
> linking to whole messages (or threads)
> 
....
> 
> What was the link to the wiki again?  If I extend the wiki we are using
> will my patches be accepted?  "Customized wiki used by ASRG filtering WG"
> would be a nifty brag point.

The current Wiki link is here:

http://www.shaftek.org/wiki/wiki.pl?Filtering_Standards

I only put this into a Wiki because I was too lazy to type up an 
Internet draft. The subgroup can decide as whole on any tool they want - 
if you want to have one person do a document that's fine also. The 
decision is yours.

The Wiki is pretty open as of now. That may change depending on how this 
subgroup develops.

Yakov