On Wed 09/Apr/2025 06:15:16 +0200 Dave Crocker wrote:
On 4/8/2025 5:43 AM, Alessandro Vesely wrote:
Although different, DKIM2 shares a huge amount of concepts developed
alongside DKIM, from the tag=value specification, to underscored domains and
key distribution, to hashing and signing. The latter, signing, seems to be
the most widely known feature of DKIM. "If you see DKIM-Signature: don't
autoconvert." It has had a significant impact on the email ecosystem. It is
from this point of view that DKIM and DKIM2 are two of a kind.
tag=value is a construct that has been in use since the start of networking.
An RFC733 header field is, really, tag=value.
Eh, not quite. DKIM definitions are really cute, and subsequent RFCs build on
them. RFC 8617, ARC, for example, doesn't even define the terms *signer* and
*verifier*.
Crypto hashing was around long before DKIM, too.
But, sure, it is likely the new thing can share some code from the old thing.
This does not make them semantically related, which the name incorrectly implies.
ARC chose a different name. Then we could argue whether DKIM2 is more like ARC
than DKIM, but one is the ancestor of the other two, so if protocols have a
family name, it should be that.
Best
Ale
--
_______________________________________________
Ietf-dkim mailing list -- ietf-dkim@ietf.org
To unsubscribe send an email to ietf-dkim-le...@ietf.org
