[ietf-dkim] RFC 4870 on Domain-Based Email Authentication Using Public Keys Advertised in the DNS (DomainKeys) (fwd)
John Levine <johnl@iecc.com> Wed, 23 May 2007 02:57 UTC
Return-path: <ietf-dkim-bounces@mipassoc.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hqh2l-0003EK-KC for ietf-dkim-archive@lists.ietf.org; Tue, 22 May 2007 22:57:43 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hqh2l-00018L-5u for ietf-dkim-archive@lists.ietf.org; Tue, 22 May 2007 22:57:43 -0400
Received: from sb7.songbird.com (sb7.songbird.com [127.0.0.1]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l4N2ub3i015938; Tue, 22 May 2007 19:56:37 -0700
Received: from gal.iecc.com (gal.iecc.com [208.31.42.53]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l4N2tl7w015849 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-dkim@mipassoc.org>; Tue, 22 May 2007 19:55:48 -0700
Received: (qmail 25539 invoked from network); 23 May 2007 02:55:50 -0000
Received: from simone.iecc.com (208.31.42.47) by mail1.iecc.com with QMQP; 23 May 2007 02:55:50 -0000
Date: Wed, 23 May 2007 02:55:50 -0000
Message-ID: <20070523025550.52065.qmail@simone.iecc.com>
From: John Levine <johnl@iecc.com>
To: ietf-dkim@mipassoc.org
In-Reply-To: <20070523000838.GG16866@isi.edu>
Organization:
Cc:
Mime-Version: 1.0
Content-type: text/plain; charset="iso-8859-1"
Content-transfer-encoding: 7bit
X-Songbird: Clean, Clean
Subject: [ietf-dkim] RFC 4870 on Domain-Based Email Authentication Using Public Keys Advertised in the DNS (DomainKeys) (fwd)
X-BeenThere: ietf-dkim@mipassoc.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF DKIM Discussion List <ietf-dkim.mipassoc.org>
List-Unsubscribe: <http://mipassoc.org/mailman/listinfo/ietf-dkim>, <mailto:ietf-dkim-request@mipassoc.org?subject=unsubscribe>
List-Archive: <http://mipassoc.org/pipermail/ietf-dkim>
List-Post: <mailto:ietf-dkim@mipassoc.org>
List-Help: <mailto:ietf-dkim-request@mipassoc.org?subject=help>
List-Subscribe: <http://mipassoc.org/mailman/listinfo/ietf-dkim>, <mailto:ietf-dkim-request@mipassoc.org?subject=subscribe>
Sender: ietf-dkim-bounces@mipassoc.org
Errors-To: ietf-dkim-bounces@mipassoc.org
X-SongbirdInformation: support@songbird.com for more information
X-Songbird-From: ietf-dkim-bounces@mipassoc.org
X-Spam-Score: -0.1 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
RFC 4870 on DK was published at the same time. (The correction in the message title is, as far as I can tell, the first version left out the bit about 4870 being obsoleted by 4871.) R's, John From: "RFC Editor" <rfc-editor@rfc-editor.org> Subject: Correction - Re: RFC 4870 on Domain-Based Email Authentication Using Public Keys Advertised in the DNS (DomainKeys) Date: Wed, 23 May 2007 02:03:02 +0000 (UTC) Organization: Taughannock Networks, Trumansburg NY 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 Obsoleted By: RFC 4871 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 --=508762=---- _______________________________________________ NOTE WELL: This list operates according to http://mipassoc.org/dkim/ietf-list-rules.html