-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
In message <[email protected]
il.com>, Emanuel Schorsch <[email protected]> writes
>I like this draft and I think it's a great addition. I see this satisfying
>all the properties that "okaytomodify" did in the discussions on the other
>thread with Wei while providing more granular information and context from
>the sender.
I don't think a single bit can be used in any practical manner.
Also, if people set CanModify: on more than a smattering of mail I doubt
that many receivers will be prepared to honour it at all. So rather
than emphasising how useful it would be to a handful of senders I think
that the hearts-and-minds activity required is to stress how unwise it
would be to set it unless you really, really need it.
>The one thing I think would be helpful to add in that spirit is a
>'canmodify=any' option.
You get that by omitting the header field altogether (and you save CPU
cycles, bandwidth and eyestrain by doing so).
>The other end of the spectrum from 'none' I think
>that would be useful for senders that are okay with any kind of
>modifications as long as the chain is recorded.
I don't think "CanModify" can have any meaning unless what you have in
your hand is a Fully Verified DKIM2 Message. Having the "chain recorded"
is a prerequisite for a message to be a Fully Verified DKIM2 Message.
- --
richard @ highwayman . com "Nothing seems the same
Still you never see the change from day to day
And no-one notices the customs slip away"
-----BEGIN PGP SIGNATURE-----
Version: PGPsdk version 1.7.1
iQA/AwUBau+T5mHfC/FfW545EQJthwCfTQEnG0J9FxuRAJaEukmtj51j090AnRwP
SwpL55IPsVOYbIDPkZ+x80qn
=EQEs
-----END PGP SIGNATURE-----
_______________________________________________
Ietf-dkim mailing list -- [email protected]
To unsubscribe send an email to [email protected]
