draft-ietf-secsh-assignednumbers-05.txt   draft-ietf-secsh-assignednumbers-06.txt 
Network Working Group S. Lehtinen Network Working Group S. Lehtinen
Internet-Draft SSH Communications Security Corp Internet-Draft SSH Communications Security Corp
Expires: March 31, 2004 D. Moffat, Ed. Expires: December 1, 2004 C. Lonvick, Ed.
Sun Microsystems Cisco Systems, Inc.
Oct 2003 June 2, 2004
SSH Protocol Assigned Numbers SSH Protocol Assigned Numbers
draft-ietf-secsh-assignednumbers-05.txt draft-ietf-secsh-assignednumbers-06.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 in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
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 other Task Force (IETF), its areas, and its working groups. Note that
groups may also distribute working documents as Internet-Drafts. other groups may also distribute working documents as
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 http:// The list of current Internet-Drafts can be accessed at
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 March 31, 2004. This Internet-Draft will expire on December 1, 2004.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
Abstract Abstract
This document defines the initial state of the IANA assigned numbers This document defines the initial state of the IANA assigned numbers
for the SSH protocol. It is intended only for initalization of the for the SSH protocol. It is intended only for initialization of the
IANA databases referenced in those documents. IANA databases referenced in those documents.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Editor's Note . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions Used in This Document . . . . . . . . . . . . . 3 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . 3 3. Conventions Used in This Document . . . . . . . . . . . . . . 3
3.1 Message Numbers . . . . . . . . . . . . . . . . . . . . . . 3 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
3.1.1 Disconnect Codes . . . . . . . . . . . . . . . . . . . . . . 5 4.1 Message Numbers . . . . . . . . . . . . . . . . . . . . . 3
3.2 Service Names . . . . . . . . . . . . . . . . . . . . . . . 5 4.1.1 Disconnect Codes . . . . . . . . . . . . . . . . . . . 5
3.2.1 Authentication Method Names . . . . . . . . . . . . . . . . 6 4.2 Service Names . . . . . . . . . . . . . . . . . . . . . . 5
3.2.2 Connection Protocol Assigned Names . . . . . . . . . . . . . 6 4.2.1 Authentication Method Names . . . . . . . . . . . . . 6
3.3 Key Exchange Method Names . . . . . . . . . . . . . . . . . 7 4.2.2 Connection Protocol Assigned Names . . . . . . . . . . 6
3.4 Assigned Algorithm Names . . . . . . . . . . . . . . . . . . 7 4.3 Key Exchange Method Names . . . . . . . . . . . . . . . . 7
3.4.1 Encryption Algorithm Names . . . . . . . . . . . . . . . . . 7 4.4 Assigned Algorithm Names . . . . . . . . . . . . . . . . . 7
3.4.2 MAC Algorithm Names . . . . . . . . . . . . . . . . . . . . 8 4.4.1 Encryption Algorithm Names . . . . . . . . . . . . . . 8
3.4.3 Public Key Algorithm Names . . . . . . . . . . . . . . . . . 8 4.4.2 MAC Algorithm Names . . . . . . . . . . . . . . . . . 8
3.4.4 Compression Algorithm Names . . . . . . . . . . . . . . . . 9 4.4.3 Public Key Algorithm Names . . . . . . . . . . . . . . 8
4. Intellectual Property . . . . . . . . . . . . . . . . . . . 9 4.4.4 Compression Algorithm Names . . . . . . . . . . . . . 9
Normative References . . . . . . . . . . . . . . . . . . . . 9 5. Intellectual Property . . . . . . . . . . . . . . . . . . . . 9
Informative References . . . . . . . . . . . . . . . . . . . 10 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 10 6.1 Normative References . . . . . . . . . . . . . . . . . . . . 9
Intellectual Property and Copyright Statements . . . . . . . 11 6.2 Informative References . . . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 10
Intellectual Property and Copyright Statements . . . . . . . . 11
1. Introduction 1. Editor's Note
The references in this document are statically defined. However, the
locations of the referenced materials are dynamic and are changing
with the whims of the Working Group. Please do not comment to the
editor or the Working Group about inaccuracies along those lines in
this document at this time. (This paragraph will be removed before
this document is submitted to the RFC Editor.)
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. Except for one HISTORIC algorithm generally regarded as
obsolete, this document does not define any new protocols or any obsolete, this document does not define any new protocols or any
number ranges not already defined in: [SSH-ARCH], [SSH-TRANS], number ranges not already defined in: [SSH-ARCH], [SSH-TRANS],
[SSH-USERAUTH], [SSH-CONNECT] [SSH-USERAUTH], [SSH-CONNECT]
2. 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 used data types and terminology are specified in the architecture
document [SSH-ARCH] document [SSH-ARCH]
The architecture document also discusses the algorithm naming The architecture document also discusses the algorithm naming
conventions that MUST be used with the SSH protocols. conventions that MUST be used with the SSH protocols.
3. IANA Considerations 4. IANA Considerations
3.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.
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 have been allocated as follows in [SSH-ARCH]:
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.)
skipping to change at page 5, line 5 skipping to change at page 5, line 12
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]
3.1.1 Disconnect Codes 4.1.1 Disconnect Codes
The Disconnect code is an 8-bit value, which describes the disconnect The Disconnect code is an 8-bit value, which describes the disconnect
reason. Requests for assignments of new disconnect codes must be reason. Requests for assignments of new disconnect codes must be
accompanied by an RFC which describes the new disconnect reason code. accompanied by an RFC which describes the new disconnect reason code.
Disconnect code Value Reference Disconnect code Value Reference
---------------- ----- --------- ---------------- ----- ---------
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]
skipping to change at page 5, line 29 skipping to change at page 5, line 36
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]
3.2 Service Names 4.2 Service Names
The Service Name is used to describe a protocol layer. These names The Service Name is used to describe a protocol layer. These names
MUST be printable US-ASCII strings, and MUST NOT contain the MUST be printable US-ASCII strings, and MUST NOT contain the
characters at-sign ('@'), comma (','), or whitespace or control characters at-sign ('@'), comma (','), or whitespace or control
characters (ASCII codes 32 or less). Names are case-sensitive, and characters (ASCII codes 32 or less). Names are case-sensitive, and
MUST NOT be longer than 64 characters. MUST NOT be longer than 64 characters.
Requests for assignments of new service names must be accompanied by Requests for assignments of new service names must be accompanied by
an RFC which describes the interpretation for the service name. If 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 or the RFC is not on the standards-track (i.e. it is an informational
experimental RFC), it must be explicitly reviewed and approved by the or experimental RFC), it must be explicitly reviewed and approved by
IESG before the RFC is published and the service name is assigned. the IESG before the RFC is published and the service name is
assigned.
Service name Reference Service name Reference
------------- --------- ------------- ---------
ssh-userauth [SSH-USERAUTH] ssh-userauth [SSH-USERAUTH]
ssh-connection [SSH-CONNECT] ssh-connection [SSH-CONNECT]
3.2.1 Authentication Method Names 4.2.1 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]. These names
MUST be printable US-ASCII strings, and MUST NOT contain the MUST be printable US-ASCII strings, and MUST NOT contain the
characters at-sign ('@'), comma (','), or whitespace or control characters at-sign ('@'), comma (','), or whitespace or control
characters (ASCII codes 32 or less). Names are case-sensitive, and characters (ASCII codes 32 or less). Names are case-sensitive, and
MUST NOT be longer than 64 characters. MUST NOT be longer than 64 characters.
Requests for assignments of new authentication method names must be Requests for assignments of new authentication method names must be
accompanied by an RFC which describes the interpretation for the accompanied by an RFC which describes the interpretation for the
authentication method. 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]
3.2.2 Connection Protocol Assigned Names 4.2.2 Connection Protocol Assigned Names
The following request and type names MUST be printable US-ASCII The following request and type names MUST be printable US-ASCII
strings, and MUST NOT contain the characters at-sign ('@'), comma strings, and MUST NOT contain the characters at-sign ('@'), comma
(','), or whitespace or control characters (ASCII codes 32 or less). (','), or whitespace or control characters (ASCII codes 32 or less).
Names are case-sensitive, and MUST NOT be longer than 64 characters. Names are case-sensitive, and MUST NOT be longer than 64 characters.
Requests for assignments of new assigned names must be accompanied by Requests for assignments of new assigned names must be accompanied by
an RFC which describes the interpretation for the type or request. an RFC which describes the interpretation for the type or request.
3.2.2.1 Connection Protocol Channel Types 4.2.2.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]
3.2.2.2 Connection Protocol Global Request Names 4.2.2.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]
3.2.2.3 Connection Protocol Channel Request Names 4.2.2.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]
3.3 Key Exchange Method Names 4.3 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]. The names MUST be printable US-ASCII strings,
and MUST NOT contain the characters at-sign ('@'), comma (','), or and MUST NOT contain the characters at-sign ('@'), comma (','), or
whitespace or control characters (ASCII codes 32 or less). Names are whitespace or control characters (ASCII codes 32 or less). Names are
case-sensitive, and MUST NOT be longer than 64 characters. case-sensitive, and MUST NOT be longer than 64 characters.
Requests for assignment of new key-exchange method names must be Requests for assignment of new key-exchange method names must be
accompanied by a reference to a standards-track or Informational RFC accompanied by a reference to a standards-track or Informational RFC
which describes this method. 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 4.5]
3.4 Assigned Algorithm Names 4.4 Assigned Algorithm Names
The following identifiers (names) MUST be printable US-ASCII strings, The following identifiers (names) MUST be printable US-ASCII strings,
and MUST NOT contain the characters at-sign ('@'), comma (','), or and MUST NOT contain the characters at-sign ('@'), comma (','), or
whitespace or control characters (ASCII codes 32 or less). Names are whitespace or control characters (ASCII codes 32 or less). Names are
case-sensitive, and MUST NOT be longer than 64 characters. case-sensitive, and MUST NOT be longer than 64 characters.
Requests for assignment of new algorithm names must be accompanied by Requests for assignment of new algorithm names must be accompanied by
a reference to a standards-track or Informational RFC or a reference a reference to a standards-track or Informational RFC or a reference
to published cryptographic literature which describes the algorithm. to published cryptographic literature which describes the algorithm.
3.4.1 Encryption Algorithm Names 4.4.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]
skipping to change at page 8, line 23 skipping to change at page 8, line 31
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] des-cbc [FIPS-46-3] HISTORIC; See page 4 of [FIPS 46-3]
3.4.2 MAC Algorithm Names 4.4.2 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]
3.4.3 Public Key Algorithm Names 4.4.3 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]
3.4.4 Compression Algorithm Names 4.4.4 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]
4. Intellectual Property 5. Intellectual Property
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 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; neither does it represent that it
has made any effort to identify any such rights. Information on the has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances 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 licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such obtain a general license or permission for the use of such
proprietary rights by implementers or users of this specification can proprietary rights by implementers or users of this specification can
be obtained from the IETF Secretariat. be obtained from the IETF Secretariat.
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.
Normative References 6. References
6.1 Normative References
[SSH-ARCH] [SSH-ARCH]
Ylonen, T., "SSH Protocol Architecture", I-D Ylonen, T. and C. Lonvick, "SSH Protocol Architecture",
draft-ietf-architecture-15.txt, Oct 2003. I-D draft-ietf-architecture-16.txt, May 2004.
[SSH-TRANS] [SSH-TRANS]
Ylonen, T., "SSH Transport Layer Protocol", I-D Ylonen, T. and C. Lonvick, "SSH Transport Layer Protocol",
draft-ietf-transport-17.txt, Oct 2003. I-D draft-ietf-transport-18.txt, May 2004.
[SSH-USERAUTH] [SSH-USERAUTH]
Ylonen, T., "SSH Authentication Protocol", I-D Ylonen, T. and C. Lonvick, "SSH Authentication Protocol",
draft-ietf-userauth-18.txt, Oct 2003. I-D draft-ietf-userauth-21.txt, May 2004.
[SSH-CONNECT] [SSH-CONNECT]
Ylonen, T., "SSH Connection Protocol", I-D Ylonen, T. and C. Lonvick, "SSH Connection Protocol", I-D
draft-ietf-connect-18.txt, Oct 2003. draft-ietf-connect-19.txt, May 2004.
[SSH-NUMBERS]
Lehtinen, S. and D. Moffat, "SSH Protocol Assigned
Numbers", I-D draft-ietf-secsh-assignednumbers-05.txt, Oct
2003.
[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.
Informative References 6.2 Informative References
[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 Authors' Addresses
Sami Lehtinen Sami Lehtinen
SSH Communications Security Corp SSH Communications Security Corp
Fredrikinkatu 42 Fredrikinkatu 42
HELSINKI FIN-00100 HELSINKI FIN-00100
Finland Finland
EMail: sjl@ssh.com EMail: sjl@ssh.com
Darren J Moffat (editor) Chris Lonvick (editor)
Sun Microsystems Cisco Systems, Inc.
901 San Antonio Road 12515 Research Blvd.
Palo Alto 94303 Austin 78759
USA USA
EMail: Darren.Moffat@Sun.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 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; neither does it represent that it
has made any effort to identify any such rights. Information on the has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and IETF's procedures with respect to rights in standards-track and
skipping to change at page 11, line 34 skipping to change at page 11, line 34
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF Executive
Director. Director.
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 Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
 End of changes. 

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