| "Paul Entzel"
<Paul.Entzel@Quantum.com>
04/25/2006 07:43 AM |
|
I took a couple of minutes to review the document and added a couple of notes. I concentrated mainly on the ERASE(6) command since my devices only support this one. I think my main area of concern is how these new bits will be handled by devices that do not check reserved fields in CDBs and also do not support these new bits. Normally, I would not be all that concerned with this, except for the location you chose for the bits. You placed the bits in the most significant 2 bits of byte 1, a location traditionally reserved since it used to hold the LUN field way back in SCSI-2 days. In many of our devices, we zero out these bits to avoid problems with systems that put the LUN into the CDB. That means these devices will not see the new bits and treat the ERASE command as if they were not set. We can certainly change this behavior in future devices, but how is the application client to know if the bits are supported, checked, or ignored?
Paul Entzel
Quantum
-----Original Message-----
From: Kevin D Butt [mailto:kdbutt@us.ibm.com]
Sent: Monday, April 24, 2006 11:31 PM
To: Erich Oetting; Greg Wheeless; BANTHER,MICHAEL (HP-UnitedKingdom,ex2);
Paul Entzel; Paul Suhler; Peterson, David; roger.cummings@symantec.com
Cc: t10@t10.org
Subject: SSC-3: Secure Data Erase
Tape Heads,
I have posted a new version of the Secure Data Erase proposal. I
am hoping to get this through this meeting cycle. Can you review
and provide feedback?
http://www.t10.org/ftp/t10/document.06/06-120r1.pdf
Thanks,
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/ [attachment "06-120r1.pdf"
deleted by Kevin D Butt/Tucson/IBM]