iSCSI : LOGO originated by target.

[Santosh Rao <santoshr@cup.hp.com>]

> Section 2.17 Asynchronous Event
> =========================
> 1) "Target requests Logout on this connection" iSCSI event
> indicator. Why not just allow the target to originate a Logout
> as is done in Fibre Channel ?

> Besides, this AEN does not meet the requirement.
> How does the target convey the CID of the connection to be
> logged out ?
> [js] CID an timeout appear now in parameters [/js]

The simplest approach and the most expeditious error recovery is to
allow the target to originate a Logout. To send an AEN and then wait for
the initiator to log out is opening up the target to dependencies on the
initiator honoring and acting on that AEN, which is un-necessary.

This should not be a violation of SAM since SAM does not restrict
unsolicited traffic for the interconnect specific commands. (Fibre
Chanel does this.)

Thanks,
Santosh

> I do not think SAM-2 lays any guidelines for how the SCSI
>  interconnect protocol handle its native PDUs. (i.e. non-scsi
> operations).
> Fibre Channel allows unsolicited inbound traffic for ELS and
> LS commands and allowing Logout and NOP-OUT
> erhaps better thought of as a NOP command) commands to
> be originated by targets would be desirable and would get rid of this
> particular AEN iSCSI event indicator.
begin:vcard 
n:Rao;Santosh 
tel;work:408-447-3751
x-mozilla-html:FALSE
org:Hewlett Packard, Cupertino.;SISL
adr:;;19420, Homestead Road, M\S 43LN,	;Cupertino.;CA.;95014.;USA.
version:2.1
email;internet:santoshr@cup.hp.com
title:Software Design Engineer
x-mozilla-cpt:;21088
fn:Santosh Rao
end:vcard