[rfc-dist] RFC 8731 on Secure Shell (SSH) Key Exchange Method Using Curve25519 and Curve448

[rfc-editor at rfc-editor.org (rfc-editor at rfc-editor.org)]

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

        
        RFC 8731

        Title:      Secure Shell (SSH) Key Exchange Method
                    Using Curve25519 and Curve448 
        Author:     A. Adamantiadis,
                    S. Josefsson,
                    M. Baushke
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2020
        Mailbox:    aris at badcode.be, 
                    simon at josefsson.org, 
                    mdb at juniper.net
        Pages:      6
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-curdle-ssh-curves-12.txt

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

        DOI:        10.17487/RFC8731

This document describes the specification for using Curve25519 and
Curve448 key exchange methods in the Secure Shell (SSH) protocol.

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 at 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