Domain-Based Email Authentication Using Public Keys Advertised in the DNS
RFC 4870, “Domain-Based Email Authentication Using Public Keys Advertised in the DNS”, is a Historic document published in May 2007 by M. Delany. It has been obsoleted by RFC 4871 — refer to the newer document for the authoritative version. The canonical text is published by the RFC Editor.
Abstract
"DomainKeys" creates a domain-level authentication framework for email by using public key technology and the DNS to prove the provenance and contents of an email.
This document defines a framework for digitally signing email on a per-domain basis. The ultimate goal of this framework is to unequivocally prove and protect identity while retaining the semantics of Internet email as it is known today.
Proof and protection of email identity may assist in the global control of "spam" and "phishing". This memo defines a Historic Document for the Internet community.
What “Historic” means
A specification that has been superseded or is otherwise no longer recommended for use.
The canonical text of RFC 4870 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 4869 Suite B Cryptographic Suites for IPsec
- RFC 4871 DomainKeys Identified Mail Signatures
- RFC 4868 Using HMAC-SHA-256, HMAC-SHA-384, and HMAC-SHA-512 with IPsec
- RFC 4872 RSVP-TE Extensions in Support of End-to-End Generalized Multi- Protocol Label Switching Recovery
- RFC 4867 RTP Payload Format and File Storage Format for the Adaptive Multi- Rate and Adaptive Multi-Rate Wideband Audio Codecs
- RFC 4873 GMPLS Segment Recovery
- RFC 4866 Enhanced Route Optimization for Mobile IPv6
- RFC 4874 Exclude Routes - Extension to Resource ReserVation Protocol-Traffic Engineering