MD5 Logical Unit Identifier

Santosh Rao santoshr at cup.hp.com
Wed Mar 27 17:53:08 PST 2002


* From the T10 Reflector (t10 at t10.org), posted by:
* Santosh Rao <santoshr at cup.hp.com>
*
Dave,

Per the proposal, one of the inputs to the message digest generator is
the standard inquiry data "product revision level".

Hence, each time there is a change in the product revision level (ex :
firmware upgrade that results in a change in product revision level),
the message digest generated, and therefore, the LU unique identifier
would change.

Such changes in LU unique identifier on a firmware upgrade would not be
desirable from the initiator's perspective, since the previously
determined LU unique identifier may be in use to authenticate the LU.

Why is the "product revision level" required to be an input to the
message digest generator ? Can this field be omitted and if necessary,
replaced by another field that would remain constant across firmware
upgrades in the target ?

Thanks,
Santosh



Dave Peterson wrote:
> 
> * From the T10 Reflector (t10 at t10.org), posted by:
> * "Dave Peterson" <dap at cisco.com>
> *
> Howdy All,
> 
> The version headed for inclusion into SPC-3 is now available:
> 
> ftp://ftp.t10.org/t10/document.02/02-035r2.pdf
> 
> As promised, the exact message input has been specified and
> an example input and output is provided.
> 
> Dave
> *
> * For T10 Reflector information, send a message with
> * 'info t10' (no quotes) in the message body to majordomo at t10.org

-- 
##################################
Santosh Rao
Software Design Engineer,
HP-UX iSCSI Driver Team,
Hewlett Packard, Cupertino.
email : santoshr at cup.hp.com
Phone : 408-447-3751
##################################
*
* 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 mailing list