-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
This version of clayton-dkim2-spec has fully integrated the latest iteration of Bron's Message-Instance header field (which carries the hash values for the header and body) with DKIM2-Signature (which just signs the M-I and D2-S headers). Other changes you might miss until you read it carefully are to have a coherent set of tag names (not slavishly copying DKIM1), and to use what is effectively relaxed/simple; because relaxed is essential to interwork for the headers -- and simple is more appropriate for something which is authenticating mail bodies. If it causes interworking issues then we should find out soon enough, and can change back to relaxed/relaxed. This should now be a stand-alone document to implement against... - -----Original message----- Subject: I-D Action: draft-clayton-dkim2-spec-04.txt To: [email protected] From: [email protected] Reply-To: [email protected] Date: Fri, 12 Dec 2025 12:38:41 -0800 Message-ID: <176557192126.986.16125993615422469935@dt-datatracker-5bd94c585b- pvtsm> Internet-Draft draft-clayton-dkim2-spec-04.txt is now available. Title: DomainKeys Identified Mail Signatures v2 (DKIM2) Authors: Richard Clayton Wei Chuang Bron Gondwana Name: draft-clayton-dkim2-spec-04.txt Pages: 33 Dates: 2025-12-12 Abstract: DomainKeys Identified Mail v2 (DKIM2) permits a person, role, or organization that owns a signing domain to document that it has handled an email message by associating their domain with the message. This is achieved by providing a hash value that has been calculated on the current contents of the message and then applying a cryptographic signature that covers the hash values and other details about the transmission of the message. Verification is performed by querying an entry within the signing domain's DNS space to retrieve an appropriate public key. As a message is transferred from author to recipient systems that alter the body or header fields will provide details of their changes and calculate new hash values. Further signatures will be added to provide a validatable "chain". This permits validators to identify the nature of changes made by intermediaries and apply a reputation to the systems that made changed. DKIM2 also allows recipients to detect when messages have been unexpectedly "replayed" and can also ensure that delivery status notifications are only sent to entities that were involved in the transmission of a message. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-clayton-dkim2-spec/ There is also an HTMLized version available at: https://datatracker.ietf.org/doc/html/draft-clayton-dkim2-spec-04 A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-clayton-dkim2-spec-04 Internet-Drafts are also available by rsync at: rsync.ietf.org::internet-drafts _______________________________________________ I-D-Announce mailing list -- [email protected] To unsubscribe send an email to [email protected] - -----End of original message from [email protected] - -- 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/AwUBaTyHv2HfC/FfW545EQKW2QCgoaaNcFYkAsvVhSJ1Z/Se3Ti9y0EAoJAK Oi8JaDaEvUnEoaMZ6bV8GpE6 =oz6d -----END PGP SIGNATURE----- _______________________________________________ Ietf-dkim mailing list -- [email protected] To unsubscribe send an email to [email protected]
