SCSI: login response for non-login request.

["John Hufferd" <hufferd@us.ibm.com>]

This is another reminder to folks on this reflector to use the prefix
iSCSI: at the beginning of the subject line, as is shown in this reply.

.
.
.
John L. Hufferd
Senior Technical Staff Member (STSM)
IBM/SSG San Jose Ca
Main Office (408) 256-0403, Tie: 276-0403,  eFax: (408) 904-4688
Home Office (408) 997-6136, Cell: (408) 499-9702
Internet address: hufferd@us.ibm.com


"Sukanta Ganguly" <sganguly@opulentsystems.com>@ece.cmu.edu on 09/28/2002
09:00:24 AM

Please respond to sganguly@opulentsystems.com

Sent by:    owner-ips@ece.cmu.edu


To:    "Michael Morrison" <mmorrison@istor.com>, "IPS" <ips@ece.cmu.edu>
cc:
Subject:    Re: login response for non-login request.



Hi Michael,
   It makes perfect sense. In case of processing the Login request the
   Target is in the Login processing state machine, if you will. Hence
   sending a Login reject is the most appropriate response.
    The development process also stays simple in that manner.

Regards
Sukanta Ganguly
Opulent Systems

*********** REPLY SEPARATOR  ***********

On 9/25/2002 at 11:22 AM Michael Morrison wrote:

>In the last paragraph of section 2.2.3 of draft 17
>
>"Once the Login phase has started, if the target
>receives any PDU except a Login request, it MUST send a Login reject
>(with Status "invalid during login") and then disconnect. If the
>initiator receives any PDU except a Login response, it MUST
>immediately terminate the connection."
>
>Shouldn't the target send back a Reject PDU with PROTOCOL ERROR in this
>case?
>
>why would the target send a Login Response to a non-login request?
>
>Thanks
>
>
>--
>Michael Morrison
>mmorrison@istor.com
>ISTOR Networks
>7585 Irvine Center Dr. Ste 250
>Irvine Ca. 92618
>PGP Key ID:
>http://pgp.mit.edu:11371/pks/lookup?search=0x74C30155&op=index