Lines Matching refs:sender
595 packet, so the sender needs to retransmit this packet. In this
596 situation, the sender adds 1 to TcpExtTCPSACKReneging. A receiver
598 unusual, it is allowed by the TCP protocol. The sender doesn't really
599 know what happened on the receiver side. The sender just waits until
600 the RTO expires for this packet, then the sender assumes this packet
611 order packet. Thus the sender would find more ACks than its
612 expectation, and the sender knows out of order occurs.
617 sender sends packet 1,2,3,4,5, and the receiving order is
618 1,2,4,5,3. When the sender receives the ACK of packet 3 (which will
627 detect reorder: (1) DSACK is received by the sender. It means the
628 sender sends the same packet more than one times. And the only reason
629 is the sender believes an out of order packet is lost so it sends the
630 packet again. (2) Assume packet 1,2,3,4,5 are sent by the sender, and
631 the sender has received SACKs for packet 2 and 5, now the sender
632 receives SACK for packet 4 and the sender doesn't retransmit the
633 packet yet, the sender would know packet 4 is out of order. The TCP
663 duplicate packets to the sender. There are two kinds of
667 sender side.
674 sends a DSACK to the sender.
679 DSACK to the sender.