draft-ietf-kitten-gssapi-channel-bindings-00.txt   draft-ietf-kitten-gssapi-channel-bindings-01.txt 
KITTEN WG N. Williams KITTEN WG N. Williams
Internet-Draft Sun Internet-Draft Sun
Expires: December 30, 2004 July 2004 Expires: April 19, 2006 October 16, 2005
Clarifications and Extensions to the GSS-API for the Use of Channel Clarifications and Extensions to the GSS-API for the Use of Channel
Bindings Bindings
draft-ietf-kitten-gssapi-channel-bindings-00.txt draft-ietf-kitten-gssapi-channel-bindings-01.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, I certify that any applicable By submitting this Internet-Draft, each author represents that any
patent or other IPR claims of which I am aware have been disclosed, applicable patent or other IPR claims of which he or she is aware
and any of which I become aware will be disclosed, in accordance with have been or will be disclosed, and any of which he or she becomes
RFC 3668. aware will be disclosed, in accordance with Section 6 of BCP 79.
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-
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 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 30, 2004. This Internet-Draft will expire on April 19, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2005).
Abstract Abstract
This document clarifies and generalizes the GSS-API "channel This document clarifies and generalizes the GSS-API "channel
bindings" facility. This document also specifies the format of the bindings" facility. This document also specifies the format of the
various types of channel bindings. various types of channel bindings.
Table of Contents Table of Contents
1. Conventions used in this document . . . . . . . . . . . . . . 3 1. Conventions used in this document . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Generic Structure for GSS-API Channel Bindings . . . . . . . . 5 3. Generic Structure for GSS-API Channel Bindings . . . . . . . . 5
3.1 Proper Mechanism Use of Channel Bindings . . . . . . . . . 5 3.1. Proper Mechanism Use of Channel Bindings . . . . . . . . . 5
4. Channel Bindings for SSHv2 . . . . . . . . . . . . . . . . . . 6 4. Channel Bindings for SSHv2 . . . . . . . . . . . . . . . . . . 6
4.1 GSS_Make_sshv2_channel_bindings() . . . . . . . . . . . . 6 4.1. GSS_Make_sshv2_channel_bindings() . . . . . . . . . . . . 6
4.1.1 C-Bindings . . . . . . . . . . . . . . . . . . . . . . 6 4.1.1. C-Bindings . . . . . . . . . . . . . . . . . . . . . . 7
5. Channel Bindings for TLS . . . . . . . . . . . . . . . . . . . 7 5. Channel Bindings for TLS . . . . . . . . . . . . . . . . . . . 8
5.1 GSS_Make_tls_channel_bindings() . . . . . . . . . . . . . 7 5.1. GSS_Make_tls_channel_bindings() . . . . . . . . . . . . . 8
5.1.1 C-Bindings . . . . . . . . . . . . . . . . . . . . . . 7 5.1.1. C-Bindings . . . . . . . . . . . . . . . . . . . . . . 9
6. Channel Bindings for IPsec . . . . . . . . . . . . . . . . . . 8 6. Channel Bindings for IPsec . . . . . . . . . . . . . . . . . . 10
6.1 GSS_Make_ipsec_channel_bindings() . . . . . . . . . . . . 8 6.1. GSS_Make_ipsec_channel_bindings() . . . . . . . . . . . . 10
6.1.1 C-Bindings . . . . . . . . . . . . . . . . . . . . . . 9 6.1.1. C-Bindings . . . . . . . . . . . . . . . . . . . . . . 11
7. Security Considerations . . . . . . . . . . . . . . . . . . . 10 7. Security Considerations . . . . . . . . . . . . . . . . . . . 12
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13
8.1 Normative . . . . . . . . . . . . . . . . . . . . . . . . . 11 8.1. Normative . . . . . . . . . . . . . . . . . . . . . . . . 13
8.2 Informative . . . . . . . . . . . . . . . . . . . . . . . . 11 8.2. Informative . . . . . . . . . . . . . . . . . . . . . . . 13
Author's Address . . . . . . . . . . . . . . . . . . . . . . . 12 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 14
A. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 13 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 15
Intellectual Property and Copyright Statements . . . . . . . . 14 Intellectual Property and Copyright Statements . . . . . . . . . . 16
1. Conventions used in this document 1. Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
2. Introduction 2. Introduction
The concept of "channel bindings" and the abstract construction of The concept of "channel bindings" and the abstract construction of
skipping to change at page 5, line 20 skipping to change at page 5, line 20
contents of the channel bindings OCTET STRINGs. The C-Bindings contents of the channel bindings OCTET STRINGs. The C-Bindings
specification [RFC2744]then defines, in terms of C, what should be specification [RFC2744]then defines, in terms of C, what should be
generic structure for channel bindings. The Kerberos V GSS mechanism generic structure for channel bindings. The Kerberos V GSS mechanism
[RFC1964]then defines a method for encoding GSS channel bindings in a [RFC1964]then defines a method for encoding GSS channel bindings in a
way that is independent of the C-Bindings! way that is independent of the C-Bindings!
In other words, the structure of GSS channel bindings given in In other words, the structure of GSS channel bindings given in
[RFC2744] is actually generic, rather than specific to the C [RFC2744] is actually generic, rather than specific to the C
programming language. programming language.
Here, then, is a generic re-statement of this structure, in Here, then, is a generic re-statement of this structure, in pseudo-
pseudo-ASN.1: ASN.1:
GSS-CHANNEL-BINDINGS := SEQUENCE { GSS-CHANNEL-BINDINGS := SEQUENCE {
initiator-address-type INTEGER, initiator-address-type INTEGER,
initiator-address OCTET STRING, initiator-address OCTET STRING,
acceptor-address-type INTEGER, acceptor-address-type INTEGER,
acceptor-address OCTET STRING, acceptor-address OCTET STRING,
application-data OCTET STRING, application-data OCTET STRING,
} }
The values for the address fields are described in [RFC2744]. The values for the address fields are described in [RFC2744].
Language-specific bindings of the GSS-API should specify a Language-specific bindings of the GSS-API should specify a language-
language-specific formulation of this structure. specific formulation of this structure.
3.1 Proper Mechanism Use of Channel Bindings 3.1. Proper Mechanism Use of Channel Bindings
As described in [CHANNEL-BINDINGS], GSS mechanisms should exchange As described in [CHANNEL-BINDINGS], GSS mechanisms should exchange
integrity protected proofs of channel bindings, where the proof is integrity protected proofs of channel bindings, where the proof is
obtained by running a strong hash of the channel bindings data obtained by running a strong hash of the channel bindings data
(encoded as per some mechanism-specific, such as in [RFC1964]) and a (encoded as per some mechanism-specific, such as in [RFC1964]) and a
binary value to represent the initiator->acceptor, and opposite, binary value to represent the initiator->acceptor, and opposite,
direction. direction.
The encoding of channel bindings used in [RFC1964], with the addition The encoding of channel bindings used in [RFC1964], with the addition
of a binary value as described above, and the substitution of SHA-1 of a binary value as described above, and the substitution of SHA-1
skipping to change at page 6, line 12 skipping to change at page 6, line 12
for MD5 is a reasonable, generic encoding of GSS-CHANNEL-BINDINGS for MD5 is a reasonable, generic encoding of GSS-CHANNEL-BINDINGS
that any future GSS mechanisms can use. that any future GSS mechanisms can use.
4. Channel Bindings for SSHv2 4. Channel Bindings for SSHv2
The SSHv2 channel bindings are constructed as an octet string for the The SSHv2 channel bindings are constructed as an octet string for the
'application-data' field of the channel bindings by concatenating the 'application-data' field of the channel bindings by concatenating the
following values and in this order: following values and in this order:
1. The ASCII string "GSS SSHv2 CB:" 1. The ASCII string "GSS SSHv2 CB:"
2. The SSHv2 session ID 2. The SSHv2 session ID
3. Any additional application-provided data, encoded as the DER 3. Any additional application-provided data, encoded as the DER
encoding of an ASN.1 OCTET STRING encoding of an ASN.1 OCTET STRING
4.1 GSS_Make_sshv2_channel_bindings() 4.1. GSS_Make_sshv2_channel_bindings()
Inputs: Inputs:
o session_id OCTET STRING, o session_id OCTET STRING,
o additional_app_data OCTET STRING o additional_app_data OCTET STRING
Outputs: Outputs:
o major_status INTEGER, o major_status INTEGER,
o minor_status INTEGER, o minor_status INTEGER,
o channel_bindings_app_data OCTET STRING o channel_bindings_app_data OCTET STRING
Return major_status codes: Return major_status codes:
o GSS_S_COMPLETE indicates no error. o GSS_S_COMPLETE indicates no error.
o GSS_S_FAILURE indicates failure to construct the channel bindings o GSS_S_FAILURE indicates failure to construct the channel bindings
as a result, perhaps, of a memory management, or similar failure. as a result, perhaps, of a memory management, or similar failure.
This function constructs an OCTET STRING for use as the value of the This function constructs an OCTET STRING for use as the value of the
application-data field of the GSS-CHANNEL-BINDINGS structure application-data field of the GSS-CHANNEL-BINDINGS structure
described above. described above.
4.1.1 C-Bindings 4.1.1. C-Bindings
OM_uint32 gss_make_sshv2_channel_bindings( OM_uint32 gss_make_sshv2_channel_bindings(
OM_uint32 *minor_status, OM_uint32 *minor_status,
const gss_buffer_t session_id, const gss_buffer_t session_id,
const gss_buffer_t additional_app_data, const gss_buffer_t additional_app_data,
gss_buffer_t channel_bindings_app_data gss_buffer_t channel_bindings_app_data
); );
5. Channel Bindings for TLS 5. Channel Bindings for TLS
skipping to change at page 7, line 12 skipping to change at page 8, line 12
gss_buffer_t channel_bindings_app_data gss_buffer_t channel_bindings_app_data
); );
5. Channel Bindings for TLS 5. Channel Bindings for TLS
The TLS channel bindings are constructed as an octet string for the The TLS channel bindings are constructed as an octet string for the
'application-data' field of the channel bindings by concatenating the 'application-data' field of the channel bindings by concatenating the
following values and in this order: following values and in this order:
1. The ASCII string "GSS TLSv1.0 CB:" 1. The ASCII string "GSS TLSv1.0 CB:"
2. The TLS finished message sent by the client 2. The TLS finished message sent by the client
3. The TLS finished message sent by the server 3. The TLS finished message sent by the server
4. Any additional application-provided data, encoded as the DER 4. Any additional application-provided data, encoded as the DER
encoding of an ASN.1 OCTET STRING encoding of an ASN.1 OCTET STRING
5.1 GSS_Make_tls_channel_bindings() 5.1. GSS_Make_tls_channel_bindings()
Inputs: Inputs:
o client_finished_msg OCTET STRING, o client_finished_msg OCTET STRING,
o server_finished_msg OCTET STRING, o server_finished_msg OCTET STRING,
o additional_app_data OCTET STRING o additional_app_data OCTET STRING
Outputs: Outputs:
o major_status INTEGER, o major_status INTEGER,
o minor_status INTEGER, o minor_status INTEGER,
o channel_bindings_app_data OCTET STRING o channel_bindings_app_data OCTET STRING
Return major_status codes: Return major_status codes:
o GSS_S_COMPLETE indicates no error. o GSS_S_COMPLETE indicates no error.
o GSS_S_FAILURE indicates failure to construct the channel bindings o GSS_S_FAILURE indicates failure to construct the channel bindings
as a result, perhaps, of a memory management, or similar failure. as a result, perhaps, of a memory management, or similar failure.
This function constructs an OCTET STRING for use as the value of the This function constructs an OCTET STRING for use as the value of the
application-data field of the GSS-CHANNEL-BINDINGS structure application-data field of the GSS-CHANNEL-BINDINGS structure
described above. described above.
5.1.1 C-Bindings 5.1.1. C-Bindings
OM_uint32 gss_make_tls_channel_bindings( OM_uint32 gss_make_tls_channel_bindings(
OM_uint32 *minor_status, OM_uint32 *minor_status,
const gss_buffer_t client_finished_msg, const gss_buffer_t client_finished_msg,
const gss_buffer_t server_finished_msg, const gss_buffer_t server_finished_msg,
const gss_buffer_t additional_app_data, const gss_buffer_t additional_app_data,
gss_buffer_t channel_bindings_app_data gss_buffer_t channel_bindings_app_data
); );
6. Channel Bindings for IPsec 6. Channel Bindings for IPsec
skipping to change at page 8, line 12 skipping to change at page 10, line 12
gss_buffer_t channel_bindings_app_data gss_buffer_t channel_bindings_app_data
); );
6. Channel Bindings for IPsec 6. Channel Bindings for IPsec
The IPsec channel bindings are constructed as an octet string for the The IPsec channel bindings are constructed as an octet string for the
'application-data' field of the channel bindings by concatenating the 'application-data' field of the channel bindings by concatenating the
following values and in this order: following values and in this order:
1. The ASCII string "GSS IPsec CB:" 1. The ASCII string "GSS IPsec CB:"
2. The transform ID for encryption, as a 16-bit big-endian word 2. The transform ID for encryption, as a 16-bit big-endian word
3. The transform ID for integrity protection, as 16-bit in
big-endian word 3. The transform ID for integrity protection, as 16-bit in big-
4. The initiator ID payload as used in the key exchange protocol endian word
4. NOTE: The following needs to be updated to take into account
progress of BTNS.
5. The initiator ID payload as used in the key exchange protocol
used for setting up the channel's SAs used for setting up the channel's SAs
5. The responder ID payload as used in the key exchange protocol
6. The responder ID payload as used in the key exchange protocol
used for setting up the channel's SAs used for setting up the channel's SAs
6. Any additional application-provided data, encoded as the DER
7. Any additional application-provided data, encoded as the DER
encoding of an ASN.1 OCTET STRING encoding of an ASN.1 OCTET STRING
Note that traffic selectors are not included. Inclusion of Note that traffic selectors are not included. Inclusion of
confidentiality/integrity algorithms protects against MITMs that can confidentiality/integrity algorithms protects against MITMs that can
compromise weaker algorithms that policy might permit, for the same compromise weaker algorithms that policy might permit, for the same
peers, for other traffic. peers, for other traffic.
6.1 GSS_Make_ipsec_channel_bindings() 6.1. GSS_Make_ipsec_channel_bindings()
Inputs: Inputs:
o encr_alg INTEGER, o encr_alg INTEGER,
o integ_alg INTEGER, o integ_alg INTEGER,
o initiator_id OCTET_STRING, o initiator_id OCTET_STRING,
o acceptor_id OCTET_STRING, o acceptor_id OCTET_STRING,
o additional_app_data OCTET STRING o additional_app_data OCTET STRING
Outputs: Outputs:
o major_status INTEGER, o major_status INTEGER,
o minor_status INTEGER, o minor_status INTEGER,
o channel_bindings_app_data OCTET STRING o channel_bindings_app_data OCTET STRING
Return major_status codes: Return major_status codes:
o GSS_S_COMPLETE indicates no error. o GSS_S_COMPLETE indicates no error.
o GSS_S_FAILURE indicates failure to construct the channel bindings o GSS_S_FAILURE indicates failure to construct the channel bindings
as a result, perhaps, of a memory management, or similar failure. as a result, perhaps, of a memory management, or similar failure.
This function constructs an OCTET STRING for use as the value of the This function constructs an OCTET STRING for use as the value of the
application-data field of the GSS-CHANNEL-BINDINGS structure application-data field of the GSS-CHANNEL-BINDINGS structure
described above. described above.
6.1.1 C-Bindings 6.1.1. C-Bindings
OM_uint32 gss_make_ipsec_channel_bindings( OM_uint32 gss_make_ipsec_channel_bindings(
OM_uint32 *minor_status, OM_uint32 *minor_status,
OM_uint32 encr_alg, OM_uint32 encr_alg,
OM_uint32 integ_alg, OM_uint32 integ_alg,
const gss_buffer_t initiator_id, const gss_buffer_t initiator_id,
const gss_buffer_t acceptor_id, const gss_buffer_t acceptor_id,
const gss_buffer_t additional_app_data, const gss_buffer_t additional_app_data,
gss_buffer_t channel_bindings_app_data gss_buffer_t channel_bindings_app_data
); );
7. Security Considerations 7. Security Considerations
For general security considerations relating to channel bindings see For general security considerations relating to channel bindings see
[CHANNEL-BINDINGS] [CHANNEL-BINDINGS]
8. References 8. References
8.1 Normative 8.1. Normative
[RFC1964] Linn, J., "The Kerberos Version 5 GSS-API Mechanism", RFC [RFC1964] Linn, J., "The Kerberos Version 5 GSS-API Mechanism",
1964, June 1996. RFC 1964, June 1996.
[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.
[RFC2743] Linn, J., "Generic Security Service Application Program [RFC2743] Linn, J., "Generic Security Service Application Program
Interface Version 2, Update 1", RFC 2743, January 2000. Interface Version 2, Update 1", RFC 2743, January 2000.
[RFC2744] Wray, J., "Generic Security Service API Version 2 : [RFC2744] Wray, J., "Generic Security Service API Version 2 :
C-bindings", RFC 2744, January 2000. C-bindings", RFC 2744, January 2000.
8.2 Informative 8.2. Informative
[RFC0854] Postel, J. and J. Reynolds, "Telnet Protocol [RFC0854] Postel, J. and J. Reynolds, "Telnet Protocol
Specification", STD 8, RFC 854, May 1983. Specification", STD 8, RFC 854, May 1983.
[RFC1035] Mockapetris, P., "Domain names - implementation and [RFC1035] Mockapetris, P., "Domain names - implementation and
specification", STD 13, RFC 1035, November 1987. specification", STD 13, RFC 1035, November 1987.
[RFC2025] Adams, C., "The Simple Public-Key GSS-API Mechanism [RFC2025] Adams, C., "The Simple Public-Key GSS-API Mechanism
(SPKM)", RFC 2025, October 1996. (SPKM)", RFC 2025, October 1996.
[RFC2203] Eisler, M., Chiu, A. and L. Ling, "RPCSEC_GSS Protocol [RFC2203] Eisler, M., Chiu, A., and L. Ling, "RPCSEC_GSS Protocol
Specification", RFC 2203, September 1997. Specification", RFC 2203, September 1997.
[RFC2478] Baize, E. and D. Pinkas, "The Simple and Protected GSS-API [RFC2478] Baize, E. and D. Pinkas, "The Simple and Protected GSS-API
Negotiation Mechanism", RFC 2478, December 1998. Negotiation Mechanism", RFC 2478, December 1998.
[RFC2623] Eisler, M., "NFS Version 2 and Version 3 Security Issues [RFC2623] Eisler, M., "NFS Version 2 and Version 3 Security Issues
and the NFS Protocol's Use of RPCSEC_GSS and Kerberos V5", and the NFS Protocol's Use of RPCSEC_GSS and Kerberos V5",
RFC 2623, June 1999. RFC 2623, June 1999.
[RFC3530] Shepler, S., Callaghan, B., Robinson, D., Thurlow, R., [RFC3530] Shepler, S., Callaghan, B., Robinson, D., Thurlow, R.,
Beame, C., Eisler, M. and D. Noveck, "Network File System Beame, C., Eisler, M., and D. Noveck, "Network File System
(NFS) version 4 Protocol", RFC 3530, April 2003. (NFS) version 4 Protocol", RFC 3530, April 2003.
Author's Address
Nicolas Williams
Sun Microsystems
5300 Riata Trace Ct
Austin, TX 78727
US
EMail: Nicolas.Williams@sun.com
Appendix A. Acknowledgments Appendix A. Acknowledgments
The author would like to thank Mike Eisler for his work on the The author would like to thank Mike Eisler for his work on the
Channel Conjunction Mechanism I-D and for bringing the problem to a Channel Conjunction Mechanism I-D and for bringing the problem to a
head, Sam Hartman for pointing out that channel bindings provide a head, Sam Hartman for pointing out that channel bindings provide a
general solution to the channel binding problem, Jeff Altman for his general solution to the channel binding problem, Jeff Altman for his
suggestion of using the TLS finished messages as the TLS channel suggestion of using the TLS finished messages as the TLS channel
bindings, Bill Sommerfeld, for his help in developing channel bindings, Bill Sommerfeld, for his help in developing channel
bindings for IPsec, and Radia Perlman for her most helpful comments. bindings for IPsec, and Radia Perlman for her most helpful comments.
Author's Address
Nicolas Williams
Sun Microsystems
5300 Riata Trace Ct
Austin, TX 78727
US
Email: Nicolas.Williams@sun.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 Rights 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; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
skipping to change at page 14, line 41 skipping to change at page 16, line 41
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement Copyright Statement
Copyright (C) The Internet Society (2004). This document is subject Copyright (C) The Internet Society (2005). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
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. 53 change blocks. 
59 lines changed or deleted 91 lines changed or added

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