DomainKeys Identified Mail Development, Deployment, and Operations
RFC 5863, “DomainKeys Identified Mail Development, Deployment, and Operations”, is an Informational document published in May 2010 by T. Hansen, E. Siegel, P. Hallam-Baker, D. Crocker. The canonical text is published by the RFC Editor.
Abstract
DomainKeys Identified Mail (DKIM) allows an organization to claim responsibility for transmitting a message, in a way that can be validated by a recipient. The organization can be the author's, the originating sending site, an intermediary, or one of their agents. A message can contain multiple signatures, from the same or different organizations involved with the message. DKIM defines a domain-level digital signature authentication framework for email, using public key cryptography and using the domain name service as its key server technology. This permits verification of a responsible organization, as well as the integrity of the message content. DKIM will also provide a mechanism that permits potential email signers to publish information about their email signing practices; this will permit email receivers to make additional assessments about messages. DKIM's authentication of email identity can assist in the global control of "spam" and "phishing". This document provides implementation, deployment, operational, and migration considerations for DKIM. This document is not an Internet Standards Track specification; it is published for informational purposes.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 5863 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5862 Path Computation Clients - Path Computation Element Requirements for Point-to-Multipoint MPLS-TE
- RFC 5864 DNS SRV Resource Records for AFS
- RFC 5861 HTTP Cache-Control Extensions for Stale Content
- RFC 5865 A Differentiated Services Code Point for Capacity-Admitted Traffic
- RFC 5860 Requirements for Operations, Administration, and Maintenance in MPLS Transport Networks
- RFC 5866 Diameter Quality-of-Service Application
- RFC 5859 TFTP Server Address Option for DHCPv4
- RFC 5867 Building Automation Routing Requirements in Low-Power and Lossy Networks