:what should happen is this:
:
:h1 send: p1 p2 p3
:h2 recv: p1 p3
:
:h1 recv: (nothing acks lost)
:h2 send: ack1 ack1 ack1 (dude, i missed a packet)
:
:h2 send: ack1 ack1 ack1 (dude, i missed a packet)
:h1 recv: ack1 ack1 ack1
:h1 send: p2 p3
:
:Basically, will the reciever keep acking not if 'it detects packet loss',
:but rather 'as long as packets are lost'.
:
:--
:-Alfred Perlstein [[EMAIL PROTECTED]]
Yuch. That won't help. Basically you are taking a brute-force
approach "Send the ack a whole bunch of times in case some of them
get lost". Such an approach does not typically work very well. For
example, if the packet loss occured due to link congestion your
solution will actually make the link more congested rather then less.
If there is significant latency in the path the acks can get into
a following run with the transmitter, making the transmitter believe
that the packet loss is worse then it actually is and responding in kind,
resulting in even more incorrect acks.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
