RFC 8308: Extension Negotiation in the Secure Shell (SSH) Protocol
In plain English — editorial summary, not part of the RFC
This memo updates RFCs 4251, 4252, 4253, and 4254 by defining a mechanism for Secure Shell (SSH) clients and servers to exchange information about supported protocol extensions confidentially after SSH key exchange.
Document record
- Document ID
- RFC8308
- Published
- March 2018
- Authors
- D. Bider
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 14
- Also known as
- —
- Updated by:
- RFC 9519
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8332Use of RSA Keys with SHA-256 and SHA-512 in the Secure Shell (SSH) ProtocolCurrent
March 2018
- RFC 8651Dynamic Link Exchange Protocol (DLEP) Control-Plane-Based Pause ExtensionCurrent
October 2019
- RFC 9681IS-IS Fast FloodingCurrent
November 2024
- RFC 8314Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and AccessUpdated
January 2018
- RFC 8322Resource-Oriented Lightweight Information Exchange (ROLIE)Current
February 2018
- RFC 8329Framework for Interface to Network Security FunctionsCurrent
February 2018
- RFC 8274Incident Object Description Exchange Format Usage GuidanceCurrent
November 2017
- RFC 8270Increase the Secure Shell Minimum Recommended Diffie-Hellman Modulus Size to 2048 BitsCurrent
December 2017
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?