draft-ietf-storm-iscsi-sam-07.txt   draft-ietf-storm-iscsi-sam-08.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: December 2013 Microsoft Expires: January 2014 Microsoft
June 2013 July 2013
Internet Small Computer Systems Interface (iSCSI) SCSI Features Internet Small Computer Systems Interface (iSCSI) SCSI Features
Update Update
draft-ietf-storm-iscsi-sam-07.txt draft-ietf-storm-iscsi-sam-08.txt
Abstract Abstract
Internet Small Computer Systems Interface (iSCSI) is a SCSI Internet Small Computer Systems Interface (iSCSI) is a SCSI
transport protocol that maps the SCSI family of protocols onto transport protocol that maps the SCSI family of protocols onto
TCP/IP. The iSCSI protocol as specified in [draft-ietf-storm- TCP/IP. The iSCSI protocol as specified in RFCxxx (and as
iscsi-cons-xx] (and as previously specified by the combination previously specified by the combination of RFC 3720 and RFC
of RFC 3720 and RFC 5048) is based on the SAM-2 (SCSI 5048) is based on the SAM-2 (SCSI Architecture Model - 2)
Architecture Model - 2) version of the SCSI family of version of the SCSI family of protocols. This document
protocols. This document defines enhancements to the iSCSI defines enhancements to the iSCSI protocol to support certain
protocol to support certain additional features of the SCSI additional features of the SCSI protocol that were defined in
protocol that were defined in SAM-3, SAM-4, and SAM-5. SAM-3, SAM-4, and SAM-5.
This document is a companion document to [draft-ietf-storm- This document is a companion document to RFCxxx.
iscsi-cons-xx].
-------------------------------------------------------- --------------------------------------------------------
RFC EDITORS NOTE: The above references to [draft-ietf-storm- RFC EDITORS NOTE: The above two references to RFCxxx should
iscsi-cons-xx] should reference the RFC number assigned to reference the RFC number assigned to the draft-ietf-storm-
that document, and this note should be removed. iscsi-cons-xx 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-
skipping to change at page 1, line 55 skipping to change at page 1, line 54
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 December, 2013. This Internet-Draft will expire January, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 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. New Feature Use................................................. 7 4. New Feature Use............................................... 7
4.1 Negotiation of New Feature Use................................. 7 4.1 Negotiation of New Feature Use............................... 7
4.2 Impact on standard INQUIRY data................................ 7 4.2 Impact on standard INQUIRY data.............................. 7
5. SCSI Commands................................................... 8 5. SCSI Commands................................................. 8
5.1 SCSI Command Additions .................................. 8 5.1 SCSI Command Additions ................................ 8
5.1.1 Command Priority (byte 2) ........................... 9 5.1.1 Command Priority (byte 2) ......................... 9
5.2 SCSI Response Additions ................................. 9 5.2 SCSI Response Additions .............................. 10
5.2.1 Status Qualifier ................................... 10 5.2.1 Status Qualifier ................................. 11
5.2.2 Data Segment - Sense and Response Data Segment ..... 10 5.2.2 Data Segment - Sense and Response Data Segment ... 11
6. Task Management Functions...................................... 11 6. Task Management Functions.................................... 12
6.1 Existing Task Management Functions ..................... 11 6.1 Existing Task Management Functions ................... 12
6.2 Task Management Function Additions ..................... 12 6.2 Task Management Function Additions ................... 13
6.2.1 LUN field .......................................... 14 6.2.1 LUN field ........................................ 14
6.2.2 Referenced Task Tag ................................ 14 6.2.2 Referenced Task Tag .............................. 14
6.2.3 RefCmdSN ........................................... 14 6.2.3 RefCmdSN ......................................... 15
6.3 Task Management Function Responses ..................... 14 6.3 Task Management Function Responses ................... 16
6.3.1 Task Management Function Response Additions ........ 16 6.3.1 Task Management Function Response Additions ...... 17
6.4 Task Management Requests Affecting Multiple Tasks ...... 16 6.4 Task Management Requests Affecting Multiple Tasks .... 18
7. Login/Text Operational Text Keys............................... 17 7. Login/Text Operational Text Keys............................. 18
7.1 New Operational Text Keys .............................. 17 7.1 New Operational Text Keys ............................ 18
7.1.1 iSCSIProtocolLevel ................................. 17 7.1.1 iSCSIProtocolLevel ............................... 18
8. Security Considerations........................................ 18 8. Security Considerations...................................... 19
9. IANA Considerations............................................ 18 9. IANA Considerations.......................................... 19
10. References.................................................... 21 10. References.................................................. 22
11. Acknowledgements.............................................. 22 11. Acknowledgements............................................ 23
1. Introduction 1. Introduction
The original iSCSI protocol [RFC3720] was built based on the The original iSCSI protocol [RFC3720] was built based on the
[SAM2] model for SCSI. Several new features and capabilities [SAM2] model for SCSI. Several new features and capabilities
have been added to the SCSI Architecture Model in the intervening have been added to the SCSI Architecture Model in the intervening
years (at the time of publication of this document, SAM-5 was the years (at the time of publication of this document, SAM-5 was the
current version of the SCSI Architecture Model). This document current version of the SCSI Architecture Model). This document
is not a complete revision of [RFC3720]. Instead, this document is not a complete revision of [RFC3720]. Instead, this document
is intended as a companion document to [draft-ietf-storm-iscsi- is intended as a companion document to [draft-ietf-storm-iscsi-
cons-xx]; this document may also be used as a companion document cons-xx]; this document may also be used as a companion document
skipping to change at page 3, line 38 skipping to change at page 3, line 38
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
in this document are to be interpreted as described in in this document are to be interpreted as described in
[RFC2119]. [RFC2119].
2.2 Acronyms 2.2 Acronyms
ISID Initiator Session Identifier ISID Initiator Session Identifier
LU Logical Unit LU Logical Unit
PDU Protocol Data Unit PDU Protocol Data Unit
SAM-4 SCSI Architecture Model - 4 (see [SAM4])
SAM-5 SCSI Architecture Model - 5 (see [SAM5]) SAM-5 SCSI Architecture Model - 5 (see [SAM5])
TMF Task Management Function 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 SAM-5 objects Section 3: The mapping of iSCSI objects to SAM-5 objects
The iSCSI node may contain both initiator and The iSCSI node may contain both initiator and
skipping to change at page 5, line 22 skipping to change at page 5, line 22
| iSCSI Name | SCSI Device Name | | iSCSI Name | SCSI Device Name |
+-----------------------------+---------------------------+ +-----------------------------+---------------------------+
| iSCSI Node Name | SCSI Device Name | | iSCSI Node Name | SCSI Device Name |
+-----------------------------+---------------------------+ +-----------------------------+---------------------------+
| iSCSI Initiator Node | SCSI Initiator Device | | iSCSI Initiator Node | SCSI Initiator Device |
+-----------------------------+---------------------------+ +-----------------------------+---------------------------+
| iSCSI Initiator Name | SCSI Device Name | | iSCSI Initiator Name | SCSI Device Name |
+-----------------------------+---------------------------+ +-----------------------------+---------------------------+
| iSCSI Initiator Port | SCSI Initiator Port | | iSCSI Initiator Port | SCSI Initiator Port |
| Identifier; (i.e., iSCSI | Identifier | | Identifier; (i.e., iSCSI | Identifier |
| Node Name + ,,,i, + ISID)*1| | | Node Name + ,,,i, + ISID)*1 | |
+-----------------------------+---------------------------+ +-----------------------------+---------------------------+
| iSCSI Initiator Port Name; | SCSI Initiator Port Name | | iSCSI Initiator Port Name; | SCSI Initiator Port Name |
| (i.e., iSCSI Node Name + | | | (i.e., iSCSI Node Name + | |
| ,,,i, + ISID)*1 | | | ,,,i, + ISID)*1 | |
+-----------------------------+---------------------------+ +-----------------------------+---------------------------+
| iSCSI Target Node | SCSI Target Device | | iSCSI Target Node | SCSI Target Device |
+-----------------------------+---------------------------+ +-----------------------------+---------------------------+
| iSCSI Target Name | SCSI Device Name | | iSCSI Target Name | SCSI Device Name |
+-----------------------------+---------------------------+ +-----------------------------+---------------------------+
| iSCSI Target Port | SCSI Target Port | | iSCSI Target Port | SCSI Target Port |
| Identifier; (i.e., iSCSI | Identifier | | Identifier; (i.e., iSCSI | Identifier |
| Node Name + ,,,t, + | | | Node Name + ,,,t, + | |
| Target Portal Group Tag)*1 | | | Target Portal Group Tag)*1 | |
+-----------------------------+---------------------------+ +-----------------------------+---------------------------+
| iSCSI Target Port Name; | SCSI Target Port Name | | iSCSI Target Port Name; | SCSI Target Port Name |
| (i.e., iSCSI Node Name + | | | (i.e., iSCSI Node Name + | |
| ,,,t, + Target Portal | | | ,,,t, + Target Portal | |
| Group Tag)*1 | | | Group Tag)*1 | |
+-----------------------------+---------------------------+ +-----------------------------+---------------------------+
| iSCSI Target Portal Group | SCSI Target Port | | iSCSI Target Portal Group | SCSI Target Port |
+-----------------------------+---------------------------+ +-----------------------------+---------------------------+
| iSCSI Initiator Name + | I_T Nexus Identifier | | iSCSI Initiator Name + | I_T Nexus Identifier |
| ',i,' + ISID + iSCSI | | | ',i,' + ISID + iSCSI | |
skipping to change at page 6, line 27 skipping to change at page 6, line 27
shows how a session that shares Network Portals within a Portal shows how a session that shares Network Portals within a Portal
Group may be established (see Target Portal Group 1). In Group may be established (see Target Portal Group 1). In
addition, this example shows the Initiator using a different addition, this example shows the Initiator using a different
Portal Group than the Target Portal Group, but the Initiator Portal Group than the Target Portal Group, but the Initiator
Portal group sharing Network Portal A with the Target Portal Portal group sharing Network Portal A with the Target Portal
Group. Group.
----------------------------IP Network--------------------- ----------------------------IP Network---------------------
| | | | | |
+----|---------------|-------+ +----|------------+ +----|---------------|-------+ +----|------------+
| +----------+ +----------+ | | +----------+ | | +----------+ +----------+ | | +----------+ |
| | Network | | Network | | | | Network | | | | Network | | Network | | | | Network | |
| | Portal A | | Portal B | | | | Portal A | | | | Portal A | | Portal B | | | | Portal A | |
| +----------+ +----------+ | | +----------+ | | +----------+ +----------+ | | +----------+ |
| | Target | | | | Initiator | | | Target | | | | Initiator |
| | Portal | | | | Portal | | | Portal | | | | Portal |
| | Group 1 | | | | Group 2 | | | Group 1 | | | | Group 2 |
+----|---------------|-------+ +----|------------+ +----|---------------|-------+ +----|------------+
| | | | | |
+----------|---------------|--------------------|--------------------+ +----------|---------------|--------------------|--------------------+
| +--------|---------------|----+ +-------------|------------------+ | | +--------|---------------|----+ +-------------|------------------+ |
| |+-------|---------------|---+| |+------------|-----------------+| | | |+-------|---------------|---+| |+------------|-----------------+| |
| ||iSCSI Session (Target side)|| ||iSCSI Session (Initiator side)|| | | ||iSCSI Session (Target side)|| ||iSCSI Session (Initiator side)|| |
| || || || || | | || || || || |
| || (TSIH = 56) || || (SSID = 48) || | | || (TSIH = 56) || || (SSID = 48) || |
skipping to change at page 7, line 12 skipping to change at page 7, line 12
| (within Network Entity, not shown) | | (within Network Entity, not shown) |
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
4. New Feature Use 4. New Feature Use
4.1 Negotiation of New Feature Use 4.1 Negotiation of New Feature Use
The iSCSIProtocolLevel operational text key (see 7.1.1) The iSCSIProtocolLevel operational text key (see 7.1.1)
containing a value of "2" MUST be negotiated to enable the use of containing a value of "2" MUST be negotiated to enable the use of
features described in this RFC. features described in this RFC.
The iSCSIProtocolLevel operational text key (see 7.1.1) This is an iSCSI negotiation mechanism that enabled iSCSI support
containing a value of "2" MUST be negotiated to enable the use of for corresponding SCSI capabilities (see [SAM5] and [SPC4]. For
features described in this RFC. This is an iSCSI negotiation this reason, negotiation of this key to a value of "2" is
mechanism that enabled iSCSI support for corresponding SCSI necessary, but not sufficient for use of the SCSI capabilities
capabilities (see [SAM5] and [SPC4]. For this reason, enabled by the iSCSI features in this RFC.
negotiation of this key to a value of "2" is necessary, but not
sufficient for hse of the SCSI capabilities enabled by the iSCSI
features in this RFC.
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.3) to "2" but respond to the new task management functions (see 6.3)
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 (as PDU that requests one of the new task management functions (as
such a reject would report an iSCSI protocol error). such a reject would report an iSCSI protocol error).
skipping to change at page 8, line 5 skipping to change at page 7, line 39
The negotiated value of the iSCSIProtocolLevel key is an The negotiated value of the iSCSIProtocolLevel key is an
increment from the base iSCSI version descriptor value increment from the base iSCSI version descriptor value
(0960h)(see [SPC4]). If the SCSI device server returns an iSCSI (0960h)(see [SPC4]). If the SCSI device server returns an iSCSI
version descriptor in the standard INQUIRY data, then the value version descriptor in the standard INQUIRY data, then the value
returned in that iSCSI version descriptor MUST be set to the sum returned in that iSCSI version descriptor MUST be set to the sum
of the base value (0960h) plus the negotiated value of the of the base value (0960h) plus the negotiated value of the
iSCSIProtocolLevel key (for example, if the negotiated iSCSIProtocolLevel key (for example, if the negotiated
iSCSIProtocolLevel=2, then if an iSCSI version descriptor is iSCSIProtocolLevel=2, then if an iSCSI version descriptor is
returned in the standard INQUIRY data it is set to 0962h). returned in the standard INQUIRY data it is set to 0962h).
--------------------------------------------------------
RFC EDITORS NOTE: The specification text in this section
requires corresponding changes in a SCSI standard (SPC-4 or
SPC-5) that is developed by INCITS Technical Committee T10.
Confirmation that these T10 changes have been made is
necessary before publishing this draft as an RFC; the
contacts for obtaining this confirmation are the primary
draft author (Frederick Knight) and storm WG chair (David
Black).
--------------------------------------------------------
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 |
skipping to change at page 9, line 8 skipping to change at page 9, line 8
-------------------------------------------------------- --------------------------------------------------------
RFC EDITORS NOTE: The above references to [RFC-cons] should RFC EDITORS NOTE: The above references to [RFC-cons] should
reference the RFC number assigned to [draft-ietf-storm-iscsi- reference the RFC number assigned to [draft-ietf-storm-iscsi-
cons-xx], and this note should be removed. cons-xx], and this note should be removed.
-------------------------------------------------------- --------------------------------------------------------
5.1.1 Command Priority (byte 2) 5.1.1 Command Priority (byte 2)
The Command Priority (PRI) is a four (4) bit field that specifies The Command Priority (PRI) is a four (4) bit field that specifies
the relative scheduling importance of this task in relation to the relative scheduling importance of this command in relation to
other SIMPLE tasks already in the task set (see [SAM4]). other commands already in the task set with SIMPLE task
attributes(see [SAM5]).
Section 11, iSCSI PDU Formats of [RFC-cons], requires that Section 11, iSCSI PDU Formats of [RFC-cons], requires that
senders set this field to zero. A sender MUST NOT set this field senders set this field to zero. A sender MUST NOT set this field
to a value other than zero unless the iSCSIProtocolLevel text key to a 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". a value of "2".
-------------------------------------------------------- --------------------------------------------------------
RFC EDITORS NOTE: The above reference to [RFC-cons] should RFC EDITORS NOTE: The above reference to [RFC-cons] should
reference the RFC number assigned to [draft-ietf-storm-iscsi- reference the RFC number assigned to [draft-ietf-storm-iscsi-
cons-xx], and this note should be removed. cons-xx], and this note should be removed.
-------------------------------------------------------- --------------------------------------------------------
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" as defined in iSCSIProtocolLevel text key with a value of "2" as defined in
section 7.1.1 was negotiated on the session. section 7.1.1 was negotiated on the session.
See [SAM5] for special considerations on the use of the priority See [SAM5] for additional considerations on the use of the
field. command priority field.
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 |
skipping to change at page 10, line 24 skipping to change at page 10, line 52
| Data-Digest (Optional) | | Data-Digest (Optional) |
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
The SCSI Response PDU above is duplicated from [RFC-cons] for The SCSI Response PDU above is duplicated from [RFC-cons] for
reference to show the Status Qualifier field. For any field reference to show the Status Qualifier field. For any field
other than the Status field, the Status Qualifier field, and the other than the Status field, the Status Qualifier field, and the
Data Segment - Sense and Response Data Segment field, the text in Data Segment - Sense and Response Data Segment field, the text in
[RFC-cons] supersedes the text in section 5.2 of this document in [RFC-cons] supersedes the text in section 5.2 of this document in
the event the two documents conflict. the event the two documents conflict.
-------------------------------------------------------- --------------------------------------------------------
RFC EDITORS NOTE: The above references to [RFC-cons] should RFC EDITORS NOTE: The above references to [RFC-cons] should
reference the RFC number assigned to [draft-ietf-storm-iscsi- reference the RFC number assigned to [draft-ietf-storm-iscsi-
cons-xx], and this note should be removed. cons-xx], and this note should be removed.
-------------------------------------------------------- --------------------------------------------------------
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]). [SAM5]).
As defined in Section 11, iSCSI PDU Formats of [RFC-cons], As defined in Section 11, iSCSI PDU Formats of [RFC-cons],
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" as defined in the iSCSIProtocolLevel text key with a value of "2" as defined in
section 7.1.1 was negotiated on the session. section 7.1.1 was negotiated on the session.
-------------------------------------------------------- --------------------------------------------------------
RFC EDITORS NOTE: The above reference to [RFC-cons] should RFC EDITORS NOTE: The above reference to [RFC-cons] should
reference the RFC number assigned to [draft-ietf-storm-iscsi- reference the RFC number assigned to [draft-ietf-storm-iscsi-
skipping to change at page 11, line 4 skipping to change at page 11, line 31
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" as defined in iSCSIProtocolLevel text key with a value of "2" as defined in
section 7.1.1 was negotiated on the session. 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 11.4.7 of [RFC-cons] specifies that iSCSI targets MUST Section 11.4.7 of [RFC-cons] 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 [RFC-cons] does not make any statements failed command. While [RFC-cons] 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" as defined in section 7.1.1 explicitly indicates that the "2" as defined in section 7.1.1 explicitly indicates that the
Data Segment MAY contain sense data at any time, no matter what Data Segment MAY contain sense data at any time, no matter what
value is set in the Status field. value is set in the Status field.
-------------------------------------------------------- --------------------------------------------------------
RFC EDITORS NOTE: The above references to [RFC-cons] should RFC EDITORS NOTE: The above references to [RFC-cons] should
reference the RFC number assigned to [draft-ietf-storm-iscsi- reference the RFC number assigned to [draft-ietf-storm-iscsi-
cons-xx], and this note should be removed. cons-xx], and this note should be removed.
-------------------------------------------------------- --------------------------------------------------------
6. Task Management Functions 6. Task Management Functions
6.1 Task Management Function Request PDU 6.1 Task Management Function Request PDU
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| 0x02 |1| Function | Reserved | 0|.|I| 0x02 |1| Function | Reserved |
skipping to change at page 12, line 4 skipping to change at page 12, line 41
36| ExpDataSN or Reserved | 36| ExpDataSN or Reserved |
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
40| Reserved / 40| Reserved /
+/ / +/ /
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
48| Header-Digest (Optional) | 48| Header-Digest (Optional) |
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
The Task Management Function Request PDU above is duplicated from The Task Management Function Request PDU above is duplicated from
[RFC-cons] for reference only. [RFC-cons] supersedes the text in [RFC-cons] for reference only. [RFC-cons] supersedes the text in
section 6.1 and 6.2 of this document in the event the two
documents conflict.
section 6.1 and 6.2 of this document in the event the two --------------------------------------------------------
documents conflict. RFC EDITORS NOTE: The above references to [RFC-cons] should
reference the RFC number assigned to [draft-ietf-storm-iscsi-
-------------------------------------------------------- cons-xx], and this note should be removed.
RFC EDITORS NOTE: The above references to [RFC-cons] should --------------------------------------------------------
reference the RFC number assigned to [draft-ietf-storm-iscsi-
cons-xx], and this note should be removed.
--------------------------------------------------------
6.2 Existing Task Management Functions 6.2 Existing Task Management Functions
Section 11.5 of [RFC-cons] defines the semantics used to request Section 11.5 of [RFC-cons] 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
skipping to change at page 13, line 45 skipping to change at page 14, line 27
response will be received on the failing connection), then a response will be received on the failing connection), then a
QUERY TASK function request may be issued on another connection. QUERY TASK function request may be issued on another connection.
This Task Management request will then establish a new allegiance This Task Management request will then establish a new allegiance
for the command being queried. for the command being queried.
At the target a QUERY TASK function MUST NOT be executed on a At the target a QUERY TASK function MUST NOT be executed on a
Task Management request; such a request MUST result in Task Task Management request; such a request MUST result in Task
Management response of "Function rejected". Management response of "Function rejected".
For the I_T NEXUS RESET function, the target device MUST respond For the I_T NEXUS RESET function, the target device MUST respond
to the function as defined in [SAM4]. Each logical unit to the function as defined in [SAM5]. 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 [SAM5] 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 received. 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 [RFC-cons], which in turn session timeout event defined in [RFC-cons], 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 [RFC-cons]. described in [RFC-cons].
-------------------------------------------------------- --------------------------------------------------------
RFC EDITORS NOTE: The above references to [RFC-cons] should RFC EDITORS NOTE: The above references to [RFC-cons] should
reference the RFC number assigned to [draft-ietf-storm-iscsi- reference the RFC number assigned to [draft-ietf-storm-iscsi-
cons-xx], and this note should be removed. cons-xx], and this note should be removed.
-------------------------------------------------------- --------------------------------------------------------
6.3.1 LUN field 6.3.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.3.2 Referenced Task Tag 6.3.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.3.3 RefCmdSN 6.3.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).
skipping to change at page 14, line 40 skipping to change at page 15, line 22
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 11.6.1 of [RFC-cons] when the task described in section 11.6.1 of [RFC-cons] when the task
identified by the Referenced Task Tag field is not in the task identified by the Referenced Task Tag field is not in the task
set. set.
-------------------------------------------------------- --------------------------------------------------------
RFC EDITORS NOTE: The above references to [RFC-cons] should RFC EDITORS NOTE: The above references to [RFC-cons] should
reference the RFC number assigned to [draft-ietf-storm-iscsi- reference the RFC number assigned to [draft-ietf-storm-iscsi-
cons-xx], and this note should be removed. cons-xx], and this note should be removed.
-------------------------------------------------------- --------------------------------------------------------
6.4 Task Management Function Responses 6.4 Task Management Function Responses
6.4.1 Task Management Function Response PDU 6.4.1 Task Management Function Response PDU
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 |
skipping to change at page 15, line 31 skipping to change at page 16, line 41
36/ Reserved / 36/ Reserved /
+/ / +/ /
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
48| Header-Digest (Optional) | 48| Header-Digest (Optional) |
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
Section 11.6 of [RFC-cons] defines the semantics used for Section 11.6 of [RFC-cons] defines the semantics used for
responses to SCSI Task Management Functions. The following responses to SCSI Task Management Functions. The following
responses are defined in [RFC-cons]: responses are defined in [RFC-cons]:
0 - Function Complete. 0 - Function Complete.
1 - Task does not exist. 1 - Task does not exist.
2 - LUN does not exist. 2 - LUN does not exist.
3 - Task still allegiant. 3 - Task still allegiant.
4 - Task allegiance reassignment not supported. 4 - Task allegiance reassignment not supported.
5 - Task management function not supported. 5 - Task management function not supported.
6 - Function authorization failed. 6 - Function authorization failed.
255 - Function rejected. 255 - Function rejected.
The Task Management Function Response PDU above and the list of The Task Management Function Response PDU above and the list of
task management function responses above are duplicated from task management function responses above are duplicated from
[RFC-cons] for reference only. [RFC-cons] supersedes the text in [RFC-cons] for reference only. [RFC-cons] supersedes the text in
section 6.4.1 of this document in the event the two documents section 6.4.1 of this document in the event the two documents
conflict. conflict.
-------------------------------------------------------- --------------------------------------------------------
RFC EDITORS NOTE: The above references to [RFC-cons] should RFC EDITORS NOTE: The above references to [RFC-cons] should
reference the RFC number assigned to [draft-ietf-storm-iscsi- reference the RFC number assigned to [draft-ietf-storm-iscsi-
skipping to change at page 16, line 14 skipping to change at page 17, line 25
For the functions QUERY TASK, QUERY TASK SET, I_T NEXUS RESET, For the functions QUERY TASK, QUERY TASK SET, I_T NEXUS RESET,
and QUERY ASYNCHRONOUS EVENT, the target performs the requested and QUERY ASYNCHRONOUS EVENT, the target performs the requested
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.4.2 Task Management Function Response Additions 6.4.2 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 in [SAM4]. response of FUNCTION SUCCEEDED in [SAM5].
The task management function response of "Function succeeded" The task management function response of "Function succeeded"
MUST 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.3). management functions (see 6.3).
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 logical unit 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 logical unit returns a Response value of Function set, then the logical unit returns a Response value of Function
skipping to change at page 16, line 41 skipping to change at page 17, line 52
in the task set from the specified I_T_L nexus, then the logical in the task set from the specified I_T_L nexus, then the logical
unit returns a Response value of Function succeeded. If there unit returns a Response value of Function succeeded. If there
are no commands present in the task set from the specified I_T_L are no commands present in the task set from the specified I_T_L
nexus, then the logical unit returns a Response value of Function nexus, then the logical unit returns a Response value of Function
complete. 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.3 for this function, the logical unit described in section 6.3 for this function, the logical unit
returns a Response value of Function complete. However, because returns a Response value of Function complete. However, because
the target drops all connections, the Service Response (defined the target drops all connections, the Service Response (defined
by [SAM4]) for this SCSI task management function may not be by [SAM5]) for this SCSI task management function may not be
reliably 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 logical unit 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 logical unit 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.5 Task Management Requests Affecting Multiple Tasks 6.5 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
skipping to change at page 17, line 43 skipping to change at page 18, line 53
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 (e.g., PDU formats, require different levels of protocol support (e.g., PDU formats,
end node semantics) for proper operation. end node semantics) for proper operation.
Negotiation of the iSCSIProtocolLevel key to a value Negotiation of the iSCSIProtocolLevel key to a value
corresponding to an RFC indicates that both negotiating parties corresponding to an RFC indicates that both negotiating parties
are compliant to the RFC in question, and agree to support the are compliant to the RFC in question, and agree to support the
corresponding PDU formats and semantics on that iSCSI session. corresponding PDU formats and semantics on that iSCSI session.
An operational value of iSCSI ProtocolLevel = "x" on an iSCSI Features using this key are expected to be cumulative.
session requires that the iSCSI protocol semantics on that iSCSI
session be a logical superset of the capabilities in all RFCs
that have claimed values of an iSCSIProtocolLevel less than "x".
An iSCSIProtocolLevel key negotiated to "0" indicates that the An iSCSIProtocolLevel key negotiated to "0" indicates that the
implementation does not claim a specific iSCSI protocol level. implementation does not claim a specific iSCSI protocol level.
An iSCSIProtocolLevel key negotiated to "1" indicates that the An iSCSIProtocolLevel key negotiated to "1" indicates that the
implementation claims compliance with [RFC-cons]. implementation claims compliance with [RFC-cons].
-------------------------------------------------------- --------------------------------------------------------
RFC EDITORS NOTE: The above reference to [RFC-cons] should RFC EDITORS NOTE: The above reference to [RFC-cons] should
reference the RFC number assigned to [draft-ietf-storm-iscsi- reference the RFC number assigned to [draft-ietf-storm-iscsi-
cons-xx], and this note should be removed. cons-xx], and this note should be removed.
-------------------------------------------------------- --------------------------------------------------------
An iSCSIProtocolLevel key negotiated to "2" is required to enable An iSCSIProtocolLevel key negotiated to "2" is required to enable
use of features defined in this RFC. 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
Poor implementations (those that do not observe the requirements Command priorities are relative values, not absolute values (see
described in [SAM5]) may allow the priority field (see 5.1.1) to [SAM5] and affect collections of commands, not necessarily
be used to create a denial of service attack. individual commands (see [SAM5]); if command priority is
supported, it should be implemented in a fashion that avoids
unwanted reduction or denial of service.
All the iSCSI-related security text in [RFC3723] is also directly All the iSCSI-related security text in [RFC3723] and the security
applicable to this document. text in [RFC-cons] is also directly applicable to this document.
-------------------------------------------------------- --------------------------------------------------------
RFC EDITORS NOTE: The above reference to [RFC-cons] should RFC EDITORS NOTE: The above reference to [RFC-cons] should
reference the RFC number assigned to [draft-ietf-storm-iscsi- reference the RFC number assigned to [draft-ietf-storm-iscsi-
cons-xx], and this note should be removed. cons-xx], and this note should be removed.
-------------------------------------------------------- --------------------------------------------------------
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
skipping to change at page 18, line 46 skipping to change at page 20, line 5
1. iSCSI Task Management Functions Codes 1. iSCSI Task Management Functions Codes
Name of the existing registry: "iSCSI TMF Codes" Name of the existing registry: "iSCSI TMF Codes"
The name of this registry should be changed to: "iSCSI Task The name of this registry should be changed to: "iSCSI Task
Management Function Codes". Management Function Codes".
Additional entries: Additional entries:
9, QUERY TASK, [RFCxxx] 9, QUERY TASK, [RFCxxx]
10, QUERY TASK SET, [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 RFC EDITORS NOTE: The above reference to [RFCxxx] should
reference this RFC, and this note should be removed. reference this RFC, and this note should be removed.
--------------------------------------------------------- ---------------------------------------------------------
2. iSCSI Login/Text Keys 2. iSCSI Login/Text Keys
Name of the existing registry: "iSCSI Text Keys" Name of the existing registry: "iSCSI Text Keys"
Fields to record in the registry: Assigned value and its Fields to record in the registry: Assigned value and its
associated RFC reference: associated RFC reference:
skipping to change at page 20, line 7 skipping to change at page 21, line 18
using this key are expected to be cumulative. For example, using this key are expected to be cumulative. For example,
since this draft explicitly lists only value 2 for the since this draft explicitly lists only value 2 for the
features listed in this draft, it is expected that a new RFC features listed in this draft, it is expected that a new RFC
assigning value 3 will also have the features listed in this assigning value 3 will also have the features listed in this
RFC and therefore such an RFC is expected to either revise or RFC and therefore such an RFC is expected to either revise or
replace this RFC. Assignments that do not follow this policy replace this RFC. Assignments that do not follow this policy
should be reviewed and approved by the INCITS T10 committee. should be reviewed and approved by the INCITS T10 committee.
3-31: range reserved by IANA for assignment in this registry. 3-31: range reserved by IANA for assignment in this registry.
Fields to record in the registry: Assigned value, and its Fields to record in the registry: Assigned value, description,
associated RFC reference. and its associated RFC reference.
0, [RFCxxx] 0, No version claimed, [RFCxxx]
1, [RFC-cons] 1, RFC-cons, [RFCxxx]
2, [RFCxxx] 2, RFCxxx, [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. The reference this RFC, and this note should be removed. The
above references to [RFC-cons] should reference the [draft- above reference to RFC-cons should be replaced with the name
ietf-storm-iscsi-cons-xx] document, and this note should be of the [draft-ietf-storm-iscsi-cons-xx] document, and this
note should be removed. All associated RFC references are to
this document; even the reference for value 1. The
description for value 1 however contains the RFC-cons name but
should not have [] around the description (it is a description
not a formal reference). The description for value 2 is the
name of this RFC but should not contain the [] (again, a
description not a formal reference). This note should be
removed. removed.
--------------------------------------------------------- ---------------------------------------------------------
Allocation Policy: Allocation Policy:
Expert review ([IANA]) and 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 Task Management Function Response Name of new registry: "iSCSI Task Management Function Response
Codes" Codes"
skipping to change at page 20, line 41 skipping to change at page 22, line 5
Name of new registry: "iSCSI Task Management Function Response Name of new registry: "iSCSI Task Management Function Response
Codes" 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, [RFC-cons] 0x0, Function complete, [RFC-cons]
0x1, Task does not exist, [RFC-cons] 0x1, Task does not exist, [RFC-cons]
0x2, LUN does not exist, [RFC-cons]
0x2, LUN does not exist, [RFC-cons]
0x3, Task still allegiant, [RFC-cons] 0x3, Task still allegiant, [RFC-cons]
0x4, Task allegiance reassignment not supported, [RFC-cons] 0x4, Task allegiance reassignment not supported, [RFC-cons]
0x5, Task management function not supported, [RFC-cons] 0x5, Task management function not supported, [RFC-cons]
0x6, Function authorization failed, [RFC-cons] 0x6, Function authorization failed, [RFC-cons]
0x7, Function succeeded, [RFCxxx] 0x7, Function succeeded, [RFCxxx]
skipping to change at page 21, line 46 skipping to change at page 23, line 11
[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.
[draft-ietf-storm-iscsi-cons-xx] Chadalapaka, M., Satran, J., [draft-ietf-storm-iscsi-cons-xx] Chadalapaka, M., Satran, J.,
Kalman, M., "iSCSI Protocol (consolidated)", RFC xxx, Kalman, M., "iSCSI Protocol (consolidated)", RFC xxx,
Date 2011. Date 2013.
------------------------------------------------------------ ------------------------------------------------------------
RFC EDITORS NOTE: The above references to [draft-ietf-storm- RFC EDITORS NOTE: The above references to [draft-ietf-storm-
iscsi-cons-xx] and [RFCxxx] should reference the RFC number iscsi-cons-xx] and RFC xxx should reference the RFC number
assigned to that draft, and this note should be removed. assigned to that draft, and this note should be removed.
------------------------------------------------------------ ------------------------------------------------------------
[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-
4).
[SAM5] T10/2104D rev r04, 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 r36, SCSI Primary Commands - 4 (SPC-4), [SPC4] T10/1731D rev r36, SCSI Primary Commands - 4 (SPC-4),
Committee Draft. Committee Draft.
10.2 Informative References 10.2 Informative References
[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
skipping to change at page 22, line 38 skipping to change at page 23, line 49
For more information on the SCSI Architecture Model and SCSI For more information on the SCSI Architecture Model and SCSI
Primary Commands - 4, contact the INCITS T10 Technical Committee Primary Commands - 4, contact the INCITS T10 Technical Committee
for SCSI Storage Interfaces at http://www.t10.org. for SCSI Storage Interfaces 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 and other IETF reviewers.
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.
------------------------------------------------------------ ------------------------------------------------------------
Author's Addresses RFC EDITORS NOTE: The above reference to [RFCxxx] should
reference this RFC, and this note should be removed.
------------------------------------------------------------
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
 End of changes. 67 change blocks. 
183 lines changed or deleted 191 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/