-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
>Internet-Draft draft-ietf-dkim-dkim2-spec-02.txt is now available. It is a
>work item of the Domain Keys Identified Mail (DKIM) WG of the IETF.
>
> Title: DomainKeys Identified Mail Signatures v2 (DKIM2)
> Authors: Richard Clayton
> Wei Chuang
> Bron Gondwana
> Name: draft-ietf-dkim-dkim2-spec-02.txt
> Pages: 40
> Dates: 2026-05-17
This version addresses a number of issues that have come up on the list
* Made explicit that base64strings must be padded with zero bits.
thanks to Steve Atkins
* Fixed header field description in JSON to be single string. and moved
the removed info into the textual discussion. Removed the z body
recipe since DSNs do not actually need this.
thanks to Steve Atkins
* Added text to emphasise that semi-colons are (easy to parse)
separators in Message-Instance and DKIM2-Signature. Also fixed the
syntax for extension tags.
thanks to Hannah Stern
* Added text about what donotmodify means and added text to the
verification section about this and the donotexplode flag.
thanks to Wei Chuang
None of have (much) implication for implementers.
HOWEVER there is one change which has come out of the interworking
experiments which are occurring. It turns out that it is inconvenient
that Authentication-Results header field need to be signed because
(obviously) they are added AFTER the message has been validated and many
systems consider it prudent to remove them from incoming messages
(recall that they are only intended for use within a trust boundary).
Accordingly the spec now adds them to the list of header fields that are
not signed by DKIM2
- --
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/AwUBagngI2HfC/FfW545EQJIQQCeOvXVwhojtnVgalOsHqZhRtEK9qgAoOeq
kfMU7RRNpiFODF0ImDbjdbOw
=yv9i
-----END PGP SIGNATURE-----
_______________________________________________
Ietf-dkim mailing list -- [email protected]
To unsubscribe send an email to [email protected]
