- routing-wg - mailman.ripe.net

RIPE NCC Region Weekly Routing Report
by Routing Analysis 21 Dec '00

21 Dec '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 22 Dec, 2000 Analysis Summary ---------------- BGP routing table entries examined: 99729 Origin ASes present in the Internet Routing Table: 9472 Origin ASes announcing only one prefix: 3343 Transit ASes present in the Internet Routing Table: 1272 Average AS path length visible in the Internet Routing Table: 5.3 Max AS path length visible: 18 Illegal AS announcements present in the Routing Table: 13 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: 1223153153 Equivalent to 72 /8s, 231 /16s and 214 /24s Percentage of available address space announced: 33.0 Percentage of allocated address space announced: 64.7 Percentage of available address space allocated: 51.0 RIPE Region Analysis Summary ---------------------------- Prefixes being announced by RIPE Region ASes: 15051 Prefixes being announced from the RIPE address blocks: 11804 RIPE Region origin ASes present in the Internet Routing Table: 2593 RIPE Region origin ASes announcing only one prefix: 1289 RIPE Region transit ASes present in the Internet Routing Table: 480 Average RIPE Region AS path length visible: 5.9 Max RIPE Region AS path length visible: 18 Number of RIPE addresses announced to Internet: 103719954 Equivalent to 6 /8s, 46 /16s and 164 /24s Percentage of available RIPE address space announced: 88.3 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 390 307 TeliaNet Sweden 1257 322 256 Swipnet AB 702 319 435 UUNET Technologies, Inc. 1270 311 422 UUNET Germany 3215 211 181 RAIN 1849 203 308 PIPEX 719 191 154 LANLINK 5515 185 334 Sonera Finland 786 181 959 JANET IP Service 3320 166 462 Deutsche Telekom AG 680 148 789 Deutschef Forschurgsnetz 517 140 139 Xlink 1942 140 53 INRIA-Rocquencourt 2856 132 384 BTnet UK Regional network 3303 125 277 Swisscom 1901 103 77 EUnet Austria 1267 97 987 IUnet S.p.A 5400 94 30 Concert Internet Plus Europea 1939 93 35 INRIA-Rocquencourt 2830 87 29 UUNET UK (formerly PIPEX) Global Per AS prefix count summary ---------------------------------- ASN No of nets /19 equiv Description 701 2582 3472 UUNET Technologies, Inc. 1221 2359 1191 Telstra 705 1414 63 UUNET Technologies, Inc. 1 1019 4573 BBN Planet 7018 889 3041 AT&T 7046 699 514 UUNET Technologies, Inc. 1239 692 1612 Sprint ICM-Inria 8013 682 69 PSINet Ltd. Canada 2914 646 1287 Verio, Inc. 2548 635 556 Digital Express Group, Inc. 174 611 2735 PSINet Inc. 209 589 568 Qwest 3561 582 1363 Cable & Wireless USA 6082 540 66 Management Analysis, Incorpor 3549 499 432 Frontier GlobalCenter 3908 451 281 Supernet, Inc. 271 438 311 BCnet Backbone 4293 437 56 Cable & Wireless USA 2764 433 128 connect.com.au pty ltd 3602 433 79 Sprint Canada List of Unregistered ASNs (Global) ---------------------------------- Bad AS Designation Network Transit AS Description 65501 PRIVATE 64.21.103.0/24 16890 Network Services, In 2027 UNALLOCATED 150.185.0.0/16 10530 Interpacket Group, I 2027 UNALLOCATED 150.185.128.0/18 8143 Publicom Corp. 2027 UNALLOCATED 150.186.0.0/16 10530 Interpacket Group, I 2027 UNALLOCATED 150.187.0.0/16 10530 Interpacket Group, I 2027 UNALLOCATED 150.188.0.0/16 10530 Interpacket Group, I 2027 UNALLOCATED 150.189.0.0/16 10530 Interpacket Group, I 1877 UNALLOCATED 192.108.196.0/24 1880 Stupi, house man's 1877 UNALLOCATED 192.108.209.0/24 1880 Stupi, house man's 1877 UNALLOCATED 192.108.210.0/24 1880 Stupi, house man's 1877 UNALLOCATED 192.108.214.0/24 1880 Stupi, house man's 5757 UNALLOCATED 192.239.13.0/24 701 UUNET Technologies, 5757 UNALLOCATED 207.19.224.0/24 701 UUNET Technologies, Advertised IANA Reserved Addresses ---------------------------------- Network Origin AS Description 91.16.23.0/24 11770 Net56 219.219.219.0/24 2563 Seoul National University 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:32 /13:59 /14:190 /15:298 /16:6749 /17:1010 /18:1969 /19:6208 /20:4293 /21:4177 /22:6407 /23:8413 /24:58309 /25:283 /26:457 /27:157 /28:115 /29:111 /30:274 /31:0 /32:177 Number of /24s announced per /8 block (Global) ---------------------------------------------- 9:2 12:297 15:1 24:625 26:1 32:7 38:10 44:2 53:2 55:1 57:9 61:60 62:108 63:2454 64:1068 65:12 66:46 91:1 128:20 129:173 130:18 131:31 132:9 133:3 134:84 135:7 136:114 137:113 138:182 139:66 140:103 141:18 142:64 143:35 144:93 145:14 146:129 147:94 148:118 149:112 150:23 151:256 152:1036 153:87 154:231 155:58 156:14 157:101 158:51 159:47 160:18 161:53 162:63 163:118 164:109 165:94 166:174 167:75 168:67 169:29 170:184 171:2 192:5354 193:1813 194:1986 195:847 196:366 198:3733 199:3392 200:1712 202:2510 203:5212 204:3593 205:2502 206:2802 207:2834 208:2780 209:3337 210:532 211:136 212:707 213:268 214:7 215:11 216:2598 217:80 219:1 End of report

1 0

RIPE Whois RPSL Migration
by RIPE NCC 21 Dec '00

21 Dec '00

[ Apologies for duplicate mails ] RIPE Whois RPSL Migration The RIPE Database re-implementation project is nearing completion. A key feature of the new database is the implementation of RPSL, to replace the old RIPE-181 standard. RPSL is similar, but not identical, to RIPE-181. The RIPE NCC expects that many programs that use the RIPE Whois database will continue to operate properly without modification. However, some programs may have problems parsing the RPSL format, or be confused by differences in behaviour. We would like to ensure that the transition to RPSL is as easy as possible. Therefore, we are working with the RIPE community to provide resources you can use to check any programs or scripts that you have that use the RIPE Whois database. Please visit our Migration page for further information: http://www.ripe.net/ripencc/pub-services/db/rpsl/index.html This page will be updated regularly with the latest information. We will provide additional tools and information as they become available. The actual timeline of when the RPSL server will replace the existing RIPE-181 server will be decided at the RIPE-38 meeting. If you want input on when the change will occur, then you should either attend this meeting or post your comments on the RIPE DB mailing list. http://www.ripe.net/ripe/meetings/current/ripe-38/index.html http://www.ripe.net/ripe/wg/db/index.html Regards, The RIPE Database Group. RIPE NCC

1 0

question regarding AS-request
by Hauke Krull 19 Dec '00

19 Dec '00

Hello! I'm not sure if this is the right address for my question but the RIPE-Hostmaster directed me to this list. I've got a question regarding the request of an AS. Let me first explain the situation: We're a local ISP in northern germany and we've got an AS (5605) and an IP allocation (195.244.224.0/19). We've got several POPs, but not all of them are operated by ourself. Now one of these POPs which is connected to our network with just one leased line has leased another line to another backbone provider for fallback. The problem is the following: He's using IPs from our allocation (195.244.225.0/24) and we inject the whole /19 with a 'network'-command into BGP. So, when the connection to this POP is down the fallback line is useless because there is no route to announce in the local POP. In my opinion there are three possibilities: 1) this POP gets his own AS and announces only the /24. and we announce the /19. This brings us an overlapping route-object in the RIPE-DB. (By the way is it possible that we get a second AS instead of this POP getting one, because we will do all the configuration...?) 2) this POP gets his own AS and a new network which is outside our allocation With this configuration we don't split our /19. 3) this POP stays in our AS and works with 'advertise-map ... non-exist-map'-commands for the /19. But therefor I have to create an overlapping route-object in the RIPE-DB for the /24 for the same AS. The good thing with this configuration is: during normal operation there is only the /19 in the world-wide routing table. But I'm not sure if all providers will accept this overlapping /24? And I'm not sure if my core-network would accept this /24-announcment from the same AS. Which is the most preferrable solution for the RIPE? Or are there any more solutions? Or is one of these solutions not possible? Thanks a lot Hauke Krull -- Dipl.-Phys. Hauke Krull NetUSE AG Siemenswall, D-24107 Kiel, Germany Fon: +49 431 386435 00 -- Fax: +49 431 386435 99

1 0

The Cidr Report
by Tony Bates 15 Dec '00

15 Dec '00

This is an auto-generated mail on Fri Dec 15 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 15Dec00 0) General Status Table History ------------- Date Prefixes 081200 95404 091200 95823 101200 95806 111200 95907 121200 95679 131200 95592 141200 95583 151200 95822 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: 9359 Number of ASes announcing only one prefix: 5425 (3034 cidr, 2391 classful) Largest number of cidr routes: 1190 announced by AS705 Largest number of classful routes: 1678 announced by AS1221 1) Gains by aggregating at the origin AS level --- 15Dec00 --- ASnum NetsNow NetsCIDR NetGain % Gain Description AS1221 1678 1238 440 26.2% TELSTRA-AS AS2563 264 82 182 68.9% KoRean Education Network AS701 1593 1434 159 10.0% Alternet AS271 284 131 153 53.9% BCnet Backbone AS9269 167 48 119 71.3% Hong Kong CTI AS7545 166 50 116 69.9% TPG Internet Pty Ltd AS8013 455 349 106 23.3% PSINET-CA AS6595 162 63 99 61.1% DODDSEUR AS7657 277 188 89 32.1% The Internet Group Limited AS13999 94 6 88 93.6% UNKNOWN AS705 326 242 84 25.8% ALTERNET-AS AS4755 189 105 84 44.4% Videsh Sanchar Nigam Ltd. India AS174 530 449 81 15.3% Performance Systems International AS4293 340 260 80 23.5% Internal ASN for C&W AS7496 100 23 77 77.0% Power Up AS7046 328 251 77 23.5% UUNET-CUSTOMER AS4151 282 208 74 26.2% USDA Internet Access Network AS724 243 170 73 30.0% DLA-ASNBLOCK-AS AS1727 172 99 73 42.4% MRMS-WEST AS3908 236 164 72 30.5% Supernet, Inc. AS1942 137 65 72 52.6% FR-CICG-GRENOBLE AS577 242 171 71 29.3% Bell Backbone AS7018 594 528 66 11.1% AT&T WorldNet Service Backbone AS5106 101 37 64 63.4% AADS-COLUMBUS AS3749 123 59 64 52.0% TECNET AS226 167 104 63 37.7% USC/Information Sciences Institut AS3602 307 249 58 18.9% Sprint Canada Inc. AS2548 366 308 58 15.8% DIGEX-AS AS16758 63 6 57 90.5% UNKNOWN AS376 133 77 56 42.1% RISQ 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 14 Dec '00

14 Dec '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 15 Dec, 2000 Analysis Summary ---------------- BGP routing table entries examined: 98466 Origin ASes present in the Internet Routing Table: 9381 Origin ASes announcing only one prefix: 3309 Transit ASes present in the Internet Routing Table: 1270 Average AS path length visible in the Internet Routing Table: 5.2 Max AS path length visible: 18 Illegal AS announcements present in the Routing Table: 13 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: 1219364782 Equivalent to 72 /8s, 174 /16s and 7 /24s Percentage of available address space announced: 32.9 Percentage of allocated address space announced: 64.5 Percentage of available address space allocated: 51.0 RIPE Region Analysis Summary ---------------------------- Prefixes being announced by RIPE Region ASes: 14938 Prefixes being announced from the RIPE address blocks: 11765 RIPE Region origin ASes present in the Internet Routing Table: 2567 RIPE Region origin ASes announcing only one prefix: 1274 RIPE Region transit ASes present in the Internet Routing Table: 475 Average RIPE Region AS path length visible: 5.9 Max RIPE Region AS path length visible: 18 Number of RIPE addresses announced to Internet: 86040796 Equivalent to 5 /8s, 32 /16s and 224 /24s Percentage of available RIPE address space announced: 73.3 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 394 307 TeliaNet Sweden 1257 337 258 Swipnet AB 702 315 427 UUNET Technologies, Inc. 1270 289 413 UUNET Germany 3215 209 181 RAIN 1849 204 316 PIPEX 719 191 154 LANLINK 5515 186 334 Sonera Finland 786 181 959 JANET IP Service 3320 161 458 Deutsche Telekom AG 1942 140 53 INRIA-Rocquencourt 517 137 138 Xlink 680 137 645 Deutschef Forschurgsnetz 2856 132 384 BTnet UK Regional network 3303 125 277 Swisscom 1901 104 77 EUnet Austria 1267 97 987 IUnet S.p.A 1275 97 501 DFN IP Service 1939 93 35 INRIA-Rocquencourt 5400 93 30 Concert Internet Plus Europea Global Per AS prefix count summary ---------------------------------- ASN No of nets /19 equiv Description 701 2587 3455 UUNET Technologies, Inc. 1221 2389 1193 Telstra 705 1488 65 UUNET Technologies, Inc. 1 1021 4565 BBN Planet 7018 891 3039 AT&T 1239 710 1590 Sprint ICM-Inria 7046 676 513 UUNET Technologies, Inc. 2914 637 1287 Verio, Inc. 2548 630 556 Digital Express Group, Inc. 174 604 2734 PSINet Inc. 3561 579 1380 Cable & Wireless USA 209 577 583 Qwest 6082 537 66 Management Analysis, Incorpor 3549 494 433 Frontier GlobalCenter 3908 453 281 Supernet, Inc. 271 439 311 BCnet Backbone 4293 439 56 Cable & Wireless USA 3602 435 80 Sprint Canada 2764 429 127 connect.com.au pty ltd 2563 412 60 Seoul National University List of Unregistered ASNs (Global) ---------------------------------- Bad AS Designation Network Transit AS Description 65501 PRIVATE 64.21.103.0/24 16890 Network Services, In 2027 UNALLOCATED 150.185.0.0/16 10530 Interpacket Group, I 2027 UNALLOCATED 150.185.128.0/18 8143 Publicom Corp. 2027 UNALLOCATED 150.186.0.0/16 10530 Interpacket Group, I 2027 UNALLOCATED 150.187.0.0/16 10530 Interpacket Group, I 2027 UNALLOCATED 150.188.0.0/16 10530 Interpacket Group, I 2027 UNALLOCATED 150.189.0.0/16 10530 Interpacket Group, I 1877 UNALLOCATED 192.108.196.0/24 1880 Stupi, house man's 1877 UNALLOCATED 192.108.209.0/24 1880 Stupi, house man's 1877 UNALLOCATED 192.108.210.0/24 1880 Stupi, house man's 1877 UNALLOCATED 192.108.214.0/24 1880 Stupi, house man's 5757 UNALLOCATED 192.239.13.0/24 701 UUNET Technologies, 5757 UNALLOCATED 207.19.224.0/24 701 UUNET Technologies, Advertised IANA Reserved Addresses ---------------------------------- Network Origin AS Description 91.16.23.0/24 11770 Net56 219.219.219.0/24 2563 Seoul National University 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:32 /13:57 /14:188 /15:296 /16:6738 /17:998 /18:1966 /19:6176 /20:4254 /21:4167 /22:6314 /23:8335 /24:57482 /25:285 /26:449 /27:155 /28:112 /29:117 /30:146 /31:0 /32:158 Number of /24s announced per /8 block (Global) ---------------------------------------------- 9:2 12:297 15:1 24:620 26:1 32:7 38:9 44:3 53:2 55:1 57:9 61:53 62:109 63:2478 64:1046 65:8 66:45 91:1 128:20 129:160 130:17 131:31 132:7 133:3 134:81 135:7 136:52 137:77 138:176 139:45 140:106 141:17 142:65 143:36 144:93 145:13 146:120 147:59 148:115 149:111 150:23 151:247 152:979 153:36 154:51 155:62 156:13 157:99 158:48 159:46 160:18 161:53 162:63 163:119 164:97 165:93 166:174 167:76 168:64 169:29 170:180 171:2 192:5336 193:1809 194:1997 195:851 196:363 198:3667 199:3399 200:1708 202:2527 203:5236 204:3520 205:2426 206:2739 207:2702 208:2804 209:3219 210:669 211:185 212:722 213:269 214:6 215:11 216:2572 217:69 219:1 End of report

1 0

Re: DANGER! Was: RIPE NCC Region Weekly Routing Report
by Tony Barber 14 Dec '00

14 Dec '00

> >Well disk space is even cheaper but people still care about SPAM. But I >might be wrong too. > > > All this will become a real issue once the number of prefixes being > > announced becomes a problem for BGP convergence, or storage space on the > > routers runs out... > >Well, what strikes me is that aggregation keeps popping up at NANOG, RIPE, >IETF etc and everyone (more or less) agrees we needs to fix this. Still... > >I agree we need a bigger carrot (and there is no bigger carrot than >money) to achieve this. The question is just how and what? But it's >not the registries' job. Maybe we could define Tier-0 ISP:s as upstreams >with a aggregation conscious? > >I doubt that more mailinglists and reports will help. And more meetings >with concensus will not add much. Having things automated (a script >mailing the corresponding AS) might be one idea, but I agree that more >mails will not do it alone. > >- :-) Kurtis is right. The engineering of the Internet has traditionally operated on a 'just in time' basis (i.e only when its really needed). With the environment being totally commercial now there is even more incentive to operate in this manner. Only if and when any related outages start to cause 'major' concerns will the operators sit up and take notice. That is not at the moment and no amount of subtle teaching will (in the long term) take effect. Daniel and ripe have noted this before where figures get better soon after a major drive; but unless this is continual (and who pays??) the results wear off and the trends continue. With my company hat on, it is a nightmare to control all of the acquired networks totally aligning them. Yes it is being worked on but is very time consuming. With all efforts targetted at revenue collection and growth where are the resources to do the right thing? There are no east answers, if there was they would have been implemented by now. Apologies that this mail doesn't add much value other than to cast doom. Tony Barber

1 0

RIPE NCC Region Weekly Routing Report
by Routing Analysis 14 Dec '00

14 Dec '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 08 Dec, 2000 Analysis Summary ---------------- BGP routing table entries examined: 98964 Origin ASes present in the Internet Routing Table: 9338 Origin ASes announcing only one prefix: 3296 Transit ASes present in the Internet Routing Table: 1253 Average AS path length visible in the Internet Routing Table: 5.3 Max AS path length visible: 18 Illegal AS announcements present in the Routing Table: 15 Non-routable prefixes present in the Routing Table: 0 Prefixes being announced from the IANA Reserved Address blocks: 4 Number of addresses announced to Internet: 1219031583 Equivalent to 72 /8s, 168 /16s and 242 /24s Percentage of available address space announced: 32.9 Percentage of allocated address space announced: 64.5 Percentage of available address space allocated: 51.0 RIPE Region Analysis Summary ---------------------------- Prefixes being announced by RIPE Region ASes: 14906 Prefixes being announced from the RIPE address blocks: 11770 RIPE Region origin ASes present in the Internet Routing Table: 2544 RIPE Region origin ASes announcing only one prefix: 1257 RIPE Region transit ASes present in the Internet Routing Table: 468 Average RIPE Region AS path length visible: 5.9 Max RIPE Region AS path length visible: 18 Number of RIPE addresses announced to Internet: 102428390 Equivalent to 6 /8s, 26 /16s and 238 /24s Percentage of available RIPE address space announced: 87.2 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 395 307 TeliaNet Sweden 1257 336 258 Swipnet AB 702 305 426 UUNET Technologies, Inc. 1270 273 410 UUNET Germany 1849 208 316 PIPEX 719 190 154 LANLINK 3215 187 181 RAIN 5515 185 334 Sonera Finland 786 181 959 JANET IP Service 3320 159 457 Deutsche Telekom AG 1942 139 53 INRIA-Rocquencourt 517 138 146 Xlink 2856 132 384 BTnet UK Regional network 680 131 612 Deutschef Forschurgsnetz 3303 125 277 Swisscom 2609 120 8 EUnet-TN 1275 106 535 DFN IP Service 1901 104 77 EUnet Austria 1267 97 987 IUnet S.p.A 1939 93 35 INRIA-Rocquencourt Global Per AS prefix count summary ---------------------------------- ASN No of nets /19 equiv Description 701 2525 3469 UUNET Technologies, Inc. 1221 2162 1191 Telstra 9768 1433 75 Korea Telecom 705 1199 55 UUNET Technologies, Inc. 1 1009 4555 BBN Planet 7018 896 3025 AT&T 1239 728 1629 Sprint ICM-Inria 7046 681 514 UUNET Technologies, Inc. 2914 662 1275 Verio, Inc. 2548 636 564 Digital Express Group, Inc. 174 603 2773 PSINet Inc. 209 564 566 Qwest 3561 561 1368 Cable & Wireless USA 6082 538 66 Management Analysis, Incorpor 3549 503 418 Frontier GlobalCenter 2563 477 64 Seoul National University 3908 457 289 Supernet, Inc. 271 442 312 BCnet Backbone 3602 437 80 Sprint Canada 4293 430 54 Cable & Wireless USA List of Unregistered ASNs (Global) ---------------------------------- Bad AS Designation Network Transit AS Description 65501 PRIVATE 64.21.103.0/24 16890 Network Services, In 64800 PRIVATE 64.78.130.128/25 5705 Sirius Solutions, In 2027 UNALLOCATED 150.185.0.0/16 10530 Interpacket Group, I 2027 UNALLOCATED 150.185.128.0/18 8143 Publicom Corp. 2027 UNALLOCATED 150.186.0.0/16 10530 Interpacket Group, I 2027 UNALLOCATED 150.187.0.0/16 10530 Interpacket Group, I 2027 UNALLOCATED 150.188.0.0/16 10530 Interpacket Group, I 2027 UNALLOCATED 150.189.0.0/16 10530 Interpacket Group, I 1877 UNALLOCATED 192.108.196.0/24 1880 Stupi, house man's 1877 UNALLOCATED 192.108.209.0/24 1880 Stupi, house man's 1877 UNALLOCATED 192.108.210.0/24 1880 Stupi, house man's 1877 UNALLOCATED 192.108.214.0/24 1880 Stupi, house man's 5757 UNALLOCATED 192.239.13.0/24 701 UUNET Technologies, 64512 PRIVATE 202.61.84.0/24 4743 IPhil Communications 5757 UNALLOCATED 207.19.224.0/24 701 UUNET Technologies, 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 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:32 /13:57 /14:188 /15:293 /16:6749 /17:991 /18:1965 /19:6157 /20:4221 /21:4153 /22:6266 /23:8278 /24:57118 /25:563 /26:953 /27:379 /28:152 /29:149 /30:156 /31:0 /32:103 Number of /24s announced per /8 block (Global) ---------------------------------------------- 9:2 12:301 15:1 24:607 26:1 32:7 38:7 44:2 53:2 55:1 57:9 61:59 62:97 63:2158 64:999 65:7 66:44 91:1 128:19 129:163 130:16 131:30 132:9 133:3 134:76 135:1 136:51 137:78 138:174 139:45 140:107 141:17 142:46 143:36 144:89 145:12 146:126 147:58 148:110 149:109 150:23 151:250 152:989 153:32 154:47 155:60 156:13 157:94 158:49 159:46 160:18 161:53 162:63 163:123 164:94 165:94 166:166 167:74 168:56 169:29 170:178 171:2 192:5326 193:1897 194:2008 195:856 196:361 198:3664 199:3413 200:1705 202:2516 203:5312 204:3507 205:2392 206:2730 207:2684 208:2759 209:3269 210:677 211:188 212:704 213:256 214:6 215:11 216:2582 217:61 219:1 End of report

13 16

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