DKIM2 remains an evolving IETF proposal, not a standard ready for deployment. Its core specification is at revision -09 and its DNS companion at -03; the working-group chairs plan to begin a final review after the 18 November 2026 meeting if major issues are resolved. Six other tracked submissions are individual drafts, so they have no formal working-group standing unless adopted. The tracker distinguishes active work from expired or superseded proposals, and notes that a proposal for DKIM2-specific DMARC reports has not yet become a draft.
Several elements have persisted across revisions: each system handling a message adds a signature, signatures bind the message to its envelope, and a chain cannot be Fully Verified if any signature is more than 14 days old. Other decisions remain unsettled, including how DKIM2 handles rewritten From fields, post-quantum keys in DNS, and integration with DMARC. Existing best-practices guidance is partly outdated: it recommends test-mode selectors that the DNS draft deprecates and tells forwarders to honor flags removed from the specification. Its timestamp guidance also differs from the stricter 14-day limit. The practical conclusion is to keep current DKIM (RFC 6376) working and wait before deploying DKIM2.
Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.