RFC 5672: RFC 4871 DomainKeys Identified Mail (DKIM) Signatures -- Update
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 6376.
Current document in this lineage: RFC 6376 — DomainKeys Identified Mail (DKIM) Signatures
In plain English — editorial summary, not part of the RFC
This document updates RFC 4871, "DomainKeys Identified Mail (DKIM) Signatures". Specifically, the document clarifies the nature, roles, and relationship of the two DKIM identifier tag values that are candidates for payload delivery to a receiving processing module. The Update is in the style of an Errata entry, albeit a rather long one. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5672
- Published
- August 2009
- Authors
- D. Crocker
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 14
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 4 RFCs, each formally replacing the one before it.
- RFC 4870 (2007)
- RFC 4871 (2007)
- RFC 5672 (2009)
- RFC 6376 (2011) ✓
Read the full history of DomainKeys Identified Mail (DKIM) Signatures →
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7489Domain-based Message Authentication, Reporting, and Conformance (DMARC)Obsoleted
March 2015
- RFC 9057Email Author Header FieldCurrent
June 2021
- RFC 7070An Architecture for Reputation ReportingCurrent
November 2013
- RFC 7071A Media Type for Reputation InterchangeCurrent
November 2013
- RFC 7072A Reputation Query ProtocolCurrent
November 2013
- RFC 7073A Reputation Response Set for Email IdentifiersCurrent
November 2013
- RFC 9216S/MIME Example Keys and CertificatesCurrent
April 2022
- RFC 5617DomainKeys Identified Mail (DKIM) Author Domain Signing Practices (ADSP)Updated
August 2009
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?