STD 76, RFC 6376 on DomainKeys Identified Mail (DKIM) Signatures
rfc-editor@rfc-editor.org Thu, 11 July 2013 19:51 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84DBD21F99F3 for <ietf-announce@ietfa.amsl.com>; Thu, 11 Jul 2013 12:51:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.885
X-Spam-Level:
X-Spam-Status: No, score=-101.885 tagged_above=-999 required=5 tests=[AWL=0.115, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JZKqm+GnNXng for <ietf-announce@ietfa.amsl.com>; Thu, 11 Jul 2013 12:51:30 -0700 (PDT)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 4DF0121F972C for <ietf-announce@ietf.org>; Thu, 11 Jul 2013 12:50:53 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 88E9A6210F; Thu, 11 Jul 2013 12:48:30 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: STD 76, RFC 6376 on DomainKeys Identified Mail (DKIM) Signatures
From: rfc-editor@rfc-editor.org
Message-Id: <20130711194830.88E9A6210F@rfc-editor.org>
Date: Thu, 11 Jul 2013 12:48:30 -0700
Cc: ietf-dkim@mipassoc.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Jul 2013 19:51:31 -0000
RFC 6376 has been elevated to Internet Standard. STD 76 RFC 6376 Title: DomainKeys Identified Mail (DKIM) Signatures Author: D. Crocker, Ed., T. Hansen, Ed., M. Kucherawy, Ed. Status: Standards Track Stream: IETF Date: September 2011 Mailbox: dcrocker@bbiw.net, tony+dkimov@maillennium.att.com, msk@cloudmark.com Pages: 76 Characters: 176999 Obsoletes: RFC 4871, RFC 5672 See Also: STD 76 I-D Tag: draft-ietf-dkim-rfc4871bis-15.txt URL: http://www.rfc-editor.org/rfc/rfc6376.txt DomainKeys Identified Mail (DKIM) permits a person, role, or organization that owns the signing domain to claim some responsibility for a message by associating the domain with the message. This can be an author's organization, an operational relay, or one of their agents. DKIM separates the question of the identity of the Signer of the message from the purported author of the message. Assertion of responsibility is validated through a cryptographic signature and by querying the Signer's domain directly to retrieve the appropriate public key. Message transit from author to recipient is through relays that typically make no substantive change to the message content and thus preserve the DKIM signature. This memo obsoletes RFC 4871 and RFC 5672. [STANDARDS-TRACK] This document is a product of the Domain Keys Identified Mail Working Group of the IETF. This is now an Internet Standard. 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 unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC