As promised at the dkim meeting, I'm resending a suggestion about o= that was sent in November and again in February.
At the Wednesday meeting, it was suggested that we replace the single character o=? (etc.) tags with tags like o=WEAK (etc.). The thrust of the messages was that we should use something that is even more meaningful. There were a couple of threads last November about changing o= to use words and splitting out the semantics around the various semantic axes that are covered by the value (sending mail, signature presence, 3rd party signatures, redirect). One message that I wrote had a table, showing what a couple possible syntaxes might be for o= (http://mipassoc.org/pipermail/ietf-dkim/2005q4/001307.html, slightly modified here): o=-signature,-3ps signature=never,3ps=never ?/WEAK o=~signature,-3ps signature=optional,3ps=never ~/NEUTRAL o=~signature,+3ps signature=optional,3ps=allowed !/EXCLUSIVE o=+signature,-3ps signature=always,3ps=never -/STRONG o=+signature,+3ps signature=always,3ps=allowed ./NEVER o=nomail nomail ^/USER o=user checkuser William Leibzon also had suggestions along the same lines (http://mipassoc.org/pipermail/ietf-dkim/2005q4/001306.html): 1. Signature required/optional: sig=MUST/SHOULD/NEVER/USER (sig=STRONG/NEUTRAL/NEVER) 2. 3rd parties allowed/not 3ps=ALLOW/DENY/USER (Or if you like o=STRONG/3PS | o=NEUTRAL/NO3PS | o=USER/USER) Hector Santos had several suggestions for additional values in the 3ps space. (http://mipassoc.org/pipermail/ietf-dkim/2005q4/001318.html): signature=always, 3PS=IGNORE -- Keep Original, don't strip, resign signature=always, 3PS=APPEND -- Append, don't strip or replace. signature=always, 3PS=RESIGN -- strip and replace. Tony Hansen [EMAIL PROTECTED] _______________________________________________ NOTE WELL: This list operates according to http://mipassoc.org/dkim/ietf-list-rules.html
