RFC 8709 on Ed25519 and Ed448 Public Key Algorithms for the Secure Shell (SSH) Protocol

rfc-editor@rfc-editor.org Wed, 26 February 2020 00:58 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 BEC483A00D9; Tue, 25 Feb 2020 16:58:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=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 2UN2jGDn4ttm; Tue, 25 Feb 2020 16:58:47 -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 221493A0042; Tue, 25 Feb 2020 16:58:47 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id DB2F1F40719; Tue, 25 Feb 2020 16:58:34 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDg3MDkgb24gRWQyNTUxOSBhbmQgRWQ0NDggUHVibGljIEtleSBBbGdvcml0aG1zIGZvciB0aGUgU2VjdXJlIFNoZWxsIChTU0gpIFByb3RvY29s?=
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, curdle@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20200226005834.DB2F1F40719@rfc-editor.org>
Date: Tue, 25 Feb 2020 16:58:34 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/DPo4GujE2rS5KevjWXu9shhKtkM>
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, 26 Feb 2020 00:58:50 -0000

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

        
        RFC 8709

        Title:      Ed25519 and Ed448 Public Key Algorithms 
                    for the Secure Shell (SSH) Protocol 
        Author:     B. Harris,
                    L. Velvindron
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2020
        Mailbox:    bjh21@bjh21.me.uk, 
                    logan@cyberstorm.mu
        Pages:      7
        Updates:    RFC 4253

        I-D Tag:    draft-ietf-curdle-ssh-ed25519-ed448-11.txt

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

        DOI:        10.17487/RFC8709

This document describes the use of the Ed25519 and Ed448 digital
signature algorithms in the Secure Shell (SSH) protocol. Accordingly,
this RFC updates RFC 4253.

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