Jump to content

Talk:TCP congestion-avoidance algorithm

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by 68.0.120.35 (talk) at 00:57, 16 February 2007 (What is triple-ack ?). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

full algorithm in tcp tahoe


graphs showing the characteristic 'shapes' of window size over time, for congestion avoidance and TCP slow-start. These are helpful for grokking what goes on.


When it says Reno: halve congestion window on triple-ACK I think it should be Reno: congestion window set to half FlightSize on triple-ACK where FlightSize is the amount of outstanding data in the network.

This is based on what it says RFC 2581 --200.122.102.147 02:19, 30 November 2005 (UTC)(German Kruszewski)[reply]

TCP Tahoe and Reno

SlowStart

  • SlowStart exists to avoid congestion at startup, not to avoid wasting time. Otherwise you would start at a higher value (not 2MSS) to get things going.
  • You dont enter Congestion Avoidance after a packet loss, but after reaching a SlowStart Threshold.
  • Packet Loss is also detected by Timeout

XCP

XCP sounds good, but has some bad behavior, especially in dynamically changing network scenarios. The "mathematical" results in the XCP dissertation considering the scenarios in which XCP can be used are not worth to be read (I have to write this so hard). If five parameters can vary in a large range, it is absolutely nonsense to fix four of them in a middle range to show that XCP works over a wide range for the fith one. In most realistic scenarios at least two of the parameters are far away from their "middle value". —The preceding unsigned comment was added by 217.247.68.155 (talk) 03:34, 9 December 2006 (UTC).[reply]

triple-ack

What is triple-ack ? triple-ack currently redirects to TCP congestion avoidance algorithm, which doesn't even mention the word. Is the explanation of what it is supposed to be in this article, or should triple-ack redirect to some other article?

The article does mention "the missing packet that was signaled by 3 duplicate ACKs". Is that the same as a "triple-ack"? The explanation is too brief to make any sense. I thought the reciever only sent an ACK for a received (non-missing) packet. Why would a missing packet generate even 1 ACK, much less 3 ACKs ?

--68.0.120.35 00:57, 16 February 2007 (UTC)[reply]

Retrieved from "https://en.wikipedia.org/w/index.php?title=Talk:TCP_congestion-avoidance_algorithm&oldid=108487858"