DomainKeys Identified Mail Signatures
RFC 6376, “DomainKeys Identified Mail Signatures”, is an Internet Standard document published in September 2011 by D. Crocker, T. Hansen, M. Kucherawy. It obsoletes RFC 4871, RFC 5672. It has since been updated by RFC 8301, RFC 8463, RFC 8553, RFC 8616. The canonical text is published by the RFC Editor.
Abstract
DomainKeys Identified Mail (DKIM) permits a person, role, or organization that owns the signing domain to claim some responsibility for a message by associating the domain with the message. This can be an author's organization, an operational relay, or one of their agents. DKIM separates the question of the identity of the Signer of the message from the purported author of the message. Assertion of responsibility is validated through a cryptographic signature and by querying the Signer's domain directly to retrieve the appropriate public key. Message transit from author to recipient is through relays that typically make no substantive change to the message content and thus preserve the DKIM signature.
This memo obsoletes RFC 4871 and RFC 5672. [STANDARDS-TRACK]
What “Internet Standard” means
A mature, widely-implemented specification that has completed the full IETF standards process — the highest maturity level on the standards track.
The canonical text of RFC 6376 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6375 A Packet Loss and Delay Measurement Profile for MPLS-Based Transport Networks
- RFC 6377 DomainKeys Identified Mail and Mailing Lists
- RFC 6374 Packet Loss and Delay Measurement for MPLS Networks
- RFC 6378 MPLS Transport Profile Linear Protection
- RFC 6373 MPLS Transport Profile Control Plane Framework
- RFC 6379 Suite B Cryptographic Suites for IPsec
- RFC 6372 MPLS Transport Profile Survivability Framework
- RFC 6380 Suite B Profile for Internet Protocol Security