RFC 8032 on Edwards-Curve Digital Signature Algorithm (EdDSA)

rfc-editor@rfc-editor.org Wed, 25 January 2017 00:48 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 5164E1295EC for <ietf-announce@ietfa.amsl.com>; Tue, 24 Jan 2017 16:48:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.401
X-Spam-Level:
X-Spam-Status: No, score=-7.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, 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 Jny9i9BcgBVF for <ietf-announce@ietfa.amsl.com>; Tue, 24 Jan 2017 16:47:58 -0800 (PST)
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 EB7E81295EA for <ietf-announce@ietf.org>; Tue, 24 Jan 2017 16:47:58 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id D41B7B81105; Tue, 24 Jan 2017 16:47:58 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org, irtf-announce@irtf.org
Subject: RFC 8032 on Edwards-Curve Digital Signature Algorithm (EdDSA)
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170125004758.D41B7B81105@rfc-editor.org>
Date: Tue, 24 Jan 2017 16:47:58 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/QmP47tXe7kiGVohVoRPNC3fMErs>
Cc: drafts-update-ref@iana.org, cfrg@irtf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
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: <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, 25 Jan 2017 00:48:00 -0000

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

        
        RFC 8032

        Title:      Edwards-Curve Digital Signature Algorithm (EdDSA) 
        Author:     S. Josefsson, I. Liusvaara
        Status:     Informational
        Stream:     IRTF
        Date:       January 2017
        Mailbox:    simon@josefsson.org, 
                    ilariliusvaara@welho.com
        Pages:      60
        Characters: 103210
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-irtf-cfrg-eddsa-08.txt

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

        DOI:        10.17487/RFC8032

This document describes elliptic curve signature scheme Edwards-curve
Digital Signature Algorithm (EdDSA).  The algorithm is instantiated
with recommended parameters for the edwards25519 and edwards448
curves.  An example implementation and test vectors are provided.

This document is a product of the Crypto Forum Research Group of the IRTF.


INFORMATIONAL: This memo provides information 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-Announce, rfc-dist and IRTF-Announce lists.  To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
  https://www.irtf.org/mailman/listinfo/irtf-announce

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