draft-ietf-secsh-assignednumbers-02.txt   draft-ietf-secsh-assignednumbers-03.txt 
Network Working Group S. Lehtinen Network Working Group S. Lehtinen
Internet-Draft SSH Communications Security Corp Internet-Draft SSH Communications Security Corp
Expires: January 12, 2004 D. Moffat Expires: February 12, 2004 D. Moffat
Sun Microsystems Sun Microsystems
July 14, 2003 August 14, 2003
SSH Protocol Assigned Numbers SSH Protocol Assigned Numbers
draft-ietf-secsh-assignednumbers-02.txt draft-ietf-secsh-assignednumbers-03.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 Internet-Drafts are draft documents valid for a maximum of six months
months and may be updated, replaced, or obsoleted by other and may be updated, replaced, or obsoleted by other documents at any
documents at any time. It is inappropriate to use Internet-Drafts time. It is inappropriate to use Internet-Drafts as reference
as reference material or to cite them other than as "work in material or to cite them other than as "work in progress."
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 January 12, 2004. This Internet-Draft will expire on February 12, 2004.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
Abstract Abstract
This document defines the initial state of the IANA assigned This document defines the initial state of the IANA assigned numbers
numbers for the SSH protocol as defined in [SSH-ARCH], [SSH- for the SSH protocol as defined in [SSH-ARCH], [SSH-TRANS], [SSH-
TRANS], [SSH-CONNECT], [SSH-USERAUTH]. This document does not CONNECT], [SSH-USERAUTH]. Except for one HISTORIC algorithm
define any new protocols or any number ranges not already defined generally regarded as obsolete, this document does not define any new
in the above referenced documents. It is intended only for protocols or any number ranges not already defined in the above
initalization of the IANA databases referenced in those documents. referenced documents. It is intended only for 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 The Message Number is an 8-bit value, which describes the payload of
of a packet. a packet.
Protocol packets have message numbers in the range 1 to 255. Protocol packets have message numbers in the range 1 to 255. These
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.)
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 38 skipping to change at page 3, line 39
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 Requests for assignments of new message numbers must be accompanied
accompanied by an RFC which describes the new packet type. If the by an RFC which describes the new packet type. If the RFC is not on
RFC is not on the standards-track (i.e. it is an informational or the standards-track (i.e. it is an informational or experimental
experimental RFC), it must be explicitly reviewed and approved by RFC), it must be explicitly reviewed and approved by the IESG before
the IESG before the RFC is published and the message number is the RFC is published and the message number is assigned.
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 32 skipping to change at page 4, line 31
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 The Disconnect code is an 8-bit value, which describes the disconnect
disconnect reason. Requests for assignments of new disconnect reason. Requests for assignments of new disconnect codes must be
codes must be accompanied by an RFC which describes the new accompanied by an RFC which describes the new disconnect reason code.
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 11 skipping to change at page 5, line 9
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 The Service Name is used to describe a protocol layer. These names
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, characters (ASCII codes 32 or less). Names are case-sensitive, and
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 Requests for assignments of new service names must be accompanied by
by an RFC which describes the interpretation for the service name. an RFC which describes the interpretation for the service name. If
If the RFC is not on the standards-track (i.e. it is an the RFC is not on the standards-track (i.e. it is an informational
informational or experimental RFC), it must be explicitly reviewed or experimental RFC), it must be explicitly reviewed and approved by
and approved by the IESG before the RFC is published and the the IESG before the RFC is published and the service name is
service name is assigned. 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 The Authentication Method Name is used to describe an authentication
authentication method for the "ssh-userauth" service [SSH- method for the "ssh-userauth" service [SSH-USERAUTH]. These names
USERAUTH]. These names MUST be printable US-ASCII strings, and MUST be printable US-ASCII strings, and MUST NOT contain the
MUST NOT contain the characters at-sign ('@'), comma (','), or characters at-sign ('@'), comma (','), or whitespace or control
whitespace or control characters (ASCII codes 32 or less). Names characters (ASCII codes 32 or less). Names are case-sensitive, and
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 Requests for assignments of new authentication method names must be
be accompanied by an RFC which describes the interpretation for accompanied by an RFC which describes the interpretation for the
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]
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 (','), or whitespace or control characters (ASCII codes 32 or less).
less). Names are case-sensitive, and MUST NOT be longer than 64 Names are case-sensitive, and MUST NOT be longer than 64 characters.
characters.
Requests for assignments of new assigned names must be accompanied Requests for assignments of new assigned names must be accompanied by
by an RFC which describes the interpretation for the type or an RFC which describes the interpretation for the type or request.
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 Key Exchange Method Name describes a key-exchange method for the
the protocol [SSH-TRANS]. The names MUST be printable US-ASCII protocol [SSH-TRANS]. The names MUST be printable US-ASCII strings,
strings, and MUST NOT contain the characters at-sign ('@'), comma and MUST NOT contain the characters at-sign ('@'), comma (','), or
(','), or whitespace or control characters (ASCII codes 32 or whitespace or control characters (ASCII codes 32 or less). Names are
less). Names are case-sensitive, and MUST NOT be longer than 64 case-sensitive, and MUST NOT be longer than 64 characters.
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 accompanied by a reference to a standards-track or Informational RFC
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]
4. Assigned Algorithm Names 4. Assigned Algorithm Names
The following identifiers (names) MUST be printable US-ASCII The following identifiers (names) MUST be printable US-ASCII strings,
strings, and MUST NOT contain the characters at-sign ('@'), comma and MUST NOT contain the characters at-sign ('@'), comma (','), or
(','), or whitespace or control characters (ASCII codes 32 or whitespace or control characters (ASCII codes 32 or less). Names are
less). Names are case-sensitive, and MUST NOT be longer than 64 case-sensitive, and MUST NOT be longer than 64 characters.
characters.
Requests for assignment of new algorithm names must be accompanied Requests for assignment of new algorithm names must be accompanied by
by a reference to a standards-track or Informational RFC or a a reference to a standards-track or Informational RFC or a reference
reference to published cryptographic literature which describes to published cryptographic literature which describes the algorithm.
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 34 skipping to change at page 8, line 31
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 [SSH-ARCH] Ylonen, T., "SSH Protocol Architecture", I-D draft-
draft-ietf-architecture-14.txt, July 2003. 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-16.txt, July 2003. draft-ietf-transport-16.txt, July 2003.
[SSH-USERAUTH] Ylonen, T., "SSH Authentication Protocol", I-D [SSH-USERAUTH] Ylonen, T., "SSH Authentication Protocol", I-D draft-
draft-ietf-userauth-17.txt, July 2003. 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-17.txt, July 2003. ietf-connect-17.txt, July 2003.
[SSH-NUMBERS] Lehtinen, S. and D. Moffat, "SSH Protocol Assigned [SSH-NUMBERS] Lehtinen, S. and D. Moffat, "SSH Protocol Assigned
Numbers", I-D draft-ietf-secsh-assignednumbers- Numbers", I-D draft-ietf-secsh-assignednumbers-
03.txt, July 2003. 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.
skipping to change at page 10, line 9 skipping to change at page 10, line 9
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 (2003). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished This document and translations of it may be copied and furnished to
to others, and derivative works that comment on or otherwise others, and derivative works that comment on or otherwise explain it
explain it or assist in its implementation may be prepared, or assist in its implementation may be prepared, copied, published
copied, published and distributed, in whole or in part, without and distributed, in whole or in part, without restriction of any
restriction of any kind, provided that the above copyright notice kind, provided that the above copyright notice and this paragraph are
and this paragraph are included on all such copies and derivative included on all such copies and derivative works. However, this
works. However, this document itself may not be modified in any document itself may not be modified in any way, such as by removing
way, such as by removing the copyright notice or references to the the copyright notice or references to the Internet Society or other
Internet Society or other Internet organizations, except as needed Internet organizations, except as needed for the purpose of
for the purpose of developing Internet standards in which case the developing Internet standards in which case the procedures for
procedures for copyrights defined in the Internet Standards copyrights defined in the Internet Standards process must be
process must be followed, or as required to translate it into followed, or as required to translate it into languages other than
languages other than English. English.
The limited permissions granted above are perpetual and will not The limited permissions granted above are perpetual and will not be
be revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on This document and the information contained herein is provided on an
an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 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.
--
Darren J Moffat
 End of changes. 

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