nanog mailing list archives
Re: Exodus/C&W Depeering
From: smd () clock org (Sean M. Doran)
Date: Tue, 26 Mar 2002 14:04:53 -0800 (PST)
| This isn't something I really care to make a big argument of, but my point | was that for many ISPs, the path will go from: | | SELF - EXODUS | | to: | | SELF - OTHER BACKBONE - C&W | | for a net increase in average path length. Are we talking AS_Path attributes here? If so, all this means is that now we don't announce OTHER BACKBONE routes to C&W/EXODUS, which we probably weren't doing anyway. Or are we talking forwarding paths, which are _different_ (and not necessarily stable even in the presence of perfect AS_Path stability)? If so, have we added any bottlenecks or sources of packet corruption? If none have been added, a change in the number of links and routers traversed is meaningless. (Note that it is possible that the number of links and routers DECREASES). Sean.
Current thread:
- RE: Exodus/C&W Depeering, (continued)
- RE: Exodus/C&W Depeering alex (Mar 26)
- RE: Exodus/C&W Depeering Borchers, Mark (Mar 26)
- RE: Exodus/C&W Depeering Sean M. Doran (Mar 26)
- RE: Exodus/C&W Depeering Hank Nussbacher (Mar 26)
- RE: Exodus/C&W Depeering Chris Parker (Mar 26)
- RE: Exodus/C&W Depeering Bill Woodcock (Mar 26)
- RE: Exodus/C&W Depeering Vadim Antonov (Mar 26)
- Re: Exodus/C&W Depeering Peter Galbavy (Mar 28)
- RE: Exodus/C&W Depeering Hank Nussbacher (Mar 26)
- RE: Exodus/C&W Depeering Sean M. Doran (Mar 26)
- RE: Exodus/C&W Depeering Stephen J. Wilcox (Mar 26)
- Re: Exodus/C&W Depeering Sean M. Doran (Mar 26)
- Re: Exodus/C&W Depeering Patrick W. Gilmore (Mar 26)
- Re: Exodus/C&W Depeering Richard A Steenbergen (Mar 26)
- Re: Exodus/C&W Depeering E.B. Dreger (Mar 26)
- Re: Exodus/C&W Depeering Patrick W. Gilmore (Mar 26)
- Re: Exodus/C&W Depeering Patrick W. Gilmore (Mar 26)
- RE: Exodus/C&W Depeering alex (Mar 26)