draft-ietf-storm-iscsi-sam-05.txt   draft-ietf-storm-iscsi-sam-06.txt 
Storage Maintenance (StorM) Working Group Frederick Knight Storage Maintenance (StorM) Working Group Frederick Knight
Internet Draft NetApp Internet Draft NetApp
Intended status: Standards Track M. Chadalapaka Intended status: Standards Track M. Chadalapaka
Expires: June 2012 Microsoft Expires: January 2013 Microsoft
December 2011 July 2012
Internet Small Computer Systems Interface (iSCSI) SCSI Features Internet Small Computer Systems Interface (iSCSI) SCSI Features
Update Update
draft-ietf-storm-iscsi-sam-05.txt draft-ietf-storm-iscsi-sam-06.txt
Abstract Abstract
Internet Small Computer Systems Interface (iSCSI) is a SCSI Internet Small Computer Systems Interface (iSCSI) is a SCSI
transport protocol that maps the SCSI family of protocols onto transport protocol that maps the SCSI family of protocols onto
TCP/IP. The iSCSI protocol as specified in [draft-ietf-storm- TCP/IP. The iSCSI protocol as specified in [draft-ietf-storm-
iscsi-cons-xx] (and as previously specified by the combination iscsi-cons-xx] (and as previously specified by the combination
of RFC 3720 and RFC 5048) is based on the SAM-2 (SCSI of RFC 3720 and RFC 5048) is based on the SAM-2 (SCSI
Architecture Model - 2) version of the SCSI family of Architecture Model - 2) version of the SCSI family of
protocols. This document defines enhancements to the iSCSI protocols. This document defines enhancements to the iSCSI
skipping to change at page 1, line 55 skipping to change at page 1, line 55
documents at any time. It is inappropriate to use Internet- documents at any time. It is inappropriate to use Internet-
Drafts as reference material or to cite them other than as "work Drafts as reference material or to cite them other than as "work
in progress." in 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/1id-abstracts.html. http://www.ietf.org/1id-abstracts.html.
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.
This Internet-Draft will expire June, 2012. This Internet-Draft will expire January, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described in document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided Section 4.e of the Trust Legal Provisions and are provided
skipping to change at page 3, line 6 skipping to change at page 3, line 6
6.4 Task Management Requests Affecting Multiple Tasks ..... 14 6.4 Task Management Requests Affecting Multiple Tasks ..... 14
7. Login/Text Operational Text Keys.............................. 15 7. Login/Text Operational Text Keys.............................. 15
7.1 New Operational Text Keys ............................. 15 7.1 New Operational Text Keys ............................. 15
7.1.1 iSCSIProtocolLevel ................................ 15 7.1.1 iSCSIProtocolLevel ................................ 15
8. Security Considerations....................................... 16 8. Security Considerations....................................... 16
9. IANA Considerations........................................... 16 9. IANA Considerations........................................... 16
10. References................................................... 18 10. References................................................... 18
11. Acknowledgements............................................. 19 11. Acknowledgements............................................. 19
1. Introduction 1. Introduction
The original [RFC3720] was built based on the [SAM2] model for The original iSCSI protocol [RFC3720] was built based on the
SCSI. Several new features and capabilities have been added to [SAM2] model for SCSI. Several new features and capabilities
the SCSI Architecture Model in the intervening years (at the time have been added to the SCSI Architecture Model in the intervening
of publication of this document, SAM-5 was the current version of years (at the time of publication of this document, SAM-5 was the
the SCSI Architecture Model). This document is not a complete current version of the SCSI Architecture Model). This document
revision of [RFC3720]. Instead, this document is intended as a is not a complete revision of [RFC3720]. Instead, this document
companion document to [draft-ietf-storm-iscsi-cons-xx]; this is intended as a companion document to [draft-ietf-storm-iscsi-
document may also be used as a companion document to the cons-xx]; this document may also be used as a companion document
combination of [RFC3720] and [RFC5048], although both of those to the combination of [RFC3720] and [RFC5048], although both of
RFCs have been obsolete by [draft-ietf-storm-iscsi-cons-xx]. those RFCs have been obsolete by [draft-ietf-storm-iscsi-cons-
xx].
-------------------------------------------------------- --------------------------------------------------------
RFC EDITORS NOTE: The above references to [draft-ietf-storm- RFC EDITORS NOTE: The above references to [draft-ietf-storm-
iscsi-cons-xx] should reference the RFC number assigned to iscsi-cons-xx] should reference the RFC number assigned to
that document, and this note should be removed. that document, and this note should be removed.
-------------------------------------------------------- --------------------------------------------------------
2. Definitions, Acronyms, and Document Summary 2. Definitions, Acronyms, and Document Summary
2.1 Definitions 2.1 Definitions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
in this document are to be interpreted as described in [RFC2119]. in this document are to be interpreted as described in
[RFC2119].
2.2 Acronyms 2.2 Acronyms
ISID Initiator Session Identifier ISID Initiator Session Identifier
LU Logical Unit LU Logical Unit
PDU Protocol Data Unit PDU Protocol Data Unit
SAM-4 SCSI Architecture Model - 4 (see [SAM4]) SAM-4 SCSI Architecture Model - 4 (see [SAM4])
SAM-5 SCSI Architecture Model - 5 (see [SAM5]) SAM-5 SCSI Architecture Model - 5 (see [SAM5])
TMF Task Management Function TMF Task Management Function
skipping to change at page 3, line 53 skipping to change at page 4, line 4
summarizes the contents of the document. summarizes the contents of the document.
Section 3: The mapping of iSCSI objects to SAM-5 objects Section 3: The mapping of iSCSI objects to SAM-5 objects
The iSCSI node may contain both initiator and The iSCSI node may contain both initiator and
target capabilities. target capabilities.
Section 4: The protocol used to negotiate the use of the new Section 4: The protocol used to negotiate the use of the new
capabilities described in this document. capabilities described in this document.
Section 5: New Command operations Section 5: New Command operations
The PRI field for SCSI command priority has been The PRI field for SCSI command priority has been
added to the SCSI command PDU (see 5.1.1). added to the SCSI command PDU (see 5.1.1).
The Status Qualifier field has been added to the The Status Qualifier field has been added to the
SCSI response PDU (see 5.2.1). SCSI response PDU (see 5.2.1).
Sense data may be returned (via autosense) for any Sense data may be returned (via autosense) for any
SCSI status, not just CHECK CONDITION (see 5.2.2). SCSI status, not just CHECK CONDITION (see 5.2.2).
Section 6: New Task Management Functions Section 6: New Task Management Functions
Four new task management functions (QUERY TASK, Four new task management functions (QUERY TASK,
QUERY TASK SET, I_T NEXUS RESET, and QUERY QUERY TASK SET, I_T NEXUS RESET, and QUERY
ASYNCHRONOUS EVENT have been added (see 6.2). ASYNCHRONOUS EVENT have been added (see 6.2).
A new "function succeeded" response has been added A new "function succeeded" response has been added
(see 6.3.1). (see 6.3.1).
Section 7: New Negotiation key Section 7: New Negotiation key
A new negotiation key has been added to enable the A new negotiation key has been added to enable the
use of the new features in section 5 and section 6. use of the new features in section 5 and section 6.
3. Terminology Mapping 3. Terminology Mapping
The iSCSI model (defined in [RFC3720]) uses different terminology The iSCSI model (defined in [RFC3720]) uses different terminology
than the SCSI Architecture Model. In some cases, iSCSI uses than the SCSI Architecture Model. In some cases, iSCSI uses
multiple terms to describe what in the SCSI Architecture Model is multiple terms to describe what in the SCSI Architecture Model is
described with a single term. The iSCSI terms and SAM-5 terms described with a single term. The iSCSI terms and SAM-5 terms
are not necessarily equivalent, but rather, the iSCSI terms are not necessarily equivalent, but rather, the iSCSI terms
represent examples of the objects or classes described in SAM-5 represent examples of the objects or classes described in SAM-5
as follows: as follows:
+-----------------------------+---------------------------+ +-----------------------------+---------------------------+
| RFCxxx Terminology | SAM-5 Terminology | | RFCxxx Terminology | SAM-5 Terminology |
+-----------------------------+---------------------------+ +-----------------------------+---------------------------+
| Network Entity | none | | Network Entity | none |
+-----------------------------+---------------------------+ +-----------------------------+---------------------------+
| iSCSI Node | SCSI Device | | iSCSI Node | SCSI Device |
+-----------------------------+---------------------------+ +-----------------------------+---------------------------+
| iSCSI Name | SCSI Device Name | | iSCSI Name | SCSI Device Name |
+-----------------------------+---------------------------+ +-----------------------------+---------------------------+
| iSCSI Node Name | SCSI Device Name | | iSCSI Node Name | SCSI Device Name |
+-----------------------------+---------------------------+ +-----------------------------+---------------------------+
| iSCSI Initiator Node | SCSI Initiator Device | | iSCSI Initiator Node | SCSI Initiator Device |
+-----------------------------+---------------------------+ +-----------------------------+---------------------------+
| iSCSI Initiator Name | SCSI Device Name | | iSCSI Initiator Name | SCSI Device Name |
+-----------------------------+---------------------------+ +-----------------------------+---------------------------+
| iSCSI Initiator Port | SCSI Initiator Port | | iSCSI Initiator Port | SCSI Initiator Port |
| Identifier; (i.e., iSCSI | Identifier | | Identifier; (i.e., iSCSI | Identifier |
| Node Name + `,i,' + ISID)*1 | | | Node Name + ,,,i, + ISID)*1| |
+-----------------------------+---------------------------+ +-----------------------------+---------------------------+
| iSCSI Initiator Port Name; | SCSI Initiator Port Name | | iSCSI Initiator Port Name; | SCSI Initiator Port Name |
| (i.e., iSCSI Node Name + | | | (i.e., iSCSI Node Name + | |
| `,i,' + ISID)*1 | | | ,,,i, + ISID)*1 | |
+-----------------------------+---------------------------+ +-----------------------------+---------------------------+
| iSCSI Target Node | SCSI Target Device | | iSCSI Target Node | SCSI Target Device |
+-----------------------------+---------------------------+ +-----------------------------+---------------------------+
| iSCSI Target Name | SCSI Device Name | | iSCSI Target Name | SCSI Device Name |
+-----------------------------+---------------------------+ +-----------------------------+---------------------------+
| iSCSI Target Port | SCSI Target Port | | iSCSI Target Port | SCSI Target Port |
| Identifier; (i.e., iSCSI | Identifier | | Identifier; (i.e., iSCSI | Identifier |
| Node Name + `,t,' + | | | Node Name + ,,,t, + | |
| Target Portal Group Tag)*1 | | | Target Portal Group Tag)*1 | |
+-----------------------------+---------------------------+ +-----------------------------+---------------------------+
| iSCSI Target Port Name; | SCSI Target Port Name | | iSCSI Target Port Name; | SCSI Target Port Name |
| (i.e., iSCSI Node Name + | | | (i.e., iSCSI Node Name + | |
| `,t,' + Target Portal | | | ,,,t, + Target Portal | |
| Group Tag)*1 | | | Group Tag)*1 | |
+-----------------------------+---------------------------+ +-----------------------------+---------------------------+
| iSCSI Target Portal Group | SCSI Target Port | | iSCSI Target Portal Group | SCSI Target Port |
+-----------------------------+---------------------------+ +-----------------------------+---------------------------+
| iSCSI Initiator Name + | I_T Nexus Identifier | | iSCSI Initiator Name + | I_T Nexus Identifier |
| ',i,' + ISID + iSCSI | | | ',i,' + ISID + iSCSI | |
| Target Name + ',t,' + | | | Target Name + ',t,' + | |
| Target Portal Group Tag | | | Target Portal Group Tag | |
+-----------------------------+---------------------------+ +-----------------------------+---------------------------+
| Target Portal Group Tag | Relative Port ID | | Target Portal Group Tag | Relative Port ID |
+-----------------------------+---------------------------+ +-----------------------------+---------------------------+
*1 The text encoding of the ISID value and the Target Portal *1 The text encoding of the ISID value and the Target Portal
Group Tag value includes an initial `0X' or `0x' (see [RFC3720]). Group Tag value includes an initial ,,0X or ,,0x (see [RFC3720]).
-------------------------------------------------------- --------------------------------------------------------
RFC EDITORS NOTE: The above reference (in row 1) to [RFCxxx] RFC EDITORS NOTE: The above reference (in row 1) to [RFCxxx]
should reference this RFC, and this note should be removed. should reference this RFC, and this note should be removed.
-------------------------------------------------------- --------------------------------------------------------
The following diagram shows an example of a combination target The following diagram shows an example of a combination target
device and initiator device. Such a configuration may exist in a device and initiator device. Such a configuration may exist in a
target device that implements a SCSI Copy Manager. This example target device that implements a SCSI Copy Manager. This example
shows how a session that shares Network Portals within a Portal shows how a session that shares Network Portals within a Portal
Group may be established (see Target Portal Group 1). In Group may be established (see Target Portal Group 1). In
addition, this example shows the Initiator using a different addition, this example shows the Initiator using a different
Portal Group than the Target Portal Group, but the Initiator Portal Group than the Target Portal Group, but the Initiator
Portal group sharing Network Portal A with the Target Portal Portal group sharing Network Portal A with the Target Portal
Group. Group.
----------------------------IP Network--------------------- ----------------------------IP Network---------------------
| | | | | |
+----|---------------|-------+ +-----|-----------+ +----|---------------|-------+ +----|------------+
| +----------+ +----------+ | | +----------+ | | +----------+ +----------+ | | +----------+ |
| | Network | | Network | | | | Network | | | | Network | | Network | | | | Network | |
| | Portal A | | Portal B | | | | Portal A | | | | Portal A | | Portal B | | | | Portal A | |
| +----------+ +----------+ | | +----------+ | | +----------+ +----------+ | | +----------+ |
| | Target | | | | Initiator | | | Target | | | | Initiator |
| | Portal | | | | Portal | | | Portal | | | | Portal |
| | Group 1 | | | | Group 2 | | | Group 1 | | | | Group 2 |
+----|---------------|-------+ +-----|-----------+ +----|---------------|-------+ +----|------------+
| | | | | |
+----------|---------------|---------------------|-------------------+ +----------|---------------|--------------------|--------------------+
| +--------|---------------|----+ +--------------|-----------------+ | | +--------|---------------|----+ +-------------|------------------+ |
| |+-------|---------------|---+| |+-------------|----------------+| | | |+-------|---------------|---+| |+------------|-----------------+| |
| ||iSCSI Session (Target side)|| ||iSCSI Session (Initiator side)|| | | ||iSCSI Session (Target side)|| ||iSCSI Session (Initiator side)|| |
| || || || || | | || || || || |
| || (TSIH = 56) || || (SSID = 48) || | | || (TSIH = 56) || || (SSID = 48) || |
| |+---------------------------+| |+------------------------------+| | | |+---------------------------+| |+------------------------------+| |
| | | | | | | | | | | |
| | iSCSI Target Node | | iSCSI Initiator Node | | | | iSCSI Target Node | | iSCSI Initiator Node | |
| +-----------------------------+ +--------------------------------+ | | +-----------------------------+ +--------------------------------+ |
| iSCSI Node | | iSCSI Node |
| (within Network Entity, not shown) | | (within Network Entity, not shown) |
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
4. New Feature Use 4. New Feature Use
4.1 Negotiation of New Feature Use 4.1 Negotiation of New Feature Use
The iSCSIProtocolLevel operational text key (see 7.1.1) The iSCSIProtocolLevel operational text key (see 7.1.1)
containing a value of "2" or higher MUST be negotiated to enable containing a value of "2" or higher MUST be negotiated to enable
the use of features described in this RFC. the use of features described in this RFC.
Note that an operational value of "2" or higher for this key on Note that an operational value of "2" or higher for this key on
skipping to change at page 8, line 11 skipping to change at page 8, line 11
iSCSIProtocolLevel key (for example, if the negotiated iSCSIProtocolLevel key (for example, if the negotiated
iSCSIProtocolLevel=2, then if an iSCSI version descriptor is iSCSIProtocolLevel=2, then if an iSCSI version descriptor is
returned in the standard INQUIRY data it is set to 0962h). returned in the standard INQUIRY data it is set to 0962h).
5. SCSI Commands 5. SCSI Commands
5.1 SCSI Command Additions 5.1 SCSI Command Additions
The format of the SCSI Command PDU is: The format of the SCSI Command PDU is:
Byte/ 0 | 1 | 2 | 3 | Byte/ 0 | 1 | 2 | 3 |
/ | | | | / | | | |
|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| |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|
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
0|.|I| 0x01 |F|R|W|. .|ATTR | PRI | Reserved | 0|.|I| 0x01 |F|R|W|. .|ATTR | PRI | Reserved |
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
4|TotalAHSLength | DataSegmentLength | 4|TotalAHSLength | DataSegmentLength |
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
8| Logical Unit Number (LUN) | 8| Logical Unit Number (LUN) |
+ + + +
12| | 12| |
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
16| Initiator Task Tag | 16| Initiator Task Tag |
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
20| Expected Data Transfer Length | 20| Expected Data Transfer Length |
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
24| CmdSN | 24| CmdSN |
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
28| ExpStatSN | 28| ExpStatSN |
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
32/ SCSI Command Descriptor Block (CDB) / 32/ SCSI Command Descriptor Block (CDB) /
+/ / +/ /
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
48/ AHS (Optional) / 48/ AHS (Optional) /
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
x/ Header Digest (Optional) / x/ Header Digest (Optional) /
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
y/ (DataSegment, Command Data) (Optional) / y/ (DataSegment, Command Data) (Optional) /
+/ / +/ /
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
z/ Data Digest (Optional) / z/ Data Digest (Optional) /
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
5.1.1 Command Priority (byte 2) 5.1.1 Command Priority (byte 2)
The Command Priority (PRI) specifies the relative scheduling The Command Priority (PRI) specifies the relative scheduling
importance of this task in relation to other SIMPLE tasks already importance of this task in relation to other SIMPLE tasks already
in the task set (see [SAM4]). in the task set (see [SAM4]).
Section 10, iSCSI PDU Formats of [RFC3720], requires that senders Section 10, iSCSI PDU Formats of [RFC3720], requires that senders
set this field to zero. A sender MUST NOT set this field to a set this field to zero. A sender MUST NOT set this field to a
value other than zero unless the iSCSIProtocolLevel text key value other than zero unless the iSCSIProtocolLevel text key
skipping to change at page 9, line 13 skipping to change at page 9, line 13
a value of "2" or higher. a value of "2" or higher.
This field MUST be ignored by iSCSI targets unless the This field MUST be ignored by iSCSI targets unless the
iSCSIProtocolLevel text key with a value of "2" or higher as iSCSIProtocolLevel text key with a value of "2" or higher as
defined in section 7.1.1 was negotiated on the session. defined in section 7.1.1 was negotiated on the session.
5.2 SCSI Response Additions 5.2 SCSI Response Additions
The format of the SCSI Response PDU is: The format of the SCSI Response PDU is:
Byte/ 0 | 1 | 2 | 3 | Byte/ 0 | 1 | 2 | 3 |
/ | | | | / | | | |
|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| |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|
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
0|.|.| 0x21 |1|. .|o|u|O|U|.| Response | Status | 0|.|.| 0x21 |1|. .|o|u|O|U|.| Response | Status |
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
4|TotalAHSLength | DataSegmentLength | 4|TotalAHSLength | DataSegmentLength |
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
8| Status Qualifier | Reserved | 8| Status Qualifier | Reserved |
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
12| Reserved | 12| Reserved |
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
skipping to change at page 11, line 16 skipping to change at page 11, line 16
Referenced Task Tag field is present in the task set. Referenced Task Tag field is present in the task set.
10 - QUERY TASK SET - determine if any command is present in 10 - QUERY TASK SET - determine if any command is present in
the task set for the I_T_L Nexus on which the task management the task set for the I_T_L Nexus on which the task management
function was received. function was received.
11 - I_T NEXUS RESET - perform an I_T nexus loss function (see 11 - I_T NEXUS RESET - perform an I_T nexus loss function (see
[SAM5]) for the I_T nexus on which the task management [SAM5]) for the I_T nexus on which the task management
function was received. function was received.
12 - QUERY ASYNCHRONOUS EVENT - determine if there is a unit 12 - QUERY ASYNCHRONOUS EVENT - determine if there is a unit
attention condition or a deferred error pending for the I_T_L attention condition or a deferred error pending for the I_T_L
nexus on which the task management function was received. nexus on which the task management function was received.
These task management function requests MUST NOT be sent unless These task management function requests MUST NOT be sent unless
the iSCSIProtocolLevel text key with a value of "2" or higher as the iSCSIProtocolLevel text key with a value of "2" or higher as
defined in section 7.1.1 was negotiated on the session. defined in section 7.1.1 was negotiated on the session.
Any compliant initiator that sends any of the new task management Any compliant initiator that sends any of the new task management
functions defined in this section MUST also support all new task functions defined in this section MUST also support all new task
management function responses (as specified in section 6.3.1). management function responses (as specified in section 6.3.1).
For all of the task management functions detailed in this For all of the task management functions detailed in this
section, the Task Management function response MUST be returned section, the Task Management function response MUST be returned
as detailed in section 6.3 Task Management Function Response. as detailed in section 6.3 Task Management Function Response.
The iSCSI target MUST ensure that no responses for the commands The iSCSI target MUST ensure that no responses for the commands
covered by a task management function are sent to the iSCSI covered by a task management function are sent to the iSCSI
initiator port after the Task Management response except for a initiator port after the Task Management response except for a
commands covered by a TASK REASSIGN, QUERY TASK, or QUERY TASK commands covered by a TASK REASSIGN, QUERY TASK, or QUERY TASK
SET. SET.
If a QUERY TASK is issued for a task created by an immediate If a QUERY TASK is issued for a task created by an immediate
command then RefCmdSN MUST be that of the Task Management request command then RefCmdSN MUST be that of the Task Management request
itself (i.e., CmdSN and RefCmdSN are equal); otherwise RefCmdSN itself (i.e., CmdSN and RefCmdSN are equal); otherwise RefCmdSN
MUST be set to the CmdSN of the task to be queried (lower than MUST be set to the CmdSN of the task to be queried (lower than
CmdSN). CmdSN).
If the connection is still active (it is not undergoing an If the connection is still active (it is not undergoing an
implicit or explicit logout), QUERY TASK MUST be issued on the implicit or explicit logout), QUERY TASK MUST be issued on the
same connection to which the task to be queried is allegiant at same connection to which the task to be queried is allegiant at
the time the Task Management request is issued. If the the time the Task Management request is issued. If the
connection is implicitly or explicitly logged out (i.e., no other connection is implicitly or explicitly logged out (i.e., no other
request will be issued on the failing connection and no other request will be issued on the failing connection and no other
response will be received on the failing connection), then a response will be received on the failing connection), then a
QUERY TASK function request may be issued on another connection. QUERY TASK function request may be issued on another connection.
This Task Management request will then establish a new allegiance This Task Management request will then establish a new allegiance
for the command being queried. for the command being queried.
At the target a QUERY TASK function MUST NOT be executed on a At the target a QUERY TASK function MUST NOT be executed on a
Task Management request; such a request MUST result in Task Task Management request; such a request MUST result in Task
Management response of "Function rejected". Management response of "Function rejected".
For the I_T NEXUS RESET function, the target device MUST respond For the I_T NEXUS RESET function, the target device MUST respond
to the function as defined in [SAM4]. Each logical unit to the function as defined in [SAM4]. Each logical unit
accessible via the receiving I_T NEXUS MUST behave as dictated by accessible via the receiving I_T NEXUS MUST behave as dictated by
the I_T nexus loss function in [SAM4] for the I_T nexus on which the I_T nexus loss function in [SAM4] for the I_T nexus on which
the task management function was received. The target device the task management function was received. The target device
skipping to change at page 13, line 5 skipping to change at page 13, line 5
If a QUERY TASK is issued for a task created by an immediate If a QUERY TASK is issued for a task created by an immediate
command then RefCmdSN MUST be that of the Task Management request command then RefCmdSN MUST be that of the Task Management request
itself (i.e., CmdSN and RefCmdSN are equal). itself (i.e., CmdSN and RefCmdSN are equal).
For a QUERY TASK of a task created by non-immediate command For a QUERY TASK of a task created by non-immediate command
RefCmdSN MUST be set to the CmdSN of the task identified by the RefCmdSN MUST be set to the CmdSN of the task identified by the
Referenced Task Tag field. Targets must use this field as Referenced Task Tag field. Targets must use this field as
described in section 10.6.1 of [RFC3720] when the task identified described in section 10.6.1 of [RFC3720] when the task identified
by the Referenced Task Tag field is not in the task set. by the Referenced Task Tag field is not in the task set.
6.3 Task Management Function Responses 6.3 Task Management Function Responses
Byte/ 0 | 1 | 2 | 3 | Byte/ 0 | 1 | 2 | 3 |
/ | | | | / | | | |
|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| |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|
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
0|.|.| 0x22 |1| Reserved | Response | Reserved | 0|.|.| 0x22 |1| Reserved | Response | Reserved |
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
4|TotalAHSLength | DataSegmentLength | 4|TotalAHSLength | DataSegmentLength |
+-----------------------------------------------+---------------+ +-----------------------------------------------+---------------+
8| Additional Response Information | Reserved | 8| Additional Response Information | Reserved |
+-----------------------------------------------+---------------+ +-----------------------------------------------+---------------+
12| Reserved | 12| Reserved |
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
skipping to change at page 16, line 19 skipping to change at page 16, line 19
Consequently, all the iSCSI-related security text in [RFC3723] is Consequently, all the iSCSI-related security text in [RFC3723] is
also directly applicable to this document. also directly applicable to this document.
9. IANA Considerations 9. IANA Considerations
This document modifies or creates a number of iSCSI-related This document modifies or creates a number of iSCSI-related
registries. The following iSCSI-related registries are modified: registries. The following iSCSI-related registries are modified:
1. iSCSI Task Management Functions Codes 1. iSCSI Task Management Functions Codes
Name of the existing registry: "iSCSI TMF Codes" Name of the existing registry: "iSCSI TMF Codes"
Additional entries: Additional entries:
9, QUERY TASK, [RFCxxx] 9, QUERY TASK, [RFCxxx]
10, QUERY TASK SET, [RFCxxx] 10, QUERY TASK SET, [RFCxxx]
11, I_T NEXUS RESET, [RFCxxx] 11, I_T NEXUS RESET, [RFCxxx]
12, QUERY ASYNCHRONOUS EVENT, [RFCxxx] 12, QUERY ASYNCHRONOUS EVENT, [RFCxxx]
--------------------------------------------------------- ---------------------------------------------------------
RFC EDITORS NOTE: The above reference to [RFCxxx] should RFC EDITORS NOTE: The above reference to [RFCxxx] should
reference this RFC, and this note should be removed. reference this RFC, and this note should be removed.
--------------------------------------------------------- ---------------------------------------------------------
2. iSCSI Login/Text Keys 2. iSCSI Login/Text Keys
Name of the existing registry: "iSCSI Text Keys" Name of the existing registry: "iSCSI Text Keys"
Fields to record in the registry: Assigned value and its Fields to record in the registry: Assigned value and its
associated RFC reference: associated RFC reference:
iSCSIProtocolLevel, [RFCxxx] iSCSIProtocolLevel, [RFCxxx]
--------------------------------------------------------- ---------------------------------------------------------
RFC EDITORS NOTE: The above references to [RFCxxx] should RFC EDITORS NOTE: The above references to [RFCxxx] should
reference this RFC, and this note should be removed. reference this RFC, and this note should be removed.
--------------------------------------------------------- ---------------------------------------------------------
 End of changes. 29 change blocks. 
172 lines changed or deleted 173 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/