Question about use of IEEE COMPANY ID in 11-322r2

Knight, Frederick Frederick.Knight at
Thu Oct 11 08:46:56 PDT 2012

Formatted message: <a href="">HTML-formatted message</a>

I agree with Rob, we should more carefully specify this than we have some of
our previous fields.
SCSI (T10) already allows this so getting this right for the translation is
		Fred Knight
From: owner-t10 at [mailto:owner-t10 at] On Behalf Of Curtis
Sent: Tuesday, October 09, 2012 6:14 PM
To: James C Hatfield; Gerry Houlder
Cc: T10 Reflector
Subject: RE: Question about use of IEEE COMPANY ID in 11-322r2
Are there any concerns about OUI-36?
Curtis E. Stevens
Director, Standards & Features Technology
3355 Michelson Dr. #100
Office: 1-1041
Irvine, Ca. 92612
Phone: 949-672-7933
Cell: 949-307-5050
E-Mail: Curtis.Stevens at
Remember, you may only be blamed for something if you are actually doing
From: owner-t10 at [mailto:owner-t10 at] On Behalf Of James C
Sent: Monday, October 08, 2012 12:10 PM
To: Gerry Houlder
Cc: T10 Reflector
Subject: Re: Question about use of IEEE COMPANY ID in 11-322r2
T13 has already defined (in ACS-3 rev 4: see A.23.2) that
      bits 31:24 are reserved
      bits 24:0   are the OUI
Thank You !!!
Jim Hatfield
Seagate Technology LLC
   e-mail:  James.C.Hatfield at
   s-mail:  389 Disc Drive;  Longmont, CO 80503 USA
   voice:  720-684-2120
   fax....: 720-684-2711
   cell...: 720-771-8914
On Mon, Oct 8, 2012 at 12:37 PM, Gerry Houlder
<gerry.houlder at> wrote:
I have noted that 11-322r2 (Device crash dump) has a 32 bit field in the
returned data for IEEE COMPANY ID. I'm sure this is because the SATA
equivalent has a 4 byte field for this also. However, the IEEE Company ID is
a 24 bit value.
Neither the SATA version or the T10 version of the crash dump feature has any
guideline about how the 24 bit value is aligned within the 32 bit field.
There is also the issue of SATA being little endian and SCSI is big endian.
This could lead to interpretation problems when comparing crash dump
information from a SATA drive with crash dump information from a SCSI drive
that are from the same manufacturer (and should have the same company ID
I suggest that the 4 byte value should be changed to a 3 byte value plus a
reserved byte. This would take care of how the 24 bit field is aligned. We
should also discuss whether we need to require the bytes to be always little
endian or always big endian regardless of whether the data is from a SATA or
SCSI drive.

More information about the T10 mailing list