| RFC 9519 | IANA SSH Registry Requirements | January 2024 |
| Yee | Standards Track | [Page] |
This specification updates the registration policies for adding new entries to registries within the IANA "Secure Shell (SSH) Protocol Parameters" group of registries. Previously, the registration policy was generally IETF Review, as defined in RFC 8126, although a few registries require Standards Action. This specification changes it from IETF Review to Expert Review. This document updates RFCs 4250, 4716, 4819, and 8308.¶
This is an Internet Standards Track document.¶
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841.¶
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc9519.¶
Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
The IANA "Secure Shell (SSH) Protocol Parameters" registry was populated by several RFCs including [RFC4250], [RFC4716], [RFC4819], and [RFC8308]. Outside of some narrow value ranges that require Standards Action in order to add new values or that are marked for Private Use, the registration policy for other portions of the registry was IETF Review [RFC8126]. This specification changes the policy from IETF Review to Expert Review. This change is in line with similar changes undertaken for certain IPsec and TLS registries.¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶
The following table lists the "Secure Shell (SSH) Protocol Parameters" registries whose registration policy has changed from IETF Review to Expert Review. Where this change applied to a specific range of values within the particular parameter, that range is given in the notes column. Affected registries now list this document as a reference.¶
| Parameter Name | RFC | Notes |
|---|---|---|
| Authentication Method Names | [RFC4250] | |
| Channel Connection Failure Reason Codes and Descriptions | [RFC4250] | 0x00000001-0xFDFFFFFF (inclusive) |
| Compression Algorithm Names | [RFC4250] | |
| Connection Protocol Channel Request Names | [RFC4250] | |
| Connection Protocol Channel Types | [RFC4250] | |
| Connection Protocol Global Request Names | [RFC4250] | |
| Connection Protocol Subsystem Names | [RFC4250] | |
| Disconnection Messages Reason Codes and Descriptions | [RFC4250] | 0x00000001-0xFDFFFFFF (inclusive) |
| Encryption Algorithm Names | [RFC4250] | |
| Extended Channel Data Transfer data_type_code and Data | [RFC4250] | 0x00000001-0xFDFFFFFF (inclusive) |
| Extension Names | [RFC8308] | |
| Key Exchange Method Names | [RFC4250] | |
| MAC Algorithm Names | [RFC4250] | |
| Pseudo-Terminal Encoded Terminal Modes | [RFC4250] | |
| Public Key Algorithm Names | [RFC4250] | |
| Publickey Subsystem Attributes | [RFC4819] | |
| Publickey Subsystem Request Names | [RFC4819] | |
| Publickey Subsystem Response Names | [RFC4819] | |
| Service Names | [ |