draft-ietf-dhc-isnsoption-05.txt   draft-ietf-dhc-isnsoption-06.txt 
DHC Working Group Charles Monia DHC Working Group Charles Monia
INTERNET DRAFT Josh Tseng INTERNET DRAFT Josh Tseng
Expires: August 2003 Kevin Gibbons Expires: November 2003 Kevin Gibbons
Internet Draft Internet Draft
Document: <draft-ietf-dhc-isnsoption-05.txt> Nishan Systems Document: <draft-ietf-dhc-isnsoption-06.txt> Nishan Systems
Category: Standards Track February 2003 Category: Standards Track May 2003
DHCP Options for Internet Storage Name Service The IPv4 DHCP Options 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
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
skipping to change at page 1, line 34 skipping to change at page 1, line 34
progress." progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Comments Comments
Comments should be sent to the IPS mailing list (ips@ece.cmu.edu) 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 5 February 2003 DHCP Option Number for iSNS Revision 6 May 2003
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....................................6 2.2 Discovery Domain Access Field....................................7
2.3 Administrative Flags Field.......................................7 2.3 Administrative Flags Field.......................................8
2.4 iSNS Server Security Bitmap......................................9 2.4 iSNS Server Security Bitmap......................................9
3.Security Considerations...........................................10 3.Security Considerations...........................................10
4.Normative References..............................................10 4.IANA Considerations...............................................10
5.Non-Normative References..........................................11 5.Normative References..............................................10
6.Author's Addresses................................................11 6.Non-Normative References..........................................11
7.Author's Addresses................................................11
Full Copyright Statement.............................................12 Full Copyright Statement.............................................12
DHCP Option Number for iSNS Revision 5 February 2003 DHCP Option Number for iSNS Revision 6 May 2003
Abstract Abstract
This document describes the DHCP option to allow iSNS clients using This document describes the DHCP option to allow Internet Storage
DHCP for IPv4 to automatically discover the location of the iSNS Name Service (iSNS) clients to automatically discover the location
server. iSNS provides discovery and management capabilities for of the iSNS server through the use of DHCP for IPv4. iSNS provides
iSCSI and Fibre Channel storage devices in an enterprise-scale IP discovery and management capabilities for Internet SCSI (iSCSI) and
storage network. iSNS provides intelligent storage management Internet Fibre Channel Protocol (iFCP) storage devices in an
services comparable to those found in Fibre Channel networks, enterprise-scale IP storage network. iSNS provides intelligent
allowing a commodity IP network to function in a similar capacity as storage management services comparable to those found in Fibre
a storage area network. Channel networks, allowing a commodity IP network to function in a
similar capacity as a storage 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 Internet Storage Name Service framework
and associated services. consisting of the storage network model 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].
All frame formats are in big endian network byte order. RESERVED All frame formats are in big endian network byte order. RESERVED
fields SHOULD be set to zero. fields SHOULD be set to zero.
This document uses the following terms: This document uses the following terms:
skipping to change at page 3, line 50 skipping to change at page 3, line 51
"iSCSI (Internet SCSI)" - iSCSI is an encapsulation of SCSI for a "iSCSI (Internet SCSI)" - iSCSI is an encapsulation of SCSI for a
new generation of storage devices interconnected with TCP/IP. new generation of storage devices interconnected with TCP/IP.
"iFCP (Internet Fibre Channel Protocol)" - iFCP is a gateway-to- "iFCP (Internet Fibre Channel Protocol)" - iFCP is a gateway-to-
gateway protocol designed to interconnect existing Fibre Channel gateway protocol designed to interconnect existing Fibre Channel
devices using TCP/IP. iFCP maps the Fibre Channel transport and devices using TCP/IP. iFCP maps the Fibre Channel transport and
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.
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 DHCP Option Number for iSNS Revision 6 May 2003
DHCP Option Number for iSNS Revision 5 February 2003
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 option numbers are not plausible due to the following Existing DHCP options cannot be used to find iSNS servers for the
reasons: following 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 DHCP options. Specifically, iSNS provides a significant
a significant superset of capabilities compared to typical name superset of capabilities compared to typical name resolution
resolution protocols such as DNS. It is designed to support protocols such as DNS. It is designed to support client devices
client devices that allow themselves to be configured and that allow themselves to be configured and managed from a
managed from a central iSNS server central iSNS server
b) iSNS requires a DHCP option format that provides more than the b) iSNS requires a DHCP option format that provides more than the
location of the iSNS server. The DHCP option number needs to location of the iSNS server. The DHCP option needs to specify
specify the subset of iSNS services that will be actively used the subset of iSNS services that may be actively used by the
by the iSNS client. iSNS client.
The DHCP option number for iSNS is used by iSCSI and iFCP devices to The DHCP option number for iSNS is used by iSCSI and iFCP devices to
discover the location and role of the iSNS server. The DHCP option discover the location and role of the iSNS server. The DHCP option
number assigned for iSNS by IANA is <<TBD>>. number assigned for iSNS by IANA is <<TBD>>.
2. iSNS Option for DHCP 2. iSNS Option for DHCP
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.
skipping to change at page 4, line 55 skipping to change at page 4, line 56
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| . . . . | | . . . . |
| 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.
minimum value for the Length field is 6 in order to account
for the iSNS Functions, Discovery Domain Access, and
Administrative Flags fields.
DHCP Option Number for iSNS Revision 5 February 2003 DHCP Option Number for iSNS Revision 6 May 2003
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 5, line 36 skipping to change at page 5, line 36
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.
Additional Secondary iSNS Servers: Each set of four octets specifies Additional Secondary iSNS Servers: Each set of four octets specifies
the IP address of a secondary iSNS server. the IP address of a secondary iSNS server.
The Code field through IP address field a1...a4 MUST be present in
every response to the iSNS query, hence the Length field has a
minimum value of 14.
If the Heartbeat bit is set in the Administrative Flags field (see
section 2.3), then b1...b4 MUST also be present. In this case, the
minimum value of the Length field is 18.
The inclusion of Additional Secondary iSNS Servers in the response
MUST be indicated by increasing the Length field accordingly.
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 Role bit field is shown in Figure 2: the iSNS Functions field is shown in Figure 2:
1 2 3 DHCP Option Number for iSNS Revision 6 May 2003
6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+--+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 0 1 1
|Vendor-Specific |RESERVED |S|A|E| 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+--+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2 -- iSNS Functions | Reserved |S|A|E|
DHCP Option Number for iSNS Revision 5 February 2003 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2 -- iSNS Functions Field
Bit field Significance Bit field Significance
--------- ------------ --------- ------------
31 Function Fields Enabled 15 Function Fields Enabled
30 DD-Based Authorization 14 DD-Based Authorization
29 Security policy distribution 13 Security Policy Distribution
28 - 24 Reserved
23 - 16 Vendor-specific
Enabled: This bit specifies the validity of the iSNS Functions Field definitions:
remaining iSNS Function fields. If set to
Function Fields This bit specifies the validity of the
Enabled: 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,
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
skipping to change at page 6, line 39 skipping to change at page 6, line 47
a common Discovery Domain are automatically a common Discovery Domain are automatically
allowed access to each other (if allowed access to each other (if
successfully authenticated). If this bit successfully authenticated). If this bit
is set to zero, then access authorization is set to zero, then access authorization
is not implied by domain membership and is not implied by domain membership and
must be explicitly performed by each must be explicitly performed by each
device. In either case, devices not in a device. In either case, devices not in a
common discovery domain are not allowed to common discovery domain are not allowed to
access each other. access each other.
Security: Indicates whether the iSNS client is to Security Policy Indicates whether the iSNS client is to
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.
Vendor- These bits are used to indicate the vendor- DHCP Option Number for iSNS Revision 6 May 2003
Specific: specific capabilities supported by the
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 5 February 2003 0 1
0 1 2 3 4 5 6 ... 5
0 1 2 3 4 5 6 ... 15
+---+---+---+---+---+---+---+---+---+ +---+---+---+---+---+---+---+---+---+
| if| tf| is| ts| C | E | Reserved | | if| tf| is| ts| C | E | Reserved |
+---+---+---+---+---+---+---+---+---+ +---+---+---+---+---+---+---+---+---+
Figure 3 -- Discovery Domain Access Figure 3 -- Discovery Domain Access Field
Bit field Significance Bit field Significance
--------- ------------ --------- ------------
0 iFCP Initiator Port
1 iFCP Target Port
2 iSCSI Initiator
3 iSCSI Target
4 Control Node
5 Enabled 5 Enabled
6 ... 15 Reserved 4 Control Node
3 iSCSI Target
2 iSCSI Initiator
1 iFCP Target Port
0 iFCP Initiator Port
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.
Control Node: Specifies whether the iSNS server allows Control Node: Specifies whether the iSNS server allows
skipping to change at page 7, line 52 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 6 May 2003
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:
DHCP Option Number for iSNS Revision 5 February 2003 0 1 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
1 2 3
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
--------- ------------ --------- ------------
31 Enabled 15 Enabled
30 Heartbeat 14 Heartbeat
29 Management SCNs 13 Management SCNs
28 Default Discovery Domain 12 Default Discovery Domain
27 - 16 RESERVED
Administrative Flags Field definitions:
Enabled: Specifies the validity of the remainder Enabled: Specifies the validity of the remainder
of the Administrative Flags field. If of the Administrative Flags field. If
set to one, then the contents of the set to one, then the contents of the
remaining Administrative Flags are remaining Administrative Flags are
valid. If set to zero, then the valid. If set to zero, then the
remaining contents MUST be ignored, remaining contents MUST be ignored,
indicating that iSNS administrative indicating that iSNS administrative
settings are obtained through means settings are obtained through means
other than DHCP. other than DHCP.
Heartbeat: Indicates whether the first IP address Heartbeat: Indicates whether the first IP address
is the multicast address to which the is the multicast address to which the
iSNS heartbeat message is sent. If set iSNS heartbeat message is sent. If set
to one, then a1-a4 contains the to one, then a1-a4 contains the
heartbeat multicast address and b1-b4 heartbeat multicast address and b1-b4
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. If address(es) of any backup servers (see
set to zero, then a1-a4 contains the IP Figure 1). If set to zero, then a1-a4
address of the primary iSNS server, contains the IP address of the primary
followed by the IP address(es) of any iSNS server, followed by the IP
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
(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 6 May 2003
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).
DHCP Option Number for iSNS Revision 5 February 2003
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
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
skipping to change at page 9, line 43 skipping to change at page 9, line 46
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
24 -- 0 Reserved
DHCP Option Number for iSNS Revision 5 February 2003 iSNS Server Security Bitmap definitions:
DHCP Option Number for iSNS Revision 6 May 2003
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 33 skipping to change at page 10, line 34
PFS 1 = PFS enabled; 0 = PFS disabled. PFS 1 = PFS enabled; 0 = PFS disabled.
Transport Mode 1 = Transport mode preferred; 0 = No Transport Mode 1 = Transport mode preferred; 0 = No
preference. preference.
Tunnel Mode 1 = Tunnel mode preferred; 0 = No Tunnel Mode 1 = Tunnel mode preferred; 0 = No
preference. preference.
3. Security Considerations 3. Security Considerations
DHCP currently provides no authentication or security mechanisms. [RFC3118] should be consulted to determine the requirements for
Potential exposures to attack are discussed in section 7 of the DHCP additional security measures to authenticate the iSNS option message
protocol specification [DHCP]. received by the DHCP client. If necessary, the authentication
option described in [RFC3118] should be utilized.
iSNS security considerations are discussed in [iSNS] and [SEC-IPS].
With regard to security considerations specific to the use of this With regard to security considerations specific to the use of this
DHCP option to discover the location of the iSNS server, exposure to DHCP option for iSNS server discovery, exposure to a "man-in-the-
a "man-in-the-middle" attack by an hostile entity modifying or middle" attack by a hostile entity modifying or replacing the
replacing the original iSNS option message should be considered a original iSNS option message should be considered a potential
potential security exposure. To prevent an attacker from weakening security exposure. If the authentication option in [RFC3118] is not
the required security and potentially tricking the iSNS client into implemented, then an attacker may trick the iSNS client into
connecting into rogue iSNS servers, reliance on local security connecting into rogue iSNS servers.
policy configuration is an appropriate countermeasure.
4. Normative References If the authentication option for DHCP is not implemented and it is
determined that the potential exists for a ˘man-in-the-middle÷
attack, then the DHCP option message for iSNS should not be
utilized.
iSNS security considerations are discussed in [iSNS] and [SEC-IPS].
4. IANA Considerations
None.
5. Normative References
DHCP Option Number for iSNS Revision 6 May 2003
[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.
[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
DHCP Option Number for iSNS Revision 5 February 2003
5. Non-Normative References [RFC3118] Arbaugh, W., Droms, R., "Authentication for DHCP
Messages", RFC 3118, June 2001
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 [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
6. 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 February 2003. All Rights "Copyright (C) The Internet Society May 2003. 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/