RFC 5016: Requirements for a DomainKeys Identified Mail (DKIM) Signing Practices Protocol
In plain English — editorial summary, not part of the RFC
DomainKeys Identified Mail (DKIM) provides a cryptographic mechanism for domains to assert responsibility for the messages they handle. A related mechanism will allow an administrator to publish various statements about their DKIM signing practices. This document defines requirements for this mechanism, distinguishing between those that must be satisfied (MUST), and those that are highly desirable (SHOULD). This memo provides information for the Internet community.
Document record
- Document ID
- RFC5016
- Published
- October 2007
- Authors
- M. Thomas
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- art
- Pages
- 15
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3713A Description of the Camellia Encryption AlgorithmCurrent
April 2004
- RFC 3711The Secure Real-time Transport Protocol (SRTP)Updated
March 2004
- RFC 6518Keying and Authentication for Routing Protocols (KARP) Design GuidelinesCurrent
February 2012
- RFC 6813The Network Endpoint Assessment (NEA) Asokan Attack AnalysisCurrent
December 2012
- RFC 3218Preventing the Million Message Attack on Cryptographic Message SyntaxCurrent
January 2002
- RFC 3211Password-based Encryption for CMSObsoleted
December 2001
- RFC 3185Reuse of CMS Content Encryption KeysCurrent
October 2001
- RFC 3129Requirements for Kerberized Internet Negotiation of KeysCurrent
June 2001
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?