North American Network Operators Group|
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical
Re: Discovering AS Path confederation...
On Wed, 25 Jul 2001, Chris Rapier wrote: <snip> > I'm plotting observed traffic against BGP reported AS paths to get a > logical view of traffic flow in a smallish network (I2). However, it was > pointed out to me (by Bradley Huffaker) that the BGP reported path does > not always correspond to the ASes a packet actually traverses. Propagation of a route in BGP requires that the network actually use that route. On the surface, this would seem to ensure that the actual path must match the BGP path. This assumes, however, that the packet follows the same route from end to end. If there is any route filtering, the packet may follow a short prefix until it reaches a network which has a longer prefix in its routing table. In that case, the packet will then follow the longer prefix. Someone looking at the BGP tables from the source would only see the route for the short prefix and may infer the wrong AS path. <snip> > My contention is that the vast majority of this seeming divergence is > the result of AS confederation and not any specific failure of the > protocol (or implementation) as a whole. <snip> I haven't thought through this one. Can you enlighten me offline? > > What I was thinking of doing was to collect a large number of traces and > their corresponding traversed ASes and run statistical analysis on it to > infer the confederations. <snip> Contact me offline. We may be able to help configure and run some tests. Steve Schaefer Dashbit - The Leader In Internet Topology www.dashbit.com www.traceloop.com