draft-ietf-dhc-isnsoption-02.txt   draft-ietf-dhc-isnsoption-03.txt 
DHC Working Group Josh Tseng DHC Working Group Josh Tseng
INTERNET DRAFT Kevin Gibbons INTERNET DRAFT Kevin Gibbons
Expires: February 2003 Charles Monia Expires: March 2003 Charles Monia
Internet Draft Internet Draft
Document: <draft-ietf-dhc-isnsoption-02.txt> Nishan Systems Document: <draft-ietf-dhc-isnsoption-03.txt> Nishan Systems
Category: Standards Track August 2002 Category: Standards Track September 2002
DHCP Options for Internet Storage Name Service DHCP Options for 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 1, line 38 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 IPS mailing list (ips@ece.cmu.edu) or Comments should be sent to the IPS mailing list (ips@ece.cmu.edu) or
to the authors. to the authors.
Table of Contents Table of Contents
DHCP Option Number for iSNS Revision 3 September 2002
Status of this Memo...................................................1 Status of this Memo...................................................1
Comments..............................................................1 Comments..............................................................1
Abstract..............................................................2 Abstract..............................................................3
Conventions used in this document.....................................2 Conventions used in this document.....................................3
1.Introduction.......................................................2 1.Introduction.......................................................3
2.iSNS Option for DHCP...............................................3 2.iSNS Option for DHCP...............................................4
2.1 iSNS Functions Field.............................................4 2.1 iSNS Functions Field.............................................5
2.2 Discovery Domain Access Field....................................5 2.2 Discovery Domain Access Field....................................6
2.3 Administrative Flags Field.......................................6 2.3 Administrative Flags Field.......................................7
3.Security Considerations............................................8 2.4 iSNS Server Security Bitmap......................................9
4.Normative References...............................................8 3.Security Considerations...........................................10
5.Non-Normative References...........................................8 4.Normative References..............................................10
6.Author's Addresses.................................................9 5.Non-Normative References..........................................10
Full Copyright Statement.............................................10 6.Author's Addresses................................................11
DHCP Option Number for iSNS Revision 2 August 2002 Full Copyright Statement.............................................12
DHCP Option Number for iSNS Revision 3 September 2002
Abstract Abstract
This document describes the DHCP option to allow iSNS clients This document describes the DHCP option to allow iSNS clients using
devices using DHCP to automatically discover the location of the DHCP to automatically discover the location of the iSNS server. iSNS
iSNS server. iSNS provides discovery and management capabilities for provides discovery and management capabilities for iSCSI and Fibre
iSCSI and Fibre Channel (FCP) storage devices in an enterprise-scale Channel (FCP) storage devices in an enterprise-scale IP storage
IP storage network. iSNS provides intelligent storage management network. iSNS provides intelligent storage management services
services comparable to those found in Fibre Channel networks, comparable to those found in Fibre Channel networks, allowing a
allowing a commodity IP network to function in a similar capacity as commodity IP network to function in a similar capacity as a storage
a storage area network. area network.
Conventions used in this document Conventions used in this document
iSNS refers to the framework consisting of the storage network model iSNS refers to the framework consisting of the storage network model
and associated services. and associated services.
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 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
this document are to be interpreted as described in [RFC2119]. this document are to be interpreted as described in [RFC2119].
skipping to change at page 3, line 4 skipping to change at page 4, line 4
The Dynamic Host Configuration Protocol provides a framework for The Dynamic Host Configuration Protocol provides a framework for
passing configuration information to hosts. Its usefulness extends passing configuration information to hosts. Its usefulness extends
to hosts and devices using the iSCSI and iFCP protocols to connect to hosts and devices using the iSCSI and iFCP protocols to connect
to block level storage assets over a TCP/IP network. to block level storage assets over a TCP/IP 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
Channel networks, except that iSNS works within the context of an IP Channel networks, except that iSNS works within the context of an IP
DHCP Option Number for iSNS Revision 2 August 2002 DHCP Option Number for iSNS Revision 3 September 2002
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 option numbers are not plausible due to the following Existing DHCP option numbers are not plausible due to the following
reasons: reasons:
a) iSNS functionality is distinctly different from other protocols a) iSNS functionality is distinctly different from other protocols
using existing DHCP option numbers. Specifically, iSNS provides using existing DHCP option numbers. Specifically, iSNS provides
a significant superset of capabilities compared to typical name a significant superset of capabilities compared to typical name
skipping to change at page 3, line 40 skipping to change at page 4, line 40
This option specifies the location of the primary and backup iSNS This option specifies the location of the primary and backup iSNS
servers and the iSNS services available to an iSNS client. servers and the iSNS services available to an iSNS client.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Code = TBD | Length | iSNS Functions | | Code = TBD | Length | iSNS Functions |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| DD Access | Administrative FLAGS | | DD Access | Administrative FLAGS |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| iSNS Server Security Bitmap |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| a1 | a2 | a3 | a4 | | a1 | a2 | a3 | a4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| b1 | b2 | b3 | b4 | | b1 | b2 | b3 | b4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| . . . . | | . . . . |
| 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. The Length: the number of bytes that follow the Length field. The
minimum value for the Length field is 6 in order to account minimum value for the Length field is 6 in order to account
for the iSNS Functions, Discovery Domain Access, and for the iSNS Functions, Discovery Domain Access, and
Administrative Flags fields. Administrative Flags fields.
DHCP Option Number for iSNS Revision 2 August 2002 DHCP Option Number for iSNS Revision 3 September 2002
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
the iSNS servers discovered through the DHCP query. The the iSNS servers discovered through the DHCP query. The
contents of this field are described in section 2.3. contents of this field are described in section 2.3.
iSNS Server Security Bitmap: Contains the iSNS server security
settings specified in section 2.4.
a1...a4: Depending on the setting of the Heartbeat bit in the a1...a4: Depending on the setting of the Heartbeat bit in the
Administrative Flags field (see section 2.3), this field Administrative Flags field (see section 2.3), this field
contains either the IP address from which the iSNS heartbeat contains either the IP address from which the iSNS heartbeat
originates (see [ISNS]) or the IP address of the primary originates (see [ISNS]) or the IP address of the primary
iSNS server. iSNS server.
b1...b4: Depending on the setting of Heartbeat bit in the b1...b4: Depending on the setting of Heartbeat bit in the
Administrative Flags field (see section 2.3), this field Administrative Flags field (see section 2.3), this field
contains either the IP address of the primary iSNS server or contains either the IP address of the primary iSNS server or
a secondary iSNS server. a secondary iSNS server.
skipping to change at page 4, line 48 skipping to change at page 6, line 4
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 Role bit field is shown in Figure 2: the iSNS Role bit field is shown in Figure 2:
1 2 3 1 2 3
6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+--+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +--+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Vendor-Specific |RESERVED |S|A|E| |Vendor-Specific |RESERVED |S|A|E|
+--+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +--+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2 -- iSNS Functions Figure 2 -- iSNS Functions
DHCP Option Number for iSNS Revision 3 September 2002
Bit field Significance Bit field Significance
--------- ------------ --------- ------------
31 Function Fields Enabled 31 Function Fields Enabled
30 DD-Based Authorization 30 DD-Based Authorization
29 Security policy distribution 29 Security policy distribution
28 - 24 Reserved 28 - 24 Reserved
23 - 16 Vendor-specific 23 - 16 Vendor-specific
Enabled: This bit specifies the validity of the Enabled: This bit specifies the validity of the
remaining iSNS Function fields. If set to remaining iSNS Function fields. If set to
one, then the contents of all other iSNS one, then the contents of all other iSNS
Function fields are valid. If set to zero, Function fields are valid. If set to zero,
DHCP Option Number for iSNS Revision 2 August 2002
then the contents of all other iSNS then the contents of all other iSNS
Function fields MUST be ignored. Function fields MUST be ignored.
DD-based Indicates whether or not devices in a DD-based Indicates whether or not devices in a
Authorization: common Discovery Domain (DD) are implicitly Authorization: common Discovery Domain (DD) are implicitly
authorized to access one another. Although authorized to access one another. Although
Discovery Domains control the scope of Discovery Domains control the scope of
device discovery, they do not necessarily device discovery, they do not necessarily
indicate whether or not a domain member is indicate whether or not a domain member is
authorized to access discovered devices. authorized to access discovered devices.
skipping to change at page 5, line 45 skipping to change at page 7, line 5
other means. other means.
Vendor- These bits are used to indicate the vendor- Vendor- These bits are used to indicate the vendor-
Specific: specific capabilities supported by the Specific: specific capabilities supported by the
indicated iSNS server. indicated iSNS server.
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:
DHCP Option Number for iSNS Revision 3 September 2002
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
+---+---+---+---+---+---+---+---+ +---+---+---+---+---+---+---+---+
| R | R | if| tf| is| ts| C | E | | R | R | if| tf| is| ts| C | E |
+---+---+---+---+---+---+---+---+ +---+---+---+---+---+---+---+---+
Figure 3 -- Discovery Domain Access Figure 3 -- Discovery Domain Access
DHCP Option Number for iSNS Revision 2 August 2002
Bit field Significance Bit field Significance
--------- ------------ --------- ------------
7 Enabled 7 Enabled
6 Control Node 6 Control Node
5 iSCSI Target 5 iSCSI Target
4 iSCSI Initiator 4 iSCSI Initiator
3 iFCP Target Port 3 iFCP Target Port
2 iFCP Initiator Port 2 iFCP Initiator Port
1 RESERVED 1 RESERVED
skipping to change at page 7, line 5 skipping to change at page 8, line 5
client type is not allowed. client type is not allowed.
(A node may implement multiple node (A node may implement multiple node
types.) types.)
2.3 Administrative Flags Field 2.3 Administrative Flags Field
The format of the Administrative Flags bit field is shown in Figure The format of the Administrative Flags bit field is shown in Figure
4: 4:
DHCP Option Number for iSNS Revision 2 August 2002 DHCP Option Number for iSNS Revision 3 September 2002
1 2 3 1 2 3
8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 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 |D|M|H|E| | RESERVED |D|M|H|E|
+---+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +---+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4 -- Administrative Flags Figure 4 -- Administrative Flags
Bit Field Significance Bit Field Significance
--------- ------------ --------- ------------
skipping to change at page 8, line 4 skipping to change at page 9, line 4
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
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
device that is not explicitly placed device that is not explicitly placed
DHCP Option Number for iSNS Revision 2 August 2002 DHCP Option Number for iSNS Revision 3 September 2002
Domain: into a Discovery Domain (DD) and Domain: 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
DD shall contain all devices in the iSNS DD shall contain all devices in the iSNS
database that have not been explicitly database that have not been explicitly
placed into a DD by an iSNS client. If placed into a DD by an iSNS client. If
set to zero, then devices not explicitly set to zero, then devices not explicitly
placed into a DD are not members of any placed into a DD are not members of any
DD. DD.
2.4 iSNS Server Security Bitmap
The format of the iSNS server security Bitmap field is shown in
Figure 5. If valid, this field communicates to the DHCP client the
security settings that are required to communicate with the
indicated iSNS server.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved |T|X|P|A|M|S|E|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 5 -- iSNS Server Security Bitmap
Bit Field Significance
--------- ----------------
31 Enabled
30 IKE/IPSec
29 Main Mode
28 Aggressive Mode
27 PFS
26 Transport Mode
25 Tunnel Mode
24 -- 0 Reserved
DHCP Option Number for iSNS Revision 3 September 2002
Enabled This bit specifies the validity of the
remainder of the iSNS server security
bitmap. If set to one, then the contents
of the remainder of the field are valid.
If set to zero, then the contents of the
rest of the field are undefined and MUST
be ignored.
IKE/IPSec 1 = IKE/IPSec enabled; 0 = IKE/IPSec
disabled.
Main Mode 1 = Main Mode enabled; 0 = Main Mode
disabled.
Aggressive Mode 1 = Aggressive mode enabled; 0 =
Aggressive mode disabled.
PFS 1 = PFS enabled; 0 = PFS disabled.
Transport Mode 1 = Transport mode preferred; 0 = No
preference.
Tunnel Mode 1 = Tunnel mode preferred; 0 = No
preference.
3. Security Considerations 3. Security Considerations
DHCP currently provides no authentication or security mechanisms. DHCP currently provides no authentication or security mechanisms.
Potential exposures to attack are discussed in section 7 of the DHCP Potential exposures to attack are discussed in section 7 of the DHCP
protocol specification [DHCP]. protocol specification [DHCP].
iSNS security considerations are discussed in [iSNS] and [SEC-IPS]. iSNS security considerations are discussed in [iSNS] and [SEC-IPS].
4. Normative References 4. Normative References
skipping to change at page 8, line 41 skipping to change at page 11, line 4
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
5. Non-Normative References 5. 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
DHCP Option Number for iSNS Revision 3 September 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
[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-
ips-isns-12.txt, August 2002 ips-isns-12.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
6. Author's Addresses 6. 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 August 2002. All Rights "Copyright (C) The Internet Society September 2002. All Rights
Reserved. This document and translations of it may be copied and Reserved. This document and translations of it may be copied and
furnished to others, and derivative works that comment on or furnished to others, and derivative works that comment on or
otherwise explain it or assist in its implementation may be otherwise explain it or assist in its implementation may be
prepared, copied, published and distributed, in whole or in part, prepared, copied, published and distributed, in whole or in part,
without restriction of any kind, provided that the above copyright without restriction of any kind, provided that the above copyright
notice and this paragraph are included on all such copies and notice and this paragraph are included on all such copies and
derivative works. However, this document itself may not be modified derivative works. However, this document itself may not be modified
in any way, such as by removing the copyright notice or references in any way, such as by removing the copyright notice or references
to the Internet Society or other Internet organizations, except as to the Internet Society or other Internet organizations, except as
needed for the purpose of developing Internet standards in which needed for the purpose of developing Internet standards in which
 End of changes. 

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