Re: Status summary on multiple connections

["Mark A. Carlson" <mark.carlson@sun.com>]

"Randall R. Stewart" wrote:
> 
> I really do NOT see how one can allow a TCP to deliver out of order
> though, oh
> I know technically how to do it, but it is a fundamental violation
> of what TCP is supposed to be delivering.... i.e. the bytes being
> transfered from 0 to N...

The scenario which everyone seems to be worried about is that
packets are delivered in order, but the ACK for one of them is
lost going back. Everything gets delivered to iSCSI, then the
non-ACKed packet is delivered again. 

Does this really happen in today's stacks?

It seems like the TCP stack would see it as a duplicate that
has already been delivered to the upper layer and drop it. 
TCP does have sequence numbers and knows this. The only way
I could imagine this happening is if there was sufficient
data to wrap the TCP sequence space.

-- mark