> Do you mean the bursty traffic after there is a dropped segment? If there is
> no dropped segment (including ACKs), TCP is as bursty as it is without window
> scaling, sending 3 segments for every ACK (assuming delayed ACK for every 2
> segments). I believe many implementations now have some simple form of
> bursty control. And with SACK and various forms of NewReno, I think TCP is
> not as busrty as it used to be when there is no window scaling.
>
> K. Poon.
> [email protected]
TCP is still bursty over high bandwidth-delay product links while inflating
the congestion window. Basically everything in the window is trasmitted at
once, and when ACKs arrive, the process repeats with a larger window. Thus
larger windows cause the burstiness to proceed for longer amounts of time.
-- Zachary Amsden [email protected] (650) 933-6919 09U-510 Core Protocols
This archive was generated by hypermail 2b29 : Thu Feb 24 2000 - 22:06:18 EST