RFC 8463 on A New Cryptographic Signature Method for DomainKeys Identified Mail (DKIM)

rfc-editor@rfc-editor.org Wed, 12 September 2018 23:17 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 AC98F129C6B; Wed, 12 Sep 2018 16:17:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qvicoOMKU8jY; Wed, 12 Sep 2018 16:17:09 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 67D50126F72; Wed, 12 Sep 2018 16:17:09 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id C4FDCB80C0D; Wed, 12 Sep 2018 16:17:06 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDg0NjMgb24gQSBOZXcgQ3J5cHRvZ3JhcGhpYyBTaWduYXR1cmUgTWV0aG9kIGZvciBEb21haW5LZXlzIElkZW50aWZpZWQgTWFpbCAoREtJTSk=?=
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, dcrup@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20180912231706.C4FDCB80C0D@rfc-editor.org>
Date: Wed, 12 Sep 2018 16:17:06 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/mk-34mBRW2om2-ZYqx6rxHwNL5A>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 12 Sep 2018 23:17:11 -0000

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

        
        RFC 8463

        Title:      A New Cryptographic Signature Method 
                    for DomainKeys Identified Mail (DKIM) 
        Author:     J. Levine
        Status:     Standards Track
        Stream:     IETF
        Date:       September 2018
        Mailbox:    standards@taugh.com
        Pages:      7
        Characters: 14152
        Updates:    RFC 6376

        I-D Tag:    draft-ietf-dcrup-dkim-crypto-14.txt

        URL:        https://www.rfc-editor.org/info/rfc8463

        DOI:        10.17487/RFC8463

This document adds a new signing algorithm, Ed25519-SHA256, to
"DomainKeys Identified Mail (DKIM) Signatures" (RFC 6376).  DKIM
verifiers are required to implement this algorithm.

This document is a product of the DKIM Crypto Update Working Group of the IETF.

This is now a Proposed 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 Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) 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
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

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