John Levine wrote:
NEW: If there are
NEW: multiple query mechanisms listed, the choice of query mechanism
NEW: MUST NOT change the interpretation of the signature. An
NEW: implementation MUST use the recognized query mechanisms in the
NEW: order presented.
I can live with either of these sentences, but they don't make sense
togther. If all of the mechanisms will give you the same answer, why
shouldn't I be allowed to send out all the queries at once and take
the one the comes back first? Or if new ones are supersets of old
ones, prefer the more informative one?
Right, I think the first sentence is a little bit suspect. We may
eventually want to
make TXT, say, historic such that it still works in the way that -base
expected it
to work, but with new extensions for DKK that may well change the
interpretation
such as giving finer grained ways to assess the signature, etc.
Mike
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html