Re: iSCSI: SNACK RunLength

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

Michael,

The paragraph says that if you issue a SNACK after the MaxPDURecvLength has decreased you should use RunLength 0 (meaning all) instead of a specific runlength which might not be accurate anymore.

Julo

Michael Schoberg <michael_schoberg@cnt.com> Sent by: owner-ips@ece.cmu.edu 25-03-02 19:43 Please respond to Michael Schoberg

To:        "IPS Reflector (E-mail)" <ips@ece.cmu.edu>         cc:                 Subject:        iSCSI: SNACK RunLength

Am I just not reading this or can this paragraph use some help?  Can someone
give an interpretation? 

   9.16.3  RunLength
                                  ...

           The first data SNACK, issued after initiator's MaxRecvPDULength 
           decreased, for a command issued on the same connection before the

           change in MaxRecvPDULength, MUST use RunLength "0" to request 
           retransmission of any number of PDUs (including one).  The number
of 
           retransmitted PDUs in this case, may or may not be the same as
the 
           original transmission, depending on whether loss was before or
after 
           the MaxRecvPDULength was changed at the target.


Does this refer to something like:

For connections with unacknowledged PDUs that undergo MaxRecvPDULength
negotiation ...