Hi, At 21:20 06/06/00, Henk Uijterwaal (RIPE-NCC) wrote:
One thing we can do is add a query with a field "AS-PATH", you enter network, peer, data and time, and the output would be something like:
[...] A 193.0.0.0/8 17/11/1999 206.251.0.85 3549 1740 11127 8708 A 193.0.0.0/8 17/11/1999 193.0.0.56 3333 286 1740 11127 8708 A 193.0.0.0/8 17/11/1999 195.8.100.22 8259 5413 1740 11127 8708 A 193.0.0.0/8 17/11/1999 193.0.0.56 3333 1103 6453 1239 1785 11127 8708 [...]
If you had entered "11127" as the AS path, it would select all records, if you had entered "1740 11127", then the first 3 will be highlighted, etc.
The idea would be to have a table representation, with lines representing changes (updates) over time, and columns, representing peers. In the above case, with an input of "AS1=1740" and "AS2=1785", one might have: Date & Time |206.251.0.85|193.0.0.56|195.8.100.22|1740|1785 17/11/1999 01:23|1740 |1740 |1740 |3 |0 17/11/1999 02:34|1740 |1785 |1740 |2 |1 Of course, colours instead of 1740 and 1785 would be great :-) This way, one can see very quickly see which of multiple paths is used to get to a specific network among a large selection of peers, and how that changes over time (with the introduction of a new transit provider or of a new peering connection, with AS padding changes, etc.). It's just a more synthetic view of the current output, which only lists the updates themselves. While I'm at RIS-related matters, have you ever though about "reproducing" the recorded BGP updates? This could be useful for testing purposes: a real life sample of BGP updates from a wide selection of peers is always better than an always too simple lab setup... Some kind of "delayed playback". Might also be useful to reproduce known past "events"... Jacques. --- Jacques Caron PSINetworks Europe Network Engineer PSINet Europe Regional Peering Coordinator Planete.net IT Manager Mail: 8/10 rue Nieuport - 78140 Velizy - France Phone: +33 (0)1 34 63 19 71 - Fax: +33 (0)1 34 63 19 51