[3448] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Ping flooding

daemon@ATHENA.MIT.EDU (Vadim Antonov)
Fri Jul 12 15:15:36 1996

Date: Fri, 12 Jul 1996 12:05:13 +0800
From: avg@ncube.com (Vadim Antonov)
To: jburgan@BayNetworks.com, vern@ee.lbl.gov
Cc: avg@ncube.com, bjp@eng.umd.edu, jerry@gi.net, nanog@merit.edu

You need to have _very_ different path parameters to cause TCP
noticeable problems (and then if one of the paths is that bad
you're screwed up anyway).

Most of asymmetrical paths are quite "symmetrical" parameter-wise.

--vadim

Vern,

>  (ftp://ftp.ee.lbl.gov/papers/routing.SIGCOMM.ps.Z).  I really wanted to
>  come up with some reason why asymmetric routing has serious implications
>  for TCP performance, but wasn't able to.  I guess this is a good thing,

Maybe in a perfect world, but given that all ISPs are not created equal, it 
is usually the case that the two paths don't have the same latency and packet
loss characteristics. 

Jeff


home help back first fref pref prev next nref lref last post