Re: iSCSI - opcodes

[julian_satran@il.ibm.com]

Brian,

Vendors can negotiate the use of their specific opcodes at login through
... vendor specific text-keys.
I am not a big fan of vendor-specific op-codes or keys but they give people
an opportunity to experiment with new things without having to get to a
"rough consensus".

Julo

Brian Pawlowski <beepy@netapp.com> on 28-05-2001 22:39:02

Please respond to Brian Pawlowski <beepy@netapp.com>

To:   Julian Satran/Haifa/IBM@IBMIL
cc:   ips@ece.cmu.edu
Subject:  Re: iSCSI - opcodes




I have a problem with this statement.

Vendor specific opcodes in a shared opcode space are subject to collision
unless a management framework wi specified to deal with the opcode
space.

What is the intention here?  Is there a precedent in SCSI (FCP or whatever)
for such use?

If they are just unused codes, I would propose they be left RESERVED.

If you intend to use them, I would like to hear how it will be managed
to ensure interoperability.

>    Initiator opcodes 0x38, 0x3a, 0x3c and 0x3e and target opcodes 0x39,
>    0x3b, 0x3d and 0x3f are vendor specific codes.