draft-ietf-storm-iscsi-sam-08.txt   draft-ietf-storm-iscsi-sam-09.txt 
Storage Maintenance (StorM) Working Group Frederick Knight Storage Maintenance (StorM) Working Group Frederick Knight
Internet Draft NetApp Internet Draft NetApp
Intended status: Standards Track M. Chadalapaka Intended status: Standards Track M. Chadalapaka
Expires: January 2014 Microsoft Expires: February 2014 Microsoft
July 2013 August 2013
Internet Small Computer Systems Interface (iSCSI) SCSI Features Internet Small Computer Systems Interface (iSCSI) SCSI Features
Update Update
draft-ietf-storm-iscsi-sam-08.txt draft-ietf-storm-iscsi-sam-09.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 RFCxxx (and as TCP/IP. The iSCSI protocol as specified in RFCxxx (and as
previously specified by the combination of RFC 3720 and RFC previously specified by the combination of RFC 3720 and RFC
5048) is based on the SAM-2 (SCSI Architecture Model - 2) 5048) is based on the SAM-2 (SCSI Architecture Model - 2)
version of the SCSI family of protocols. This document version of the SCSI family of protocols. This document
defines enhancements to the iSCSI protocol to support certain defines enhancements to the iSCSI protocol to support certain
skipping to change at page 1, line 54 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 January, 2014. This Internet-Draft will expire February, 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
skipping to change at page 2, line 38 skipping to change at page 2, line 38
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 .............................. 10 5.2 SCSI Response Additions .............................. 10
5.2.1 Status Qualifier ................................. 11 5.2.1 Status Qualifier ................................. 11
5.2.2 Data Segment - Sense and Response Data Segment ... 11 5.2.2 Data Segment - Sense and Response Data Segment ... 11
6. Task Management Functions.................................... 12 6. Task Management Functions.................................... 12
6.1 Existing Task Management Functions ................... 12 6.1 Task Management Function Request PDU ................. 12
6.2 Task Management Function Additions ................... 13 6.2 Existing Task Management Functions ................... 12
6.2.1 LUN field ........................................ 14 6.3 Task Management Function Additions ................... 13
6.2.2 Referenced Task Tag .............................. 14 6.3.1 LUN field ........................................ 14
6.2.3 RefCmdSN ......................................... 15 6.3.2 Referenced Task Tag .............................. 14
6.3 Task Management Function Responses ................... 16 6.3.3 RefCmdSN ......................................... 15
6.3.1 Task Management Function Response Additions ...... 17 6.4 Task Management Function Responses ................... 16
6.4 Task Management Requests Affecting Multiple Tasks .... 18 6.4.1 Task Management Function Response PDU ............ 16
6.4.2 Task Management Function Response Additions ...... 17
6.5 Task Management Requests Affecting Multiple Tasks .... 18
7. Login/Text Operational Text Keys............................. 18 7. Login/Text Operational Text Keys............................. 18
7.1 New Operational Text Keys ............................ 18 7.1 New Operational Text Keys ............................ 18
7.1.1 iSCSIProtocolLevel ............................... 18 7.1.1 iSCSIProtocolLevel ............................... 18
8. Security Considerations...................................... 19 8. Security Considerations...................................... 19
9. IANA Considerations.......................................... 19 9. IANA Considerations.......................................... 19
10. References.................................................. 22 10. References.................................................. 22
11. Acknowledgements............................................ 23 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
skipping to change at page 7, line 6 skipping to change at page 7, line 6
| || (TSIH = 56) || || (SSID = 48) || | | || (TSIH = 56) || || (SSID = 48) || |
| |+---------------------------+| |+------------------------------+| | | |+---------------------------+| |+------------------------------+| |
| | | | | | | | | | | |
| | iSCSI Target Node | | iSCSI Initiator Node | | | | iSCSI Target Node | | iSCSI Initiator Node | |
| +-----------------------------+ +--------------------------------+ | | +-----------------------------+ +--------------------------------+ |
| iSCSI Node | | iSCSI Node |
| (within Network Entity, not shown) | | (within Network Entity, not shown) |
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
4. New Feature Use 4. New Feature Use
4.1 Negotiation of New Feature Use 4.1 Negotiation of New Feature Use
The iSCSIProtocolLevel operational text key (see 7.1.1) The iSCSIProtocolLevel operational text key (see 7.1.1)
containing a value of "2" 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.
This is an iSCSI negotiation mechanism that enabled iSCSI support This is an iSCSI negotiation mechanism that enabled iSCSI support
for corresponding SCSI capabilities (see [SAM5] and [SPC4]. For for corresponding SCSI capabilities (see [SAM5] and [SPC4]. For
this reason, negotiation of this key to a value of "2" is this reason, negotiation of this key to a value of "2" is
necessary, but not sufficient for use of the SCSI capabilities necessary, but not sufficient for use of the SCSI capabilities
enabled by the iSCSI features in this RFC. enabled by the iSCSI features in this RFC.
skipping to change at page 8, line 11 skipping to change at page 8, line 11
draft author (Frederick Knight) and storm WG chair (David draft author (Frederick Knight) and storm WG chair (David
Black). 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 19, line 49 skipping to change at page 19, line 49
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
registries. The following iSCSI-related registries are modified: registries. The following iSCSI-related registries are modified:
1. iSCSI Task Management Functions Codes 1. iSCSI Task Management Functions Codes
Name of the existing registry: "iSCSI TMF Codes" Name of the existing registry: "iSCSI Task Management Function
Codes"
The name of this registry should be changed to: "iSCSI Task
Management Function Codes".
Additional entries: Additional entries:
9, QUERY TASK, [RFCxxx] 9, QUERY TASK, [RFCxxx]
10, QUERY TASK SET, [RFCxxx] 10, QUERY TASK SET, [RFCxxx]
11, I_T NEXUS RESET, [RFCxxx] 11, I_T NEXUS RESET, [RFCxxx]
12, QUERY ASYNCHRONOUS EVENT, [RFCxxx] 12, QUERY ASYNCHRONOUS EVENT, [RFCxxx]
13-127, Unassigned, [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. The last
entry (values 13-127 in the above list) should replace the
existing entry for the "Unassigned" values.
--------------------------------------------------------- ---------------------------------------------------------
2. iSCSI Login/Text Keys 2. iSCSI Login/Text Keys
Name of the existing registry: "iSCSI Text Keys" Name of the existing registry: "iSCSI Login/Text Keys"
Fields to record in the registry: Assigned value and its Fields to record in the registry: Assigned value and its
associated RFC reference: associated RFC reference:
iSCSIProtocolLevel, [RFCxxx] iSCSIProtocolLevel, [RFCxxx]
--------------------------------------------------------- ---------------------------------------------------------
RFC EDITORS NOTE: The above references to [RFCxxx] should RFC EDITORS NOTE: The above references to [RFCxxx] should
reference this RFC, and this note should be removed. reference this RFC, and this note should be removed.
--------------------------------------------------------- ---------------------------------------------------------
skipping to change at page 21, line 16 skipping to change at page 21, line 16
this registry. Compatibility and interoperability will be this registry. Compatibility and interoperability will be
adversely impacted if proper care is not exercised. Features adversely impacted if proper care is not exercised. Features
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 available to IANA for assignment in this registry.
Fields to record in the registry: Assigned value, description, Fields to record in the registry: Assigned value, description,
and its associated RFC reference. and its associated RFC reference.
0, No version claimed, [RFCxxx] 0, No version claimed, [RFCxxx]
1, RFC-cons, [RFCxxx] 1, RFC-cons, [RFCxxx]
2, RFCxxx, [RFCxxx] 2, RFCxxx, [RFCxxx]
3-31, Unassigned
--------------------------------------------------------- ---------------------------------------------------------
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 reference to RFC-cons should be replaced with the name above reference to RFC-cons should be replaced with the name
of the [draft-ietf-storm-iscsi-cons-xx] document, and this of the [draft-ietf-storm-iscsi-cons-xx] document, and this
note should be removed. All associated RFC references are to note should be removed. All associated RFC references are to
this document; even the reference for value 1. The this document; even the reference for value 1. The
description for value 1 however contains the RFC-cons name but description for value 1 however contains the RFC-cons name but
should not have [] around the description (it is a description should not have [] around the description (it is a description
not a formal reference). The description for value 2 is the not a formal reference). The description for value 2 is the
name of this RFC but should not contain the [] (again, a name of this RFC but should not contain the [] (again, a
description not a formal reference). This note should be 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 Function Response Codes
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 available to 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] 0, Function complete, [RFC-cons]
0x1, Task does not exist, [RFC-cons] 1, Task does not exist, [RFC-cons]
0x2, LUN does not exist, [RFC-cons] 2, LUN does not exist, [RFC-cons]
0x3, Task still allegiant, [RFC-cons] 3, Task still allegiant, [RFC-cons]
0x4, Task allegiance reassignment not supported, [RFC-cons] 4, Task allegiance reassignment not supported, [RFC-cons]
0x5, Task management function not supported, [RFC-cons] 5, Task management function not supported, [RFC-cons]
0x6, Function authorization failed, [RFC-cons] 6, Function authorization failed, [RFC-cons]
0x7, Function succeeded, [RFCxxx] 7, Function succeeded, [RFCxxx]
8-254, Unassigned
255, Function rejected, [RFC-cons] 255, Function rejected, [RFC-cons]
------------------------------------------------------------ ------------------------------------------------------------
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.
The above references to [RFC-cons] should reference the The above references to [RFC-cons] should reference the
[draft-ietf-storm-iscsi-cons-xx] document, and this note [draft-ietf-storm-iscsi-cons-xx] document, and this note
should be removed. should be removed.
skipping to change at page 23, line 50 skipping to change at page 24, line 4
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 and other IETF reviewers. 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 RFC EDITORS NOTE: The above reference to [RFCxxx] should
reference this RFC, and this note should be removed. reference this RFC, and this note should be removed.
------------------------------------------------------------ ------------------------------------------------------------
Author's Addresses: Author's Addresses:
Frederick Knight Frederick Knight
7301 Kit Creek Road 7301 Kit Creek Road
P.O. Box 13917 P.O. Box 13917
Research Triangle Park, NC 27709, USA Research Triangle Park, NC 27709, USA
Phone: +1-919-476-5362 Phone: +1-919-476-5362
 End of changes. 28 change blocks. 
43 lines changed or deleted 51 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/