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

Re[4]: RIPE NCC Region Weekly Routing Report
by Adam Obszynski 13 Dec '00

13 Dec '00

>> RIPE can only sugest to people to behave like good citizens, explaining >> the reasons for it from the community perspective and also tell them >> why their mileage may vary anyways. There is no way RIPE or the RIPE >> NCC can pressure ISPs to change their behavior. > "Bad" behaviour could result in the assignment window being lowered, future > allocations being delayed, RIPE NCC could suggest to relevant upstreams that > the downstream be filtered (or see figure 1)... Yes but if we only filter bad aggregation w/o mass backbone operator agreement or smthing like new ripe working group agregatin-wg(a)ripe.net ? the efect will be a very small or small with compare to ip address asigments if ripe will policy agregation like ip assigment and db actuality i could bring us well agregated eurpoean AS route.. PS: try undertand it 8-) -- Regards, Adam Obszyï¿½ski ATM Inc. +48-22-5156418

2 1

Re: RIPE NCC Region Weekly Routing Report
by Mike Portworsnick 12 Dec '00

12 Dec '00

But not at Genuity (AS1) and UUnet (AS701) it's more work but you know exactly what you do announce to them Mike At 14:48 11.12.2000 -0600, you wrote: >On Mon, Dec 11, 2000 at 09:37:13PM +0100, Mike Portworsnick wrote: > > We should ask their upstream provider why they are accepting this prefix! > > > > Soltani, Abi (AS2563) and Sprintlink (AS1239) > > >sh ip bgp reg 2563$ > >way too many prefixes, and a lot of them can be aggregated. ;) > >I've noticed this behavior with sprint/as1239, qwest/as209, and few other >major carriers, as soon as their customer is gone 20+ prefixes they just stop >maintain ACLs/prefix-lists for them... :| > >-- >Basil Kruglov [BK252-ARIN] >Network Engineering and Security >CIFNet, Inc. ******************************************************************** Mike Portworsnick Senior Internetwork Expert - CCIE# 4985 Energis (Switzerland) AG Carrier Services Industriestrasse 21 CH-8304 Wallisellen Switzerland Phone: +41 1 839 33 54 Fax: +41 1 877 44 90 Email: mike.portworsnick(a)energis-ecs.com

2 2

AW: RIPE NCC Region Weekly Routing Report
by Alexander Ottl 11 Dec '00

11 Dec '00

But that inetnum object looks like it is just a typo. It should have been 212.3.97.0/24, which incidentally is also in the DB with the same owner. The one /24 out of 219/8 that is announced is 219.219.219.0 as listed in the Weekly Routing Report: Advertised IANA Reserved Addresses ---------------------------------- Network Origin AS Description 50.0.0.0/8 9487 Handong University 91.16.23.0/24 11770 Net56 105.200.136.0/30 9768 Korea Telecom 219.219.219.0/24 2563 Seoul National University Regards, Alex -----Ursprï¿½ngliche Nachricht----- Von: Sascha E. Pollok [mailto:sp@iphh.net] Gesendet: Montag, 11. Dezember 2000 09:31 An: Ana Susanj; routing-wg(a)ripe.net Betreff: Re: RIPE NCC Region Weekly Routing Report >There's one /24 in 219/8 space? Although, it doesn't seem to be >announced. > >According to the list of RIRs on the APNIC's website, 219/8 is >IANA-Reserved. Looks like someone definitely put a wrong object in the db: inetnum: 219.3.97.0 - 219.3.97.255 netname: FE-NET descr: Future Electronics Ltd descr: Zaporizhzya, Ukraine country: UA admin-c: AE1363-RIPE admin-c: SB187-RIPE tech-c: IF388-RIPE rev-srv: ns.fe-club.net rev-srv: ns2.trifle.net status: ASSIGNED PA notify: hostmaster(a)trifle.net changed: hostmaster(a)trifle.net 19990913 source: RIPE Well, he is indeed not announcing that one and there is no route-object either so why don't you ripe-ncc people not just go ahead and remove it? ;-) Regards, Sascha --- Sascha E. Pollok Internet Port Hamburg Technical Manager / Network Operations Grosse Reichenstrasse 27 D-20457 Hamburg Germany Tel.ï¿½ï¿½ +49 (0)40 37 49 19-0 Faxï¿½ï¿½ï¿½ +49 (0)40 37 49 19-29 Email: sp(a)iphh.net ICQ #38955239

1 0

The Cidr Report
by Tony Bates 08 Dec '00

08 Dec '00

This is an auto-generated mail on Fri Dec 8 12:00:00 PST 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 08Dec00 0) General Status Table History ------------- Date Prefixes 011200 93154 021200 93136 031200 93184 041200 95348 051200 95118 061200 95808 071200 95387 081200 95404 Check http://www.employees.org/~tbates/cidr.plot.html for a plot of the table history. Possible Bogus Routes --------------------- *** Bogus 91.16.23.0/24 from AS11770 *** Bogus 219.219.219.0 from AS2563 AS Summary ---------- Number of ASes in routing system: 9339 Number of ASes announcing only one prefix: 5413 (3047 cidr, 2366 classful) Largest number of cidr routes: 1001 announced by AS701 Largest number of classful routes: 1708 announced by AS1221 1) Gains by aggregating at the origin AS level --- 08Dec00 --- ASnum NetsNow NetsCIDR NetGain % Gain Description AS1221 1708 1240 468 27.4% TELSTRA-AS AS2563 348 114 234 67.2% KoRean Education Network AS271 289 133 156 54.0% BCnet Backbone AS701 1534 1390 144 9.4% Alternet AS9269 167 48 119 71.3% Hong Kong CTI AS7545 166 50 116 69.9% TPG Internet Pty Ltd AS2609 115 11 104 90.4% EUnet-TN AS6595 164 63 101 61.6% DODDSEUR AS8013 453 353 100 22.1% PSINET-CA AS7657 285 194 91 31.9% The Internet Group Limited AS13999 94 6 88 93.6% UNKNOWN AS705 331 247 84 25.4% ALTERNET-AS AS4293 344 262 82 23.8% Internal ASN for C&W AS174 526 445 81 15.4% Performance Systems International AS4755 194 114 80 41.2% Videsh Sanchar Nigam Ltd. India AS7496 102 25 77 75.5% Power Up AS7046 326 250 76 23.3% UUNET-CUSTOMER AS4151 285 209 76 26.7% USDA Internet Access Network AS3908 238 166 72 30.3% Supernet, Inc. AS1942 136 64 72 52.9% FR-CICG-GRENOBLE AS577 243 172 71 29.2% Bell Backbone AS724 224 158 66 29.5% DLA-ASNBLOCK-AS AS7018 594 528 66 11.1% AT&T WorldNet Service Backbone AS226 169 104 65 38.5% USC/Information Sciences Institut AS5106 101 37 64 63.4% AADS-COLUMBUS AS1727 153 91 62 40.5% MRMS-WEST AS3749 116 56 60 51.7% TECNET AS3602 306 248 58 19.0% Sprint Canada Inc. AS2548 369 311 58 15.7% DIGEX-AS AS16758 63 6 57 90.5% 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

Announcement: RIPE Whois Database version 3.0 beta is out
by RIPE Database Administration 08 Dec '00

08 Dec '00

Dear All, [ Apologies for duplicate messages ] This mail is to inform you that version 3.0 beta of the RIPE Whois Database is out. Read on! You will be affected too. The RIPE Database is about to change its data format, from RIPE181 to RPSL (the Routing Policy Specification Language, see RFC2622). This will affect all object types, including "person", "domain" and "inetnum". The version 2 of the RIPE Database, the one currently in production on whois.ripe.net, will in the next months be replaced by version 3. All the entries in the RIPE Database will be translated into RPSL format, and that is the format you will get when you will be querying the Database. Don't be mistaken: for the moment, whois.ripe.net continues running with version 2 and answering to your queries in the old-fashioned way. But this will not last forever; in a few months, all will become RPSL. So if you use the Whois database, we encourage all of you to prepare for this change as soon as possible. We strongly suggest you to start to get used to RPSL and version 3.0 . In this aim, you can do the following: - Query rpsl.ripe.net at port 43. You will find there exactly the same objects that are in whois.ripe.net, mirrored live and in RPSL format. - If you have any script that runs by querying whois.ripe.net, test it by pointing it to rpsl.ripe.net and make it v3.0-compliant. - Try our CGI interface to the RPSL server: you can find it at http://www.ripe.net/ripencc/pub-services/db/reimp/. - Get to know the new update path: use our "sandbox" database for RPSL updates. Send your updates to <auto-rip(a)ripe.net> and query the corresponding database at rpsl.ripe.net, port 4343 . Remember that in a few months, that's the way the RIPE Database will be running; so the earlier you start working with it, the less likely you are to be unpleasantly surprised later. We are currently preparing additional resources to help ease the transition; we will announce them as soon as they are available, which will happen later this month. Please note that the software is still in a "beta" phase. So we need your feedback! If you happen to find something that looks like a bug when you are testing the RPSL database, don't hesitate... Send us a bug report at <dbrip(a)ripe.net> ! If you want to actively participate to the migration effort, you could join the "RIP migration Task force" and let yourself be heard. Just write to <ripe-dbm(a)ripe.net> and ask to join the Task Force. For the ones interested in viewing or trying the code, you can download it at: ftp://ftp.ripe.net/ripe/dbase/reimp/whois-rip-3.0beta1.tar.gz You can also join a discussion list related to version 3.0 beta of the RIPE Database Software. To subscribe to this list, send a message to <majordomo(a)ripe.net> with the line: subscribe db-beta in the body of your letter. It is a moderated mailing list so some delays in subscription are possible. Regards, The RIPE Database Group.

1 0

The Cidr Report
by Tony Bates 01 Dec '00

01 Dec '00

This is an auto-generated mail on Fri Dec 1 12:00:00 PST 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 01Dec00 0) General Status Table History ------------- Date Prefixes 241100 92527 251100 92668 261100 92623 271100 92643 281100 92681 291100 92893 301100 93098 011200 93154 Check http://www.employees.org/~tbates/cidr.plot.html for a plot of the table history. Possible Bogus Routes --------------------- *** Bogus 91.16.23.0/24 from AS11770 *** Bogus 219.219.219.0 from AS2563 AS Summary ---------- 1) Gains by aggregating at the origin AS level --- 01Dec00 --- ASnum NetsNow NetsCIDR NetGain % Gain Description 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