RE: iSCSI: key negotiation - Unrecognized value?

["Julian Satran" <Julian_Satran@il.ibm.com>]

Correct - I have removed it - Julo

"Buck Landry" <blandry@crossroads.com> Sent by: owner-ips@ece.cmu.edu 21-02-02 06:42

To:        <pat_thaler@agilent.com>, <ips@ece.cmu.edu>         cc:                 Subject:        RE: iSCSI: key negotiation - Unrecognized value?

>>>
If it is during Login Phase, then the target can't send a Reject PDU to
indicate protocol error because only Login Request and Login Response PDUs
are allowed.
<<<

Not to take this too far off track, but the exact phrase in the v10 draft,

"Before the Full Feature Phase is established, only Login Request and Login Response PDUs are allowed"

.. would seem to make Reject PDU reason code 0x01, "Full Feature Phase Command before login", fairly useless.

--buck

-----Original Message-----
From: pat_thaler@agilent.com [mailto:pat_thaler@agilent.com]
Sent: Wednesday, February 20, 2002 7:29 PM
To: santoshr@cup.hp.com; ips@ece.cmu.edu
Subject: RE: iSCSI: key negotiation - Unrecognized value?


Santosh,

If it is during Login Phase, then the target can't send a Reject PDU to
indicate protocol error because only Login Request and Login Response PDUs
are allowed. 

A Login Response with a status class of Initiator Error and a status detail
of Initiator Error seems reasonable. None of the other status details seem
to quite fit the description. An invalid value isn't a missing parameter.

That would be consistant with the text on Negotiation Failures. 

I don't think it should respond to the key with not understood, but a
response to the key of Reject would be reasonable and doing so might make it
easier to debug the negotiation problem.

Regards,
Pat

<snip>