RE: iSCSI: UNH plugfest

["Dave Peterson" <dap@cisco.com>]

As previously announced by UNH they will be using the opcodes below.
Thus it would be a good idea for us to also use them.

Dave

-----Original Message-----
From: gwendalg@gg736541.cup.hp.com
[mailto:gwendalg@gg736541.cup.hp.com]On Behalf Of Gwendal Grignou
Sent: Friday, June 29, 2001 2:28 PM
To: Dave Peterson
Cc: ips@ece.cmu.edu
Subject: Re: iSCSI: UNH plugfest


Dave Peterson wrote:

> Below are the opcodes applicable for Rev 06+ testing at the UNH Plugfest:

Those opcodes are different from Rev6 and I didn't find any document
defining
precisely Rev6+, just a bunch of mails.
Not having a precise Rev6+ iSCSI draft will not ease interoperabilty.
Why not stick to Rev6 draft published 04/19/2001 ?

Regards,

Gwendal.

> Valid initiator opcodes are:
>         0x00 NOP-Out (from initiator to target)
>         0x01 SCSI Command (encapsulates a SCSI Command Descriptor Block)
>         0x02 SCSI Task Management Command
>         0x03 Login Command
>         0x04 Text Command
>         0x05 SCSI Data-out (for WRITE operations)
>         0x06 Logout Command
>         0x10 SNACK Request
>
> Valid target opcodes are:
>
>         0x20 NOP-In (from target to initiator)
>         0x21 SCSI Response (contains SCSI status and possibly sense
>                 information or other response information)
>         0x22 SCSI Task Management Response
>         0x23 Login Response
>         0x24 Text Response
>         0x25 SCSI Data-in (for READ operations)
>         0x26 Logout Response
>         0x31 Ready To Transfer (R2T - sent by target to initiator when it
>                                 is ready to receive data from initiator)
>         0x32 Asynchronous Message (sent by target to initiator to indicate
>                                      certain special conditions)
>         0x3f Reject
>
> Initiator opcodes 0x1c-0x1e and target opcodes 0x3c-0x3e are vendor
specific
> codes.