June 2000 - routing-wg - mailman.ripe.net

Problems with RIPE210
by Philip Smith 05 Jul '00

05 Jul '00

Hi, There are some problems/errors/omissions in RIPE-210 which are causing me, and some of the ISPs trying to implement the recommendations, some problems. It seems that the choice has been made to include X.root-servers.net *and* X.gtld-servers.net, but I can find no reference to these in the description of the example configuration in S2.3. It would be good to do this so that people know what they are dampening. Also, an expansion of S1.6 would achieve this quite well. It is also worth noting that the "root networks" change from time to time, and that all ISPs should check that these network announcements are still current before implementing the recommendations. You'll be surprised how many people simply cut and paste the configuration without checking the detail. Some problems: - S1.6 refers to "probably" removing the A, D and H servers as they are on /16 prefix announcements. But A is on a /24 announcement. (Is there evidence to suggest that a /16 flaps less than a /24 - the analysis I've done in AsiaPac doesn't prove anything conclusively.) - In S2.3, B, C, D, H, K, L and M are omitted. With no explanation as to why. They are not all on /16 prefix announcements. - In S2.3, A&J network is listed twice - why? - In S2.3, if including the gtld servers is the goal, G.gtld and I.gtld are omitted. I.gtld is announced on a /24 network. The list I have been recommending to ISPs in AsiaPac for about the last year is below: ip prefix-list rootns permit 198.41.0.0/24 ! A & J ip prefix-list rootns permit 128.9.0.0/16 ! B ip prefix-list rootns permit 192.33.4.0/24 ! C ip prefix-list rootns permit 128.8.0.0/16 ! D ip prefix-list rootns permit 192.203.230.0/24 ! E ip prefix-list rootns permit 192.5.4.0/23 ! F ip prefix-list rootns permit 192.112.36.0/24 ! G ip prefix-list rootns permit 128.63.0.0/16 ! H ip prefix-list rootns permit 192.36.148.0/24 ! I ip prefix-list rootns permit 193.0.14.0/24 ! K ip prefix-list rootns permit 198.32.64.0/24 ! L ip prefix-list rootns permit 202.12.27.0/24 ! M which is basically the current list of roots and their corresponding prefixes as announced to the Internet. If the decision is to include X.gtld-servers.net, the list could be augmented as: ip prefix-list gltdns permit 198.41.3.0/24 ! A ip prefix-list gtldns permit 205.188.128.0/17 ! C ip prefix-list gtldns permit 198.17.208.0/24 ! F ip prefix-list gtldns permit 192.215.0.0/16 ! G ip prefix-list gtldns permit 216.33.64.0/19 ! H ip prefix-list gtldns permit 192.36.144.0/24 ! I ip prefix-list gtldns permit 198.41.0.0/24 ! J ip prefix-list gtldns permit 195.8.96.0/19 ! K ip prefix-list gtldns permit 210.176.0.0/16 ! M but I'd probably list them under a separate route-map section of Golden Networks. I hope the above can be incorporated in RIPE-210 so that accuracy is achieved. best wishes! philip -- -------------------------------------------------------- Philip Smith ph: +61 7 3238 8200 Consulting Engineering, Office of the CTO, Cisco Systems --------------------------------------------------------

4 8

The Cidr Report
by Tony Bates 30 Jun '00

30 Jun '00

This is an auto-generated mail on Fri Jun 30 12:00:00 PDT 2000 It is not checked before it leaves my workstation. However, hopefully you will find this report interesting and will take the time to look through this to see if you can improve the amount of aggregation you perform. The report is split into sections: 0) General Status List the route table history for the last week, list any possibly bogus routes seen and give some status on ASes. 1) Gains by aggregating at the origin AS level This lists the "Top 30" players who if they decided to aggregate their announced classful prefixes at the origin AS level could make a significant difference in the reduction of the current size of the Internet routing table. This calculation does not take into account the inclusion of holes when forming an aggregate so it is possible even larger reduction should be possible. 2) Weekly Delta A summary of the last weeks changes in terms of withdrawn and added routes. Please note that this is only a snapshot but does give some indication of ASes participating in CIDR. Clearly, it is generally a good thing to see a large amont of withdrawls. 3) Interesting aggregates Interesting here means not an aggregate made as a set of classful routes. Thanks to xara.net for giving me access to their routing tables once a day. Please send any comments about this report directly to me. Check http://www.employees.org/~tbates/cidr-report.html for a daily update of this report. ------------------------------------------------------------------------------ CIDR REPORT for 30Jun00 0) General Status Table History ------------- Date Prefixes 230600 80236 240600 80187 250600 80366 260600 80526 270600 80814 280600 80884 290600 80973 300600 80928 Check http://www.employees.org/~tbates/cidr.plot.html for a plot of the table history. Possible Bogus Routes --------------------- *** Bogus 65.56.64.0/21 from AS2941 AS Summary ---------- Number of ASes in routing system: 7777 Number of ASes announcing only one prefix: 4376 (2400 cidr, 1976 classful) Largest number of cidr routes: 964 announced by AS701 Largest number of classful routes: 1070 announced by AS701 1) Gains by aggregating at the origin AS level --- 30Jun00 --- ASnum NetsNow NetsCIDR NetGain % Gain Description AS271 436 149 287 65.8% BCnet Backbone AS1221 645 445 200 31.0% TELSTRA-AS AS7046 534 360 174 32.6% COQUI-NET PRTC Internet AS9269 183 55 128 69.9% Hong Kong CTI AS9706 152 26 126 82.9% Pusan Metropolitan City Office of AS2609 127 12 115 90.6% EUnet-TN AS9304 122 18 104 85.2% Hutchcity AS7657 293 190 103 35.2% The Internet Group Limited AS7545 153 55 98 64.1% TPG Internet Pty Ltd AS6429 210 118 92 43.8% RDC-INTERNET AS174 563 471 92 16.3% Performance Systems International AS7496 127 42 85 66.9% Power Up AS4293 328 243 85 25.9% Internal ASN for C&W AS705 343 263 80 23.3% ALTERNET-AS AS701 1070 998 72 6.7% Alternet AS577 250 178 72 28.8% Bell Backbone AS724 229 158 71 31.0% DLA-ASNBLOCK-AS AS3908 274 205 69 25.2% Supernet, Inc. AS1727 152 83 69 45.4% MRMS-WEST AS9557 95 28 67 70.5% Pakistan Telecommunication Compan AS3602 304 245 59 19.4% Sprint Canada Inc. AS6595 108 50 58 53.7% DODDSEUR AS5106 88 30 58 65.9% AADS-COLUMBUS AS7568 81 24 57 70.4% C.S. Communications Co., Ltd. AS4740 331 275 56 16.9% Ozemail Pty Ltd (ASN-OZEMAIL) AS3749 112 56 56 50.0% TECNET AS7018 545 492 53 9.7% AT&T WorldNet Service Backbone AS1785 361 312 49 13.6% NYSERNet Backbone AS209 257 209 48 18.7% Qwest Communications AS14562 80 35 45 56.2% UNKNOWN For the rest of the previous weeks gain information please see http://www.employees.org:80/~tbates/cidr-report.html 2) Weekly Delta Please see http://www.employees.org:80/~tbates/cidr-report.html for this part of the report 3) Interesting aggregates Please see http://www.employees.org:80/~tbates/cidr-report.html for this part of the report

1 0

RIPE NCC Region Weekly Routing Report
by Routing Analysis 29 Jun '00

29 Jun '00

This is an automated weekly mailing sent to the RIPE Routing WG e-mail list describing the state of the Internet Routing Table in Europe, Middle East and North Africa. Daily listings are sent to bgp-stats(a)lists.apnic.net For a graphical representation, please see http://www.apnic.net/stats/bgp. If you have any comments please contact Philip Smith <pfs(a)cisco.com>. Europe, Middle East, North Africa Report 30 Jun, 2000 Analysis Summary ---------------- BGP routing table entries examined: 82924 Origin ASes present in the Internet Routing Table: 7793 Origin ASes announcing only one prefix: 2549 Transit ASes present in the Internet Routing Table: 1085 Average AS path length visible in the Internet Routing Table: 5.2 Max AS path length visible: 15 Illegal AS announcements present in the Routing Table: 5 Non-routable prefixes present in the Routing Table: 0 Prefixes being announced from the IANA Reserved Address blocks: 2 Number of addresses announced to Internet: 1182034576 Equivalent to 70 /8s, 116 /16s and 106 /24s Percentage of available address space announced: 31.9 Percentage of allocated address space announced: 63.7 Percentage of available address space allocated: 50.1 RIPE Region Analysis Summary ---------------------------- Prefixes being announced by RIPE Region ASes: 13030 Prefixes being announced from the RIPE address blocks: 10253 RIPE Region origin ASes present in the Internet Routing Table: 2077 RIPE Region origin ASes announcing only one prefix: 970 RIPE Region transit ASes present in the Internet Routing Table: 397 Average RIPE Region AS path length visible: 5.8 Max RIPE Region AS path length visible: 15 Number of RIPE addresses announced to Internet: 88849150 Equivalent to 5 /8s, 75 /16s and 186 /24s Percentage of available RIPE address space announced: 75.7 RIPE AS Blocks 1877 - 1901, 2042, 2047, 2107 - 2136, 2585 - 2614 2773 - 2822, 2830 - 2879, 3154 - 3353, 5377 - 5631 6656 - 6911, 8192 - 9215, 12288 - 13311, 15360 - 16383 RIPE Address Blocks 62/8, 193/8, 194/7, 212/7 and 217/8 RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /19 equiv Description 3301 385 281 TeliaNet Sweden 1257 333 267 Swipnet AB 1270 249 390 UUNET Germany 1849 248 461 PIPEX 1275 231 1131 DFN IP Service 3320 217 249 Deutsche Telekom AG 786 181 959 JANET IP Service 719 180 145 LANLINK 5515 174 362 Sonera Finland 517 161 2247 Xlink 2609 127 4 EUnet-TN 1267 126 947 IUnet S.p.A 2856 124 271 BTnet UK Regional network 3303 120 286 Swisscom 9057 110 37 Level 3 public IP n 3215 102 124 RAIN 1901 92 74 EUnet Austria 8895 92 28 Saudi Arabia AS 1290 83 195 PSINet UK Ltd. Global Per AS prefix count summary ---------------------------------- ASN No of nets /19 equiv Description 701 2040 3180 UUNET Technologies, Inc. 7018 1113 3044 AT&T 1 894 4553 BBN Planet 1221 894 979 Telstra 7046 865 492 UUNET Technologies, Inc. 2914 774 1410 Verio, Inc. 3561 704 1666 Cable & Wireless USA 1239 701 1746 Sprint ICM-Inria 174 638 2835 PSINet Inc. 705 623 2085 UUNET Technologies, Inc. 1785 524 832 Sprint ICM 271 468 411 BCnet Backbone 2764 462 117 connect.com.au pty ltd 3549 455 345 Frontier GlobalCenter 3602 450 78 Sprint Canada 209 436 379 Qwest 1740 435 623 CERFnet 3908 429 354 Supernet, Inc. 4293 404 69 Cable & Wireless USA List of Illegal AS's (Global) ----------------------------- Bad AS Designation Network Transit AS Description 64602 PRIVATE 63.236.57.0/24 209 Qwest 64601 PRIVATE 63.236.90.0/24 209 Qwest 61200 RESERVED 163.247.54.0/24 6429 RdC Internet 64512 PRIVATE 193.39.51.0/24 5462 Cable Internet Ltd 64605 PRIVATE 208.47.206.0/24 209 Qwest Advertised IANA Reserved Addresses ---------------------------------- Network Origin AS Description 39.96.40.224/30 14408 iCAIR 65.56.64.0/21 2941 Community News Service Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:24 /9:4 /10:5 /11:9 /12:26 /13:49 /14:167 /15:285 /16:6533 /17:863 /18:1708 /19:5537 /20:3330 /21:3512 /22:5292 /23:7114 /24:47649 /25:135 /26:182 /27:85 /28:75 /29:77 /30:155 /31:0 /32:108 End of report

1 0

Re: RE: RIPE Prefix Filter Recommendation?
by philip bridge 27 Jun '00

27 Jun '00

At 12:29 27.06.00 +0200, Lars Marowsky-Bree wrote: >On 2000-06-27T12:25:34, > Fredrik Rosenbecker <fredrik.rosenbecker(a)ip-only.net> said: > > > Yes, such a document could be useful. We're using a prefix-list as shown below. > > We could use it as a starting-point to establish a standard prefix filter, or > > as Randy put it, a prefix filter technical coding advice. > >What is also very helpful is to point out the usefulness of anti-spoofing >rules - ie filter your own netblocks when they are announced to you, >_including_ more specific routes ;-) Hm. Yes. But this gets us into a controversial issue since filtering more specifics from your own netblocks means your multihomed customers don't get connectivity to you when the line between you and them is down. I am a bit worried about expanding the scope of this to the point where we get bogged down in arguments about such practices. It seems to me that there is a large body of non-controversial practices that simply require collation and documentation in order to acheive a major effect. We should stick to those, at least in the first instance. Phil >Sincerely, > Lars Marowsky-Brï¿½e <lmb(a)suse.de> > >-- >Perfection is our goal, excellence will be tolerated. -- J. Yahl Philip Bridge Nextra (Schweiz) AG <www.nextra.ch> Tel: +41 031 985 88 06 / Mobile: +41 79 659 75 50 E-Mail: <mailto:bridge@nextra.ch> Disclaimer: <http://www.nextra.ch/signature_nw.html>

2 1

RIPE NCC CIDR blocks - smallest allocations
by Joao Luis Silva Damas 27 Jun '00

27 Jun '00

During the RIPE 36 meeting in Budapest there was a request to publish the list of CIDR blocks allocated by the RIPE NCC and the smallest allocation issued from each of them. This is it: 62/8: /19 193/8: /29 # Contain small PI assignments 194/8: /29 # Contain small PI assignments 195/8: /29 # Contain small PI assignments 212/8: /19 213/8: /19 217/8: /20 We shall put this information permanently on our website. regards, Joao Damas Head of External Services RIPE NCC

8 11

The Cidr Report
by Tony Bates 23 Jun '00

23 Jun '00

This is an auto-generated mail on Fri Jun 23 12:00:00 PDT 2000 It is not checked before it leaves my workstation. However, hopefully you will find this report interesting and will take the time to look through this to see if you can improve the amount of aggregation you perform. The report is split into sections: 0) General Status List the route table history for the last week, list any possibly bogus routes seen and give some status on ASes. 1) Gains by aggregating at the origin AS level This lists the "Top 30" players who if they decided to aggregate their announced classful prefixes at the origin AS level could make a significant difference in the reduction of the current size of the Internet routing table. This calculation does not take into account the inclusion of holes when forming an aggregate so it is possible even larger reduction should be possible. 2) Weekly Delta A summary of the last weeks changes in terms of withdrawn and added routes. Please note that this is only a snapshot but does give some indication of ASes participating in CIDR. Clearly, it is generally a good thing to see a large amont of withdrawls. 3) Interesting aggregates Interesting here means not an aggregate made as a set of classful routes. Thanks to xara.net for giving me access to their routing tables once a day. Please send any comments about this report directly to me. Check http://www.employees.org/~tbates/cidr-report.html for a daily update of this report. ------------------------------------------------------------------------------ CIDR REPORT for 23Jun00 0) General Status Table History ------------- Date Prefixes 160600 80091 170600 79759 180600 80139 190600 79957 200600 79704 210600 80023 220600 80240 230600 80236 Check http://www.employees.org/~tbates/cidr.plot.html for a plot of the table history. Possible Bogus Routes --------------------- *** Bogus 65.56.64.0/21 from AS2941 AS Summary ---------- Number of ASes in routing system: 7723 Number of ASes announcing only one prefix: 4350 (2384 cidr, 1966 classful) Largest number of cidr routes: 939 announced by AS701 Largest number of classful routes: 1047 announced by AS701 1) Gains by aggregating at the origin AS level --- 23Jun00 --- ASnum NetsNow NetsCIDR NetGain % Gain Description AS271 439 151 288 65.6% BCnet Backbone AS7046 534 360 174 32.6% COQUI-NET PRTC Internet AS1221 583 411 172 29.5% TELSTRA-AS AS9269 192 50 142 74.0% Hong Kong CTI AS9706 154 21 133 86.4% Pusan Metropolitan City Office of AS2609 127 12 115 90.6% EUnet-TN AS7657 273 170 103 37.7% The Internet Group Limited AS9304 121 22 99 81.8% Hutchcity AS7545 167 68 99 59.3% TPG Internet Pty Ltd AS174 568 476 92 16.2% Performance Systems International AS6429 208 118 90 43.3% RDC-INTERNET AS7496 127 42 85 66.9% Power Up AS4293 326 241 85 26.1% Internal ASN for C&W AS705 340 260 80 23.5% ALTERNET-AS AS577 248 176 72 29.0% Bell Backbone AS724 229 158 71 31.0% DLA-ASNBLOCK-AS AS9557 97 29 68 70.1% Pakistan Telecommunication Compan AS701 1047 981 66 6.3% Alternet AS1727 148 82 66 44.6% MRMS-WEST AS3602 305 245 60 19.7% Sprint Canada Inc. AS3749 118 59 59 50.0% TECNET AS5106 87 29 58 66.7% AADS-COLUMBUS AS6595 106 49 57 53.8% DODDSEUR AS4740 329 273 56 17.0% Ozemail Pty Ltd (ASN-OZEMAIL) AS7018 541 487 54 10.0% AT&T WorldNet Service Backbone AS7568 70 17 53 75.7% C.S. Communications Co., Ltd. AS1785 363 314 49 13.5% NYSERNet Backbone AS209 264 216 48 18.2% Qwest Communications AS1 616 572 44 7.1% GTE Internetworking AS6499 96 55 41 42.7% Brooks Fiber Properties, Inc. For the rest of the previous weeks gain information please see http://www.employees.org:80/~tbates/cidr-report.html 2) Weekly Delta Please see http://www.employees.org:80/~tbates/cidr-report.html for this part of the report 3) Interesting aggregates Please see http://www.employees.org:80/~tbates/cidr-report.html for this part of the report

1 0

RIPE NCC Region Weekly Routing Report
by Routing Analysis 22 Jun '00

22 Jun '00

This is an automated weekly mailing sent to the RIPE Routing WG e-mail list describing the state of the Internet Routing Table in Europe, Middle East and North Africa. Daily listings are sent to bgp-stats(a)lists.apnic.net For a graphical representation, please see http://www.apnic.net/stats/bgp. If you have any comments please contact Philip Smith <pfs(a)cisco.com>. Europe, Middle East, North Africa Report 23 Jun, 2000 Analysis Summary ---------------- BGP routing table entries examined: 81823 Origin ASes present in the Internet Routing Table: 7738 Origin ASes announcing only one prefix: 2537 Transit ASes present in the Internet Routing Table: 1082 Average AS path length visible in the Internet Routing Table: 5.2 Max AS path length visible: 16 Illegal AS announcements present in the Routing Table: 6 Non-routable prefixes present in the Routing Table: 0 Prefixes being announced from the IANA Reserved Address blocks: 2 Number of addresses announced to Internet: 1129807739 Equivalent to 67 /8s, 87 /16s and 127 /24s Percentage of available address space announced: 30.5 Percentage of allocated address space announced: 60.9 Percentage of available address space allocated: 50.1 RIPE Region Analysis Summary ---------------------------- Prefixes being announced by RIPE Region ASes: 12992 Prefixes being announced from the RIPE address blocks: 10199 RIPE Region origin ASes present in the Internet Routing Table: 2063 RIPE Region origin ASes announcing only one prefix: 961 RIPE Region transit ASes present in the Internet Routing Table: 403 Average RIPE Region AS path length visible: 5.8 Max RIPE Region AS path length visible: 15 Number of RIPE addresses announced to Internet: 71687629 Equivalent to 4 /8s, 69 /16s and 221 /24s Percentage of available RIPE address space announced: 61.0 RIPE AS Blocks 1877 - 1901, 2042, 2047, 2107 - 2136, 2585 - 2614 2773 - 2822, 2830 - 2879, 3154 - 3353, 5377 - 5631 6656 - 6911, 8192 - 9215, 12288 - 13311, 15360 - 16383 RIPE Address Blocks 62/8, 193/8, 194/7, 212/7 and 217/8 RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /19 equiv Description 3301 385 281 TeliaNet Sweden 1257 330 267 Swipnet AB 1849 247 468 PIPEX 1270 246 389 UUNET Germany 1275 233 1131 DFN IP Service 786 181 959 JANET IP Service 719 179 145 LANLINK 5515 174 362 Sonera Finland 517 160 202 Xlink 3320 152 244 Deutsche Telekom AG 2856 133 271 BTnet UK Regional network 2609 127 4 EUnet-TN 1267 126 947 IUnet S.p.A 3303 122 287 Swisscom 9057 106 35 Level 3 public IP n 3352 104 161 Ibernet, Internet A 3215 99 124 RAIN 1901 92 74 EUnet Austria 8895 89 28 Saudi Arabia AS Global Per AS prefix count summary ---------------------------------- ASN No of nets /19 equiv Description 701 1983 3167 UUNET Technologies, Inc. 7018 1081 3040 AT&T 1 892 4545 BBN Planet 7046 848 489 UUNET Technologies, Inc. 1221 833 977 Telstra 2914 775 1413 Verio, Inc. 1239 749 1701 Sprint ICM-Inria 3561 712 1603 Cable & Wireless USA 174 635 2835 PSINet Inc. 705 594 36 UUNET Technologies, Inc. 1785 526 832 Sprint ICM 271 471 411 BCnet Backbone 2764 454 117 connect.com.au pty ltd 3549 453 345 Frontier GlobalCenter 3602 451 78 Sprint Canada 209 447 389 Qwest 1740 435 623 CERFnet 4293 404 69 Cable & Wireless USA 4740 393 84 Ozemail List of Illegal AS's (Global) ----------------------------- Bad AS Designation Network Transit AS Description 64602 PRIVATE 63.236.57.0/24 209 Qwest 64601 PRIVATE 63.236.90.0/24 209 Qwest 64512 PRIVATE 193.39.51.0/24 5462 Cable Internet Ltd 64513 PRIVATE 200.12.17.0/24 6471 ENTEL CHILE S.A. 64605 PRIVATE 208.47.206.0/24 209 Qwest 65014 PRIVATE 208.185.113.0/24 6461 AboveNet Communicati Advertised IANA Reserved Addresses ---------------------------------- Network Origin AS Description 39.96.40.224/30 14408 iCAIR 65.56.64.0/21 2941 Community News Service Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:21 /9:4 /10:5 /11:9 /12:26 /13:50 /14:168 /15:280 /16:6527 /17:857 /18:1703 /19:5443 /20:3277 /21:3469 /22:5222 /23:7043 /24:46986 /25:130 /26:180 /27:74 /28:57 /29:69 /30:140 /31:0 /32:83 End of report

1 0

Re: [apops] Re: RIPE NCC CIDR blocks - smallest allocations
by Randy Bush 22 Jun '00

22 Jun '00

[ note reduced cc:s ] >> would other rirs be so kind as to do the same, keep them updated, and link >> the lists to eachother or something? (yes, i know some do) > http://www.apnic.net/db/RIRs.html . given three to five rirs, i can probably remember their names. the referenced page lacks prefix sizes, the subject here. randy

2 2

RIPE NCC ADDRESS POLICY CHANGES
by Joao Luis Silva Damas 21 Jun '00

21 Jun '00

*** CHANGES IN RIPE NCC ADDRESS POLICY *** During the RIPE 36 meeting in Budapest (16-19 May 2000) the LIR working group agreed that the RIPE NCC will: - lower the minimum allocation from a /19 to a /20. - this change will take effect starting August 1 Allocations of this size will initially be issued from CIDR block 217/8. Minimum allocations do not constrain requests for address space that can justify bigger blocks of addresses. ******************************************************************************** ** If you use prefix based filtering in your routers, please note this change ** ******************************************************************************** regards, Joao Damas Head of External Services RIPE NCC

1 0

Re: RIS Query
by Jacques Caron 20 Jun '00

20 Jun '00

At 00:24 08/06/00, Antony Antony wrote: >Hi Jacques, > >On Wed, 7 Jun 2000, Jacques Caron wrote: > > > 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 > >IMHO column representation is probably not very suitable for >time series. All peers may not update at the same time. There would be a new line for each update. >Also in columns you loose rest of the aspath info. You don't >really see how a transit path may get selected over other. Or >if put whole path columns will become very long. It's just a question of getting a "synthetic" view. Then one can use the regular (current) RIS output to check out exact details... > > 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.). > > > 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 > >Yes it is possible. Current database will not help you here as it >don't contain all BGP attributes. Raw data collected by RIS is >in MRT's binary format. bgpsim, which comes with MRT can replay it. >You find about bgpsim in MRT home page http://www.mrtd.net/ >We haven't used this to look at "interesting events". Thanks for the info, I'll get a look. 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

3 3