idnits 2.17.1 draft-ietf-dhc-isnsoption-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (February 2002) is 8105 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Missing reference section? 'RFC2026' on line 227 looks like a reference -- Missing reference section? 'RFC2119' on line 230 looks like a reference -- Missing reference section? 'DHCP' on line 209 looks like a reference -- Missing reference section? 'SEC-IPS' on line 223 looks like a reference Summary: 5 errors (**), 0 flaws (~~), 1 warning (==), 6 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 DHC Josh Tseng 3 Internet Draft Nishan Systems 4 5 Expires August 2002 February 2002 7 DHCP Options for Internet Storage Name Service 9 Status of this Memo 11 This document is an Internet-Draft and is in full conformance with 12 all provisions of Section 10 of [RFC2026]. 14 Internet-Drafts are working documents of the Internet Engineering 15 Task Force (IETF), its areas, and its working groups. Note that 16 other groups may also distribute working documents as Internet- 17 Drafts. Internet-Drafts are draft documents valid for a maximum of 18 six months and may be updated, replaced, or obsoleted by other 19 documents at any time. It is inappropriate to use Internet- Drafts 20 as reference material or to cite them other than as "work in 21 progress." 23 The list of current Internet-Drafts can be accessed at 24 http://www.ietf.org/ietf/1id-abstracts.txt 26 The list of Internet-Draft Shadow Directories can be accessed at 27 http://www.ietf.org/shadow.html. 29 Comments 31 Comments should be sent to the IPS mailing list (ips@ece.cmu.edu) or 32 to the authors. 34 Table of Contents 36 Status of this Memo...................................................1 37 Comments..............................................................1 38 Abstract..............................................................2 39 Conventions used in this document.....................................2 40 1.Introduction.......................................................2 41 2.iSNS Option for DHCP...............................................3 42 3.Security Considerations............................................4 43 4.References.........................................................5 44 5.Author's Addresses.................................................5 45 Full Copyright Statement..............................................6 46 DHCP Option Number for iSNS February 2002 48 Abstract 50 This document describes the DHCP option to allow iSNS clients 51 devices using DHCP to automatically discover the location of the 52 iSNS server. iSNS provides discovery and management capabilities for 53 iSCSI and Fibre Channel (FCP) storage devices in an enterprise-scale 54 IP storage network. iSNS provides intelligent storage management 55 services comparable to those found in Fibre Channel networks, 56 allowing a commodity IP network to function in a similar capacity as 57 a storage area network. 59 Conventions used in this document 61 iSNS refers to the framework consisting of the storage network model 62 and associated services. 64 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 65 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 66 this document are to be interpreted as described in [RFC2119]. 68 All frame formats are in big endian network byte order. RESERVED 69 fields SHOULD be set to zero. 71 This document uses the following terms: 73 "iSNS Client" - iSNS clients are processes resident in iSCSI and 74 iFCP devices that initiate transactions with the iSNS server using 75 the iSNS Protocol. 77 "iSNS Server" - The iSNS server responds to iSNS protocol query and 78 registration messages, and initiates asynchronous notification 79 messages. The iSNS server stores information registered by iSNS 80 clients. 82 "iSCSI (Internet SCSI)" - iSCSI is an encapsulation of SCSI for a 83 new generation of storage devices interconnected with TCP/IP. 85 "iFCP (Internet Fibre Channel Protocol)" - iFCP is a gateway-to- 86 gateway protocol designed to interconnect existing Fibre Channel and 87 SCSI devices using TCP/IP. iFCP maps the existing FCP standard and 88 associated Fibre Channel services to TCP/IP. 90 1. Introduction 92 The Dynamic Host Configuration Protocol provides a framework for 93 passing configuration information to hosts. Its usefulness extends 94 to hosts and devices using the iSCSI and iFCP protocols to connect 95 to block level storage assets over a TCP/IP network. 97 The iSNS Protocol provides a framework for automated discovery, 98 management, and configuration of iSCSI and iFCP devices on a TCP/IP 99 network. It provides functionality similar to that found on Fibre 100 Channel networks, except that iSNS works within the context of an IP 101 DHCP Option Number for iSNS February 2002 103 network. iSNS thereby provides the requisite storage intelligence 104 to IP networks that are standard on existing Fibre Channel networks. 106 Existing DHCP option numbers are not plausible due to the following 107 reasons: 109 1) iSNS functionality is distinctly different from other protocols 110 using existing DHCP option numbers. Specifically, iSNS provides a 111 significant superset of capabilities compared to typical name 112 resolution protocols such as DNS. It is designed to support client 113 devices that allow themselves to be configured and managed from a 114 central iSNS server. 116 2) iSNS requires a DHCP option format that provides more than the 117 location of the iSNS server. The DHCP option number needs to 118 specify the subset of iSNS services that will be actively used by 119 the iSNS client. 121 The DHCP option number for iSNS is used by iSCSI and iFCP devices to 122 discover the location and role of the iSNS server. The DHCP option 123 number assigned for iSNS by IANA is <>. 125 2. iSNS Option for DHCP 127 This option specifies the location of the primary and backup iSNS 128 servers and the subset of iSNS services that will be used by the 129 iSNS client. 131 0 1 2 3 132 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 133 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 134 | Code = TBD | Length | FLAGS | 135 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 136 | a1 | a2 | a3 | a4 | 137 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 138 | b1 | b2 | b3 | b4 | 139 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 140 | . . . . | 141 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 143 The iSNS Option specifies a list of IP addresses used by iSNS 144 servers. 146 Length indicates the number of bytes that follow the Length field. 147 The minimum value for the Length field is 2 in order to account for 148 the FLAGS field. 150 The format of the FLAGS field is shown below: 152 DHCP Option Number for iSNS February 2002 154 1 2 3 155 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 156 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 157 | Site-Spec | RESERVED |S|A|H| 158 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 160 Bit field Significance 161 --------- ------------ 162 31 Heartbeat 163 30 Authorization 164 29 Security 165 28-22 RESERVED 166 21-16 Site-specific or Vendor-specific use only 168 Heartbeat: Indicates whether the first IP address is the multicast 169 address for the iSNS heartbeat message. If enabled, then a1-a4 170 contains the heartbeat multicast address and b1-b4 contains the IP 171 address of the primary iSNS server, followed by the IP address(es) 172 of any backup servers. If disabled, then a1-a4 contains the IP 173 address of the primary iSNS server, followed by the IP address(es) 174 of any backup servers. 176 Authorization: Indicates the role of the iSNS server in determining 177 device access authorizations. If disabled, then the role of the 178 iSNS server is only for discovery purposes only. Discovery Domains 179 MAY be used to manage the discovery process, but they do not 180 indicate necessarily indicate authorization to access discovered 181 devices. If enabled, then Discovery Domain/Zoning features of the 182 iSNS indicate device access authorizations. Devices in a common DD 183 SHALL be allowed access to each other if they are successfully 184 authenticated. Devices not in a common DD shall not be allowed to 185 access each other. 187 Security: Indicates whether the iSNS client is to download and use 188 the security policy configuration stored in the iSNS server. If 189 enabled, then the AuthMethod and IKE/IPSec policy stored in the iSNS 190 server SHALL be used by the iSNS client for its own security policy. 191 If disabled, then the iSNS client SHALL NOT query for its own 192 security policy attributes in the iSNS server. 194 Site-Specific: These bits are used to indicate site-specific or 195 vendor-specific capabilities in the indicated iSNS server. 197 3. Security Considerations 199 DHCP currently provides no authentication or security mechanisms. 200 Potential exposures to attack are discussed in section 7 of the DHCP 201 protocol specification [DHCP]. 203 iSNS security considerations are discussed in [iSNS] and [SEC-IPS]. 205 DHCP Option Number for iSNS February 2002 207 4. References 209 [DHCP] Droms, R., "Dynamic Host Configuration Protocol", RFC 210 2131, Bucknell University, March 1997. 212 [iSCSI] Satran, J., et al., "iSCSI", Internet draft (work in 213 progress), draft-ietf-ips-iSCSI-10.txt, January 2002 215 [iFCP] Monia, C., et al., "iFCP - A Protocol for Internet Fibre 216 Channel Storage Networking", Internet draft (work in 217 progress), draft-ietf-ips-ifcp-09.txt, January 2002 219 [iSNS] Tseng, J. et al., "iSNS - Internet Storage Name 220 Service", Internet draft (work in progress), draft-ietf- 221 ips-isns-09.txt, March 2002 223 [SEC-IPS] Aboba, B., et al., "Securing IP Block Storage 224 Protocols", draft-ietf-ips-security-09.txt, February 225 2002 227 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 228 3", BCP 9, RFC 2026, October 1996. 230 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 231 Requirement Levels", BCP 14, RFC 2119, March 1997 233 5. Author's Addresses 235 Josh Tseng 236 Nishan Systems 237 3850 North First Street 238 San Jose, CA 95134-1702 239 Phone: (408) 519-3749 240 Email: jtseng@nishansystems.com 241 Internet Storage Name Service (iSNS) November 2001 243 Full Copyright Statement 245 "Copyright (C) The Internet Society (date). All Rights Reserved. 246 This document and translations of it may be copied and furnished to 247 others, and derivative works that comment on or otherwise explain it 248 or assist in its implementation may be prepared, copied, published 249 and distributed, in whole or in part, without restriction of any 250 kind, provided that the above copyright notice and this paragraph 251 are included on all such copies and derivative works. However, this 252 document itself may not be modified in any way, such as by removing 253 the copyright notice or references to the Internet Society or other 254 Internet organizations, except as needed for the purpose of 255 developing Internet standards in which case the procedures for 256 copyrights defined in the Internet Standards process must be 257 followed, or as required to translate it into languages other than 258 English. 260 The limited permissions granted above are perpetual and will not be 261 revoked by the Internet Society or its successors or assigns. 263 This document and the information contained herein is provided on an 264 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 265 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 266 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 267 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 268 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE." 269 Internet Storage Name Service (iSNS) November 2001