- routing-wg - mailman.ripe.net

The Cidr Report
by Tony Bates 21 Jul '00

21 Jul '00

This is an auto-generated mail on Fri Jul 21 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 21Jul00 0) General Status Table History ------------- Date Prefixes 140700 82006 150700 82099 160700 81998 170700 81940 180700 82120 190700 82574 200700 82381 210700 82529 Check http://www.employees.org/~tbates/cidr.plot.html for a plot of the table history. Possible Bogus Routes --------------------- AS Summary ---------- Number of ASes in routing system: 7959 Number of ASes announcing only one prefix: 4467 (2482 cidr, 1985 classful) Largest number of cidr routes: 964 announced by AS701 Largest number of classful routes: 1068 announced by AS701 1) Gains by aggregating at the origin AS level --- 21Jul00 --- ASnum NetsNow NetsCIDR NetGain % Gain Description AS271 436 149 287 65.8% BCnet Backbone AS7046 638 397 241 37.8% COQUI-NET PRTC Internet AS1221 560 401 159 28.4% TELSTRA-AS AS9706 154 21 133 86.4% Pusan Metropolitan City Office of AS2609 128 8 120 93.8% EUnet-TN AS7657 295 187 108 36.6% The Internet Group Limited AS9304 123 17 106 86.2% Hutchcity AS7545 155 57 98 63.2% TPG Internet Pty Ltd AS6429 213 115 98 46.0% RDC-INTERNET AS9269 154 63 91 59.1% Hong Kong CTI AS7496 126 38 88 69.8% Power Up AS4293 334 247 87 26.0% Internal ASN for C&W AS174 553 467 86 15.6% Performance Systems International AS577 256 171 85 33.2% Bell Backbone AS705 327 250 77 23.5% ALTERNET-AS AS724 218 150 68 31.2% DLA-ASNBLOCK-AS AS1727 161 94 67 41.6% MRMS-WEST AS3908 256 190 66 25.8% Supernet, Inc. AS701 1068 1007 61 5.7% Alternet AS6595 112 51 61 54.5% DODDSEUR AS5106 95 35 60 63.2% AADS-COLUMBUS AS3749 121 62 59 48.8% TECNET AS7568 81 24 57 70.4% C.S. Communications Co., Ltd. AS7018 551 494 57 10.3% AT&T WorldNet Service Backbone AS3602 300 244 56 18.7% Sprint Canada Inc. AS4755 154 101 53 34.4% Videsh Sanchar Nigam Ltd. India AS4740 323 271 52 16.1% Ozemail Pty Ltd (ASN-OZEMAIL) AS7993 78 28 50 64.1% Global One Communications AS1785 359 311 48 13.4% NYSERNet Backbone AS11252 86 38 48 55.8% Idaho State University 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 20 Jul '00

20 Jul '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 21 Jul, 2000 Analysis Summary ---------------- BGP routing table entries examined: 84418 Origin ASes present in the Internet Routing Table: 7932 Origin ASes announcing only one prefix: 2661 Transit ASes present in the Internet Routing Table: 1107 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: 11 Non-routable prefixes present in the Routing Table: 0 Prefixes being announced from the IANA Reserved Address blocks: 0 Number of addresses announced to Internet: 1137349026 Equivalent to 67 /8s, 202 /16s and 145 /24s Percentage of available address space announced: 30.7 Percentage of allocated address space announced: 62.4 Percentage of available address space allocated: 49.2 RIPE Region Analysis Summary ---------------------------- Prefixes being announced by RIPE Region ASes: 13145 Prefixes being announced from the RIPE address blocks: 10373 RIPE Region origin ASes present in the Internet Routing Table: 2095 RIPE Region origin ASes announcing only one prefix: 988 RIPE Region transit ASes present in the Internet Routing Table: 415 Average RIPE Region AS path length visible: 5.9 Max RIPE Region AS path length visible: 15 Number of RIPE addresses announced to Internet: 73010888 Equivalent to 4 /8s, 90 /16s and 14 /24s Percentage of available RIPE address space announced: 62.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 386 281 TeliaNet Sweden 1257 334 271 Swipnet AB 1270 251 333 UUNET Germany 1849 244 463 PIPEX 786 181 959 JANET IP Service 702 180 225 UUNET Technologies, Inc. 1273 179 89 Cable & Wireless ECRC GmbH 1275 179 954 DFN IP Service 719 177 145 LANLINK 517 160 193 Xlink 5515 159 345 Sonera Finland 3320 145 250 Deutsche Telekom AG 13019 134 20 RR-BRETAGNE Autonomous System 2609 126 4 EUnet-TN 2856 126 271 BTnet UK Regional network 3303 120 286 Swisscom 9057 118 43 Level 3 public IP n 3215 106 126 RAIN 1901 100 75 EUnet Austria Global Per AS prefix count summary ---------------------------------- ASN No of nets /19 equiv Description 701 2075 3202 UUNET Technologies, Inc. 1 1128 4564 BBN Planet 7046 959 487 UUNET Technologies, Inc. 1221 820 984 Telstra 2914 775 1426 Verio, Inc. 7018 746 3045 AT&T 7473 718 3476 SINGTEL-IX 705 689 39 UUNET Technologies, Inc. 3561 689 1609 Cable & Wireless USA 1239 673 1620 Sprint ICM-Inria 174 634 2847 PSINet Inc. 1785 525 826 Sprint ICM 3549 468 369 Frontier GlobalCenter 271 464 412 BCnet Backbone 2764 458 117 connect.com.au pty ltd 209 449 388 Qwest 3602 437 76 Sprint Canada 1740 434 615 CERFnet 3908 429 346 Supernet, Inc. List of Illegal AS's (Global) ----------------------------- Bad AS Designation Network Transit AS Description 65534 PRIVATE 63.87.74.0/24 7046 UUNET Technologies, 64601 PRIVATE 63.236.90.0/24 209 Qwest 65132 PRIVATE 153.9.0.0/16 7473 SINGTEL-IX 65132 PRIVATE 155.225.0.0/16 7473 SINGTEL-IX 65132 PRIVATE 168.216.0.0/16 7473 SINGTEL-IX 65132 PRIVATE 169.150.0.0/16 7473 SINGTEL-IX 65132 PRIVATE 192.160.121.0/24 7473 SINGTEL-IX 65132 PRIVATE 193.5.123.0/24 7473 SINGTEL-IX 65132 PRIVATE 198.204.92.0/24 7473 SINGTEL-IX 65132 PRIVATE 199.164.178.0/24 7473 SINGTEL-IX 64605 PRIVATE 208.47.206.0/24 209 Qwest 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:49 /14:169 /15:284 /16:6566 /17:873 /18:1762 /19:5656 /20:3407 /21:3591 /22:5370 /23:7267 /24:48710 /25:120 /26:165 /27:77 /28:52 /29:57 /30:88 /31:0 /32:90 End of report

1 0

draft minutes of the Routing WG session RIPE 36
by SchmitzJo＠aol.com 19 Jul '00

19 Jul '00

Dear colleagues, please find below the draft minutes of the Routing WG session at RIPE 36 in Budapest. My thanks go to Marek Bukowy of the NCC for taking the minutes. As usual, comments, additions, corrections very much welcome. Thanks Joachim --- JS395-RIPE -- standard disclaimer --- R I P E 3 6 B U D A P E S T Routing Working Group Session 17-May-2000 Draft Minutes chair: Joachim Schmitz (JS395-RIPE) scribe: Marek Bukowy, RIPE NCC 70 participants A. Preliminaries Due to some cancellations, less time was needed than originally anticipated, and the first slot was not used, freeing up space for other Working Groups (LIR overflow ;-) and reducing overlap with parallel sessions. The shortened agenda then looked like: A. Preliminaries B. Update to RIPE-178 (Christian Panigl) C. Tnsition to RPSL (Andrei Robachevski, Joao Luis Silva Damas) D. RIS, Status and Plans (Antony Antony, Henk Uijterwaal) Y. General I/O with Other WGs Z. AOB Joachim welcomed the participants, passed around the participants' list, and asked for a volunteer scribe. Marek Bukowy volunteered to take the minutes. There were no objections to the minutes of the RIPE 35 Routing WG circulated just prior to the meeting. Joachim apologized for the very late distribution and announced a period of one week after the meeting to allow for possible amendments or changes to the minutes. In that time there was one addition, but otherwise, the minutes were accepted. Then the status of 3 old action points was reviewed: o 31.R1 RIPE NCC, D.Kessens, J.Schmitz Basic design for an IPv6 IRR -postponed- This action is sitting around for quite some time without much progress. To give this a chance to continue, we considere to define a project out of this and make it part of the NCC activity plan o 32.R1 RIPE NCC, JLS.Damas Prepare draft document on RIPE-181 -> RPSL transition issues -in progress- The draft document is still being worked on, but not yet publicly available, even though done for the most part. A presentation during this WG session will provide an update o 34.R1 C.Panigl Provide updates to RIPE-178 -to be closed- This is ready to be published as a RIPE document. Details will be presented by Christian Panigl during this WG session Before starting with the individual reports, Joachim gave a short overview of the full day Multicast Routing Tutorial which had been held on the previous day. There were 30 participants, who were not only following the presentations, but encouraged by the great way of presentation, also discussed quite a lot of issues around multicast routing. The thanks go to Stefano Previdi of Cisco, who took the work on him to present and discuss this topic at the RIPE meeting. For those interested in reading back on the slides, look at ftp://ftpeng.cisco.com/ipmulticast. B. Update to RIPE-178 (Christian Panigl) The document was updated and will be assigned a new number. Changes can be summarised as follows: - access-list has been changed to prefix-list (supported in IOS for quite some time now) - list of root nameserver networks has been updated - recommendations have been added to combine no bgp fast-external-fallover with per-neighbor keep-alive for networks that need faster convergence than available through default bgp timeout - there also was a hint about BGP route refresh capability a.k.a. triggered soft which is part of a set of enhancements (IOS 12.0.7 T&S) * Discussion A question was asked why "golden networks" which are recommended to be excluded from route flap damping, are still needed, and why DNS fallover to secondary nameservers was considered insufficient renundancy. The answer is, that at least in Europe, many ISPs still have only one upstream link. In such a case, if this network's border router operates with flap damping enabled, route flapping caused by instability up the stream prevents the network from accessing the whole Internet, including all root server networks. C. Transition to RPSL (Andrei Robachevsky, RIPE NCC) The presentation is available from: http://www.ripe.net/ripe/meetings/archive/ripe-36/index.html The history of the project was presented starting 1998, going together with a complete reimplementation of the database software. Motivation included performance enhancement, new functionality and maintainability. A decision was taken to do a full rewrite after modifying the old code to support the referral mechanism and referential integrity. The Alpha version has been online since 31 Dec 1999. Next beta version including almost all queries, NRTM server (Near-real-time mirroring, using the old protocol but serving RPSL objects) is online since 12 May 2000. It is kept up to date with the primary whois database by means of NRTM. The development is still focused on adding functionality. Portability issues are not yet addressed; currently the development environment is Solaris 6 and 7 on Sparc/intel and Mysql as the backend. Next steps are documentation, testing and porting. General differences between RPSL and ripe-181 were briefly discussed. Some RPSL modifications will affect all objects, not only routing-related. Those changes include: - line continuation - preservation of the line order and - invalidity of empty attributes In the data migration process, a remarks line "This object is automatically converted from the RIPE181 registry" will be added to all routing registry objects transferred from the current RIPE database. Some features of RPSL with regard to the routing registry specific objects were presented (route, autnum, as-set). Regarding the related implementation of rps-auth, several issues were discussed on how to use member-of and member-by-ref in as-sets and autnum objects, together with which update paths are included, and the "bilateral" nature of the member specification. Members-by-ref of the as-set specifies the mntners which are allowed to claim membership of an autnum object by listing the as-set name in the member-of attribute of the aut-num object. The old style specification using "members" is still valid, but no searches on this attribute are possible, rendering it nearly equivalent to a "remarks" line. A comment was made that the irrd has such searches for RADB and this should also be the case in RIPE. This discussion in conjunction with other items discussed later on led to an action on the NCC (see below) The same membership specification applies to route-set (present as community in ripe-181). Both sides must specify/allow membership, otherwise it is not effective. An update of an aut-num object with member-of attribute will be rejected if the as-set does not allow this membership. Two attributes of the mntner object enable control over mntner objects that are outdated and forgotten: referral-by - pointing to the maintainer that created the mntner, and auth-override - allowing deletion of the slack mntner by the mntner listed in the referral-by attribute. New query switches were also presented, which were implemented to enable all queries needed by RAtoolset: general: -q version - displays version of the server -q sources - displays available sources as well as expansions of the collection of switches devoted to address space related objects: -l one level less specific lookup -l / -L / -m / -M also available for in-addr domains now -x exact match only (default is exact or less specific) A request for active beta testing was expressed towards the community. Query functionality of the new software can be tested with an instance of the database holding real data, available at reimp.ripe.net port 43 (where peering sets and route sets could not yet be queried at the time the presentation was given). Updates in RPSL can be sent to a new test database at auto-rip(a)ripe.net. This database can be queried at reimp.ripe.net port 4343. The PGP authentication is not functional as of yet, though. Phase II of the transition will start end of June 2000 (current schedule), Phase III depends on testing and consensus on the final transition. * Discussion A question was asked from the audience if the database software was going to support the domain objects which are not defined by RPSL, and so could be used by ccTLDs. The answer to this was positive. Another question was asked if the irrd-style query commands (!commands) for expansion were going to be provided. This started a short discussion: while the syntax is not (yet) supported, the functionality of these commands was already provided. A quick show of hands showed that about 4 people from the audience used this irrd functionality. Consequently, it was felt to be a low priority issue for the moment. A suggestion was made to intensify cooperation with Merit on testing the new software using the test suites that Merit used during the transition to RPSL. An interoperability issue was raised. It was felt that it is essential to ensure compatibility on the user-object level with irrd and whois, so that the RIPE database could be used as an NRTM client of irrd or a server for irrd in order to be able to accomodate all databases in a single whois server. It was suggested to do that with filters if no other way was possible. Nonetheless the highest possible level of interoperability shall be maintained. o 36.R1 on the RIPE NCC During the transition phase to the RPSL software - verify with RADB on their test suites for testing RPSL implementations - coordinate with RADB on consistent mirroring of databases (NRTM) - coordinate with RADB on consistent whois interface of databases including irrd Part of this work is covered by the rps-dist effort, but the Routing WG explicitely asks RIPE NCC and Merit (RADB) to work closely together here to guarantee interoperability, because rps-dist is not yet mature. D. RIS, Status and Plans (Antony Antony, RIPE NCC) presentation available at http://www.ripe.net/ripencc/pub-services/np/Talks/0005_RIPE36/ Major topics of the presentation were * introduction * progress since RIPE35 * explanation current setup * observations made * plans which are comprised below * introduction Goal of RIS: to store the history of inter-as routing information and make this history queryable for the good of the community. It will also be a foundation for the reality check project of the routing registry and trend analysis. The queries will allow viewing of a routing table at a specific point in time as well as viewing of the changes observed during specified periods of time. This is achieved by collecting BGP data available to the project participants at different points of the internet and storing at the RIPE NCC. New developments in the project since RIPE35 were presented: - increase of the number of peers to 13 - web interface available at http://abcoude.ripe.net/ris/risalpha.cgi * Discussion A suggestion was made that a command line interface would be useful for scripts. It was explained that lots of information needs to be transferred to the program as arguments, infeasible to do by hand, but technically not a problem, because this is actually what is more or less behind the web interface. It was suggested that a perl library could be useful. This issue will be considered in more detail by the NCC. A question on software availablility was asked. It was explained, that the software consists of 3 components: - BGP listener (MRT/Zebra) - available in public domain - tool to insert the data into the database - written by NCC - query engine - written by NCC The components developed by NCC are not publicly available at the moment, but this may change. Following these questions, some remaining open questions were presented: - investigation on hardware/software needed (scalability problems) - decision on how long keep in the database (current plan for 3 months) - how often should the dumps occur (now 3/day) - how this should be turned into a regular service It is estimated that for most of these questions answers will be found from the experience during the current alpha phase, and later beta. * observations made 'dark prefixes' still exist (difference between the union of all prefixes available at all peers and the set of prefixes available to particular peers, indicating fragments of the internet unavailable to the peers) 25.4 % of the IPv4 address space is currently announced and can be seen by at least one RIS peer. 25.36% can be seen at NCC (equivalent of 19 /16s missing w.r.t the union seen by RIS.) 25.32% can be seen at CERN (53 /16s missing) (overlaps have been eliminated) No trend can be observed so far, the instabilities are more of the random nature and are sometimes high, like a /8 unavailable at the NCC for a whole day. The decrease on the graph of the number of prefixes can be explained by about 8000 /30s observed before RIPE35 that were internal routes of one of the RIS peers and have been withdrawn. * Discussion: These preliminary results triggered the question if there was a distinction between announcements from the peers, meaning routes this peer tells to any Internet peers, or the backbone routes, or those for their customers. So far no consistency was enforced in requesting the peering policy from RIS peers. Hence some differences in the set of prefixes covered can appear. Without the consistency, the results are not really comparable. It is obvious that such a policy should be developed. This is considered to be part of RIS, but also input from the community is required here. Since the policies themselves were not going to be public and practically no traffic was being sent from the RIS peers, it was pointed out that the NCC should have no problems requesting RIS peers to peer with the RRC boxes following specific policy guidelines. NCC will come up with a suggested policy. User feedback on usefulness and suggestions for functionality was requested. An example on the propagation of the announcement of the meetings' prefix on the Internet was presented by Daniel Karrenberg, giving an impression of what can already be done today with the alpha version of RIS. It was stressed that the tool provides an integrated view eliminating the need to consult multiple looking-glasses. * project plans were subsequently summarised: - 2 more RRC's (Remote Route Collectors) in Europe - solve scalability problems of the BGP listener - answer open questions on usability - examine observed effects closely Y. General I/O with Other WGs Besides progress report on the database reimplementation and corresponding issues, which will be presented at the Database WG session, no other I/O happened with other WGs. Z. Any Other Business No other issues turned up and thus no other business was discussed. Summary of open Action Points ----------------------------- 31.R1 on RIPE NCC, D.Kessens, J.Schmitz Basic design for an IPv6 IRR - postponed - 32.R1 on RIPE NCC, JLS.Damas Prepare draft document on issues of RIPE-181 to RPSL transition - in progress - 34.R1 on C.Panigl Provide update to RIPE-178 - closed - 36.R1 on RIPE NCC During the transition phase to the RPSL software - verify with RADB on their test suites for testing RPSL implementations - coordinate with RADB on consistent mirroring of databases (NRTM) - coordinate with RADB on consistent whois interface of databases including irrd Marek Bukowy, Joachim Schmitz, July 2000 -----

3 2

***Announcement: Merit to convert to 'PGPKEY' authentication (RFC 2726)
by gerald＠merit.edu 18 Jul '00

18 Jul '00

On 7/30/00 between 5 AM - 8 AM EDT Merit will convert from 'PGP-FROM' to 'PGPKEY' authentication as described in RFC 2726. All maintainer object 'PGP-FROM' instances will be converted to a 'PGPKEY' instance and a 'key-cert' object will be created for each unique 'PGPKEY' instance. After the conversion all public keys used for signing DB submissions will be visible in the registry as 'key-cert' objects. Registering public keys allows users to verify a maintainer's identity and to submit, update and maintain their own public keys like any other DB object. Normal PGP signing of DB submissions will continue to work exactly as before the conversion. The conversion should be seamless to our DB user community and no action is required. Merit will send email to all users who will be affected by the conversion. The notice will give users a chance to remove their PGP references if (for whatever reason) they do not wish to take part in the new PGP authentication scheme. The new 'PGPKEY' scheme makes it easier for users to integrate PGP signing into their DB update process. It is our wish that into the future all registry users will PGP sign their DB submissions. Please see www.radb.net/docs/keyfaq.html for additional information on the conversion process and tutorial information regarding the use of 'PGPKEY' authentication. Please consult RFC 2726 for the authoritative specification. IRRd team --Gerald Winters

1 0

The Cidr Report
by Tony Bates 14 Jul '00

14 Jul '00

This is an auto-generated mail on Fri Jul 14 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 14Jul00 0) General Status Table History ------------- Date Prefixes 070700 81549 080700 81249 090700 81150 100700 81258 110700 81337 120700 81502 130700 81740 140700 82006 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: 7900 Number of ASes announcing only one prefix: 4446 (2454 cidr, 1992 classful) Largest number of cidr routes: 960 announced by AS701 Largest number of classful routes: 1078 announced by AS701 1) Gains by aggregating at the origin AS level --- 14Jul00 --- ASnum NetsNow NetsCIDR NetGain % Gain Description AS271 435 152 283 65.1% BCnet Backbone AS7046 610 400 210 34.4% COQUI-NET PRTC Internet AS1221 555 397 158 28.5% TELSTRA-AS AS9706 153 26 127 83.0% Pusan Metropolitan City Office of AS2609 128 8 120 93.8% EUnet-TN AS7657 298 190 108 36.2% The Internet Group Limited AS9304 123 17 106 86.2% Hutchcity AS7545 155 57 98 63.2% TPG Internet Pty Ltd AS6429 211 115 96 45.5% RDC-INTERNET AS705 350 259 91 26.0% ALTERNET-AS AS7496 127 39 88 69.3% Power Up AS174 558 470 88 15.8% Performance Systems International AS9269 153 66 87 56.9% Hong Kong CTI AS577 268 181 87 32.5% Bell Backbone AS4293 330 243 87 26.4% Internal ASN for C&W AS724 227 156 71 31.3% DLA-ASNBLOCK-AS AS701 1078 1009 69 6.4% Alternet AS1727 159 92 67 42.1% MRMS-WEST AS3908 261 195 66 25.3% Supernet, Inc. AS5106 93 34 59 63.4% AADS-COLUMBUS AS3749 119 60 59 49.6% TECNET AS6595 108 50 58 53.7% DODDSEUR AS4755 151 93 58 38.4% Videsh Sanchar Nigam Ltd. India AS7568 81 24 57 70.4% C.S. Communications Co., Ltd. AS4740 348 291 57 16.4% Ozemail Pty Ltd (ASN-OZEMAIL) AS3602 299 243 56 18.7% Sprint Canada Inc. AS7018 549 494 55 10.0% AT&T WorldNet Service Backbone AS2764 479 425 54 11.3% connect.com.au pty ltd AS1785 360 311 49 13.6% NYSERNet Backbone AS209 266 218 48 18.0% Qwest Communications 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 13 Jul '00

13 Jul '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 14 Jul, 2000 Analysis Summary ---------------- BGP routing table entries examined: 83443 Origin ASes present in the Internet Routing Table: 7920 Origin ASes announcing only one prefix: 2634 Transit ASes present in the Internet Routing Table: 1100 Average AS path length visible in the Internet Routing Table: 5.3 Max AS path length visible: 15 Illegal AS announcements present in the Routing Table: 8 Non-routable prefixes present in the Routing Table: 3 Prefixes being announced from the IANA Reserved Address blocks: 2 Number of addresses announced to Internet: 1185353947 Equivalent to 70 /8s, 167 /16s and 16 /24s Percentage of available address space announced: 32.0 Percentage of allocated address space announced: 63.9 Percentage of available address space allocated: 50.1 RIPE Region Analysis Summary ---------------------------- Prefixes being announced by RIPE Region ASes: 13233 Prefixes being announced from the RIPE address blocks: 10332 RIPE Region origin ASes present in the Internet Routing Table: 2108 RIPE Region origin ASes announcing only one prefix: 993 RIPE Region transit ASes present in the Internet Routing Table: 412 Average RIPE Region AS path length visible: 5.9 Max RIPE Region AS path length visible: 15 Number of RIPE addresses announced to Internet: 89520744 Equivalent to 5 /8s, 85 /16s and 250 /24s Percentage of available RIPE address space announced: 76.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 386 281 TeliaNet Sweden 1257 336 271 Swipnet AB 1270 268 398 UUNET Germany 1849 241 464 PIPEX 3320 236 250 Deutsche Telekom AG 1275 218 1075 DFN IP Service 786 181 959 JANET IP Service 719 178 145 LANLINK 5515 173 362 Sonera Finland 702 165 201 UUNET Technologies, Inc. 517 160 193 Xlink 2609 126 4 EUnet-TN 2856 126 271 BTnet UK Regional network 3303 118 285 Swisscom 9057 113 41 Level 3 public IP n 3215 104 125 RAIN 1901 100 75 EUnet Austria 8895 93 29 Saudi Arabia AS 1267 92 955 IUnet S.p.A Global Per AS prefix count summary ---------------------------------- ASN No of nets /19 equiv Description 701 2059 3164 UUNET Technologies, Inc. 1 894 4553 BBN Planet 7046 859 486 UUNET Technologies, Inc. 1221 847 986 Telstra 2914 774 1427 Verio, Inc. 7018 737 3021 AT&T 1239 696 1654 Sprint ICM-Inria 705 690 39 UUNET Technologies, Inc. 3561 673 1615 Cable & Wireless USA 174 635 2845 PSINet Inc. 1785 524 826 Sprint ICM 271 471 411 BCnet Backbone 2764 467 117 connect.com.au pty ltd 3549 455 353 Frontier GlobalCenter 209 447 388 Qwest 3602 443 77 Sprint Canada 1740 439 623 CERFnet 3908 433 346 Supernet, Inc. 2548 408 542 Digital Express Group, Inc. List of Illegal AS's (Global) ----------------------------- Bad AS Designation Network Transit AS Description 65209 PRIVATE 63.233.140.0/22 209 Qwest 65209 PRIVATE 63.233.154.0/24 209 Qwest 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 65000 PRIVATE 198.154.77.0/24 1959 Defense Information 64605 PRIVATE 208.47.206.0/24 209 Qwest 65019 PRIVATE 208.185.254.128/27 6461 AboveNet Communicati Prefixes from private and non-routed address space (Global) ----------------------------------------------------------- Prefix Origin AS Description 192.168.15.4/30 2518 C&C Internet Service Mesh 192.168.15.8/30 2518 C&C Internet Service Mesh 192.168.15.208/28 2518 C&C Internet Service Mesh 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:287 /16:6559 /17:863 /18:1743 /19:5598 /20:3364 /21:3541 /22:5314 /23:7138 /24:47826 /25:142 /26:177 /27:98 /28:78 /29:82 /30:218 /31:0 /32:131 End of report

1 0

The Cidr Report
by Tony Bates 07 Jul '00

07 Jul '00

This is an auto-generated mail on Fri Jul 7 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 07Jul00 0) General Status Table History ------------- Date Prefixes 300600 80928 010700 80965 020700 80894 030700 80985 040700 81051 050700 81066 060700 81438 070700 81549 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: 7835 Number of ASes announcing only one prefix: 4407 (2427 cidr, 1980 classful) Largest number of cidr routes: 975 announced by AS701 Largest number of classful routes: 1061 announced by AS701 1) Gains by aggregating at the origin AS level --- 07Jul00 --- ASnum NetsNow NetsCIDR NetGain % Gain Description AS271 436 149 287 65.8% BCnet Backbone AS1221 626 446 180 28.8% TELSTRA-AS AS7046 535 365 170 31.8% COQUI-NET PRTC Internet AS9269 187 45 142 75.9% Hong Kong CTI AS9706 153 21 132 86.3% Pusan Metropolitan City Office of AS705 569 448 121 21.3% ALTERNET-AS AS7657 295 190 105 35.6% The Internet Group Limited AS2609 125 20 105 84.0% EUnet-TN AS9304 122 18 104 85.2% Hutchcity AS7545 154 56 98 63.6% TPG Internet Pty Ltd AS6429 211 116 95 45.0% RDC-INTERNET AS577 267 180 87 32.6% Bell Backbone AS174 556 469 87 15.6% Performance Systems International AS7496 128 43 85 66.4% Power Up AS4293 325 241 84 25.8% Internal ASN for C&W AS724 228 157 71 31.1% DLA-ASNBLOCK-AS AS3908 273 204 69 25.3% Supernet, Inc. AS1727 159 90 69 43.4% MRMS-WEST AS701 1061 996 65 6.1% Alternet AS6595 110 50 60 54.5% DODDSEUR AS5106 89 31 58 65.2% AADS-COLUMBUS AS3749 116 58 58 50.0% TECNET AS7568 81 24 57 70.4% C.S. Communications Co., Ltd. AS3602 301 244 57 18.9% Sprint Canada Inc. AS4740 328 273 55 16.8% Ozemail Pty Ltd (ASN-OZEMAIL) AS7018 541 488 53 9.8% AT&T WorldNet Service Backbone AS1785 360 311 49 13.6% NYSERNet Backbone AS209 259 211 48 18.5% Qwest Communications AS9557 61 16 45 73.8% Pakistan Telecommunication Compan 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 06 Jul '00

06 Jul '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 07 Jul, 2000 Analysis Summary ---------------- BGP routing table entries examined: 83516 Origin ASes present in the Internet Routing Table: 7848 Origin ASes announcing only one prefix: 2590 Transit ASes present in the Internet Routing Table: 1096 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: 6 Non-routable prefixes present in the Routing Table: 3 Prefixes being announced from the IANA Reserved Address blocks: 2 Number of addresses announced to Internet: 1167128256 Equivalent to 69 /8s, 144 /16s and 246 /24s Percentage of available address space announced: 31.5 Percentage of allocated address space announced: 62.9 Percentage of available address space allocated: 50.1 RIPE Region Analysis Summary ---------------------------- Prefixes being announced by RIPE Region ASes: 13038 Prefixes being announced from the RIPE address blocks: 10432 RIPE Region origin ASes present in the Internet Routing Table: 2092 RIPE Region origin ASes announcing only one prefix: 984 RIPE Region transit ASes present in the Internet Routing Table: 401 Average RIPE Region AS path length visible: 5.9 Max RIPE Region AS path length visible: 15 Number of RIPE addresses announced to Internet: 89172550 Equivalent to 5 /8s, 80 /16s and 170 /24s Percentage of available RIPE address space announced: 75.9 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 336 271 Swipnet AB 1270 249 390 UUNET Germany 1849 246 464 PIPEX 3320 222 250 Deutsche Telekom AG 1275 220 1091 DFN IP Service 786 181 959 JANET IP Service 719 178 145 LANLINK 5515 173 362 Sonera Finland 517 161 192 Xlink 1267 128 956 IUnet S.p.A 2609 127 4 EUnet-TN 2856 126 271 BTnet UK Regional network 3303 119 285 Swisscom 9057 111 38 Level 3 public IP n 3215 102 124 RAIN 1901 99 75 EUnet Austria 8895 92 28 Saudi Arabia AS 1290 84 195 PSINet UK Ltd. Global Per AS prefix count summary ---------------------------------- ASN No of nets /19 equiv Description 701 2040 3207 UUNET Technologies, Inc. 7018 1277 3082 AT&T 1 894 4553 BBN Planet 1221 887 979 Telstra 7046 876 500 UUNET Technologies, Inc. 705 822 2091 UUNET Technologies, Inc. 2914 770 1407 Verio, Inc. 1239 706 1674 Sprint ICM-Inria 3561 702 1643 Cable & Wireless USA 174 640 2845 PSINet Inc. 1785 523 824 Sprint ICM 271 469 411 BCnet Backbone 2764 459 117 connect.com.au pty ltd 3549 452 345 Frontier GlobalCenter 3602 443 77 Sprint Canada 1740 435 623 CERFnet 209 433 379 Qwest 3908 427 354 Supernet, Inc. 4293 397 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 65019 PRIVATE 208.185.254.128/27 6461 AboveNet Communicati Prefixes from private and non-routed address space (Global) ----------------------------------------------------------- Prefix Origin AS Description 192.168.15.4/30 2518 C&C Internet Service Mesh 192.168.15.8/30 2518 C&C Internet Service Mesh 192.168.15.208/28 2518 C&C Internet Service Mesh 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:23 /9:4 /10:5 /11:9 /12:26 /13:49 /14:166 /15:285 /16:6554 /17:860 /18:1732 /19:5571 /20:3341 /21:3520 /22:5303 /23:7130 /24:48045 /25:143 /26:176 /27:95 /28:73 /29:71 /30:195 /31:0 /32:140 End of report

1 0

APNIC REGION CIDR blocks - smallest allocations
by Anne Lord 06 Jul '00

06 Jul '00

Hi, In response to a request to these lists, APNIC has now compiled information about the minimum allocation sizes for the APNIC region address blocks. You can find this information at the URL below. http://www.apnic.net/db/min-alloc.html I hope this information is useful. Regards, Anne Manager, Member Services -- See you at the APNIC Meeting - Brisbane, Australia 25 - 27 October 2000 | http://www.apnic.net/meetings/ *****************************************************

1 0

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