[rfc-dist] RFC 8080 on Edwards-Curve Digital Security Algorithm (EdDSA) for DNSSEC

rfc-editor@rfc-editor.org Wed, 15 February 2017 01:40 UTC

Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25A23129990 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 14 Feb 2017 17:40:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 38g-_6cThzXo for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 14 Feb 2017 17:40:30 -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 E5C841299BB for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue, 14 Feb 2017 17:40:05 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id E91F5B814E3; Tue, 14 Feb 2017 17:40:01 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 7E732B814D7; Tue, 14 Feb 2017 17:40:00 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170215014000.7E732B814D7@rfc-editor.org>
Date: Tue, 14 Feb 2017 17:40:00 -0800
Subject: [rfc-dist] RFC 8080 on Edwards-Curve Digital Security Algorithm (EdDSA) for DNSSEC
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, curdle@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: rfc-dist <rfc-dist-bounces@rfc-editor.org>

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

        
        RFC 8080

        Title:      Edwards-Curve Digital Security Algorithm (EdDSA) 
                    for DNSSEC 
        Author:     O. Sury, 
                    R. Edmonds
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2017
        Mailbox:    ondrej.sury@nic.cz, 
                    edmonds@mycre.ws
        Pages:      7
        Characters: 13513
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-curdle-dnskey-eddsa-03.txt

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

        DOI:        10.17487/RFC8080

This document describes how to specify Edwards-curve Digital Security
Algorithm (EdDSA) keys and signatures in DNS Security (DNSSEC).  It
uses EdDSA with the choice of two curves: Ed25519 and Ed448.

This document is a product of the CURves, Deprecating and a Little more Encryption 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


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org