17 March r1 SAM-4 SAS-2 QUERY TASK SET task management function

Size: px
Start display at page:

Download "17 March r1 SAM-4 SAS-2 QUERY TASK SET task management function"

Transcription

1 17 March r1 SAM-4 SAS-2 QUERY ASK SE task management function o: 10 echnical Committee From: Rob Elliott, HP Date: 17 March 2007 Subject: r1 SAM-4 SAS-2 QUERY ASK SE task management function Revision history Revision 0 (14 February 2007) First revision Revision 1 (17 March 2007) Incorporated comments from March 2007 FCP and CAP WG. Split the FCP-4 changes into Related documents sam4r08 - SCSI Architecture Model - 4 (SAM-4) revision 8 sas2r08 - Serial Attached SCSI - 2 (SAS-2) revision 8 fcp4r00 - Fibre Channel Protocol - 4 (FCP-4) revision SAM-4 SAS-2 QUERY UNI AENION task management function (Rob Elliott, HP) FCP-4 QUERY ASK task management function (Rob Elliott, HP) FCP-4 QUERY ASK SE task management function (Rob Elliott, HP) FCP-4 QUERY UNI AENION task management function (Rob Elliott, HP) Overview Just as ABOR ASK has a companion task management function called ABOR ASK SE that aborts all tasks in the task set from the specified I_ nexus, QUERY ASK should be joined by a task management function called QUERY ASK SE that reports FUNCION SUCCEEDED if there is any task in the task set from the specified I_ nexus. QUERY ASK SE can be used by an initiator to determine if all its tasks were aborted (e.g., due to a persistent reservations PREEMP AND ABOR, an I_ nexus loss, CLEAR ASK SE, LOGICAL UNI RESE, or a hard reset) without having to query each task one-by-one. he proposed semantics parallel ABOR ASK SE rather than CLEAR ASK SE. QUERY ASK SE only queries tasks in the task set from the specified I_ nexus, t tasks from any I_ nexus in the task set. Changes are proposed for SAM-4 and SAS-2. FCP-4 changes are proposed in iscsi could adopt this change when it is upgraded to SAM-4 from SAM-2. he AD editor is including this in the AD-3 work list. Suggested changes to SAM SCSI task router class he SCSI task router class routes information (e.g., commands and task management functions) between a logical unit and a service delivery subsystem using the route task operation. he task router routes commands and task management functions as follows: a) Commands addressed to a valid logical unit are routed to the task manager in the specified logical unit; b) Commands addressed to an incorrect logical unit are handled as described in 5.8.4; c) ask management functions with I L nexus scope (e.g., ABOR ASK SE, CLEAR ASK SE, QUERY ASK SE, CLEAR ACA, and LOGICAL UNI RESE) or I L_Q nexus scope (e.g., ABOR ASK and QUERY ASK) addressed to a valid logical unit are routed to the task manager in the specified logical unit; d) ask management functions with an I_ nexus scope (e.g., I_ NEXUS RESE) are routed to the task manager in each logical unit about which the task router kws; and e) ask management functions with I L nexus scope or I L_Q nexus scope addressed to an incorrect logical unit are handled as described in In some transport protocols, the task router may check for overlapped task tags on commands (see 5.8.3). 7.1 Introduction 1

2 07-066r1 SAM-4 SAS-2 QUERY ASK SE task management function 17 March 2007 An application client requests the processing of a task management function by invoking the SCSI transport protocol services described in 7.10, the collective operation of which is modeled in the following procedure call: Service Response = Function name (IN ( nexus )) he task management function names are summarized in table 34. able 34 ask Management Functions ask Management Function Nexus Reference ABOR ASK I L_Q 7.2 ABOR ASK SE I L 7.3 CLEAR ACA I L 7.4 CLEAR ASK SE I L 7.5 I_ NEXUS RESE I L 7.6 LOGICAL UNI RESE I L 7.7 QUERY ASK I L_Q 7.8 QUERY ASK SE I L 7.xx... One of the following SCSI transport protocol specific service responses shall be returned: FUNCION COMPLEE: A task manager response indicating that the requested function is complete. Unless ather response is required, the task manager shall return this response upon completion of a task management request supported by the logical unit or SCSI target device to which the request was directed. FUNCION SUCCEEDED: An optional task manager response indicating that the requested function is supported and completed successfully. his task manager response shall only be used by functions that require tification of success (e.g., QUERY ASK or QUERY ASK SE). FUNCION REJECED: An task manager response indicating that the requested function is t supported by the logical unit or SCSI target device to which the function was directed. INCORREC LOGICAL UNI NUMBER: An optional task router response indicating that the function requested processing for an incorrect logical unit number. SERVICE DELIVERY OR ARGE FAILURE: he request was terminated due to a service delivery failure (see ) or SCSI target device malfunction. he task manager may or may t have successfully performed the specified function. Each SCSI transport protocol standard shall define the events comprising each of these service responses. he task manager response to task management requests is subject to the presence of access restrictions, as managed by ACCESS CONROL OU and ACCESS CONROL IN commands (see SPC-3), as follows: a) A task management request of ABOR ASK, ABOR ASK SE, CLEAR ACA, I_ NEXUS RESE, or QUERY ASK, or QUERY ASK SE shall t be affected by the presence of access restrictions; b) A task management request of CLEAR ASK SE or LOGICAL UNI RESE received from a SCSI initiator port that is denied access to the logical unit, either because it has access rights or because it is in the pending-enrolled state, shall t cause any changes to the logical unit; and c) he task management function service response shall t be affected by the presence of access restrictions. 7.8 QUERY ASK 2

3 17 March r1 SAM-4 SAS-2 QUERY ASK SE task management function Request: Service Response = QUERY ASK (IN (I L_Q Nexus )) Description: SCSI transport protocols may or may t support QUERY ASK and may or may t require logical units accessible through SCSI target ports using such transport protocols to support QUERY ASK. he task manager shall return a response of FUNCION SUCCEEDED if the specified task is present in the task set, or FUNCION COMPLEE if the specified task is t present in the task set. he task manager in the specified logical unit shall return a service response as follows: a) if the specified task is present in the task set, FUNCION SUCCEEDED; and b) if the specified task is t present in the task set, FUNCION COMPLEE. 7.xx QUERY ASK SE Request: Service Response = QUERY ASK SE (IN (I L Nexus)) Description: SCSI transport protocols may or may t support QUERY ASK SE and may or may t require logical units accessible through SCSI target ports using such transport protocols to support QUERY ASK SE. he task manager in the specified logical unit shall return a service response as follows: a) if there is any task present in the task set from the specified I_ nexus, FUNCION SUCCEEDED; and b) if there is task present in the task set from the specified I_ nexus, FUNCION COMPLEE. Suggested changes to SAS PL_OC2:Overall_Control state frame transmission... his state shall t send a x Frame message containing a ASK frame for a task that only affects an I L_Q nexus (e.g., an ABOR ASK or QUERY ASK task management function (see SAM-4)) to any PL_PM state machine until this state has received one of the following messages for each x Frame message with the same I L_Q nexus: a) ransmission Status (ACK Received); b) ransmission Status (NAK Received); c) ransmission Status (ACK/NAK imeout); or d) ransmission Status (Connection Lost Without ACK/NAK). his state shall t send a x Frame message containing a ASK frame for a task that only affects an I L nexus (e.g., an ABOR ASK SE, CLEAR ASK SE, QUERY ASK SE, CLEAR ACA, or LOGICAL UNI RESE task management function (see SAM-4)) to any PL_PM state machine until this state has received one of the following messages for each x Frame message with the same I L nexus: a) ransmission Status (ACK Received); b) ransmission Status (NAK Received); c) ransmission Status (ACK/NAK imeout); or d) ransmission Status (Connection Lost Without ACK/NAK). his state shall t send a x Frame message containing a ASK frame for a task that only affects an I_ nexus (e.g., an I_ NEXUS RESE task management function (see SAM-4)) to any PL_PM state machine until this state has received one of the following messages for each x Frame message with the same I_ nexus: a) ransmission Status (ACK Received); b) ransmission Status (NAK Received); 3

4 07-066r1 SAM-4 SAS-2 QUERY ASK SE task management function 17 March 2007 c) ransmission Status (ACK/NAK imeout); or d) ransmission Status (Connection Lost Without ACK/NAK) ASK frame - ask Management Function information unit able 152 defines the ASK MANAGEMEN FUNCION field. able 152 ASK MANAGEMEN FUNCION field Code ask management function Uses LOGICAL UNI NUMBER field Uses AG OF ASK O BE MANAGED field Description 01h ABOR ASK yes yes he task manager shall perform the ABOR ASK task management function with L set to the value of the LOGICAL UNI NUMBER field and Q set to the value of the AG OF ASK O BE MANAGED field (see SAM-4). a 02h ABOR ASK SE yes he task manager shall perform the ABOR ASK SE task management function with L set to the value of the LOGICAL UNI NUMBER field (see SAM-4). a 04h CLEAR ASK SE yes he task manager shall perform the CLEAR ASK SE task management function with L set to the value of the LOGICAL UNI NUMBER field (see SAM-4). a 08h LOGICAL UNI RESE yes he task manager shall perform the LOGICAL UNI RESE task management function with L set to the value of the LOGICAL UNI NUMBER field (see SAM-4). a 10h I_ NEXUS RESE he task manager shall perform the I_ NEXUS RESE task management function (see SAM-4). a 20h Reserved 40h CLEAR ACA yes 80h QUERY ASK yes yes he task manager shall perform the CLEAR ACA task management function with L set to the value of the LOGICAL UNI NUMBER field (see SAM-4). a he task manager shall perform the QUERY ASK task management function with L set to the value of the LOGICAL UNI NUMBER field and Q set to the value of the AG OF ASK O BE MANAGED field (see SAM-4). a 81h QUERY ASK SE yes he task manager shall perform the QUERY ASK SE task management function with L set to the value of the LOGICAL UNI NUMBER field (see SAM-4). a 82h All others QUERY UNI AENION (proposed in 07-xxxr0) Reserved a he task manager shall perform the specified task management function with the I and arguments set to the initiator port and target port involved in the connection used to deliver the ASK frame. If the ASK MANAGEMEN FUNCION field contains a reserved or unsupported value, the task manager shall return a RESPONSE frame with the DAAPRES field set to RESPONSE_DAA and its RESPONSE CODE field set to ASK MANAGEMEN FUNCION NO SUPPORED. 4

5 17 March r1 SAM-4 SAS-2 QUERY ASK SE task management function If the ASK MANAGEMEN FUNCION field is set to ABOR ASK or QUERY ASK, the AG OF ASK O BE MANAGED field specifies the AG value from the COMMAND frame that contained the task to be aborted or checked. For all other task management functions, the AG OF ASK O BE MANAGED field shall be igred SCSI transport protocol services overview... An application client requests the processing of a SCSI command by invoking SCSI transport protocol services, the collective operation of which is conceptually modeled in the following remote procedure call (see SAM-4): Service response = Execute Command (IN (I L_Q Nexus, CDB, ask Attribute, [Data-In Buffer Size], [Data-Out Buffer], [Data-Out Buffer Size], [ask Priority]), OU ([Data-In Buffer], [Sense Data], [Sense Data Length], Status)) An application client requests the processing of a SCSI task management function by invoking SCSI transport protocol services, the collective operation of which is conceptually modeled in the following remote procedure calls (see SAM-4): a) Service Response = ABOR ASK (IN (Nexus)); b) Service Response = ABOR ASK SE (IN (Nexus)); c) Service Response = CLEAR ACA (IN (Nexus)); d) Service Response = CLEAR ASK SE (IN (Nexus)); e) Service Response = I_ NEXUS RESE (IN (Nexus)); f) Service Response = LOGICAL UNI RESE (IN (Nexus)); and g) Service Response = QUERY ASK (IN (Nexus)).; and h) Service Response = QUERY ASK SE (IN (Nexus)). SSP defines the transport protocol services required by SAM-4 in support of the these remote procedure calls. 5

6 07-066r1 SAM-4 SAS-2 QUERY ASK SE task management function 17 March 2007 able 180 describes the mapping of the remote procedure calls to transport protocol services and the SSP implementation of each transport protocol service. able 180 SCSI architecture mapping Remote procedure call ype of transport protocol service ransport protocol service interaction ransport protocol service I/ a SSP implementation Execute Command ABOR ASK, ABOR ASK SE, CLEAR ACA, CLEAR ASK SE, I_ NEXUS RESE, LOGICAL UNI RESE, and QUERY ASK, and QUERY ASK SE a b Request/ Data-In ransfer b Data-Out ransfer b erminate Data ransfer b Request/ Request Indication Response Send SCSI Command SCSI Command Received Send Command Complete Command Complete Received I I COMMAND frame Receipt of the COMMAND frame RESPONSE frame Receipt of the RESPONSE frame or problem transmitting the COMMAND frame Request Send Data-In Read DAA frames Data-In Delivered Receipt of ACKs for the read DAA frames Request Receive Data-Out XFER_RDY frame Data-Out Received Request Request Indication Response erminate Data ransfer Data ransfer erminated Send ask Management Request ask Management Request Received ask Management Function Executed Received ask Management Function Executed I I Receipt of write DAA frames ASK frame Receipt of the ASK frame RESPONSE frame Receipt of the RESPONSE frame or problem transmitting the ASK frame I/ indicates whether the SSP initiator port (I) or the SSP target port () implements the transport protocol service. Data transfer transport protocol services for SCSI initiator ports are t specified by SAM Send ask Management Request transport protocol service An application client uses the Send ask Management Request transport protocol service request to request that an SSP initiator port transmit a ASK frame. 6

7 17 March r1 SAM-4 SAS-2 QUERY ASK SE task management function Send ask Management Request (IN (Nexus, Function Identifier, [Association])) able 191 shows how the arguments to the Send ask Management Request transport protocol service are used. able 191 Send ask Management Request transport protocol service arguments Argument Nexus Function Identifier [Association] SAS SSP implementation I L nexus or I L_Q nexus (depending on the Function Identifier), where: a) I specifies the initiator port to send the ASK frame; b) specifies the target port to which the ASK frame is sent; c) L specifies the LOGICAL UNI NUMBER field in the ASK frame header; and d) Q (for an I L_Q nexus) specifies the AG OF ASK O BE MANAGED field in the ASK frame header. Specifies the ASK MANAGEMEN FUNCION field in the ASK frame. Only these task management functions are supported: a) ABOR ASK (Nexus argument specifies an I L_Q Nexus); b) ABOR ASK SE (Nexus argument specifies an I L Nexus); c) CLEAR ACA (Nexus argument specifies an I L Nexus); d) CLEAR ASK SE (Nexus argument specifies an I L Nexus); e) I_ NEXUS RESE (Nexus argument specifies an I_ Nexus); f) LOGICAL UNI RESE (Nexus argument specifies an I L Nexus); and g) QUERY ASK (Nexus argument specifies an I L_Q Nexus).; and h) QUERY ASK SE (Nexus argument specifies an I L Nexus). Specifies the AG field in the ASK frame header ask Management Request Received transport protocol service An SSP target port uses the ask Management Request Received transport protocol service indication to tify a task manager that it has received a ASK frame. ask Management Request Received (IN (Nexus, Function Identifier, [Association])) 7

8 07-066r1 SAM-4 SAS-2 QUERY ASK SE task management function 17 March 2007 able 192 shows how the arguments to the ask Management Request Received transport protocol service are determined. able 192 ask Management Request Received transport protocol service arguments Argument Nexus Function Identifier [Association] SAS SSP implementation I L nexus or I L_Q nexus (depending on the Function Identifier), where: a) I indicates the initiator port that sent the ASK frame; b) indicates the target port that received the ASK frame; c) L indicated by the LOGICAL UNI NUMBER field in the ASK frame header; and d) Q (for an I L_Q nexus) indicated by the AG OF ASK O BE MANAGED field in the ASK frame header. Indicates the ASK MANAGEMEN FUNCION field in the ASK frame. Only these task management functions are supported: a) ABOR ASK (Nexus argument specifiesindicates an I L_Q Nexus); b) ABOR ASK SE (Nexus argument specifiesindicates an I L Nexus); c) CLEAR ACA (Nexus argument specifiesindicates an I L Nexus); d) CLEAR ASK SE (Nexus argument specifiesindicates an I L Nexus); e) I_ NEXUS RESE (Nexus argument specifiesindicates an I_ Nexus); f) LOGICAL UNI RESE (Nexus argument specifiesindicates an I L Nexus); and g) QUERY ASK (Nexus argument specifiesindicates an I L_Q Nexus).; and h) QUERY ASK SE (Nexus argument indicates an I L Nexus). Indicates the AG field in the ASK frame header. 8

17 March r1 SAM-4 SAS-2 QUERY UNIT ATTENTION task management function

17 March r1 SAM-4 SAS-2 QUERY UNIT ATTENTION task management function To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 17 March 2007 Subject: 07-067r1 SAM-4 SAS-2 QUERY UNIT ATTENTION task management function Revision history Revision 0 (13 February

More information

04-372r1 SAM-4 SPC-4 SAS-1.1 I_T NEXUS RESET task management function 13 November 2004

04-372r1 SAM-4 SPC-4 SAS-1.1 I_T NEXUS RESET task management function 13 November 2004 To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 13 November 2004 Subject: 04-372r1 SAM-4 SPC-4 SAS-1.1 I_T NEXUS RESET task management function Revision history Revision 0 (5 November

More information

04-372r0 SAM-4 SPC-3 SAS-1.1 I_T NEXUS LOSS task management function 5 November 2004

04-372r0 SAM-4 SPC-3 SAS-1.1 I_T NEXUS LOSS task management function 5 November 2004 To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 5 November 2004 Subject: 04-372r0 SAM-4 SPC-3 SAS-1.1 I_T NEXUS LOSS task management function Revision history Revision 0 (5 November

More information

6 June r0 SAM-4 SCSI Initiator Port and Target Port capabilities attributes

6 June r0 SAM-4 SCSI Initiator Port and Target Port capabilities attributes 6 June 2007 07-263r0 SAM-4 SCSI Initiator Port and Target Port capabilities attributes To: T10 Technical Committee From: Rob Elliott (elliott@hp.com) Date: 6 June 2007 Subject: 07-263r0 SAM-4 SCSI Initiator

More information

10 May r1 SAM-4 TASK ABORTED status clarifications

10 May r1 SAM-4 TASK ABORTED status clarifications 10 May 2007 06-026r1 SAM-4 TASK ABORTED status clarifications To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 10 May 2007 Subject: 06-026r1 SAM-4 TASK ABORTED status clarifications

More information

Item 2) In clause PL_OC2:Overall_Control state frame transmission cancellations: change the text to be as follows:

Item 2) In clause PL_OC2:Overall_Control state frame transmission cancellations: change the text to be as follows: a Maxtor Corporation 500 McCarthy Boulevard Milpitas, CA 95035 USA To: T10 SAS Protocol Working Group Contact: Mark Evans Phone: 408-894-5310 Email: mark_evans@maxtor.com Date: 23 February 2004 Subject:

More information

Revision history Revision 0 (9 October 2002) first revision Revision 1 (6 November 2002) Incorporated comments from CAP WG.

Revision history Revision 0 (9 October 2002) first revision Revision 1 (6 November 2002) Incorporated comments from CAP WG. To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 6 November 2002 Subject: T10/02-404r1 SAM-3 Data In Size and Sense Data Size for Execute Command Revision history Revision 0 (9

More information

03-351r1 SAM-3 SPC-3 Task Attributes VPD page 11 December 2003

03-351r1 SAM-3 SPC-3 Task Attributes VPD page 11 December 2003 To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 11 December 2003 Subject: 03-351r1 SAM-3 SPC-3 Task Attributes VPD page Revision history Revision 0 (14 October 2003) First revision

More information

03-186r5 SAS-1.1 Transport layer retries 13 January 2004

03-186r5 SAS-1.1 Transport layer retries 13 January 2004 To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 13 January 2004 Subject: 03-186r5 SAS-1.1 Transport layer retries Revision history Revision 0 (6 May 2003) first revision Revision

More information

03-186r3r3 SAS-1.1 Transport layer retries 25 October 2003

03-186r3r3 SAS-1.1 Transport layer retries 25 October 2003 To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 25 October 2003 Subject: 03-186r3r3 SAS-1.1 Transport layer retries Revision history Revision 0 (6 May 2003) first revision Revision

More information

12 January r1 SAS2: ST_TTS retransmitted DATA frames

12 January r1 SAS2: ST_TTS retransmitted DATA frames To: T10 Technical Committee From: Bob Sheffield (Robert.L.Sheffield@intel.com) Date: 12 January 2007 Subject: 06-371r1 SAS2: ST_TTS retransmitted DATA frames Revision history Revision 0 (20 July 2006)

More information

T10/03-229r1 SAS-1.1 Transport layer retries ladder diagrams

T10/03-229r1 SAS-1.1 Transport layer retries ladder diagrams To: T10 Technical Committee From: Jim Jones, Quantum (jim.jones@quantum.com) and Rob Elliott, HP (elliott@hp.com) Date: 11 August 2003 Subject: T10/03-229r1 SAS-1.1 Transport Layer Retries ladder diagrams

More information

03-344r4 SPC-3 SAM-3 Report all initiator and target ports 9 February 2004

03-344r4 SPC-3 SAM-3 Report all initiator and target ports 9 February 2004 To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 9 February 2004 Subject: 0-44r4 SPC- SAM- Report all initiator and target ports Revision history Revision 0 (6 October 200) First

More information

T10/01-134r Page 1 of 13

T10/01-134r Page 1 of 13 To: T10 Technical Committee From: Rob Elliott, Compaq Computer Corporation (Robert.Elliott@compaq.com) Date: 18 July 2001 Subject: SAM-2, SPC-3, SPI-4, SBC-2 WAKEUP and reset cleanup T10/01-134r2 Revision

More information

04-340r0 SAS-1.1 OPEN_REJECT BAD DESTINATION handling 18 October 2004

04-340r0 SAS-1.1 OPEN_REJECT BAD DESTINATION handling 18 October 2004 To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 18 October 2004 Subject: 04-340r0 SAS-1.1 OPEN_REJECT BAD DESTINATION handling Revision history Revision 0 (18 October 2004) First

More information

T10/03-229r0 SAS-1.1 Transport layer retries ladder diagrams

T10/03-229r0 SAS-1.1 Transport layer retries ladder diagrams To: T10 Technical Committee From: Jim Jones, Quantum (jim.jones@quantum.com) and Rob Elliott, HP (elliott@hp.com) Date: 25 June 2003 Subject: T10/03-229r0 SAS-1.1 Transport Layer Retries ladder diagrams

More information

T10/03-186r2 SAS-1.1 Transport layer retries

T10/03-186r2 SAS-1.1 Transport layer retries To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) and Jim Jones, Quantum (jim.jones@quantum.com) Date: 28 July 2003 Subject: T10/03-186r1 SAS-1.1 Transport layer retries T10/03-186r2 SAS-1.1

More information

03-344r2 SPC-3 SAM-3 Report all initiator and target ports 30 December 2003

03-344r2 SPC-3 SAM-3 Report all initiator and target ports 30 December 2003 To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 0 December 200 Subject: 0-44r2 SPC- SAM- Report all initiator and target ports Revision history Revision 0 (6 October 200) First

More information

T10/02-230r1. Maxtor Corporation 500 McCarthy Boulevard Milpitas, CA USA

T10/02-230r1. Maxtor Corporation 500 McCarthy Boulevard Milpitas, CA USA Maxtor Corporation 500 McCarthy Boulevard Milpitas, CA 95035 USA To: Serial Attached SCSI Protocol Working Group From: Mark Evans Phone: 408-894-5310 Email: mark_evans@maxtor.com Date: 08 July 2002 Subject:

More information

22 March r1 FCP-4 QUERY TASK task management function

22 March r1 FCP-4 QUERY TASK task management function To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 22 March 2007 Subject: 07-072r1 FCP-4 QUERY TASK task management function Revision history Revision 0 (14 February 2007) First revision

More information

2.0.3 attributes: A named property of a class that describes the range of values that the class or its instances (i.e., objects) may hold.

2.0.3 attributes: A named property of a class that describes the range of values that the class or its instances (i.e., objects) may hold. T0/04-023 revision 2 Date: September 06, 2005 To: T0 Committee (SCSI) From: George Penokie (IBM/Tivoli) Subject: SAM-4: Converting to UML part Overview The current SCSI architecture follows no particular

More information

Related Documents ses2r00 - SCSI Enclosure Services - 2 revision r0 - SES-2 INVOP for Threshold In page

Related Documents ses2r00 - SCSI Enclosure Services - 2 revision r0 - SES-2 INVOP for Threshold In page To: T10 Technical Committee From: Dennis Spicher (dennis.spicher@hp.com) and Rob Elliott, HP (elliott@hp.com) Date: 18 July 00 Subject: Revision History Revision 0 (8 June 00) first revision Revision 1

More information

2.0.3 attributes: A named property of a class that describes the range of values that the class or its instances (i.e., objects) may hold.

2.0.3 attributes: A named property of a class that describes the range of values that the class or its instances (i.e., objects) may hold. T0/06-6 revision 0 Date: March 0, 2006 To: T0 Committee (SCSI) From: George Penokie (IBM/Tivoli) Subject: SAM-4: Converting to UML part Overview The current SCSI architecture follows no particular documentation

More information

Revision History Related Documents Overview 1. iscsi port names and device names Suggestion 2. iscsi logical unit names Suggestion

Revision History Related Documents Overview 1. iscsi port names and device names Suggestion 2. iscsi logical unit names Suggestion To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 12 March 2003 Subject: T10/02-419r2 SAM-3 SPC-3 SAS FCP-3 SRP-2 Device identifiers and VPD data Revision History Revision 0 (2 November

More information

SERIAL ATTACHED SCSI (SAS) CONSORTIUM

SERIAL ATTACHED SCSI (SAS) CONSORTIUM SERIAL ATTACHED SCSI (SAS) CONSORTIUM Clause 8 SAS SPL Target Error Handling Test Suite Version0.3 Technical Document Last Updated: 6 September 2011 Serial Attached SCSI Consortium 121 Technology Drive,

More information

Revision History Revision 0 (2 November 2002) first revision Revision 1 (31 December 2002) incorporated comments from November CAP WG.

Revision History Revision 0 (2 November 2002) first revision Revision 1 (31 December 2002) incorporated comments from November CAP WG. To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 31 December 2002 Subject: T10/02-419r1 SAM-3 SPC-3 SAS FCP-3 SRP-2 Device identifiers and VPD data Revision History Revision 0 (2

More information

2.0.3 attributes: A named property of a class that describes the range of values that the class or its instances (i.e., objects) may hold.

2.0.3 attributes: A named property of a class that describes the range of values that the class or its instances (i.e., objects) may hold. T0/06-6 revision 2 Date: May 22, 2006 To: T0 Committee (SCSI) From: George Penokie (IBM/Tivoli) Subject: SAM-4: Converting to UML part Overview The current SCSI architecture follows no particular documentation

More information

9 January r0 SAS-2 SPC-4 Enabling and disabling Transport Layer Retries

9 January r0 SAS-2 SPC-4 Enabling and disabling Transport Layer Retries To: T10 Technical Committee From: Chris Martin (chris.martin@hp.com) and Rob Elliott, HP (elliott@hp.com) Date: 9 January 2007 Subject: 07-027r0 SAS-2 SPC-4 Enabling and disabling Transport Layer Retries

More information

04-352r0 SAS-1.1 Phy test functions for SMP 29 October 2004

04-352r0 SAS-1.1 Phy test functions for SMP 29 October 2004 To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 29 October 2004 Subject: 04-352r0 SAS-1.1 Phy test functions for SMP Revision history Revision 0 (29 October 2004) First revision

More information

16 July r1 SAS-2 Add device slot numbering fields to DISCOVER

16 July r1 SAS-2 Add device slot numbering fields to DISCOVER 16 July 2008 08-183r1 SAS-2 Add device slot numbering fields to DISCOVER To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 16 July 2008 Subject: 08-183r1 SAS-2 Add device slot numbering

More information

Revisions. Introduction. Proposal

Revisions. Introduction. Proposal To: INCITS Technical Committee T10 From: Kevin Butt Date: Printed Wednesday, January 23, 2008 10:01 am Document: T10/08-025r3 Persistent Reservations - Team Revisions 1. 08-025r0 Initial revision (10 December

More information

Serial Attached SCSI Comparison to Fibre Channel with FCP

Serial Attached SCSI Comparison to Fibre Channel with FCP Serial Attached SCSI Comparison to Fibre Channel with FCP by Rob Elliott HP Industry Standard Servers Server Storage Advanced Technology elliott@hp.com http://www.hp.com 30 September 2003 Notice These

More information

04-374r0 SES-2 Define a SAS Expander element 7 November 2004

04-374r0 SES-2 Define a SAS Expander element 7 November 2004 To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 7 November 2004 Subject: 04-374r0 SES-2 Define a SAS Expander element Revision history Revision 0 (7 November 2004) First revision

More information

Revisions. Introduction. Proposal

Revisions. Introduction. Proposal To: INCITS Technical Committee T10 From: Kevin Butt Date: Printed Monday, January 07, 2008 6:31 pm Document: T10/08-025r1 Persistent Reservations - Team Revisions 1. 08-025r0 Initial revision (10 December

More information

7 April r0 SAS-2 SMP function result for incomplete descriptor lists

7 April r0 SAS-2 SMP function result for incomplete descriptor lists 7 April 2007 07-176r0 SAS-2 SMP function result for incomplete descriptor lists To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 7 April 2007 Subject: 07-176r0 SAS-2 SMP function

More information

04-340r1 SAS-1.1 OPEN_REJECT BAD DESTINATION handling 24 December 2004

04-340r1 SAS-1.1 OPEN_REJECT BAD DESTINATION handling 24 December 2004 To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 24 December 2004 Subject: 04-340r1 SAS-1.1 OPEN_REJECT BAD DESTINATION handling Revision history Revision 0 (18 October 2004) First

More information

SAM-2 Letter Ballot comment HP 71 expressed a concern long held by the SAM-2/3 editor, to whit:

SAM-2 Letter Ballot comment HP 71 expressed a concern long held by the SAM-2/3 editor, to whit: ENDL TEXAS Date: 2 April 2003 To: T10 Technical Committee From: Ralph O. Weber Subject: Remove ULP and LLP from SAM-3 SAM-2 Letter Ballot comment HP 71 expressed a concern long held by the SAM-2/3 editor,

More information

16 January r3 SAM-4 SPC-4 SBC-3 Unit attention condition queuing

16 January r3 SAM-4 SPC-4 SBC-3 Unit attention condition queuing 16 January 2008 07-459r3 SAM-4 SPC-4 SBC-3 Unit attention condition queuing To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 16 January 2008 Subject: 07-459r3 SAM-4 SPC-4 SBC-3

More information

4 July r1 SAS-2 Enable and disable zoning

4 July r1 SAS-2 Enable and disable zoning To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 4 July 2006 Subject: 06-281r1 SAS-2 Enable and disable zoning Revision history Revision 0 (15 June 2006) First revision Revision

More information

04-172r1 SAS-2 More counters 11 September 2005

04-172r1 SAS-2 More counters 11 September 2005 To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 11 September 2005 Subject: 04-172r1 SAS-2 More ers Revision history Revision 0 (21 June 2004) First revision Revision 1 (11 September

More information

Storage Maintenance (StorM) Working Group. Intended status: Standards Track. December 2011

Storage Maintenance (StorM) Working Group. Intended status: Standards Track. December 2011 Storage Maintenance (StorM) Working Group Internet Draft Intended status: Standards Track Expires: June 2012 Frederick Knight NetApp M. Chadalapaka Microsoft December 2011 Internet Small Computer Systems

More information

10.2 SCSI application layer

10.2 SCSI application layer 2 November 2007 07-479r0 SAS-2 Phy test pattern transmitter controls To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 2 November 2007 Subject: 07-479r0 SAS-2 Phy test pattern transmitter

More information

2 May r2 SAS-2 WWN-based Attached Device Name for SATA

2 May r2 SAS-2 WWN-based Attached Device Name for SATA To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 2 May 2007 Subject: 06-476r2 SAS-2 WWN-based Attached Device Name for SATA Revision history Revision 0 (31 October 2006) First revision

More information

8 January r3 SAS-2 More counters

8 January r3 SAS-2 More counters 8 January 2006 04-172r3 SAS-2 More ers To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 8 January 2006 Subject: 04-172r3 SAS-2 More ers Revision history Revision 0 (21 June 2004)

More information

04-374r2 SES-2 Define a SAS Expander element 13 January 2005

04-374r2 SES-2 Define a SAS Expander element 13 January 2005 To: T0 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 3 January 2005 Subject: 04-374r2 SES-2 Define a SAS Expander element Revision history Revision 0 (7 November 2004) First revision

More information

06-378r0: SAT - Miscellaneous changes 18 August 2006

06-378r0: SAT - Miscellaneous changes 18 August 2006 To: T10 Technical Committee From: Bob Sheffield(robert.l.sheffield@intel.com) Date: 18 August 2006 Subject: 06-378r0: SAT - Miscellaneous changes Revision history Revision 0 (18 August 2006) First revision

More information

Internet Engineering Task Force (IETF) Request for Comments: April Internet Small Computer System Interface (iscsi) SCSI Features Update

Internet Engineering Task Force (IETF) Request for Comments: April Internet Small Computer System Interface (iscsi) SCSI Features Update Internet Engineering Task Force (IETF) Request for Comments: 7144 Category: Standards Track ISSN: 2070-1721 F. Knight NetApp M. Chadalapaka Microsoft April 2014 Internet Small Computer System Interface

More information

Revision History Revision 0 (09 December 2007) first revision

Revision History Revision 0 (09 December 2007) first revision To: T10 Technical Committee From: Jeff Wolford, HP (jeff.wolford@hp.com) Date: 09 December 2007 Subject: T10/08-019r0 SAT-2 WRITE BUFFER MODE 7 to DOWNLOAD MICROCODE Mode 3 Revision History Revision 0

More information

03-388r2 SPC-3 SBC-2 Nonvolatile caches 10 March 2004

03-388r2 SPC-3 SBC-2 Nonvolatile caches 10 March 2004 To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 10 March 2004 Subject: 03-388r2 SPC-3 SBC-2 Nonvolatile caches Revision history Revision 0 (11 December 2003) First revision Revision

More information

Overview This proposes topics and text for an InfiniBand annex for the SCSI over RDMA (SRP) standard.

Overview This proposes topics and text for an InfiniBand annex for the SCSI over RDMA (SRP) standard. To: From: T10 Technical Committee Greg Pellegrino (Greg.Pellegrino@compaq.com) and Rob Elliott, Compaq Computer Corporation (Robert.Elliott@compaq.com) Date: 19 June 2001 Subject: SRP InfiniBand annex

More information

02-360r3 SAS spinup 25 October 2002

02-360r3 SAS spinup 25 October 2002 To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 25 October 2002 Subject: 02-360r3 SAS spinup Revision Histy Revision 0 (10 September 2002) First revision Revision 1 (13 October

More information

Revision 1: Correct editorial issues identified at the 22 September 2003 working group conference call.

Revision 1: Correct editorial issues identified at the 22 September 2003 working group conference call. To: From: INCITS T10 Committee Paul Entzel, Quantum Date: 20 October 2003 Document: Subject: T10/03-322r2 Transport protocol service extensions for ADT. 1 Revision History Revision 0: Initial revision.

More information

ADT Frame Format Notes (Paul Suhler) ADI ADT Frame Format Proposal (Rod Wideman)

ADT Frame Format Notes (Paul Suhler) ADI ADT Frame Format Proposal (Rod Wideman) To: INCITS T10 Membership From: Paul Entzel, Quantum Date: 11 November 2002 Document: T10/02-329r2 Subject: Proposed frame format for ADT 1 Related Documents T10/02-233r0 T10/02-274r0 ADT Frame Format

More information

TCG. TCG Storage Interface Interactions Specification. Specification Version 1.0. January 27, Contacts:

TCG. TCG Storage Interface Interactions Specification. Specification Version 1.0. January 27, Contacts: TCG Storage Interface Interactions Specification January 27, 2009 Contacts: storagewg@trustedcomputinggroup.org Copyright TCG 2009 TCG Copyright 2009 Trusted Computing Group, Incorporated. Disclaimer,

More information

T10/06-119r0 SAS-2 BREAK_REPLY 28 February 2006

T10/06-119r0 SAS-2 BREAK_REPLY 28 February 2006 T10/06-119r0 SAS-2 _REPLY 28 February 2006 To: T10 Technical Committee From: Timothy Hoglund, LSI Logic Date: 28 February 2006 Subject: Serial Attached SCSI - 2 (SAS-2) Revision History Revision 0 (28

More information

Add the following section to REPORT SUPPORTED OPERATION CODES command.

Add the following section to REPORT SUPPORTED OPERATION CODES command. Page 1 of 7 Self Describing Cmd Timouts.fm/05-284r4 November 8, 2006 To: INCITS Technical Committee T10 From: Kevin Butt, IBM Date: November 8, 2006 12:48 pm Document: T10/05-284r4 Subject: SPC-4: Self

More information

04-075r0 SBC-2 Obsolete more features 27 February 2004

04-075r0 SBC-2 Obsolete more features 27 February 2004 To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 27 February 200 Subject: 0-075r0 SBC-2 Obsolete more features Revision history Revision 0 (27 February 200) First revision Related

More information

Table 1 Revision History

Table 1 Revision History Western Digital Corporation 20511 Lake Forest Drive Lake Forest, CA 92630 To: T10 CAP Working Group Contact: Curtis E. Stevens Phone: 949-672-7933 Email: Curtis.Stevens@wdc.com Date: January 15, 2000 Subject:

More information

04-218r1 SAT SPC-3 INQUIRY contents 29 July 2004

04-218r1 SAT SPC-3 INQUIRY contents 29 July 2004 To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 29 July 200 Subject: 0-218r1 SAT SPC-3 INQUIRY contents Revision history Revision 0 (8 July 200) First revision Revision 1 (29 July

More information

INTERNATIONAL STANDARD

INTERNATIONAL STANDARD INTERNATIONAL STANDARD ISO/IEC 14776-413 First edition 2007-02 Information technology Small computer system interface (SCSI) Part 413: Architecture model-3 (SAM-3) Reference number ISO/IEC 14776-413:2007(E)

More information

HP LTO Ultrium Tape Drives Technical Reference Manual Volume 3: Host Interface Guide

HP LTO Ultrium Tape Drives Technical Reference Manual Volume 3: Host Interface Guide HP LTO Ultrium Tape Drives Technical Reference Manual Volume : Host Interface Guide LTO drives Abstract This is one of five volumes that document HP LTO Ultrium tape drives (Fibre Channel and SAS). This

More information

2.0.3 attributes: A named property of a class that describes the range of values that the class or its instances (i.e., objects) may hold.

2.0.3 attributes: A named property of a class that describes the range of values that the class or its instances (i.e., objects) may hold. Date: May 05, 2004 To: T0 Committee (SCSI) From: George Penokie (IBM/Tivoli) Subject: SAM-3: Converting to UML part Overview The current SCSI architecture follows no particular documentation convention

More information

Information technology - Small Computer System Interface - Part 412: SCSI Architecture Model - 2 (SAM-2)

Information technology - Small Computer System Interface - Part 412: SCSI Architecture Model - 2 (SAM-2) 14776-412 Information technology - Small Computer System Interface - Part 412: SCSI Architecture Model - 2 (SAM-2) Reference number 14776-412 ISO/IEC:2003 Printed Monday, March 10, 2003 5:13 PM ISO/IEC

More information

4 General. 4.1 Architecture. T10/ revision 1

4 General. 4.1 Architecture. T10/ revision 1 T0/04-042 revision Date: 2/25/04 To: T0 Committee (SCSI) From: George Penokie (IBM/Tivoli) Subject: SAS UML Corrections 4 General 4. Architecture 4.. Architecture overview. SAS UML Corrections 24 T0/04-042

More information

4 General. 4.1 Architecture. T10/ revision 4

4 General. 4.1 Architecture. T10/ revision 4 T0/04-042 revision 4 Date: 9/3/04 To: T0 Committee (SCSI) From: George Penokie (IBM/Tivoli) Subject: SAS UML Corrections 4 General 4. Architecture 4.. Architecture overview. SAS UML Corrections 24 T0/04-042

More information

05-023r0 SAS-1.1 Connector figures 23 December 2004

05-023r0 SAS-1.1 Connector figures 23 December 2004 To: T10 Technical Committee From: Jerry Kachlic, Molex (Jerry.Kachlic@molex.com) and Rob Elliott, HP (elliott@hp.com) Date: 23 December 2004 Subject: 05-023r0 SAS-1.1 Connector figures Revision history

More information

04-247r0 SAS-1.1 XL6 and idle dwords 8 September 2004

04-247r0 SAS-1.1 XL6 and idle dwords 8 September 2004 To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 8 September 2004 Subject: 04-247r0 SAS-1.1 XL6 and idle dwords Revision history Revision 0 (8 September 2004) First revision Related

More information

2.0.3 attributes: A named property of a class that describes the range of values that the class or its instances (i.e., objects) may hold.

2.0.3 attributes: A named property of a class that describes the range of values that the class or its instances (i.e., objects) may hold. Date: December 23, 2003 To: T10 Committee (SCSI) From: George Penokie (IBM/Tivoli) Subject: SAM-3: Converting to UML part 1 1 Overview The current SCSI architecture follows no particular documentation

More information

03-364r1 MSC Report Bridge Mapping command 27 February 2004

03-364r1 MSC Report Bridge Mapping command 27 February 2004 To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 27 February 2004 Subject: 03-364r1 MSC Report Bridge Mapping command Revision history Revision 0 (23 October 2003) First revision

More information

Information on IEEE company IDs may be found at

Information on IEEE company IDs may be found at To: T0 Technical Committee From: Rob Elliott, Compaq Computer Corporation (Robert.Elliott@compaq.com) Date: March 00 Subject: SPC-3 VPD Page 83 Device Identifier rewrite Revision History Revision 0: (

More information

Table 21. OOB signal transmitter requirements Idle time minimum. maximum 175 ns

Table 21. OOB signal transmitter requirements Idle time minimum. maximum 175 ns To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 28 June 2002 Subject: T10/02-198r4 SAS OOB timing T10/02-198r4 SAS OOB timing Revision History Revision 0 (20 May 2002) first revision

More information

Revisions. General. T10 Membership FROM: Paul A. Suhler, Quantum Corporation DATE: 29 May 2008 SUBJECT: T10/07-469r4, ADT-2: Internet ADT (iadt)

Revisions. General. T10 Membership FROM: Paul A. Suhler, Quantum Corporation DATE: 29 May 2008 SUBJECT: T10/07-469r4, ADT-2: Internet ADT (iadt) TO: T10 Membership FROM: Paul A. Suhler, Quantum Corporation DATE: 29 May 2008 SUBJECT: T10/07-469r4, -2: Internet (i) Revisions 0 Initial revision (2 November 2007) 1 First revision (9 March 2008) Changed

More information

Revision history Related documents Overview Suggested changes to SAT Approved references

Revision history Related documents Overview Suggested changes to SAT Approved references To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) and Jeff Wolford, HP (jeff.wolford@hp.com) Date: 10 Dec 2007 Subject: 07-200r3 SAT-2 WRITE LONG to WRITE UNCORRECTABLE EXT Revision history

More information

3 2 Parameters and states for managing asymmetrical access to SCSI logical units

3 2 Parameters and states for managing asymmetrical access to SCSI logical units T10/00 232 r2 To: John Lohmeyer, chairperson, T10 From: Ken Moe Email: kenneth.moe@sun.com Date: October 20, 2000 Subject: Asymmetrical SCSI behavior 1 Introduction A significant number of SCSI storage

More information

Overview The OOB timing requirements need to be more precise, listing the transmit burst time and specifying receiver tolerances.

Overview The OOB timing requirements need to be more precise, listing the transmit burst time and specifying receiver tolerances. To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 19 June 2002 Subject: T10/02-198r3 SAS OOB timing T10/02-198r3 SAS OOB timing Revision History Revision 0 (20 May 2002) first revision

More information

04-218r5 SAT SPC-3 INQUIRY contents 30 October 2004

04-218r5 SAT SPC-3 INQUIRY contents 30 October 2004 To: T10 Technical Committee From: Rob Elliott (elliott@hp.com) and Wayne Bellamy, HP (wayne.bellamy@hp.com) Date: 30 October 2004 Subject: 04-218r5 SAT SPC-3 INQUIRY contents Revision history Revision

More information

1 Overview. 2 Changes to SPC-4. T10/ revision 5

1 Overview. 2 Changes to SPC-4. T10/ revision 5 Date: 3/18/09 To: T10 Committee (SCSI) From: George Penokie (LSI) Subject: SPC-4: Cache hits and power on statistics 1 Overview There are some performance statistics relating to cache hits that would be

More information

Revision 6: Red text Incorporate comments from January 5, 2004 conference call. Minor wording changes.

Revision 6: Red text Incorporate comments from January 5, 2004 conference call. Minor wording changes. To: INCITS T10 Committee From: Susan Gray, Quantum Date: January, 5, 2004 Document Number: T10/03-355r6 Subject: ADT Section 4.7.1.3 1 Revision History Revision 6: Red text Incorporate comments from January

More information

February T11 Network Address Authority (NAA) Naming Format for iscsi Node Names

February T11 Network Address Authority (NAA) Naming Format for iscsi Node Names Network Working Group Request for Comments: 3980 Updates: 3720 Category: Standards Track M. Krueger M. Chadalapaka R. Elliott Hewlett-Packard Corp. February 2005 Status of this Memo T11 Network Address

More information

Revisions. General. T10 Membership FROM: Paul A. Suhler, Quantum Corporation DATE: 13 June 2008 SUBJECT: T10/07-469r5, ADT-2: Internet ADT (iadt)

Revisions. General. T10 Membership FROM: Paul A. Suhler, Quantum Corporation DATE: 13 June 2008 SUBJECT: T10/07-469r5, ADT-2: Internet ADT (iadt) TO: T10 Membership FROM: Paul A. Suhler, Quantum Corporation DATE: 13 June 2008 SUBJECT: T10/07-469r5, ADT-2: Internet ADT (iadt) Revisions 0 Initial revision (2 November 2007) 1 First revision (9 March

More information

TCG Storage Interface Interactions Specification (SIIS) Specification Version 1.02 Revision December, 2011 TCG

TCG Storage Interface Interactions Specification (SIIS) Specification Version 1.02 Revision December, 2011 TCG TCG Storage Interface Interactions Specification (SIIS) Specification Version 1.02 Revision 1.00 30 December, 2011 TCG TCG PUBLISHED Copyright TCG 2011 Copyright 2011 Trusted Computing Group, Incorporated.

More information

26 April r0 SAT-2 WRITE LONG to WRITE UNCORRECTABLE EXT

26 April r0 SAT-2 WRITE LONG to WRITE UNCORRECTABLE EXT 26 April 2007 07-200r0 SAT-2 WRITE LONG to WRITE UNCORRECTABLE EXT To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) and Jeff Wolford, HP (jeff.wolford@hp.com) Date: 26 April 2007 Subject:

More information

03-240r2 SAS-1.1 Internal wide connector and cable 28 April 2004

03-240r2 SAS-1.1 Internal wide connector and cable 28 April 2004 To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 28 April 2004 Subject: 03-240r2 SAS-1.1 Internal wide connector and cable Revision history Revision 0 (2 July 2003) First revision

More information

03-240r5 SAS-1.1 Internal wide connector and cable 11 September 2004

03-240r5 SAS-1.1 Internal wide connector and cable 11 September 2004 To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 11 September 2004 Subject: 03-240r5 SAS-1.1 Internal wide connector and cable Revision history Revision 0 (2 July 2003) First revision

More information

ATA Command Pass-Through

ATA Command Pass-Through T10/04-262r4 October 14, 2004 ATA Command Pass-Through October 14, 2004 Revision 4 Technical Editor: Curtis E. Stevens Western Digital Phone: 949-672-7933 E-Mail: Curtis.Stevens@WDC.com Revision History

More information

ENDL TEXAS. T10/03-005r0

ENDL TEXAS. T10/03-005r0 ENDL TEXAS Date: 5 January 2003 To: T10 Technical Committee From: Ralph O. Weber Subject: Almost since I started editing SAM I have wanted to move anything not directly part of the architecture from SAM

More information

2 September r0 SAT-2 ATA PASS-THROUGH sense data format

2 September r0 SAT-2 ATA PASS-THROUGH sense data format To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 2 September 2008 Subject: 08-344r0 SAT-2 ATA PASS-THROUGH sense data format Revision history Revision 0 (2 September 2008) First

More information

03-347r0 SES-2 Reporting peer enclosure service processes 15 October 2003

03-347r0 SES-2 Reporting peer enclosure service processes 15 October 2003 To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 15 October 2003 Subject: 03-347r0 SES-2 Reing peer enclosure service processes Revision history Revision 0 (15 October 2003) First

More information

The number in square brackets at the end of each comment description counts all the comments presented in this document.

The number in square brackets at the end of each comment description counts all the comments presented in this document. ENDL TEXAS Date: 15 January 2005 To: T10 Technical Committee From: Ralph O. Weber Subject: Response to T10 Letter Ballot comments on SPC-3 This document contains the responses to the T10 Letter Ballot

More information

24 October r2 SAS-2 Support multiple STP affiliations

24 October r2 SAS-2 Support multiple STP affiliations 24 October 2006 06-188r2 SAS-2 Support multiple STP affiliations To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 24 October 2006 Subject: 06-188r2 SAS-2 Support multiple STP affiliations

More information

04-082r0 SBC-2 Replace Notch and Partition mode page with READ CAPACITY 5 March 2004

04-082r0 SBC-2 Replace Notch and Partition mode page with READ CAPACITY 5 March 2004 To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 5 March 2004 Subject: 04-082r0 SBC-2 Replace Notch and Partition mode page with READ CAPACITY Revision history Revision 0 (5 March

More information

16 June 2007 e07129r1 ATA8-ACS Endianness clarifications

16 June 2007 e07129r1 ATA8-ACS Endianness clarifications 16 June 2007 e07129r1 ATA8-ACS Endianness clarifications To: T13 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 16 June 2007 Subject: e07129r1 ATA8-ACS Endianness clarifications Revision

More information

Request for Comments: May 2004

Request for Comments: May 2004 Network Working Group Request for Comments: 3783 Category: Informational M. Chadalapaka R. Elliott Hewlett-Packard Co. May 2004 Status of this Memo Small Computer Systems Interface (SCSI) Command Ordering

More information

03-346r2 SAS-1.1 Pathway recovery priority corrections 3 November 2003

03-346r2 SAS-1.1 Pathway recovery priority corrections 3 November 2003 To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 3 November 2003 Subject: 03-346r2 SAS-1.1 Pathway recovery priority corrections Revision history Revision 0 (22 October 2003) First

More information

Table 21. OOB signal transmitter requirements Idle time minimum. maximum 175 ns

Table 21. OOB signal transmitter requirements Idle time minimum. maximum 175 ns To: T10 Technical Committee From: Rob Elliott (elliott@hp.com) and Thomas Grieff (thomas.grieff@hp.com), HP Date: 18 July 2002 Subject: T10/02-198r6 SAS OOB timing T10/02-198r6 SAS OOB timing Revision

More information

ATA Command Pass-Through

ATA Command Pass-Through T10/04-262r2 August 16, 2004 ATA Command Pass-Through August 16, 2004 Revision 2 Technical Editor: Curtis E. Stevens Western Digital Phone: 949-672-7933 E-Mail: Curtis.Stevens@WDC.com Table of Contents

More information

Subject Report Element Information

Subject Report Element Information memorandum T10/08-066r87 To INCITS T10 Committee From Curtis Ballard, HP Subject Report Element Information Date 8 April1 May, 2009 Revision History Revision History for original document number 06-272

More information

Information technology - SCSI Enclosure Services - 2 (SES-2)

Information technology - SCSI Enclosure Services - 2 (SES-2) Working Draft Project T10/1559-D Revision 7 29 March 2004 Information technology - SCSI Enclosure Services - 2 (SES-2) This is an internal working document of T10, a Technical Committee of Accredited Standards

More information

The number in square brackets at the end of each comment description counts all the comments presented in this document.

The number in square brackets at the end of each comment description counts all the comments presented in this document. ENDL TEXAS Date: 4 May 2005 To: T10 Technical Committee From: Ralph O. Weber Subject: Response to T10 Letter Ballot comments on SPC-3 This document contains the responses to the T10 Letter Ballot comments

More information

07-416r1 T10 USB Queuing Transport (UQT) study group introduction. by Rob Elliott, HP 25 September 2007

07-416r1 T10 USB Queuing Transport (UQT) study group introduction. by Rob Elliott, HP 25 September 2007 07-416r1 T10 USB Queuing Transport (UQT) study group introduction by Rob Elliott, HP 25 September 2007 USB and other external desktop interfaces USB dominates the market - 6.2 billion USB ports shipped

More information