To: "Knight, Frederick" <Frederick.Knight@netapp.com>
Cc: t10@t10.org
Subject: RE: SSC-3 Action Item Reminder
From: Kevin D Butt <kdbutt@us.ibm.com>
Date: Fri, 4 Jan 2008 11:03:07 -0700
X-Message-Number: 8388
Formatted message: HTML-formatted message

Fred,
I think you left off T10 from the distribution accidentally.  I have 
included the reflector.
Kevin D. Butt
SCSI & Fibre Channel Architect, Tape Firmware
MS 6TYA, 9000 S. Rita Rd., Tucson, AZ 85744
Tel: 520-799-2869 / 520-799-5280
Fax: 520-799-2723 (T/L:321)
Email address: kdbutt@us.ibm.com
http://www-03.ibm.com/servers/storage/ 
"Knight, Frederick" <Frederick.Knight@netapp.com> 
01/04/2008 09:20 AM
To
Kevin D Butt/Tucson/IBM@IBMUS
cc
Subject
RE: SSC-3 Action Item Reminder
My action below re: table 123 in SSC-3r03e.  I have no issue with removing 
the version byte, and the format byte.
The question about those fields had to do their layout and intended use:
 byte 2-3 - specifies the length of the label field (upto 64k)
 byte 4 - version byte or format byte - not specified which
 byte 5 - version byte or format byte - not specified which
 byte 6-n - contains wrapped key descriptors (defined in 8.5.4.7)
    which contains descriptor type, reserved, and wrapped key descriptor 
length and wrapped key descriptor
 byte n+1-m - contains wrapped key length
 byte m+1-x - contains the wrapped keys
We should either specify which goes where, and what they are for; or if we 
don't know yet, but think we may need something later, then just create 2 
reserved bytes; or totally remove them.  Does anyone remember what 
structure this version/format were referring to (and why it's not part of 
that structure itself)?
Right now, they both shall be set to 00h, so it's no big deal (which also 
means we could just mark them as reserved - or it means we don't really 
need it).  If someone else knows why they are there, then the 
justification for keeping them will need to come from that someone else.
    Fred Knight
From: Kevin D Butt [mailto:kdbutt@us.ibm.com] 
Sent: Thursday, January 03, 2008 7:55 PM
To: t10@t10.org
Subject: SSC-3 Action Item Reminder
This is a reminder of the Action Items still outstanding in the SSC-3 
Working Group. 
Dave Peterson: Bring in a White Paper on the value added with Explicit 
Command Set. 
Dave Peterson incorporate TapeAlert Delineation (06-138r6) into SSC-3 
Dave Peterson to incorporate Requested Recovery log page (07-046r3) 
Paul Suhler will provide his companies definition of medium as a selection 
from Section 5.1.2 
Kevin Butt will provide his companies definition of medium as a selection 
from Section 5.1.2 
Erich Oetting will provide his companies definition of medium as a 
selection from Section 5.1.2 
Paul Suhler to provide his companies answer to ?Should a device server 
allow host write access to MAM on a write protected volume?? 
Erich Oetting to provide his companies answer to ?Should a device server 
allow host write access to MAM on a write protected volume?? 
Fred Knight to invistigate if the version byte and the format byte from 
the LABEL field from Table 123 in SSC-3r03e can be removed. 
Dave Peterson to incorporate Protecting a partially encrypted volume 
(07-290r3) into SSC-3. 
Paul Suhler assign an owner from the ADI group for item 2.7 of 05-351r1 
which is to provide a means for the library Serial Number to be reported 
by the Tape Drive. 
Curtis Ballard to revise and post SSC-3: Out of Band Encryption Key 
Management (07-361r4) 
Dave Peterson to incorporate SSC-3: Out of Band Encryption Key Management 
(07-361r5) into SSC-3. 
Kevin D. Butt
SCSI & Fibre Channel Architect, Tape Firmware
MS 6TYA, 9000 S. Rita Rd., Tucson, AZ 85744
Tel: 520-799-2869 / 520-799-5280
Fax: 520-799-2723 (T/L:321)
Email address: kdbutt@us.ibm.com
http://www-03.ibm.com/servers/storage/