RFC 4871 on DomainKeys Identified Mail (DKIM) Signatures

rfc-editor@rfc-editor.org Wed, 23 May 2007 00:06 UTC

Return-path: <ietf-announce-bounces@ietf.org>
Received: from [] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HqeNW-0006Lw-CT; Tue, 22 May 2007 20:06:58 -0400
Received: from [] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HqeNU-0006JD-R1 for ietf-announce@ietf.org; Tue, 22 May 2007 20:06:56 -0400
Received: from nit.isi.edu ([]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HqeNU-0001WF-Ew for ietf-announce@ietf.org; Tue, 22 May 2007 20:06:56 -0400
Received: from nit.isi.edu (loopback []) by nit.isi.edu ( with ESMTP id l4N06uIV026550; Tue, 22 May 2007 17:06:56 -0700
Received: (from apache@localhost) by nit.isi.edu ( id l4N06tdi026549; Tue, 22 May 2007 17:06:55 -0700
Date: Tue, 22 May 2007 17:06:55 -0700
Message-Id: <200705230006.l4N06tdi026549@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
X-Spam-Score: -14.8 (--------------)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Cc: ietf-dkim@mipassoc.org, rfc-editor@rfc-editor.org
Subject: RFC 4871 on DomainKeys Identified Mail (DKIM) Signatures
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Errors-To: ietf-announce-bounces@ietf.org

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

        RFC 4871

        Title:      DomainKeys Identified Mail (DKIM) Signatures 
        Author:     E. Allman, J. Callas,
                    M. Delany, M. Libbey,
                    J. Fenton, M. Thomas
        Status:     Standards Track
        Date:       May 2007
        Mailbox:    eric+dkim@sendmail.org, 
                    fenton@cisco.com,  mat@cisco.com
        Pages:      71
        Characters: 166054
        Obsoletes:  RFC4870

        I-D Tag:    draft-ietf-dkim-base-10.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4871.txt

DomainKeys Identified Mail (DKIM) defines a domain-level
authentication framework for email using public-key cryptography and
key server technology to permit verification of the source and
contents of messages by either Mail Transfer Agents (MTAs) or Mail
User Agents (MUAs).  The ultimate goal of this framework is to permit
a signing domain to assert responsibility for a message, thus
protecting message signer identity and the integrity of the messages
they convey while retaining the functionality of Internet email as it
is known today.  Protection of email identity may assist in the
global control of "spam" and "phishing".  [STANDARDS TRACK]

This document is a product of the Domain Keys Identified Mail
Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and 
suggestions for improvements.Please refer to the current edition of the 
Internet Official Protocol Standards (STD 1) for the standardization 
state and status of this protocol.  Distribution of this memo is 

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

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