Re: login response for non-login request.

[Bill Studenmund <[e-mail]>]

On 25 Sep 2002, 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?

No. This case explicitly requires a Login Response.

> why would the target send a Login Response to a non-login request?

You mean besides the fact that's what the standard says? :-)

I think the idea is if we're not in FFP, only Login Req/Rsp PDUs are
valid. If we're in FFP, everything except them is valid. If the target
thinks the initiator broke that rule, it should not also break the rule in
telling the initiator that the initiator messed up. Thus a Login Rsp.

Also, things should be clearer for the initator. If it thinks it's not in
FFP, and it gets a PDU other than Login Rsp, it can immediately flag it as
an error.  It doesn't have to look and see, "oh, the target is saying I
did something wrong."

Take care,

Bill