On October 12, 2005 at 19:36, "Hallam-Baker, Phillip" wrote:
At the moment it can't unless it assumes the order of the signature
headers is preserved.
But this is very easy to fix as we discussed earlier. Have a requirement
that if a signer adds a signature to a message that already has one it
adds in a counter attribute with a higher counter value than any other
signature already present.
The order isn't sufficient since it requires an assumption on who
the first signer is, which may not be sender or even the originating
domain.
I do agree that it would be nice to denote signing order.
I would also like to see a way for the signer to describe the role in
which they are accepting responsibility. It may not be possible to do
this in every case but if the signer can say that it is the originator,
a forwarder, a mailing list or whatever that will be usefull.
Agreed. I've brought up the issue of signer roles, but it appears
to have been rejected or gained no traction.
--ewh
_______________________________________________
ietf-dkim mailing list
http://dkim.org