- routing-wg - mailman.ripe.net

The status of the migration iissues
by Andrei Robachevsky 26 Apr '01

26 Apr '01

Dear Colleagues, As some of you might have noticed, several problems showed up after the migration. Let me present an update on their status: 1. PGP signed messages sent to <auto-rpsl(a)ripe.net> didn't pass authorization checks This was fixed on 24th of April. Please note that PGP signed updates cannot be processed by <auto-dbm(a)ripe.net>. Until 14th of May, <auto-dbm(a)ripe.net> processes updates in RIPE-181 format and automatically translates them into RPSL, which voids PGP signatures. 2. Conversion problems of updates sent to <auto-dbm(a)ripe.net> Problematic objects were: - Objects with syntax errors - Indented objects (containing leading whitespace) In both cases objects were not converted to RPSL and user received an empty acknowledgement. This was fixed today, 26th of April. Please note that <auto-dbm(a)ripe.net> cannot reproduce all the behaviour of the v2 database. In particular, empty attribute is treated as a syntax error and Routing Policy System Security authorization rules apply. We strongly recommend you to switch to updates in RPSL format as soon as possible. Also note, that <auto-dbm(a)ripe.net> will process updates in RIPE-181 format until 14th of May. After that, updates in RIPE-181 format should be sent to the new address, <auto-181(a)ripe.net>, and <auto-dbm(a)ripe.net> will accept only RPSL syntax. 3. Due to above problems some of the updates were not processed. If you haven't received an acknowledgement from the database one day after you sent your update we would kindly ask to re-send it. We apologize for any inconvenience these problems caused. We are working on some minor problems and rely on your understanding. Please visit the "Migration Issues" link on the "Database Status" page (http://www.ripe.net/ripencc/pub-services/db/issues.html) for the up-to-date information. Regards, Andrei Robachevsky DB Group Manager RIPE NCC

3 2

Draft revision of RIPE-210: Coordinated Route Flap Damping Parameters
by Philip Smith 25 Apr '01

25 Apr '01

Hi, bcc: nanog, apops, APNIC routing SIG, afnog Please accept my apologies for any duplicates. The attached is a proposed update and revision of the RIPE-210 Coordinated Route Flap Damping Parameters document. The authors would welcome any comments and feedback regarding the content of this document, either to the RIPE Routing Working Group, or at the RIPE meeting in Bologna, Italy, on w/b 30th April. We would also welcome links/sample configurations/examples for other router platforms (specifically Juniper/Foundry/Extreme and any other platforms which may be found in today's Internet) to augment the Cisco IOS configuration examples given in the Appendix. thanks, and kind regards, philip -- >>>>begin RIPE Routing-WG Recommendation for coordinated route-flap damping parameters Philip Smith Daniel Karrenberg Christian Panigl Joachim Schmitz This document Obsoletes: ripe-210, ripe-178 ----------------------------------------------------------------- Document status Version 1.2, April 24th, 2001 Abstract This paper recommends a set of route-flap damping parameters which should be applied by all ISPs in the Internet and should be deployed as default values by BGP router vendors. Table of Contents 1. Introduction 1.1 Motivation for route-flap damping 1.2 What is route-flap damping ? 1.3 "Progressive" versus "flat&gentle" approach 1.4 Motivation for coordinated parameters 1.5 Aggregation versus damping 1.6 "Golden Networks" 2. Recommended damping parameters 2.1 Motivation for recommendation 2.2 Description of recommended damping parameters 2.3 Example configuration for Cisco IOS 3. Other Features contributing to Internet Stability 3.1 BGP Route Refresh 3.2 Soft Reconfiguration (Cisco IOS) 3.3 Fast-External-Fallover (Cisco IOS) 4. Potential problems 4.1 Multiplication of flaps between ASes with multiple interconnections 4.2 Non-recommended flap damping parameters 5. References 6. Acknowledgements Appendices A.1 "Golden Networks" A.2 Sample Cisco IOS Configuration A.3 Study of Flap Damping Operation 1. Introduction Route-flap damping is a mechanism for (BGP) routers which is aimed at improving the overall stability of the Internet routing table and reducing the load on the CPUs of the core routers. 1.1 Motivation for route-flap damping In the early 1990s the accelerating growth in the number of prefixes being announced to the Internet (often due to inadequate prefix-aggregation), the denser meshing through multiple inter-provider paths, and increased instabilities started to cause significant impact on the performance and efficiency of the Internet backbone routers. Every time a routing prefix becomes unreachable because of a single line-flap, the withdrawal has to be advertised to the whole core Internet and dealt with by every single router which is carrying the full Internet routing table. To overcome this situation a route-flap damping mechanism was invented in 1993 and has been integrated into several router software implementations since 1995 (for example, Cisco, Merit/RSd, GateD Consortium). The implementation is described in detail in RFC2439. The flap damping mechanism is now widely used to help keep severe instabilities under control and more localised in the Internet. And there is a second benefit: it is raising the awareness of the existence of instabilities because severe route/line-flapping problems lead to permanent suppression of the unstable area by means of holding down the flapping prefixes. Route-flap damping has its greatest and most consistent value if it is applied as near to the source of the problem as possible. Therefore flap-damping should be applied both at peering and upstream boundaries, as well as at customer boundaries (see 1.4 and 1.5 for details). 1.2 What is route-flap damping ? When BGP route-flap damping is enabled in a router the router starts to collect statistics about the announcement and withdrawal of prefixes. Route-flap damping is governed by a set of parameters with vendor-supplied default values which may be modified by the router manager. The names, semantic and syntax of these parameters differ between the various implementations; however, the behaviour of the damping mechanism is basically the same. Each time a prefix is withdrawn, the router will increment the damping penalty by a fixed amount. When the number of withdrawals/announcements (=flap) is exceeded in a given time frame (cutoff threshold) the path is no longer used and not advertised to any BGP neighbour for a predetermined period starting from when the prefix stops flapping. Any more flaps happening after the prefix enters suppressed state will attract additional penalty. Once the prefix stops flapping, the penalty is decremented over time using a half-life parameter until the penalty is below a reuse threshold. Once below this reuse threshold the suppressed path is then re-used and re-advertised to BGP neighbours. Pointers to some more detailed and vendor specific documents: Cisco BGP Case Studies: Route Flap Damping http://www.cisco.com/warp/public/459/16.html ISI/RSd Configuration: Route Flap Damping http://www.isi.edu/div7/ra/RSd/doc/dampen.html GateD Configuration: Weighted Route Damping Statement http://www.gated.org/gated-web/code/doc/manuals/config_guide/bgp/ weighted_route_dampening.html See also "5. References" 1.3 "Progressive" versus "flat&gentle" approach One easy approach would be to just apply the current default-parameters which are treating all prefixes equally ("flat&gentle") everywhere. However, there is a major concern to penalise longer prefixes (=smaller aggregates) more than well aggregated short prefixes ("progressive"), because the number of short prefixes in the routing table is significantly lower and it seems in general that those are tending to be more stable and also are tending to affect more users. Another aspect is that progressive damping might increase the awareness of aggregation needs. However, it has to be accompanied by a careful design which doesn't force a rush to request and assign more address space than needed. A significant number of important services is sitting in long prefixes (e.g. root name servers), so the progressive approach has to exclude the strong penalisation for these so-called "golden" prefixes. With this recommendation we are trying to make a compromise and it is therefore called "graded damping". 1.4 Motivation for coordinated parameters There is a strong need for the coordinated use of damping parameters for several reasons: Coordination of "progressiveness": If penalties are not coordinated throughout the Internet, route-flap damping could lead to additional flapping or inconsistent routing because longer prefixes might already be re-announced through some parts of the Internet where shorter prefixes are still held down through other paths. Coordination of hold-down and reuse-threshold parameters between ISPs: If an upstream or peering provider would be damping more aggressively (e.g. triggered by less flaps or applying longer hold-down timers) than an access-provider towards his customers it will lead to a very inconsistent situation, where a flapping network might still be able to reach "near-line" parts of the Internet. Debugging of such instabilities is then much harder because the effect for the customer leads to the assumption that there is a problem "somewhere" in the "upstream" Internet instead of making him just call his ISPs hot-line and complain that he can't get out any longer. Further, after successful repair of the problem the access-provider can easily clear the flap-damping for his customer on his local router instead of needing to contact upstream NOCs all over the Internet to get the damping cleared. Vendor Defaults: As with most software implementations, there need to be some default values set when route-flap damping is enabled on routers. Vendors choosing different default values will result in a similar situation to that described above, where the more aggressive values will result in "black spots" in the Internet. Coordinated values will ensure consistency in dealing with instabilities. 1.5 Aggregation versus damping If a customer of an ISP is only using Provider Aggregated addresses, the aggregating upstream provider doesn't need to apply damping on these prefixes towards his customer, because instabilities of such prefixes will not propagate into the Internet. However, if a customer insists on announcing prefixes which can't be aggregated by its provider, damping should be applied. Reasons for leaking prefixes might include dual-homing (to different providers) of a customer, or customer's reluctance to renumber into the provider's aggregated address range. 1.6 "Golden Networks" Even though damping is strongly recommended, in some cases it may make sense to exclude certain networks or even individual hosts from damping. This is especially true if damping would cut off the access to vital infrastructure elements of the Internet. A most prominent example are the root name servers. At least in principle, there should be enough redundancy for root name servers. However we are still facing a situation where, at least outside USA, large parts of the Internet are seeing all of them through the same one or two backbone/upstream links (sea cable) and any instability of those links which is triggering damping would unnecessarily prolong the inaccessibility of the root name servers for an hour (at least those sitting in a /24 or longer prefix). Other examples of inclusions in the "Golden Networks" might be the Global Top Level Domain (gTLD) name servers, and possibly overseas or "special" networks the local ISP wishes to have continued connectivity to regardless of the instability of the infrastructure inbetween. Appendix 1 gives an example of the Golden Networks at the time of publication of this document. Before implementation of route flap damping using these Golden Networks, network managers are strongly encouraged to check that the networks listed are indeed still being announced, and are home to the servers mentioned. This can be done by matching BGP table announcements with the published addresses for the listed servers. These exceptions must only be made if there are strong and identifiable needs for them - the rule should be to apply coordinated route flap damping throughout. 2. Recommended damping parameters 2.1 Motivation for recommendation At RIPE26 and 27 Christian Panigl presented the following network backbone maintenance example from his own experience, which was triggering flap damping in some upstream and peering ISPs routers for all his and his customers /24 prefixes for more than 3 hours because of too "aggressive" parameters: scheduled SW upgrade of backbone router failed: - reload after SW upgrade 1 flap - new SW crashed 1 flap - reload with old SW 1 flap ------ 3 flaps within 10 minutes which resulted in the following damping scenario at some boundaries with progressive route-flap damping enabled: Prefix length: /24 /19 /16 suppress time: ~3h 45-60' <30' Therefore, in the Routing-WG session at RIPE27, it was agreed that suppression should not start until the 4th flap in a row and that the maximum suppression should in no case last longer than 1 hour from the last flap. It was agreed that a recommendation from RIPE would be desirable. Given that the current allocation policies are expected to hold for the foreseeable future, it was suggested that all /19's or shorter prefixes are not penalised harder (longer) than current Cisco default damping does. More recently, this recommendation has been altered so that only prefixes longer than a /21 are now damped more aggresively. The registries' minimum allocation is currently a /20, and a /21 announcement is quite feasible for a multihoming situation. With these suggestions in mind, Tony Barber designed the following set of route-flap damping parameters which have proved to work smoothly in his environment for a couple of months prior to the publication of RIPE-178 (the original version of this document). 2.2 Description of recommended damping parameters Basically the recommended values do the following with harsher treatment for /24 and longer prefixes: * don't start damping until the 4th flap * /24 and longer prefixes: max=min outage 60 minutes * /22 and /23 prefixes: max outage 45 minutes; min outage of 30 minutes * all other prefix lengths: max outage 30 minutes; min outage 10 minutes If a specific damping implementation does not allow configuration of prefix-dependent parameters the least aggressive set should be used: * don't start damping before the 4th flap in a row * max outage 30 minutes; min outage 10 minutes A sample configuration for Cisco IOS is provided in Appendix 2. This sample can be used as a basis for a configuration on other router platforms. 3. Other Features contributing to Internet Stability 3.1 BGP Route refresh RFC2918 describes a Route Refresh Capability for BGP-4. Prior to this, there was no mechanism to reset or refresh a BGP peering session without tearing it down and waiting for it to re-establish. This process is destructive - prefixes being exchanged between the two peering routers are withdrawn from their respective ASes, and this withdrawal can potentially pass through the whole Internet causing the burden and increased instability discussed earlier. Usually all that an ISP wishes when reseting a BGP session is to implement new or revised policy - destroying a BGP session carrying a large or the full routing table has severe impact on the ISP and his neighbours on the Internet. Furthermore, reset of a BGP session means the withdrawal of reachability information from the ISP's customers, and they have the perception that the Internet has "vanished" - the impression left with the end-user is that of an unreliable network. Route Refresh implements a messaging system whereby a router wishing to refresh or reset its BGP peering with its neighbour simply has to send the notification. When the neighbour receives the notification, it will send its entire announcement to its peer (obtained from BGP best path table and applicable outbound policy). To find out if your neighbour supports Route Refresh, using Cisco IOS as an example, enter: Router# sho ip bgp neigh w.x.y.c | include refresh Received route refresh capability(new) from peer Route refresh request: received 0, sent 0 If your router and your peer router support Route Refresh, you can use: Router# clear ip bgp w.x.y.c in for requesting a route refresh without clearing the BGP session. For an outbound route refresh without clearing the BGP session use Router# clear ip bgp w.x.y.c out It is recommended that all users of BGP use the route refresh capability when implementing new BGP policy. 3.2 Soft-Reconfiguration (Cisco IOS) Where the neighbour does not support RFC 2918 Route Refresh, there is a functionality in Cisco IOS called "Soft Reconfiguration". This reserves additional memory in the router to store the BGP table exactly as it was received from the peer, prior to any inbound policy being applied. The advantage of this is that the ISP can then change any inbound policy on the router without reseting the BGP session - the router simply uses the "raw" BGP table it has received from its peer. Disadvantage is that this functionality could potentially consume almost twice the amount of memory required for the BGP table heard from the peer. To configure soft-reconfiguration in IOS, simply add the extra line to the BGP peer configuration as below. Soft-reconfiguration is configured on a per-neighbour basis. ! router bgp 65501 neighbor 10.0.0.2 remote-as 65502 neighbor 10.0.0.2 soft-reconfiguration inbound ! Without the keyword "soft" a "clear ip bgp x.x.x.x" will completely reset the BGP session and therefore always withdraw all announced prefixes from/to neighbour x.x.x.x and re-advertise them (= route-flap for all prefixes which are available before and after the clear). With "clear ip bgp x.x.x.x soft out" the router doesn't reset the BGP session itself but sends an update for all its advertised prefixes. With "clear ip bgp x.x.x.x soft in" the router just compares the already received routes (stored in the "received" data structures) from the neighbour against locally configured inbound policy statements. It is recommended to use soft-reconfiguration with all peers which do not support RFC2918 Route Refresh Capability. 3.3 Fast-External-Fallover (Cisco IOS) Cisco IOS by default implements a feature known as "fast-external-fallover". This feature immediately clears the BGP session whenever the line-protocol to the external neighbour goes down. This feature is desirable so that there is fast failover in case of link failures - the router can withdraw paths as soon as the line goes down, rather than waiting for BGP keepalive timers. The drawback of this, however, is that circuits which are prone to unreliability will cause BGP sessions to drop and return (i.e. flap), resulting in instability within the ISP's network, and the potential for flap damping by upstreams or peers. If fast-external-fallover is turned off, the BGP sessions will survive these short line-flaps as it will use the longer BGP keepalive/hold timers (default 60/180 seconds). The drawback of turning it off - and currently it has to be done for a whole router and can not be selected peer-by-peer - is that the switch-over to an alternative path will take longer. We recommend turning off fast-external-fallover whenever possible: ! router bgp 65501 no bgp fast-external-fallover ! Alternatively it might be considered acceptable to retain "fast-external-fallover" and to turn off "interface keepalives" on unreliable circuits to overcome the immediate BGP resets on any significant CRC error period. Another potentially more satisfactory alternative would be to use a shorter per-neighbour BGP keepalive timer which has to be applied on both routers (e.g. 10 seconds which gives a hold-timer of 30 seconds): ! router bgp 65501 neighbor w.x.y.z timers 10 ! 4. Potential problems 4.1 Multiplication of flaps between ASes with multiple interconnections Christian Panigl experienced the following during a circuit upgrade of an Ebone customer: - Only ONE flap was generated as a result of the upgrade process (disconnect router-port from modem A, reconnect to modem B). Nevertheless the customer's prefix was damped in all ICM routers. - The flap statistics in the ICM routers stated *4* flaps !!! - The only explanation would be that the multiple interconnections between Ebone/AS1755 and ICM/AS1800 did multiply the flaps (advertisements/withdrawals arrived time-shifted at ICM routers through the multiple circuits). - This would then potentially hold true for any meshed topology because of the propagation delays of advertisements/withdrawals. There are two potential solutions to workaround this problem. The first one is operational, the second one is a software configuration feature (for Cisco IOS and possibly other implementations as well). * Schedule a downtime for at least 3-5 minutes which should be enough time for the prefix withdrawals to have propagated through all paths before reconnection and re-advertisement of the prefix. Avoid clearing BGP sessions as this also could generate a 30 minute outage through flap damping! * Configure a permanent static route pointing to the customer interface. Even if the interface goes down, there is still an entry in the routing table for the customer network, and BGP will therefore still announce the prefix. Example: ! router bgp 65500 network 169.254.0.0 mask 255.255.0.0 ip route 169.254.0.0 255.255.0.0 serial 5/0 permanent ! If migrating the customer from one router port to another, simply enter the second static route pointing to the new interface. Move the cable between ports - BGP continues to announce the prefix as the entry is still in the routing table. Note: this solution only applies to customers who connect using static routes. If the customer connects using BGP, first disable fast-external-fallover on both the customer and ISP router, and then move the cable in a time period less than the BGP hold-timer. 4.2 Non-recommended flap damping parameters There are situations where service providers would like to design their own route flap damping parameters for local needs or conditions. If this is really desired, then it is important to pay attention to how flap damping parameters are configured, whether the values are feasible or not, etc. For example, in Cisco IOS, it is perfectly possible to configure flap damping parameters which do nothing. * One example might be the configuration "set dampening 15 500 3000 30". Here the reuse limit is 500, maximum suppress time is 30 minutes and the half life is 15 minutes. Using these three parameters gives a maximum possible penalty value of 2000, well below the suppress limit of 3000. So even though this can be successfully configured on the router, no damping will take place. * Another example might be the configuration "set dampening 15 750 3000 30". Here the reuse limit is 750, maximum suppress time is 30 minutes and the half life is 15 minutes. Using these three parameters gives a maximum possible penalty of 3000, exactly the same as the suppress-limit. In Cisco IOS, the penalty is decayed every 5 seconds, so flap damping will only be take place if the update follows the withdraw within that 5 second time frame. 99% of the time no flap damping will take place. 5. References RIPE/Routing-WG Minutes dealing with Route Flap Damping: http://www.ripe.net/ripe/meetings/archive/ripe-24/ripe-m-24.txt http://www.ripe.net/ripe/meetings/archive/ripe-25/ripe-m-25.txt http://www.ripe.net/wg/routing/r25-routing.html http://www.ripe.net/wg/routing/r26-routing.html http://www.ripe.net/wg/routing/r27-routing.html Curtis Villamizar, Ravi Chandra, Ramesh Govindan RFC2439: BGP Route Flap Damping (Proposed Standard) ftp://ftp.ietf.org/rfc/rfc2439.txt Enke Chen RFC2918: Route Refresh Capability for BGP-4 (Proposed Standard) ftp://ftp.ietf.org/rfc/rfc2918.txt Merit/IPMA: Internet Routing Recommendations http://www.merit.edu/ipma/docs/help.html Cisco BGP Case Studies: Route Flap Damping http://www.cisco.com/warp/public/459/16.html Cisco Documentation: Configuring BGP / Route Dampening http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/ 121cgcr/ip_c/ipcprt2/1cdbgp.htm Cisco Documentation: BGP Soft Reset Enhancement http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/ 120newft/120t/120t7/sftrst.htm ISI/RSd Configuration: Route Flap Damping http://www.isi.edu/div7/ra/RSd/doc/dampen.html GateD Configuration: Weighted Route Damping Statement http://www.gated.org/gated-web/code/doc/manuals/config_guide/bgp/ weighted_route_dampening.html 6. Acknowledgements Thanks to all the contributors to this updated version. 7. Changes over previous versions This document is a significant rewrite and update of RIPE-210. The "Golden Networks" have now been moved to an Appendix as they are frequently changing and the authors have come across several instances of providers implementing the recommendations without actually checking that the Root Nameserver networks were still as listed in the document. Updates to the Cisco IOS configuration have been made, and the parameters chosen for /24 networks have been corrected to make them feasible. Examples of flap damping in operation have been added to Appendix 3. The sample configuration has been moved to Appendix 2 - again IOS is used as a known working example. Appendices A.1 "Golden Networks" This appendix lists some examples of Golden Networks which could be used when applying route flap damping at the edge of an ISP's network. The example uses Cisco IOS configuration syntax. The list was correct at time of writing (April 2001). ip prefix-list golden-networks description Golden Networks ! Root Nameservers ip prefix-list golden-networks permit 198.41.0.0/24 ! A & J ip prefix-list golden-networks permit 128.9.0.0/16 ! B ip prefix-list golden-networks permit 192.33.4.0/24 ! C ip prefix-list golden-networks permit 128.8.0.0/16 ! D ip prefix-list golden-networks permit 192.203.230.0/24 ! E ip prefix-list golden-networks permit 192.5.4.0/23 ! F ip prefix-list golden-networks permit 192.112.36.0/24 ! G ip prefix-list golden-networks permit 128.63.0.0/16 ! H ip prefix-list golden-networks permit 192.36.148.0/24 ! I ip prefix-list golden-networks permit 193.0.14.0/24 ! K ip prefix-list golden-networks permit 198.32.64.0/24 ! L ip prefix-list golden-networks permit 202.12.27.0/24 ! M ! Global Top Level Domain Servers ip prefix-list golden-networks permit 192.5.6.0/24 ! A ip prefix-list golden-networks permit 203.181.96.0/19 ! B ip prefix-list golden-networks permit 192.26.92.0/24 ! C ip prefix-list golden-networks permit 192.31.80.0/24 ! D ip prefix-list golden-networks permit 192.12.94.0/24 ! E ip prefix-list golden-networks permit 192.35.51.0/24 ! F ip prefix-list golden-networks permit 192.42.93.0/24 ! G ! ip prefix-list golden-networks permit ???? ! No H ip prefix-list golden-networks permit 192.36.144.0/24 ! I ip prefix-list golden-networks permit 210.132.96.0/19 ! J ip prefix-list golden-networks permit 213.177.192.0/21 ! K ip prefix-list golden-networks permit 192.41.162.0/24 ! L ip prefix-list golden-networks permit 202.153.112.0/20 ! M A.2 Sample Cisco IOS Configuration ! Parameters are : ! set damp <half-life-time> <reuse-at> <suppress-at> <max-suppress-time> ! There is a 1000 penalty for each flap ! There is a 500 penalty for change in attribute ! Penalty decays at granularity of 5 seconds, decay starts as soon as ! prefix is withdrawn ! Unsuppressed at granularity of 10 seconds ! damping info kept until penalty becomes < half of reuse limit. ! ! Cisco/IOS value-ranges: ! ! <half-life-time> (range is 1-45 minutes). ! <reuse-value> (range is 1-20000). ! <suppress-value> (range is 1-20000). ! <max-suppress-time> (range is 1-255 minutes ). ! !----------------------------------------------------------------------- ! ENABLE BGP DAMPenING using "graded" route-map !----------------------------------------------------------------------- router bgp 65500 NO bgp damp bgp damp route-map graded-flap-damping ! !----------------------------------------------------------------------- ! DEFINE "graded" route-map !----------------------------------------------------------------------- NO route-map graded-flap-damping ! ! don't damp Candidate Default Routes ! OPTIONAL (not part of recommendation) ! prefix-list default-networks lists the Candidate Default Routes ! !route-map graded-flap-damping deny 5 ! match ip address prefix-list default-networks ! ! don't damp Golden Networks ! route-map graded-flap-damping deny 10 match ip address prefix-list golden-networks ! ! - /24 and longer prefixes: max=min outage 60 minutes ! route-map graded-flap-damping permit 20 match ip address prefix-list min24 set damp 30 820 3000 60 ! ! - /22 and /23 prefixes: max outage 45 minutes but potential for ! less because of shorter half life value - minimum of 30 minutes ! outage route-map graded-flap-damping permit 30 match ip address prefix-list max22-23 set damp 15 750 3000 45 ! ! - all else prefixes: max outage 30 minutes min outage 10 minutes ! route-map graded-flap-damping permit 40 set damp 10 1500 3000 30 ! !----------------------------------------------------------------------- ! DEFINE PREFIX-LISTS !----------------------------------------------------------------------- ! ! OPTIONAL default-networks !no ip prefix-list default-networks !ip prefix-list default-networks description Candidate Default Routes ! no ip prefix-list golden-networks ip prefix-list golden-networks description Golden Networks ! See 7.1 above for sample list ! no ip prefix-list min24 ip prefix-list min24 description Apply to /24 and longer prefixes ip prefix-list min24 permit 0.0.0.0/0 ge 24 ! no ip prefix-list max22-23 ip prefix-list max22-23 description Apply to /22 and /23 prefixes ip prefix-list max22-23 permit 0.0.0.0/0 ge 22 le 23 ! A.3 Study of Flap Damping Operation It is instructive to observe how route flap damping actually works on a router - doing so will help the reader understand how the particular values described above were chosen. The test bed had two Cisco routers connected to each other. One router originated prefixes, the other one had the flap damping parameters described above in the text. The router originating the prefixes would withdraw a prefix, then reannounce, then withdraw, reannounce, etc. The BGP process in IOS checks every 60 seconds for any new or withdrawn prefixes in the local configuration - so on the source router, the withdraw and announce was done by removing and adding the BGP network statement for the prefix in question. The router monitoring the flaps would see the prefix being withdrawn and then announced 60s later. A.3.1 For /24s Parameters used are "set dampening 15 820 3000 30" 1st flap 1000 decay to 966, 982 at update 2nd flap 1966 decay to 1894, 1926 at update 3rd flap 2894 decay to 2787, 2846 at update 4th flap 3280 decay to 3165, 3226 at update Maximum possible penalty is 3280 as defined by the flap parameters, so the penalty at the 4th flap was only incremented from 2787 to 3280, not 3787 as might have been expected. At the 4th flap the prefix was marked as being suppressed for 59 minutes when the update message was received. If the update after the 4th flap was not received within 4 minutes and 20 seconds, the penalty dropped below 3000, and the prefix was not suppressed. A.3.2 For /22s, /23s Parameters used are "set dampening 15 750 3000 45" 1st flap 1000 decay to 921, 960 at update 2nd flap 1921 decay to 1777, 1850 at update 3rd flap 2777 decay to 2583, 2671 at update 4th flap 3583 decay to 3311, 3451 at update Maximum possible penalty is 6000. At the 4th flap the prefix was marked as being suppressed for 33 minutes when the update message was received. If the update after the 4th flap was not received within 4 minutes and 40 seconds, the penalty dropped below 3000, and the prefix was not suppressed. A.3.3 For remaining prefixes Parameters used are "set dampening 10 1500 3000 30" 1st flap 1000 decay to 889, 946 at update 2nd flap 1889 decay to 1679, 1781 at update 3rd flap 2679 decay to 2367, 2526 at update 4th flap 3367 decay to 3019, 3176 at update Maximum possible penalty is 12000. At the 4th flap the prefix was marked as being suppressed for 10 minutes when the update message was received. If the update after the 4th flap was not received within 2 minutes and 5 seconds, the penalty dropped below 3000, and the prefix was not suppressed. A.3.4 Summary When analysing flap damping performance on the router or across the network, network managers should compare with the above lab tests. Note especially that slowly flapping prefixes are unlikely to be suppressed even though they show significant flapping history. A future version of this document may consider what to do in this instance. >>>>end

2 2

draft agenda routing/joint routing&db wg RIPE 39
by SchmitzJo＠aol.com 24 Apr '01

24 Apr '01

Dear colleagues, please find enclosed the first draft of the agenda for the session of the routing working rgoup at RIPE 39, Bologna. The session will be held Wednesday, 2-May, 14:00 Routing WG session Due to the importance of the subject and because it is affecting both working groups we are having again a joint session of the routing and database groups on the same day in the 2nd afternoon slot. Wednesday, 2-May, 16:00 Joint routing/db WG session I would also like to direct your attention to two interesting tutorials: For more information on these two tutorials, please refer to the RIPE meeting web pages. Monday, 30-Apr, 9:00 Full day tutorial on MPLS by Clarence Filsfils (Cisco) Tuesday, 1-May, 9:00 Half day tutorial on the RAToolSet by Cengiz Allaettinoglu (Packetdesign) As usual comments, additions, changes to the agenda of the Routing WG welcome! ---- R I P E 3 9 B O L O G N A Routing Working Group Session A. Preliminaries (Joachim Schmitz) (5min) - introduction - participants' list - volunteering of scribe - agenda bashing - RIPE 37 minutes - actions from earlier meetings B. Cengiz Allaettinoglu: Observations on ISIS Convergence (30min) C. Philip Smith: Update on RIPE-210 (Route Flap Damping) (20min) - update - discussion D. Henk Uijterwaal: Update from the RIS Project (15min) Joint Session with the Database WG E. Andrei Robachevsky: Migration to the new RIPE database (20min) F. Cengiz Allaettinoglu: Application of the RAToolSet (open end) Y. Input from other WGs Z. AOB ---- Thanks Joachim --- JS395-RIPE -- standard disclaimer ---

1 0

Re: New DB and line continuation?
by Andrei Robachevsky 23 Apr '01

23 Apr '01

Dear Berislav, Berislav Todorovic wrote: > > On Mon, 23 Apr 2001, DB-News wrote: > > >> The new version of the RIPE Database is now up and running! > >> All objects have been automatically converted to RPSL and loaded into > >> the new version of the Database. > > Congratulations! However, I have a question: > > When an attribute needs multiple lines to be described, the standard > RPSL format requires the attribute name to be mentioned once, while > successive lines are separted by spaces or commas (like you defined > in the transition document as well). It used to be like that in the > previous version of rpsl.ripe.net. However, right now, it seems to > me there is a strange RIPE-181/RPSL mix in place. See example: > Indeed, we tried to introduce as little changes to objects look as possible, while staying RPSL compliant. In fact, RPSL defines members attribute as: Attribute Value Type as-set <object-name> mandatory, single-valued, class key members list of <as-numbers> or optional, multi-valued <as-set-names> which means that one can have multiple 'members:' attribute, each of them may have a list of members separated by commas. So, formally there is no RPSL syntax violation. You can update your object to make it look like in RADB, both examples are accepted and valid in the RIPE database. Regards, Andrei > * RADB and old REIMP.RIPE (standard RPSL): > > [beri@nix00 ~]$ rwhois -h whois.ra.net as-kq > as-set: AS-KQ > descr: KPNQwest European routes > Formerly AS-EUNET AND NOT AS-EUNETQWEST > members: AS286, AS719, AS1136, AS1137, AS1213, > AS1234, AS1889, AS1891, AS1902, AS2043, > AS2049, AS2110, AS2135, AS2857, AS3220, > ... > > * RIPE (new format, RPSL): > > as-set: AS-KQ > descr: KPNQwest European routes > descr: Formerly AS-EUNET AND NOT AS-EUNETQWEST > members: AS286, AS719, AS1136, AS1137, AS1213, AS1234, AS1889 > members: AS1891, AS1902, AS2043, AS2049, AS2110, AS2135, AS2857 > members: AS3220, AS3246, AS3262, AS3265, AS3286, AS3324, AS3333 > members: AS3347, AS3615, AS5385, AS5399, AS5403, AS5407, AS5419 > > While some of you might think this is not important, this is VERY > important to some of us who make scripts for automating our tasks with > the RIPE DB. > > Can anyone explain the reason of this RPSL syntax violation? Thanks! > > Regards, > Beri > > --------- Berislav Todorovic, Network Engineer --------- > ------- KPNQwest N.V. - IP NOC (formerly EUnet NOC) ------- > ---- Wilhelmina van Pruisenweg 78, 2595 AN Den Haag, NL ---- > --- Phone: +31-70-379-3990; Mobile: +31-651-333-641 --- > -- Email: beri(a)kpnqwest.net <=> beri(a)EU.net -- > --- _ _ ____ _ .--. ____ ____ __/_ --- > ----- /__/ /___/ /\ / / / | / /___/ /___ / ------ > ------ _/ \_ / _/ \/ (__.\ |/\/ /___ ____/ (__. ----- -- Andrei Robachevsky DB Group Manager RIPE NCC

1 0

Re: New DB and line continuation?
by RIPE Database Administration 23 Apr '01

23 Apr '01

Hi, Berislav Todorovic, Thank you for reporting this. We are investigating. If you have anymore questions, please contact <ripe-dbm(a)ripe.net>. Regards, A. M. R. Magee ______________ RIPE NCC Berislav Todorovic <beri(a)kpnqwest.net> writes: * On Mon, 23 Apr 2001, DB-News wrote: * * >> The new version of the RIPE Database is now up and running! * >> All objects have been automatically converted to RPSL and loaded into * >> the new version of the Database. * * Congratulations! However, I have a question: * * When an attribute needs multiple lines to be described, the standard * RPSL format requires the attribute name to be mentioned once, while * successive lines are separted by spaces or commas (like you defined * in the transition document as well). It used to be like that in the * previous version of rpsl.ripe.net. However, right now, it seems to * me there is a strange RIPE-181/RPSL mix in place. See example: * * * RADB and old REIMP.RIPE (standard RPSL): * * [beri@nix00 ~]$ rwhois -h whois.ra.net as-kq * as-set: AS-KQ * descr: KPNQwest European routes * Formerly AS-EUNET AND NOT AS-EUNETQWEST * members: AS286, AS719, AS1136, AS1137, AS1213, * AS1234, AS1889, AS1891, AS1902, AS2043, * AS2049, AS2110, AS2135, AS2857, AS3220, * ... * * * RIPE (new format, RPSL): * * as-set: AS-KQ * descr: KPNQwest European routes * descr: Formerly AS-EUNET AND NOT AS-EUNETQWEST * members: AS286, AS719, AS1136, AS1137, AS1213, AS1234, AS1889 * members: AS1891, AS1902, AS2043, AS2049, AS2110, AS2135, AS2857 * members: AS3220, AS3246, AS3262, AS3265, AS3286, AS3324, AS3333 * members: AS3347, AS3615, AS5385, AS5399, AS5403, AS5407, AS5419 * * While some of you might think this is not important, this is VERY * important to some of us who make scripts for automating our tasks with * the RIPE DB. * * Can anyone explain the reason of this RPSL syntax violation? Thanks! * * Regards, * Beri * * --------- Berislav Todorovic, Network Engineer --------- * ------- KPNQwest N.V. - IP NOC (formerly EUnet NOC) ------- * ---- Wilhelmina van Pruisenweg 78, 2595 AN Den Haag, NL ---- * --- Phone: +31-70-379-3990; Mobile: +31-651-333-641 --- * -- Email: beri(a)kpnqwest.net <=> beri(a)EU.net -- * --- _ _ ____ _ .--. ____ ____ __/_ --- * ----- /__/ /___/ /\ / / / | / /___/ /___ / ------ * ------ _/ \_ / _/ \/ (__.\ |/\/ /___ ____/ (__. ----- * *

1 0

First phase of the migration to the new RIPE Database is completed
by DB-News 23 Apr '01

23 Apr '01

Dear Colleagues, The new version of the RIPE Database is now up and running! All objects have been automatically converted to RPSL and loaded into the new version of the Database. The first phase of the migration has been successfully completed. The following mail robots accept updates to the RIPE Database: <auto-dbm(a)ripe.net> - updates are accepted in RIPE-181 format and automatically translated into RPSL. However, several restrictions apply to such updates: empty and misspelled attributes are not allowed, PGP auth is not supported. Also, RPSL authorization rules apply. <auto-rpsl(a)ripe.net> - updates are accepted in RPSL format. This setup will be in place till 14 May, 2001. For more information about the migration please visit http://www.ripe.net/ripencc/pub-services/db/rpsl/announcement.html and http://www.ripe.net/ripencc/pub-services/db/rpsl/index.html Best Regards, Andrei Robachevsky DB Group RIPE NCC

1 0

The Cidr Report
by Tony Bates 21 Apr '01

21 Apr '01

This is an auto-generated mail on Fri Apr 20 23:00:00 PDT 2001 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 20Apr01 0) General Status Table History ------------- Date Prefixes 130401 99823 140401 99656 150401 99795 160401 99731 170401 99601 180401 99779 190401 99884 200401 100216 Check http://www.employees.org/~tbates/cidr.plot.html for a plot of the table history. Possible Bogus Routes --------------------- *** Bogus 223.255.46.0 from AS6853 *** Bogus 223.255.70.0 from AS6853 AS Summary ---------- Number of ASes in routing system: 10519 Number of ASes announcing only one prefix: 6219 (3531 cidr, 2688 classful) Largest number of cidr routes: 1218 announced by AS705 Largest number of classful routes: 1592 announced by AS1221 1) Gains by aggregating at the origin AS level --- 20Apr01 --- ASnum NetsNow NetsCIDR NetGain % Gain Description AS1221 1592 1194 398 25.0% Telstra Pty Ltd AS701 1462 1276 186 12.7% 1 AS705 368 251 117 31.8% 1 AS6429 214 105 109 50.9% 1 AS4151 247 139 108 43.7% 1 AS6595 163 62 101 62.0% 1 AS13999 104 8 96 92.3% 1 AS4293 370 277 93 25.1% 1 AS7018 694 605 89 12.8% 1 AS15412 430 341 89 20.7% FLAG Telecom Global Internet AS AS8013 319 236 83 26.0% 1 AS4755 218 138 80 36.7% Videsh Sanchar Nigam Ltd. Autonom AS577 241 172 69 28.6% 1 AS5106 101 37 64 63.4% 1 AS3749 120 59 61 50.8% 1 AS9498 75 15 60 80.0% BHARTI BT INTERNET LTD. AS3464 151 92 59 39.1% 1 AS11252 92 34 58 63.0% 1 AS724 203 146 57 28.1% 1 AS16758 63 6 57 90.5% 1 AS1 609 552 57 9.4% 1 AS6413 67 11 56 83.6% 1 AS226 149 93 56 37.6% 1 AS7568 84 29 55 65.5% C.S. Communications Co., Ltd. AS6471 99 46 53 53.5% 1 AS4323 230 178 52 22.6% 1 AS9269 116 67 49 42.2% City Telecom (H.K.) Ltd. AS852 200 152 48 24.0% 1 AS10692 62 14 48 77.4% 1 AS9683 48 2 46 95.8% Kyonggi Cable TV 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

Migration of the TEST database is completed
by Andrei Robachevsky 20 Apr '01

20 Apr '01

Dear Colleagues, The TEST database has been successfully migrated to v3 software. All objects in the TEST database were converted to RPSL compliant format. You can continue using the TEST database till 14 May as follows: - <test-dbm(a)ripe.net> mail robot accepts updates in RIPE-181 format with some limitations. - <test-rpsl(a)ripe.net> mail robot accepts updates in RPSL format. After that day changes in robots' functionality will follow the plan fro the production database. Please see http://www/ripencc/pub-services/db/rpsl/announcement.html and http://www/ripencc/pub-services/db/rpsl/index.html for more information. Finding objects in the TEST Database: Do whois -h test-whois.ripe.net <Search String> e.g. whois -h test-whois.ripe.net PB3-TEST The whois options that work in the RIPE Database also work in the TEST Database. We invite you to try them. Regards, Andrei Robachevsky DB Group Manager RIPE NCC

1 0

RAToolSet 4.7.0 now supports the new RIPE server
by Cengiz Alaettinoglu 20 Apr '01

20 Apr '01

RAToolSet 4.7.0 is available at ftp://ftp.isi.edu/ra/RAToolSet (There are redhat linux 7.1 and solaris 2.5.1 binaries as well). This release supports the new ripe server. Please use -protocol ripe option when connecting to the new server. All the tools, including RtConfig to configure routers, peval, and roe to manage route objects, work with the new server. Several features of roe are only available with the new RIPE server. I will be giving a tutorial on RPSL and these tools in the upcoming RIPE meeting. Lastly, I would like to thank Shane Kerr and Andrei Robacevsky for answering all my questions with patience and their help coding the client side. Cengiz

1 0

Weekly Routing Table Report
by Routing Analysis 19 Apr '01

19 Apr '01

This is an automated weekly mailing describing the state of the Internet Routing Table as seen from APNIC's router in Japan. 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>. Routing Table Report 20 Apr, 2001 Analysis Summary ---------------- BGP routing table entries examined: 103456 Origin ASes present in the Internet Routing Table: 10626 Origin ASes announcing only one prefix: 3836 Transit ASes present in the Internet Routing Table: 1422 Average AS path length visible in the Internet Routing Table: 5.3 Max AS path length visible: 17 Illegal AS announcements present in the Routing Table: 34 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: 1239197280 Equivalent to 73 /8s, 220 /16s and 166 /24s Percentage of available address space announced: 33.4 Percentage of allocated address space announced: 65.6 Percentage of available address space allocated: 51.0 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 15690 Prefixes being announced from the APNIC address blocks: 14205 APNIC Region origin ASes present in the Internet Routing Table: 1232 APNIC Region origin ASes announcing only one prefix: 436 APNIC Region transit ASes present in the Internet Routing Table: 197 Average APNIC Region AS path length visible: 5.1 Max APNIC Region AS path length visible: 14 Number of APNIC addresses announced to Internet: 71391058 Equivalent to 4 /8s, 65 /16s and 87 /24s Percentage of available APNIC address space announced: 70.2 APNIC AS Blocks 4608 - 4864, 7467 - 7722, 9216 - 10239, 17408 - 18431 APNIC Address Blocks 61/8, 202/7, 210/7 and 218/8 ARIN Region Analysis Summary ---------------------------- Prefixes being announced by ARIN Region ASes: 71577 Prefixes being announced from the ARIN address blocks: 49051 ARIN Region origin ASes present in the Internet Routing Table: 6462 ARIN Region origin ASes announcing only one prefix: 1911 ARIN Region transit ASes present in the Internet Routing Table: 683 Average ARIN Region AS path length visible: 5.2 Max ARIN Region AS path length visible: 14 Number of ARIN addresses announced to Internet: 180570501 Equivalent to 10 /8s, 195 /16s and 73 /24s Percentage of available ARIN address space announced: 82.8 ARIN AS Blocks 1 - 1876, 1902 - 2042, 2044 - 2046, 2048 - 2106 2138 - 2584, 2615 - 2772, 2823 - 2829, 2880 - 3153 3354 - 4607, 4865 - 5119, 5632 - 6655, 6912 - 7466 7723 - 8191, 10240 - 12287, 13312 - 15359 16384 - 17407, 18432 - 20479 ARIN Address Blocks 63/8, 64/7, 66/8, 199/8, 200/8, 204/6, 208/7 and 216/8 RIPE Region Analysis Summary ---------------------------- Prefixes being announced by RIPE Region ASes: 16155 Prefixes being announced from the RIPE address blocks: 12841 RIPE Region origin ASes present in the Internet Routing Table: 2939 RIPE Region origin ASes announcing only one prefix: 1489 RIPE Region transit ASes present in the Internet Routing Table: 540 Average RIPE Region AS path length visible: 5.9 Max RIPE Region AS path length visible: 17 Number of RIPE addresses announced to Internet: 96663513 Equivalent to 5 /8s, 194 /16s and 247 /24s Percentage of available RIPE address space announced: 82.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 20480 - 21503 RIPE Address Blocks 62/8, 193/8, 194/7, 212/7 and 217/8 APNIC Region per AS prefix count summary ---------------------------------------- ASN No of nets /19 equiv Description 1221 2001 684 Telstra 2764 425 147 connect.com.au pty ltd 703 390 205 UUNET Technologies, Inc. 2907 363 875 SINET Japan 4755 301 110 VSNL India 4538 235 1038 China Education and Research 7539 228 102 Delegated to TWNIC for subseq 4134 188 623 Data Communications Bureau 4766 187 770 KORnet Powered BY Korea Telec 7474 178 85 Optus Communications 9269 161 22 Hong Kong CTI 1237 156 70 System Engineering Research I 4740 152 10 Ozemail 7657 152 12 The Internet Group Limited 17561 151 61 Internet service provision to 7545 147 10 TPG Internet Pty Ltd 4786 129 7 NetConnect Communications Pty 7586 124 9 Paradox Digital Pty. Ltd 7617 124 46 One.Net Pty Ltd 9797 122 10 Asia Online Australia RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /19 equiv Description 702 480 670 UUNET Technologies, Inc. 3301 389 337 TeliaNet Sweden 1270 280 448 UUNET Germany 1257 277 247 Swipnet AB 680 207 914 Deutschef Forschurgsnetz 3215 207 228 RAIN 5515 190 336 Sonera Finland 719 189 146 LANLINK 786 185 959 JANET IP Service 3320 160 710 Deutsche Telekom AG 5400 129 41 Concert Internet Plus Europea 517 127 134 Xlink 3303 123 298 Swisscom 2856 122 388 BTnet UK Regional network 1290 117 206 PSINet UK Ltd. 8708 113 5 Romania Data System 3352 108 241 Ibernet, Internet A 1849 107 223 UUNET UK (formerly PIPEX) 1267 97 978 IUnet S.p.A 1901 97 77 EUnet Austria ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /19 equiv Description 701 2426 3626 UUNET Technologies, Inc. 705 1612 69 UUNET Technologies, Inc. 7018 962 3190 AT&T 1 960 4495 BBN Planet 7046 801 552 UUNET Technologies, Inc. 1239 641 1603 Sprint ICM-Inria 2914 608 1210 Verio, Inc. 3561 561 1264 Cable & Wireless USA 174 533 2751 PSINet Inc. 3549 505 514 Global Crossing 4293 480 52 Cable & Wireless USA 209 449 707 Qwest 690 424 43 Merit Network 2548 400 514 Digital Express Group, Inc. 3908 376 262 Supernet, Inc. 8151 362 218 UniNet S.A. de C.V. 3967 336 226 Exodus Communication 4323 336 136 Time Warner Communications, I 8013 336 54 PSINet Ltd. Canada 11371 332 50 Rhythms NetConnections Global Per AS prefix count summary ---------------------------------- ASN No of nets /19 equiv Description 701 2426 3626 UUNET Technologies, Inc. 1221 2001 684 Telstra 705 1612 69 UUNET Technologies, Inc. 7018 962 3190 AT&T 1 960 4495 BBN Planet 7046 801 552 UUNET Technologies, Inc. 1239 641 1603 Sprint ICM-Inria 2914 608 1210 Verio, Inc. 3561 561 1264 Cable & Wireless USA 174 533 2751 PSINet Inc. 3549 505 514 Global Crossing 702 480 670 UUNET Technologies, Inc. 4293 480 52 Cable & Wireless USA 209 449 707 Qwest 2764 425 147 connect.com.au pty ltd 690 424 43 Merit Network 2548 400 514 Digital Express Group, Inc. 703 390 205 UUNET Technologies, Inc. 3301 389 337 TeliaNet Sweden 3908 376 262 Supernet, Inc. List of Unregistered ASNs (Global) ---------------------------------- Bad AS Designation Network Transit AS Description 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 1800 SPRINT 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 1800 SPRINT 5757 UNALLOCATED 192.239.13.0/24 701 UUNET Technologies, 64561 PRIVATE 202.139.40.192/27 7474 Optus Communications 64537 PRIVATE 202.139.47.96/29 7474 Optus Communications 64537 PRIVATE 202.139.116.0/25 7474 Optus Communications 64532 PRIVATE 202.139.116.128/27 7474 Optus Communications 64532 PRIVATE 202.139.116.192/27 7474 Optus Communications 64532 PRIVATE 202.139.116.224/29 7474 Optus Communications 64532 PRIVATE 202.139.116.240/29 7474 Optus Communications 64532 PRIVATE 202.139.116.248/29 7474 Optus Communications 64534 PRIVATE 202.139.121.0/28 7474 Optus Communications 64537 PRIVATE 202.139.168.192/27 7474 Optus Communications 64543 PRIVATE 202.139.182.0/28 7474 Optus Communications 65535 PRIVATE 203.24.169.0/24 17486 Swiftel Communicatio 65500 PRIVATE 203.166.86.0/24 10084 Western Australian I 64553 PRIVATE 203.202.2.72/29 7474 Optus Communications 64555 PRIVATE 203.202.9.88/29 7474 Optus Communications 64534 PRIVATE 203.202.9.128/25 7474 Optus Communications 64548 PRIVATE 203.202.10.0/27 7474 Optus Communications 64560 PRIVATE 203.202.14.80/28 7474 Optus Communications 64553 PRIVATE 203.202.15.16/28 7474 Optus Communications 5555 UNALLOCATED 205.110.64.0/24 721 DLA Systems Automati 5555 UNALLOCATED 205.110.68.0/22 721 DLA Systems Automati 5555 UNALLOCATED 205.110.72.0/21 721 DLA Systems Automati 5757 UNALLOCATED 207.19.224.0/24 701 UUNET Technologies, Advertised IANA Reserved Addresses ---------------------------------- Network Origin AS Description 223.255.46.0/24 6853 GLOBAL-ONE-PORTUGAL 223.255.70.0/24 6853 GLOBAL-ONE-PORTUGAL Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:22 /9:4 /10:4 /11:10 /12:29 /13:67 /14:206 /15:326 /16:6939 /17:1125 /18:2106 /19:6583 /20:5060 /21:4421 /22:6744 /23:8626 /24:59774 /25:275 /26:405 /27:216 /28:196 /29:134 /30:125 /31:1 /32:58 Number of /24s announced per /8 block (Global) ---------------------------------------------- 9:3 12:354 13:10 15:1 17:1 24:709 26:1 32:12 38:7 44:3 47:1 53:2 55:1 57:11 61:28 62:131 63:1916 64:1461 65:954 66:274 128:30 129:112 130:20 131:26 132:9 133:1 134:168 135:8 136:16 137:117 138:247 139:52 140:149 141:176 142:61 143:41 144:131 145:9 146:132 147:134 148:154 149:134 150:27 151:175 152:801 153:33 154:15 155:77 156:39 157:109 158:61 159:83 160:28 161:56 162:61 163:136 164:129 165:127 166:177 167:134 168:82 169:34 170:219 171:2 192:5410 193:1949 194:2046 195:770 196:406 198:3656 199:3384 200:1909 202:2471 203:4989 204:3376 205:2246 206:2719 207:2844 208:2905 209:3202 210:481 211:190 212:847 213:408 214:9 215:11 216:2936 217:196 223:2 End of report

1 0