Am 02.11.26 um 17:50 schrieb John Levine:
Our plan is for DKIM2 to replace DKIM1. If people are updating their software,
we want
them to update it to DKIM2.
Also, as the author of the Ed25519 RFC 8463 I can tell you that the number of
places that
have implemented it rounds to zero. We basically did it in the unlikely event
that RSA
was broken. Even if we added a PQ alg to DKIM1, nobody would implement that,
either.
I'm aware of that, and it should definitely be the long-term goal. However, I don't think everyone
will adopt DKIM2 immediately, so DKIM1 and DKIM2 have to run in parallel for a while.
I also don’t think Ed25519 should be compared to PQ algorithms (even though I use it myself, I can
confirm that its adoption is low but still growing...), since Ed25519 is only considered as a
backup, whereas PQ algorithms generally prevent future attack scenarios. If one of the PQ algorithms
becomes a MUST, its use is likely to increase significantly anyway.
Bastian
--
Bastian Buck - Geschäftsführer
BWeb-SSL Services UG & Co. KG - 88512 Mengen - www.bweb-ssl.de
AG Ulm HRB 736203 - Geschäftsführende Komplementärin: BT computers & more UG
(haftbeschr.)
E-Mail: [email protected] - Webseite: www.bastian-buck.de
_______________________________________________
Ietf-dkim mailing list -- [email protected]
To unsubscribe send an email to [email protected]
