[e2e] TCP Local Area Normal behaviour? any references?

[Cannara]

Ahhh, yes, but -- there's always at least one.  :]

But, 99.9999% of people have no idea of how their stacks' parameters are set
by default and less idea how those and their OSs interact with their traffic
and links.  Again, ask someone thought to be network wise how much performance
will be lost on a full-MTU link when just 1% of TCP packets are lost (error,
etc., not even congestion).  Ask IT managers how their stack params are set,
and why.  Be ready for blank looks.  :]

And, as to the ephemeral 'capture effect', the vendors have been so successful
making $ selling LAN switches for so long that there are almost no segments
anymore for it to exist on, even if it ever was an issue --  "backpressure"
mateys, backpressure.  It's more relevant that single-chip 16/24-port switches
are in D-Link & Linksys boxes at Fry's for $25 now, and, with sub-100nm
fabbing, they fail more often, with far more obscure & sneaky performance
effects.  {:o] 

Alex

Jon Crowcroft wrote:
> 
> um, yes i recall that - any  pointers to papers/web page/results appreciated.
> 
> We are a bit like Sigmund Freud :-
> we base an entire "science" on pathological behaviour,
> but most TCP connections are not congested,
> just like most people aren't crazy
> (or tell awful austrian 19th century jokes:)
> 
> how many papers written on bottleneck behaviour
> and how few on whats normal?- what we need is
> the Alex Comfort of TCP, so to speak...
> 
> hmm - i foresee a whole new conference on
> packet loss and the unconscious
> and
> beyond the AIMD principle
> and
> endless arguments about IP SLA archetypes and TCP mandalas
> 
> :-)
> 
> In missive <20050121180410.GA6946 at isi.edu>, Aaron Falk typed:
> 
>  >>Jon Crowcroft wrote:
>  >>>
>  >>> how fair/efficient is TCP in normal operation when there's no router
>  >>> or buffer in an intermediate node (yes i knoiw some switches have
>  >>> more than 1 packet buffers but ignore those)
>  >>
>  >>I seem to recall Matt Mathis talking about this at IETF around 5 years
>  >>ago in the context of MAC 'capture effects'.
>  >>
>  >>--aaron
> 
>  cheers
> 
>    jon