- routing-wg - mailman.ripe.net

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

bogus BGP annoucements - some thoughts for relief
by Kurt Kayser 19 Jun '00

19 Jun '00

Hi, I'm trying to get rid of the section called 'Advertised IANA Reserved Addresses' in the 'RIPE NCC Region Weekly Routing Report'. Since about some time I'm watching very interested how these networks are still 'annoucable'. I have implemented a ingress-BGP filter list that tell a syslogger to show all 'reserved-IP-space' announcements. Since the advent of the RIS, it is even better to have some kind of evidence which AS did announce when these networks. There is basically nothing wrong with making mistakes, but I'm starting to believe that some networks are being misused for spam or other annoyances. Please have a look to the last week's list: ---------------------------------- Network Origin AS Description 39.96.40.224/30 14408 iCAIR 65.56.64.0/21 2941 Community News Service 109.177.9.0/24 1785 Sprint ICM 219.91.160.0/22 7742 InternetNow, Inc. 219.91.164.0/23 7742 InternetNow, Inc. Funny enough that the RIS-database shows the following path for one of these networks: A 109.177.9.0/24 2000-06-13 13:24:25 212.20.151.253 13129 3549 6347 10664 A 109.177.9.0/24 2000-06-13 15:10:28 192.65.184.3 513 209 701 10664 A 109.177.9.0/24 2000-06-13 15:10:28 195.8.100.22 8259 5413 2828 701 10664 Always AS10664 as being the origin-AS. Wonder, why there is no such AS listed in ARIN's database as well?! There are small blocks, and I'm even missing some, which I'm seeing constantly in variations: Jun 15 19:23:57.558 MET_DST: %SEC-6-IPACCESSLOGNP: list 121 denied 0 1.1.1.0 -> 255.255.255.0, 2 packets Jun 15 19:28:57.740 MET_DST: %SEC-6-IPACCESSLOGNP: list 121 denied 0 1.1.1.0 -> 255.255.255.0, 2 packets If we want to try get some of this stuff out of the backbone and even decrease some (unnecessary) BGP-traffic, why not publish a 'ingress BGP-filterlist' that is endorsed by the RIPE-wg, RIPE or the community at large? What it basically does is: 1. Reject illegal prefixes (127/8, 0/0, RFC1918, etc.) 2. Log orginiators (if wanted) 3. Decrease SPAM-complaints 4. Prevent abuse It's low on CPU (it's no IP filter-list!), just a BGP-ingress filter. I have even added some prefix-length filter, but this is another topic, and depends on your upstream's policy. (I just can't stand /32s in the table!). Kurt -- noris network GmbH | Deutschherrnstr. 15-19 | 90429 Nuernberg Tel. (0911) 27738-0 | Fax. (0911) 27738-100 | kurt(a)noris.net %IDS-4-IP_IMPOSSIBLE_SIG: Sig:1102:Impossible IP Packet

3 2

The Cidr Report
by Tony Bates 16 Jun '00

16 Jun '00

This is an auto-generated mail on Fri Jun 16 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 16Jun00 0) General Status Table History ------------- Date Prefixes 090600 78901 100600 79105 110600 79003 120600 79282 130600 79244 140600 79247 150600 79514 160600 80091 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: 7668 Number of ASes announcing only one prefix: 4319 (2370 cidr, 1949 classful) Largest number of cidr routes: 935 announced by AS701 Largest number of classful routes: 1018 announced by AS701 1) Gains by aggregating at the origin AS level --- 16Jun00 --- ASnum NetsNow NetsCIDR NetGain % Gain Description AS271 439 151 288 65.6% BCnet Backbone AS1221 580 409 171 29.5% TELSTRA-AS AS7046 504 344 160 31.7% COQUI-NET PRTC Internet AS9269 193 46 147 76.2% Hong Kong CTI AS9706 154 21 133 86.4% Pusan Metropolitan City Office of AS2609 127 8 119 93.7% EUnet-TN AS7657 269 166 103 38.3% The Internet Group Limited AS7545 167 68 99 59.3% TPG Internet Pty Ltd AS6429 208 116 92 44.2% RDC-INTERNET AS9304 117 26 91 77.8% Hutchcity AS7496 125 40 85 68.0% Power Up AS577 286 206 80 28.0% Bell Backbone AS4293 316 238 78 24.7% Internal ASN for C&W AS705 339 262 77 22.7% ALTERNET-AS AS174 522 446 76 14.6% Performance Systems International AS1727 165 92 73 44.2% MRMS-WEST AS9557 84 19 65 77.4% Pakistan Telecommunication Compan AS724 208 146 62 29.8% DLA-ASNBLOCK-AS AS3602 306 246 60 19.6% Sprint Canada Inc. AS3749 118 59 59 50.0% TECNET AS5106 85 27 58 68.2% AADS-COLUMBUS AS6595 104 47 57 54.8% DODDSEUR AS4740 333 277 56 16.8% Ozemail Pty Ltd (ASN-OZEMAIL) AS209 395 339 56 14.2% Qwest Communications AS7568 67 14 53 79.1% C.S. Communications Co., Ltd. AS7018 532 479 53 10.0% AT&T WorldNet Service Backbone AS376 120 68 52 43.3% RISQ AS1591 173 122 51 29.5% HQASC MEDNET-ASN AS1785 364 315 49 13.5% NYSERNet Backbone AS701 1018 970 48 4.7% Alternet 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 15 Jun '00

15 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 16 Jun, 2000 Analysis Summary ---------------- BGP routing table entries examined: 81279 Origin ASes present in the Internet Routing Table: 7681 Origin ASes announcing only one prefix: 2526 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: 15 Illegal AS announcements present in the Routing Table: 3 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: 1142028298 Equivalent to 68 /8s, 17 /16s and 248 /24s Percentage of available address space announced: 30.8 Percentage of allocated address space announced: 62.1 Percentage of available address space allocated: 49.6 RIPE Region Analysis Summary ---------------------------- Prefixes being announced by RIPE Region ASes: 12824 Prefixes being announced from the RIPE address blocks: 10025 RIPE Region origin ASes present in the Internet Routing Table: 2054 RIPE Region origin ASes announcing only one prefix: 962 RIPE Region transit ASes present in the Internet Routing Table: 399 Average RIPE Region AS path length visible: 5.8 Max RIPE Region AS path length visible: 15 Number of RIPE addresses announced to Internet: 71461006 Equivalent to 4 /8s, 66 /16s and 104 /24s Percentage of available RIPE address space announced: 71.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 and 212/7 RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /19 equiv Description 3301 383 281 TeliaNet Sweden 1257 330 267 Swipnet AB 1270 248 388 UUNET Germany 1849 247 492 PIPEX 1275 232 1131 DFN IP Service 786 181 959 JANET IP Service 719 179 145 LANLINK 5515 170 362 Sonera Finland 517 164 204 Xlink 3320 151 245 Deutsche Telekom AG 1267 126 947 IUnet S.p.A 2609 126 4 EUnet-TN 2856 125 271 BTnet UK Regional network 3303 122 287 Swisscom 9057 101 34 Level 3 public IP n 3215 99 124 RAIN 1901 90 74 EUnet Austria 8895 90 28 Saudi Arabia AS 1290 83 195 PSINet UK Ltd. Global Per AS prefix count summary ---------------------------------- ASN No of nets /19 equiv Description 701 1974 3149 UUNET Technologies, Inc. 7018 1064 3007 AT&T 1 888 4553 BBN Planet 7046 833 497 UUNET Technologies, Inc. 1221 823 976 Telstra 2914 783 1413 Verio, Inc. 1239 758 1626 Sprint ICM-Inria 3561 716 1625 Cable & Wireless USA 174 638 2851 PSINet Inc. 209 617 652 Qwest 705 572 35 UUNET Technologies, Inc. 1785 530 832 Sprint ICM 271 471 411 BCnet Backbone 2764 460 121 connect.com.au pty ltd 3602 455 78 Sprint Canada 3549 452 345 Frontier GlobalCenter 1740 440 635 CERFnet 4293 396 69 Cable & Wireless USA 4740 394 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 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:22 /9:4 /10:5 /11:9 /12:26 /13:49 /14:163 /15:276 /16:6514 /17:849 /18:1675 /19:5399 /20:3260 /21:3444 /22:5173 /23:6995 /24:46727 /25:123 /26:159 /27:81 /28:53 /29:67 /30:124 /31:0 /32:82 End of report

1 0

The Cidr Report
by Tony Bates 09 Jun '00

09 Jun '00

This is an auto-generated mail on Fri Jun 9 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 09Jun00 0) General Status Table History ------------- Date Prefixes 110400 75403 120400 75730 130400 75919 010500 76182 020500 76265 070600 78743 080600 78857 090600 78901 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 *** Bogus 109.177.9.0/24 from AS1785 AS Summary ---------- Number of ASes in routing system: 7613 Number of ASes announcing only one prefix: 4265 (2328 cidr, 1937 classful) Largest number of cidr routes: 907 announced by AS701 Largest number of classful routes: 1020 announced by AS701 1) Gains by aggregating at the origin AS level --- 09Jun00 --- ASnum NetsNow NetsCIDR NetGain % Gain Description AS271 438 150 288 65.8% BCnet Backbone AS9269 203 28 175 86.2% Hong Kong CTI AS1221 578 405 173 29.9% TELSTRA-AS AS7046 511 347 164 32.1% COQUI-NET PRTC Internet AS9706 152 28 124 81.6% Pusan Metropolitan City Office of AS2609 127 8 119 93.7% EUnet-TN AS7545 167 68 99 59.3% TPG Internet Pty Ltd AS6429 209 117 92 44.0% RDC-INTERNET AS174 568 477 91 16.0% Performance Systems International AS9304 115 28 87 75.7% Hutchcity AS7496 127 40 87 68.5% Power Up AS7657 250 165 85 34.0% The Internet Group Limited AS705 339 262 77 22.7% ALTERNET-AS AS4293 312 237 75 24.0% Internal ASN for C&W AS577 250 178 72 28.8% Bell Backbone AS724 216 148 68 31.5% DLA-ASNBLOCK-AS AS9557 84 19 65 77.4% Pakistan Telecommunication Compan AS1727 140 79 61 43.6% MRMS-WEST AS3602 303 243 60 19.8% Sprint Canada Inc. AS3749 118 59 59 50.0% TECNET AS6595 104 47 57 54.8% DODDSEUR AS209 431 374 57 13.2% Qwest Communications AS4740 329 274 55 16.7% Ozemail Pty Ltd (ASN-OZEMAIL) AS7018 530 477 53 10.0% AT&T WorldNet Service Backbone AS7568 66 14 52 78.8% C.S. Communications Co., Ltd. AS701 1020 968 52 5.1% Alternet AS6528 48 6 42 87.5% WORLD-LYNX AS6499 97 56 41 42.3% Brooks Fiber Properties, Inc. AS6629 67 27 40 59.7% NOAA-AS AS4755 128 88 40 31.2% Videsh Sanchar Nigam Ltd. India 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 08 Jun '00

08 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 09 Jun, 2000 Analysis Summary ---------------- BGP routing table entries examined: 80868 Origin ASes present in the Internet Routing Table: 7643 Origin ASes announcing only one prefix: 2501 Transit ASes present in the Internet Routing Table: 1072 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: 4 Non-routable prefixes present in the Routing Table: 0 Prefixes being announced from the IANA Reserved Address blocks: 3 Number of addresses announced to Internet: 1157136383 Equivalent to 68 /8s, 248 /16s and 127 /24s Percentage of available address space announced: 31.2 Percentage of allocated address space announced: 62.9 Percentage of available address space allocated: 49.6 RIPE Region Analysis Summary ---------------------------- Prefixes being announced by RIPE Region ASes: 12767 Prefixes being announced from the RIPE address blocks: 9955 RIPE Region origin ASes present in the Internet Routing Table: 2049 RIPE Region origin ASes announcing only one prefix: 962 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: 71247087 Equivalent to 4 /8s, 63 /16s and 36 /24s Percentage of available RIPE address space announced: 70.8 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 and 212/7 RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /19 equiv Description 3301 376 280 TeliaNet Sweden 1257 330 267 Swipnet AB 1270 253 413 UUNET Germany 1849 246 492 PIPEX 1275 235 1132 DFN IP Service 786 181 959 JANET IP Service 719 179 145 LANLINK 5515 171 362 Sonera Finland 517 163 203 Xlink 3320 150 245 Deutsche Telekom AG 1267 126 947 IUnet S.p.A 2609 125 4 EUnet-TN 2856 124 271 BTnet UK Regional network 3303 121 295 Swisscom 3215 98 124 RAIN 9057 98 34 Level 3 public IP n 1901 89 74 EUnet Austria 8895 89 28 Saudi Arabia AS 1290 83 195 PSINet UK Ltd. Global Per AS prefix count summary ---------------------------------- ASN No of nets /19 equiv Description 701 1961 3250 UUNET Technologies, Inc. 7018 1055 3015 AT&T 1 870 4552 BBN Planet 7046 845 473 UUNET Technologies, Inc. 1221 825 985 Telstra 2914 764 1372 Verio, Inc. 1239 744 1627 Sprint ICM-Inria 3561 726 1629 Cable & Wireless USA 209 659 705 Qwest 174 635 2849 PSINet Inc. 705 539 34 UUNET Technologies, Inc. 271 471 411 BCnet Backbone 2764 460 121 connect.com.au pty ltd 3549 453 344 Frontier GlobalCenter 1740 443 636 CERFnet 3602 432 78 Sprint Canada 4293 395 69 Cable & Wireless USA 4740 388 84 Ozemail 816 379 179 UUNET Canada4 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 65500 PRIVATE 200.186.247.0/24 11415 IMPSAT Comunicacoes 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 109.177.9.0/24 1785 Sprint ICM Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:23 /9:4 /10:5 /11:9 /12:26 /13:49 /14:163 /15:276 /16:6497 /17:850 /18:1671 /19:5373 /20:3221 /21:3430 /22:5159 /23:6958 /24:46374 /25:128 /26:182 /27:89 /28:69 /29:80 /30:141 /31:0 /32:91 End of report

1 0

Re: RIS Query
by Jacques Caron 08 Jun '00

08 Jun '00

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

2 1

RIS
by Jacques Caron 06 Jun '00

06 Jun '00

Hi again, I guess another view might be interesting: have one column per peer (with the ability to select a subset of peers, of course), a line per update, and then in each "cell" the AS path received from that peer (if any). This enables to see which path is adopted by several peers for a multihomed network. Another option would be to be able to give an AS to "grep" into the AS paths, and show which cells contain it or not (or the same thing with several ASes and colored cells). Not sure this is very clear, so I'll give an example. Let's say network N is multihomed to two transit providers AS1 and AS2. Now, I want to see which path is taken from multiple locations to this network. I would input network N, peers A, B, C, D, the two ASes AS1 and AS2 and start/end times. Then it woud output a table with columns A, B C and D, a line per update, and on each line, a different color depending on whether the route received from that peer contains AS1 or AS2 (or both, or none, maybe). Optionally, an additional column giving the proportion of peers using AS1 or AS2 could be interesting. Sounds like a good idea? 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

2 1

Top 100 Maintainers List 20000605
by RIPE Database Administration 05 Jun '00

05 Jun '00

1 0