draft-ietf-dhc-isnsoption-11.txt   draft-ietf-dhc-isnsoption-12.txt 
DHC Working Group Charles Monia DHC Working Group Charles Monia
INTERNET DRAFT Josh Tseng INTERNET DRAFT Josh Tseng
Expires: September 2004 Kevin Gibbons Expires: January 2005 Kevin Gibbons
Internet Draft Internet Draft McDATA
Document: <draft-ietf-dhc-isnsoption-11.txt> Nishan Systems Corporation
Category: Standards Track March 2004 Document: <draft-ietf-dhc-isnsoption-12.txt>
Category: Standards Track July 2004
The IPv4 DHCP Option for the Internet Storage Name Service The IPv4 DHCP Option for the Internet Storage Name Service
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with By submitting this Internet-Draft, I certify that any applicable
all provisions of Section 10 of [RFC2026]. patent or other IPR claims of which I am aware have been disclosed,
or will be disclosed, and any of which I become aware will be
disclosed, in accordance with RFC 3668.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Internet-Drafts are draft documents valid for a maximum of Drafts. Internet-Drafts are draft documents valid for a maximum of
six months and may be updated, replaced, or made obsolete by other six months and may be updated, replaced, or made obsolete by other
documents at any time. It is inappropriate to use Internet- Drafts documents at any time. It is inappropriate to use Internet- Drafts
as reference material or to cite them other than as "work in as reference material or to cite them other than as "work in
progress." progress."
skipping to change at page 1, line 37 skipping to change at page 2, line 5
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.
Comments Comments
Comments should be sent to the DHCP mailing list (dhcwg@ietf.org) or Comments should be sent to the DHCP mailing list (dhcwg@ietf.org) or
to the authors. to the authors.
DHCP Option Number for iSNS Revision 12 July 2004
Table of Contents Table of Contents
DHCP Option Number for iSNS Revision 11 March 2004
Status of this Memo...................................................1 Status of this Memo...................................................1
Comments..............................................................1 Comments..............................................................1
Abstract..............................................................3 Abstract..............................................................3
Conventions used in this document.....................................3 Conventions used in this document.....................................3
1. Introduction.....................................................3 1. Introduction.......................................................3
2. iSNS Option for DHCP.............................................4 2. iSNS Option for DHCP...............................................4
2.1 iSNS Functions Field.............................................5 2.1 iSNS Functions Field..............................................5
2.2 Discovery Domain Access Field....................................7 2.2 Discovery Domain Access Field.....................................7
2.3 Administrative Flags Field.......................................8 2.3 Administrative Flags Field........................................8
2.4 iSNS Server Security Bitmap......................................8 2.4 iSNS Server Security Bitmap.......................................9
3. Security Considerations.........................................10 3. Security Considerations...........................................10
4. IANA Considerations.............................................11 4. IANA Considerations...............................................11
5. Normative References............................................11 5. Normative References..............................................12
6. Non-Normative References........................................11 6. Non-Normative References..........................................12
7. Author's Addresses..............................................12 7. Author's Addresses................................................13
Full Copyright Statement.............................................13 8. Intellectual Property.............................................13
DHCP Option Number for iSNS Revision 11 March 2004 9. Full Copyright Statement..........................................13
10. Disclaimer of Validity...........................................13
11. Acknowledgement..................................................14
12. Expiration Notice................................................14
DHCP Option Number for iSNS Revision 12 July 2004
Abstract Abstract
This document describes the DHCP option to allow Internet Storage This document describes the DHCP option to allow Internet Storage
Name Service (iSNS) clients to automatically discover the location Name Service (iSNS) clients to automatically discover the location
of the iSNS server through the use of DHCP for IPv4. iSNS provides of the iSNS server through the use of DHCP for IPv4. iSNS provides
discovery and management capabilities for Internet SCSI (iSCSI) and discovery and management capabilities for Internet SCSI (iSCSI) and
Internet Fibre Channel Protocol (iFCP) storage devices in an Internet Fibre Channel Protocol (iFCP) storage devices in an
enterprise-scale IP storage network. iSNS provides intelligent enterprise-scale IP storage network. iSNS provides intelligent
storage management services comparable to those found in Fibre storage management services comparable to those found in Fibre
skipping to change at page 3, line 57 skipping to change at page 4, line 5
fabric services to TCP/IP. fabric services to TCP/IP.
1. Introduction 1. Introduction
The Dynamic Host Configuration Protocol for IPv4 provides a The Dynamic Host Configuration Protocol for IPv4 provides a
framework for passing configuration information to hosts. Its framework for passing configuration information to hosts. Its
usefulness extends to hosts and devices using the iSCSI and iFCP usefulness extends to hosts and devices using the iSCSI and iFCP
protocols to connect to block level storage assets over a TCP/IP protocols to connect to block level storage assets over a TCP/IP
network. network.
DHCP Option Number for iSNS Revision 12 July 2004
The iSNS Protocol provides a framework for automated discovery, The iSNS Protocol provides a framework for automated discovery,
management, and configuration of iSCSI and iFCP devices on a TCP/IP management, and configuration of iSCSI and iFCP devices on a TCP/IP
network. It provides functionality similar to that found on Fibre network. It provides functionality similar to that found on Fibre
DHCP Option Number for iSNS Revision 11 March 2004
Channel networks, except that iSNS works within the context of an IP Channel networks, except that iSNS works within the context of an IP
network. iSNS thereby provides the requisite storage intelligence network. iSNS thereby provides the requisite storage intelligence
to IP networks that are standard on existing Fibre Channel networks. to IP networks that are standard on existing Fibre Channel networks.
Existing DHCP options cannot be used to find iSNS servers for the Existing DHCP options cannot be used to find iSNS servers for the
following reasons: following reasons:
a) iSNS functionality is distinctly different from other protocols a) iSNS functionality is distinctly different from other protocols
using DHCP options. Specifically, iSNS provides a significant using DHCP options. Specifically, iSNS provides a significant
superset of capabilities compared to typical name resolution superset of capabilities compared to typical name resolution
skipping to change at page 4, line 56 skipping to change at page 5, line 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| . . . . | | . . . . |
| Additional Secondary iSNS Servers | | Additional Secondary iSNS Servers |
| . . . . | | . . . . |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1 -- iSNS Server Option Figure 1 -- iSNS Server Option
The iSNS Option specifies a list of IP addresses used by iSNS The iSNS Option specifies a list of IP addresses used by iSNS
servers. The option contains the following parameters: servers. The option contains the following parameters:
Length: the number of bytes that follow the Length field. DHCP Option Number for iSNS Revision 12 July 2004
DHCP Option Number for iSNS Revision 11 March 2004 Length: the number of bytes that follow the Length field.
iSNS Functions: A bitmapped field defining the functions supported iSNS Functions: A bitmapped field defining the functions supported
by the iSNS servers. The format of this field is described by the iSNS servers. The format of this field is described
in section 2.1. in section 2.1.
Discovery Domain Access: A bit field indicating the types of iSNS Discovery Domain Access: A bit field indicating the types of iSNS
clients that are allowed to modify Discovery Domains. The clients that are allowed to modify Discovery Domains. The
field contents are described in section 2.2. field contents are described in section 2.2.
Administrative Flags field: Contains the administrative settings for Administrative Flags field: Contains the administrative settings for
skipping to change at page 6, line 5 skipping to change at page 6, line 5
2.1 iSNS Functions Field 2.1 iSNS Functions Field
The iSNS Functions Field defines the iSNS server's operational role The iSNS Functions Field defines the iSNS server's operational role
(i.e., how the iSNS server is to be used). The iSNS server's role (i.e., how the iSNS server is to be used). The iSNS server's role
can be as basic as providing simple discovery information, or as can be as basic as providing simple discovery information, or as
significant as providing IKE/IPSec security policies and significant as providing IKE/IPSec security policies and
certificates for the use of iSCSI and iFCP devices. The format of certificates for the use of iSCSI and iFCP devices. The format of
the iSNS Functions field is shown in Figure 2: the iSNS Functions field is shown in Figure 2:
DHCP Option Number for iSNS Revision 11 March 2004 DHCP Option Number for iSNS Revision 12 July 2004
0 1 1 0 1 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RESERVED |S|A|E| | RESERVED |S|A|E|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2 -- iSNS Functions Field Figure 2 -- iSNS Functions Field
Bit field Significance Bit field Significance
--------- ------------ --------- ------------
skipping to change at page 7, line 5 skipping to change at page 7, line 5
Security Policy Indicates whether the iSNS client is to Security Policy Indicates whether the iSNS client is to
Distribution: download and use the security policy Distribution: download and use the security policy
configuration stored in the iSNS server. configuration stored in the iSNS server.
If set to one, then the policy is stored in If set to one, then the policy is stored in
the iSNS server and must be used by the the iSNS server and must be used by the
iSNS client for its own security policy. iSNS client for its own security policy.
If set to zero, then the iSNS client must If set to zero, then the iSNS client must
obtain its security policy configuration by obtain its security policy configuration by
other means. other means.
DHCP Option Number for iSNS Revision 11 March 2004 DHCP Option Number for iSNS Revision 12 July 2004
2.2 Discovery Domain Access Field 2.2 Discovery Domain Access Field
The format of the DD Access bit field is shown in Figure 3: The format of the DD Access bit field is shown in Figure 3:
0 1 1 1 1 1 1 0 1 1 1 1 1 1
0 ... 9 0 1 2 3 4 5 0 ... 9 0 1 2 3 4 5
+---+---+---+---+---+---+---+---+---+ +---+---+---+---+---+---+---+---+---+
| RESERVED | if| tf| is| ts| C | E | | RESERVED | if| tf| is| ts| C | E |
+---+---+---+---+---+---+---+---+---+ +---+---+---+---+---+---+---+---+---+
skipping to change at page 7, line 57 skipping to change at page 8, line 4
iSCSI Initiator, respective registered iSNS client iSCSI Initiator, respective registered iSNS client
iFCP Target Port, (determined by iSCSI Node Type or iFCP iFCP Target Port, (determined by iSCSI Node Type or iFCP
iFCP Initiator Port Role) is allowed to add, delete, or iFCP Initiator Port Role) is allowed to add, delete, or
Port: modify Discovery Domains. If set to Port: modify Discovery Domains. If set to
one, then modification by the specified one, then modification by the specified
client type is allowed. If set to zero, client type is allowed. If set to zero,
then modification by the specified then modification by the specified
client type is not allowed. client type is not allowed.
(A node may implement multiple node (A node may implement multiple node
DHCP Option Number for iSNS Revision 12 July 2004
types.) types.)
DHCP Option Number for iSNS Revision 11 March 2004
2.3 Administrative Flags Field 2.3 Administrative Flags Field
The format of the Administrative Flags bit field is shown in The format of the Administrative Flags bit field is shown in
Figure 4: Figure 4:
0 1 1 0 1 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RESERVED |D|M|H|E| | RESERVED |D|M|H|E|
skipping to change at page 8, line 53 skipping to change at page 9, line 4
iSNS server, followed by the IP iSNS server, followed by the IP
address(es) of any backup servers (see address(es) of any backup servers (see
Figure 1). If set to zero, then a1-a4 Figure 1). If set to zero, then a1-a4
contains the IP address of the primary contains the IP address of the primary
iSNS server, followed by the IP iSNS server, followed by the IP
address(es) of any backup servers. address(es) of any backup servers.
Management SCNs: Indicates whether control nodes are Management SCNs: Indicates whether control nodes are
authorized to register to receive authorized to register to receive
Management State Change Notifications Management State Change Notifications
DHCP Option Number for iSNS Revision 12 July 2004
(SCN's). Management SCN's are a special (SCN's). Management SCN's are a special
class of State Change Notification whose class of State Change Notification whose
scope is the entire iSNS database. If scope is the entire iSNS database. If
set to one, then control nodes are set to one, then control nodes are
authorized to register to receive authorized to register to receive
Management SCN's. If set to zero, then Management SCN's. If set to zero, then
DHCP Option Number for iSNS Revision 11 March 2004
control nodes are not authorized to control nodes are not authorized to
receive Management SCN's (although they receive Management SCN's (although they
may receive normal SCN's). may receive normal SCN's).
Default Discovery Indicates whether a newly registered Default Discovery Indicates whether a newly registered
Domain: device that is not explicitly placed Domain: device that is not explicitly placed
into a Discovery Domain (DD) and into a Discovery Domain (DD) and
Discovery Domain Set (DDS) should be Discovery Domain Set (DDS) should be
automatically placed into a default DD automatically placed into a default DD
and DDS. If set to one, then a default and DDS. If set to one, then a default
skipping to change at page 10, line 5 skipping to change at page 10, line 5
31 Enabled 31 Enabled
30 IKE/IPSec 30 IKE/IPSec
29 Main Mode 29 Main Mode
28 Aggressive Mode 28 Aggressive Mode
27 PFS 27 PFS
26 Transport Mode 26 Transport Mode
25 Tunnel Mode 25 Tunnel Mode
iSNS Server Security Bitmap definitions: iSNS Server Security Bitmap definitions:
DHCP Option Number for iSNS Revision 11 March 2004 DHCP Option Number for iSNS Revision 12 July 2004
Enabled This bit specifies the validity of the Enabled This bit specifies the validity of the
remainder of the iSNS server security remainder of the iSNS server security
bitmap. If set to one, then the contents bitmap. If set to one, then the contents
of the remainder of the field are valid. of the remainder of the field are valid.
If set to zero, then the contents of the If set to zero, then the contents of the
rest of the field are undefined and MUST rest of the field are undefined and MUST
be ignored. be ignored.
IKE/IPSec 1 = IKE/IPSec enabled; 0 = IKE/IPSec IKE/IPSec 1 = IKE/IPSec enabled; 0 = IKE/IPSec
skipping to change at page 10, line 46 skipping to change at page 10, line 46
an IPSec security association for the iSNS session. an IPSec security association for the iSNS session.
If IKE/IPsec is enabled, an implementation SHALL enable: If IKE/IPsec is enabled, an implementation SHALL enable:
a) One of Main Mode or Aggressive Mode but not both and a) One of Main Mode or Aggressive Mode but not both and
b) One of Transport Mode or Tunnel Mode but not both. b) One of Transport Mode or Tunnel Mode but not both.
3. Security Considerations 3. Security Considerations
DHCP security considerations are addressed in [RFC3118]. Among The DHCP Authentication security option as specified in [RFC3118]
these is the potential for a "man-in-the-middle" attack by a hostile to protect the iSNS option may present a problem due to the limited
entity modifying or replacing the original iSNS option message. implementation and deployment of the DHCP authentication option.
Unless some form of authentication is implemented, an attacker may The IPSec security mechanisms for iSNS itself are specified in
trick the iSNS client into connecting into rogue iSNS servers. [iSNS] to provide confidentiality when sensitive information is
distributed via iSNS. See the Security Considerations section of
[iSNS] for details and specific requirements for implementation of
IPSec.
To thwart such attacks, the DHCP response should be verified in some In addition,[iSNS] describes an authentication block that provides
manner. One approach is direct authentication via [RFC3118], when message integrity for multicast or broadcast iSNS messages (i.e. for
implemented. Since this technology is not widely deployed, an
alternative is to authenticate the discovered iSNS server through
use of IPSec or the iSNS authentication block as described in
[ISNS]. Of course, use of iSNS Server authentication implies a site
DHCP Option Number for iSNS Revision 11 March 2004
wide policy requiring use of one of the authentication methods DHCP Option Number for iSNS Revision 12 July 2004
specified in [ISNS] by all iSNS servers.
If no authentication is used and it is determined that the potential heartbeat/discovery messages only). See [RFC 3723] for further
exists for one of the attacks described in [RFC3118], then the DHCP discussion of security for these protocols.
option message for iSNS should not be utilized.
If no sensitive information, as described in [iSNS], is being
distributed via iSNS, and an Entity is discovered via iSNS,
authentication and authorization are handled by the IP Storage
protocols whose endpoints are discovered via iSNS, specifically iFCP
[iFCP] and iSCSI [RFC 3720]. It is the responsibility of the
providers of these services to ensure that an inappropriately
advertised or discovered service does not compromise their security.
When no security is used, there is a risk of distribution of false
discovery information (e.g., via the iSNS DHCP option identifying a
false iSNS server that distributes the false discovery information).
The primary countermeasure for this risk is authentication. When
this risk is a significant concern, IPsec SAs SHOULD be used for IP
Storage protocol (iSCSI and iFCP) traffic subject to this risk to
ensure that such traffic only flows between endpoints that have
participated in IKE authentication. For example, if an attacker
distributes discovery information falsely identifying an iSCSI
endpoint, that endpoint will lack the secret information necessary
to successfully complete IKE authentication, and hence will be
prevented from falsely sending or receiving iSCSI traffic. When this
risk of false discovery information is a significant concern and
IPSec is implemented for iSNS, IPSec SAs SHOULD also be used for
iSNS traffic to prevent use of a false iSNS server rather than
relying only on the IP Storage protocols to detect false discovery
information.
There remains a risk of a denial of service attack based on repeated
use of false discovery information that will cause initiation of IKE
negotiation. The countermeasures for this are administrative
configuration of each iSNS and IP Storage (iSCSI and FCIP) Entity to
limit the peers that it is willing to communicate with (i.e., by IP
address range and/or DNS domain), and maintenance of a negative
authentication cache to avoid repeatedly contacting an iSNS Entity
that fails to authenticate. These three measures (i.e., IP address
range limits, DNS domain limits, negative authentication cache) MUST
be implemented for IP Storage (iSCSI and iFCP) protocols and iSNS
Entities. For iSNS, these requirements apply only when this DHCP
option is used, and in addition, the negative authentication cache
requirement applies only when IPSec support is implemented for iSNS,
as a negative authentication cache is of no value in the absence of
authentication.
4. IANA Considerations 4. IANA Considerations
In accordance with the policy defined in [DHCP], IANA has assigned a In accordance with the policy defined in [DHCP], IANA has assigned a
value of TBD for this option. value of TBD for this option.
DHCP Option Number for iSNS Revision 12 July 2004
There are no other IANA-assigned values defined by this There are no other IANA-assigned values defined by this
specification. specification.
5. Normative References 5. Normative References
[DHCP] Droms, R., "Dynamic Host Configuration Protocol", RFC [DHCP] Droms, R., "Dynamic Host Configuration Protocol", RFC
2131, Bucknell University, March 1997. 2131, Bucknell University, March 1997.
[iSNS] Tseng, J. et al., "iSNS - Internet Storage Name [iSNS] Tseng, J. et al., "iSNS - Internet Storage Name
Service", Internet draft (work in progress), draft-ietf- Service", Internet draft (work in progress), draft-ietf-
skipping to change at page 11, line 39 skipping to change at page 12, line 28
[RFC2026] Bradner, S., "The Internet Standards Process -- [RFC2026] Bradner, S., "The Internet Standards Process --
Revision 3", BCP 9, RFC 2026, October 1996 Revision 3", BCP 9, RFC 2026, October 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
[RFC3118] Arbaugh, W., Droms, R., "Authentication for DHCP [RFC3118] Arbaugh, W., Droms, R., "Authentication for DHCP
Messages", RFC 3118, June 2001 Messages", RFC 3118, June 2001
[RFC3667] Bradner, S., "IETF Rights in Contributions", BCP 78,
RFC 3667, February 2004
[RFC3668] Bradner, S., "Intellectual Property Rights in IETF
Technology", BCP 79, RFC 3668, February 2004
[RFC3720] Satran, J., et al., "Internet Small Computer Systems
Interface (iSCSI)", RFC 3720, April 2004
[RFC3723] Aboba, B., et al., "Securing Block Storage Protocols
over IP", RFC 3723, April 2004
6. Non-Normative References 6. Non-Normative References
[iFCP] Monia, C., et al., "iFCP - A Protocol for Internet Fibre [iFCP] Monia, C., et al., "iFCP - A Protocol for Internet Fibre
Channel Storage Networking", Internet draft (work in Channel Storage Networking", Internet draft (work in
progress), draft-ietf-ips-ifcp-13.txt, May 2002 progress), draft-ietf-ips-ifcp-13.txt, May 2002
[iSCSI] Satran, J., et al., "iSCSI", Internet draft (work in
progress), draft-ietf-ips-iSCSI-15.txt, August 2002
[SEC-IPS] Aboba, B., et al., "Securing IP Block Storage
Protocols", draft-ietf-ips-security-14.txt, June 2002
Internet Storage Name Service (iSNS) March 2004
7. Author's Addresses 7. Author's Addresses
Kevin Gibbons, Kevin Gibbons,
Charles Monia, Charles Monia,
Josh Tseng Josh Tseng
Nishan Systems McDATA Corporation
3850 North First Street 3850 North First Street
San Jose, CA 95134-1702 San Jose, CA 95134-1702
Phone: (408) 519-3700 Phone: (408) 519-3700
Email: cmonia@nishansystems.com Email: charles.monia@mcdata.com
jtseng@nishansystems.com joshtseng@yahoo.com
kgibbons@nishansystems.com kevin.gibbons@mcdata.com
Full Copyright Statement
"Copyright (C) The Internet Society March 2004. All Rights Reserved. 8. Intellectual Property
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph
are included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be The IETF takes no position regarding the validity or scope of any
revoked by the Internet Society or its successors or assigns. Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in this
document or the extent to which any license under such rights might or
might not be available; nor does it represent that it has made any
independent effort to identify any such rights. Information on the
procedures with respect to rights in RFC documents can be found in BCP 78
and BCP 79.
This document and the information contained herein is provided on an Copies of IPR disclosures made to the IETF Secretariat and any assurances
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING of licenses to be made available, or the result of an attempt made to
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING obtain a general license or permission for the use of such proprietary
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION rights by implementers or users of this specification can be obtained
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF from the IETF on-line IPR repository at http://www.ietf.org/ipr.
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE."
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary rights
that may cover technology that may be required to implement this
standard. Please address the information to the IETF at ietf-
ipr@ietf.org.
9. Full Copyright Statement
Copyright (C) The Internet Society July 2004. This document is subject to
the rights, licenses and restrictions contained in BCP 78, and except as
set forth therein, the authors retain all their rights.
10. Disclaimer of Validity
This document and the information contained herein are provided on an "AS
IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS
SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT
NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL
DHCP Option Number for iSNS Revision 12 July 2004
NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE.
Internet-Drafts are working documents of the Internet Engineering Task
Force (IETF), its areas, and its working groups. Note that other groups
may also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months and
may be upated, replaced, or obsoleted by other documents at any time. It
is inappropriate to use Internet-Drafts as reference material or to cite
them other than a "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
11. Acknowledgement
Funding for the RFC Editor function is currently provided by the Internet
Society.
12. Expiration Notice
This Internet-Draft expires in January 2005.
 End of changes. 

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