-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
In message <175630516792.705080.14465626239906026210@dt-datatracker-
67876766b7-bkzgr>, [email protected] writes
>Internet-Draft draft-clayton-dkim2-spec-00.txt is now available.
>
> Title: DomainKeys Identified Mail Signatures v2 (DKIM2)
> Authors: Richard Clayton
> Wei Chuang
> Bron Gondwana
> Name: draft-clayton-dkim2-spec-00.txt
> Pages: 28
> Dates: 2025-08-27
This draft is modelled on RFC 6376 and is intended to set out a formal
specification of DKIM2-Signature fields. It doubtless contains many
errors and omissions.
Bron will be updating his HEADERS draft in due course to align with what
is in this document. Note also that all the text about keys has gone
into Wei's DKIMKEYS draft -- DKIM2 is planned to use DKIM1 keys without
any changes, except in so far as deprecating some of the exotica that
doesn't get used (at all?) and text here indicates that you should not
expect such exotica to impact DKIM2 signing/verifying at all.
Note that 6376 contained a lot of text about how DKIM1 worked overall
and most of that has been removed -- we're expecting appropriate
replacement text to end up in an overview document and/or an operational
considerations document.
So although this document will allow you to code a signer and a verifier
you will need to consult other documentation to implement a running
DKIM2 system
- --
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/AwUBaK8aQ2HfC/FfW545EQLFtgCgwyUL/y+NUXBwkdZZe9wX1KXalSMAoM67
Ljxataz23CY/VwsbBSXjndMA
=Wl+B
-----END PGP SIGNATURE-----
_______________________________________________
Ietf-dkim mailing list -- [email protected]
To unsubscribe send an email to [email protected]
