draft-ietf-storm-iscsi-sam-03.txt   draft-ietf-storm-iscsi-sam-04.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: January 2012 Microsoft Expires: February 2012 Microsoft
Updates: 3720, 5048 July 2011 August 2011
Internet Small Computer Systems Interface (iSCSI) SAM Internet Small Computer Systems Interface (iSCSI) SCSI Architecture
draft-ietf-storm-iscsi-sam-03.txt Features Update
draft-ietf-storm-iscsi-sam-04.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. RFC 3720 defines the iSCSI protocol. The current TCP/IP. The iSCSI protocol as specified in [draft-ietf-storm-
iSCSI protocol (RFC 3720 and RFC 5048) is based on the SAM-2 iscsi-cons-xx] (and as previously specified by the combination
version of the SCSI family of protocols). This document of RFC 3720 and RFC 5048) is based on the SAM-2 (SCSI
defines additions and changes to the iSCSI protocol to enabled Architecture Model - 2) version of the SCSI family of
additional features that were added to the SCSI family of protocols. This document defines enhancements to the iSCSI
protocols through SAM-3, SAM-4, and SAM-5. protocol to support certain additional features of the SCSI
protocol that were defined in SAM-3, SAM-4, and SAM-5.
This document updates RFC 3720 and RFC 5048 and the text in This document is a companion document to [draft-ietf-storm-
this document supersedes the text in RFC 3720 and RFC 5048 iscsi-cons-xx].
when the two differ.
--------------------------------------------------------
RFC EDITORS NOTE: The above references to [draft-ietf-storm-
iscsi-cons-xx] should reference the RFC number assigned to
that document, and this note should be removed.
--------------------------------------------------------
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with This Internet-Draft is submitted to IETF in full conformance with
the provisions of BCP 78 and BCP 79. the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 48 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 January, 2012. This Internet-Draft will expire February, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 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
without warranty as described in the Simplified BSD License. without warranty as described in the Simplified BSD License.
Table of Contents Table of Contents
1 Introduction.................................................. 3 1 Introduction.................................................. 3
2 Definitions, Acronyms, and Document Summary................... 3 2 Definitions, Acronyms, and Document Summary................... 3
2.1 Definitions ............................................ 3 2.1 Definitions ............................................ 3
2.2 Acronyms ............................................... 3 2.2 Acronyms ............................................... 3
2.3 New Semantics .......................................... 3 2.3 New Semantics .......................................... 3
3 Terminology Mapping........................................... 4 3 Terminology Mapping........................................... 4
4 Negotiation of New Feature Use................................ 7 4 Negotiation of New Feature Use................................ 7
skipping to change at page 2, line 42 skipping to change at page 2, line 47
6.2 Task Management Function Additions .................... 10 6.2 Task Management Function Additions .................... 10
6.2.1 LUN field ......................................... 12 6.2.1 LUN field ......................................... 12
6.2.2 Referenced Task Tag ............................... 12 6.2.2 Referenced Task Tag ............................... 12
6.2.3 RefCmdSN .......................................... 12 6.2.3 RefCmdSN .......................................... 12
6.3 Task Management Function Responses .................... 13 6.3 Task Management Function Responses .................... 13
6.3.1 Task Management Function Response Additions ....... 14 6.3.1 Task Management Function Response Additions ....... 14
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...................................... 15 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 [RFC3720] was built based on the [SAM2] model for
SCSI. Several new features and capabilities have been added to SCSI. Several new features and capabilities have been added to
the SCSI Architecture Model in the intervening years (SAM5 is now the SCSI Architecture Model in the intervening years (at the time
the current version of the SCSI Architecture Model). This of publication of this document, SAM-5 was the current version of
document is not a complete revision of [RFC3720]. Instead, this the SCSI Architecture Model). This document is not a complete
document is intended as a companion document to [RFC3720] and revision of [RFC3720]. Instead, this document is intended as a
[RFC5048]. companion document to [draft-ietf-storm-iscsi-cons-xx]; this
document may also be used as a companion document to the
combination of [RFC3720] and [RFC5048], although both of those
RFCs have been obsolete by [draft-ietf-storm-iscsi-cons-xx].
The text in this document, however, updates and supersedes the --------------------------------------------------------
text in [RFC3720] and [RFC5048] whenever there is any conflict. RFC EDITORS NOTE: The above references to [draft-ietf-storm-
iscsi-cons-xx] should reference the RFC number assigned to
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 NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
this document are to be interpreted as described in [RFC2119]. this document are to be interpreted as described in [RFC2119].
2.2 Acronyms 2.2 Acronyms
SAM4 SCSI Architecture Model - 4 ISID Initiator Session Identifier
SAM5 SCSI Architecture Model - 5 LU Logical Unit
SAM SAM4 or SAM5 PDU Protocol Data Unit
SAM-4 SCSI Architecture Model - 4 (see [SAM4])
SAM-5 SCSI Architecture Model - 5 (see [SAM5])
TMF Task Management Function
2.3 New Semantics 2.3 New Semantics
This document specifies new iSCSI semantics. This section This document specifies new iSCSI semantics. This section
summarizes the contents of the document. summarizes the contents of the document.
Section 3: The mapping of iSCSI objects to SAM5 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 terms are described with a single term. The iSCSI terms and SAM-5 terms
not necessarily equivalent, but rather, the iSCSI terms represent are not necessarily equivalent, but rather, the iSCSI terms
examples of the objects or classes described in SAM as follows: represent examples of the objects or classes described in SAM-5
as follows:
+-----------------------------+---------------------------+ +-----------------------------+---------------------------+
| RFCxxx Terminology | SAM 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 Name | SCSI Initiator Port Name | | iSCSI Initiator Port Name | SCSI Initiator Port Name |
| iSCSI Node Name + ',i,' + | | | iSCSI Node Name + ',i,' + | |
| ISID | | | ISID | |
+-----------------------------+---------------------------+ +-----------------------------+---------------------------+
| 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 Name | SCSI Target Port Name | | iSCSI Target Port Name | SCSI Target Port Name |
| iSCSI Node Name + ',t,' + | | | iSCSI Node Name + ',t,' + | |
| Target Portal Group Tag | | | Target Portal Group Tag | |
+-----------------------------+---------------------------+ +-----------------------------+---------------------------+
| iSCSI Target Portal Group | SCSI Target Port | | iSCSI Target Portal Group | SCSI Target Port |
+-----------------------------+---------------------------+ +-----------------------------+---------------------------+
| iSCSI Initiator Node + | SCSI Initiator Port | | iSCSI Initiator Node + | SCSI Initiator Port |
| active ISID | | | active ISID | |
+-----------------------------+---------------------------+ +-----------------------------+---------------------------+
| iSCSI Initiator Name + | I_T Nexus | | iSCSI Initiator Name + | I_T Nexus |
| ',i,' + ISID, iSCSI Target | | | ',i,' + ISID, iSCSI Target | |
| Name + ',t,' + Portal | | | Name + ',t,' + Portal | |
| Group Tag | | | Group Tag | |
+-----------------------------+---------------------------+ +-----------------------------+---------------------------+
| Target Portal Group Tag | Relative Port ID | | Target Portal Group Tag | Relative Port ID |
+-----------------------------+---------------------------+ +-----------------------------+---------------------------+
-------------------------------------------------------- --------------------------------------------------------
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.
-------------------------------------------------------- --------------------------------------------------------
skipping to change at page 6, line 32 skipping to change at page 6, line 32
| | 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. Negotiation of New Feature Use 4. 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
an iSCSI session does not influence the SCSI level features in an iSCSI session does not influence the SCSI level features in
any way on that I_T nexus. An operational value of "2" or higher any way on that I_T nexus. An operational value of "2" or higher
for this key permits the iSCSI-related features defined in this for this key permits the iSCSI-related features defined in this
document to be used on all connections on this iSCSI session. document to be used on all connections on this iSCSI session.
SCSI level hand-shakes (e.g. commands, mode pages) eventually SCSI level hand-shakes (e.g. commands, mode pages) eventually
determine the existence or lack of various SAM features available determine the existence or lack of various SAM-5 features
for the I_T nexus between the two SCSI end points). To available for the I_T nexus between the two SCSI end points). To
summarize, negotiation of this key to "2" or higher is a summarize, negotiation of this key to "2" or higher is a
necessary but not a sufficient condition of [SAM4] compliant necessary but not a sufficient condition of SAM-5 compliant
feature usage at the SCSI protocol level. feature usage at the SCSI protocol level.
For example, an iSCSI implementation may negotiate this new key For example, an iSCSI implementation may negotiate this new key
to "2" but respond to the new task management functions (see 6.2) to "2" but respond to the new task management functions (see 6.2)
with a "Task management function not supported" (which indicates with a "Task management function not supported" (which indicates
a SCSI error that prevents the function from being performed). a SCSI error that prevents the function from being performed).
In contrast, if the key is negotiated to "2", an iSCSI In contrast, if the key is negotiated to "2", an iSCSI
implementation MUST NOT reject a task management function request implementation MUST NOT reject a task management function request
PDU that requests one of the new task management functions (such PDU that requests one of the new task management functions (such
a reject would report an iSCSI protocol error). a reject would report an iSCSI protocol error).
4.2 Impact on standard INQUIRY data
The negotiated value of the iSCSIProtocolLevel key is an
increment from the base iSCSI version descriptor value
(0960h)(see [SPC4]). If the SCSI device server returns an iSCSI
version descriptor in the standard INQUIRY data, then the value
returned in that iSCSI version descriptor MUST be set to the sum
of the base value (0960h) plus the negotiated value of the
iSCSIProtocolLevel key (for example, if the negotiated
iSCSIProtocolLevel=2, then if an iSCSI version descriptor is
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
defined in section 7.1.1 has been negotiated on the session with defined in section 7.1.1 has been negotiated on the session with
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 5 skipping to change at page 11, line 5
5 - LOGICAL UNIT RESET 5 - LOGICAL UNIT RESET
6 - TARGET WARM RESET 6 - TARGET WARM RESET
7 - TARGET COLD RESET 7 - TARGET COLD RESET
8 - TASK REASSIGN 8 - TASK REASSIGN
6.2 Task Management Function Additions 6.2 Task Management Function Additions
Additional task Management function codes are listed below. For Additional task Management function codes are listed below. For
a more detailed description of SCSI task management, see [SAM5]. a more detailed description of SCSI task management, see [SAM5].
9 - QUERY TASK - determines if the task identified by the 9 - QUERY TASK - determines if the task identified by the
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 task is present in the 10 - QUERY TASK SET - determine if any task is present in the
task set. task set for the I_T_L Nexus on which the task management
function was received.
11 - I_T NEXUS RESET - perform an I_T nexus loss function for 11 - I_T NEXUS RESET - perform an I_T nexus loss function for
the I_T nexus of each logical unit accessible through the I_T the I_T nexus of each logical unit accessible through the I_T
Nexus on which the task management function was received. Nexus on which the task management 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 (see 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 tasks The iSCSI target MUST ensure that no responses for the tasks
covered by a task management function are sent to the iSCSI covered by a task management function are sent to the iSCSI
initiator after the Task Management response except for a task initiator after the Task Management response except for a task
covered by a TASK REASSIGN, QUERY TASK, or QUERY TASK SET. covered by a TASK REASSIGN, QUERY TASK, or QUERY TASK 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
implicit or explicit logout), QUERY TASK MUST be issued on the
same connection to which the task to be queried is allegiant at
the time the Task Management Request is issued. If the
connection is implicitly or explicitly logged out (i.e., no other
request will be issued on the failing connection and no other
response will be received on the failing connection), then a
QUERY TASK function request may be issued on another connection.
This Task Management request will then establish a new allegiance
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
MUST drop all connections in the session over which this function MUST drop all connections in the session over which this function
is recevied. Independent of the DefaultTime2Wait and is received. Independent of the DefaultTime2Wait and
DefaultTime2Retain value applicable to the session over which DefaultTime2Retain value applicable to the session over which
this function is received, the target device MUST consider each this function is received, the target device MUST consider each
participating connection in the session to have immediately timed participating connection in the session to have immediately timed
out, leading to FREE state. The resulting timeouts cause the out, leading to FREE state. The resulting timeouts cause the
session timeout event defined in [RFC3720], which in turn session timeout event defined in [RFC3720], which in turn
triggers the I_T nexus loss notification to the SCSI layer as triggers the I_T nexus loss notification to the SCSI layer as
described in [RFC3720]. described in [RFC3720].
6.2.1 LUN field 6.2.1 LUN field
This field is required for functions that address a specific LU This field is required for functions that address a specific LU
(i.e., ABORT TASK, CLEAR TASK SET, ABORT TASK SET, CLEAR ACA, (i.e., ABORT TASK, CLEAR TASK SET, ABORT TASK SET, CLEAR ACA,
LOGICAL UNIT RESET, QUERY TASK, QUERY TASK SET, and QUERY LOGICAL UNIT RESET, QUERY TASK, QUERY TASK SET, and QUERY
ASYNCHRONOUS EVENT) and is reserved in all others. ASYNCHRONOUS EVENT) and is reserved in all others.
6.2.2 Referenced Task Tag 6.2.2 Referenced Task Tag
The Initiator Task Tag of the task to be aborted for the ABORT The Initiator Task Tag of the task to be aborted for the ABORT
TASK function, reassigned for the TASK REASSIGN function, or TASK function, reassigned for the TASK REASSIGN function, or
queried for the QUERY TASK function. For all other functions queried for the QUERY TASK function. For all other functions
this field MUST be set to the reserved value 0xffffffff. this field MUST be set to the reserved value 0xffffffff.
6.2.3 RefCmdSN 6.2.3 RefCmdSN
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 |
skipping to change at page 14, line 12 skipping to change at page 14, line 12
Task Management function and sends a Task Management response Task Management function and sends a Task Management response
back to the initiator. back to the initiator.
6.3.1 Task Management Function Response Additions 6.3.1 Task Management Function Response Additions
The new response is listed below: The new response is listed below:
7 - Function succeeded. 7 - Function succeeded.
In symbolic terms Response value 7 maps to the SCSI service In symbolic terms Response value 7 maps to the SCSI service
response of FUNCTION SUCCEEDED. response of FUNCTION SUCCEEDED in [SAM4].
The task management function response of function succeeded MUST The task management function response of "Function succeeded"
be supported by an initiator that sends any of the new task MUST be supported by an initiator that sends any of the new task
management functions (see 6.2). management functions (see 6.2).
For the QUERY TASK function, if the specified task is in the task For the QUERY TASK function, if the specified task is in the task
set, then the target returns a Response value of Function set, then the logical unit returns a Response value of Function
succeeded and additional response information is returned as succeeded and additional response information is returned as
specified in [SAM5]. If the specified task is not in the task specified in [SAM5]. If the specified task is not in the task
set, then the target returns a Response value of Function set, then the logical unit returns a Response value of Function
complete. complete.
For the QUERY TASK SET function, if there is any command present For the QUERY TASK SET function, if there is any command present
in the task set from the specified I_T_L nexus, then the target in the task set from the specified I_T_L nexus, then the logical
returns a Response value of Function succeeded. If there are no unit returns a Response value of Function succeeded. If there
commands present in the task set from the specified I_T_L nexus, are no commands present in the task set from the specified I_T_L
then the target returns a Response value of Function complete. nexus, then the logical unit returns a Response value of Function
complete.
For the I_T NEXUS RESET function, after completion of the events For the I_T NEXUS RESET function, after completion of the events
described in section 6.2 for this function, the target returns a described in section 6.2 for this function, the logical unit
Response value of Function complete. However, because the target returns a Response value of Function complete. However, because
drops all connections, the Service Response (defined by [SAM4]) the target drops all connections, the Service Response (defined
for this SCSI task management function may not be reliably by [SAM4]) for this SCSI task management function may not be
delivered to the issuing initiator port. reliably delivered to the issuing initiator port.
For the QUERY ASYNCHRONOUS EVENT, if there is a unit attention For the QUERY ASYNCHRONOUS EVENT, if there is a unit attention
condition or deferred error pending for the specified I_T_L condition or deferred error pending for the specified I_T_L
nexus, then the target returns a Response value of Function nexus, then the logical unit returns a Response value of Function
succeeded and additional response information is returned as succeeded and additional response information is returned as
specified in [SAM5]. If there is no unit attention or deferred specified in [SAM5]. If there is no unit attention or deferred
error pending for the specified I_T_L nexus then the target error pending for the specified I_T_L nexus then the logical unit
returns a Response value of Function complete. returns a Response value of Function complete.
6.4 Task Management Requests Affecting Multiple Tasks 6.4 Task Management Requests Affecting Multiple Tasks
Section 4.1 of [RFC5048] defines the notion of "affected tasks" Section 4.1 of [RFC5048] defines the notion of "affected tasks"
in multi-task abort scenarios. This section adds to the list in multi-task abort scenarios. This section adds to the list
include in that section by defining the tasks affected by the I_T include in that section by defining the tasks affected by the I_T
NEXUS RESET function. NEXUS RESET function.
I_T NEXUS RESET: All outstanding tasks received on the I_T I_T NEXUS RESET: All outstanding tasks received on the I_T
nexus on which the function request was received for all nexus on which the function request was received for all
logical units accessible to the I_T nexus. logical units accessible to the I_T nexus.
Section 4.1.2 of [RFC5048] and section 4.1.3 of [RFC5048] Section 4.1.2 of [RFC5048] and section 4.1.3 of [RFC5048]
identify semantics for task management functions that involve identify semantics for task management functions that involve
multi-task abort operations. If an iSCSI implementation supports multi-task abort operations. If an iSCSI implementation supports
the I_T NEXUS RESET function, it MUST also support the protocol the I_T NEXUS RESET function, it MUST also support the protocol
behavior as defined in those sections and follow the sequence of behavior as defined in those sections and follow the sequence of
actions as described in those sections when processing the I_T actions as described in those sections when processing the I_T
NEXUS RESET function. NEXUS RESET function.
7. Login/Text Operational Text Keys 7. Login/Text Operational Text Keys
7.1 New Operational Text Keys 7.1 New Operational Text Keys
7.1.1 iSCSIProtocolLevel 7.1.1 iSCSIProtocolLevel
Use: LO Use: LO, IO
Irrelevant when: SessionType = Discovery Irrelevant when: SessionType = Discovery
Senders: Initiator and Target Senders: Initiator and Target
Scope: SW Scope: SW
iSCSIProtocolLevel=<numerical-value-from-0-to-65535> iSCSIProtocolLevel=<numerical-value-from-0-to-31>
Default is 1. Default is 1.
Result function is Minimum. Result function is Minimum.
This key is used to negotiate the use of iSCSI features that This key is used to negotiate the use of iSCSI features that
require different levels of protocol support for proper require different levels of protocol support (e.g., PDU formats,
operation. This key is negotiated on the iSCSI session once the end node semantics) for proper operation.
session is in full feature phase.
Negotiation of the iSCSIProtocolLevel key to a value claimed by Negotiation of the iSCSIProtocolLevel key to a value
an RFC indicates that both negotiating parties are compliant to corresponding to an RFC indicates that both negotiating parties
the RFC in question, and agree to support the corresponding are compliant to the RFC in question, and agree to support the
semantics on that iSCSI session. An operational value of iSCSI corresponding PDU formats and semantics on that iSCSI session.
ProtocolLevel = "x" on an iSCSI session requires that the iSCSI An operational value of iSCSI ProtocolLevel = "x" on an iSCSI
protocol semantics on that iSCSI session be a logical superset of session requires that the iSCSI protocol semantics on that iSCSI
the capabilities in all RFCs that have claimed values of an session be a logical superset of the capabilities in all RFCs
iSCSIProtocolLevel less than "x". that have claimed values of an iSCSIProtocolLevel less than "x".
An iSCSIProtocolLevel key negotiated to "2" or higher is required An iSCSIProtocolLevel key negotiated to "0" indicates that the
to enable use of features defined in this RFC. implementation does not claim a specific iSCSI protocol level.
An iSCSIProtocolLevel key negotiated to "0" indicates that the An iSCSIProtocolLevel key negotiated to "2" or higher is required
implementation does not claim a specific iSCSI protocol level. to enable use of features defined in this RFC.
If the negotiation answer is ignored by the acceptor, or the If the negotiation answer is ignored by the acceptor, or the
answer from the remote iSCSI end point is key=NotUnderstood, then answer from the remote iSCSI end point is key=NotUnderstood, then
the features defined in this RFC, and the features defined in any the features defined in this RFC, and the features defined in any
RFC requiring a key value greater than "2" MUST NOT be used. RFC requiring a key value greater than "2" MUST NOT be used.
8. Security Considerations
8. Security Considerations
At the time of writing this document does not introduce any new At the time of writing this document does not introduce any new
security considerations other than those described in [RFC3720]. security considerations other than those described in [RFC3720].
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:
skipping to change at page 16, line 42 skipping to change at page 16, line 45
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.
--------------------------------------------------------- ---------------------------------------------------------
This document creates the following iSCSI-related registries for This document creates the following iSCSI-related registries for
IANA to manage. IANA to manage.
3. iSCSI Protocol Level 3. iSCSI Protocol Level
Name of new registry: "iSCSI Protocol Level" Name of new registry: "iSCSI Protocol Level"
Namespace details: Numerical values from 0 to 65535 Namespace details: Numerical values from 0 to 31
Information that must be provided to assign a new value: An Information that must be provided to assign a new value: An
IESG-approved specification defining the semantics and IESG-approved standards track specification defining the
interoperability requirements of the proposed new value and semantics and interoperability requirements of the proposed
the fields to be recorded in the registry. new value and the fields to be recorded in the registry.
Assignment policy: Assignment policy:
If the requested value is not already assigned, it may be The assignments of these values must be coordinated with the
assigned to the requester. ANSI/INCITS T10 committee; therefore review by an expert that
maintains an association with that committee is required prior
to IESG approval of the associated specification. After
creation of the registry, values are to be assigned
sequentially (for example, any value greater than 4 will not
be assigned until after the value 4 has been assigned).
1 and 3-65535: range reserved by IANA for assignment in this 1 and 3-31: range reserved by IANA for assignment in this
registry. registry.
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.
0, [RFCxxx] 0, [RFCxxx]
2, [RFCxxx] 2, [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.
--------------------------------------------------------- ---------------------------------------------------------
Allocation Policy: Allocation Policy:
Standards Action ([IANA]) Expert review ([IANA]) and Standards Action ([IANA])
4. iSCSI Task Management Response Codes 4. iSCSI Task Management Response Codes
Name of new registry: "iSCSI TMF Response Codes" Name of new registry: "iSCSI TMF Response Codes"
Namespace details: Numerical values that can fit in 8 bits. Namespace details: Numerical values that can fit in 8 bits.
Information that must be provided to assign a new value: An Information that must be provided to assign a new value: An
IESG-approved specification defining the semantics and IESG-approved specification defining the semantics and
interoperability requirements of the proposed new value and interoperability requirements of the proposed new value and
the fields to be recorded in the registry. the fields to be recorded in the registry.
Assignment policy: Assignment policy:
If the requested value is not already assigned, it may be If the requested value is not already assigned, it may be
assigned to the requester. assigned to the requester.
8-254: Range reserved by iANA for assignment in this registry. 8-254: Range reserved by iANA for assignment in this registry.
Fields to record in the registry: Assigned value, Operation Fields to record in the registry: Assigned value, Operation
Name, and its associated RFC reference. Name, and its associated RFC reference.
0x0, Function complete, [RFC3720]
0x0, Function complete, [RFC3720]
0x1, Task does not exist, [RFC3720] 0x1, Task does not exist, [RFC3720]
0x2, LUN does not exist, [RFC3720] 0x2, LUN does not exist, [RFC3720]
0x3, Task still allegiant, [RFC3720] 0x3, Task still allegiant, [RFC3720]
0x4, Task allegiance reassignment not supported, [RFC3720] 0x4, Task allegiance reassignment not supported, [RFC3720]
0x5, Task management function not supported, [RFC3720] 0x5, Task management function not supported, [RFC3720]
skipping to change at page 18, line 48 skipping to change at page 19, line 5
Interface (iSCSI)", RFC 3720, April 2004. Interface (iSCSI)", RFC 3720, April 2004.
[RFC3723] Aboba, B., Tseng, J., Walker, J., Rangan, V., and [RFC3723] Aboba, B., Tseng, J., Walker, J., Rangan, V., and
Travostino, F., "Securing Block Storage Protocols Travostino, F., "Securing Block Storage Protocols
over IP", RFC 3723, April 2004. over IP", RFC 3723, April 2004.
[RFC5048] Chadalapaka, M., "Internet Small Computer System [RFC5048] Chadalapaka, M., "Internet Small Computer System
Interface (iSCSI) Corrections and Clarifications", Interface (iSCSI) Corrections and Clarifications",
RFC 5048, October 2007. RFC 5048, October 2007.
[IANA] Narten, T. and H. Alvestrand, "Guidelines for Writing [draft-ietf-storm-iscsi-cons-xx] Chadalapaka, M., Satran, J.,
Kalman, M., "iSCSI Protocol (consolidated)", RFC xxx,
Date 2011.
------------------------------------------------------------
RFC EDITORS NOTE: The above references to [draft-ietf-storm-
iscsi-cons-xx] and [RFCxxx] should reference the RFC number
assigned to that draft, and this note should be removed.
------------------------------------------------------------
[IANA] Narten, T. and H. Alvestrand, "Guidelines for Writing
an IANA Considerations Section in RFCs", BCP 26, RFC an IANA Considerations Section in RFCs", BCP 26, RFC
5226,May 2008. 5226, May 2008.
[SAM2] T10/1157D, SCSI Architecture Model - 2 (SAM-2). [SAM2] T10/1157D, SCSI Architecture Model - 2 (SAM-2).
[SAM4] ISO/IEC 14776-414, SCSI Architecture Model - 4 (SAM- [SAM4] ISO/IEC 14776-414, SCSI Architecture Model - 4 (SAM-
4). 4).
[SAM5] T10/2104D rev r05, SCSI Architecture Model - 5 (SAM- [SAM5] T10/2104D rev r04, SCSI Architecture Model - 5 (SAM-
5), Committee Draft. 5), Committee Draft.
[SPC4] T10/1731D rev r23, SCSI Primary Commands - 4 (SPC-4),
Committee Draft.
10.2 Additional Reference Sources 10.2 Additional Reference Sources
For more information on the SCSI Architecture Model, contact the For more information on the SCSI Architecture Model, contact the
T10 group at http://www.t10.org. T10 group at http://www.t10.org.
11. Acknowledgements 11. Acknowledgements
The Storage Maintenance (STORM) Working Group in the Transport The Storage Maintenance (STORM) Working Group in the Transport
Area of the IETF has been responsible for defining these Area of the IETF has been responsible for defining these
additions to the iSCSI protocol (apart from other relevant IP additions to the iSCSI protocol (apart from other relevant IP
Storage protocols). The editor acknowledges the contributions of Storage protocols). The editor acknowledges the contributions of
the entire working group. the entire working group.
The following individuals directly contributed to identifying
The following individuals directly contributed to identifying [RFCxxx] issues and/or suggesting resolutions to the issues
[RFCxxx] issues and/or suggesting resolutions to the issues clarified in this document: David Black, Rob Elliott. This
clarified in this document: David Black, Rob Elliott. This document benefited from all of these contributions.
document benefited from all of these contributions.
------------------------------------------------------------ ------------------------------------------------------------
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.
------------------------------------------------------------ ------------------------------------------------------------
Author's Addresses Author's Addresses
Frederick Knight Frederick Knight
7301 Kit Creek Road 7301 Kit Creek Road
P.O. Box 13917 P.O. Box 13917
Research Triangle Park, NC 27709, USA Research Triangle Park, NC 27709, USA
Phone: +1-919-476-5362 Phone: +1-919-476-5362
Email: knight@netapp.com Email: knight@netapp.com
Mallikarjun Chadalapaka Mallikarjun Chadalapaka
Microsoft Microsoft
One Microsoft Way One Microsoft Way
Redmond, WA 98052 USA Redmond, WA 98052 USA
EMail: cbm@chadalapaka.com Email: cbm@chadalapaka.com
 End of changes. 73 change blocks. 
194 lines changed or deleted 255 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/