RE: iSCSI: Question on MaxCmdRN update rule

[Charles Monia <cmonia@NishanSystems.com>]

Hi Julo:

I was referring to rev 02, which was current as of the posting date.

The problem is fixed in rev 03.

Charles

> -----Original Message-----
> From: julian_satran@il.ibm.com [mailto:julian_satran@il.ibm.com]
> Sent: Friday, January 12, 2001 1:53 AM
> To: ips@ece.cmu.edu
> Subject: Re: iSCSI: Question on MaxCmdRN update rule
> 
> 
> 
> 
> Charles,
> 
> What version of the document are you referring to?
> 
> Julo
> 
> Charles Monia <cmonia@NishanSystems.com> on 11/01/2001 05:15:08
> 
> Please respond to Charles Monia <cmonia@NishanSystems.com>
> 
> To:   Julian Satran/Haifa/IBM@IBMIL
> cc:   "Ips (E-mail)" <ips@ece.cmu.edu>
> Subject:  iSCSI: Question on MaxCmdRN update rule
> 
> 
> 
> 
> Hi Julo:
> 
> I don't understand the MaxCmdRN update policy as defined below:
> 
> "2.3.10 MaxCmdRN - maximum CmdRN acceptable from this initiator
> 
> MaxCmdRN is a reference number that the target iSCSI returns to the
> initiator to indicate the maximum CmdRN the initiator can send. The
> initiator must ignore values not between the current value of the
> ExpCmdRN and MaxCmdRN; this may be required when updates arrive out
> of order (they travel on different TCP connections)."
> 
> As I interpret the above, values not within the upper and lower limits
> given
> above must be discarded.
> 
> I would think this parameter should be updated when a new 
> value greater
> than
> the current MaxCmdRN is received.
> 
> Charles
> 
> 
>