I support adoption. Bron.
On Fri, May 22, 2026, at 21:39, Murray Kucherawy via Datatracker wrote: > This message starts a dkim WG Call for Adoption of: > draft-herr-dkim2-bcp-01 > > This Working Group Call for Adoption ends on 2026-06-05 > > Abstract: > [DKIM2] and associated documents describe the DomainKeys Identified > Mail v2 (DKIM2) email authentication protocol. DKIM2 is designed to > address shortcomings in email authentication protocols and mechanisms > released prior to DKIM2, specifically SPF [RFC7208], DKIM [RFC6376], > DMARC [RFC7489], and ARC [RFC8617]. Those shortcomings most commonly > manifested themselves in email messages that passed through one or > more intermediary hosts (e.g., forwarders or mailing list servers) > while transiting from origination to final destination. Although > these messages were properly authenticated when sent, the alteration > of their path and/or content by the intermediary hosts would cause > authentication checks to fail at the final destination. In addition, > DKIM was susceptible to "replay" of signatures, when attackers would > construct abusive messages in such a way that they would pass > validation checks for a DKIM signature that had been imported from > another message entirely. > > To address these shortcomings, DKIM2 provides methods not only for > intermediary systems to provide details of the changes that they make > to a message in transit, but also for receiving hosts to validate > those changes in addition to the original message. DKIM2 also allows > recipients to detect when messages have been unexpectedly "replayed" > and can also ensure that delivery status notifications (DSNs) are > only sent to entities that were involved in the transmission of a > message. > > This document describes the recommended usage of the DKIM2 protocol > for sending hosts, intermediary hosts, and receiving hosts. > > Please reply to this message and indicate whether or not you support adoption > of this Internet-Draft by the dkim WG. Comments to explain your preference > are greatly appreciated. Please reply to all recipients of this message and > include this message in your response. > > Authors, and WG participants in general, are reminded of the Intellectual > Property Rights (IPR) disclosure obligations described in BCP 79 [2]. > Appropriate IPR disclosures required for full conformance with the provisions > of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any. > Sanctions available for application to violators of IETF IPR Policy can be > found at [3]. > > Thank you. > [1] https://datatracker.ietf.org/doc/bcp78/ > [2] https://datatracker.ietf.org/doc/bcp79/ > [3] https://datatracker.ietf.org/doc/rfc6701/ > > The IETF datatracker status page for this Internet-Draft is: > https://datatracker.ietf.org/doc/draft-herr-dkim2-bcp/ > > There is also an HTMLized version available at: > https://datatracker.ietf.org/doc/html/draft-herr-dkim2-bcp-01 > > A diff from the previous version is available at: > https://author-tools.ietf.org/iddiff?url2=draft-herr-dkim2-bcp-01 > > _______________________________________________ > Ietf-dkim mailing list -- [email protected] > To unsubscribe send an email to [email protected] > -- Bron Gondwana, CEO, Fastmail Pty Ltd / Fastmail US LLC [email protected]
_______________________________________________ Ietf-dkim mailing list -- [email protected] To unsubscribe send an email to [email protected]
