Re: How to Quicken TCP Re-transmission?

Actually, TCP is a single sliding window protocol, which limits its
performance on seriously lossy and long delay transmission media.
We assume that a sender has sent packets [A] [B] [C] [D] [E] while
the receiver has received packets [A] [C] [E]. With TCP the receiver can
only tell the sender that [A] has reached. If the receiver can notify
the sender that both [B] and [D] should be re-sent, the performance will
be better.
------------------------------------------------------------------------
From Beijing, China

Mark Allman wrote:


1. Receiver should tell sender to re-send as soon as possible.
(But TCP makes receiver purely passive)

This isn't really going to help you at all. With SACK (especially, but
even without it) the receiver isn't really in a whole lot better
position than the sender to judge when a packet is actually lost. Some
people have worked on SNACKs (selective NEGATIVE acknowledgments), but
my opinion is that the results (that I have seen) show them to be fairly
equivalent to SACK in terms of performance.

2. Receiver should tell sender what is really necessary to re-send.
(Sometimes only a single ACK number of TCP cannot include enough
information)

RFC2018. (Which provides more than a single ACK number. But, this
doesn't make the receiver tell the sender what to resend. The logic
still resides at the sender.)

allman







_______________________________________________
freebsd-net@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: Question: Designing a protocol over TCP
    ... Your receivecall will be completed as soon as an incoming TCP segment has ... Once your recv() call has been completed, ... sender and receiver side makes it possible for the receiver side to always ... complete recvcalls with exactly the number of bytes the sender has sent. ...
    (microsoft.public.win32.programmer.networks)
  • Re: Controlling rate of tcp/ip data transmission
    ... the receiver has 0 TX and the sender has 0 RX on the connection. ... TCP was developed precisely to solve problems just like ... to the sender you cannot use TCP, and some sort of rate-based pacing ...
    (comp.os.linux.networking)
  • Re: How to Quicken TCP Re-transmission?
    ... even without it) the receiver isn't really in a whole lot better ... position than the sender to judge when a packet is actually lost. ... equivalent to SACK in terms of performance. ... (Sometimes only a single ACK number of TCP cannot include enough ...
    (freebsd-net)
  • Re: Simulating smaller MTU? ie sending small packets.
    ... The smaller the packets are, ... This is due to the fact that TCP ... > What I observe is that once the receiver is not ... > keeping up with the speed the sender is spewing packets, ...
    (comp.lang.perl.misc)
  • Re: Neutral Format as a Coupling reduction idea that doesnt work.
    ... There are potentially unlimited and unexpected side effects for both sender and receiver. ... That definition defines the semantics of the just the data packet. ... That represents a solution level coupling but at least it is very narrowly focused on the message definition rather than what each side does with the information. ...
    (comp.object)