RFC 4870 on Domain-Based Email Authentication Using Public Keys Advertised in the DNS (DomainKeys)

A new Request for Comments is now available in online RFC libraries.

        RFC 4870

        Title:      Domain-Based Email Authentication Using Public 
                    Keys Advertised in the DNS (DomainKeys) 
        Author:     M. Delany
        Status:     Historic
        Date:       May 2007
        Mailbox:    markd+domainkeys@yahoo-inc.com
        Pages:      41
        Characters: 87378
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-delany-domainkeys-base-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4870.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@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

The RFC Editor Team
USC/Information Sciences Institute

...

_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce