Security Protocol Out/Request volume Element Address

Greg Wheeless greg_wheeless at
Thu Mar 30 10:37:10 PST 2006

Formatted message: <A HREF="r060330j_f.htm">HTML-formatted message</A>

I agree with Kevin that we should avoid duplicating an existing op code for
the new Security Protocol In and Security Protocol Out commands, as the
intent was to make these commands potentially available for all device types.
 Is a different op code available for the Security Protocol Out command?
Greg Wheeless
-----Original Message-----
From: owner-t10 at [mailto:owner-t10 at]On Behalf Of Kevin D Butt
Sent: Wednesday, March 29, 2006 1:54 PM
To: t10 at
Subject: Security Protocol Out/Request volume Element Address
I just noticed that the new Security Protocol Out command collides with the
op code for an SMC device (Request Volume Element Address).  I thought a free
op code was requested.	This means that Automation devices will never be able
to use any of the security protocols.  I think this is a bad idea.  I don't
know where how all the library vendors missed this.  Can this be changed? 
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 at 

More information about the T10 mailing list