draft-ietf-dhc-isnsoption-10.txt   draft-ietf-dhc-isnsoption-11.txt 
DHC Working Group Charles Monia DHC Working Group Charles Monia
INTERNET DRAFT Josh Tseng INTERNET DRAFT Josh Tseng
Expires: March 2004 Kevin Gibbons Expires: September 2004 Kevin Gibbons
Internet Draft Internet Draft
Document: <draft-ietf-dhc-isnsoption-10.txt> Nishan Systems Document: <draft-ietf-dhc-isnsoption-11.txt> Nishan Systems
Category: Standards Track September 2003 Category: Standards Track March 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 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
skipping to change at page 2, line 4 skipping to change at page 2, line 4
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.
Table of Contents Table of Contents
DHCP Option Number for iSNS Revision 10 September 2003 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......................................9 2.4 iSNS Server Security Bitmap......................................8
3. Security Considerations.........................................10 3. Security Considerations.........................................10
4. IANA Considerations.............................................11 4. IANA Considerations.............................................11
5. Normative References............................................11 5. Normative References............................................11
6. Non-Normative References........................................11 6. Non-Normative References........................................11
7. Author's Addresses..............................................12 7. Author's Addresses..............................................12
Full Copyright Statement.............................................13 Full Copyright Statement.............................................13
DHCP Option Number for iSNS Revision 10 September 2003 DHCP Option Number for iSNS Revision 11 March 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 4, line 4 skipping to change at page 4, line 4
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.
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 10 September 2003 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
skipping to change at page 5, line 5 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. Length: the number of bytes that follow the Length field.
DHCP Option Number for iSNS Revision 10 September 2003 DHCP Option Number for iSNS Revision 11 March 2004
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 10 September 2003 DHCP Option Number for iSNS Revision 11 March 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
--------- ------------ --------- ------------
15 Function Fields Enabled 15 Function Fields Enabled
14 DD-Based Authorization 14 DD-Based Authorization
13 Security Policy Distribution 13 Security Policy Distribution
iSNS Functions Field definitions: iSNS Functions Field definitions:
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 10 September 2003 DHCP Option Number for iSNS Revision 11 March 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 0 1 1 1 1 1 1
0 1 2 3 4 5 6 ... 5 0 ... 9 0 1 2 3 4 5
+---+---+---+---+---+---+---+---+---+ +---+---+---+---+---+---+---+---+---+
| if| tf| is| ts| C | E | Reserved | | RESERVED | if| tf| is| ts| C | E |
+---+---+---+---+---+---+---+---+---+ +---+---+---+---+---+---+---+---+---+
Figure 3 -- Discovery Domain Access Field Figure 3 -- Discovery Domain Access Field
Bit field Significance Bit field Significance
--------- ------------ --------- ------------
5 Enabled 15 Enabled
4 Control Node 14 Control Node
3 iSCSI Target 13 iSCSI Target
2 iSCSI Initiator 12 iSCSI Initiator
1 iFCP Target Port 11 iFCP Target Port
0 iFCP Initiator Port 10 iFCP Initiator Port
Discovery Domain Access Field Definitions: Discovery Domain Access Field Definitions:
Enabled: This bit specifies the validity of the Enabled: This bit specifies the validity of the
remaining DD Access bit fields. If this remaining DD Access bit fields. If this
bit is set to one, then the contents of bit is set to one, then the contents of
the remainder of the DD Access field are the remainder of the DD Access field are
valid. If this bit is set to zero, then valid. If this bit is set to zero, then
the contents of the remainder of this the contents of the remainder of this
field MUST be ignored. field MUST be ignored.
skipping to change at page 8, line 4 skipping to change at page 8, line 4
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
types.) types.)
DHCP Option Number for iSNS Revision 10 September 2003 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 9, line 4 skipping to change at page 9, line 4
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
(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 10 September 2003 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
skipping to change at page 9, line 33 skipping to change at page 9, line 33
2.4 iSNS Server Security Bitmap 2.4 iSNS Server Security Bitmap
The format of the iSNS server security Bitmap field is shown in The format of the iSNS server security Bitmap field is shown in
Figure 5. If valid, this field communicates to the DHCP client the Figure 5. If valid, this field communicates to the DHCP client the
security settings that are required to communicate with the security settings that are required to communicate with the
indicated iSNS server. indicated iSNS server.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved |T|X|P|A|M|S|E| | RESERVED |T|X|P|A|M|S|E|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 5 -- iSNS Server Security Bitmap Figure 5 -- iSNS Server Security Bitmap
Bit Field Significance Bit Field Significance
--------- ---------------- --------- ----------------
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 10 September 2003 DHCP Option Number for iSNS Revision 11 March 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 11, line 4 skipping to change at page 11, line 4
entity modifying or replacing the original iSNS option message. entity modifying or replacing the original iSNS option message.
Unless some form of authentication is implemented, an attacker may Unless some form of authentication is implemented, an attacker may
trick the iSNS client into connecting into rogue iSNS servers. trick the iSNS client into connecting into rogue iSNS servers.
To thwart such attacks, the DHCP response should be verified in some To thwart such attacks, the DHCP response should be verified in some
manner. One approach is direct authentication via [RFC3118], when manner. One approach is direct authentication via [RFC3118], when
implemented. Since this technology is not widely deployed, an implemented. Since this technology is not widely deployed, an
alternative is to authenticate the discovered iSNS server through alternative is to authenticate the discovered iSNS server through
use of IPSec or the iSNS authentication block as described in use of IPSec or the iSNS authentication block as described in
[ISNS]. Of course, use of iSNS Server authentication implies a site [ISNS]. Of course, use of iSNS Server authentication implies a site
DHCP Option Number for iSNS Revision 10 September 2003 DHCP Option Number for iSNS Revision 11 March 2004
wide policy requiring use of one of the authentication methods wide policy requiring use of one of the authentication methods
specified in [ISNS] by all iSNS servers. specified in [ISNS] by all iSNS servers.
If no authentication is used and it is determined that the potential If no authentication is used and it is determined that the potential
exists for one of the attacks described in [RFC3118], then the DHCP exists for one of the attacks described in [RFC3118], then the DHCP
option message for iSNS should not be utilized. option message for iSNS should not be utilized.
4. IANA Considerations 4. IANA Considerations
skipping to change at page 12, line 4 skipping to change at page 12, line 4
[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 [iSCSI] Satran, J., et al., "iSCSI", Internet draft (work in
progress), draft-ietf-ips-iSCSI-15.txt, August 2002 progress), draft-ietf-ips-iSCSI-15.txt, August 2002
[SEC-IPS] Aboba, B., et al., "Securing IP Block Storage [SEC-IPS] Aboba, B., et al., "Securing IP Block Storage
Protocols", draft-ietf-ips-security-14.txt, June 2002 Protocols", draft-ietf-ips-security-14.txt, June 2002
Internet Storage Name Service (iSNS) November 2001 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 Nishan Systems
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: cmonia@nishansystems.com
jtseng@nishansystems.com jtseng@nishansystems.com
kgibbons@nishansystems.com kgibbons@nishansystems.com
Full Copyright Statement Full Copyright Statement
"Copyright (C) The Internet Society September 2003. All Rights "Copyright (C) The Internet Society March 2004. All Rights Reserved.
Reserved. This document and translations of it may be copied and This document and translations of it may be copied and furnished to
furnished to others, and derivative works that comment on or others, and derivative works that comment on or otherwise explain it
otherwise explain it or assist in its implementation may be or assist in its implementation may be prepared, copied, published
prepared, copied, published and distributed, in whole or in part, and distributed, in whole or in part, without restriction of any
without restriction of any kind, provided that the above copyright kind, provided that the above copyright notice and this paragraph
notice and this paragraph are included on all such copies and are included on all such copies and derivative works. However, this
derivative works. However, this document itself may not be modified document itself may not be modified in any way, such as by removing
in any way, such as by removing the copyright notice or references the copyright notice or references to the Internet Society or other
to the Internet Society or other Internet organizations, except as Internet organizations, except as needed for the purpose of
needed for the purpose of developing Internet standards in which developing Internet standards in which case the procedures for
case the 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 be The limited permissions granted above are perpetual and will not 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 an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE." MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE."
 End of changes. 

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