idnits 2.17.1 draft-ietf-ips-iscsi-slp-06.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? == There is 1 instance of lines with non-ascii characters in the document. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 1 instance of lines with non-RFC2606-compliant FQDNs in the document. -- The document has examples using IPv4 documentation addresses according to RFC6890, but does not use any IPv6 documentation addresses. Maybe there should be IPv6 examples, too? Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- 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 (September 2003) is 7528 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC3082' is defined on line 868, but no explicit reference was found in the text == Outdated reference: A later version (-01) exists of draft-kempf-svrloc-rfc2614bis-00 == Outdated reference: A later version (-10) exists of draft-ietf-ips-iscsi-name-disc-09 == Outdated reference: A later version (-08) exists of draft-ietf-ips-auth-mib-04 == Outdated reference: A later version (-22) exists of draft-ietf-ips-isns-17 == Outdated reference: A later version (-12) exists of draft-ietf-ips-iscsi-boot-07 == Outdated reference: A later version (-06) exists of draft-ietf-ips-iscsi-string-prep-04 -- Unexpected draft version: The latest known version of draft-ietf-idn-nameprep is -10, but you're referring to -11. Summary: 2 errors (**), 0 flaws (~~), 11 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft Mark Bakke 3 Cisco 4 Expires September 2003 5 John Hufferd 6 Kaladhar Voruganti 7 IBM 9 Marjorie Krueger 10 HP 12 Todd Sperry 13 Adaptec 15 March 2003 17 Finding iSCSI Targets and Name Servers Using SLP 19 Status of this Memo 21 This document is an Internet-Draft and is in full conformance with 22 all provisions of Section 10 of RFC2026. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF), its areas, and its working groups. Note that 26 other groups may also distribute working documents as Internet- 27 Drafts. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet- Drafts as reference 32 material or to cite them other than as "work in progress." 34 The list of current Internet-Drafts can be accessed at 35 http://www.ietf.org/ietf/1id-abstracts.txt 37 The list of Internet-Draft Shadow Directories can be accessed at 38 http://www.ietf.org/shadow.html. 40 Copyright Notice 42 Copyright (C) The Internet Society (2001). All Rights Reserved. 44 Abstract 46 The iSCSI protocol provides a way for hosts to access SCSI devices 47 over an IP network. This document defines the use of the Service 48 Location Protocol (SLP) by iSCSI hosts, devices, and management 49 services, along with the SLP service type templates that describe the 50 services they provide. 52 Acknowledgements 54 This draft was produced by the iSCSI Naming and Discovery team, 55 including Joe Czap, Jim Hafner, John Hufferd, and Kaladhar Voruganti 56 (IBM), Howard Hall (Pirus), Jack Harwood (EMC), Yaron Klein (Sanrad), 57 Marjorie Krueger (HP), Lawrence Lamers (San Valley), Todd Sperry 58 (Adaptec), and Joshua Tseng (Nishan). Thanks also to Julian Satran 59 (IBM) for suggesting the use of SLP for iSCSI discovery, and to Matt 60 Peterson (Caldera) and James Kempf (Sun) for reviewing the document 61 from an SLP perspective. 63 Table of Contents 65 1. Introduction.................................................2 66 2. Notation Conventions.........................................3 67 3. Terminology..................................................3 68 4. Using SLP for iSCSI Service Discovery........................4 69 5. iSCSI SLP Templates.........................................14 70 6. Security Considerations.....................................19 71 7. IANA Considerations.........................................20 72 8. Summary.....................................................20 73 9. Normative References........................................20 74 10. Informative References......................................21 75 11. Authors' Addresses..........................................22 76 12. Full Copyright Notice.......................................22 78 1. Introduction 80 iSCSI [iSCSI] is a protocol used to transport SCSI [SAM2] commands, 81 data, and status across an IP network. This protocol is connection- 82 oriented, and is currently defined over TCP. iSCSI uses a client- 83 server relationship. The client end of the connection is an 84 initiator, and sends SCSI commands; the server end of the connection 85 is called a target, and receives and executes the commands. 87 There are several methods an iSCSI initiator can use to find the 88 targets to which it should connect. Two of these methods can be 89 accomplished without the use of SLP: 91 - Each target and its address can be statically configured on the 92 initiator. 94 - Each address providing targets can be configured on the initiator; 95 iSCSI provides a mechanism by which the initiator can query the 96 address for a list of targets. 98 The above methods are further defined in "iSCSI Naming and Discovery 99 Requirements" [NDT]. 101 Each of the above methods requires a small amount of configuration to 102 be done on each initiator. The ability to discover targets and name 103 services without having to configure initiators is a desirable 104 feature. The Service Location Protocol (SLP) [RFC2608] is an IETF 105 standards track protocol that provides several features that will 106 simplify locating iSCSI services. This document describes how SLP 107 can be used in iSCSI environments to discover targets, addresses 108 providing targets, and storage management servers. 110 2. Notation Conventions 112 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 113 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 114 document are to be interpreted as described in [RFC2119]. 116 3. Terminology 118 Here are some definitions that may aid readers that are unfamiliar 119 with either SLP, SCSI, or iSCSI. Some of these definitions have been 120 reproduced from [RFC2608] and "Finding an RSIP Server with SLP" 121 [RFC3105]. 123 User Agent (UA) A process working on the client's behalf 124 to establish contact with some service. 125 The UA retrieves service information from 126 the Service Agents or Directory Agents. 128 Service Agent (SA) A process working on behalf of one or more 129 services to advertise the services and 130 their capabilities. 132 Directory Agent (DA) A process which collects service 133 advertisements. There can only be one DA 134 present per given host. 136 Scope A named set of services, typically making 137 up a logical administrative group. 139 Service Advertisement A URL, attributes, and a lifetime 140 (indicating how long the advertisement is 141 valid), providing service access 142 information and capabilities description 143 for a particular service. 145 Initiator A logical entity, typically within a host, 146 that sends SCSI commands to targets to be 147 executed. An initiator is usually present 148 in the form of a device driver. 150 Target A logical entity, typically within a 151 storage controller or gateway, that 152 receives SCSI commands from an initiator 153 and executes them. A target includes one 154 or more Logical Units (LUs); each LU is a 155 SCSI device, such as a disk or tape drive. 157 iSCSI Name A UTF-8 character string which serves as a 158 unique identifier for iSCSI initiators and 159 targets. Its format and usage is further 160 defined in [NDT]. 162 iSCSI Client A logical entity, typically a host, which 163 includes at least one iSCSI Initiator. 165 iSCSI Server A logical entity, typically a storage 166 controller or gateway, which includes at 167 least one iSCSI Target. 169 Storage Management Server An addressable entity that provides 170 management services that benefit an iSCSI 171 environment. "Storage management server" 172 is used as a generic term, rather than a 173 specific protocol or service. 175 4. Using SLP for iSCSI Service Discovery 177 Two entities are involved in iSCSI discovery. The end result is that 178 an iSCSI initiator (e.g. a host) discovers iSCSI targets, usually 179 provided by storage controllers or gateways. 181 iSCSI targets are registered with SLP as a set of service URLs, one 182 for each address on which the target may be accessed. Initiators 183 discover these targets using SLP service requests. Targets that do 184 not directly support SLP, or are under the control of a management 185 service, may be registered by a proxy service agent as part of the 186 software providing this service. 188 iSCSI entities may also use SLP to discover higher-level management 189 services where needed. 191 This section first describes the use of SLP for discovery of targets 192 by iSCSI initiators, and then describes the use of SLP to discover 193 storage management servers. 195 This document assumes that SLPv2 will be used when discovering iSCSI- 196 related services; no attempt is made to include support for SLPv1. 198 4.1. Discovering iSCSI Targets using SLP 200 The following diagram shows the relationship between iSCSI clients, 201 servers, initiators, and targets. An iSCSI client includes at least 202 one iSCSI initiator, and an SLP user agent (UA). An iSCSI server 203 includes at least one iSCSI target, and an SLP service agent (SA). 204 Some entities, such as extended copy engines, include both initiators 205 and targets. These include both an SA, for its targets to be 206 discovered, and a UA, for its initiator(s) to discover other targets. 208 +---------------------------------+ 209 | iSCSI Client | 210 | +-----------+ | 211 | | iSCSI | | 212 | | initiator | | 213 | | "myhost" | | 214 | +-----------+ | 215 | | 216 +--------------------------+------+ 217 | iSCSI Driver | UA | 218 +--------------------------+------+ 219 | TCP/UDP/IP | 220 +----------------+----------------+ 221 | Interface 1 | Interface 2 | 222 +----------------+----------------+ 223 | | 224 +------------+ | | +------------+ 225 | SLP DA | | | | SLP DA | 226 | (optional) |----+ IP Networks +----| (optional) | 227 +------------+ | | +------------+ 228 | | 229 +-----------------+-----------------| 230 | Interface 1 | Interface 2 | 231 | 192.0.2.131 | 192.0.2.3 | 232 +-----------------+-----------------+ 233 | TCP/UDP/IP | 234 +---------------------------+-------+ 235 | iSCSI Driver | SA | 236 +---------------------------+-------| 237 | | 238 | +--------+ +--------+ +---------+ | 239 | | iSCSI | | iSCSI | | iSCSI | | 240 | | target | | target | | target | | 241 | | "one" | | "two" | | "three" | | 242 | +--------+ +--------+ +---------+ | 243 | iSCSI Server | 244 +-----------------------------------+ 246 In the above drawing, the iSCSI server has three iSCSI targets that 247 the client could discover, named "one", "two" and "three". The iSCSI 248 client has an iSCSI initiator with the name "myhost". The iSCSI 249 client may use the initiator name in its SLP Service Requests as a 250 filter to discover only targets that are configured to accept iSCSI 251 connections from "myhost". 253 Each iSCSI target and initiator has a unique name, called an iSCSI 254 Name. This identifier is the same regardless of the network path 255 (through adapter cards, networks, interfaces on the storage device) 256 over which the target is discovered and accessed. For this example, 257 the iSCSI names "one" and "two", and "three" are used for the 258 targets; the initiator uses the name "myhost". An actual iSCSI name 259 would incorporate more structure, including a naming authority, and 260 is not described here. 262 Each of the iSCSI targets in the drawing can appear at two addresses, 263 since two network interfaces are present. Each target, would have 264 two service URLs. 266 An iSCSI target URL consists of its fully qualified host name or IP 267 address, the TCP port on which it is listening, and its iSCSI name. 268 An iSCSI server must register each of its individual targets at each 269 of its network addresses. 271 The iSCSI server constructs a service advertisement of the type 272 "service:iscsi:target" for each of the service URLs it wishes to 273 register. The advertisement contains a lifetime, along with other 274 attributes which are defined in the service template. 276 If the server in the above drawing is listening at TCP port 3260 for 277 both network addresses, the service URLs registered would be: 279 - 192.0.2.131:3260/one 281 - 192.0.2.131:3260/two 283 - 192.0.2.131:3260/three 285 - 192.0.2.3:3260/one 287 - 192.0.2.3:3260/two 289 - 192.0.2.3:3260/three 291 The remainder of the discovery procedure is identical to that used by 292 any client/server pair implementing SLP: 294 1. If an SLP DA is found, the SA contacts the DA and registers 295 the service advertisement. Whether or not one or more SLPv2 296 DAs are discovered, the SA maintains the advertisement itself 297 and answers multicast UA queries directly. 299 2. When the iSCSI initiator requires contact information for an 300 iSCSI target, the UA either contacts the DA using unicast or 301 the SA using multicast. If a UA is configured with the address 302 of the SA, it may avoid multicast and contact an SA using 303 unicast. The UA includes a query based on 304 the attributes to indicate the characteristics of the 305 target(s) it requires. 307 3. Once the UA has the host name or address of the iSCSI server 308 as well as the port number and iSCSI Target Name, it can begin the 309 normal iSCSI login to the target. 311 As information contained in the iSCSI target template may exceed 312 common network datagram sizes, the SLP implementation for both UAs 313 and SAs supporting this template MUST implement SLP over TCP. 315 4.1.1. Finding Targets Based on Initiator Credentials 317 To be allowed access to an iSCSI target, an initiator must be 318 authenticated. The initiator may be required by the target to 319 produce one or more of the following credentials: 321 - - An iSCSI Initiator Name 323 - - An IP address 325 - - A CHAP, SRP, or Kerberos credential 327 - - Any combination of the above 329 Most iSCSI targets allow access to only one or two initiators. In 330 the ideal discovery scenario, an initiator would send an SLP request, 331 and receive responses ONLY for those targets to which the initiator 332 is guaranteed a successful login. To achieve this goal, the iSCSI 333 target template contains the following attributes, each of which 334 allows a list of values: 336 1. auth-name - This attribute contains the list of initiator names 337 allowed to access this target, or the value "any", indicating 338 that no specific initiator name is required. 340 2. auth-addr - This attribute contains the list of host names 341 and/or IP addresses which will be allowed access to this target, 342 or the value "any", indicating that no specific address or 343 host name is required. If a large number of addresses is to 344 be allowed (perhaps a subnet), this attribute may contain the 345 value "any". 347 3. auth-cred - This attribute contains a list of "method/identifier" 348 credentials that will be allowed access to the target, provided 349 they can produce the correct password or other verifier during 350 the login process. If no specific credentials are required, the 351 value "any" is used. 353 The above identifiers follow the semantics described in the IP 354 Storage Authentication MIB [AUTH-MIB]. Examples showing initiator 355 searches based on auth-xxxx attributes are shown in the target- 356 specific template section below. 358 4.1.2. Supporting Access by Multiple Identities to the Same Target 360 If a target is to allow access to multiple host identities, more than 361 one combination of auth-xxxx attributes will need to be present. 362 Since service URLs must be unique, each of these must be registered 363 under its own service URL. 365 For systems that support the configuration of multiple identities to 366 access a target, the service URL must contain an additional, opaque 367 string defining the identity. This appears after the iSCSI name in 368 the URL string, and is separated by a "/". Each registered (target- 369 address, target-name, initiator-identity) tuple can then register its 370 own set of auth-xxxx attributes. 372 An initiator-identity is equivalent to the authentication identity 373 defined in [AUTH-MIB]. 375 4.1.3. Using SLP in a Non-Multicast Environment 377 In some networks, the use of multicast for discovery purposes is 378 either unavailable or not allowed. Such networks include public or 379 service-provider networks that are placed in between an iSCSI client 380 and server; these are probably most common between two iSCSI 381 gateways, one at a storage service provider site, and one at a 382 customer site. 384 In these networks, an initiator may, instead or in addition to its DA 385 configuration, allow the addresses of one or more SAs to be 386 configured. The initiator would then make unicast SLP service 387 requests directly to these SAs, without the use of multicast to first 388 discover them. 390 This functionality is well within the scope of the current SLP 391 protocol. However, it does have two consequences for implementors: 393 - A service-agent responding to requests for iSCSI targets MUST 394 implement SLP over TCP; UDP only is not enough. This is not 395 an issue, since TCP is a requirement for iSCSI implementations 396 that use SLP for other reasons. 398 - An initiator configured to make direct, unicast requests to an 399 SA will have to add this to the SLP API, if it is following the 400 service location API defined in [RFC2614]. This capability 401 is being added to the next revision of the API, in [2614BIS]. 403 4.2. Discovering Storage Management Services using SLP 405 Storage management servers can be built to manage and control access 406 to targets in a variety of ways. They can also provide extended 407 services beyond discovery, which could include storage allocation and 408 management. None of these services are defined here; the intent of 409 this document is to allow these services to be discovered by both 410 clients and servers, in addition to the target discovery already 411 being performed. 413 The following drawing shows an iSCSI client, an iSCSI server, and a 414 storage management server. To simplify the drawing, the second IP 415 network is not shown, but is assumed to exist. The storage 416 management server would use its own protocol (smsp) to provide 417 capabilities to iSCSI clients and servers; these clients and servers 418 can both use SLP to discover the storage management server. 420 +---------------------------+ 421 | iSCSI Client | 422 | | 423 | +-----------+ | 424 | | iSCSI | | 425 | | initiator | | 426 | +-----------+ | 427 | | 428 +---------------+------+----+ +------------+ 429 | iSCSI Driver | smsp | UA | | SLP DA | 430 +---------------+------+----+ | | 431 | TCP/UDP/IP | | (optional) | 432 +---------------+------+----+ +------------+ 433 | | 434 | IP Network | 435 ------------------------------------------ 436 | | 437 | | 438 +---------------+-----------+ +---------------------+ 439 | TCP/UDP/IP | | TCP/UDP/IP | 440 +---------------+------+----+ +---------------------+ 441 | iSCSI Driver | smsp | UA | | SA | smsp | 442 +---------------+------+----+ +---------------------+ 443 | | | | 444 | +--------+ +--------+ | | storage mgmt server | 445 | | iSCSI | | iSCSI | | | | 446 | | target | | target | | +---------------------+ 447 | | 1 | | 2 | | 448 | +--------+ +--------+ | 449 | | 450 | iSCSI Server | 451 +---------------------------+ 453 Note the difference between the storage management server model and 454 the previously-defined target discovery model. When target discovery 455 was used, the iSCSI Server implemented an SA, to be discovered by the 456 initiator's UA. In the storage management server model, the iSCSI 457 clients and servers both implement UAs, and the management server 458 implements the SA. 460 A storage management server's URL contains the domain name or IP 461 address and TCP port. No other information is required. 463 The storage management server constructs a service advertisement of 464 the type "service:iscsi:sms" for each of the addresses at which it 465 appears. The advertisement contains the URL, a lifetime, along with 466 other attributes which are defined in the service template. 468 The remainder of the discovery procedure is identical to that used to 469 discover iSCSI targets, except that both initiators and targets would 470 normally be "clients" of the storage management service. 472 Targets that support a storage management service implement a UA in 473 addition to the SA. A target may alternatively just implement the 474 UA, and allow the storage management service to advertise its targets 475 appropriately by providing an SA and registering the appropriate 476 service:iscsi:target registrations on the target's behalf; the target 477 device would not have to advertise its own targets. This has no 478 impact on the initiator. 480 This allows the initiators' discovery of targets to be completely 481 interoperable regardless of which storage management service is used, 482 or whether one is used at all, or whether the target registrations 483 are provided directly by the target or by the management service. 485 4.3. NAT and NAPT Considerations 487 Since SLP provides IP address and TCP port information within its 488 payload, the addresses an SA or DA advertise may not be the same as 489 those a UA must use if a Network Address(/Port) Translation 490 (NAT/NAPT) device is present between the UA and the SA. This may 491 result in the UA discovering address information that is unusable. 492 Here are a few recommendations to handle this: 494 - A fully-qualified domain name (i.e. not an IP address) SHOULD be 495 used in service URLs, the mgmt-entity attribute, and the auth-addr 496 attribute. 498 - The default, IANA-assigned iSCSI TCP port number SHOULD be used in 499 service URLs, wherever possible. 501 - If advertising service URLs through a translating device (e.g. a 502 NAT/NAPT device), and the FQDN, IP address, or TCP port will be 503 translated, the translating device can provide an SLPv2 proxy 504 capability to do the translation. 506 4.4. Internationalization Considerations 508 SLP allows internationalized strings to be registered and retrieved. 509 Attributes in the template that are not marked with an 'L' (literal) 510 will be registered in a localized manner. An "en" (English) 511 localization MUST be registered, and others MAY be registered. 513 Attributes that include non-ASCII characters will be encoded using 514 UTF-8, as discussed in [STRINGPREP] and [NAMEPREP]. 516 5. iSCSI SLP Templates 518 Three templates are provided: an iSCSI target template, a management 519 service template, and an abstract template to encapsulate the two. 521 5.1. The iSCSI Abstract Service Type Template 523 This template defines the abstract service "service:iscsi". It is 524 used as a top-level service to encapsulate all other iSCSI-related 525 services. 527 Name of submitter: Mark Bakke 528 Language of service template: en 529 Security Considerations: 530 See the security considerations of the concrete service types. 532 Template Text: 533 -------------------------template begins here----------------------- 534 template-type=iscsi 536 template-version=0.1 538 template-description= 539 This is an abstract service type. The purpose of the iscsi 540 service type is to encompass all of the services used to support 541 the iSCSI protocol. 543 template-url-syntax= 544 url-path= ; Depends on the concrete service type. 546 --------------------------template ends here------------------------ 548 5.2. The iSCSI Target Concrete Service Type Template 550 This template defines the service "service:iscsi:target". An entity 551 containing iSCSI targets that wishes them discovered via SLP would 552 register each of them, with each of their addresses, as this service 553 type. 555 Initiators (and perhaps management services) wishing to discover 556 targets in this way will generally use one of the following queries: 558 1. Find a specific target, given its iSCSI Target Name: 560 Service: service:iscsi:target 561 Scope: initiator-scope-list 562 Query: (iscsi-name=iqn.2001-04.com.example.sn.456) 564 2. Find all of the iSCSI Target Names that may allow access to a 565 given initiator: 567 Service: service:iscsi:target 568 Scope: initiator-scope-list 569 Query: (auth-name=iqn.1998-03.com.example.hostid.045A7B) 571 3. Find all of the iSCSI Target Names that may allow access to 572 any initiator: 574 Service: service:iscsi:target 575 Scope: initiator-scope-list 576 Query: (auth-name=any) 578 4. Find all of the iSCSI Target Names that may allow access to 579 this initiator, or that will allow access to any initiator: 581 Service: service:iscsi:target 582 Scope: initiator-scope-list 583 Query: &(auth-name=iqn.1998-03.com.example.hostid.045A7B) 584 (auth-name=any) 586 5. Find all of the iSCSI Target Names that may allow access to 587 a given CHAP user name: 589 Service: service:iscsi:target 590 Scope: initiator-scope-list 591 Query: (auth-cred=chap/my-user-name) 593 6. Find all of the iSCSI Target Names that may allow access to 594 a given initiator that supports two IP addresses, a CHAP 595 credential and an SRP credential, and an initiator name: 597 Service: service:iscsi:target 598 Scope: initiator-scope-list 599 Query: &(|(auth-name=iqn.com.example:host47)(auth-name=any) 600 |(auth-addr=192.0.2.3)(auth-addr=192.0.2.131)(auth-addr=any) 601 |(auth-cred=chap/foo)(auth-cred=srp/my-user-name) 602 (auth-cred=any)) 604 7. Find the iSCSI Target Names from which the given initiator is 605 allowed to boot: 607 Service: service:iscsi:target 608 Scope: initiator-scope-list 609 Query: (boot-list=iqn.1998-03.com.example.hostid.045A7B) 611 8. In addition, a management service may wish to discover all 612 targets: 614 Service: service:iscsi:target 615 Scope: management-server-scope-list 616 Query: 618 More details on booting from an iSCSI target are defined in [BOOT]. 620 Name of submitter: Mark Bakke 621 Language of service template: en 622 Security Considerations: 623 See later section. 625 Template Text: 626 -------------------------template begins here----------------------- 627 template-type=iscsi:target 629 template-version=0.1 631 template-description= 632 This is a concrete service type. The iscsi:target service type is 633 used to register individual target addresses to be discovered by 634 others. UAs will generally search for these by including one of 635 the following: 637 - the iSCSI target name 638 - iSCSI initiator identifiers (iSCSI name, credential, IP address) 639 - the service URL 641 template-url-syntax= 642 url-path = hostport "/" iscsi-name [ "/" identity ] 643 hostport = host [ ":" port ] 644 host = hostname / hostnumber ; DNS name or IP address 645 hostname = *( domainlabel "." ) toplabel 646 alphanum = ALPHA / DIGIT 647 domainlabel = alphanum / alphanum *[alphanum / "-"] alphanum 648 toplabel = ALPHA / ALPHA *[ alphanum / "-" ] alphanum 649 hostnumber = ipv4-number 650 ipv4-number = 1*3DIGIT 3("." 1*3DIGIT) 651 port = 1*DIGIT 652 iscsi-name = iscsi-char ; iSCSI target name 653 identity = iscsi-char ; optional identity string 654 iscsi-char = ALPHA / DIGIT / escaped / ":" / "-" / "." 655 ; Intended to allow UTF-8 encoded strings 656 escaped = 1*(`� HEXDIG HEXDIG) 657 ; 658 ; The iscsi-name part of the URL is required and must be the iSCSI 659 ; name of the target being registered. 660 ; A device representing multiple targets must individually 661 ; register each target/address combination with SLP. 662 ; The identity part of the URL is optional, and is used to 663 ; indicate an identity that is allowed to access this target. 664 ; 665 ; Example (split into two lines for clarity): 666 ; service:iscsi:target://192.0.2.3:3260/ 667 ; iqn.2001-04.com.example.sn.45678 669 iscsi-name = string 670 # The iSCSI Name of this target. 671 # This must match the iscsi-name in the url-path. 673 portal-group = integer 674 # The iSCSI portal group tag for this address. Addresses sharing 675 # the same iscsi-name and portal-group tag can be used within the 676 # same iSCSI session. Portal groups are described in [iSCSI]. 678 transports = string M L 679 tcp 680 # This is a list of transport protocols that the registered 681 # entity supports. iSCSI is currently supported over TCP, 682 # but it is anticipated that it could be supported over other 683 # transports, such as SCTP, in the future. 684 tcp 686 mgmt-entity = string O 687 # The fully qualified domain name, or IP address in dotted-decimal 688 # notation, of the management interface of the entity containing 689 # this target. 690 # 692 alias = string O 693 # The alias string contains a descriptive name of the target. 695 auth-name = string M X 696 # A list of iSCSI Initiator Names that can access this target. 697 # Normal iSCSI names will be 80 characters or less; max length 698 # is 255. 699 # Normally, only one or a few values will be in the list. 700 # Using the equivalence search on this will evaluate to "true" 701 # if any one of the items in this list matches the query. 702 # If this list contains the default name "any", any initiator 703 # is allowed to access this target, provided it matches the 704 # other auth-xxx attributes. 706 auth-addr = string M X 707 # A list of initiator IP addresses (or host names) which will 708 # be allowed access to this target. If this list contains the 709 # default name "any", any IP address is allowed access to this 710 # target, provided it matches the other auth-xxx attributes. 712 auth-cred = string M X 713 # A list of credentials which will be allowed access to the target 714 # (provided they can provide the correct password or other 715 # authenticator). Entries in this list are of the form 716 # "method/identifier", where the currently defined methods are 717 # "chap" and "srp", both of which take usernames as their 718 # identifiers. 720 boot-list = string M O 721 # A list of iSCSI Initiator Names that can boot from this target. 722 # This list works precisely like the auth-name attribute. A name 723 # appearing in this list must either appear in the access-list, 724 # or the access-list must contain the initiator name "iscsi". 725 # Otherwise, an initiator will be unable to find its boot target. 726 # If boot-list contains the name "iscsi", any host can boot from it, 727 # but I am not sure if this is useful to anyone. 728 # If this attribute is not registered, this target is not "bootable". 729 # 730 # Note that the LUN the host boots from is not specified here; a 731 # host will generally attempt to boot from LUN 0. 732 # 733 # It is quite possible that other attributes will need to be defined 734 # here for booting as well. 736 --------------------------template ends here------------------------ 738 5.3. iSCSI Storage Management Service Templates 740 This template defines the service "service:iscsi:sms". An entity 741 supporting one or more iSCSI management service protocols may 742 register itself with SLP as this service type. 744 iSCSI clients and servers wishing to discover storage management 745 services using SLP will usually search for them by the protocol(s) 746 they support: 748 Service: service:iscsi:sms 749 Scope: initiator-scope-list 750 Query: (protocols=isns) 752 Name of submitter: Mark Bakke 753 Language of service template: en 754 Security Considerations: 755 See later section. 757 Template Text: 758 -------------------------template begins here----------------------- 759 template-type=iscsi:sms 761 template-version=0.1 763 template-description= 764 This is a concrete service type. The iscsi:sms service type 765 provides the capability for entities supporting iSCSI to discover 766 appropriate management services. 768 template-url-syntax= 769 url-path = ; The URL of the management service [RFC2608]. 771 protocols = string M 772 # The list of protocols supported by this name service. This 773 # list may be expanded in the future. There is no default. 774 # 775 # "isns" - This management service supports the use of the iSNS 776 # protocol for access management, health monitoring, and 777 # discovery management services. This protocol is defined 778 # in [ISNS]. 779 isns 781 --------------------------template ends here------------------------ 783 6. Security Considerations 785 The SLPv2 security model does not provide confidentiality, but does 786 provide an authentication mechanism for UAs to assure that service 787 advertisements only come from trusted SAs [RFC2608]. 789 Once a target or management server is discovered, authentication and 790 authorization are handled by the iSCSI protocol, or by the management 791 server's protocol. It is the responsibility of the providers of 792 these services to ensure that an inappropriately advertised or 793 discovered service does not compromise their security. 795 6.1. Security Implementation 797 For all implementations, IPsec SHOULD be implemented. When security 798 policy information distribution using SLPv2 is supported, IPsec MUST 799 be implemented. 801 To provide confidentiality, IPsec with ESP and a non-null transform 802 SHOULD be implemented. When security policy information distribution 803 via SLPv2 is used, IPsec with ESP and a non-null transform MUST be 804 used. 806 SLPv2 authentication is OPTIONAL to implement and use, and SLPv2 807 authentication SHOULD be implemented when IPsec is not supported. 809 The use of IPsec and IKE for SLPv2 in an IP storage environment is 810 described in [IPS-SEC]. 812 7. IANA Considerations 814 This document describes three SLP Templates. When they have been 815 reviewed and approved by the IESG, they should be registered in the 816 IANA "SVRLOC Templates" registry. This process is described in the 817 IANA Considerations section of [RFC2609]. 819 8. Summary 821 This document describes how SLP can be used by iSCSI initiators to 822 find iSCSI targets and storage management servers. Service type 823 templates for iSCSI targets and storage management servers are 824 presented. 826 9. Normative References 828 [RFC2608] E. Guttman, C. Perkins, J. Veizades, M. Day. "Service 829 Location Protocol, version 2", RFC 2608, July 1999. 831 [RFC2609] E. Guttman, C. Perkins, J. Kempf. "Service Templates and 832 service: Schemes", RFC 2609, July 1999. 834 [RFC2119] S. Bradner. "Key Words for Use in RFCs to Indicate 835 Requirement Levels", RFC 2119, March 1997. 837 [iSCSI] J. Satran, et. al. "iSCSI", Work in Progress, draft-ietf- 838 ips-iscsi-20.txt, January 2003. 840 [IPS-SEC] B. Aboba, et. al., "Securing Block Storage Protocols over 841 IP", Work in Progress, draft-ietf-ips-security-19.txt, 842 January 2003. 844 10. Informative References 846 [RFC2614] J. Kempf, E. Guttman. "An API for Service Location", RFC 847 2614, June 1999. 849 [2614BIS] J. Kempf, E. Guttman. "An API for Service Location", draft- 850 kempf-svrloc-rfc2614bis-00.txt, February 2002. 852 [SAM2] ANSI T10. "SCSI Architectural Model 2", March 2000. 854 [NDT] M. Bakke et. al. "iSCSI Naming and Discovery", Work in 855 Progress, draft-ietf-ips-iscsi-name-disc-09.txt, March 2003. 857 [AUTH-MIB] M. Bakke, J. Muchow, "Definitions of Managed Objects for 858 User Identity Authentication", Work in Progress, draft-ietf- 859 ips-auth-mib-04.txt, March 2003. 861 [ISNS] J. Tseng, et. al. "Internet Storage Name Service", Work in 862 Progress, draft-ietf-ips-isns-17.txt, January 2003. 864 [BOOT] P. Sarkar, D. Missimer, C. Sapuntzakis. "A Standard for 865 Bootstrapping Clients using the iSCSI Protocol", Work in 866 Progress, draft-ietf-ips-iscsi-boot-07.txt, October 2002. 868 [RFC3082] J. Kempf, J Goldschmidt. "Notification and Subscription for 869 SLP", RFC 3082, March 2001. 871 [RFC3105] Kempf, J., Montenegro, G. "Finding an RSIP Server with SLP", 872 RFC 3105, October 2001. 874 [STRINGPREP] 875 Bakke, M. "String Profile for iSCSI Names", Work in 876 Progress, draft-ietf-ips-iscsi-string-prep-04.txt, March 877 2003. 879 [NAMEPREP] Hoffman, P., Blanchet, M. "Nameprep: A Stringprep Profile 880 for Internationalized Domain Names", Work in Progress, 881 draft-ietf-idn-nameprep-11.txt, June 2002. 883 11. Authors' Addresses 885 Mark Bakke 886 Cisco Systems, Inc. 887 6450 Wedgwood Road 888 Maple Grove, MN 55311 889 Voice: +1 763-398-1000 890 EMail: mbakke@cisco.com 892 Kaladhar Voruganti 893 IBM Almaden Research Center 894 650 Harry Road 895 San Jose, CA 95120 896 Email: kaladhar@us.ibm.com 898 John L. Hufferd 899 IBM Storage Systems Group 900 5600 Cottle Road 901 San Jose, CA 95193 902 Voice: +1 408 256-0403 903 Email: hufferd@us.ibm.com 905 Marjorie Krueger 906 Hewlett-Packard Corporation 907 8000 Foothills Blvd 908 Roseville, CA 95747-5668, USA 909 Voice: +1 916 785-2656 910 Email: marjorie_krueger@hp.com 912 Todd Sperry 913 Adaptec, Inc. 914 691 South Milpitas Boulevard 915 Milpitas, Ca. 95035 916 Voice: +1 408 957-4980 917 Email: todd_sperry@adaptec.com 919 12. Full Copyright Notice 921 Copyright (C) The Internet Society (2001). All Rights Reserved. 923 This document and translations of it may be copied and furnished to 924 others, and derivative works that comment on or otherwise explain it 925 or assist in its implementation may be prepared, copied, published 926 and distributed, in whole or in part, without restriction of any 927 kind, provided that the above copyright notice and this paragraph are 928 included on all such copies and derivative works. However, this 929 document itself may not be modified in any way, such as by removing 930 the copyright notice or references to the Internet Society or other 931 Internet organizations, except as needed for the purpose of 932 developing Internet standards in which case the procedures for 933 copyrights defined in the Internet Standards process must be 934 followed, or as required to translate it into languages other than 935 English. 937 The limited permissions granted above are perpetual and will not be 938 revoked by the Internet Society or its successors or assigns. 940 This document and the information contained herein is provided on an 941 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 942 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 943 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 944 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 945 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 947 Acknowledgement 949 Funding for the RFC Editor function is currently provided by the 950 Internet Society.