DomainKeys Identified Mail (DKIM) Development, Deployment, and Operations (RFC5863)
Original Publication Date: 2010-May-01
Included in the Prior Art Database: 2010-May-28
Internet Society Requests For Comment (RFCs)
T. Hansen: AUTHOR [+4]
DomainKeys Identified Mail (DKIM) allows an organization to claim responsibility for transmitting a message, in a way that can be validated by a recipient. This document provides practical tips for those who are developing DKIM software, mailing list managers, filtering strategies based on the output from DKIM verification, and DNS servers; those who are deploying DKIM software, keys, mailing list software, and migrating from DomainKeys [RFC4870]; and those who are responsible for the ongoing operations of an email infrastructure that has deployed DKIM.
Internet Engineering Task Force (IETF) T. Hansen Request for Comments: 5863 AT&T Laboratories Category: Informational E. Siegel ISSN: 2070-1721 Consultant P. Hallam-Baker Default Deny Security, Inc. D. Crocker Brandenburg InternetWorking May 2010
DomainKeys Identified Mail (DKIM) Development, Deployment, and Operations
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
Status of This Memo
This document is not an Internet Standards Track specification; it is published for informational purposes.
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741.
Hansen, et al. Informational ...