Add the following section to REPORT SUPPORTED OPERATION CODES command.

Size: px
Start display at page:

Download "Add the following section to REPORT SUPPORTED OPERATION CODES command."

Transcription

1 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, :48 pm Document: T10/05-284r4 Subject: SPC-4: Self Describing Command Timeouts 1. Revisions 1. Incorporated feedback received from Rob Elliott on July 21, Incorporate comments from George Penokie and Nov 2005 CAP meeting 3. Modify to use Report Supported Op Codes instead of descriptors. Suggested by George Penokie. 4. Incorporate changes from Sept 2006 CAP meeting 5. Incorporate changes made in Nov 2006 CAP meeting to match r3 as modified that was passed. 2. Introduction The SMC working group has given me an action to create a method to describe the timeout values for each command. I believe this is a more general issue than SMC and belongs in SPC. Additions by this proposal are in this color - blue. Issues to work out are in this color - red. 3. Proposal Add the following section to REPORT SUPPORTED OPERATION CODES command REPORT SUPPORTED OPERATION CODES command introduction The REPORT SUPPORTED OPERATION CODES command (see table 154) requests information on commands the addressed logical unit supports. An application client may request a list of all operation codes and service actions supported by the logical unit or the command support data for a specific command. The REPORT SUPPORTED OPERATION CODES command is a service action of the MAIN- TENANCE IN command. Additional MAINTENANCE IN service actions are defined in SCC-2 and in this standard. The MAINTENANCE IN service actions defined in SCC-2 apply only to

2 Page 2 of 7 Self Describing Cmd Timouts.fm/05-284r4 November 8, 2006 logical units that return a device type of 0Ch or the SCCS bit set to one in their standard INQUIRY data (see 6.4.2). TABLE 154. REPORT SUPPORTED OPERATION CODES command 0 OPERATION CODE (A3h) 1 SERVICE ACTION (0Ch) 2 RCPT REPORTING OPTIONS 3 REQUESTED OPERATION CODE 4 (MSB) REQUESTED SERVICE ACTION 5 6 (MSB) ALLOCATION LENGTH CONTROL A Return Command Processing Time (RCPT) bit set to one specifies that the Command Timeouts descriptor (see Section ) shall be included in each Command descriptor that is returned and to the One_command parameter data that is returned. A RCPT bit set to zero specifies that the Command Timeouts descriptor shall not be included in any parameter data returned. The REPORTING OPTIONS field (see table 155) specifies the information to be returned in the parameter data. TABLE 155. REPORT SUPPORTED OPERATION CODES REPORTING OPTIONS field Code 000b 001b A list of all operation codes and service actions supported by the logical unit shall be returned in the all_commands parameter data format. The REQUESTED OPERATION CODE CDB field and REQUESTED SERVICE ACTION CDB field shall be ignored. The command support data for the operation code specified in the REQUESTED OPERATION CODE field shall be returned in the one_command parameter data format. The REQUESTED SERVICE ACTION CDB field shall be ignored. If the REQUESTED OPERATION CODE field specifies an operation code that has service actions, then the command shall be terminated with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN CDB. Parameter Data Reference

3 Page 3 of 7 Self Describing Cmd Timouts.fm/05-284r4 November 8, b 011b-111b The command support data for the operation code and service action specified in the REQUESTED OPERATION CODE CDB field and REQUESTED SERVICE ACTION CDB field shall be returned in the one_command parameter data format. If the REQUESTED OPERATION CODE CDB field specifies an operation code that does not have service actions, then the command shall be terminated with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN CDB. The REQUESTED OPERATION CODE field specifies the operation code of the command to be returned in the one_command parameter data format (see ). The REQUESTED SERVICE ACTION field specifies the service action of the command to be returned in the one_command parameter data format. The ALLOCATION LENGTH field is defined in Command Timeouts Descriptor The Command Timeouts descriptor returns timeout information for commands supported by the logical unit based on the time from the start of processing the command, to its reported completion. Values returned in this descriptor do not include times that are outside the control of the device server (e.g., a prior command with the IMMED bit set to one in the CDB, concurrent commands from the same or different I_T nexuses, manual unloads, power-on self tests, commands issued after aborted commands, commands which force cache synchronization, delays in the service delivery subsystem). For commands that cause a change in power condition (see ), these times do not include the power condition transition time (e.g., the time to spinup rotating media). The values in this descriptor should not be used to compare products. The Command Processing Times descriptor is described in Table 156 TABLE Command Processing Times descriptor (MSB) 1 Code TABLE 155. REPORT SUPPORTED OPERATION CODES REPORTING OPTIONS field Descriptor Length (0Ah) 2 3 Restricted (Defined in command set specific standards) Parameter Data Reference

4 Page 4 of 7 Self Describing Cmd Timouts.fm/05-284r4 November 8, (MSB) 7 8 (MSB) 11 A non-zero value in the NOMINAL COMMAND PROCESSING TIME field specifies the minimum amount of time in seconds the application client should wait prior to querying for progress for the command specified by the CDB OPERATION CODE and CDB SERVICE ACTION fields. A value of zero in the NOMINAL COMMAND PROCESSING TIME field indicates that no time is being specified. Note: The value specified in the NOMINAL COMMAND PROCESSING TIME field may include time required for typical device error recovery procedures expected to occur on a regular basis. A non-zero value in the RECOMMENDED COMMAND TIMEOUT field specifies the recommended time in seconds the application client should use when timing out the command specified by the CDB OPERATION CODE and CDB SERVICE ACTION fields. A value of zero in the RECOMMENDED COMMAND TIMEOUT field indicates that no time is being recommended. The device server should set the RECOMMENDED COMMAND TIMEOUT field to a value greater than or equal to the NOMINAL COMMAND PROCESSING TIME field All_commands parameter data format NOMINAL COMMAND PROCESSING TIME RECOMMENDED COMMAND TIMEOUT The REPORT SUPPORTED OPERATION CODES all_commands parameter data format (see table 156) begins with a four-byte header that contains the length in bytes of the parameter data followed by a list of supported commands. Each command descriptor contains information about a single supported command CDB (i.e., one operation code and service action combination, or one non-service-action operation code). The list of command descriptors shall contain all commands supported by the logical unit. TABLE 157. All_commands parameter data 0 (MSB) 3 4 TABLE Command Processing Times descriptor COMMAND DATA LENGTH (n-3) Command descriptors Command descriptor 0 (see table 158)...

5 Page 5 of 7 Self Describing Cmd Timouts.fm/05-284r4 November 8, 2006 TABLE 157. All_commands parameter data n Command descriptor x (see table 158) The COMMAND DATA LENGTH field indicates the length in bytes of the command descriptor list. Each command descriptor (see table 158) contains information about a single supported command CDB. TABLE 158. Command descriptor format 0 OPERATION CODE 1 2 (MSB) 3 SERVICE ACTION 4 5 CPTDP SERVACTV 6 (MSB) CDB LENGTH Command Processing Times descriptor (if any) The OPERATION CODE field contains the operation code of a command supported by the logical unit. The SERVICE ACTION field contains a supported service action of the supported operation code indicated by the OPERATION CODE field. If the operation code indicated in the OPERATION CODE field does not have a service actions, the SERVICE ACTION field shall be set to 00h. A service action valid (SERVACTV) bit set to zero indicates the operation code indicated by the OPERATION CODE field does not have service actions and the SERVICE ACTION field contents are reserved. A SERVACTV bit set to one indicates the operation code indicated by the OPERATION CODE field has service actions and the contents of the SERVICE ACTION field are valid. A command processing time descriptor present (CPTDP) bit set to one indicates that the Command Processing Times descriptor shall be included in the data. A CPTDP bit set to zero indicates that the Command Processing Times descriptor shall not be included in the data.

6 Page 6 of 7 Self Describing Cmd Timouts.fm/05-284r4 November 8, 2006 The CDB LENGTH field contains the length of the command CDB in bytes for the operation code indicated in the OPERATION CODE field, and if the SERVACTV bit is set to the service action indicated by the SERVICE ACTION field. If the RCPT bit of the REPORT SUPPORTED OPERATION CODES CDB is set to one, the Command Processing Times descriptor (see Table 158) shall be included. If the RCPT bit of the CDB is set to zero, the Command Processing Times descriptor shall not be included One_command parameter data format The REPORT SUPPORTED OPERATION CODES one_command parameter data format (see table 159) contains information about the CDB and a usage map for bits in the CDB for the command specified by the REPORTING OPTIONS, REQUESTED OPERATION CODE, and REQUESTED SERVICE ACTION fields in the REPORT SUPPORTED OPERATION CODES CDB. The SUPPORT field is defined in table 160. TABLE 159. One_command parameter data 0 1 CPTDP SUPPORT 2 (MSB) CDB SIZE (n-3) 3 4 n CDB USAGE DATA n+1 n+12 Command Processing Times descriptor (if any) TABLE 160. SUPPORT values Support 000b 001b 010b 011b 100b Data about the requested SCSI command is not currently available. All data after byte 1 is not valid. A subsequent request for command support data may be successful. The device server does not support the requested command. All data after byte 1 is undefined. The device server supports the requested command in conformance with a SCSI standard. The parameter data format conforms to the definition in table 159.

7 Page 7 of 7 Self Describing Cmd Timouts.fm/05-284r4 November 8, 2006 Support 101b 110b - 111b The device server supports the requested command in a vendor specific manner. The parameter data format conforms to the definition in table 159. TABLE 160. SUPPORT values A command processing time descriptor present (CPTDP) bit set to one indicates that the Command Processing Times descriptor shall be included in the data. A CPTDP bit set to zero indicates that the Command Processing Times descriptor shall not be included in the data. The CDB SIZE field contains the size of the CDB USAGE DATA field in the parameter data, and the number of bytes in the CDB for command being queried (i.e., the command specified by the REPORTING OPTIONS, REQUESTED OPERATION CODE, and REQUESTED SERVICE ACTION fields in the REPORT SUPPORTED OPERATION CODES CDB). The CDB USAGE DATA field contains information about the CDB for the command being queried. The first byte of the CDB USAGE DATA field shall contain the operation code for the command being queried. If the command being queried contains a service action, then that service action code shall be placed in the CDB USAGE DATA field in the same location as the SERVICE ACTION field of the command CDB. All other bytes of the CDB USAGE DATA field shall contain a usage map for bits in the CDB for the command being queried. The bits in the usage map shall have a one-for-one correspondence to the CDB for the command being queried. If the device server evaluates a bit in the CDB for the command being queried, the usage map shall contain a one in the corresponding bit position. If any bit representing part of a field is returned as one, all bits for the field shall be returned as one. If the device server ignores or treats as reserved a bit in the CDB for the command being queried, the usage map shall contain a zero in the corresponding bit position. The usage map bits for a given CDB field all shall have the same value. For example, the CDB usage bit map for the REPORT SUPPORTED OPERATION CODES command is: A3h, 0Ch, 03h, FFh, FFh, FFh, FFh, FFh, FFh, FFh, 00h, 07h. This example assumes that the logical unit only supports the low-order three bits of the CDB CONTROL byte. The first byte contains the operation code, and the second byte contains three reserved bits and the service action. The remaining bytes contain the usage map. If the RCPT bit of the REPORT SUPPORTED OPERATION CODES CDB is set to one, the Command Processing Times descriptor (see Table 158) shall be included. If the RCPT bit of the CDB is set to zero, the Command Processing Times descriptor shall not be included.

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

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

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

Subject Report Volume Information. This command is a companion to , Report Element Information. Full background is available in that proposal.

Subject Report Volume Information. This command is a companion to , Report Element Information. Full background is available in that proposal. memorandum To INCITS T0 Committee From Curtis Ballard, HP Subject Report Volume Information T0/0-2r3 DRAFT Date May, 200 Revision History Revision 0 Initial document Related Documents smc3r04 SCSI Media

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

1 Overview. T10/ revision 0

1 Overview. T10/ revision 0 Date: 10/22/08 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

More information

This command may be expanded in the future to report other LBA characteristics.

This command may be expanded in the future to report other LBA characteristics. To: INCITS Technical Committee T10 From: Fred Knight, NetApp David Black, EMC Email: knight@netapp.com black_david@emc.com Date: June 2, 2009 Subject: SBC-3 Thin Provisioning Management Commands 1) Revision

More information

Null second level LUN (0000h) (LSB) Null third level LUN (0000h) Null fourth level LUN (0000h)

Null second level LUN (0000h) (LSB) Null third level LUN (0000h) Null fourth level LUN (0000h) Date: October 10, 2005 To: T10 Committee (SCSI) From: George Penokie (IBM/Tivoli) Subject: SAM-4: Addressing more than 16384 logical units 1 Overview There are storage subsystems that are exceeding the

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

T10/06-393r1 On-disk bitmap support. Date: October 24, T10 Committee (SCSI) Roger Cummings (Symantec)

T10/06-393r1 On-disk bitmap support. Date: October 24, T10 Committee (SCSI) Roger Cummings (Symantec) Date: October 24, 2006 To: From: Subject: T10 Committee (SCSI) Roger Cummings (Symantec) T10/06-393r1 On-disk bitmap support Revision History 06-393r0 (August 31, 2006) Original 06-393r1 (October 24, 2006)

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

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

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

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

T10/06-393r3 On-disk bitmap support. Date: January 16, T10 Committee (SCSI) Roger Cummings (Symantec)

T10/06-393r3 On-disk bitmap support. Date: January 16, T10 Committee (SCSI) Roger Cummings (Symantec) Date: January 16, 2007 To: From: Subject: T10 Committee (SCSI) Roger Cummings (Symantec) T10/06-393r3 On-disk bitmap support Revision History 06-393r0 (August 31, 2006) Original 06-393r1 (October 24, 2006)

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

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

6 May 2008 T10/08-018r3

6 May 2008 T10/08-018r3 To: T10 Technical Committee From: Mark Overby, NVIDIA Corporation (moverby@nvidia.com) Date: 6 May 2008 Subject: T10/08-018r3 SAT-2: NV Cache Translation Revision History Revision 0 - Initial draft of

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

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

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

Subject Report Element Information

Subject Report Element Information memorandum To INCITS T10 Committee From Curtis Ballard, HP Michael Banther, HP Subject Report Element Information T10/08-066r2 Date 7 March, 2008 Revision History for original document number 06-272 Revision

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

X3T10/ revision 2 5/6/97

X3T10/ revision 2 5/6/97 To: X3T10 Committee () From: George Penokie (IBM) Subject: Addressing Model for SAM-2 1 Overview 1.1 Example of hierarchical system A system that is composed of many layers appears as a tree. For example,

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

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

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

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-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

1 Overview. T10/ revision 6

1 Overview. T10/ revision 6 Date: October 07, 2003 To: T10 Committee (SCSI) From: George Penokie (IBM/Tivoli) Subject: End-to-End Data Protection 1 Overview Any inconsistencies between this section and the remaining sections in the

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

03-388r0 SBC-2 Nonvolatile caches 11 December 2003

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

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

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

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

1 Overview. T10/ revision 8

1 Overview. T10/ revision 8 Date: October 20, 2003 To: T10 Committee (SCSI) From: George Penokie (IBM/Tivoli) Subject: End-to-End Data Protection 1 Overview Any inconsistencies between this section and the remaining sections in the

More information

1) Revision history 2) Related documents 3) Overview

1) Revision history 2) Related documents 3) Overview To: INCITS Technical Committee T10 From: Fred Knight, Network Appliance Email: knight@netapp.com Date: Sept 5, 2008 Subject: SBC-3 Thin Provisioning Commands 1) Revision history Revision 0 (July 7, 2008)

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 next page shows the questions asked in revision 0 of this proposal and the answers supplied by the May SCSI Working Group meeting.

The next page shows the questions asked in revision 0 of this proposal and the answers supplied by the May SCSI Working Group meeting. T10/99-163r1 Date: 13 May 1999 To: T10 Technical Committee From: Ralph Weber, LSI Logic Alternate Member of T10 Subj: EXTENDED COPY command for SPC-2 This revision contains those changes agreed by the

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

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

14 January 2009 T10/08-018r4

14 January 2009 T10/08-018r4 To: T10 Technical Committee From: Mark Overby, NVIDIA Corporation (moverby@nvidia.com) Date: 14 January 2009 Subject: T10/08-018r4 SAT-3: NV Cache Translation Revision History Revision 0 - Initial draft

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

IBM System Storage TS3100 Tape Library and TS3200 Tape Library. Reference. Machine Type 3573 GA

IBM System Storage TS3100 Tape Library and TS3200 Tape Library. Reference. Machine Type 3573 GA IBM System Storage TS3100 Tape Library and TS3200 Tape Library SCSI Reference Machine Type 3573 GA32-0547-01 Second Edition (June 2006) This edition applies to the IBM System Storage TM TS3100 Tape Library

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

Suggested Changes. Add to Clause 8 8.AA SECURITY PROTOCOL IN command 8.BB SECURITY PROTOCOL OUT command. Jim Hatfield (Seagate) Page 1 of 5

Suggested Changes. Add to Clause 8 8.AA SECURITY PROTOCOL IN command 8.BB SECURITY PROTOCOL OUT command. Jim Hatfield (Seagate) Page 1 of 5 To: T10 Technical Committee From: Jim Hatfield, Seagate (James.C.Hatfield@seagate.com) Date: May 8, 2007 Subject: Revision History Revision 0 (Feb. 14, 2007) First revision Revision 1 (Mar. 1, 2007) Incorporate

More information

As a result of proposal r2 (SAS-2 STP connection time limits and STP/SMP I_T nexus loss) a REQUEST

As a result of proposal r2 (SAS-2 STP connection time limits and STP/SMP I_T nexus loss) a REQUEST Date: September 13, 2007 To: T10 Committee (SCSI) From: George Penokie (IBM) Subject: SAS-2: Indeterminate response lenght to a SMP REPORT GENERAL function 1 Overview As a result of proposal 05-306r2 (SAS-2

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

Gene Milligab, T10 Principal member

Gene Milligab, T10 Principal member X3T10/97-225r20 Seagate Technology Tel: 405-324-3070 10323 West Reno (West Dock) Fax: 405-324-3794 Oklahoma City, OK 73127-9705 gene_milligan@notes.seagate.com P.O. Box 12313 Oklahoma City, OK 73157-2313

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

September 11, T10 Technical Committee John Lohmeyer, LSI Logic Principal Member of T10 Expander Communication Protocol. Revision 3 changes:

September 11, T10 Technical Committee John Lohmeyer, LSI Logic Principal Member of T10 Expander Communication Protocol. Revision 3 changes: September 11, 2000 4420 ArrowsWest Drive Colorado Springs, CO 80907 To: From: Subj: T10 Technical Committee John Lohmeyer, LSI Logic Principal Member of T10 Revision 3 changes: 1. Required the initiator

More information

CONTENTS ISO/IEC:2005(E)

CONTENTS ISO/IEC:2005(E) 2 14776-351 ISO/IEC:2005(E) CONTENTS FOREWORD... 5 INTRODUCTION... 6 1 Scope... 8 2 Normative References... 8 3 Definitions, symbols and abbreviations... 8 3.1 Definitions... 8 3.2 Symbols and abbreviations...13

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

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

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

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

Note: All CDB formats in this proposal assume that is approved for incorporation prior to or concurrently with this proposal.

Note: All CDB formats in this proposal assume that is approved for incorporation prior to or concurrently with this proposal. ENDL TEXAS Date: 3 July 2008 To: T10 Technical Committee From: Ralph O. Weber Subject: Introduction The SNIA OSD TWG Snapshots Proposal describes the ability to replicate entire partitions in the form

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

IBM System Storage TS3310 Tape Library. Reference GA

IBM System Storage TS3310 Tape Library. Reference GA IBM System Storage TS3310 Tape Library SCSI Reference GA32-0476-00 IBM System Storage TS3310 Tape Library SCSI Reference GA32-0476-00 Note Before using this information and the product it supports, read

More information

COPYRIGHT DISCLAIMER TRADEMARK NOTICES PART NUMBER REVISION HISTORY CONTACTING TANDBERG DATA CORPORATION

COPYRIGHT DISCLAIMER TRADEMARK NOTICES PART NUMBER REVISION HISTORY CONTACTING TANDBERG DATA CORPORATION VXA-320 (VXA-3) SCSI Reference COPYRIGHT DISCLAIMER TRADEMARK NOTICES Copyright 2008 by Tandberg Data Corporation. All rights reserved. This item and the information contained herein are the property of

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

06-078r3 SAS-2 Expander Route Table (REPORT EXPANDER ROUTE TABLE) 21 June 2006

06-078r3 SAS-2 Expander Route Table (REPORT EXPANDER ROUTE TABLE) 21 June 2006 To: T10 Technical Committee From: Steve Johnson LSI Logic (steve.johnson@lsil.com) Date: 21 June 2006 Subject: 06-078r3 SAS-2 Expander Route Table (REPORT EXPANDER ROUTE TABLE) Revision history Revision

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

SBC-2 Option to Check Only the Logical Block Guard

SBC-2 Option to Check Only the Logical Block Guard Date: April 18, 2004 To: From: Subject: T10 Technical Committee Keith Holt (LSI Logic) SBC-2 Data Protection Option to Check Only the Logical Block Guard 1. Introduction The RDPROTECT and WRPROTECT data

More information

4.3 The Command Descriptor Block (CDB)

4.3 The Command Descriptor Block (CDB) Date: 1 August 2000 To: T10 Technical Committee From: Ralph O. Weber Subject: CDB Structure Rewrite Several SPC-2 letter ballot comments suggest non-substantive rewriting the subclauses in clause that

More information

26 April r2 SBC-3 Physical blocks

26 April r2 SBC-3 Physical blocks To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 26 April 2006 Subject: 06-034r2 SBC-3 Physical blocks Revision history Revision 0 (4 January 2006) First revision Revision 1 (3

More information

03-348r0 SBC-2 4-byte LBA commands on 8 byte capable drives 11 October 2003

03-348r0 SBC-2 4-byte LBA commands on 8 byte capable drives 11 October 2003 To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 11 October 2003 Subject: 03-348r0 SBC-2 4-byte LBA commands on 8 byte capable drives Revision history Revision 0 (11 October 2003)

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

Intel Storage System JBOD 2000S3 Product Family

Intel Storage System JBOD 2000S3 Product Family Intel Storage System JBOD 2000S3 Product Family SCSI Enclosure Services Programming Guide SES Version 3.0, Revision 1.8 Apr 2017 Intel Server Boards and Systems Headline

More information

Table 1 - Medium partition page(1)

Table 1 - Medium partition page(1) To: From: Membership of X3T10 Edward Lappin Exabyte Corporation tedl@exabyte.com Date: January 23, 1995 Subject: Medium Partition Page(1-4) enhancements for SCSI-3. 1.1.1.1 Medium partition page(1) The

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

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

The author believes that this revision of this document addresses the following previously unresolved OSD Letter Ballot comments:

The author believes that this revision of this document addresses the following previously unresolved OSD Letter Ballot comments: ENDL TEXAS Date: 27 June 2004 To: T10 Technical Committee SNIA OSD TWG From: Ralph O. Weber Subject: Rewrite of OSD Security Policy/Storage Manager Models Revision History This document is being presented

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

INT 13 command: SCSI Pass Through Proposal

INT 13 command: SCSI Pass Through Proposal INT 13 command: SCSI Pass Through Proposal 8/25/2000 To: T13 Membership From: Ron Roberts, Adaptec Corp. Subject: EDD 3.0 comment Referencing the EDD specification, Rev 3.0 Feb 18, 2000 section 6.11, the

More information

06-037r5 SAS-2 SMP Lists (DISCOVER LIST) 1 May, 2006

06-037r5 SAS-2 SMP Lists (DISCOVER LIST) 1 May, 2006 To: T10 Technical Committee From: Steve Johnson LSI Logic (steve.johnson@lsil.com), Brad Besmer LSI Logic Date: 1 May, 2006 Subject: 06-037r5 SAS-2 SMP Lists (DISCOVER LIST) Revision history Revision 0

More information

August 14, T10 Technical Committee John Lohmeyer, LSI Logic Principal Member of T10 Expander Communication Protocol. Revision 1 changes:

August 14, T10 Technical Committee John Lohmeyer, LSI Logic Principal Member of T10 Expander Communication Protocol. Revision 1 changes: August 14, 2000 4420 ArrowsWest Drive Colorado Springs, CO 80907 To: From: Subj: T10 Technical Committee John Lohmeyer, LSI Logic Principal Member of T10 Expander Communication Protocol Revision 1 changes:

More information

Subject SMC-3 TapeAlert enhancements

Subject SMC-3 TapeAlert enhancements To INCITS T10 Committee From Michael Banther, HP Subject SMC-3 TapeAlert enhancements Date 10 September 2006 Revision History Background Revision 0 Initial document The TapeAlert feature suffers from several

More information

T10 Membership Kevin D. Butt IBM DATE: 20 October 2006 SUBJECT: T10/06-462r0, SSC-3 Keyless Copy of Encrypted Data

T10 Membership Kevin D. Butt IBM DATE: 20 October 2006 SUBJECT: T10/06-462r0, SSC-3 Keyless Copy of Encrypted Data TO: FROM: T10 Membership Kevin D Butt IBM kdbutt@usibmcom DATE: 20 October 2006 SUBJECT: T10/06-462r0, SSC-3 Keyless Copy of Encrypted Data 1 Revisions 06-412r0 Initial revision (8 September 2006) 06-412r1

More information

Proposal for Storage and Access of Data on Auxiliary Memory

Proposal for Storage and Access of Data on Auxiliary Memory Proposal for Storage and Access of Data on Auxiliary Memory Revision History Author: Sid Crighton Phone: +44 117 3128339 Location: R&D, Hewlett-Packard Ltd, Bristol, UK Email: ianc@bri.hp.com Version Date

More information

06-037r3 SAS-2 SMP Lists (DISCOVER LIST) 28 April, 2006

06-037r3 SAS-2 SMP Lists (DISCOVER LIST) 28 April, 2006 To: T10 Technical Committee From: Steve Johnson LSI Logic (steve.johnson@lsil.com), Brad Besmer LSI Logic Date: 28 April, 2006 Subject: 06-037r3 SAS-2 SMP Lists (DISCOVER LIST) Revision history 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/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

FCD Information Technology - Small Computer System Interface - Part 381: Optical Memory Card Device Commands (SCSI OMC)

FCD Information Technology - Small Computer System Interface - Part 381: Optical Memory Card Device Commands (SCSI OMC) Final Committee Draft IS/IEC JTC 1/SC 25N 533 1998-12-10 FCD 14776-381 Information Technology - Small Computer System Interface - Part 381: ptical Memory Card Device Commands (SCSI MC) Contents... Page

More information

Revision History Revision 0 (T10/06-225r0): Posted to the T10 web site on 4 May 2006.

Revision History Revision 0 (T10/06-225r0): Posted to the T10 web site on 4 May 2006. To: INCITS T10 Committee From: Matt Ball, Quantum Corporation Date: March 13, 2007 Subject: SSC-3: Key Entry using Encapsulating Security Payload (ESP) Revision History Revision 0 (T10/06-225r0): Posted

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

This proposal attempts to correct that by defining FLUSH xxx commands for all object types.

This proposal attempts to correct that by defining FLUSH xxx commands for all object types. ENDL TEXAS Date: 21 June 2004 To: T10 Technical Committee and SNIA OSD TWG From: Ralph O. Weber Subject: A FLUSH for every object type OSD Letter Ballot comments HP 76) and HP 77) note that FLUSH OBJECT

More information

Hard Drive Self-tests

Hard Drive Self-tests T10/99-179 rev 1 To: T10 Technical committee From: Mark Evans Quantum Corporation 500 McCarthy Boulevard Milpitas, CA USA 95035 Phone: 408-894-4019 Fax: 408-952-3620 Email: mark.evans@quantum.com Date:

More information

Page 1 of 10 ISV Responses Work list.fm/07-131r1 September 8, 2008

Page 1 of 10 ISV Responses Work list.fm/07-131r1 September 8, 2008 Page 1 of 10 ISV Responses Work list.fm/07-131r1 September 8, 2008 To: INCITS Technical Committee T10 From: Kevin Butt, IBM Date: September 8, 2008 1:38 pm Document: T10/07-131r1 Subject: Responses to

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

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

Document T10/ rev. 1

Document T10/ rev. 1 To: T10 Committee From: Gerry Houlder, Seagate Technology, gerry_houlder@seagate.com Developed for Trusted Computing Group, www.trustedcomputinggroup.org Subj: SPC-3 Security Commands proposal Date: June

More information

Timely Safe Recording. Nero Copyright

Timely Safe Recording. Nero Copyright Timely Safe Recording ## Permission is granted to members of INCITS, its technical ## committees and their associated task groups to reproduce ## this document for the purposes of INCITS standardization

More information

These changes would become part of the peripheral device type table in the SCC standard. The new peripheral device type table would appear as follows:

These changes would become part of the peripheral device type table in the SCC standard. The new peripheral device type table would appear as follows: Date: Mar 02,1993 X3T10/94-041 rev 2 To: X3T9.2 Committee (SCSI) From: George Penokie (IBM) Subject: SDA States and Types 1.0 Overview The SCSI-3 Disk Array Model requires the definition of several new

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

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

Subject SSC-3 TapeAlert enhancements

Subject SSC-3 TapeAlert enhancements memorandum Hewlett-Packard Company T10/05-154r3 To INCITS T10 Committee From Michael Banther, HP Subject SSC-3 TapeAlert enhancements Date 7 October 2005 Revision History Revision 0 Initial document Revision

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

Capability based Command Security

Capability based Command Security Capability based Command Security SCSI commands standard proposal IBM Research Lab in Haifa February 2007 Table of Contents 1 General... 1 1.1 Overview...1 1.2 The Security Manager...2 1.3 Special Considerations...3

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