On 4/11/2025 1:00 PM, Richard Clayton wrote:
Our current thinking, which will be reflected in documents Real Soon Now
is that we will provide a standard list of header fields that will be
required to be signed by default -- signers can add to this if they
wish. In each case we will sign all instances of a header field that are
present (in the order they occur in the email) -- viz: we will specify
oversigning by default.

Again:  that warrants a BCP, not a protocol revision.



It also reduces the size of every (cautious) email by 383 bytes (766 if
the oversigning is not default) ... and there's a carbon footprint issue
here that we should not ignore without careful consideration

What percentage of an average email is that?


d/

--
Dave Crocker

Brandenburg InternetWorking
bbiw.net
bluesky: @dcrocker.bsky.social
mast: @[email protected]

_______________________________________________
Ietf-dkim mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to