Skip to main content

8. IANA Considerations

  1. IANA Considerations

This document is part of a set. The instructions for the IANA for the SSH protocol, as defined in this document, [SSH-USERAUTH], [SSH-TRANS], and [SSH-CONNECT], are detailed in [SSH-NUMBERS]. The following is a brief summary for convenience, but note well that [SSH-NUMBERS] contains the actual instructions to the IANA, which may be superseded in the future.

Allocation of the following types of names in the SSH protocols is assigned by IETF consensus:

o Service Names

  • Authentication Methods
  • Connection Protocol Channel Names
  • Connection Protocol Global Request Names
  • Connection Protocol Channel Request Names

o Key Exchange Method Names

o Assigned Algorithm Names

  • Encryption Algorithm Names
  • MAC Algorithm Names
  • Public Key Algorithm Names
  • Compression Algorithm Names

These names MUST be printable US-ASCII strings, and MUST NOT contain the characters at-sign ("@"), comma (","), whitespace, control characters (ASCII codes 32 or less), or the ASCII code 127 (DEL). Names are case-sensitive, and MUST NOT be longer than 64 characters.

Names with the at-sign ("@") are locally defined extensions and are not controlled by the IANA.

RFC 4251 SSH Protocol Architecture January 2006

Each category of names listed above has a separate namespace. However, using the same name in multiple categories SHOULD be avoided to minimize confusion.

Message numbers (see Section 7) in the range of 0 to 191 are allocated via IETF CONSENSUS, as described in [RFC2434]. Message numbers in the 192 to 255 range (local extensions) are reserved for PRIVATE USE, also as described in [RFC2434].

Last updated on