 | This redirect does not require a rating on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||
| |||||||||||
 | The contents of the Congestion window page were merged into TCP congestion-avoidance algorithm on 2016-03-13. For the contribution history and old versions of the merged article please see its history. |
I would be in favor of removing this stub and redirecting it to TCP Tuning. That article has a more complete discussion of the receive window and other TCP options, and some other articles (e.g. TCP Receive Window) already redirect there. Blandoon 00:02, 21 June 2007 (UTC)
I'm not certain that the window starts at the maximum value. I think it may start at a minimum value and then increase exponentially until a timeout occurs. Then from there on it increases linearly. I left it because I'm not sure though. —Preceding unsigned comment added by 207.207.127.240 (talk) 23:00, 17 December 2008 (UTC)
I am also not certain that the window starts at maximum value. By refering a book of Andrew Tenebaum fourth edition, it has been stated that the window starts from minimum value and it then increases exponentially untill the threshold value and then it increases linearly after the threshold till the timeout value. —Preceding unsigned comment added by 118.102.186.6 (talk) 05:28, 14 February 2010 (UTC)
Idanm (talk) 07:39, 23 February 2010 (UTC)
from the article:
"...the congestion window, also called the TCP receive window..."
The congestion window and the receive window are different. While the congestion window size is kept within each side
of the connection, and receive window size is published to the other side in the tcp header.