Update to the IANA SSH Protocol Parameters Registry Requirements
RFC 9519
Peter E. Yee
AKAYLA
Mountain View
CA
94043
United States of America
peter@akayla.com
January 2024
sec
ssh
iana
registry
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.
Introduction
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.
Requirements Language
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.
SSH Protocol Parameters Affected
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.
Secure Shell (SSH) Protocol Parameters Affected
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 | [RFC4250] |
Signal Names | [RFC4250] |
SSH Public-Key File Header Tags | [RFC4716] | Excluding header-tags beginning with x-
The only IANA SSH protocol parameter registries not affected are "Message Numbers" and "Publickey Subsystem Status Codes", as these remain Standards Action due to their limited resources as one-byte registry values.
Designated Expert Pool
Expert Review [RFC8126] registry requests are registered after a three-week review period on the <ssh-reg-review@ietf.org> mailing list, and on the advice of one or more designated experts. However, to allow for the allocation of values prior to publication, the designated experts may approve registration once they are satisfied that such a specification will be published.
Registration requests sent to the mailing list for review SHOULD use an appropriate subject (e.g., "Request to register value in SSH protocol parameters <specific parameter> registry").
Within the review period, the designated experts will either approve or deny the registration request, communicating this decision to the review list and IANA. Denials MUST include an explanation and, if applicable, suggestions as to how to make the request successful. Registration requests that are undetermined for a period longer than 21 days can be brought to the IESG's attention (using the <iesg@ietf.org> mailing list) for resolution.
Criteria that SHOULD be applied by the designated experts includes determining whether the proposed registration duplicates existing functionality (which is not permitted), whether it is likely to be of general applicability or useful only for a single application, and whether the registration description is clear.
IANA MUST only accept registry updates from the designated experts and the IESG. It SHOULD direct all requests for registration from other sources to the review mailing list.
It is suggested that multiple designated experts be appointed who are able to represent the perspectives of different applications using this specification, in order to enable broadly informed review of registration decisions. In cases where a registration decision could be perceived as creating a conflict of interest for a particular expert, that expert SHOULD defer to the judgment of the other experts.
IANA Considerations
This memo is entirely about updating the IANA "Secure Shell (SSH) Protocol Parameters" registry.
Security Considerations
This memo does not change the Security Considerations for any of the updated RFCs.
References
Normative References
Informative References
[CURDLE-MA]

Subject: [Curdle] Time to Review IANA SSH Registries Policies?
Sean Turner
February 2021
message to the Curdle mailing list
[RFC4250]
[RFC4716]
[RFC4819]
[RFC8308]
[RFC8126]
[RFC2119]
[RFC8174]
Acknowledgements
The impetus for this specification was a February 2021 discussion on the CURDLE mailing list [CURDLE-MA].