-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
In message <178767437565.531816.9073017873681261278@dt-datatracker-
786f84c586-vck88>, [email protected] writes
> Title: DomainKeys Identified Mail Signatures v2 (DKIM2)
> Authors: Richard Clayton
> Wei Chuang
> Bron Gondwana
> Name: draft-ietf-dkim-dkim2-spec-05.txt
> Pages: 45
> Dates: 2026-08-25
after some delay (I went to see the eclipse in Spain and drove back in a
leisurely manner) here is the latest version of the spec
implementors should note:
there is a much extended list of header fields that should not be
signed --- this follows from the work that Bron did (with Claude's
help) to identify trace header fields from existing RFCs
sha512 is now required as a hash function alongside sha256. This is
mainly to allow implementors to test their code for multiple hash
functions; we might want to take it out before finalising the
document but for the moment it is a MUST for Verifiers
there is now text to forbid repetition of algorithm or selectors
(there's no interop issues here, but it means you can reject
messages that are just trying to push up your electricity bill)
however, the SHOULD NOT on specious Message-Instance fields is toned
down (they are now just discouraged)
Header field names in the JSON Recipes MUST be lower case; and
Verifiers should now report JSON issues specifically.
- --
richard @ highwayman . com "Nothing seems the same
Still you never see the change from day to day
And no-one notices the customs slip away"
-----BEGIN PGP SIGNATURE-----
Version: PGPsdk version 1.7.1
iQA/AwUBao3BjmHfC/FfW545EQI9AQCg7kkN0bbPORU2a0XfZVZ7JyXLamMAoLmq
bl1qGZS315w6h/ya7EUNk3t0
=tSpe
-----END PGP SIGNATURE-----
_______________________________________________
Ietf-dkim mailing list -- [email protected]
To unsubscribe send an email to [email protected]
