idnits 2.17.1 draft-ietf-storm-iscsi-sam-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC3720, updated by this document, for RFC5378 checks: 2000-11-06) -- 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 (April 2010) is 5118 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: 'RFCxxx' is mentioned on line 792, but not defined == Unused Reference: 'SAM2' is defined on line 766, but no explicit reference was found in the text ** Obsolete normative reference: RFC 3720 (Obsoleted by RFC 7143) ** Obsolete normative reference: RFC 5048 (Obsoleted by RFC 7143) ** Obsolete normative reference: RFC 5226 (ref. 'IANA') (Obsoleted by RFC 8126) -- Possible downref: Non-RFC (?) normative reference: ref. 'SAM2' -- Possible downref: Non-RFC (?) normative reference: ref. 'SAM4' -- Possible downref: Non-RFC (?) normative reference: ref. 'SAM5' Summary: 3 errors (**), 0 flaws (~~), 3 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Storage Maintenance (StorM) Working Group F. Knight 2 Internet Draft NetApp 3 Intended status: Standards Track M. Chadalapaka 4 Expires: October 2010 Hewlett-Packard Co. 5 Updates: 3720, 5048 April 2010 7 Internet Small Computer Systems Interface (iSCSI) Update 8 draft-ietf-storm-iscsi-sam-01.txt 10 Abstract 12 Internet Small Computer Systems Interface (iSCSI) is a SCSI 13 transport protocol that maps the SCSI family of protocols onto 14 TCP/IP. RFC 3720 defines the iSCSI protocol. The current iSCSI 15 protocol (RFC 3720 and RFC 5048) is based on the SAM-2 version of 16 the SCSI family of protocols). This document defines additions 17 and changes to the iSCSI protocol to enabled additional features 18 that were added to the SCSI family of protocols through SAM-3, 19 SAM-4, and SAM-5. 21 This document updates RFC 3720 and RFC 5048 and the text in this 22 document supersedes the text in RFC 3720 and RFC 5048 when the 23 two differ. 25 Status of this Memo 27 This Internet-Draft is submitted to IETF in full conformance with 28 the provisions of BCP 78 and BCP 79. 30 Internet-Drafts are working documents of the Internet Engineering 31 Task Force (IETF), its areas, and its working groups. Note that 32 other groups may also distribute working documents as Internet- 33 Drafts. 35 Internet-Drafts are draft documents valid for a maximum of six 36 months and may be updated, replaced, or obsoleted by other 37 documents at any time. It is inappropriate to use Internet- 38 Drafts as reference material or to cite them other than as "work 39 in progress." 41 The list of current Internet-Drafts can be accessed at 42 http://www.ietf.org/1id-abstracts.html. 44 The list of Internet-Draft Shadow Directories can be accessed at 45 http://www.ietf.org/shadow.html. 47 This Internet-Draft will expire October, 2010. 49 Copyright Notice 50 Copyright (c) 2010 IETF Trust and the persons identified as the 51 document authors. All rights reserved. 53 This document is subject to BCP 78 and the IETF Trust's Legal 54 Provisions Relating to IETF Documents 55 (http://trustee.ietf.org/license-info) in effect on the date of 56 publication of this document. Please review these documents 57 carefully, as they describe your rights and restrictions with 58 respect to this document. Code Components extracted from this 59 document must include Simplified BSD License text as described in 60 Section 4.e of the Trust Legal Provisions and are provided without 61 warranty as described in the Simplified BSD License. 63 Table of Contents 65 1 Introduction.................................................... 3 66 2 Definitions, Acronyms, and Document Summary..................... 3 67 2.1 Definitions ...............................................3 68 2.2 Acronyms ..................................................3 69 2.3 New Semantics .............................................3 70 3 Terminology Mapping............................................. 4 71 4 Negotiation of New Feature Use.................................. 7 72 5 SCSI Commands................................................... 8 73 5.1 SCSI Command Additions ....................................8 74 5.1.1 Command Priority (byte 2) ............................ 8 75 5.2 SCSI Response Additions ...................................9 76 5.2.1 Status Qualifier .................................... 10 77 5.2.2 Data Segment - Sense and Response Data Segment ...... 10 78 6 Task Management Functions...................................... 10 79 6.1 Existing Task Management Functions .......................10 80 6.2 Task Management Function Additions .......................10 81 6.2.1 LUN field ........................................... 12 82 6.2.2 Referenced Task Tag ................................. 12 83 6.2.3 RefCmdSN ............................................ 12 84 6.3 Task Management Function Responses .......................13 85 6.3.1 Task Management Function Response Additions ......... 14 86 6.4 Task Management Requests Affecting Multiple Tasks ........14 87 7 Login/Text Operational Text Keys............................... 15 88 7.1 New Operational Text Keys ................................15 89 7.1.1 iSCSIProtocolLevel .................................. 15 90 8 Security Considerations........................................ 16 91 9 IANA Considerations............................................ 16 92 10 References .................................................. 17 93 11 Acknowledgements ............................................ 18 94 1. Introduction 96 The original [RFC3720] was built based on the SAM-2 model for 97 SCSI. Several new features and capabilities have been added to 98 the SCSI Architecture Model in the intervening years (SAM5 is now 99 the current version of the SCSI Architecture Model). This 100 document is not a complete revision of [RFC3720]. Instead, this 101 document is intended as a companion document to [RFC3720] and 102 [RFC5048]. 104 The text in this document, however, updates and supersedes the 105 text in [RFC3720] and [RFC5048] whenever there is any conflict. 107 2. Definitions, Acronyms, and Document Summary 109 2.1 Definitions 111 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL 112 NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and 113 "OPTIONAL" in this document are to be interpreted as described in 114 [RFC2119]. 116 2.2 Acronyms 118 SAM4 SCSI Architecture Model - 4 119 SAM5 SCSI Architecture Model - 5 120 SAM SAM4 or SAM5 122 2.3 New Semantics 124 This document specifies new iSCSI semantics. This section 125 summarizes the contents of the document. 127 Section 3: The mapping of iSCSI objects to SAM5 objects 128 The iSCSI node may contain both initiator and 129 target capabilities. 131 Section 4: The protocol used to negotiate the use of the new 132 capabilities described in this document. 134 Section 5: New Command operations 135 The PRI field for SCSI command priority has been 136 added to the SCSI command PDU (see 5.1.1). 137 The Status Qualifier field has been added to the 138 SCSI response PDU (see 5.2.1). 139 Sense data may be returned (via autosense) for any 140 SCSI status, not just CHECK CONDITION (see 5.2.2). 142 Section 6: New Task Management Functions 143 Four new task management functions (QUERY TASK, 144 QUERY TASK SET, I_T NEXUS RESET, and QUERY 145 ASYNCHRONOUS EVENT have been added (see 6.2). 146 A new "function succeeded" response has been added 147 (see 6.3.1). 149 Section 7: New Negotiation key 150 A new negotiation key has been added to enable the 151 use of the new features in section 5 and section 152 6. 154 3. Terminology Mapping 156 The iSCSI model (defined in [RFC3720]) uses different terminology 157 than the SCSI Architecture Model. In some cases, iSCSI uses 158 multiple terms to describe what in the SCSI Architecture Model is 159 described with a single term. The iSCSI terms and SAM terms are 160 not necessarily equivalent, but rather, the iSCSI terms represent 161 examples of the objects or classes described in SAM as follows: 163 +-----------------------------+---------------------------+ 164 | RFCxxx Terminology | SAM Terminology | 165 +-----------------------------+---------------------------+ 166 | Network Entity | none | 167 +-----------------------------+---------------------------+ 168 | iSCSI Node | SCSI Device | 169 +-----------------------------+---------------------------+ 170 | iSCSI Name | SCSI Device Name | 171 +-----------------------------+---------------------------+ 172 | iSCSI Node Name | SCSI Device Name | 173 +-----------------------------+---------------------------+ 174 | iSCSI Initiator Node | SCSI Initiator Device | 175 +-----------------------------+---------------------------+ 176 | iSCSI Initiator Name | SCSI Device Name | 177 +-----------------------------+---------------------------+ 178 | iSCSI Initiator Port Name | SCSI Initiator Port Name | 179 | iSCSI Node Name + ',i,' + | | 180 | ISID | | 181 +-----------------------------+---------------------------+ 182 | iSCSI Target Node | SCSI Target Device | 183 +-----------------------------+---------------------------+ 184 | iSCSI Target Name | SCSI Device Name | 185 +-----------------------------+---------------------------+ 186 | iSCSI Target Port Name | SCSI Target Port Name | 187 | iSCSI Node Name + ',t,' + | | 188 | Target Portal Group Tag | | 189 +-----------------------------+---------------------------+ 190 | iSCSI Target Portal Group | SCSI Target Port | 191 +-----------------------------+---------------------------+ 192 | iSCSI Initiator Node + | SCSI Initiator Port | 193 | active ISID | | 194 +-----------------------------+---------------------------+ 195 | iSCSI Initiator Name + | I_T Nexus | 196 | ',i,' + ISID, iSCSI Target | | 197 | Name + ',t,' + Portal | | 198 | Group Tag | | 199 +-----------------------------+---------------------------+ 200 | Target Portal Group Tag | Relative Port ID | 201 +-----------------------------+---------------------------+ 203 -------------------------------------------------------- 204 RFC EDITORS NOTE: The above reference (in row 1) to [RFCxxx] 205 should reference this RFC, and this note should be removed. 206 -------------------------------------------------------- 208 The following diagram shows an example of a combination target 209 device and initiator device. Such a configuration may exist in a 210 target device that implements a SCSI Copy Manager. This example 211 shows how a session that shares Network Portals within a Portal 212 Group may be established (see Target Portal Group 1). In 213 addition, this example shows the Initiator using a different 214 Portal Group than the Target Portal Group, but the Initiator 215 Portal group sharing Network Portal A with the Target Portal 216 Group. 218 ----------------------------IP Network--------------------- 219 | | | 220 +----|---------------|-------+ +----|------------+ 221 | +----------+ +----------+ | | +----------+ | 222 | | Network | | Network | | | | Network | | 223 | | Portal A | | Portal B | | | | Portal A | | 224 | +----------+ +----------+ | | +----------+ | 225 | | Target | | | | Initiator | 226 | | Portal | | | | Portal | 227 | | Group 1 | | | | Group 2 | 228 +----|---------------|-------+ +----|------------+ 229 | | | 230 +----------|---------------|--------------------|--------------------+ 231 | +--------|---------------|----+ +-------------|------------------+ | 232 | |+-------|---------------|---+| |+------------|-----------------+| | 233 | ||iSCSI Session (Target side)|| ||iSCSI Session (Initiator side)|| | 234 | || || || || | 235 | || (TSIH = 56) || || (SSID = 48) || | 236 | |+---------------------------+| |+------------------------------+| | 237 | | | | | | 238 | | iSCSI Target Node | | iSCSI Initiator Node | | 239 | +-----------------------------+ +--------------------------------+ | 240 | iSCSI Node | 241 | (within Network Entity, not shown) | 242 +--------------------------------------------------------------------+ 243 4. Negotiation of New Feature Use 245 The iSCSIProtocolLevel operational text key (see 7.1.1) 246 containing a value of "2" or higher MUST be negotiated to enable 247 the use of features described in this RFC. 249 Note that an operational value of "2" or higher for this key on 250 an iSCSI session does not influence the SCSI level features in 251 any way on that I_T nexus. An operational value of "2" or higher 252 for this key permits the iSCSI-related features defined in this 253 document to be used on all connections on this iSCSI session. 254 SCSI level hand-shakes (e.g. commands, mode pages) eventually 255 determine the existence or lack of various SAM features available 256 for the I_T nexus between the two SCSI end points). To 257 summarize, negotiation of this key to "2" or higher is a 258 necessary but not a sufficient condition of SAM-4 compliant 259 feature usage at the SCSI protocol level. 261 For example, an iSCSI implementation may negotiate this new key 262 to "2" but respond to the new task management functions (see 6.2) 263 with a "Task management function not supported" (which indicates 264 a SCSI error that prevents the function from being performed). 265 In contrast, if the key is negotiated to "2", an iSCSI 266 implementation MUST NOT reject a task management function request 267 PDU that requests one of the new task management functions (such 268 a reject would report an iSCSI protocol error). 270 5. SCSI Commands 272 5.1 SCSI Command Additions 274 The format of the SCSI Command PDU is: 276 Byte/ 0 | 1 | 2 | 3 | 277 / | | | | 278 |0 1 2 3 4 5 6 7|0 1 2 3 4 5 6 7|0 1 2 3 4 5 6 7|0 1 2 3 4 5 6 7| 279 +---------------+---------------+---------------+---------------+ 280 0|.|I| 0x01 |F|R|W|. .|ATTR | PRI | Reserved | 281 +---------------+---------------+---------------+---------------+ 282 4|TotalAHSLength | DataSegmentLength | 283 +---------------+---------------+---------------+---------------+ 284 8| Logical Unit Number (LUN) | 285 + + 286 12| | 287 +---------------+---------------+---------------+---------------+ 288 16| Initiator Task Tag | 289 +---------------+---------------+---------------+---------------+ 290 20| Expected Data Transfer Length | 291 +---------------+---------------+---------------+---------------+ 292 24| CmdSN | 293 +---------------+---------------+---------------+---------------+ 294 28| ExpStatSN | 295 +---------------+---------------+---------------+---------------+ 296 32/ SCSI Command Descriptor Block (CDB) / 297 +/ / 298 +---------------+---------------+---------------+---------------+ 299 48/ AHS (Optional) / 300 +---------------+---------------+---------------+---------------+ 301 x/ Header Digest (Optional) / 302 +---------------+---------------+---------------+---------------+ 303 y/ (DataSegment, Command Data) (Optional) / 304 +/ / 305 +---------------+---------------+---------------+---------------+ 306 z/ Data Digest (Optional) / 307 +---------------+---------------+---------------+---------------+ 309 5.1.1 Command Priority (byte 2) 311 The Command Priority (PRI) specifies the relative scheduling 312 importance of this task in relation to other SIMPLE tasks already 313 in the task set (see [SAM4]). 315 Section 10, iSCSI PDU Formats of [RFC3720], requires that senders 316 set this field to zero. A sender MUST NOT set this field to a 317 value other than zero unless the iSCSIProtocolLevel text key 319 defined in section 7.1.1 has been negotiated on the session with 320 a value of "2" or higher. 322 This field MUST be ignored by iSCSI targets unless the 323 iSCSIProtocolLevel text key with a value of "2" or higher as 324 defined in section 7.1.1 was negotiated on the session. 326 5.2 SCSI Response Additions 328 The format of the SCSI Response PDU is: 330 Byte/ 0 | 1 | 2 | 3 | 331 / | | | | 332 |0 1 2 3 4 5 6 7|0 1 2 3 4 5 6 7|0 1 2 3 4 5 6 7|0 1 2 3 4 5 6 7| 333 +---------------+---------------+---------------+---------------+ 334 0|.|.| 0x21 |1|. .|o|u|O|U|.| Response | Status | 335 +---------------+---------------+---------------+---------------+ 336 4|TotalAHSLength | DataSegmentLength | 337 +---------------+---------------+---------------+---------------+ 338 8| Status Qualifier | Reserved | 339 +---------------+---------------+---------------+---------------+ 340 12| Reserved | 341 +---------------+---------------+---------------+---------------+ 342 16| Initiator Task Tag | 343 +---------------+---------------+---------------+---------------+ 344 20| SNACK Tag or Reserved | 345 +---------------+---------------+---------------+---------------+ 346 24| StatSN | 347 +---------------+---------------+---------------+---------------+ 348 28| ExpCmdSN | 349 +---------------+---------------+---------------+---------------+ 350 32| MaxCmdSN | 351 +---------------+---------------+---------------+---------------+ 352 36| ExpDataSN or Reserved | 353 +---------------+---------------+---------------+---------------+ 354 40| Bidirectional Read Residual Count or Reserved | 355 +---------------+---------------+---------------+---------------+ 356 44| Residual Count or Reserved | 357 +---------------+---------------+---------------+---------------+ 358 48| Header-Digest (Optional) | 359 +---------------+---------------+---------------+---------------+ 360 / Data Segment (Optional) / 361 +/ / 362 +---------------+---------------+---------------+---------------+ 363 | Data-Digest (Optional) | 364 +---------------+---------------+---------------+---------------+ 366 5.2.1 Status Qualifier 368 The Status Qualifier provides additional status information (see 369 [SAM4]). 371 As defined in Section 10, iSCSI PDU Formats of [RFC3720], 372 compliant senders already set this field to zero. Compliant 373 senders MUST NOT set this field to a value other than zero unless 374 the iSCSIProtocolLevel text key with a value of "2" or higher as 375 defined in section 7.1.1 was negotiated on the session. 377 This field MUST be ignored by receivers unless the 378 iSCSIProtocolLevel text key with a value of "2" or higher as 379 defined in section 7.1.1 was negotiated on the session. 381 5.2.2 Data Segment - Sense and Response Data Segment 383 Section 10.4.7 of [RFC3720] specifies that iSCSI targets MUST 384 support and enable autosense. If Status is CHECK CONDITION 385 (0x02), then the Data Segment MUST contain sense data for the 386 failed command. While [RFC3720] does not make any statements 387 about the state of the Data Segment when the Status is not CHECK 388 CONDITION (0x02)(i.e., the Data Segment is not prohibited from 389 containing sense data when the Status is not CHECK CONDITION), 390 negotiation of the iSCSIProtocolLevel text key with a value of 391 "2" or higher as defined in section 7.1.1 explicitly indicates 392 that the Data Segment MAY contain sense data at any time, no 393 matter what value is set in the Status field. 395 6. Task Management Functions 397 6.1 Existing Task Management Functions 399 Section 10.5 of [RFC3720] defines the semantics used to request 400 SCSI Task Management Functions be performed. The following task 401 management functions are defined: 403 1 - ABORT TASK 404 2 - ABORT TASK SET 405 3 - CLEAR ACA 406 4 - CLEAR TASK SET 407 5 - LOGICAL UNIT RESET 408 6 - TARGET WARM RESET 409 7 - TARGET COLD RESET 410 8 - TASK REASSIGN 412 6.2 Task Management Function Additions 413 Additional task Management function codes are listed below. For 414 a more detailed description of SCSI task management, see [SAM5]. 416 9 - QUERY TASK - determines if the task identified by the 417 Referenced Task Tag field is present in the task set. 419 10 - QUERY TASK SET - determine if any task is present in the 420 task set. 422 11 - I_T NEXUS RESET - perform an I_T nexus loss function for 423 the I_T nexus of each logical unit accessible through the I_T 424 Nexus on which the task management function was received. 426 12 - QUERY ASYNCHRONOUS EVENT - determine if there is a unit 427 attention condition or a deferred error pending for the I_T_L 428 nexus on which the task management function was received. 430 These task management function requests MUST NOT be sent unless 431 the iSCSIProtocolLevel text key with a value of "2" or higher as 432 defined in section 7.1.1 was negotiated on the session. 434 Any compliant initiator that sends any of the new task management 435 functions defined in this section MUST also support all new task 436 management function responses (see 6.3.1). 438 For all of the task management functions detailed in this 439 section, the Task Management function response MUST be returned 440 as detailed in section 6.3 Task Management Function Response. 442 The iSCSI target MUST ensure that no responses for the tasks 443 covered by a task management function are sent to the iSCSI 444 initiator after the Task Management response except for a task 445 covered by a TASK REASSIGN, QUERY TASK, or QUERY TASK SET. 447 If a QUERY TASK is issued for a task created by an immediate 448 command then RefCmdSN MUST be that of the Task Management request 449 itself (i.e., CmdSN and RefCmdSN are equal); otherwise RefCmdSN 450 MUST be set to the CmdSN of the task to be queried (lower than 451 CmdSN). 453 At the target a QUERY TASK function MUST NOT be executed on a 454 Task Management request; such a request MUST result in Task 455 Management response of "Function rejected". 457 For the I_T NEXUS RESET function, the target device MUST respond 458 to the function as defined in [SAM4]. Each logical unit 459 accessible via the receiving I_T NEXUS MUST behave as dictated by 460 the I_T nexus loss function in [SAM4] for the I_T nexus on which 461 the task management function was received. The target device 462 MUST drop all connections in the session over which this function 464 is recevied. Independent of the DefaultTime2Wait and 465 DefaultTime2Retain value applicable to the session over which 466 this function is received, the target device MUST consider each 467 participating connection in the session to have immediately timed 468 out, leading to FREE state. The resulting timeouts cause the 469 session timeout event defined in [RFC3720], which in turn 470 triggers the I_T nexus loss notification to the SCSI layer as 471 described in [RFC3720]. 473 6.2.1 LUN field 475 This field is required for functions that address a specific LU 476 (i.e., ABORT TASK, CLEAR TASK SET, ABORT TASK SET, CLEAR ACA, 477 LOGICAL UNIT RESET, QUERY TASK, QUERY TASK SET, and QUERY 478 ASYNCHRONOUS EVENT) and is reserved in all others. 480 6.2.2 Referenced Task Tag 482 The Initiator Task Tag of the task to be aborted for the ABORT 483 TASK function, reassigned for the TASK REASSIGN function, or 484 queried for the QUERY TASK function. For all other functions 485 this field MUST be set to the reserved value 0xffffffff. 487 6.2.3 RefCmdSN 489 If a QUERY TASK is issued for a task created by an immediate 490 command then RefCmdSN MUST be that of the Task Management request 491 itself (i.e., CmdSN and RefCmdSN are equal). 493 For a QUERY TASK of a task created by non-immediate command 494 RefCmdSN MUST be set to the CmdSN of the task identified by the 495 Referenced Task Tag field. Targets must use this field as 496 described in section 10.6.1 of [RFC3720] when the task identified 497 by the Referenced Task Tag field is not in the task set. 499 6.3 Task Management Function Responses 501 Byte/ 0 | 1 | 2 | 3 | 502 / | | | | 503 |0 1 2 3 4 5 6 7|0 1 2 3 4 5 6 7|0 1 2 3 4 5 6 7|0 1 2 3 4 5 6 7| 504 +---------------+---------------+---------------+---------------+ 505 0|.|.| 0x22 |1| Reserved | Response | Reserved | 506 +---------------+---------------+---------------+---------------+ 507 4|TotalAHSLength | DataSegmentLength | 508 +-----------------------------------------------+---------------+ 509 8| Additional Response Information | Reserved | 510 +-----------------------------------------------+---------------+ 511 12| Reserved | 512 +---------------+---------------+---------------+---------------+ 513 16| Initiator Task Tag | 514 +---------------+---------------+---------------+---------------+ 515 20| Reserved | 516 +---------------+---------------+---------------+---------------+ 517 24| StatSN | 518 +---------------+---------------+---------------+---------------+ 519 28| ExpCmdSN | 520 +---------------+---------------+---------------+---------------+ 521 32| MaxCmdSN | 522 +---------------+---------------+---------------+---------------+ 523 36/ Reserved / 524 +/ / 525 +---------------+---------------+---------------+---------------+ 526 48| Header-Digest (Optional) | 527 +---------------+---------------+---------------+---------------+ 529 Section 10.6 of [RFC3720] defines the semantics used for 530 responses to SCSI Task Management Functions. The following 531 responses are defined in [RFC3720]: 533 0 - Function Complete. 534 1 - Task does not exist. 535 2 - LUN does not exist. 536 3 - Task still allegiant. 537 4 - Task allegiance reassignment not supported. 538 5 - Task management function not supported. 539 6 - Function authorization failed. 540 255 - Function rejected. 542 Responses to new task management functions (see 6.3.1) are listed 543 below. In addition, a new task Management response is listed 544 below. For a more detailed description of SCSI task management 545 responses, see [SAM5]. 547 For the functions QUERY TASK, QUERY TASK SET, I_T NEXUS RESET, 548 and QUERY ASYNCHRONOUS EVENT, the target performs the requested 549 Task Management function and sends a Task Management response 550 back to the initiator. 552 6.3.1 Task Management Function Response Additions 554 The new response is listed below: 556 7 - Function succeeded. 558 In symbolic terms Response value 7 maps to the SCSI service 559 response of FUNCTION SUCCEEDED. 561 The task management function response of function succeeded MUST 562 be supported by an initiator that sends any of the new task 563 management functions (see 6.2). 565 For the QUERY TASK function, if the specified task is in the task 566 set, then the target returns a Response value of Function 567 succeeded and additional response information is returned as 568 specified in [SAM5]. If the specified task is not in the task 569 set, then the target returns a Response value of Function 570 complete. 572 For the QUERY TASK SET function, if there is any command present 573 in the task set from the specified I_T_L nexus, then the target 574 returns a Response value of Function succeeded. If there are no 575 commands present in the task set from the specified I_T_L nexus, 576 then the target returns a Response value of Function complete. 578 For the I_T NEXUS RESET function, after completion of the events 579 described in section 6.2 for this function, the target returns a 580 Response value of Function complete. However, because the target 581 drops all connections, the Service Response (defined by [SAM4]) 582 for this SCSI task management function may not be reliably 583 delivered to the issuing initiator port. 585 For the QUERY ASYNCHRONOUS EVENT, if there is a unit attention 586 condition or deferred error pending for the specified I_T_L 587 nexus, then the target returns a Response value of Function 588 succeeded and additional response information is returned as 589 specified in [SAM5]. If there is no unit attention or deferred 590 error pending for the specified I_T_L nexus then the target 591 returns a Response value of Function complete. 593 6.4 Task Management Requests Affecting Multiple Tasks 595 Section 4.1 of [RFC5048] defines the notion of "affected tasks" 596 in multi-task abort scenarios. This section adds to the list 597 include in that section by defining the tasks affected by the I_T 598 NEXUS RESET function. 600 I_T NEXUS RESET: All outstanding tasks received on the I_T 601 nexus on which the function request was received for all 602 logical units accessible to the I_T nexus. 604 Section 4.1.2 of [RFC5048] and section 4.1.3 of [RFC5048] 605 identify semantics for task management functions that involve 606 multi-task abort operations. If an iSCSI implementation supports 607 the I_T NEXUS RESET function, it MUST also support the protocol 608 behavior as defined in those sections and follow the sequence of 609 actions as described in those sections when processing the I_T 610 NEXUS RESET function. 612 7. Login/Text Operational Text Keys 614 7.1 New Operational Text Keys 616 7.1.1 iSCSIProtocolLevel 618 Use: LO 619 Irrelevant when: SessionType = Discovery 620 Senders: Initiator and Target 621 Scope: SW 623 iSCSIProtocolLevel= 625 Default is 1. 626 Result function is Minimum. 628 This key is used to negotiate the use of iSCSI features that 629 require different levels of protocol support for proper 630 operation. This key is negotiated on the iSCSI session once the 631 session is in full feature phase. 633 Negotiation of the iSCSIProtocolLevel key to a value claimed by 634 an RFC indicates that both negotiating parties are compliant to 635 the RFC in question, and agree to support the corresponding 636 semantics on that iSCSI session. An operational value of iSCSI 637 ProtocolLevel = "x" on an iSCSI session requires that the iSCSI 638 protocol semantics on that iSCSI session be a logical superset of 639 the capabilities in all RFCs that have claimed values of an 640 iSCSIProtocolLevel less than "x". 642 An iSCSIProtocolLevel key negotiated to "2" or higher is required 643 to enable use of features defined in this RFC. 645 If the negotiation answer is ignored by the acceptor, or the 646 answer from the remote iSCSI end point is key=NotUnderstood, then 647 the features defined in this RFC, and the features defined in any 648 RFC requiring a key value greater than "2" MUST NOT be used. 650 8. Security Considerations 652 At the time of writing this document does not introduce any new 653 security considerations other than those described in [RFC3720]. 654 Consequently, all the iSCSI-related security text in [RFC3723] is 655 also directly applicable to this document. 657 9. IANA Considerations 659 This document modifies or creates a number of iSCSI-related 660 registries. The following iSCSI-related registries are modified: 662 1. iSCSI Task Management Functions Codes 664 Name of the existing registry: "iSCSI TMF Codes" 666 Additional entries: 668 9, QUERY TASK, [RFCxxx] 670 10, QUERY TASK SET, [RFCxxx] 672 11, I_T NEXUS RESET, [RFCxxx] 674 12, QUERY ASYNCHRONOUS EVENT, [RFCxxx] 676 --------------------------------------------------------- 677 RFC EDITORS NOTE: The above reference to [RFCxxx] should 678 reference this RFC, and this note should be removed. 679 --------------------------------------------------------- 681 2. iSCSI Login/Text Keys 683 Name of the existing registry: "iSCSI Text Keys" 685 Additional entry: 687 iSCSIProtocolLevel = "2", [RFCxxx] 688 --------------------------------------------------------- 689 RFC EDITORS NOTE: The above references to [RFCxxx] should 690 reference this RFC, and this note should be removed. 691 --------------------------------------------------------- 693 This document creates the following iSCSI-related registries for 694 IANA to manage. 696 3. iSCSI Task Management Response Codes 697 Name of new registry: "iSCSI TMF Response Codes" 699 Namespace details: Numerical values that can fit in 8 bits. 701 Information that must be provided to assign a new value: An 702 IESG-approved specification defining the semantics and 703 interoperability requirements of the proposed new value and 704 the fields to be recorded in the registry. 706 Assignment policy: 708 If the requested value is not already assigned, it may be 709 assigned to the requester. 711 8-254: Range reserved by iANA for assignment in this registry. 713 Fields to record in the registry: Assigned value, Operation 714 Name, and its associated RFC reference. 716 0x0, Function complete, [RFC3720] 718 0x1, Task does not exist, [RFC3720] 720 0x2, LUN does not exist, [RFC3720] 722 0x3, Task still allegiant, [RFC3720] 724 0x4, Task allegiance reassignment not supported, [RFC3720] 726 0x5, Task management function not supported, [RFC3720] 728 0x6, Function authorization failed, [RFC3720] 730 0x7, Function succeeded, [RFCxxx] 732 255, Function rejected, [RFC3720] 734 ------------------------------------------------------------ 735 RFC EDITORS NOTE: The above reference to [RFCxxx] should 736 reference this RFC, and this note should be removed. 737 ------------------------------------------------------------ 739 Allocation Policy: 741 Standards Action ([IANA]) 743 10. References 745 10.1 Normative References 747 [RFC2119] Bradner, S. "Key Words for use in RFCs to Indicate 748 Requirement Levels", BCP 14, RFC 2119, March 1997. 750 [RFC3720] Satran, J., Meth, K., Sapuntzakis, C., Chadalapaka, 751 M., and E. Zeidner, "Internet Small Computer Systems 752 Interface (iSCSI)", RFC 3720, April 2004. 754 [RFC3723] Aboba, B., Tseng, J., Walker, J., Rangan, V., and 755 Travostino, F., "Securing Block Storage Protocols 756 over IP", RFC 3723, April 2004. 758 [RFC5048] Chadalapaka, M., "Internet Small Computer System 759 Interface (iSCSI) Corrections and Clarifications", 760 RFC 5048, October 2007. 762 [IANA] Narten, T. and H. Alvestrand, "Guidelines for Writing 763 an IANA Considerations Section in RFCs", BCP 26, RFC 764 5226,May 2008. 766 [SAM2] T10/1157D, SCSI Architecture Model - 2 (SAM-2). 768 [SAM4] ISO/IEC 14776-414, SCSI Architecture Model - 4 (SAM- 769 4). 771 [SAM5] T10/2104D rev r05, SCSI Architecture Model - 5 (SAM- 772 5), Committee Draft. 774 10.2 Additional Reference Sources 776 For more information on the SCSI Architecture Model, contact the 777 T10 group at http://www.t10.org. 779 11. Acknowledgements 781 The Storage Maintenance (STORM) Working Group in the Transport 782 Area of the IETF has been responsible for defining these 783 additions to the iSCSI protocol (apart from other relevant IP 784 Storage protocols). The editor acknowledges the contributions of 785 the entire working group. 787 The following individuals directly contributed to identifying 788 [RFCxxx] issues and/or suggesting resolutions to the issues 789 clarified in this document: David Black, Rob Elliott. This 790 document benefited from all of these contributions. 791 ------------------------------------------------------------ 792 RFC EDITORS NOTE: The above reference to [RFCxxx] should 793 reference this RFC, and this note should be removed. 794 ------------------------------------------------------------ 796 Editor's Addresses 797 Frederick Knight 798 7301 Kit Creek Road 799 P.O. Box 13917 800 Research Triangle Park, NC 27709, USA 801 Phone: +1-919-476-5362 802 Email: knight@netapp.com 804 Mallikarjun Chadalapaka 805 Hewlett-Packard Company 806 8000 Foothills Blvd. 807 Roseville, CA 95747-5668, USA 808 Phone: +1-916-785-5621 809 EMail: cbm@rose.hp.com