Five Step Plan for a less weighty SPC-5

George Penokie george.penokie at avagotech.com
Mon Jun 30 14:03:21 PDT 2014


Formatted message: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1406301_f.htm">HTML-formatted message</a>

Kevin,
Are you going to provide an editor for these proposed new standards?
Bye for now,
George Penokie
Avago Technologies
3033 41 St NW
Rochester , MN 55901
507-328-9017
george.penokie at avagotech.com
On Mon, Jun 30, 2014 at 3:32 PM, Kevin D Butt <kdbutt at us.ibm.com> wrote:
> Some of my engineers are asking why we don't pare down SPC-5 by also
> pulling out into separate documents the following sections which in their
> minds technically doesn't really belong in SPC.
>
> Document 1: Annex F (*Numeric order codes*) and Annex G (*T10 vendor
> identification*) The additional sense codes table in section 4 should
> also be removed.  Section 4 is sorted alphabetically and Annex F is sorted
> numerically, so it is the same stuff anyway.	The section 4, Sense Data,
> should point to this new document instead of listing them all.  Most people
> go to the web to get this information anyway.
>
> Document 2: Third Party Copy - all of it.  The model, the VPD, the
> commands, etc.
>
> Document 3: Well Known Logical Units are its' own device type.  This
> should be in a different standard that is stand-alone.
>
> Kevin D. Butt
> SCSI Architect, Tape Firmware, T10 Standards
> Data Protection & Retention
> MS 6TYA, 9000 S. Rita Rd., Tucson, AZ 85744
> Tel: 520-799-5280
> Fax: 520-799-2723 (T/L:321)
> Email address: kdbutt at us.ibm.com
> http://www-03.ibm.com/servers/storage/
>
>
>
> From:        Ralph Weber <Ralph.Weber at wdc.com>
> To:	     "t10 at t10.org" <t10 at t10.org>,
> Date:        06/26/2014 05:20 PM
> Subject:	  Five Step Plan for a less weighty SPC-5
> Sent by:	  <owner-t10 at t10.org>
> ------------------------------
>
>
>
> A Five Step path has been mapped out in order to pare SPC-5 down by as
> much as 300 pages ... so that it can be the super thin (well, at least less
> bulky) SPC-5 everybody want to see.
>
> The first four obsolescence steps to a sure-fire smaller SPC-5 are:
>
>    - Ashcanning the third-party copy LID1 commands
> *http://www.t10.org/cgi-bin/ac.pl?t=d&f=14-164r0.pdf*
>    <http://www.t10.org/cgi-bin/ac.pl?t=d&f=14-164r0.pdf&gt;;
>     - Sending Access Controls to wherever the dinosaurs went
> *http://www.t10.org/cgi-bin/ac.pl?t=d&f=14-165r0.pdf*
>    <http://www.t10.org/cgi-bin/ac.pl?t=d&f=14-165r0.pdf&gt;;
>     - Edselizing Alias Lists
> *http://www.t10.org/cgi-bin/ac.pl?t=d&f=14-166r0.pdf*
>    <http://www.t10.org/cgi-bin/ac.pl?t=d&f=14-166r0.pdf&gt;;
>
>    and last but by no means least ...
>     - Putting the deep freeze on Capability-based Command Security
> *http://www.t10.org/cgi-bin/ac.pl?t=d&f=14-167r0.pdf*
>    <http://www.t10.org/cgi-bin/ac.pl?t=d&f=14-167r0.pdf&gt;.
>
> The fifth and final SPC-5 slenderizer step is actual two steps in one:
>
>    - Remove SFSC content from SPC-5
> *http://www.t10.org/cgi-bin/ac.pl?t=d&f=14-168r0.pdf*
>    <http://www.t10.org/cgi-bin/ac.pl?t=d&f=14-168r0.pdf&gt;;
>
>    and
>     - Build SFSC revision 00
> *http://www.t10.org/cgi-bin/ac.pl?t=d&f=14-171r0.pdf*
>    <http://www.t10.org/cgi-bin/ac.pl?t=d&f=14-171r0.pdf&gt;.
>
> If you have not already purchased tickets to Colorado Springs, now would
> be a good time to correct that slip of the wrist. There's going to be a
> gigantic text roast in our favorite July stomping ground this year.
>
> All the best,
>
> .Ralph
>



More information about the T10 mailing list