On Fri, 25 Jun 2004, Daniel Lang wrote: > liamfoy_at_sepulcrum.org wrote on Fri, Jun 25, 2004 at 11:24:01AM +0200: > [..] > > > > I just commited the work done at Yahoo! to implement SACK in our tcp > > > > stack. Please report any bugs or problems and we'll work on getting > > > > them addressed. > [..] > > What is SACK anyone? > [..] > > "Selective Acknowledgement", it allows a host/router to explicitly > acknowledge TCP segments and retransmit them, such that if a segment > gets lost, it can be retransmitted from the last hop instead of the > connection endpoint, which would result in a much larger delay. > Especially if you have wireless links, SACK can be a huge improvement. > > Please correct/elaborate, I'm not sure if I got that entirely right, > except for the idea. ;-) Mostly right, except that it's only the end-hosts in the TCP connection. Technically, one can be a router, but I'm guessing that's not the common case. Basically, the original TCP said "retransmit everything" when it realized a packet was dropped, and TCP SACK allows it to be more selective, which conserves bandwidth, which has the effective of reducing load, reducing latency, etc. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert_at_fledge.watson.org Principal Research Scientist, McAfee ResearchReceived on Fri Jun 25 2004 - 11:59:54 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:58 UTC