[e2e] TCP implementations in various OS's

Lachlan Andrew lachlan.andrew at gmail.com
Wed May 12 17:05:02 PDT 2010

On 13 May 2010 06:29, Detlef Bosau <detlef.bosau at web.de> wrote:
> However, can we agree that a good measure to prevent misbehaviour (which
> _can_ result from a single flow using window scaling while the competitors
> don't) is to enable window scaling actually on _all_ flows or on _no_ flows?
> Although this might lead to some moderate level of congestions even in lines
> with comparably moderate load?

I don't think that those conditions are necessary.

Any flow is entitled to send at *less* than their congestion window.
If they choose to do that by limiting the protocol to a legacy mode
(no window scaling), that is their prerogative.  Window scaling is an
approved mechanism for allowing the intended AIMD behaviour of Reno.

The fact that a saturated source sends on a link with a source which
chooses not to use its full window doesn't mean the saturated source
is "misbehaving".


Lachlan Andrew  Centre for Advanced Internet Architectures (CAIA)
Swinburne University of Technology, Melbourne, Australia
<http://caia.swin.edu.au/cv/landrew>  Ph +61 3 9214 4837

More information about the end2end-interest mailing list