February 2006 - NANOG - lists.nanog.org

NANOG36-NOTES 2006.02.14 Tools BOF Notes
by Matthew Petach 18 Feb '06

18 Feb '06

Last notes of the day... Matt 2006.02.14 Tools BOF Todd Underwood, panel moderator A number of interesting tools presented earlier today; all of them are good and interesting and solve a particular set of problems. None are in widespread use. There's a lot of possible reasons; do they solve problems you don't have, in which case they can move onto something new; or they solve a problem similar to one you have, but not quite. Or they solve a problem you can't quite implement yet. Discuss use cases, problems they're trying to solve, and give feedback, as interactively as comfortably as people can. 3 tools, OpenBGPD, IRR powertools/webtools (to get feedback and is the IRR even useful anymore?) and Flamingo as one of 2 netflow platforms. Start with Henning, active in open source software development; he'll go in more depth on openbgpd. OpenBGPD Henning Brauer henning at openbsd.org 3 process design Principle of least privilege the RDE (route decision engine) does not need any special priv at all, so it runs as __bgpd:__bgpd: chrooted to /var/empty SE needs to bind to TCP/179 parent needs to modify kernel routing table. Session Engine (SE) needs to bind to 179/tcp we have the parent open sockets see recvmsg(2) parent needsd to keep track of which fds the SE has open, so it doesn't bind() again to same ip/port the SE can drop all privs, then. SE 2 since one process handles all bgpd, need nonblocking sockets. on blocking, you call write(2), won't reurn until it's done or get errors on nonblocking, returns as soon as it can't proceed immediately So, have to handle buffer managmeent SE 3 designed an easy to use buffer API and mesg handling system. Messaging internal messaging is core comp. in reused for OpenNTPD, OPenOSPFD, and somee more. bgpd has more than 52 message types, more than OpenSSH bgpctl talks to bgpd using same imsg socket tcp md5 some very old code in kernel for tcp md5, from 4.4 BSD never worked tcp md5 is somewhat similar to ipsec, ah, so implement it within IPSec maze. Had to add pfkey interface to bgpd; committee designed API. that made IPSec that much easier; extended the API so they can request unused SPIs from kernel, don't have to be configured manually. tcp md5/ipsec when you don't have tcp md5 or ipsec in place, big tcp windows are risky stay at 16k window unless you have tcp md5 or ipsec, then you get 64K so ipsec improves performance. Joel Yagli asks how big a tcp window do you need for a BGP session at all? initial connection gets faster with 64K, but thereafter, similar. looking glass just added an optional second control socket that is restricted to the "show" operations regular bgpctl binary can be used with it cgi, yeah, that needs to be hacked in shape, but it's easy. Juniper only does static IPSec setup, so requires nasty setup. OpenBGPD is dynamic, but interoperates with Junipers. So back to looking glass, security on OpenBSD, the httpd (an apache 1.3 variant) runs in a chroot jail by default th readonly socket can be placed inside that jail bgpd_flags="-r /var/www/bgpd.rsock" in rc.conf.local put a statically linked bgpctl binary in the chroot /path/to/bgpctl -s /bgp.rsock, $ impressions from road to ipv6 most heinous checkin message yet. The lower 2 bytes of the scopeID overwrite part of the v6 address...ugly! Performance http://hasso.linux.ee/linux/openbgpd.php it's quick openBGPD 3.6 port for linux; can't communicate with kernel, no v6, no md5; 8 times faster than quagga. future plans and ideas the biggest task waits outside bgpd itself; kernel routing table. we need to make use of the radix mpath capabilities added in 2004, and add route source markers (BGP, OSPF, etc) bgpd and ospfd can blindly install their routes kernel then knows precedence hard to do, once it's done, routing will be easier. Also need multiple routing tables, with pf acting as table selector so unholy route-to can died, and associated issues vanish/ might be useful with bgpd as well. iddeas for quite radical changs, speed up packet forwarding dramatically. will have fast path where all easy cases can be handled on specialized PCI cards multiple 10GE at wire speed within 2 years. hardware exists, on way to him. for route servers, reversing filter and best path selection would be good. filter generation from RIPE DB or similar but IRR toolset sucks hairy moose balls should be solvable in perl "someone" has to code it. (maybe use IRR power tools for it instead!) [ we can fail over IP addresses already, thanks to CARP we can hve synchronized state tables on multiiple machines, gives HA firewall clusters. Would be really cool to be able to fail over TCP sessions and bgp sessions. could make for BGP hitless failover syncging BGP stuff shouldn't be too hard lots of work, not much time. Money has to come from somewhere, obviously. Unfortunately, people forget about this, just go to mirrors. Vendors don't help Never got anything for OpenSSH yet it comes down to you. yes YOU. buy our CDs, donate cash, tee-shirts, etc. or sponsor events, plane tickets, etc. Matt asks if they can be configured actively only, not binding on port 179. Currently, no. Can bind to loopbacks for the moment, or modify the code as appropriate. RAS asks if they support the lastest IETF draft for collision handling. They don't implement collision detection RFC-wise, no. And they're not active only, without passive. He also asks about comparing a RIB-in; that's been in the code for 2 weeks now, still has some bugs. Add support for passing more than one best path in case people are using this for a looking-glass. ie the VRF style hack for getting multiple views of the same route. Todd asks if they log dump output in MRT format. Short answer, yes. Many thanks to Henning! OK, over to RAS for IRR power tools. One leading question is whether the IRRs are even worthy of supporting, or are they a dead horse we've been flagellating for ten years? Todd kicks it off with question--you developed toolset because you think IRRs are a worthy effort to support, right? RAS notes that manual filters aren't a reasonable means to configure routers. Our current system is broken, something needs to change. Tool was written for internal use initially, Chris Morrow convinced him to release it for others. Not really meant as a plug for the IRRs, it's more "if you're going to use the IRRs Riverdomain, package base, if it can be a .rpm or .deb package, it would help; RAS doesn't do Linux, but others are welcome to package it up. When people go to implement this, they find a lot of cruft lurking around. Verio is the primary forcer right now for using IRRs; Level3 proxy objects are a great pain point. No motivation to remove old information out of the system. Larry Blunt with Merit; if you send email to them, they will remove old stale objects. It may take a little while, but it will get done. They're starting to check for inconsistencies so you can do bulk deletions of blocks that aren't being announced. Could they send out a monthly nag message, send that initially. They charge a yearly fee. When someone doesn't pay, companies will eventually be phased out. About 1600 maintainers, some are proactive about keeping them up to date, others are pretty minimal or are laggards. Website will show out-of-date info, but won't allow cleaning it up; next step is to allow them to clean it up via the web. They're looking to have a simple form vs complex form coming up, for those who don't have a complete understanding of BGP. Report section works across all registries. Could check to see if there's a less specific entry already with a different MAINT-ID. What about an INET-num to block any more specifics from the block from being registered. Challenge centers around the split between IP allocation and route registration. Peter Shoenmaker, works for Verio; many people mirror other databases, so there's compounded stale data. There are certain companies that have large blocks, and they'll register all the more specifics under it as well. Generating those filter lists gets ugly. RAS notes his tool auto-aggregates to least specific block possible. Samantha Billington, ISC, current maintainers of the current IRR ToolSet; would love to re-do it if there were some backing behind it. Currently trying to develop peering tools to make keeping track of peerings more easily. Randy Bush, IIJ, peers at the SIX using a perl script to generate filter lists around peval; it's a decade later, and we're still hacking more tools on top of the same broken data. It's time to do something new; doing the same thing, and expecting different outcome is definition of insanity. He says let's just give up, and change. Todd asks about SBGP/SO-BGP; they haven't caught on, and perhaps never well. But in the meantime, Randy notes it will let you build filters that are at least rigorously verifiable. And it'll be a backend only change in the future to drop in for the IRR in the future. It'll be downhill, incremental work at that point. Randy doesn't think it makes sense to continue forward at all. Let's stop for a year and redo things on better course before another ten years goes past. Randy offers to show Todd his ass...the audience groans, and we return to a more serious note. This is quicksand, let's get out of the quicksand. it's just an issue of going in the wrong direction. If you don't mind doing work twice, OK; but if you do, then save your time and energy, and let's focus on a PKI system. So, let's do PKI now, and we add this into the tools to jump start the process. You get a list of signed objects, you traverse the list of signed attestations that you recieve, you verify up the chain to IANA, and verify that the chain is intact. For Addresses and ASes, IANA is the root. For the identities of the ISPs and RIRs, may not be a single root. IRRs aren't secure enough to use for the database system. It's not transport free? LDAP would very likely be the storage/retrieval system. Let's start coding it; 2585 for queries, it's over HTTP, lets you talk to PKI certificate abstraction. Need to cover changes to certs needed to cover address space and ASNs. Can 2585 cover certificte modification, though? Needs Andy Putnams, Intelliden, config challenge will exist regardless of the pki; how do you ensure that you don't have multiple, overlapping entries? RAS notes that if we could handle PKI inside the IRRR, it would jumpstart the data. Chris asks why we can't start doing verifications with the existing infrastructure? Randy's not saying throw away the existing infrastructure; just pause on chasing it down, and change direction for the future. RPSL is a huge overkill, 90% of it isn't used at all, would we want to put PKI in there? Sandy Murphy, Sparta. Could we use the PKI to prevent people from adding or removing routes that we don't want touched? Could the people RUNNING the IRR check before you stick it in; then we also check on the way out. RFC 2725--her name is on it, but it's really Curtis Villamizer's proposal, but it does allow for the web of trust between systems to start with. Now onto Flamingo; Manish will walk through a live demo off his netflow data. flamingo.merit.edu:4444 it's more for security than traffic engineering; for those of us doing traffic engineering, though might still be of some use. Gives a large overview when we start it up, use the minimum threshold to filter out background noise. Traffic volume based on source AS view is of somewhat interesting. Ooops, neighbor AS, actually. (or origin, depending on your router setting) quad tree works same for AS number, just 16 bit number, not 32 bit archive. collector is based off flow tools, uses similar file format. Can pause updates so you don't loose current data you're about to zoom in on, for example. last view is combined source, dest, port, etc. everything sampled by netflow all in one window. sliders are a little crude, would be nice to have text entry boxes as well as slider bars. You can also list specific networks you care about that you want to see data for. So you can see traffic sourced from a given subnet. Every bar will then be a /32 hostname, will show traffic volumes for each; can shift zoom to limit what is on the display. Can do same visualizations of darknet space. They generate darkspace network off an unnumbered interface, and generating flow data from what is seen on the scatterback. Lots of scans from lots of people. Last 10 seconds or last 2 seconds, very dynamic. so the vertical here is walking across ports. single source port hitting lots of destination ports. Can also playback feeds from netflow collector format, etc. The platform is displaying pretty well at about 5k records/second, but scaling up for for a large content provider would be tough. Most of the code is written in-house, on Linux; may port to other platforms later. Running on a 3.6ghz p4 right now, nice graphics card, 256MB nvidia graphics card, no other real specs right now. Heavy dependencies on openGL, so no licensing for that. Software tool is largely GPL free. Availability is an issue right now. In trials, happy to do more trials, that's where they'll leave it for now. Manpower issues, no QA, no support, so not sure if they can really release it to the public yet. Are there additional visualizations that might help? On the ops side, which of these ways of looking at this would help the poor folks who run NOCs? What about saving profiles the NOC can compare against to recognize quickly "bad things". Mike Hughes (I think) says it's not really a first-alert type tool, it's for a second or third level escalation tool; too hard to interpret for a front line NOC person. They find it most useful for playback, rather than realtime 'spot the attack'. Chris--scaling for netflow is always a challenge. He has 9 routers reporting 50,000 flows/second; he has 300 others to add. So the scaling part is a challenge. The SOC might find it useful. It can use pre-existing netflow/flowtool archive files, server can play those back. Chris Morrow would just like to see some rough stats on what it could support. Mike Hughes, runs layer 2 environment, could it be sFlow and layer 2 aware. Walt Prue asks if he could point at a line to see info about it. On the feature list.

2 1

Exchange Points
by sjk 18 Feb '06

18 Feb '06

We're a small facilities based ISP in Chicago and I am looking for a public exchange point for peering. I have been told, by someone at SBC, that the public NAP here is no longer accepting connections and is essentially going to shut down over time. Has anyone else heard this? Are there other exchange options - other then to haul transport to multiple net operators? Thanks -- Steve

3 2

Disaster recovery using as-prepend?
by Christopher J. Pilkington 18 Feb '06

18 Feb '06

My apologies if this question doesn't belong here. We have a PI /24 we'd like to advertise out of our primary data center for production use. (Well, actually, we'll be advertising a more specific from our /21 assignment, so already not too friendly... but I digress.) We have a disaster recovery site which will have a clone of the myriad production servers. We'd like to fail over to that site automagically. I'm thinking advertising the same prefix and just doing several as-prepends. However, now I'm not sure if this is a polite thing to do or not. Someone mentioned to me something with MEDs, but as soon as that term was used, I started twitching, and couldn't follow the conversation. Would a "good netizen" use the as-prepend method? Or am I missing a simpler/more polite solution? -Christopher

7 10

[operational update] Looking behind the smoke screen of the Internet
by Gadi Evron 18 Feb '06

18 Feb '06

You can find the information and update here: http://blogs.securiteam.com/index.php/archives/298 Apparently nanog drops email messages with long subject lines. Thanks, Gadi. -- http://blogs.securiteam.com/ "Out of the box is where I live". -- Cara "Starbuck" Thrace, Battlestar Galactica.

1 0

RE: MLPPP over MPLS
by Erik Amundson 17 Feb '06

17 Feb '06

I've used MLPPP before with T1s...not the hardest thing to do...in fact, MLFR is a little bigt nastier, but still nothing that the average CCNA couldn't wrap their brain around... Erik Amundson -----Original Message----- From: owner-nanog(a)merit.edu [mailto:owner-nanog@merit.edu] On Behalf Of Jon R. Kibler Sent: Friday, February 17, 2006 1:37 PM To: nanog(a)merit.net Subject: MLPPP over MPLS Greetings all, Would anyone who has every done MLPPP over MPLS care to share their experiences with this type of network? We have a customer that is implementing an MPLS network that will have 2 to 6 T1 feeds at some locations that will be using MLPPP for channel bonding. This is a telco provided network that will be customer managed. The routers will be customer managed because the same equipment will have interfaces to another telco's network as a backup to the MPLS network. Needless to say, no telco will support equipment that interfaces competitors networks. The customer is being told by their router vendor that an MLPPP/MPLS network is 'too complex' to be managed by anyone except for the router vendor's VARs or the telco. They indicated that it would be impossible for the customer's router vendor certified network person to come up to speed on MLPPP/MPLS configurations and manage such a network -- that it takes years to adequately learn how to manage that type of network configuration. This doesn't sound like rocket science to me -- it should be simple and rather straight forward, I would think: The telco specifies its requirements for the router configuration, the customer implements that configuration on the required router interfaces, the telco monitors line quality, and the customer does basic router monitoring. Am I missing something here, or is the router vendor just blowing a lot of smoke to try to provide business for some of his clients that provide managed services? Thanks in advance for your feedback! Jon Kibler -- Jon R. Kibler Chief Technical Officer A.S.E.T., Inc. Charleston, SC USA (843) 849-8214 ================================================== Filtered by: TRUSTEM.COM's Email Filtering Service http://www.trustem.com/ No Spam. No Viruses. Just Good Clean Email.

1 0

Peering BOF XI Meeting Minutes ----- D R A F T
by William B. Norton 17 Feb '06

17 Feb '06

Peering BOF XI Meeting Minutes Facilitator: William B. Norton <wbn(a)equinix.com> Agenda 1. Notes from the Field - wbn 2. ad Hoc Transit Survey – Dave Wodelet 3. Paid Peering as an Adjunct to Settlement Free Interconnect (15 min). -wbn 4. The Great Peering Debate (30 min) ras, ianai 5. Peering Contact Database (peeringdb.com) Update (10 min). - ras 6. AS7018 & AS7132 Discussion (15 min) 7. Peering Personals – all (remainder) 1) Notes from the Field Trying something new this NANOG Peering BOF: Community Seating This was a hit! We had 200 chairs arranged in three concentric ovals so everyone could see everyone else. The protocol for speaking did not involve queueing up at a microphone but rather standing up and speaking your peace. It took a little while to get used to it but it certainly facilitated very interactive and lively community discussions. Peering Ecosystems Update – Italy Peering Ecosystem Exception Telecom Italia peers its domestic routes openly in a single (or if needed two) location in Italy. This is counter to every peering ecosystem I have studied; Tier 1 ISPs (those with access to the entire routing table for the country solely via peering relationships) typically will not peer with anyone else, making Telecom Italia and Italy an interesting exception. Daniele (from NaMex) pointed out the recently privatized Telecom Italia peered openly to avoid government regulation, and I mentioned that they also pointed to increased revenue from fiber and copper sales to successful competitive ISPs. Note that this is a different entity from Telecom Italia Sparkle, which is the sole international transit provider for TI and does not peer openly. Job (from AMS-IX) mentioned that KPN is similarly openly peering. - Past Peering Debate documented The last NANOG Peering Ratios debate spilled over into heated discussions in the hallways and I went ahead and documented the strongest arguments overheard on both sides of the issue. I have this white paper available to anyone who wishes to better understand the Peering Ratios issue. This white paper is now freely available. Send email to bill.norton(a)gmail.com with "The Folly of Peering Ratios?" in the subject line and I'll be glad to send a copy of the "The Folly of Peering Ratios?" white paper. 2) Ad Hoc Transit Survey – Dave Wodelet (dave.wodelet(a)sjrb.ca) Dave was interested in continuing the transit survey we have done in the past peering bofs with a little more specificity, so he asked several questions: a) who are your upstream transit providers? b) what are the prices per mbps and commits? c) how old is the contract? d) are there any special aspects of the deal? Dave agreed to report back on the results at the next NANOG Peering BOF. 3) Top 8 reasons Paid Peering Has Not Taken Off The Peering community has discussed paid peering for over a decade. The question was floated around "Why hasn't paid peering taken off?" resulting in the following answers: 1. Unpredictability & Budgeting & Gaming the system 2. We are "peers" & we shouldn't pay. 3. If we pay now it will be harder to migrate to settlement free later 4. No Signatory Authority for $$$ - another group handles vendors/paying 5. Transit Price < Paid Peering Price – why bother, use communities to limit transit, have a backup just in case 6. We don't have that product to offer 7. Low margin product – the margins are already thin on transit, too much effort 8. I don't want to screw up my existing peering relationships. Even if I get some $$, I piss off a peer I care about. This was also a lively discussion resulting in a total of eight reasons when my hallway conversations initially resulted in five reasons why paid peering hasn't taken off. 4) "The Utility of MEDs" Peering Debate • Peering Question: "From a Practical Perspective, are MEDs useful for distributing the peering traffic load?" 2 minutes each: 1. "MEDs are not a useful tool for Peering" - ras 2. "MEDs are a useful tool for Peering" - patrick 3. Ras attacks "MEDs are a useful tool for Peering" position 4. Patrick attacks "MEDs are not a useful tool for Peering" position 5. Closing Arguments • Initial vote: How many people believe MEDs are a useful tool for distributing peering traffic? Group Answer by Vote: MEDs ARE useful. Debate begins... "MEDs are not a useful tool for Peering" - ras 1. MEDs worsen route quality and increase latency 2. Costs go up overall – just shifting costs around 3. Foolhardy to assume you can route to someone else's network better than they can "MEDs are a useful tool for Peering" - patrick 1. Judicious use of MEDs can improve performance 2. MEDs can remove the technical objections to peering 3. It's foolhardy to assume other people can route properly inside their own network. • Audience votes "Which side made the more compelling case" Group Answer: Patrick did - "MEDs are useful for Distributing Peering Load" • Audience added in points that were not made during the debate, or reinforce positions that you believe needed reinforcement. • Audience voted "Are MEDs a useful tool for Peering?" Group Answer: "MEDs are useful for Distributing Peering Load" 5) Peeringdb.com • Peering Contact Information goes out of date very quickly 7) Peering Personals • If you are a peering coordinator, stand up • If you are an IX, sit down • Look around the room • Point with two hands the people that you know the least We had a few folks stand up and introduce themselves, their ASN, their network, what they are looking for in a peer, and why the group should want to peer with them. 6) AS7018 & AS7132 Discussion With the merger of two of the largest peering companies in the U.S. Peering Ecosystem there are questions in the Peering Community about the near and medium term impacts. Ren Provo (AS7132) and Susan Martens (AS7018) stood up and announced the website for peering: http://www.att.com/peering/ and that things were pretty much business as usual now. -- //------------------------------------------------ // William B. Norton <wbn(a)equinix.com> // Co-Founder and Chief Technical Liaison, Equinix // GSM Mobile: 650-315-8635 // Skype, Y!IM: williambnorton

1 0

Re: Drone Army (how to contact)?
by infowolfe 17 Feb '06

17 Feb '06

No need anymore, I've already spoken with both Gadi and Randy on the matter that concerned me. Thanks, Allen On 2/17/06, Roland Dobbins <rdobbins(a)cisco.com> wrote: > > cc'ing Gadi. > > On Feb 17, 2006, at 2:10 AM, infowolfe wrote: > > > > > I'd really like to know how I can get ahold of the people that do the > > Drone Army reports, as I am a serveradmin on an irc network that was > > identified as being abusive. > > > > If you're responding as part of the Drone Army, please reply to me > > off list. > > > > Allen Parker > > ---------------------------------------------------------------------- > Roland Dobbins <rdobbins(a)cisco.com> // 408.527.6376 voice > > Everything has been said. But nobody listens. > > -- Roger Shattuck > >

1 0

Weekly Routing Table Report
by Routing Table Analysis 17 Feb '06

17 Feb '06

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 If you have any comments please contact Philip Smith <pfs(a)cisco.com>. Routing Table Report 04:00 +10GMT Sat 18 Feb, 2006 Analysis Summary ---------------- BGP routing table entries examined: 181818 Prefixes after maximum aggregation: 101253 Unique aggregates announced to Internet: 88390 Total ASes present in the Internet Routing Table: 21539 Origin-only ASes present in the Internet Routing Table: 18718 Origin ASes announcing only one prefix: 8901 Transit ASes present in the Internet Routing Table: 2821 Transit-only ASes present in the Internet Routing Table: 71 Average AS path length visible in the Internet Routing Table: 4.5 Max AS path length visible: 25 Prefixes from unregistered ASNs in the Routing Table: 8 Special use prefixes present in the Routing Table: 0 Prefixes being announced from unallocated address space: 12 Number of addresses announced to Internet: 1497414880 Equivalent to 89 /8s, 64 /16s and 188 /24s Percentage of available address space announced: 40.4 Percentage of allocated address space announced: 59.6 Percentage of available address space allocated: 67.8 Total number of prefixes smaller than registry allocations: 88714 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 38138 Total APNIC prefixes after maximum aggregation: 16214 Prefixes being announced from the APNIC address blocks: 35865 Unique aggregates announced from the APNIC address blocks: 17515 APNIC Region origin ASes present in the Internet Routing Table: 2471 APNIC Region origin ASes announcing only one prefix: 682 APNIC Region transit ASes present in the Internet Routing Table: 380 Average APNIC Region AS path length visible: 4.5 Max APNIC Region AS path length visible: 21 Number of APNIC addresses announced to Internet: 213143264 Equivalent to 12 /8s, 180 /16s and 78 /24s Percentage of available APNIC address space announced: 66.6 APNIC AS Blocks 4608-4864, 7467-7722, 9216-10239, 17408-18431 (pre-ERX allocations) 23552-24575, 37888-38911 APNIC Address Blocks 58/7, 60/7, 121/8, 122/7, 124/7, 126/8, 202/7 210/7, 218/7, 220/7 and 222/8 ARIN Region Analysis Summary ---------------------------- Prefixes being announced by ARIN Region ASes: 95582 Total ARIN prefixes after maximum aggregation: 56516 Prefixes being announced from the ARIN address blocks: 74869 Unique aggregates announced from the ARIN address blocks: 28469 ARIN Region origin ASes present in the Internet Routing Table: 10520 ARIN Region origin ASes announcing only one prefix: 3939 ARIN Region transit ASes present in the Internet Routing Table: 964 Average ARIN Region AS path length visible: 4.3 Max ARIN Region AS path length visible: 17 Number of ARIN addresses announced to Internet: 287630592 Equivalent to 17 /8s, 36 /16s and 229 /24s Percentage of available ARIN address space announced: 71.4 ARIN AS Blocks 1-1876, 1902-2042, 2044-2046, 2048-2106 (pre-ERX allocations) 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, 21504-23551, 25600-26591, 26624-27647, 29696-30719, 31744-33791 35840-36863 ARIN Address Blocks 24/8, 63/8, 64/6, 68/7, 70/6, 74/7, 76/8, 198/7, 204/6, 208/7 and 216/8 RIPE Region Analysis Summary ---------------------------- Prefixes being announced by RIPE Region ASes: 35923 Total RIPE prefixes after maximum aggregation: 24185 Prefixes being announced from the RIPE address blocks: 32944 Unique aggregates announced from the RIPE address blocks: 22224 RIPE Region origin ASes present in the Internet Routing Table: 7661 RIPE Region origin ASes announcing only one prefix: 4015 RIPE Region transit ASes present in the Internet Routing Table: 1289 Average RIPE Region AS path length visible: 5.0 Max RIPE Region AS path length visible: 19 Number of RIPE addresses announced to Internet: 236823424 Equivalent to 14 /8s, 29 /16s and 163 /24s Percentage of available RIPE address space announced: 70.6 RIPE AS Blocks 1877-1901, 2043, 2047, 2107-2136, 2585-2614 (pre-ERX allocations) 2773-2822, 2830-2879, 3154-3353, 5377-5631 6656-6911, 8192-9215, 12288-13311, 15360-16383 20480-21503, 24576-25599, 28672-29695 30720-31743, 33792-35839, 38912-39935 RIPE Address Blocks 62/8, 80/5, 88/6, 188/8, 193/8, 194/7, 212/7 and 217/8 LACNIC Region Analysis Summary ------------------------------ Prefixes being announced by LACNIC Region ASes: 10234 Total LACNIC prefixes after maximum aggregation: 3455 Prefixes being announced from the LACNIC address blocks: 8426 Unique aggregates announced from the LACNIC address blocks: 4988 LACNIC Region origin ASes present in the Internet Routing Table: 674 LACNIC Region origin ASes announcing only one prefix: 222 LACNIC Region transit ASes present in the Internet Routing Table: 120 Average LACNIC Region AS path length visible: 5.1 Max LACNIC Region AS path length visible: 25 Number of LACNIC addresses announced to Internet: 25451008 Equivalent to 1 /8s, 132 /16s and 90 /24s Percentage of available LACNIC address space announced: 37.9 LACNIC AS Blocks 26592-26623, 27648-28671, plus ERX transfers LACNIC Address Blocks 189/8, 190/8, 200/7 AfriNIC Region Analysis Summary ------------------------------- Prefixes being announced by AfriNIC Region ASes: 1928 Total AfriNIC prefixes after maximum aggregation: 883 Prefixes being announced from the AfriNIC address blocks: 1293 Unique aggregates announced from the AfriNIC address blocks: 886 AfriNIC Region origin ASes present in the Internet Routing Table: 147 AfriNIC Region origin ASes announcing only one prefix: 43 AfriNIC Region transit ASes present in the Internet Routing Table: 23 Average AfriNIC Region AS path length visible: 4.4 Max AfriNIC Region AS path length visible: 14 Number of AfriNIC addresses announced to Internet: 3779584 Equivalent to 0 /8s, 57 /16s and 172 /24s Percentage of available AfriNIC address space announced: 11.3 AfriNIC AS Blocks 36864-37887 & ERX transfers AfriNIC Address Blocks 41/8, 196/8 APNIC Region per AS prefix count summary ---------------------------------------- ASN No of nets /20 equiv MaxAgg Description 4134 996 6480 204 CHINANET-BACKBONE 9583 852 109 15 Sify Limited 4766 701 3927 301 Korea Telecom (KIX) 4755 665 255 61 Videsh Sanchar Nigam Ltd. Aut 1221 652 1428 468 Telstra Pty Ltd 9498 535 211 73 BHARTI BT INTERNET LTD. 7545 517 108 70 TPG Internet Pty Ltd 17488 515 31 7 Hathway IP Over Cable Interne 17676 480 6949 104 Softbank BB Corp. 9443 411 94 85 Primus Telecommunications 4802 367 75 159 Wantree Development 2907 341 1763 318 SINET Japan 9929 331 218 50 China Netcom Corp. 18101 326 68 26 Reliance Infocom Ltd Internet 17974 321 77 38 PT TELEKOMUNIKASI INDONESIA 17557 316 25 162 Pakistan Telecom 7474 298 211 230 SingTel Optus Pty Ltd 4780 281 226 16 Digital United Inc. 9837 272 78 168 Powertel Ltd 9800 260 410 67 CHINA UNICOM ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 7018 1467 6263 948 AT&T WorldNet Services 4323 1208 711 235 Time Warner Telecom 721 993 21921 302 DLA Systems Automation Center 174 986 5787 928 Cogent Communications 6197 985 458 511 BellSouth Network Solutions, 701 957 8065 792 UUNET Technologies, Inc. 18566 909 272 8 Covad Communications 2386 888 505 664 AT&T Data Communications Serv 1239 847 2790 607 Sprint 19029 701 152 115 New Edge Networks 209 693 3607 542 Qwest 20115 664 582 356 Charter Communications 6198 652 449 238 BellSouth Network Solutions, 22773 632 1480 40 Cox Communications, Inc. 11492 628 81 12 Cable One 19262 628 1831 156 Verizon Global Networks 852 572 1088 380 Telus Advanced Communications 855 571 244 64 Canadian Research Network 19916 563 49 54 OLM LLC 3602 522 127 106 Sprint Canada, Inc. RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 702 586 1952 462 UUNET - Commercial IP service 3301 305 1071 290 TeliaNet Sweden 3352 303 1500 30 Ibernet, Internet Access Netw 3320 281 3477 235 Deutsche Telekom AG 8220 274 474 268 COLT Telecommunications 680 243 2025 240 DFN-IP service G-WiN 3246 229 487 219 Song Networks 6746 224 86 196 Dynamic Network Technologies, 8708 223 274 206 Romania Data Systems S.A. 1257 204 712 173 SWIPnet Swedish IP Network 8551 187 181 25 Bezeq International 3269 186 1925 70 TELECOM ITALIA 5515 176 839 124 Sonera Solution Autonomous Sy 3215 174 1438 85 France Telecom Transpac 786 173 1794 173 The JANET IP Service 8866 171 37 12 Bulgarian Telecommunication C 24863 169 38 9 LINKdotNET AS number 3300 166 171 94 AUCS Communications Services 5400 166 328 135 BT Ignite European Backbone 6830 163 733 34 UPC Distribution Services LACNIC Region per AS prefix count summary ----------------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 578 1051 219 UniNet S.A. de C.V. 22047 383 142 10 VTR PUNTO NET S.A. 11172 303 110 77 Servicios Alestra S.A de C.V 16814 295 18 7 NSS, S.A. 14117 184 11 6 Telefonica del Sur S.A. 7303 157 74 18 Telecom Argentina Stet-France 6147 154 126 22 Telefonica Del Peru 11556 130 64 3 Cable-Wireless Panama 19169 123 8 30 Telconet 10481 121 48 8 Prima S.A. 21826 116 15 19 INTERCABLE 6503 114 149 81 AVANTEL, S.A. 5639 113 12 9 Telecommunications Services o 6505 108 88 80 Global One Communicaoes Ltda 23216 105 23 10 RAMtelecom Telecomunicaciones 18822 99 8 10 TELEFONICA MANQUEHUE 25620 99 6 3 COTAS LTDA 7315 96 6 3 Grupo Rey Moreno 14522 96 12 8 SatNet S.A. 11311 95 8 23 Sinectis S.A. AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 3741 278 819 234 The Internet Solution 8452 164 60 7 TEDATA 5536 122 8 16 Internet Egypt Network 2018 117 298 103 Tertiary Education Network 6713 105 103 12 Itissalat Al-MAGHRIB 15475 103 84 4 Nile Online 2905 74 155 67 The Internetworking Company o 24835 60 50 7 RAYA Telecom - Egypt 20928 58 16 2 Noor Advanced Technologies AS 5713 39 294 35 Telkom SA Ltd 15706 31 8 3 Sudatel Internet Exchange Aut 33774 30 7 21 AS Number for Telecom Algeria 12455 27 6 3 Jambonet Autonomous system 23889 26 8 11 MAURITIUS TELECOM 8524 24 1 4 AUCEGYPT Autonomous System 16637 23 10 21 Johnnic e-Ventures 10798 22 1 13 Standard Bank of South Africa 8346 21 14 18 SONATEL-AS Autonomous System 15804 17 2 1 AS of The Way Out Internet So 15808 17 2 2 Communication Solutions Ltd i Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 4323 1208 973 Time Warner Telecom 18566 909 901 Covad Communications 9583 852 837 Sify Limited 4134 996 792 CHINANET-BACKBONE 721 993 691 DLA Systems Automation Center 11492 628 616 Cable One 4755 665 604 Videsh Sanchar Nigam Ltd. Aut 22773 632 592 Cox Communications, Inc. 19029 701 586 New Edge Networks 19916 563 509 OLM LLC 17488 515 508 Hathway IP Over Cable Interne 855 571 507 Canadian Research Network 5668 517 492 CenturyTel Internet Holdings, 6197 985 474 BellSouth Network Solutions, 19262 628 472 Verizon Global Networks 9498 535 462 BHARTI BT INTERNET LTD. 7545 517 447 TPG Internet Pty Ltd 7757 462 443 AT&T Broadband 3602 522 416 Sprint Canada, Inc. 6198 652 414 BellSouth Network Solutions, List of Unregistered ASNs (Global) ---------------------------------- Bad AS Designation Network Transit AS Description 33364 UNALLOCATED 65.111.76.0/24 7018 AT&T WorldNet Servic 65211 PRIVATE 125.64.3.0/24 4134 CHINANET-BACKBONE 65005 PRIVATE 159.153.148.0/22 24989 IX Europe Frankfurt 65202 PRIVATE 195.47.234.0/24 23649 New Skies Satellites 65505 PRIVATE 206.252.200.192/27 8002 Stealth Communicatio 65518 PRIVATE 211.144.192.0/19 24421 * 64512 PRIVATE 218.108.0.0/16 24139 HANGZHOU DIGITAL TV 64512 PRIVATE 218.109.0.0/16 24139 HANGZHOU DIGITAL TV Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 132.0.0.0/10 721 DLA Systems Automation Center 137.0.0.0/13 721 DLA Systems Automation Center 158.0.0.0/13 721 DLA Systems Automation Center 192.43.230.0/24 7575 Australian Academic and Rease 192.44.0.0/24 5501 Fraunhofer Gesellschaft 192.44.0.0/19 702 UUNET - Commercial IP service 192.70.164.0/24 25689 National Research Council of 192.72.0.0/18 4780 Digital United Inc. 192.72.0.0/16 4780 Digital United Inc. 192.84.205.0/24 719 LANLINK autonomous system 192.119.135.0/24 270 NASA 192.172.0.0/19 721 DLA Systems Automation Center Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:18 /9:9 /10:8 /11:23 /12:87 /13:200 /14:350 /15:695 /16:8716 /17:3081 /18:5100 /19:11307 /20:12612 /21:10851 /22:13891 /23:15052 /24:98843 /25:353 /26:264 /27:201 /28:58 /29:24 /30:32 /31:3 /32:40 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 18566 892 909 Covad Communications 6197 789 985 BellSouth Network Solutions, 7018 750 1467 AT&T WorldNet Services 9583 672 852 Sify Limited 19029 623 701 New Edge Networks 11492 620 628 Cable One 2386 617 888 AT&T Data Communications Serv 4323 584 1208 Time Warner Telecom 19916 557 563 OLM LLC 6198 517 652 BellSouth Network Solutions, 4766 506 701 Korea Telecom (KIX) 7011 446 516 Citizens Utilities 7757 444 462 AT&T Broadband 855 443 571 Canadian Research Network 5668 402 517 CenturyTel Internet Holdings, 702 371 586 UUNET - Commercial IP service 1239 368 847 Sprint 15270 348 378 PaeTec.net -a division of Pae 6517 340 369 Yipes Communications, Inc. 22773 331 632 Cox Communications, Inc. Number of /24s announced per /8 block (Global) ---------------------------------------------- 4:3 8:40 12:1634 13:1 15:12 16:3 17:3 18:4 20:44 24:859 25:1 30:2 32:67 38:196 40:54 44:3 47:3 52:4 55:1 56:3 57:33 58:119 59:163 60:181 61:803 62:762 63:1903 64:3003 65:2240 66:3053 67:594 68:675 69:1433 70:310 71:50 72:618 73:23 74:6 80:750 81:584 82:516 83:370 84:347 85:444 86:312 87:169 88:22 89:31 124:19 125:267 128:152 129:174 130:106 131:313 132:32 133:7 134:146 135:47 136:168 137:60 138:191 139:87 140:475 141:133 142:413 143:144 144:223 145:38 146:304 147:133 148:327 149:185 150:113 151:75 152:61 153:103 154:6 155:184 156:96 157:123 158:158 159:180 160:87 161:68 162:220 163:143 164:167 165:201 166:147 167:235 168:470 169:140 170:321 171:12 172:1 190:30 192:5745 193:3392 194:2511 195:1774 196:762 198:3895 199:3240 200:4169 201:603 202:6425 203:6754 204:3885 205:2092 206:2410 207:2911 208:1992 209:3759 210:1944 211:823 212:1271 213:1474 214:332 215:41 216:4005 217:1172 218:239 219:145 220:642 221:346 222:154 End of report

1 0

metric 0 vs 'no metric at all'
by Alexander Koch 17 Feb '06

17 Feb '06

Hiya, I was wondering if someone had done any or some research on this before... basically I am not sure with all the many implementations of BGP and all the vendors if and what those will do when they see a metric of 0 and no metric. I am not an expert knowing the actual protocol's messages exchanged, but I see some routes with nothing in the metric field on the various show commands, and some have explicit '0' metric. I do not trust all the BGP implementations around, and we consider changing the default outbound, with MEDs of course still available on request. Alexander

6 5

The Cidr Report
by cidr-report＠potaroo.net 17 Feb '06

17 Feb '06

This report has been generated at Fri Feb 17 21:46:53 2006 AEST. The report analyses the BGP Routing Table of an AS4637 (Reach) router and generates a report on aggregation potential within the table. Check http://www.cidr-report.org/as4637 for a current version of this report. Recent Table History Date Prefixes CIDR Agg 10-02-06 177853 117660 11-02-06 177886 117658 12-02-06 178120 117757 13-02-06 178249 117785 14-02-06 178232 117883 15-02-06 178454 117890 16-02-06 178290 117967 17-02-06 178434 117952 AS Summary 21444 Number of ASes in routing system 8908 Number of ASes announcing only one prefix 1456 Largest number of prefixes announced by an AS AS7018 : ATT-INTERNET4 - AT&T WorldNet Services 91308800 Largest address span announced by an AS (/32s) AS721 : DLA-ASNBLOCK-AS - DoD Network Information Center Aggregation Summary The algorithm used in this report proposes aggregation only when there is a precise match using the AS path, so as to preserve traffic transit policies. Aggregation is also proposed across non-advertised address space ('holes'). --- 17Feb06 --- ASnum NetsNow NetsAggr NetGain % Gain Description Table 178505 117983 60522 33.9% All ASes AS4323 1204 239 965 80.1% TWTC - Time Warner Telecom AS18566 909 9 900 99.0% COVAD - Covad Communications Co. AS4134 978 251 727 74.3% CHINANET-BACKBONE No.31,Jin-rong Street AS721 1020 312 708 69.4% DLA-ASNBLOCK-AS - DoD Network Information Center AS22773 629 48 581 92.4% CCINET-2 - Cox Communications Inc. AS6197 994 477 517 52.0% BATI-ATL - BellSouth Network Solutions, Inc AS7018 1456 948 508 34.9% ATT-INTERNET4 - AT&T WorldNet Services AS855 571 64 507 88.8% CANET-ASN-4 - Aliant Telecom AS19916 563 65 498 88.5% ASTRUM-0001 - OLM LLC AS7757 462 19 443 95.9% CCCH-AS4 - Comcast Cable Communications Holdings, Inc AS17488 515 86 429 83.3% HATHWAY-NET-AP Hathway IP Over Cable Internet AS3602 522 106 416 79.7% AS3602-RTI - Rogers Telecom Inc. AS812 438 28 410 93.6% ROGERS-CABLE - Rogers Cable Inc. AS6198 651 243 408 62.7% BATI-MIA - BellSouth Network Solutions, Inc AS9498 534 129 405 75.8% BBIL-AP BHARTI BT INTERNET LTD. AS17676 480 104 376 78.3% JPNIC-JP-ASN-BLOCK Japan Network Information Center AS11492 628 263 365 58.1% CABLEONE - CABLE ONE AS4766 666 303 363 54.5% KIXS-AS-KR Korea Telecom AS6467 394 52 342 86.8% ESPIRECOMM - e.spire Communications, Inc. AS15270 372 31 341 91.7% AS-PAETEC-NET - PaeTec.net -a division of PaeTecCommunications, Inc. AS4755 662 330 332 50.2% VSNL-AS Videsh Sanchar Nigam Ltd. Autonomous System AS22047 383 60 323 84.3% VTR BANDA ANCHA S.A. AS18101 326 34 292 89.6% RIL-IDC Reliance Infocom Ltd Internet Data Centre, AS14654 300 14 286 95.3% WAYPORT - Wayport AS3352 303 30 273 90.1% TELEFONICA-DATA-ESPANA Internet Access Network of TDE AS6167 339 67 272 80.2% CELLCO-PART - Cellco Partnership AS9583 852 583 269 31.6% SIFY-AS-IN Sify Limited AS5668 516 249 267 51.7% AS-5668 - CenturyTel Internet Holdings, Inc. AS9929 320 57 263 82.2% CNCNET-CN China Netcom Corp. AS16814 295 54 241 81.7% NSS S.A. Total 18282 5255 13027 71.3% Top 30 total Possible Bogus Routes 24.246.0.0/17 AS7018 ATT-INTERNET4 - AT&T WorldNet Services 24.246.128.0/18 AS7018 ATT-INTERNET4 - AT&T WorldNet Services 64.17.32.0/24 AS13488 CBWU-13488 - Continental Broadband Florida, Inc DBA WebUnited 64.17.33.0/24 AS13488 CBWU-13488 - Continental Broadband Florida, Inc DBA WebUnited 64.17.37.0/24 AS13488 CBWU-13488 - Continental Broadband Florida, Inc DBA WebUnited 64.25.224.0/20 AS12180 INTERNAP-2BLK - Internap Network Services 64.25.224.0/22 AS15083 INFOLINK-MIA-US - Infolink Information Services Inc. 64.38.96.0/19 AS19654 HOSTING-NETWORK - HOSTING-NETWORK, INC. 64.127.128.0/17 AS19654 HOSTING-NETWORK - HOSTING-NETWORK, INC. 66.11.32.0/20 AS6261 VISINET - Visionary Systems, Inc. 66.37.96.0/20 AS3764 IA-HOU-AS - Internet America, Inc. 66.51.134.0/24 AS29876 LNTC - Latency LLC 66.96.0.0/20 AS3770 WORLDPATH-AS - WorldPath Internet Services 66.117.0.0/19 AS33104 FUZION-COLO - FUZION COLO 66.117.0.0/21 AS30033 NHI-NETWORKS - NHI Networks 66.117.8.0/24 AS174 COGENT Cogent/PSI 66.117.23.0/24 AS31972 EMGINECONCEPT-01 - Emagine Concept, Inc. 66.117.25.0/24 AS31972 EMGINECONCEPT-01 - Emagine Concept, Inc. 66.117.26.0/24 AS31972 EMGINECONCEPT-01 - Emagine Concept, Inc. 66.117.27.0/24 AS31972 EMGINECONCEPT-01 - Emagine Concept, Inc. 66.186.192.0/19 AS19654 HOSTING-NETWORK - HOSTING-NETWORK, INC. 66.187.96.0/24 AS10026 ANC Asia Netcom Corporation 66.187.108.0/24 AS10026 ANC Asia Netcom Corporation 66.187.109.0/24 AS10026 ANC Asia Netcom Corporation 66.216.0.0/18 AS19654 HOSTING-NETWORK - HOSTING-NETWORK, INC. 66.235.158.0/23 AS7018 ATT-INTERNET4 - AT&T WorldNet Services 69.31.151.0/24 AS26627 AS-PILOSOFT - Pilosoft, Inc. 69.39.193.0/24 AS25973 MZIMA - Mzima Networks, Inc. 69.39.195.0/24 AS25973 MZIMA - Mzima Networks, Inc. 69.39.196.0/24 AS25973 MZIMA - Mzima Networks, Inc. 83.175.128.0/20 AS12968 CDP Crowley Data Poland, sp. z o.o. 85.129.3.0/24 AS14585 CIFNET - CIFNet, Inc. 85.129.4.0/24 AS14585 CIFNET - CIFNet, Inc. 90.192.0.0/16 AS12654 RIPE-NCC-RIS-AS RIPE NCC RIS Project. 90.255.248.0/21 AS12654 RIPE-NCC-RIS-AS RIPE NCC RIS Project. 91.192.0.0/16 AS12654 RIPE-NCC-RIS-AS RIPE NCC RIS Project. 91.255.248.0/21 AS12654 RIPE-NCC-RIS-AS RIPE NCC RIS Project. 125.213.0.0/16 AS4134 CHINANET-BACKBONE No.31,Jin-rong Street 131.64.0.0/12 AS721 DLA-ASNBLOCK-AS - DoD Network Information Center 132.0.0.0/10 AS721 DLA-ASNBLOCK-AS - DoD Network Information Center 137.0.0.0/13 AS721 DLA-ASNBLOCK-AS - DoD Network Information Center 138.136.0.0/13 AS721 DLA-ASNBLOCK-AS - DoD Network Information Center 151.135.0.0/16 AS4763 TELSTRANZ-AS TelstraClear Ltd 158.0.0.0/13 AS721 DLA-ASNBLOCK-AS - DoD Network Information Center 163.142.0.0/16 AS2500 JPNIC-ASBLOCK-AP JPNIC 192.30.93.0/24 AS17757 HPAUS-AP HP Australia 192.30.94.0/24 AS17757 HPAUS-AP HP Australia 192.40.105.0/24 AS5515 SONERA-GLOBAL-IP Sonera Solution Autonomous System 192.43.230.0/24 AS7575 AARNET-AS-AP Australian Academic and Reasearch Network (AARNet) 192.44.0.0/19 AS702 AS702 MCI EMEA - Commercial IP service provider in Europe 192.44.0.0/24 AS5501 FRAUNHOFER-CLUSTER-BW Fraunhofer Gesellschaft 192.70.164.0/24 AS25689 NRCNET-AS - National Research Council of Canada 192.72.0.0/16 AS4780 SEEDNET Digital United Inc. 192.72.0.0/18 AS4780 SEEDNET Digital United Inc. 192.72.192.0/18 AS4780 SEEDNET Digital United Inc. 192.81.183.0/24 AS719 ELISA-AS Elisa Oyj 192.81.184.0/24 AS719 ELISA-AS Elisa Oyj 192.88.99.0/24 AS559 SWITCH SWITCH, Swiss Education and Research Network 192.96.36.0/24 AS5713 AFRINIC African Network Information Center 192.96.37.0/24 AS10474 AFRINIC African Network Information Center 192.96.135.0/24 AS2018 TENET - 1 - The Uninet Project 192.96.136.0/23 AS2018 TENET - 1 - The Uninet Project 192.96.140.0/24 AS2018 TENET - 1 - The Uninet Project 192.96.143.0/24 AS2018 TENET - 1 - The Uninet Project 192.96.145.0/24 AS2018 TENET - 1 - The Uninet Project 192.96.177.0/24 AS6083 AFRINIC African Network Information Center 192.96.250.0/24 AS2018 TENET - 1 - The Uninet Project 192.107.104.0/24 AS6458 GUATEL 192.119.135.0/24 AS270 PSCNI-AS - National Aeronautics and Space Administration 192.124.252.0/22 AS680 DFN-IP DFN-IP service X-WiN 192.133.6.0/24 AS10282 EQUANT-CEEUR EQUANT AS for Central and Eastern Europe region 192.136.53.0/24 AS8346 SONATEL-AS Autonomous System 192.153.144.0/21 AS721 DLA-ASNBLOCK-AS - DoD Network Information Center 192.168.255.255/32 AS4637 REACH Reach Network Border AS 192.172.0.0/19 AS721 DLA-ASNBLOCK-AS - DoD Network Information Center 192.188.208.0/20 AS721 DLA-ASNBLOCK-AS - DoD Network Information Center 193.0.246.0/24 AS3303 SWISSCOM Swisscom Solutions Ltd 193.32.19.0/24 AS702 AS702 MCI EMEA - Commercial IP service provider in Europe 193.32.20.0/23 AS702 AS702 MCI EMEA - Commercial IP service provider in Europe 193.36.1.0/24 AS8220 COLT COLT Telecommunications 193.37.69.0/24 AS2856 BT-UK-AS BTnet UK Regional network 193.37.236.0/24 AS702 AS702 MCI EMEA - Commercial IP service provider in Europe 193.110.77.0/24 AS3356 LEVEL3 Level 3 Communications 193.110.78.0/24 AS3356 LEVEL3 Level 3 Communications 193.110.79.0/24 AS3356 LEVEL3 Level 3 Communications 194.31.227.0/24 AS21461 TRANSFAIRNET Transfair-net GmbH Krefeld 194.59.176.0/20 AS1273 CW Cable & Wireless 194.153.156.0/24 AS24865 KMITCHELL-AS Keith Mitchell's Network 194.246.72.0/23 AS8893 ARTFILES-AS Artfiles New Media GmbH 198.23.26.0/24 AS4390 BELLATLANTIC-COM - Bell Atlantic, Inc. 198.54.82.0/24 AS2018 TENET - 1 - The Uninet Project 198.54.92.0/24 AS2018 TENET - 1 - The Uninet Project 198.54.222.0/24 AS2018 TENET - 1 - The Uninet Project 198.54.249.0/24 AS2018 TENET - 1 - The Uninet Project 198.54.250.0/24 AS2018 TENET - 1 - The Uninet Project 198.54.251.0/24 AS2018 TENET - 1 - The Uninet Project 198.97.72.0/21 AS721 DLA-ASNBLOCK-AS - DoD Network Information Center 198.97.80.0/20 AS721 DLA-ASNBLOCK-AS - DoD Network Information Center 198.97.96.0/19 AS721 DLA-ASNBLOCK-AS - DoD Network Information Center 198.97.240.0/20 AS721 DLA-ASNBLOCK-AS - DoD Network Information Center 198.101.4.0/22 AS721 DLA-ASNBLOCK-AS - DoD Network Information Center 198.136.32.0/20 AS19329 MCNET - Martin County Board of County Commissioners 198.160.171.0/24 AS7046 UUNET-CUSTOMER - UUNET Technologies, Inc. 198.161.87.0/24 AS6539 GT-BELL - Bell Canada 198.163.155.0/24 AS684 MTSAL-ASN - MTS Allstream Inc. 198.167.0.0/16 AS7456 INTERHOP - Interhop Network SERVICES Inc. 198.167.163.0/24 AS15290 ALLST-15290 - Allstream Corp. Corporation Allstream 198.168.0.0/16 AS701 ALTERNET-AS - UUNET Technologies, Inc. 198.169.0.0/16 AS803 SASKTEL - SaskTel 198.232.133.0/24 AS23075 SKOTOS-AS - Skotos Tech, Inc 199.9.128.0/17 AS668 ASN-ASNET-NET-AS - Defense Research and Engineering Network 199.10.0.0/16 AS721 DLA-ASNBLOCK-AS - DoD Network Information Center 199.60.0.0/20 AS271 BCNET-AS - University of British Columbia 199.114.0.0/21 AS721 DLA-ASNBLOCK-AS - DoD Network Information Center 199.114.128.0/18 AS721 DLA-ASNBLOCK-AS - DoD Network Information Center 199.114.130.0/24 AS721 DLA-ASNBLOCK-AS - DoD Network Information Center 199.114.132.0/24 AS721 DLA-ASNBLOCK-AS - DoD Network Information Center 199.114.134.0/24 AS3541 ITSDN-U4 - DISA/UNRRA 199.114.136.0/24 AS27044 DDN-ASNBLK1 - DoD Network Information Center 199.114.138.0/24 AS721 DLA-ASNBLOCK-AS - DoD Network Information Center 199.114.140.0/24 AS3544 ITSDN-U7 - DISA/UNRRA 199.114.142.0/24 AS721 DLA-ASNBLOCK-AS - DoD Network Information Center 199.114.144.0/24 AS27064 DDN-ASNBLK1 - DoD Network Information Center 199.114.148.0/24 AS721 DLA-ASNBLOCK-AS - DoD Network Information Center 199.114.150.0/24 AS721 DLA-ASNBLOCK-AS - DoD Network Information Center 199.114.152.0/24 AS27033 DDN-ASNBLK1 - DoD Network Information Center 199.114.153.0/24 AS27034 DDN-ASNBLK1 - DoD Network Information Center 199.114.154.0/24 AS3542 ITSDN-U5 - DISA/UNRRA 199.114.160.0/24 AS1733 CENTAF-SWA - AF DDN PMO 199.121.0.0/16 AS721 DLA-ASNBLOCK-AS - DoD Network Information Center 199.123.0.0/18 AS721 DLA-ASNBLOCK-AS - DoD Network Information Center 199.123.16.0/20 AS721 DLA-ASNBLOCK-AS - DoD Network Information Center 199.123.80.0/21 AS721 DLA-ASNBLOCK-AS - DoD Network Information Center 199.189.32.0/19 AS7332 IQUEST-AS - IQuest Internet 199.202.0.0/16 AS701 ALTERNET-AS - UUNET Technologies, Inc. 199.246.116.0/24 AS813 UUNET-AS1 - UUNET Technologies, Inc. 202.9.64.0/19 AS9290 TPN-AS-AP Smart Global Network (M) Sdn Bhd 202.58.113.0/24 AS19161 INNOCOM-TELECOM - INNOCOM TELECOM 202.74.32.0/19 AS9315 CWN-AS-AP Chomanan WorldNet Co., Ltd. 202.86.252.0/22 AS9304 HUTCHISON-AS-AP Hutchison Global Communications 202.86.253.0/24 AS9304 HUTCHISON-AS-AP Hutchison Global Communications 202.86.254.0/24 AS9304 HUTCHISON-AS-AP Hutchison Global Communications 202.86.255.0/24 AS9304 HUTCHISON-AS-AP Hutchison Global Communications 202.90.33.0/24 AS9830 SWIFTONLINE-AS-AP SWIFT ONLINE BORDER AS 202.90.40.0/24 AS9830 SWIFTONLINE-AS-AP SWIFT ONLINE BORDER AS 202.90.41.0/24 AS9830 SWIFTONLINE-AS-AP SWIFT ONLINE BORDER AS 202.90.42.0/24 AS9830 SWIFTONLINE-AS-AP SWIFT ONLINE BORDER AS 202.90.43.0/24 AS9830 SWIFTONLINE-AS-AP SWIFT ONLINE BORDER AS 202.90.44.0/24 AS9830 SWIFTONLINE-AS-AP SWIFT ONLINE BORDER AS 202.93.0.0/20 AS4134 CHINANET-BACKBONE No.31,Jin-rong Street 202.131.64.0/19 AS9381 NEWTT-IP-AP Wharf T&T Ltd. 202.148.32.0/20 AS17495 GATEWAY-AP BROADBAND WIRELESSS INTERNET SERVICE PROVIDER 203.13.171.0/24 AS1221 ASN-TELSTRA Telstra Pty Ltd 203.62.0.0/17 AS7575 AARNET-AS-AP Australian Academic and Reasearch Network (AARNet) 203.78.48.0/20 AS9299 IPG-AS-AP Philippine Long Distance Telephone Company 203.89.134.0/24 AS17557 PKTELECOM-AS-AP Pakistan Telecom 203.89.139.0/24 AS17911 BRAINPK-AS-AP Brain Telecommunication Ltd. 203.89.143.0/24 AS17557 PKTELECOM-AS-AP Pakistan Telecom 203.89.144.0/24 AS17557 PKTELECOM-AS-AP Pakistan Telecom 203.89.147.0/24 AS17557 PKTELECOM-AS-AP Pakistan Telecom 203.89.148.0/24 AS17557 PKTELECOM-AS-AP Pakistan Telecom 203.89.149.0/24 AS17557 PKTELECOM-AS-AP Pakistan Telecom 203.89.150.0/24 AS17557 PKTELECOM-AS-AP Pakistan Telecom 203.89.151.0/24 AS17557 PKTELECOM-AS-AP Pakistan Telecom 203.89.153.0/24 AS17557 PKTELECOM-AS-AP Pakistan Telecom 203.89.154.0/24 AS17557 PKTELECOM-AS-AP Pakistan Telecom 203.89.158.0/24 AS17557 PKTELECOM-AS-AP Pakistan Telecom 203.89.159.0/24 AS17557 PKTELECOM-AS-AP Pakistan Telecom 203.99.0.0/19 AS17746 ORCONINTERNET-NZ-AP Orcon Internet 203.99.142.0/24 AS9826 ILINK-HK-AP iLink.net Ltd 203.111.192.0/20 AS7473 SINGTEL-AS-AP Singapore Telecom 203.210.69.0/24 AS17536 PRODIGY-AS-AP Prodidgy Telecommunications 204.48.118.0/23 AS29912 CITIZENS-PROPERTY-INSURANCE-CORPORATION - Citizens Property Insurance Corporation 204.48.119.0/24 AS29912 CITIZENS-PROPERTY-INSURANCE-CORPORATION - Citizens Property Insurance Corporation 204.154.125.0/24 AS3952 TELLABS-ASN - TELLABS Operations, Inc. 204.154.126.0/24 AS3952 TELLABS-ASN - TELLABS Operations, Inc. 204.154.127.0/24 AS3952 TELLABS-ASN - TELLABS Operations, Inc. 205.150.0.0/15 AS701 ALTERNET-AS - UUNET Technologies, Inc. 206.128.104.0/21 AS11709 VIC - VIRTUAL INTERACTIVE CENTER 206.167.57.0/24 AS376 RISQ-AS - Reseau Interordinateurs Scientique Quebecois (RISQ) 206.191.64.0/18 AS15290 ALLST-15290 - Allstream Corp. Corporation Allstream 206.191.96.0/19 AS15290 ALLST-15290 - Allstream Corp. Corporation Allstream 207.231.96.0/19 AS11194 NUNETPA - NuNet Inc 208.65.100.0/22 AS36388 SIGNAL-TELECOM - Signal Telecommunications, Inc 208.65.112.0/22 AS36446 OCOSA - OCOSA Communication, LLC 208.65.112.0/24 AS36446 OCOSA - OCOSA Communication, LLC 208.65.115.0/24 AS36446 OCOSA - OCOSA Communication, LLC 209.40.192.0/21 AS6487 CyberNet de Guatemala S.A. 209.40.200.0/21 AS6487 CyberNet de Guatemala S.A. 209.40.208.0/21 AS6487 CyberNet de Guatemala S.A. 209.40.216.0/21 AS6487 CyberNet de Guatemala S.A. 209.205.69.0/24 AS21578 Universidad autonoma de Bucaramanga 209.205.70.0/24 AS21578 Universidad autonoma de Bucaramanga 209.205.81.0/24 AS15066 SkyNet de Colombia S.A. 209.205.82.0/24 AS15066 SkyNet de Colombia S.A. 209.205.84.0/24 AS15066 SkyNet de Colombia S.A. 209.234.0.0/18 AS3845 STATE-NET - CS&W, Inc. 216.37.110.0/23 AS4264 CERNET-ASN-BLOCK - California Education and Research Federation Network 216.71.224.0/20 AS23527 COTELLIGENCE - Cotelligence, Inc. 216.82.160.0/20 AS20481 CALYX-NL Calyx Internet B.V. Netherlands 216.96.128.0/18 AS7018 ATT-INTERNET4 - AT&T WorldNet Services 216.201.68.0/24 AS13564 BELLSOUTHINTERNATIONL - BellSouth International - Network Services 216.201.69.0/24 AS13564 BELLSOUTHINTERNATIONL - BellSouth International - Network Services 216.201.70.0/24 AS13564 BELLSOUTHINTERNATIONL - BellSouth International - Network Services 216.201.71.0/24 AS13564 BELLSOUTHINTERNATIONL - BellSouth International - Network Services 216.201.72.0/24 AS14709 Telefonica Moviles Panama S.A. 216.201.73.0/24 AS14709 Telefonica Moviles Panama S.A. 216.201.74.0/24 AS14709 Telefonica Moviles Panama S.A. 216.201.75.0/24 AS14709 Telefonica Moviles Panama S.A. 216.201.76.0/24 AS14709 Telefonica Moviles Panama S.A. 216.201.77.0/24 AS14709 Telefonica Moviles Panama S.A. 216.201.78.0/24 AS14709 Telefonica Moviles Panama S.A. 216.201.79.0/24 AS14709 Telefonica Moviles Panama S.A. 216.228.64.0/21 AS6295 WHIDBEY1 - Whidbey Internet Services 216.228.224.0/20 AS13674 VRIS-AS-BLOCK-13661-13675 - Verizon Internet Services Inc. 216.240.240.0/20 AS7018 ATT-INTERNET4 - AT&T WorldNet Services 216.240.242.0/24 AS7018 ATT-INTERNET4 - AT&T WorldNet Services Please see http://www.cidr-report.org for the full report ------------------------------------ Copies of this report are mailed to: nanog(a)merit.edu eof-list(a)ripe.net apops(a)apops.net routing-wg(a)ripe.net afnog(a)afnog.org

1 0