comment on 06-369r2 -- Security Association Model for SPC-4
roweber at ieee.org
Sat Aug 26 20:00:02 PDT 2006
* From the T10 Reflector (t10 at t10.org), posted by:
* Ralph Weber <roweber at ieee.org>
I have reorganized the subclauses more or less along the lines
you suggested in the newly uploaded:
I believe the question of which security protocols create SAs
will be addressed when the TBDs in table x2 are replaced with
Perhaps these will be the only security protocols that
specifically relate to SAs. If not, one or more additional
tables may be needed.
In any case, the default assumption should be that any given
security protocol does not use SAs and some statement to
the contrary should be made in the other cases.
It is my intention that 06-369rx address SAs as they are
applicable to all device types. Therefore, I would not
support discussing tape protocols in SPC-4 (except in
one of those famous coded value lists in Annex D).
All the best,
Gerry.Houlder at seagate.com wrote:
> * From the T10 Reflector (t10 at t10.org), posted by:
> * Gerry.Houlder at seagate.com
> While reading through the new section 5.13, I thought the information was
> not organized in the best order for understanding. 5.13.1 and 5.13.2
> introduce tables without describing what they are for. Clause 5.13.3
> finally starts defining a "security association" and what it is used for.
> This should become the first clause in 5.13 because it provides a basis for
> understanding the stuff in the other clauses.
> It is also unclear if this security association method is required for all
> "security protocols" supported in SECURITY PROTOCOL IN/ OUT commands or
> just the tape protocol (which is the only one described in SPC-4 at the
> I would like to see a more generic model that starts with material from
> 5.13.1,5.13.3, and 5.13.4; then moves on to describe the choices made for
> the minimum SA parameters, etc. for the tape protocol. It should also state
> that the tape protocol details do not necessarily apply to protocols that
> reference other documents for their description.
> * For T10 Reflector information, send a message with
> * 'info t10' (no quotes) in the message body to majordomo at t10.org
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org
More information about the T10