[rfc-dist] RFC 4870 on Domain-Based Email Authentication Using Public Keys Advertised in the DNS (DomainKeys)
rfc-editor at rfc-editor.org
Tue May 22 17:06:47 PDT 2007
A new Request for Comments is now available in online RFC libraries.
Title: Domain-Based Email Authentication Using Public
Keys Advertised in the DNS (DomainKeys)
Author: M. Delany
Date: May 2007
Mailbox: markd+domainkeys at yahoo-inc.com
I-D Tag: draft-delany-domainkeys-base-06.txt
"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.
HISTORIC: This memo defines a Historic Document for the Internet
community. It does not specify an Internet standard of any kind.
Distribution of this memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info at RFC-EDITOR.ORG
Subject: getting rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
The RFC Editor Team
USC/Information Sciences Institute
More information about the rfc-dist