draft-ietf-secsh-assignednumbers-06.txt   draft-ietf-secsh-assignednumbers-07.txt 
Network Working Group S. Lehtinen Network Working Group C. Lonvick, Ed.
Internet-Draft SSH Communications Security Corp Internet-Draft Cisco Systems, Inc
Expires: December 1, 2004 C. Lonvick, Ed. Expires: April 24, 2005 October 24, 2004
Cisco Systems, Inc.
June 2, 2004
SSH Protocol Assigned Numbers SSH Protocol Assigned Numbers
draft-ietf-secsh-assignednumbers-06.txt draft-ietf-secsh-assignednumbers-07.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is subject to all provisions
all provisions of Section 10 of RFC2026. of section 3 of RFC 3667. By submitting this Internet-Draft, each
author represents that any applicable patent or other IPR claims of
which he or she is aware have been or will be disclosed, and any of
which he or she become aware will be disclosed, in accordance with
RFC 3668.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as other groups may also distribute working documents as
Internet-Drafts. Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on December 1, 2004. This Internet-Draft will expire on April 24, 2005.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2004).
Abstract Abstract
This document defines the initial state of the IANA assigned numbers This document defines the instructions to the IANA and the initial
for the SSH protocol. It is intended only for initialization of the state of the IANA assigned numbers for the SSH protocol. It is
IANA databases referenced in those documents. intended only for the initialization of the IANA registries
referenced in the documents.
Table of Contents Table of Contents
1. Editor's Note . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Editor's Note . . . . . . . . . . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Conventions Used in This Document . . . . . . . . . . . . . . 3 3. Conventions Used in This Document . . . . . . . . . . . . . 3
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . 4
4.1 Message Numbers . . . . . . . . . . . . . . . . . . . . . 3 4.1 Message Numbers . . . . . . . . . . . . . . . . . . . . . 4
4.1.1 Disconnect Codes . . . . . . . . . . . . . . . . . . . 5 4.1.1 Conventions . . . . . . . . . . . . . . . . . . . . . 4
4.2 Service Names . . . . . . . . . . . . . . . . . . . . . . 5 4.1.2 Initial Assignments . . . . . . . . . . . . . . . . . 5
4.2.1 Authentication Method Names . . . . . . . . . . . . . 6 4.1.3 Future Assignments . . . . . . . . . . . . . . . . . . 6
4.2.2 Connection Protocol Assigned Names . . . . . . . . . . 6 4.2 Disconnection Messages Reason Codes and Descriptions . . . 6
4.3 Key Exchange Method Names . . . . . . . . . . . . . . . . 7 4.2.1 Conventions . . . . . . . . . . . . . . . . . . . . . 6
4.4 Assigned Algorithm Names . . . . . . . . . . . . . . . . . 7 4.2.2 Initial Assignments . . . . . . . . . . . . . . . . . 6
4.4.1 Encryption Algorithm Names . . . . . . . . . . . . . . 8 4.2.3 Future Assignments . . . . . . . . . . . . . . . . . . 7
4.4.2 MAC Algorithm Names . . . . . . . . . . . . . . . . . 8 4.3 Channel Connection Failure Reason Codes and Descriptions . 7
4.4.3 Public Key Algorithm Names . . . . . . . . . . . . . . 8 4.3.1 Conventions . . . . . . . . . . . . . . . . . . . . . 7
4.4.4 Compression Algorithm Names . . . . . . . . . . . . . 9 4.3.2 Initial Assignments . . . . . . . . . . . . . . . . . 7
5. Intellectual Property . . . . . . . . . . . . . . . . . . . . 9 4.3.3 Future Assignments . . . . . . . . . . . . . . . . . . 7
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 4.4 Extended Channel Data Transfer data_type_code and Data . . 8
6.1 Normative References . . . . . . . . . . . . . . . . . . . . 9 4.4.1 Conventions . . . . . . . . . . . . . . . . . . . . . 8
6.2 Informative References . . . . . . . . . . . . . . . . . . . 10 4.4.2 Initial Assignments . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 10 4.4.3 Future Assignments . . . . . . . . . . . . . . . . . . 8
Intellectual Property and Copyright Statements . . . . . . . . 11 4.5 Pseudo-Terminal Encoded Terminal Modes . . . . . . . . . . 8
4.5.1 Conventions . . . . . . . . . . . . . . . . . . . . . 9
4.5.2 Initial Assignments . . . . . . . . . . . . . . . . . 9
4.5.3 Future Assignments . . . . . . . . . . . . . . . . . . 10
4.6 Names . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.6.1 Conventions for Names . . . . . . . . . . . . . . . . 11
4.6.2 Future Assignments of Names . . . . . . . . . . . . . 11
4.7 Service Names . . . . . . . . . . . . . . . . . . . . . . 11
4.8 Authentication Method Names . . . . . . . . . . . . . . . 12
4.9 Connection Protocol Assigned Names . . . . . . . . . . . . 12
4.9.1 Connection Protocol Channel Types . . . . . . . . . . 12
4.9.2 Connection Protocol Global Request Names . . . . . . . 12
4.9.3 Connection Protocol Channel Request Names . . . . . . 12
4.9.4 Initial Assignment of Signal Names . . . . . . . . . . 13
4.10 Key Exchange Method Names . . . . . . . . . . . . . . . 13
4.11 Assigned Algorithm Names . . . . . . . . . . . . . . . . 13
4.11.1 Encryption Algorithm Names . . . . . . . . . . . . . 14
4.11.2 MAC Algorithm Names . . . . . . . . . . . . . . . . 14
4.11.3 Public Key Algorithm Names . . . . . . . . . . . . . 14
4.11.4 Compression Algorithm Names . . . . . . . . . . . . 15
5. References . . . . . . . . . . . . . . . . . . . . . . . . . 15
5.1 Normative References . . . . . . . . . . . . . . . . . . . . 15
5.2 Informative References . . . . . . . . . . . . . . . . . . . 16
Author's Address . . . . . . . . . . . . . . . . . . . . . . 16
Intellectual Property and Copyright Statements . . . . . . . 17
1. Editor's Note 1. Editor's Note
The references in this document are statically defined. However, the The references in this document are statically defined. However, the
locations of the referenced materials are dynamic and are changing locations of the referenced materials are dynamic and are changing
with the whims of the Working Group. Please do not comment to the with the whims of the Working Group. Please do not comment to the
editor or the Working Group about inaccuracies along those lines in editor or the Working Group about inaccuracies along those lines in
this document at this time. (This paragraph will be removed before this document at this time. (This paragraph will be removed before
this document is submitted to the RFC Editor.) this document is submitted to the RFC Editor.)
2. Introduction 2. Introduction
This document does not define any new protocols. It is intended only This document does not define any new protocols. It is intended only
to create the initial state of the IANA databases for the SSH to create the initial state of the IANA databases for the SSH
protocol. Except for one HISTORIC algorithm generally regarded as protocol and also contains instructions for future assignments.
obsolete, this document does not define any new protocols or any Except for one HISTORIC algorithm generally regarded as obsolete,
number ranges not already defined in: [SSH-ARCH], [SSH-TRANS], this document does not define any new protocols or any number ranges
[SSH-USERAUTH], [SSH-CONNECT] not already defined in: [SSH-ARCH], [SSH-TRANS], [SSH-USERAUTH],
[SSH-CONNECT].
3. Conventions Used in This Document 3. Conventions Used in This Document
The keywords "MUST", "MUST NOT", "REQUIRED", "SHOULD", "SHOULD NOT", The keywords "MUST", "MUST NOT", "REQUIRED", "SHOULD", "SHOULD NOT",
and "MAY" that appear in this document are to be interpreted as and "MAY" that appear in this document are to be interpreted as
described in [RFC2119] described in [RFC2119].
The used data types and terminology are specified in the architecture The keywords "PRIVATE USE", "HIERARCHICAL ALLOCATION", "FIRST COME
document [SSH-ARCH] FIRST SERVED", "EXPERT REVIEW", "SPECIFICATION REQUIRED", "IESG
APPROVAL", "IETF CONSENSUS", and "STANDARDS ACTION" that appear in
this document when used to describe namespace allocation are to be
interpreted as described in [RFC2434]. These designations are
repeated in this document for clarity.
The architecture document also discusses the algorithm naming PRIVATE USE - For private or local use only, with the type and
conventions that MUST be used with the SSH protocols. 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.
FIRST COME FIRST SERVED - Anyone can obtain an assigned number, so
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.
EXPERT REVIEW - approval by a Designated Expert is required.
SPECIFICATION REQUIRED - Values and their meaning must be documented
in an RFC or other permanent and readily available reference, in
sufficient detail so that interoperability between independent
implementations is possible.
IESG APPROVAL - New assignments must be approved by the IESG, but
there is no requirement that the request be documented in an RFC
(though the IESG has discretion to request documents or other
supporting materials on a case-by-case basis).
IETF CONSENSUS - New values are assigned through the IETF consensus
process. Specifically, new assignments are made via RFCs approved by
the IESG. Typically, the IESG will seek input on prospective
assignments from appropriate persons (e.g., a relevant Working Group
if one exists).
STANDARDS ACTION - Values are assigned only for Standards Track RFCs
approved by the IESG.
4. IANA Considerations 4. IANA Considerations
This entire document is the IANA considerations for the SSH protocol
as is defined in [SSH-ARCH], [SSH-TRANS], [SSH-USERAUTH],
[SSH-CONNECT]. This section contains conventions used in naming the
namespaces, the initial state of the registry, and instructions for
future assignments.
4.1 Message Numbers 4.1 Message Numbers
The Message Number is an 8-bit value, which describes the payload of The Message Number is an 8-bit value, which describes the payload of
a packet. a packet.
4.1.1 Conventions
Protocol packets have message numbers in the range 1 to 255. These Protocol packets have message numbers in the range 1 to 255. These
numbers have been allocated as follows in [SSH-ARCH]: numbers are allocated as follows:
Transport layer protocol: Transport layer protocol:
1 to 19 Transport layer generic (e.g. disconnect, ignore, debug, etc.) 1 to 19 Transport layer generic (e.g. disconnect, ignore,
debug, etc.)
20 to 29 Algorithm negotiation 20 to 29 Algorithm negotiation
30 to 49 Key exchange method specific (numbers can be reused for 30 to 49 Key exchange method specific (numbers can be reused
different authentication methods) for different authentication methods)
User authentication protocol: User authentication protocol:
50 to 59 User authentication generic 50 to 59 User authentication generic
60 to 79 User authentication method specific (numbers can be 60 to 79 User authentication method specific (numbers can be
reused for different authentication methods) reused for different authentication methods)
Connection protocol: Connection protocol:
80 to 89 Connection protocol generic 80 to 89 Connection protocol generic
90 to 127 Channel related messages 90 to 127 Channel related messages
Reserved for client protocols: Reserved for client protocols:
128 to 191 Reserved 128 to 191 Reserved
Local extensions: Local extensions:
192 to 255 Local extensions 192 to 255 Local extensions
Requests for assignments of new message numbers must be accompanied 4.1.2 Initial Assignments
by an RFC which describes the new packet type. If the RFC is not on
the standards-track (i.e. it is an informational or experimental
RFC), it must be explicitly reviewed and approved by the IESG before
the RFC is published and the message number is assigned.
Message ID Value Reference Message ID Value Reference
----------- ----- --------- ----------- ----- ---------
SSH_MSG_DISCONNECT 1 [SSH-TRANS] SSH_MSG_DISCONNECT 1 [SSH-TRANS]
SSH_MSG_IGNORE 2 [SSH-TRANS] SSH_MSG_IGNORE 2 [SSH-TRANS]
SSH_MSG_UNIMPLEMENTED 3 [SSH-TRANS] SSH_MSG_UNIMPLEMENTED 3 [SSH-TRANS]
SSH_MSG_DEBUG 4 [SSH-TRANS] SSH_MSG_DEBUG 4 [SSH-TRANS]
SSH_MSG_SERVICE_REQUEST 5 [SSH-TRANS] SSH_MSG_SERVICE_REQUEST 5 [SSH-TRANS]
SSH_MSG_SERVICE_ACCEPT 6 [SSH-TRANS] SSH_MSG_SERVICE_ACCEPT 6 [SSH-TRANS]
SSH_MSG_KEXINIT 20 [SSH-TRANS] SSH_MSG_KEXINIT 20 [SSH-TRANS]
skipping to change at page 5, line 12 skipping to change at page 6, line 13
SSH_MSG_CHANNEL_OPEN_FAILURE 92 [SSH-CONNECT] SSH_MSG_CHANNEL_OPEN_FAILURE 92 [SSH-CONNECT]
SSH_MSG_CHANNEL_WINDOW_ADJUST 93 [SSH-CONNECT] SSH_MSG_CHANNEL_WINDOW_ADJUST 93 [SSH-CONNECT]
SSH_MSG_CHANNEL_DATA 94 [SSH-CONNECT] SSH_MSG_CHANNEL_DATA 94 [SSH-CONNECT]
SSH_MSG_CHANNEL_EXTENDED_DATA 95 [SSH-CONNECT] SSH_MSG_CHANNEL_EXTENDED_DATA 95 [SSH-CONNECT]
SSH_MSG_CHANNEL_EOF 96 [SSH-CONNECT] SSH_MSG_CHANNEL_EOF 96 [SSH-CONNECT]
SSH_MSG_CHANNEL_CLOSE 97 [SSH-CONNECT] SSH_MSG_CHANNEL_CLOSE 97 [SSH-CONNECT]
SSH_MSG_CHANNEL_REQUEST 98 [SSH-CONNECT] SSH_MSG_CHANNEL_REQUEST 98 [SSH-CONNECT]
SSH_MSG_CHANNEL_SUCCESS 99 [SSH-CONNECT] SSH_MSG_CHANNEL_SUCCESS 99 [SSH-CONNECT]
SSH_MSG_CHANNEL_FAILURE 100 [SSH-CONNECT] SSH_MSG_CHANNEL_FAILURE 100 [SSH-CONNECT]
4.1.1 Disconnect Codes 4.1.3 Future Assignments
The Disconnect code is an 8-bit value, which describes the disconnect Requests for assignments of new message numbers in the range of 1 to
reason. Requests for assignments of new disconnect codes must be 127 MUST be done through the STANDARDS ACTION method as described in
accompanied by an RFC which describes the new disconnect reason code. [RFC2434].
Disconnect code Value Reference Requests for assigments of new message numbers in the range of 128 to
---------------- ----- --------- 191 MUST be done through the IETF CONSENSUS method as described in
[RFC2434].
The IANA will not control the message numbers range of 192 through
255. This range will be left for PRIVATE USE.
4.2 Disconnection Messages Reason Codes and Descriptions
The Disconnection Message 'reason code' is a uint32 value. The
associated Disconnection Message 'description string' is a
human-readable message which describes the disconnect reason.
4.2.1 Conventions
Protocol packets containing the SSH_MSG_DISCONNECT message MUST have
Disconnection Message 'reason code' values in the range of 0x00000001
to 0xFFFFFFFF.
4.2.2 Initial Assignments
description string reason Reference
code
------------------ ----- ---------
SSH_DISCONNECT_HOST_NOT_ALLOWED_TO_CONNECT 1 [SSH-TRANS] SSH_DISCONNECT_HOST_NOT_ALLOWED_TO_CONNECT 1 [SSH-TRANS]
SSH_DISCONNECT_PROTOCOL_ERROR 2 [SSH-TRANS] SSH_DISCONNECT_PROTOCOL_ERROR 2 [SSH-TRANS]
SSH_DISCONNECT_KEY_EXCHANGE_FAILED 3 [SSH-TRANS] SSH_DISCONNECT_KEY_EXCHANGE_FAILED 3 [SSH-TRANS]
SSH_DISCONNECT_RESERVED 4 [SSH-TRANS] SSH_DISCONNECT_RESERVED 4 [SSH-TRANS]
SSH_DISCONNECT_MAC_ERROR 5 [SSH-TRANS] SSH_DISCONNECT_MAC_ERROR 5 [SSH-TRANS]
SSH_DISCONNECT_COMPRESSION_ERROR 6 [SSH-TRANS] SSH_DISCONNECT_COMPRESSION_ERROR 6 [SSH-TRANS]
SSH_DISCONNECT_SERVICE_NOT_AVAILABLE 7 [SSH-TRANS] SSH_DISCONNECT_SERVICE_NOT_AVAILABLE 7 [SSH-TRANS]
SSH_DISCONNECT_PROTOCOL_VERSION_NOT_SUPPORTED 8 [SSH-TRANS] SSH_DISCONNECT_PROTOCOL_VERSION_NOT_SUPPORTED 8 [SSH-TRANS]
SSH_DISCONNECT_HOST_KEY_NOT_VERIFIABLE 9 [SSH-TRANS] SSH_DISCONNECT_HOST_KEY_NOT_VERIFIABLE 9 [SSH-TRANS]
SSH_DISCONNECT_CONNECTION_LOST 10 [SSH-TRANS] SSH_DISCONNECT_CONNECTION_LOST 10 [SSH-TRANS]
SSH_DISCONNECT_BY_APPLICATION 11 [SSH-TRANS] SSH_DISCONNECT_BY_APPLICATION 11 [SSH-TRANS]
SSH_DISCONNECT_TOO_MANY_CONNECTIONS 12 [SSH-TRANS] SSH_DISCONNECT_TOO_MANY_CONNECTIONS 12 [SSH-TRANS]
SSH_DISCONNECT_AUTH_CANCELLED_BY_USER 13 [SSH-TRANS] SSH_DISCONNECT_AUTH_CANCELLED_BY_USER 13 [SSH-TRANS]
SSH_DISCONNECT_NO_MORE_AUTH_METHODS_AVAILABLE 14 [SSH-TRANS] SSH_DISCONNECT_NO_MORE_AUTH_METHODS_AVAILABLE 14 [SSH-TRANS]
SSH_DISCONNECT_ILLEGAL_USER_NAME 15 [SSH-TRANS] SSH_DISCONNECT_ILLEGAL_USER_NAME 15 [SSH-TRANS]
4.2 Service Names 4.2.3 Future Assignments
The Service Name is used to describe a protocol layer. These names Disconnection Message 'reason code' values MUST be assigned
MUST be printable US-ASCII strings, and MUST NOT contain the sequentially. Requests for assignments of new Disconnection Message
characters at-sign ('@'), comma (','), or whitespace or control 'reason codes', and their associated Disconnection Message
characters (ASCII codes 32 or less). Names are case-sensitive, and 'description string', in the range of 0x00000010 through 0xFFFFFFE9
MUST NOT be longer than 64 characters. MUST be done through the IETF CONSENSUS method as described in
[RFC2434]. The IANA will not assign Disconnection Message 'reason
codes' in the range of 0xFFFFFFF0 through 0xFFFFFFFF. Disconnection
Message 'reason code' values in that range are left for PRIVATE USE
as described in [RFC2434].
Requests for assignments of new service names must be accompanied by 4.3 Channel Connection Failure Reason Codes and Descriptions
an RFC which describes the interpretation for the service name. If
the RFC is not on the standards-track (i.e. it is an informational The Channel Connection Failure 'reason code' is a uint32 value. The
or experimental RFC), it must be explicitly reviewed and approved by associated Channel Connection Failure 'description string' is a
the IESG before the RFC is published and the service name is human-readable message which describes the channel connection failure
assigned. reason.
4.3.1 Conventions
Protocol packets containing the SSH_MSG_CHANNEL_OPEN_FAILURE message
MUST have Channel Connection Failure 'reason code' values in the
range of 0x00000001 to 0xFFFFFFFF.
4.3.2 Initial Assignments
description string reason Reference
code
------------------ ----- ---------
SSH_OPEN_ADMINISTRATIVELY_PROHIBITED 1 [SSH-CONNECT]
SSH_OPEN_CONNECT_FAILED 2 [SSH-CONNECT]
SSH_OPEN_UNKNOWN_CHANNEL_TYPE 3 [SSH-CONNECT]
SSH_OPEN_RESOURCE_SHORTAGE 4 [SSH-CONNECT]
4.3.3 Future Assignments
Channel Connection Failure 'reason code' values MUST be assigned
sequentially. Requests for assignments of new Channel Connection
Failure 'reason code' values, and their associated Channel Connection
Failure 'description string', in the range of 0x00000005 to
0xFFFFFFE9 MUST be done through the IETF CONSENSUS method as
described in [RFC2434]. The IANA will not assign Channel Connection
Failure 'reason code' values in the range of 0xFFFFFFF0 to
0xFFFFFFFF. Channel Connection Failure 'reason code' values in that
range are left for PRIVATE USE as described in [RFC2434].
4.4 Extended Channel Data Transfer data_type_code and Data
The Extended Channel Data Transfer 'data_type_code' is an uint23
value. The associated Extended Channel Data Transfer 'data' is a
human-readable message which describes the type of data allowed to be
transferred in the channel.
4.4.1 Conventions
Protocol packets containing the SSH_MSG_CHANNEL_EXTENDED_DATA message
MUST have Extended Channel Data Transfer 'data_type_code' values in
the range of 0x00000001 to 0xFFFFFFFF.
4.4.2 Initial Assignments
data data_type_code Reference
---- -------------- ---------
SSH_EXTENDED_DATA_STDERR 1 [SSH-CONNECT]
4.4.3 Future Assignments
Extended Channel Data Transfer 'data_type_code' values MUST be
assigned sequentially. Requests for assignments of new Extended
Channel Data Transfer 'data_type_code' values, and their associated
Extended Channel Data Transfer 'data' strings, in the range of
0x00000002 to 0xFFFFFFE9 MUST be done through the IETF CONSENSUS
method as described in [RFC2434]. The IANA will not assign Extended
Channel Data Transfer 'data_type_code' values in the range of
0xFFFFFFF0 to 0xFFFFFFFF. Extended Channel Data Transfer
'data_type_code' values in that range are left for PRIVATE USE as
described in [RFC2434].
4.5 Pseudo-Terminal Encoded Terminal Modes
SSH_MSG_CHANNEL_REQUEST messages with a "pty-req" string MUST contain
"encoded terminal modes". These "encoded terminal modes" are
opcode-argument pairs consisting of an opcode and an argument.
4.5.1 Conventions
Protocol packets containing the SSH_MSG_CHANNEL_REQUEST message with
a "pty-req" string MUST contain "encoded terminal modes" with an
opcode of 1 byte. The opcode values are in the range of 1 to 255.
Opcodes 1 to 159 have a single uint32 argument. Opcodes 160 to 255
are not yet defined.
4.5.2 Initial Assignments
opcode argument description
------ -------- -----------
0 TTY_OP_END Indicates end of options.
1 VINTR Interrupt character; 255 if none. Similarly
for the other characters. Not all of these
characters are supported on all systems.
2 VQUIT The quit character (sends SIGQUIT signal on
POSIX systems).
3 VERASE Erase the character to left of the cursor.
4 VKILL Kill the current input line.
5 VEOF End-of-file character (sends EOF from the
terminal).
6 VEOL End-of-line character in addition to
carriage return and/or linefeed.
7 VEOL2 Additional end-of-line character.
8 VSTART Continues paused output (normally
control-Q).
9 VSTOP Pauses output (normally control-S).
10 VSUSP Suspends the current program.
11 VDSUSP Another suspend character.
12 VREPRINT Reprints the current input line.
13 VWERASE Erases a word left of cursor.
14 VLNEXT Enter the next character typed literally,
even if it is a special character
15 VFLUSH Character to flush output.
16 VSWTCH Switch to a different shell layer.
17 VSTATUS Prints system status line (load, command,
pid, etc).
18 VDISCARD Toggles the flushing of terminal output.
30 IGNPAR The ignore parity flag. The parameter
SHOULD be 0 if this flag is FALSE set,
and 1 if it is TRUE.
31 PARMRK Mark parity and framing errors.
32 INPCK Enable checking of parity errors.
33 ISTRIP Strip 8th bit off characters.
34 INLCR Map NL into CR on input.
35 IGNCR Ignore CR on input.
36 ICRNL Map CR to NL on input.
37 IUCLC Translate uppercase characters to
lowercase.
38 IXON Enable output flow control.
39 IXANY Any char will restart after stop.
40 IXOFF Enable input flow control.
41 IMAXBEL Ring bell on input queue full.
50 ISIG Enable signals INTR, QUIT, [D]SUSP.
51 ICANON Canonicalize input lines.
52 XCASE Enable input and output of uppercase
characters by preceding their lowercase
equivalents with "\".
53 ECHO Enable echoing.
54 ECHOE Visually erase chars.
55 ECHOK Kill character discards current line.
56 ECHONL Echo NL even if ECHO is off.
57 NOFLSH Don't flush after interrupt.
58 TOSTOP Stop background jobs from output.
59 IEXTEN Enable extensions.
60 ECHOCTL Echo control characters as ^(Char).
61 ECHOKE Visual erase for line kill.
62 PENDIN Retype pending input.
70 OPOST Enable output processing.
71 OLCUC Convert lowercase to uppercase.
72 ONLCR Map NL to CR-NL.
73 OCRNL Translate carriage return to newline
(output).
74 ONOCR Translate newline to carriage
return-newline (output).
75 ONLRET Newline performs a carriage return
(output).
90 CS7 7 bit mode.
91 CS8 8 bit mode.
92 PARENB Parity enable.
93 PARODD Odd parity, else even.
128 TTY_OP_ISPEED Specifies the input baud rate in
bits per second.
129 TTY_OP_OSPEED Specifies the output baud rate in
bits per second.
4.5.3 Future Assignments
Requests for assignments of new opcodes and their associated
arguments MUST be done through the IETF CONSENSUS method as described
in [RFC2434].
4.6 Names
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.
4.6.1 Conventions for Names
All names registered by the IANA in the following sections MUST be
printable US-ASCII strings, and MUST NOT contain the characters
at-sign ("@"), comma (","), or whitespace or control characters
(ASCII codes 32 or less). Names are case-sensitive, 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. Names with the at-sign in them will have the format of
"name@domainname" (without the double quotes) where the part
preceeding the at-sign is the name. The format of the part preceding
the at sign is not specified, however these names MUST be printable
US-ASCII strings, and MUST NOT contain the comma character (","), or
whitespace, or control characters (ASCII codes 32 or less). The part
following the at-sign MUST be a valid, fully qualified internet
domain name [RFC1034] controlled by the person or organization
defining the name. Names are case-sensitive, and MUST NOT be longer
than 64 characters. It is up to each domain how it manages its local
namespace. It has been noted that these names resemble [RFC0822]
email addresses. This is purely coincidental and actually has
nothing to do with [RFC0822]. An example of a locally defined name
is "ourcipher-cbc@example.com" (without the double quotes).
4.6.2 Future Assignments of Names
Requests for assignments of new Names MUST be done through the IETF
CONSENSUS method as described in [RFC2434].
4.7 Service Names
The Service Name is used to describe a protocol layer.
Service name Reference Service name Reference
------------- --------- ------------- ---------
ssh-userauth [SSH-USERAUTH] ssh-userauth [SSH-USERAUTH]
ssh-connection [SSH-CONNECT] ssh-connection [SSH-CONNECT]
4.2.1 Authentication Method Names 4.8 Authentication Method Names
The Authentication Method Name is used to describe an authentication The Authentication Method Name is used to describe an authentication
method for the "ssh-userauth" service [SSH-USERAUTH]. These names method for the "ssh-userauth" service [SSH-USERAUTH].
MUST be printable US-ASCII strings, and MUST NOT contain the
characters at-sign ('@'), comma (','), or whitespace or control
characters (ASCII codes 32 or less). Names are case-sensitive, and
MUST NOT be longer than 64 characters.
Requests for assignments of new authentication method names must be
accompanied by an RFC which describes the interpretation for the
authentication method.
Method name Reference Method name Reference
------------ --------- ------------ ---------
publickey [SSH-USERAUTH, Section 4] publickey [SSH-USERAUTH, Section 4]
password [SSH-USERAUTH, Section 5] password [SSH-USERAUTH, Section 5]
hostbased [SSH-USERAUTH, Section 6] hostbased [SSH-USERAUTH, Section 6]
none [SSH-USERAUTH, Section 2.3] none [SSH-USERAUTH, Section 2.3]
4.2.2 Connection Protocol Assigned Names 4.9 Connection Protocol Assigned Names
The following request and type names MUST be printable US-ASCII
strings, and MUST NOT contain the characters at-sign ('@'), comma
(','), or whitespace or control characters (ASCII codes 32 or less).
Names are case-sensitive, and MUST NOT be longer than 64 characters.
Requests for assignments of new assigned names must be accompanied by The following are the Connection Protocol Type and Request names.
an RFC which describes the interpretation for the type or request.
4.2.2.1 Connection Protocol Channel Types 4.9.1 Connection Protocol Channel Types
Channel type Reference Channel type Reference
------------ --------- ------------ ---------
session [SSH-CONNECT, Section 4.1] session [SSH-CONNECT, Section 4.1]
x11 [SSH-CONNECT, Section 4.3.2] x11 [SSH-CONNECT, Section 4.3.2]
forwarded-tcpip [SSH-CONNECT, Section 5.2] forwarded-tcpip [SSH-CONNECT, Section 5.2]
direct-tcpip [SSH-CONNECT, Section 5.2] direct-tcpip [SSH-CONNECT, Section 5.2]
4.2.2.2 Connection Protocol Global Request Names 4.9.2 Connection Protocol Global Request Names
Request type Reference Request type Reference
------------ --------- ------------ ---------
tcpip-forward [SSH-CONNECT, Section 5.1] tcpip-forward [SSH-CONNECT, Section 5.1]
cancel-tcpip-forward [SSH-CONNECT, Section 5.1] cancel-tcpip-forward [SSH-CONNECT, Section 5.1]
4.2.2.3 Connection Protocol Channel Request Names 4.9.3 Connection Protocol Channel Request Names
Request type Reference Request type Reference
------------ --------- ------------ ---------
pty-req [SSH-CONNECT, Section 4.2] pty-req [SSH-CONNECT, Section 4.2]
x11-req [SSH-CONNECT, Section 4.3.1] x11-req [SSH-CONNECT, Section 4.3.1]
env [SSH-CONNECT, Section 4.4] env [SSH-CONNECT, Section 4.4]
shell [SSH-CONNECT, Section 4.5] shell [SSH-CONNECT, Section 4.5]
exec [SSH-CONNECT, Section 4.5] exec [SSH-CONNECT, Section 4.5]
subsystem [SSH-CONNECT, Section 4.5] subsystem [SSH-CONNECT, Section 4.5]
window-change [SSH-CONNECT, Section 4.7] window-change [SSH-CONNECT, Section 4.7]
xon-xoff [SSH-CONNECT, Section 4.8] xon-xoff [SSH-CONNECT, Section 4.8]
signal [SSH-CONNECT, Section 4.9] signal [SSH-CONNECT, Section 4.9]
exit-status [SSH-CONNECT, Section 4.10] exit-status [SSH-CONNECT, Section 4.10]
exit-signal [SSH-CONNECT, Section 4.10] exit-signal [SSH-CONNECT, Section 4.10]
4.3 Key Exchange Method Names 4.9.4 Initial Assignment of Signal Names
Signal Reference
------ ---------
ABRT [SSH-CONNECT]
ALRM [SSH-CONNECT]
FPE [SSH-CONNECT]
HUP [SSH-CONNECT]
ILL [SSH-CONNECT]
INT [SSH-CONNECT]
KILL [SSH-CONNECT]
PIPE [SSH-CONNECT]
QUIT [SSH-CONNECT]
SEGV [SSH-CONNECT]
TERM [SSH-CONNECT]
USR1 [SSH-CONNECT]
USR2 [SSH-CONNECT]
4.10 Key Exchange Method Names
The Key Exchange Method Name describes a key-exchange method for the The Key Exchange Method Name describes a key-exchange method for the
protocol [SSH-TRANS]. The names MUST be printable US-ASCII strings, protocol [SSH-TRANS]. Note that, for historical reasons, the name
and MUST NOT contain the characters at-sign ('@'), comma (','), or "diffie-hellman-group1-sha1" is used for a key exchange method using
whitespace or control characters (ASCII codes 32 or less). Names are Oakley Group 2. This is considered an aberration and should not be
case-sensitive, and MUST NOT be longer than 64 characters. repeated. Any future specifications of Diffie Hellman key exchange
using Oakley groups defined in [RFC2412] or its successors should be
named using the group numbers assigned by IANA, and names of the form
"diffie-hellman-groupN-sha1" should be reserved for this purpose.
Requests for assignment of new key-exchange method names must be Editor's Note: diffie-hellman-group14-sha1 is controversial at the
accompanied by a reference to a standards-track or Informational RFC moment. It is being discussed on the mailing list.
which describes this method.
Method name Reference Method name Reference
------------ --------- ------------ ---------
diffie-hellman-group1-sha1 [SSH-TRANS, Section 4.5] diffie-hellman-group1-sha1 [SSH-TRANS, Section 8.1]
diffie-hellman-group14-sha1 [SSH-TRANS, Section 8.2]
4.4 Assigned Algorithm Names
The following identifiers (names) MUST be printable US-ASCII strings, 4.11 Assigned Algorithm Names
and MUST NOT contain the characters at-sign ('@'), comma (','), or
whitespace or control characters (ASCII codes 32 or less). Names are
case-sensitive, and MUST NOT be longer than 64 characters.
Requests for assignment of new algorithm names must be accompanied by The following names identify the Encryption Algorithm Names.
a reference to a standards-track or Informational RFC or a reference
to published cryptographic literature which describes the algorithm.
4.4.1 Encryption Algorithm Names 4.11.1 Encryption Algorithm Names
Cipher name Reference Cipher name Reference
------------ --------- ------------ ---------
3des-cbc [SSH-TRANS, Section 4.3] 3des-cbc [SSH-TRANS, Section 4.3]
blowfish-cbc [SSH-TRANS, Section 4.3] blowfish-cbc [SSH-TRANS, Section 4.3]
twofish256-cbc [SSH-TRANS, Section 4.3] twofish256-cbc [SSH-TRANS, Section 4.3]
twofish-cbc [SSH-TRANS, Section 4.3] twofish-cbc [SSH-TRANS, Section 4.3]
twofish192-cbc [SSH-TRANS, Section 4.3] twofish192-cbc [SSH-TRANS, Section 4.3]
twofish128-cbc [SSH-TRANS, Section 4.3] twofish128-cbc [SSH-TRANS, Section 4.3]
aes256-cbc [SSH-TRANS, Section 4.3] aes256-cbc [SSH-TRANS, Section 4.3]
aes192-cbc [SSH-TRANS, Section 4.3] aes192-cbc [SSH-TRANS, Section 4.3]
aes128-cbc [SSH-TRANS, Section 4.3] aes128-cbc [SSH-TRANS, Section 4.3]
serpent256-cbc [SSH-TRANS, Section 4.3] serpent256-cbc [SSH-TRANS, Section 4.3]
serpent192-cbc [SSH-TRANS, Section 4.3] serpent192-cbc [SSH-TRANS, Section 4.3]
serpent128-cbc [SSH-TRANS, Section 4.3] serpent128-cbc [SSH-TRANS, Section 4.3]
arcfour [SSH-TRANS, Section 4.3] arcfour [SSH-TRANS, Section 4.3]
idea-cbc [SSH-TRANS, Section 4.3] idea-cbc [SSH-TRANS, Section 4.3]
cast128-cbc [SSH-TRANS, Section 4.3] cast128-cbc [SSH-TRANS, Section 4.3]
none [SSH-TRANS, Section 4.3] none [SSH-TRANS, Section 4.3]
des-cbc [FIPS-46-3] HISTORIC; See page 4 of [FIPS 46-3] of [FIPS 46-3]
4.4.2 MAC Algorithm Names 4.11.2 MAC Algorithm Names
The following names identify the MAC Algorithm Names.
MAC name Reference MAC name Reference
--------- --------- --------- ---------
hmac-sha1 [SSH-TRANS, Section 4.4] hmac-sha1 [SSH-TRANS, Section 4.4]
hmac-sha1-96 [SSH-TRANS, Section 4.4] hmac-sha1-96 [SSH-TRANS, Section 4.4]
hmac-md5 [SSH-TRANS, Section 4.4] hmac-md5 [SSH-TRANS, Section 4.4]
hmac-md5-96 [SSH-TRANS, Section 4.4] hmac-md5-96 [SSH-TRANS, Section 4.4]
none [SSH-TRANS, Section 4.4] none [SSH-TRANS, Section 4.4]
4.4.3 Public Key Algorithm Names 4.11.3 Public Key Algorithm Names
This table identifies the Public Key Algorithm names.
Algorithm name Reference Algorithm name Reference
--------------- --------- --------------- ---------
ssh-dss [SSH-TRANS, Section 4.6] ssh-dss [SSH-TRANS, Section 4.6]
ssh-rsa [SSH-TRANS, Section 4.6] ssh-rsa [SSH-TRANS, Section 4.6]
x509v3-sign-rsa [SSH-TRANS, Section 4.6] x509v3-sign-rsa [SSH-TRANS, Section 4.6]
x509v3-sign-dss [SSH-TRANS, Section 4.6] x509v3-sign-dss [SSH-TRANS, Section 4.6]
spki-sign-rsa [SSH-TRANS, Section 4.6] spki-sign-rsa [SSH-TRANS, Section 4.6]
spki-sign-dss [SSH-TRANS, Section 4.6] spki-sign-dss [SSH-TRANS, Section 4.6]
pgp-sign-rsa [SSH-TRANS, Section 4.6] pgp-sign-rsa [SSH-TRANS, Section 4.6]
pgp-sign-dss [SSH-TRANS, Section 4.6] pgp-sign-dss [SSH-TRANS, Section 4.6]
4.4.4 Compression Algorithm Names 4.11.4 Compression Algorithm Names
The following names identify the Compression Algorithm names.
Algorithm name Reference Algorithm name Reference
--------------- --------- --------------- ---------
none [SSH-TRANS, Section 4.2] none [SSH-TRANS, Section 4.2]
zlib [SSH-TRANS, Section 4.2] zlib [SSH-TRANS, Section 4.2]
5. Intellectual Property 5. References
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such
proprietary rights by implementers or users of this specification can
be obtained from the IETF Secretariat.
The IETF has been notified of intellectual property rights claimed in
regard to some or all of the specification contained in this
document. For more information consult the online list of claimed
rights.
6. References
6.1 Normative References 5.1 Normative References
[SSH-ARCH] [SSH-ARCH]
Ylonen, T. and C. Lonvick, "SSH Protocol Architecture", Ylonen, T. and C. Lonvick, "SSH Protocol Architecture",
I-D draft-ietf-architecture-16.txt, May 2004. I-D draft-ietf-architecture-17.txt, October 2004.
[SSH-TRANS] [SSH-TRANS]
Ylonen, T. and C. Lonvick, "SSH Transport Layer Protocol", Ylonen, T. and C. Lonvick, "SSH Transport Layer Protocol",
I-D draft-ietf-transport-18.txt, May 2004. I-D draft-ietf-transport-19.txt, October 2004.
[SSH-USERAUTH] [SSH-USERAUTH]
Ylonen, T. and C. Lonvick, "SSH Authentication Protocol", Ylonen, T. and C. Lonvick, "SSH Authentication Protocol",
I-D draft-ietf-userauth-21.txt, May 2004. I-D draft-ietf-userauth-22.txt, October 2004.
[SSH-CONNECT] [SSH-CONNECT]
Ylonen, T. and C. Lonvick, "SSH Connection Protocol", I-D Ylonen, T. and C. Lonvick, "SSH Connection Protocol", I-D
draft-ietf-connect-19.txt, May 2004. draft-ietf-connect-20.txt, October 2004.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
6.2 Informative References [RFC2412] Orman, H., "The OAKLEY Key Determination Protocol", RFC
2412, November 1998.
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 2434,
October 1998.
5.2 Informative References
[RFC0822] Crocker, D., "Standard for the format of ARPA Internet
text messages", STD 11, RFC 822, August 1982.
[RFC1034] Mockapetris, P., "Domain names - concepts and facilities",
STD 13, RFC 1034, November 1987.
[FIPS-46-3] [FIPS-46-3]
U.S. Dept. of Commerce, "FIPS PUB 46-3, Data Encryption U.S. Dept. of Commerce, "FIPS PUB 46-3, Data Encryption
Standard (DES)", October 1999. Standard (DES)", October 1999.
Authors' Addresses Author's Address
Sami Lehtinen
SSH Communications Security Corp
Fredrikinkatu 42
HELSINKI FIN-00100
Finland
EMail: sjl@ssh.com
Chris Lonvick (editor) Chris Lonvick (editor)
Cisco Systems, Inc. Cisco Systems, Inc
12515 Research Blvd. 12515 Research Blvd.
Austin 78759 Austin 78759
USA USA
EMail: clonvick@cisco.com EMail: clonvick@cisco.com
Intellectual Property Statement Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it might or might not be available; nor does it represent that it has
has made any effort to identify any such rights. Information on the made any independent effort to identify any such rights. Information
IETF's procedures with respect to rights in standards-track and on the procedures with respect to rights in RFC documents can be
standards-related documentation can be found in BCP-11. Copies of found in BCP 78 and BCP 79.
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to Copies of IPR disclosures made to the IETF Secretariat and any
obtain a general license or permission for the use of such assurances of licenses to be made available, or the result of an
proprietary rights by implementors or users of this specification can attempt made to obtain a general license or permission for the use of
be obtained from the IETF Secretariat. such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF at
Director. ietf-ipr@ietf.org.
The IETF has been notified of intellectual property rights claimed in The IETF has been notified of intellectual property rights claimed in
regard to some or all of the specification contained in this regard to some or all of the specification contained in this
document. For more information consult the online list of claimed document. For more information consult the online list of claimed
rights. rights.
Full Copyright Statement Disclaimer of Validity
Copyright (C) The Internet Society (2004). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and the information contained herein are provided on an
others, and derivative works that comment on or otherwise explain it "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
or assist in its implementation may be prepared, copied, published OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
and distributed, in whole or in part, without restriction of any ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
kind, provided that the above copyright notice and this paragraph are INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
included on all such copies and derivative works. However, this INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
document itself may not be modified in any way, such as by removing WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be Copyright Statement
revoked by the Internet Society or its successors or assignees.
This document and the information contained herein is provided on an Copyright (C) The Internet Society (2004). This document is subject
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING to the rights, licenses and restrictions contained in BCP 78, and
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING except as set forth therein, the authors retain all their rights.
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/