RFC 8709: Ed25519 and Ed448 Public Key Algorithms for the Secure Shell (SSH) Protocol
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC8709
- Published
- February 2020
- Authors
- B. Harris; L. Velvindron
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 7
- Also known as
- —
- Updates:
- RFC 4253
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8708Use of the HSS/LMS Hash-Based Signature Algorithm in the Cryptographic Message Syntax (CMS)Obsoleted
February 2020
- RFC 8707Resource Indicators for OAuth 2.0Current
February 2020
- RFC 8705OAuth 2.0 Mutual-TLS Client Authentication and Certificate-Bound Access TokensCurrent
February 2020
- RFC 8702Use of the SHAKE One-Way Hash Functions in the Cryptographic Message Syntax (CMS)Current
January 2020
- RFC 8701Applying Generate Random Extensions And Sustain Extensibility (GREASE) to TLS ExtensibilityCurrent
January 2020
- RFC 8696Using Pre-Shared Key (PSK) in the Cryptographic Message Syntax (CMS)Current
December 2019
- RFC 8693OAuth 2.0 Token ExchangeCurrent
January 2020
- RFC 8725JSON Web Token Best Current PracticesCurrent
February 2020
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?