RE: iSCSI: invalid key value

[kevin_lemay@agilent.com]

I disagree,

This is an initiator error and the login should be rejected as such.
NotUnderStood should be returned in the key with the login rejected.

Kevin Lemay
Agilent Technologies

-----Original Message-----
From: Steve Senum [mailto:ssenum@cisco.com]
Sent: Friday, January 25, 2002 7:57 AM
To: ietf-ips
Cc: Eddy Quicksall
Subject: Re: iSCSI: invalid key value


Eddy,

If someone sends me "DataDigest=#$C32C,none".
I will respond "DataDigest=none".

I think responding with "DataDigest=NotUnderstoood"
or one of the other special responses would be wrong,
as there is nothing wrong with the key ("DataDigest").

Since I support "none", and can't tell "#$C32C"
is really "CRC32C", I believe "DataDigest=none"
is the only correct response.

Steve Senum

-----------------------------------------
Subject: iSCSI: invalid key value
   Date: Fri, 25 Jan 2002 10:17:12 -0500
   From: Eddy Quicksall <Eddy_Quicksall@ivivity.com>
     To: "ips@ece. cmu. edu (E-mail)" <ips@ece.cmu.edu>




If a key has a value that is not valid, do you know how I respond?

       

For example, DataDigest=#$C32C,none. The valid values are CRC32C,none.

       

If I say DataDigest=NotUnderstood, wouldn't that mean the key was not
understood?

       

If I say DataDigest=Reject, that would mean I don't support the key for the
current initiator.

       

If I say DataDigest=Irrelevant, that would mean the digest is not relevant
for
the current negotiation.

 

If I say DataDigest=none, that would mean I don't support CRC32C when in
reality
I do. It could be that, since there is no digest in login,
the 1st two letters got changed.

 

If I treat it as a protocol error and send a response with status == 0200 or
0201, then the initiator does not know why.

       

Eddy