IANA
Click on the red underlined text to get to the source
... to create the initial state of the IANA databases for the SSH
protocol and also contains instructions for future assignments.
Except for one HISTORIC algorithm ...
... purpose defined by the local site. No attempt is made to prevent
multiple sites from using the same value in different (and
incompatible) ways. There is no need for IANA to review such
assignments and assignments are not generally useful for
interoperability ...
... HIERARCHICAL ALLOCATION - Delegated managers can assign values
provided they have been given control over that part of the name
space. IANA controls the higher levels of the namespace according to
one of the other policies.
...
... long as they provide a point of contact and a brief description of
what the value would be used for. For numbers, the exact value is
generally assigned by the IANA; with names, specific names are
usually requested.
...
... IANA Considerations ...
...
This entire document is the IANA considerations for the SSH protocol,
as defined in [SSH-ARCH ...
... method, as described in
[RFC2434]. The IANA will not assign Disconnection Message 'reason
code' values in the range ...
...
While it is understood that the IANA will have no control over the
range of 0xFE000000 to 0xFFFFFFFF, this range ...
... session@example.com"
but fails, then the server will respond with either a 'reason
code' assigned by the IANA (as listed above and in the range of
0x00000001 to 0xFDFFFFFF), or with a locally assigned value in the
...
... that is consistent with the proposed local 'channel type'. It is
assumed that practitioners will first attempt to use the IANA-
assigned 'reason code' values and then document their locally
assigned 'reason code' values.
...
...
In the following sections, the values for the name spaces are
textual. The conventions and instructions to the IANA for future
assignments are given in this section. The initial assignments are
given in their respective sections.
...
...
All names registered by the IANA in the following sections MUST be
printable US-ASCII strings, and MUST NOT contain the characters at-
...
... and MUST NOT be longer than 64 characters.
A provision is made here for locally extensible names. The IANA will
not register, and will not control, names with the at-sign in them.
...
... Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998. ...