On Mon 21/Apr/2025 09:37:35 +0200 Wei Chuang wrote:
On Sun, Apr 20, 2025 at 4:10 AM Alessandro Vesely <[email protected]> wrote:
I would prefer to use a class of "good" transformations, such as the subject,
footer, mimeify, add-part and mime-wrap of draft-kucherawy-dkim-transform,
I also like the idea of mime part algebra as an addition to text algebra to
remove the need to do base64 transformation. +1 to looking more into
draft-kucherawy-dkim-transform. I don't understand your earlier concern
around quoted printable and algebra.
and one "complex" transformation to be defined on a byte-by-byte basis.
Can you expand what you mean by this?
Changes that are not of a mailing list type can be reported with something
similar to the output of a diff utility.
[...]
The characteristic of the "good" transformations above is that they are
attributable to a typical mailing list transformation; that is, non-
invasive and respectful of the original content. If the verifier can
determine this, it can override dmarc=fail.
If the transformation is a complete replacement of the body, a dmarc=fail
deserves to be rejected, according to policy.
It's risky to throw around subjective terminology that's very similar to
the notion of "trust" i.e. "good transformations". I think the "algebra"
concept is more helpfully thought of as identifying which of the content
is created by whom and not worrying which mutation happened.
The ability to recognize which mediator made which changes remains the core
functionality. Enabling verifiers to easily recognize the category of changes
is an added feature that allows it to be exploited in practice.
Best
Ale
--
_______________________________________________
Ietf-dkim mailing list -- [email protected]
To unsubscribe send an email to [email protected]
