draft-ietf-secsh-assignednumbers-01.txt   draft-ietf-secsh-assignednumbers-02.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, 2003 D. Moffat Expires: January 12, 2004 D. Moffat
Sun Microsystems Sun Microsystems
September 30, 2002 July 14, 2003
SSH Protocol Assigned Numbers SSH Protocol Assigned Numbers
draft-ietf-secsh-assignednumbers-01.txt draft-ietf-secsh-assignednumbers-02.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 Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six
and may be updated, replaced, or obsoleted by other documents at any months and may be updated, replaced, or obsoleted by other
time. It is inappropriate to use Internet-Drafts as reference documents at any time. It is inappropriate to use Internet-Drafts
material or to cite them other than as "work in progress." as reference 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 March 31, 2003. This Internet-Draft will expire on January 12, 2004.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2002). All Rights Reserved. Copyright (C) The Internet Society (2003). 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
for the SSH protocol as defined in [SSH-ARCH], [SSH-TRANS], [SSH- numbers for the SSH protocol as defined in [SSH-ARCH], [SSH-
CONNECT], [SSH-USERAUTH]. This document does not define any new TRANS], [SSH-CONNECT], [SSH-USERAUTH]. This document does not
protocols or any number ranges not already defined in the above define any new protocols or any number ranges not already defined
referenced documents. It is intended only for initalization of the in the above referenced documents. It is intended only for
IANA databases referenced in those documents. initalization of the IANA databases referenced in those documents.
Table of Contents Table of Contents
1. Message Numbers . . . . . . . . . . . . . . . . . . . . . . 3 1. Message Numbers . . . . . . . . . . . . . . . . . . . . . . 3
1.1 Disconnect Codes . . . . . . . . . . . . . . . . . . . . . . 4 1.1 Disconnect Codes . . . . . . . . . . . . . . . . . . . . . . 4
2. Service Names . . . . . . . . . . . . . . . . . . . . . . . 5 2. Service Names . . . . . . . . . . . . . . . . . . . . . . . 5
2.1 Authentication Method Names . . . . . . . . . . . . . . . . 5 2.1 Authentication Method Names . . . . . . . . . . . . . . . . 5
2.2 Connection Protocol Assigned Names . . . . . . . . . . . . . 6 2.2 Connection Protocol Assigned Names . . . . . . . . . . . . . 6
2.2.1 Connection Protocol Channel Types . . . . . . . . . . . . . 6 2.2.1 Connection Protocol Channel Types . . . . . . . . . . . . . 6
2.2.2 Connection Protocol Global Request Names . . . . . . . . . . 6 2.2.2 Connection Protocol Global Request Names . . . . . . . . . . 6
skipping to change at page 3, line 4 skipping to change at page 3, line 4
2.2.2 Connection Protocol Global Request Names . . . . . . . . . . 6 2.2.2 Connection Protocol Global Request Names . . . . . . . . . . 6
2.2.3 Connection Protocol Channel Request Names . . . . . . . . . 6 2.2.3 Connection Protocol Channel Request Names . . . . . . . . . 6
3. Key Exchange Method Names . . . . . . . . . . . . . . . . . 7 3. Key Exchange Method Names . . . . . . . . . . . . . . . . . 7
4. Assigned Algorithm Names . . . . . . . . . . . . . . . . . . 7 4. Assigned Algorithm Names . . . . . . . . . . . . . . . . . . 7
4.1 Encryption Algorithm Names . . . . . . . . . . . . . . . . . 7 4.1 Encryption Algorithm Names . . . . . . . . . . . . . . . . . 7
4.2 MAC Algorithm Names . . . . . . . . . . . . . . . . . . . . 8 4.2 MAC Algorithm Names . . . . . . . . . . . . . . . . . . . . 8
4.3 Public Key Algorithm Names . . . . . . . . . . . . . . . . . 8 4.3 Public Key Algorithm Names . . . . . . . . . . . . . . . . . 8
References . . . . . . . . . . . . . . . . . . . . . . . . . 8 References . . . . . . . . . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 9 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 9
Full Copyright Statement . . . . . . . . . . . . . . . . . . 10 Full Copyright Statement . . . . . . . . . . . . . . . . . . 10
1. Message Numbers 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
a packet. of 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.
numbers have been allocated as follows in [SSH-ARCH]: These 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.)
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 for
different authentication methods) different authentication methods)
User authentication protocol: User authentication protocol:
skipping to change at page 3, line 39 skipping to change at page 3, line 38
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 Requests for assignments of new message numbers must be
by an RFC which describes the new packet type. If the RFC is not on accompanied by an RFC which describes the new packet type. If the
the standards-track (i.e. it is an informational or experimental RFC is not on the standards-track (i.e. it is an informational or
RFC), it must be explicitly reviewed and approved by the IESG before experimental RFC), it must be explicitly reviewed and approved by
the RFC is published and the message number is assigned. 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 4, line 31 skipping to change at page 4, line 32
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]
1.1 Disconnect Codes 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
reason. Requests for assignments of new disconnect codes must be disconnect reason. Requests for assignments of new disconnect
accompanied by an RFC which describes the new disconnect reason code. codes must be 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]
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]
skipping to change at page 5, line 9 skipping to change at page 5, line 11
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]
2. Service Names 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
MUST be printable US-ASCII strings, and MUST NOT contain the names 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,
MUST NOT be longer than 64 characters. and 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
an RFC which describes the interpretation for the service name. If by an RFC which describes the interpretation for the service name.
the RFC is not on the standards-track (i.e. it is an informational If the RFC is not on the standards-track (i.e. it is an
or experimental RFC), it must be explicitly reviewed and approved by informational or experimental RFC), it must be explicitly reviewed
the IESG before the RFC is published and the service name is and approved by the IESG before the RFC is published and the
assigned. 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]
2.1 Authentication Method Names 2.1 Authentication Method Names
The Authentication Method Name is used to describe an authentication The Authentication Method Name is used to describe an
method for the "ssh-userauth" service [SSH-USERAUTH]. These names authentication method for the "ssh-userauth" service [SSH-
MUST be printable US-ASCII strings, and MUST NOT contain the USERAUTH]. These names MUST be printable US-ASCII strings, and
characters at-sign ('@'), comma (','), or whitespace or control MUST NOT contain the characters at-sign ('@'), comma (','), or
characters (ASCII codes 32 or less). Names are case-sensitive, and whitespace or control characters (ASCII codes 32 or less). Names
MUST NOT be longer than 64 characters. are case-sensitive, and 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
accompanied by an RFC which describes the interpretation for the be accompanied by an RFC which describes the interpretation for
authentication method. 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]
2.2 Connection Protocol Assigned Names 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
Names are case-sensitive, and MUST NOT be longer than 64 characters. less). 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
an RFC which describes the interpretation for the type or request. by an RFC which describes the interpretation for the type or
request.
2.2.1 Connection Protocol Channel Types 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]
skipping to change at page 7, line 4 skipping to change at page 7, line 4
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. Key Exchange Method Names 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
protocol [SSH-TRANS]. The names MUST be printable US-ASCII strings, the protocol [SSH-TRANS]. The names MUST be printable US-ASCII
and MUST NOT contain the characters at-sign ('@'), comma (','), or strings, and MUST NOT contain the characters at-sign ('@'), comma
whitespace or control characters (ASCII codes 32 or less). Names are (','), or whitespace or control characters (ASCII codes 32 or
case-sensitive, and MUST NOT be longer than 64 characters. less). Names are 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
which describes this method. RFC 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]
4. Assigned Algorithm Names 4. Assigned Algorithm Names
The following identifiers (names) MUST be printable US-ASCII strings, The following identifiers (names) MUST be printable US-ASCII
and MUST NOT contain the characters at-sign ('@'), comma (','), or strings, and MUST NOT contain the characters at-sign ('@'), comma
whitespace or control characters (ASCII codes 32 or less). Names are (','), or whitespace or control characters (ASCII codes 32 or
case-sensitive, and MUST NOT be longer than 64 characters. less). Names are 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
a reference to a standards-track or Informational RFC or a reference by a reference to a standards-track or Informational RFC or a
to published cryptographic literature which describes the algorithm. reference to published cryptographic literature which describes
the algorithm.
4.1 Encryption Algorithm Names 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]
skipping to change at page 8, line 31 skipping to change at page 8, line 34
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]
References References
[SSH-ARCH] Ylonen, T., "SSH Protocol Architecture", I-D draft- [SSH-ARCH] Ylonen, T., "SSH Protocol Architecture", I-D
ietf-architecture-13.txt, September 2002. draft-ietf-architecture-14.txt, July 2003.
[SSH-TRANS] Ylonen, T., "SSH Transport Layer Protocol", I-D [SSH-TRANS] Ylonen, T., "SSH Transport Layer Protocol", I-D
draft-ietf-transport-15.txt, September 2002. draft-ietf-transport-16.txt, July 2003.
[SSH-USERAUTH] Ylonen, T., "SSH Authentication Protocol", I-D draft- [SSH-USERAUTH] Ylonen, T., "SSH Authentication Protocol", I-D
ietf-userauth-16.txt, September 2002. draft-ietf-userauth-17.txt, July 2003.
[SSH-CONNECT] Ylonen, T., "SSH Connection Protocol", I-D draft- [SSH-CONNECT] Ylonen, T., "SSH Connection Protocol", I-D draft-
ietf-connect-16.txt, September 2002. ietf-connect-17.txt, July 2003.
[SSH-NUMBERS] Lehtinen, S. and D. Moffat, "SSH Protocol Assigned
Numbers", I-D draft-ietf-secsh-assignednumbers-
03.txt, July 2003.
[FIPS-46-3] U.S. Dept. of Commerce, ., "FIPS PUB 46-3, Data [FIPS-46-3] U.S. Dept. of Commerce, ., "FIPS PUB 46-3, Data
Encryption Standard (DES)", October 1999. Encryption 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
skipping to change at page 10, line 7 skipping to change at page 10, line 7
Darren J Moffat Darren J Moffat
Sun Microsystems Sun Microsystems
901 San Antonio Road 901 San Antonio Road
Palo Alto 94303 Palo Alto 94303
USA USA
EMail: Darren.Moffat@Sun.COM EMail: Darren.Moffat@Sun.COM
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2002). All Rights Reserved. Copyright (C) The Internet Society (2003). 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
others, and derivative works that comment on or otherwise explain it to others, and derivative works that comment on or otherwise
or assist in its implementation may be prepared, copied, published explain it or assist in its implementation may be prepared,
and distributed, in whole or in part, without restriction of any copied, published and distributed, in whole or in part, without
kind, provided that the above copyright notice and this paragraph are restriction of any kind, provided that the above copyright notice
included on all such copies and derivative works. However, this and this paragraph are included on all such copies and derivative
document itself may not be modified in any way, such as by removing works. However, this document itself may not be modified in any
the copyright notice or references to the Internet Society or other way, such as by removing the copyright notice or references to the
Internet organizations, except as needed for the purpose of Internet Society or other Internet organizations, except as needed
developing Internet standards in which case the procedures for for the purpose of developing Internet standards in which case the
copyrights defined in the Internet Standards process must be procedures for copyrights defined in the Internet Standards
followed, or as required to translate it into languages other than process must be followed, or as required to translate it into
English. languages other than English.
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns. be revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement Acknowledgement
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/