RFC 4250: The Secure Shell (SSH) Protocol Assigned Numbers
In plain English — editorial summary, not part of the RFC
This document defines the instructions to the IANA and the initial state of the IANA assigned numbers for the Secure Shell (SSH) protocol. It is intended only for the initialization of the IANA registries referenced in the set of SSH documents. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4250
- Published
- January 2006
- Authors
- S. Lehtinen; C. Lonvick
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 20
- Also known as
- —
Topics
Referenced by
3 later RFCs formally update or obsolete part of this document.
- RFC 8268More Modular Exponentiation (MODP) Diffie-Hellman (DH) Key Exchange (KEX) Groups for Secure Shell (SSH)Current
December 2017
- RFC 9142Key Exchange (KEX) Method Updates and Recommendations for Secure Shell (SSH)Current
January 2022
- RFC 9519Update to the IANA SSH Protocol Parameters Registry RequirementsCurrent
January 2024
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4251The Secure Shell (SSH) Protocol ArchitectureUpdated
January 2006
- RFC 4252The Secure Shell (SSH) Authentication ProtocolUpdated
January 2006
- RFC 4253The Secure Shell (SSH) Transport Layer ProtocolUpdated
January 2006
- RFC 4254The Secure Shell (SSH) Connection ProtocolUpdated
January 2006
- RFC 4256Generic Message Exchange Authentication for the Secure Shell Protocol (SSH)Current
January 2006
- RFC 4255Using DNS to Securely Publish Secure Shell (SSH) Key FingerprintsCurrent
January 2006
- RFC 4262X.509 Certificate Extension for Secure/Multipurpose Internet Mail Extensions (S/MIME) CapabilitiesCurrent
December 2005
- RFC 4279Pre-Shared Key Ciphersuites for Transport Layer Security (TLS)Updated
December 2005
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?