draft-ietf-storm-iscsi-sam-01.txt   draft-ietf-storm-iscsi-sam-02.txt 
Storage Maintenance (StorM) Working Group F. Knight
Internet Draft NetApp
Intended status: Standards Track M. Chadalapaka
Expires: October 2010 Hewlett-Packard Co.
Updates: 3720, 5048 April 2010
Internet Small Computer Systems Interface (iSCSI) Update Storage Maintenance (StorM) Working Group F. Knight
draft-ietf-storm-iscsi-sam-01.txt Internet Draft NetApp
Intended status: Standards Track M. Chadalapaka
Expires: October 2011 Hewlett-Packard Co.
Updates: 3720, 5048 March 2011
Abstract Internet Small Computer Systems Interface (iSCSI) SAM
draft-ietf-storm-iscsi-sam-02.txt
Internet Small Computer Systems Interface (iSCSI) is a SCSI Abstract
transport protocol that maps the SCSI family of protocols onto
TCP/IP. RFC 3720 defines the iSCSI protocol. The current iSCSI
protocol (RFC 3720 and RFC 5048) is based on the SAM-2 version of
the SCSI family of protocols). This document defines additions
and changes to the iSCSI protocol to enabled additional features
that were added to the SCSI family of protocols through SAM-3,
SAM-4, and SAM-5.
This document updates RFC 3720 and RFC 5048 and the text in this Internet Small Computer Systems Interface (iSCSI) is a SCSI
document supersedes the text in RFC 3720 and RFC 5048 when the transport protocol that maps the SCSI family of protocols onto
two differ. TCP/IP. RFC 3720 defines the iSCSI protocol. The current iSCSI
protocol (RFC 3720 and RFC 5048) is based on the SAM-2 version of
the SCSI family of protocols). This document defines additions
and changes to the iSCSI protocol to enabled additional features
that were added to the SCSI family of protocols through SAM-3,
SAM-4, and SAM-5.
Status of this Memo This document updates RFC 3720 and RFC 5048 and the text in this
document supersedes the text in RFC 3720 and RFC 5048 when the
two differ.
This Internet-Draft is submitted to IETF in full conformance with Status of this Memo
the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering This Internet-Draft is submitted to IETF in full conformance with
Task Force (IETF), its areas, and its working groups. Note that the provisions of BCP 78 and BCP 79.
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are working documents of the Internet Engineering
months and may be updated, replaced, or obsoleted by other Task Force (IETF), its areas, and its working groups. Note that
documents at any time. It is inappropriate to use Internet- other groups may also distribute working documents as Internet-
Drafts as reference material or to cite them other than as "work Drafts.
in progress."
The list of current Internet-Drafts can be accessed at Internet-Drafts are draft documents valid for a maximum of six
http://www.ietf.org/1id-abstracts.html. months and may be updated, replaced, or obsoleted by other
documents at any time. It is inappropriate to use Internet-
Drafts as reference material or to cite them other than as "work
in progress."
The list of Internet-Draft Shadow Directories can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/1id-abstracts.html.
This Internet-Draft will expire October, 2010. The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
Copyright Notice This Internet-Draft will expire October, 2011.
Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Copyright Notice
Provisions Relating to IETF Documents Internet-Draft iSCSI SAM March 11
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without
warranty as described in the Simplified BSD License.
Table of Contents Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved.
1 Introduction.................................................... 3 This document is subject to BCP 78 and the IETF Trust's Legal
2 Definitions, Acronyms, and Document Summary..................... 3 Provisions Relating to IETF Documents
2.1 Definitions ...............................................3 (http://trustee.ietf.org/license-info) in effect on the date of
2.2 Acronyms ..................................................3 publication of this document. Please review these documents
2.3 New Semantics .............................................3 carefully, as they describe your rights and restrictions with
3 Terminology Mapping............................................. 4 respect to this document. Code Components extracted from this
4 Negotiation of New Feature Use.................................. 7 document must include Simplified BSD License text as described in
5 SCSI Commands................................................... 8 Section 4.e of the Trust Legal Provisions and are provided without
5.1 SCSI Command Additions ....................................8 warranty as described in the Simplified BSD License.
5.1.1 Command Priority (byte 2) ............................ 8
5.2 SCSI Response Additions ...................................9
5.2.1 Status Qualifier .................................... 10
5.2.2 Data Segment - Sense and Response Data Segment ...... 10
6 Task Management Functions...................................... 10
6.1 Existing Task Management Functions .......................10
6.2 Task Management Function Additions .......................10
6.2.1 LUN field ........................................... 12
6.2.2 Referenced Task Tag ................................. 12
6.2.3 RefCmdSN ............................................ 12
6.3 Task Management Function Responses .......................13
6.3.1 Task Management Function Response Additions ......... 14
6.4 Task Management Requests Affecting Multiple Tasks ........14
7 Login/Text Operational Text Keys............................... 15
7.1 New Operational Text Keys ................................15
7.1.1 iSCSIProtocolLevel .................................. 15
8 Security Considerations........................................ 16
9 IANA Considerations............................................ 16
10 References .................................................. 17
11 Acknowledgements ............................................ 18
1. Introduction
The original [RFC3720] was built based on the SAM-2 model for Table of Contents
SCSI. Several new features and capabilities have been added to
the SCSI Architecture Model in the intervening years (SAM5 is now
the current version of the SCSI Architecture Model). This
document is not a complete revision of [RFC3720]. Instead, this
document is intended as a companion document to [RFC3720] and
[RFC5048].
The text in this document, however, updates and supersedes the 1 Introduction........................................... 3
text in [RFC3720] and [RFC5048] whenever there is any conflict. 2 Definitions, Acronyms, and Document Summary............ 3
2.1 Definitions....................................... 3
2.2 Acronyms.......................................... 3
2.3 New Semantics..................................... 3
3 Terminology Mapping.................................... 4
4 Negotiation of New Feature Use......................... 7
5 SCSI Commands.......................................... 8
5.1 SCSI Command Additions............................ 8
5.1.1 Command Priority (byte 2)...................... 8
5.2 SCSI Response Additions........................... 9
5.2.1 Status Qualifier.............................. 10
5.2.2 Data Segment - Sense and Response Data Segment 10
6 Task Management Functions............................. 10
6.1 Existing Task Management Functions............... 10
6.2 Task Management Function Additions............... 10
6.2.1 LUN field..................................... 12
6.2.2 Referenced Task Tag........................... 12
6.2.3 RefCmdSN...................................... 12
6.3 Task Management Function Responses............... 13
6.3.1 Task Management Function Response Additions... 14
6.4 Task Management Requests Affecting Multiple Tasks 14
7 Login/Text Operational Text Keys...................... 15
7.1 New Operational Text Keys........................ 15
7.1.1 iSCSIProtocolLevel............................ 15
8 Security Considerations............................... 16
9 IANA Considerations................................... 16
10 References .......................................... 17
11 Acknowledgements .................................... 18
Internet-Draft iSCSI SAM March 11
2. Definitions, Acronyms, and Document Summary 1. Introduction
2.1 Definitions The original [RFC3720] was built based on the SAM-2 model for
SCSI. Several new features and capabilities have been added to
the SCSI Architecture Model in the intervening years (SAM5 is now
the current version of the SCSI Architecture Model). This
document is not a complete revision of [RFC3720]. Instead, this
document is intended as a companion document to [RFC3720] and
[RFC5048].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL The text in this document, however, updates and supersedes the
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and text in [RFC3720] and [RFC5048] whenever there is any conflict.
"OPTIONAL" in this document are to be interpreted as described in
[RFC2119].
2.2 Acronyms 2. Definitions, Acronyms, and Document Summary
SAM4 SCSI Architecture Model - 4 2.1 Definitions
SAM5 SCSI Architecture Model - 5
SAM SAM4 or SAM5
2.3 New Semantics The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
[RFC2119].
This document specifies new iSCSI semantics. This section 2.2 Acronyms
summarizes the contents of the document.
Section 3: The mapping of iSCSI objects to SAM5 objects SAM4 SCSI Architecture Model - 4
The iSCSI node may contain both initiator and SAM5 SCSI Architecture Model - 5
target capabilities. SAM SAM4 or SAM5
Section 4: The protocol used to negotiate the use of the new 2.3 New Semantics
capabilities described in this document.
Section 5: New Command operations This document specifies new iSCSI semantics. This section
The PRI field for SCSI command priority has been summarizes the contents of the document.
added to the SCSI command PDU (see 5.1.1).
The Status Qualifier field has been added to the
SCSI response PDU (see 5.2.1).
Sense data may be returned (via autosense) for any
SCSI status, not just CHECK CONDITION (see 5.2.2).
Section 6: New Task Management Functions Section 3: The mapping of iSCSI objects to SAM5 objects
Four new task management functions (QUERY TASK, The iSCSI node may contain both initiator and
QUERY TASK SET, I_T NEXUS RESET, and QUERY target capabilities.
ASYNCHRONOUS EVENT have been added (see 6.2).
A new "function succeeded" response has been added
(see 6.3.1).
Section 7: New Negotiation key Section 4: The protocol used to negotiate the use of the new
A new negotiation key has been added to enable the capabilities described in this document.
use of the new features in section 5 and section
6.
3. Terminology Mapping Section 5: New Command operations
The PRI field for SCSI command priority has been
added to the SCSI command PDU (see 5.1.1).
The Status Qualifier field has been added to the
SCSI response PDU (see 5.2.1).
Sense data may be returned (via autosense) for any
SCSI status, not just CHECK CONDITION (see 5.2.2).
The iSCSI model (defined in [RFC3720]) uses different terminology Section 6: New Task Management Functions
than the SCSI Architecture Model. In some cases, iSCSI uses Internet-Draft iSCSI SAM March 11
multiple terms to describe what in the SCSI Architecture Model is
described with a single term. The iSCSI terms and SAM terms are
not necessarily equivalent, but rather, the iSCSI terms represent
examples of the objects or classes described in SAM as follows:
+-----------------------------+---------------------------+ Four new task management functions (QUERY TASK,
| RFCxxx Terminology | SAM Terminology | QUERY TASK SET, I_T NEXUS RESET, and QUERY
+-----------------------------+---------------------------+ ASYNCHRONOUS EVENT have been added (see 6.2).
| Network Entity | none | A new "function succeeded" response has been added
+-----------------------------+---------------------------+ (see 6.3.1).
| iSCSI Node | SCSI Device |
+-----------------------------+---------------------------+
| iSCSI Name | SCSI Device Name |
+-----------------------------+---------------------------+
| iSCSI Node Name | SCSI Device Name |
+-----------------------------+---------------------------+
| iSCSI Initiator Node | SCSI Initiator Device |
+-----------------------------+---------------------------+
| iSCSI Initiator Name | SCSI Device Name |
+-----------------------------+---------------------------+
| iSCSI Initiator Port Name | SCSI Initiator Port Name |
| iSCSI Node Name + ',i,' + | |
| ISID | |
+-----------------------------+---------------------------+
| iSCSI Target Node | SCSI Target Device |
+-----------------------------+---------------------------+
| iSCSI Target Name | SCSI Device Name |
+-----------------------------+---------------------------+
| iSCSI Target Port Name | SCSI Target Port Name |
| iSCSI Node Name + ',t,' + | |
| Target Portal Group Tag | |
+-----------------------------+---------------------------+
| iSCSI Target Portal Group | SCSI Target Port |
+-----------------------------+---------------------------+
| iSCSI Initiator Node + | SCSI Initiator Port |
| active ISID | |
+-----------------------------+---------------------------+
| iSCSI Initiator Name + | I_T Nexus |
| ',i,' + ISID, iSCSI Target | |
| Name + ',t,' + Portal | |
| Group Tag | |
+-----------------------------+---------------------------+
| Target Portal Group Tag | Relative Port ID |
+-----------------------------+---------------------------+
-------------------------------------------------------- Section 7: New Negotiation key
RFC EDITORS NOTE: The above reference (in row 1) to [RFCxxx] A new negotiation key has been added to enable the
should reference this RFC, and this note should be removed. use of the new features in section 5 and section
-------------------------------------------------------- 6.
The following diagram shows an example of a combination target 3. Terminology Mapping
device and initiator device. Such a configuration may exist in a
target device that implements a SCSI Copy Manager. This example
shows how a session that shares Network Portals within a Portal
Group may be established (see Target Portal Group 1). In
addition, this example shows the Initiator using a different
Portal Group than the Target Portal Group, but the Initiator
Portal group sharing Network Portal A with the Target Portal
Group.
----------------------------IP Network--------------------- The iSCSI model (defined in [RFC3720]) uses different terminology
| | | than the SCSI Architecture Model. In some cases, iSCSI uses
+----|---------------|-------+ +----|------------+ multiple terms to describe what in the SCSI Architecture Model is
| +----------+ +----------+ | | +----------+ | described with a single term. The iSCSI terms and SAM terms are
| | Network | | Network | | | | Network | | not necessarily equivalent, but rather, the iSCSI terms represent
| | Portal A | | Portal B | | | | Portal A | | examples of the objects or classes described in SAM as follows:
| +----------+ +----------+ | | +----------+ |
| | Target | | | | Initiator |
| | Portal | | | | Portal |
| | Group 1 | | | | Group 2 |
+----|---------------|-------+ +----|------------+
| | |
+----------|---------------|--------------------|--------------------+
| +--------|---------------|----+ +-------------|------------------+ |
| |+-------|---------------|---+| |+------------|-----------------+| |
| ||iSCSI Session (Target side)|| ||iSCSI Session (Initiator side)|| |
| || || || || |
| || (TSIH = 56) || || (SSID = 48) || |
| |+---------------------------+| |+------------------------------+| |
| | | | | |
| | iSCSI Target Node | | iSCSI Initiator Node | |
| +-----------------------------+ +--------------------------------+ |
| iSCSI Node |
| (within Network Entity, not shown) |
+--------------------------------------------------------------------+
4. Negotiation of New Feature Use
The iSCSIProtocolLevel operational text key (see 7.1.1) Internet-Draft iSCSI SAM March 11
containing a value of "2" or higher MUST be negotiated to enable
the use of features described in this RFC.
Note that an operational value of "2" or higher for this key on +-----------------------------+---------------------------+
an iSCSI session does not influence the SCSI level features in | RFCxxx Terminology | SAM Terminology |
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 | Network Entity | none |
document to be used on all connections on this iSCSI session. +-----------------------------+---------------------------+
SCSI level hand-shakes (e.g. commands, mode pages) eventually | iSCSI Node | SCSI Device |
determine the existence or lack of various SAM features available +-----------------------------+---------------------------+
for the I_T nexus between the two SCSI end points). To | iSCSI Name | SCSI Device Name |
summarize, negotiation of this key to "2" or higher is a +-----------------------------+---------------------------+
necessary but not a sufficient condition of SAM-4 compliant | iSCSI Node Name | SCSI Device Name |
feature usage at the SCSI protocol level. +-----------------------------+---------------------------+
| iSCSI Initiator Node | SCSI Initiator Device |
+-----------------------------+---------------------------+
| iSCSI Initiator Name | SCSI Device Name |
+-----------------------------+---------------------------+
| iSCSI Initiator Port Name | SCSI Initiator Port Name |
| iSCSI Node Name + ',i,' + | |
| ISID | |
+-----------------------------+---------------------------+
| iSCSI Target Node | SCSI Target Device |
+-----------------------------+---------------------------+
| iSCSI Target Name | SCSI Device Name |
+-----------------------------+---------------------------+
| iSCSI Target Port Name | SCSI Target Port Name |
| iSCSI Node Name + ',t,' + | |
| Target Portal Group Tag | |
+-----------------------------+---------------------------+
| iSCSI Target Portal Group | SCSI Target Port |
+-----------------------------+---------------------------+
| iSCSI Initiator Node + | SCSI Initiator Port |
| active ISID | |
+-----------------------------+---------------------------+
| iSCSI Initiator Name + | I_T Nexus |
| ',i,' + ISID, iSCSI Target | |
| Name + ',t,' + Portal | |
| Group Tag | |
+-----------------------------+---------------------------+
| Target Portal Group Tag | Relative Port ID |
+-----------------------------+---------------------------+
For example, an iSCSI implementation may negotiate this new key -----------------------------------------------------------
to "2" but respond to the new task management functions (see 6.2) RFC EDITORS NOTE: The above reference (in row 1) to [RFCxxx]
with a "Task management function not supported" (which indicates should reference this RFC, and this note should be removed.
a SCSI error that prevents the function from being performed). -----------------------------------------------------------
In contrast, if the key is negotiated to "2", an iSCSI Internet-Draft iSCSI SAM March 11
implementation MUST NOT reject a task management function request
PDU that requests one of the new task management functions (such
a reject would report an iSCSI protocol error).
5. SCSI Commands The following diagram shows an example of a combination target
device and initiator device. Such a configuration may exist in a
target device that implements a SCSI Copy Manager. This example
shows how a session that shares Network Portals within a Portal
Group may be established (see Target Portal Group 1). In
addition, this example shows the Initiator using a different
Portal Group than the Target Portal Group, but the Initiator
Portal group sharing Network Portal A with the Target Portal
Group.
5.1 SCSI Command Additions ----------------------------IP Network---------------------
| | |
+----|---------------|-------+ +----|------------+
| +----------+ +----------+ | | +----------+ |
| | Network | | Network | | | | Network | |
| | Portal A | | Portal B | | | | Portal A | |
| +----------+ +----------+ | | +----------+ |
| | Target | | | | Initiator |
| | Portal | | | | Portal |
| | Group 1 | | | | Group 2 |
+----|---------------|-------+ +----|------------+
| | |
+----------|---------------|--------------------|--------------------+
| +--------|---------------|----+ +-------------|------------------+ |
| |+-------|---------------|---+| |+------------|-----------------+| |
| ||iSCSI Session (Target side)|| ||iSCSI Session (Initiator side)|| |
| || || || || |
| || (TSIH = 56) || || (SSID = 48) || |
| |+---------------------------+| |+------------------------------+| |
| | | | | |
| | iSCSI Target Node | | iSCSI Initiator Node | |
| +-----------------------------+ +--------------------------------+ |
| iSCSI Node |
| (within Network Entity, not shown) |
+--------------------------------------------------------------------+
Internet-Draft iSCSI SAM March 11
The format of the SCSI Command PDU is: 4. Negotiation of New Feature Use
Byte/ 0 | 1 | 2 | 3 | The iSCSIProtocolLevel operational text key (see 7.1.1)
/ | | | | containing a value of "2" or higher MUST be negotiated to enable
|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| the use of features described in this RFC.
+---------------+---------------+---------------+---------------+
0|.|I| 0x01 |F|R|W|. .|ATTR | PRI | Reserved |
+---------------+---------------+---------------+---------------+
4|TotalAHSLength | DataSegmentLength |
+---------------+---------------+---------------+---------------+
8| Logical Unit Number (LUN) |
+ +
12| |
+---------------+---------------+---------------+---------------+
16| Initiator Task Tag |
+---------------+---------------+---------------+---------------+
20| Expected Data Transfer Length |
+---------------+---------------+---------------+---------------+
24| CmdSN |
+---------------+---------------+---------------+---------------+
28| ExpStatSN |
+---------------+---------------+---------------+---------------+
32/ SCSI Command Descriptor Block (CDB) /
+/ /
+---------------+---------------+---------------+---------------+
48/ AHS (Optional) /
+---------------+---------------+---------------+---------------+
x/ Header Digest (Optional) /
+---------------+---------------+---------------+---------------+
y/ (DataSegment, Command Data) (Optional) /
+/ /
+---------------+---------------+---------------+---------------+
z/ Data Digest (Optional) /
+---------------+---------------+---------------+---------------+
5.1.1 Command Priority (byte 2) Note that an operational value of "2" or higher for this key on
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
for this key permits the iSCSI-related features defined in this
document to be used on all connections on this iSCSI session.
SCSI level hand-shakes (e.g. commands, mode pages) eventually
determine the existence or lack of various SAM features available
for the I_T nexus between the two SCSI end points). To
summarize, negotiation of this key to "2" or higher is a
necessary but not a sufficient condition of SAM-4 compliant
feature usage at the SCSI protocol level.
For example, an iSCSI implementation may negotiate this new key
to "2" but respond to the new task management functions (see 6.2)
with a "Task management function not supported" (which indicates
a SCSI error that prevents the function from being performed).
In contrast, if the key is negotiated to "2", an iSCSI
implementation MUST NOT reject a task management function request
PDU that requests one of the new task management functions (such
a reject would report an iSCSI protocol error).
Internet-Draft iSCSI SAM March 11
5. SCSI Commands
5.1 SCSI Command Additions
The format of the SCSI Command PDU is:
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|.|I| 0x01 |F|R|W|. .|ATTR | PRI | Reserved |
+---------------+---------------+---------------+---------------+
4|TotalAHSLength | DataSegmentLength |
+---------------+---------------+---------------+---------------+
8| Logical Unit Number (LUN) |
+ +
12| |
+---------------+---------------+---------------+---------------+
16| Initiator Task Tag |
+---------------+---------------+---------------+---------------+
20| Expected Data Transfer Length |
+---------------+---------------+---------------+---------------+
24| CmdSN |
+---------------+---------------+---------------+---------------+
28| ExpStatSN |
+---------------+---------------+---------------+---------------+
32/ SCSI Command Descriptor Block (CDB) /
+/ /
+---------------+---------------+---------------+---------------+
48/ AHS (Optional) /
+---------------+---------------+---------------+---------------+
x/ Header Digest (Optional) /
+---------------+---------------+---------------+---------------+
y/ (DataSegment, Command Data) (Optional) /
+/ /
+---------------+---------------+---------------+---------------+
z/ Data Digest (Optional) /
+---------------+---------------+---------------+---------------+
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
Internet-Draft iSCSI SAM March 11
defined in section 7.1.1 has been negotiated on the session with defined in section Error! Reference source not found. has been
a value of "2" or higher. negotiated on the session with 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 Error! Reference source not found. 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 |
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
16| Initiator Task Tag | 16| Initiator Task Tag |
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
20| SNACK Tag or Reserved | 20| SNACK Tag or Reserved |
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
24| StatSN | 24| StatSN |
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
28| ExpCmdSN | 28| ExpCmdSN |
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
32| MaxCmdSN | 32| MaxCmdSN |
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
36| ExpDataSN or Reserved | 36| ExpDataSN or Reserved |
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
40| Bidirectional Read Residual Count or Reserved | 40| Bidirectional Read Residual Count or Reserved |
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
44| Residual Count or Reserved | 44| Residual Count or Reserved |
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
48| Header-Digest (Optional) | 48| Header-Digest (Optional) |
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
/ Data Segment (Optional) / / Data Segment (Optional) /
+/ / +/ /
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
| Data-Digest (Optional) | | Data-Digest (Optional) |
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
Internet-Draft iSCSI SAM March 11
5.2.1 Status Qualifier 5.2.1 Status Qualifier
The Status Qualifier provides additional status information (see The Status Qualifier provides additional status information (see
[SAM4]). [SAM4]).
As defined in Section 10, iSCSI PDU Formats of [RFC3720], As defined in Section 10, iSCSI PDU Formats of [RFC3720],
compliant senders already set this field to zero. Compliant compliant senders already set this field to zero. Compliant
senders MUST NOT set this field to a value other than zero unless senders MUST NOT set this field to a value other than zero 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.
This field MUST be ignored by receivers unless the This field MUST be ignored by receivers 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.2 Data Segment - Sense and Response Data Segment 5.2.2 Data Segment - Sense and Response Data Segment
Section 10.4.7 of [RFC3720] specifies that iSCSI targets MUST Section 10.4.7 of [RFC3720] specifies that iSCSI targets MUST
support and enable autosense. If Status is CHECK CONDITION support and enable autosense. If Status is CHECK CONDITION
(0x02), then the Data Segment MUST contain sense data for the (0x02), then the Data Segment MUST contain sense data for the
failed command. While [RFC3720] does not make any statements failed command. While [RFC3720] does not make any statements
about the state of the Data Segment when the Status is not CHECK about the state of the Data Segment when the Status is not CHECK
CONDITION (0x02)(i.e., the Data Segment is not prohibited from CONDITION (0x02)(i.e., the Data Segment is not prohibited from
containing sense data when the Status is not CHECK CONDITION), containing sense data when the Status is not CHECK CONDITION),
negotiation of the iSCSIProtocolLevel text key with a value of negotiation of the iSCSIProtocolLevel text key with a value of
"2" or higher as defined in section 7.1.1 explicitly indicates "2" or higher as defined in section Error! Reference source not
that the Data Segment MAY contain sense data at any time, no found. explicitly indicates that the Data Segment MAY contain
matter what value is set in the Status field. sense data at any time, no matter what value is set in the Status
field.
6. Task Management Functions 6. Task Management Functions
6.1 Existing Task Management Functions 6.1 Existing Task Management Functions
Section 10.5 of [RFC3720] defines the semantics used to request Section 10.5 of [RFC3720] defines the semantics used to request
SCSI Task Management Functions be performed. The following task SCSI Task Management Functions be performed. The following task
management functions are defined: management functions are defined:
1 - ABORT TASK 1 - ABORT TASK
2 - ABORT TASK SET 2 - ABORT TASK SET
3 - CLEAR ACA 3 - CLEAR ACA
4 - CLEAR TASK SET 4 - CLEAR TASK SET
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
Internet-Draft iSCSI SAM March 11
6.2 Task Management Function Additions 6.2 Task Management Function Additions
Additional task Management function codes are listed below. For
a more detailed description of SCSI task management, see [SAM5].
9 - QUERY TASK - determines if the task identified by the Additional task Management function codes are listed below. For
Referenced Task Tag field is present in the task set. a more detailed description of SCSI task management, see [SAM5].
10 - QUERY TASK SET - determine if any task is present in the 9 - QUERY TASK - determines if the task identified by the
task set. Referenced Task Tag field is present in the task set.
11 - I_T NEXUS RESET - perform an I_T nexus loss function for 10 - QUERY TASK SET - determine if any task is present in the
the I_T nexus of each logical unit accessible through the I_T task set.
Nexus on which the task management function was received.
12 - QUERY ASYNCHRONOUS EVENT - determine if there is a unit 11 - I_T NEXUS RESET - perform an I_T nexus loss function for
attention condition or a deferred error pending for the I_T_L 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.
These task management function requests MUST NOT be sent unless 12 - QUERY ASYNCHRONOUS EVENT - determine if there is a unit
the iSCSIProtocolLevel text key with a value of "2" or higher as attention condition or a deferred error pending for the I_T_L
defined in section 7.1.1 was negotiated on the session. nexus on which the task management function was received.
Any compliant initiator that sends any of the new task management These task management function requests MUST NOT be sent unless
functions defined in this section MUST also support all new task the iSCSIProtocolLevel text key with a value of "2" or higher as
management function responses (see 6.3.1). defined in section 7.1.1. was negotiated on the session.
For all of the task management functions detailed in this Any compliant initiator that sends any of the new task management
section, the Task Management function response MUST be returned functions defined in this section MUST also support all new task
as detailed in section 6.3 Task Management Function Response. management function responses (see 6.3.1).
The iSCSI target MUST ensure that no responses for the tasks For all of the task management functions detailed in this
covered by a task management function are sent to the iSCSI section, the Task Management function response MUST be returned
initiator after the Task Management response except for a task as detailed in section 6.3 Task Management Function Response.
covered by a TASK REASSIGN, QUERY TASK, or QUERY TASK SET.
If a QUERY TASK is issued for a task created by an immediate The iSCSI target MUST ensure that no responses for the tasks
command then RefCmdSN MUST be that of the Task Management request covered by a task management function are sent to the iSCSI
itself (i.e., CmdSN and RefCmdSN are equal); otherwise RefCmdSN initiator after the Task Management response except for a task
MUST be set to the CmdSN of the task to be queried (lower than covered by a TASK REASSIGN, QUERY TASK, or QUERY TASK SET.
CmdSN).
At the target a QUERY TASK function MUST NOT be executed on a If a QUERY TASK is issued for a task created by an immediate
Task Management request; such a request MUST result in Task command then RefCmdSN MUST be that of the Task Management request
Management response of "Function rejected". itself (i.e., CmdSN and RefCmdSN are equal); otherwise RefCmdSN
MUST be set to the CmdSN of the task to be queried (lower than
CmdSN).
For the I_T NEXUS RESET function, the target device MUST respond At the target a QUERY TASK function MUST NOT be executed on a
to the function as defined in [SAM4]. Each logical unit Task Management request; such a request MUST result in Task
accessible via the receiving I_T NEXUS MUST behave as dictated by Management response of "Function rejected".
the I_T nexus loss function in [SAM4] for the I_T nexus on which
the task management function was received. The target device
MUST drop all connections in the session over which this function
is recevied. Independent of the DefaultTime2Wait and For the I_T NEXUS RESET function, the target device MUST respond
DefaultTime2Retain value applicable to the session over which to the function as defined in [SAM4]. Each logical unit
this function is received, the target device MUST consider each accessible via the receiving I_T NEXUS MUST behave as dictated by
participating connection in the session to have immediately timed Internet-Draft iSCSI SAM March 11
out, leading to FREE state. The resulting timeouts cause the
session timeout event defined in [RFC3720], which in turn
triggers the I_T nexus loss notification to the SCSI layer as
described in [RFC3720].
6.2.1 LUN field the I_T nexus loss function in [SAM4] for the I_T nexus on which
the task management function was received. The target device
MUST drop all connections in the session over which this function
is recevied. Independent of the DefaultTime2Wait and
DefaultTime2Retain value applicable to the session over which
this function is received, the target device MUST consider each
participating connection in the session to have immediately timed
out, leading to FREE state. The resulting timeouts cause the
session timeout event defined in [RFC3720], which in turn
triggers the I_T nexus loss notification to the SCSI layer as
described in [RFC3720].
This field is required for functions that address a specific LU 6.2.1 LUN field
(i.e., ABORT TASK, CLEAR TASK SET, ABORT TASK SET, CLEAR ACA,
LOGICAL UNIT RESET, QUERY TASK, QUERY TASK SET, and QUERY
ASYNCHRONOUS EVENT) and is reserved in all others.
6.2.2 Referenced Task Tag This field is required for functions that address a specific LU
(i.e., ABORT TASK, CLEAR TASK SET, ABORT TASK SET, CLEAR ACA,
LOGICAL UNIT RESET, QUERY TASK, QUERY TASK SET, and QUERY
ASYNCHRONOUS EVENT) and is reserved in all others.
The Initiator Task Tag of the task to be aborted for the ABORT 6.2.2 Referenced Task Tag
TASK function, reassigned for the TASK REASSIGN function, or
queried for the QUERY TASK function. For all other functions
this field MUST be set to the reserved value 0xffffffff.
6.2.3 RefCmdSN The Initiator Task Tag of the task to be aborted for the ABORT
TASK function, reassigned for the TASK REASSIGN function, or
queried for the QUERY TASK function. For all other functions
this field MUST be set to the reserved value 0xffffffff.
If a QUERY TASK is issued for a task created by an immediate 6.2.3 RefCmdSN
command then RefCmdSN MUST be that of the Task Management request
itself (i.e., CmdSN and RefCmdSN are equal).
For a QUERY TASK of a task created by non-immediate command If a QUERY TASK is issued for a task created by an immediate
RefCmdSN MUST be set to the CmdSN of the task identified by the command then RefCmdSN MUST be that of the Task Management request
Referenced Task Tag field. Targets must use this field as itself (i.e., CmdSN and RefCmdSN are equal).
described in section 10.6.1 of [RFC3720] when the task identified
by the Referenced Task Tag field is not in the task set.
6.3 Task Management Function Responses 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
Referenced Task Tag field. Targets must use this field as
described in section 10.6.1 of [RFC3720] when the task identified
by the Referenced Task Tag field is not in the task set.
Byte/ 0 | 1 | 2 | 3 | Internet-Draft iSCSI SAM March 11
/ | | | |
|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 |
+---------------+---------------+---------------+---------------+
4|TotalAHSLength | DataSegmentLength |
+-----------------------------------------------+---------------+
8| Additional Response Information | Reserved |
+-----------------------------------------------+---------------+
12| Reserved |
+---------------+---------------+---------------+---------------+
16| Initiator Task Tag |
+---------------+---------------+---------------+---------------+
20| Reserved |
+---------------+---------------+---------------+---------------+
24| StatSN |
+---------------+---------------+---------------+---------------+
28| ExpCmdSN |
+---------------+---------------+---------------+---------------+
32| MaxCmdSN |
+---------------+---------------+---------------+---------------+
36/ Reserved /
+/ /
+---------------+---------------+---------------+---------------+
48| Header-Digest (Optional) |
+---------------+---------------+---------------+---------------+
Section 10.6 of [RFC3720] defines the semantics used for 6.3 Task Management Function Responses
responses to SCSI Task Management Functions. The following
responses are defined in [RFC3720]:
0 - Function Complete. Byte/ 0 | 1 | 2 | 3 |
1 - Task does not exist. / | | | |
2 - LUN does not exist. |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|
3 - Task still allegiant. +---------------+---------------+---------------+---------------+
4 - Task allegiance reassignment not supported. 0|.|.| 0x22 |1| Reserved | Response | Reserved |
5 - Task management function not supported. +---------------+---------------+---------------+---------------+
6 - Function authorization failed. 4|TotalAHSLength | DataSegmentLength |
255 - Function rejected. +-----------------------------------------------+---------------+
8| Additional Response Information | Reserved |
+-----------------------------------------------+---------------+
12| Reserved |
+---------------+---------------+---------------+---------------+
16| Initiator Task Tag |
+---------------+---------------+---------------+---------------+
20| Reserved |
+---------------+---------------+---------------+---------------+
24| StatSN |
+---------------+---------------+---------------+---------------+
28| ExpCmdSN |
+---------------+---------------+---------------+---------------+
32| MaxCmdSN |
+---------------+---------------+---------------+---------------+
36/ Reserved /
+/ /
+---------------+---------------+---------------+---------------+
48| Header-Digest (Optional) |
+---------------+---------------+---------------+---------------+
Responses to new task management functions (see 6.3.1) are listed Section 10.6 of [RFC3720] defines the semantics used for
below. In addition, a new task Management response is listed responses to SCSI Task Management Functions. The following
below. For a more detailed description of SCSI task management responses are defined in [RFC3720]:
responses, see [SAM5].
For the functions QUERY TASK, QUERY TASK SET, I_T NEXUS RESET, 0 - Function Complete.
and QUERY ASYNCHRONOUS EVENT, the target performs the requested 1 - Task does not exist.
Task Management function and sends a Task Management response 2 - LUN does not exist.
back to the initiator. 3 - Task still allegiant.
4 - Task allegiance reassignment not supported.
5 - Task management function not supported.
6 - Function authorization failed.
255 - Function rejected.
6.3.1 Task Management Function Response Additions Responses to new task management functions (see 6.3.1) are listed
below. In addition, a new task Management response is listed
below. For a more detailed description of SCSI task management
responses, see [SAM5].
The new response is listed below: Internet-Draft iSCSI SAM March 11
7 - Function succeeded. For the functions QUERY TASK, QUERY TASK SET, I_T NEXUS RESET,
and QUERY ASYNCHRONOUS EVENT, the target performs the requested
Task Management function and sends a Task Management response
back to the initiator.
In symbolic terms Response value 7 maps to the SCSI service 6.3.1 Task Management Function Response Additions
response of FUNCTION SUCCEEDED.
The task management function response of function succeeded MUST The new response is listed below:
be supported by an initiator that sends any of the new task
management functions (see 6.2).
For the QUERY TASK function, if the specified task is in the task 7 - Function succeeded.
set, then the target returns a Response value of Function
succeeded and additional response information is returned as
specified in [SAM5]. If the specified task is not in the task
set, then the target returns a Response value of Function
complete.
For the QUERY TASK SET function, if there is any command present In symbolic terms Response value 7 maps to the SCSI service
in the task set from the specified I_T_L nexus, then the target response of FUNCTION SUCCEEDED.
returns a Response value of Function succeeded. If there are no
commands present in the task set from the specified I_T_L nexus,
then the target returns a Response value of Function complete.
For the I_T NEXUS RESET function, after completion of the events The task management function response of function succeeded MUST
described in section 6.2 for this function, the target returns a be supported by an initiator that sends any of the new task
Response value of Function complete. However, because the target management functions (see 6.2).
drops all connections, the Service Response (defined by [SAM4])
for this SCSI task management function may not be reliably
delivered to the issuing initiator port.
For the QUERY ASYNCHRONOUS EVENT, if there is a unit attention For the QUERY TASK function, if the specified task is in the task
condition or deferred error pending for the specified I_T_L set, then the target returns a Response value of Function
nexus, then the target 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 there is no unit attention or deferred set, then the target returns a Response value of Function
error pending for the specified I_T_L nexus then the target complete.
returns a Response value of Function complete.
6.4 Task Management Requests Affecting Multiple Tasks 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
returns a Response value of Function succeeded. If there are no
commands present in the task set from the specified I_T_L nexus,
then the target returns a Response value of Function complete.
Section 4.1 of [RFC5048] defines the notion of "affected tasks" For the I_T NEXUS RESET function, after completion of the events
in multi-task abort scenarios. This section adds to the list described in section 6.2 for this function, the target returns a
include in that section by defining the tasks affected by the I_T Response value of Function complete. However, because the target
NEXUS RESET function. drops all connections, the Service Response (defined by [SAM4])
for this SCSI task management function may not be reliably
delivered to the issuing initiator port.
I_T NEXUS RESET: All outstanding tasks received on the I_T For the QUERY ASYNCHRONOUS EVENT, if there is a unit attention
condition or deferred error pending for the specified I_T_L
nexus, then the target returns a Response value of Function
succeeded and additional response information is returned as
specified in [SAM5]. If there is no unit attention or deferred
error pending for the specified I_T_L nexus then the target
returns a Response value of Function complete.
6.4 Task Management Requests Affecting Multiple Tasks
Section 4.1 of [RFC5048] defines the notion of "affected tasks"
in multi-task abort scenarios. This section adds to the list
Internet-Draft iSCSI SAM March 11
include in that section by defining the tasks affected by the I_T
NEXUS RESET function.
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
Irrelevant when: SessionType = Discovery Irrelevant when: SessionType = Discovery
Senders: Initiator and Target Senders: Initiator and Target
Scope: SW Scope: SW
iSCSIProtocolLevel=<numerical-value-from-1-to-65535> iSCSIProtocolLevel=<numerical-value-from-1-to-65535>
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 for proper
operation. This key is negotiated on the iSCSI session once the operation. This key is negotiated on the iSCSI session once the
session is in full feature phase. session is in full feature phase.
Negotiation of the iSCSIProtocolLevel key to a value claimed by Negotiation of the iSCSIProtocolLevel key to a value claimed by
an RFC indicates that both negotiating parties are compliant to an RFC indicates that both negotiating parties are compliant to
the RFC in question, and agree to support the corresponding the RFC in question, and agree to support the corresponding
semantics on that iSCSI session. An operational value of iSCSI semantics on that iSCSI session. An operational value of iSCSI
ProtocolLevel = "x" on an iSCSI session requires that the iSCSI ProtocolLevel = "x" on an iSCSI session requires that the iSCSI
protocol semantics on that iSCSI session be a logical superset of protocol semantics on that iSCSI session be a logical superset of
the capabilities in all RFCs that have claimed values of an the capabilities in all RFCs that have claimed values of an
iSCSIProtocolLevel less than "x". iSCSIProtocolLevel less than "x".
An iSCSIProtocolLevel key negotiated to "2" or higher is required An iSCSIProtocolLevel key negotiated to "2" or higher is required
to enable use of features defined in this RFC. 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 Internet-Draft iSCSI SAM March 11
RFC requiring a key value greater than "2" MUST NOT be used.
8. Security Considerations the features defined in this RFC, and the features defined in any
RFC requiring a key value greater than "2" MUST NOT be used.
At the time of writing this document does not introduce any new 8. Security Considerations
security considerations other than those described in [RFC3720].
Consequently, all the iSCSI-related security text in [RFC3723] is
also directly applicable to this document.
9. IANA Considerations At the time of writing this document does not introduce any new
security considerations other than those described in [RFC3720].
Consequently, all the iSCSI-related security text in [RFC3723] is
also directly applicable to this document.
This document modifies or creates a number of iSCSI-related 9. IANA Considerations
registries. The following iSCSI-related registries are modified:
1. iSCSI Task Management Functions Codes This document modifies or creates a number of iSCSI-related
registries. The following iSCSI-related registries are modified:
Name of the existing registry: "iSCSI TMF Codes" 1. iSCSI Task Management Functions Codes
Additional entries: Name of the existing registry: "iSCSI TMF Codes"
9, QUERY TASK, [RFCxxx] Additional entries:
10, QUERY TASK SET, [RFCxxx] 9, QUERY TASK, [RFCxxx]
11, I_T NEXUS RESET, [RFCxxx] 10, QUERY TASK SET, [RFCxxx]
12, QUERY ASYNCHRONOUS EVENT, [RFCxxx] 11, I_T NEXUS RESET, [RFCxxx]
--------------------------------------------------------- 12, QUERY ASYNCHRONOUS EVENT, [RFCxxx]
RFC EDITORS NOTE: The above reference to [RFCxxx] should
reference this RFC, and this note should be removed.
---------------------------------------------------------
2. iSCSI Login/Text Keys ---------------------------------------------------------
RFC EDITORS NOTE: The above reference to [RFCxxx] should
reference this RFC, and this note should be removed.
---------------------------------------------------------
Name of the existing registry: "iSCSI Text Keys" 2. iSCSI Login/Text Keys
Additional entry: Name of the existing registry: "iSCSI Text Keys"
iSCSIProtocolLevel = "2", [RFCxxx] Additional entry:
---------------------------------------------------------
RFC EDITORS NOTE: The above references to [RFCxxx] should
reference this RFC, and this note should be removed.
---------------------------------------------------------
This document creates the following iSCSI-related registries for iSCSIProtocolLevel = "2", [RFCxxx]
IANA to manage. ---------------------------------------------------------
RFC EDITORS NOTE: The above references to [RFCxxx] should
reference this RFC, and this note should be removed.
---------------------------------------------------------
3. iSCSI Task Management Response Codes This document creates the following iSCSI-related registries for
Name of new registry: "iSCSI TMF Response Codes" IANA to manage.
Namespace details: Numerical values that can fit in 8 bits. 3. iSCSI Task Management Response Codes
Internet-Draft iSCSI SAM March 11
Information that must be provided to assign a new value: An Name of new registry: "iSCSI TMF Response Codes"
IESG-approved specification defining the semantics and
interoperability requirements of the proposed new value and
the fields to be recorded in the registry.
Assignment policy: Namespace details: Numerical values that can fit in 8 bits.
If the requested value is not already assigned, it may be Information that must be provided to assign a new value: An
assigned to the requester. IESG-approved specification defining the semantics and
interoperability requirements of the proposed new value and
the fields to be recorded in the registry.
8-254: Range reserved by iANA for assignment in this registry. Assignment policy:
Fields to record in the registry: Assigned value, Operation If the requested value is not already assigned, it may be
Name, and its associated RFC reference. assigned to the requester.
0x0, Function complete, [RFC3720] 8-254: Range reserved by iANA for assignment in this registry.
0x1, Task does not exist, [RFC3720] Fields to record in the registry: Assigned value, Operation
Name, and its associated RFC reference.
0x2, LUN does not exist, [RFC3720] 0x0, Function complete, [RFC3720]
0x3, Task still allegiant, [RFC3720] 0x1, Task does not exist, [RFC3720]
0x4, Task allegiance reassignment not supported, [RFC3720] 0x2, LUN does not exist, [RFC3720]
0x5, Task management function not supported, [RFC3720] 0x3, Task still allegiant, [RFC3720]
0x6, Function authorization failed, [RFC3720] 0x4, Task allegiance reassignment not supported, [RFC3720]
0x7, Function succeeded, [RFCxxx] 0x5, Task management function not supported, [RFC3720]
255, Function rejected, [RFC3720] 0x6, Function authorization failed, [RFC3720]
------------------------------------------------------------ 0x7, Function succeeded, [RFCxxx]
RFC EDITORS NOTE: The above reference to [RFCxxx] should
reference this RFC, and this note should be removed.
------------------------------------------------------------
Allocation Policy: 255, Function rejected, [RFC3720]
Standards Action ([IANA]) ------------------------------------------------------------
RFC EDITORS NOTE: The above reference to [RFCxxx] should
reference this RFC, and this note should be removed.
------------------------------------------------------------
10. References Allocation Policy:
10.1 Normative References Standards Action ([IANA])
[RFC2119] Bradner, S. "Key Words for use in RFCs to Indicate 10. References
10.1 Normative References
Internet-Draft iSCSI SAM March 11
[RFC2119] Bradner, S. "Key Words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3720] Satran, J., Meth, K., Sapuntzakis, C., Chadalapaka, [RFC3720] Satran, J., Meth, K., Sapuntzakis, C., Chadalapaka,
M., and E. Zeidner, "Internet Small Computer Systems M., and E. Zeidner, "Internet Small Computer Systems
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 [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 r05, SCSI Architecture Model - 5 (SAM-
5), Committee Draft. 5), 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
reference this RFC, and this note should be removed.
------------------------------------------------------------
Editor's Addresses ------------------------------------------------------------
Frederick Knight RFC EDITORS NOTE: The above reference to [RFCxxx] should
7301 Kit Creek Road reference this RFC, and this note should be removed.
P.O. Box 13917 ------------------------------------------------------------
Research Triangle Park, NC 27709, USA Internet-Draft iSCSI SAM March 11
Phone: +1-919-476-5362
Email: knight@netapp.com
Mallikarjun Chadalapaka Editor's Addresses
Hewlett-Packard Company Frederick Knight
8000 Foothills Blvd. 7301 Kit Creek Road
Roseville, CA 95747-5668, USA P.O. Box 13917
Phone: +1-916-785-5621 Research Triangle Park, NC 27709, USA
EMail: cbm@rose.hp.com Phone: +1-919-476-5362
Email: knight@netapp.com
Mallikarjun Chadalapaka
Hewlett-Packard Company
8000 Foothills Blvd.
Roseville, CA 95747-5668, USA
Phone: +1-916-785-5621
EMail: cbm@rose.hp.com
 End of changes. 163 change blocks. 
623 lines changed or deleted 649 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/