-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In message <e12aca72-2d51-408b-906a-f4df2fb36...@bluepopcorn.net>, Jim Fenton <fen...@bluepopcorn.net> writes
>On 11 Apr 2025, at 13:00, Richard Clayton wrote: > >> The list of header fields is currently >> >> Author >> Bcc > >Bcc header field? Doesn’t that contradict the “blank” carbon copy? I suggest you read RFC5322 #3.6.3, which has quite a lot of text explaining the complexity of what a Bcc header field can look like. For length, I will not include that here. You can try arguing there is no value in signing the field because nothing ever displays it or acts upon its content ... I am not confident about that. >> 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 > >383/766 bytes seems insignificant in comparison to the huge, opaque header >fields being added by some email providers that provide little utility except >perhaps to themselves. Perhaps we should be calculating the carbon cost and asking them to justify themselves ... but it's not a reason for ignoring what we can do >We made a similar optimization when designing DKIM not to include the public >key >in the signature and publish a digest of it in the DNS. This turned out to be >the wrong thing when public key sizes had to increase and the DNS couldn’t >easily accommodate that. Let’s not make an analogous mistake here. you should perhaps note the size of some of the post-quantum stuff ! - -- richard Richard Clayton Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. Benjamin Franklin 11 Nov 1755 -----BEGIN PGP SIGNATURE----- Version: PGPsdk version 1.7.1 iQA/AwUBZ/wIWGHfC/FfW545EQLAKwCgyPWdq+4WL/v6cA9y9kxNOpijJ4gAn1eQ /vPVIq5fPHWSx49PHFst05UT =NRF0 -----END PGP SIGNATURE----- _______________________________________________ Ietf-dkim mailing list -- ietf-dkim@ietf.org To unsubscribe send an email to ietf-dkim-le...@ietf.org
