From owner-apops Sat Sep 14 17:38:21 1996 Received: (from daemon@localhost) by teckla.apnic.net (8.7.1/8.7.1) id RAA07460 for apops-outgoing; Sat, 14 Sep 1996 17:38:21 +0900 (JST) Received: from sunflower.singnet.com.sg (sunflower.singnet.com.sg [165.21.1.58]) by teckla.apnic.net (8.7.1/8.7.1) with SMTP id RAA07455 for ; Sat, 14 Sep 1996 17:38:16 +0900 (JST) Received: from ts900-2415.singnet.com.sg (ts900-2415.singnet.com.sg [165.21.157.99]) by sunflower.singnet.com.sg (8.6.12/8.6.9) with SMTP id QAA16706 for ; Sat, 14 Sep 1996 16:40:02 +0800 Received: by ts900-2415.singnet.com.sg with Microsoft Mail id <01BBA263.81F37A20@ts900-2415.singnet.com.sg>; Sat, 14 Sep 1996 17:38:14 -0000 Message-ID: <01BBA263.81F37A20@ts900-2415.singnet.com.sg> From: Barry Raveendran Greene To: "'apops@apnic.net'" Subject: Kick off discussion - CIDR problem from the APNIC region. Date: Sat, 14 Sep 1996 17:37:21 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Sender: owner-apops@apnic.net Precedence: bulk Hello All, Lets kick off the work. The global routing table is now in the +40K = region. Something is not working. From discussion on several list, I = noticed the following statistic: Block #Rts >=3D/24 /23 /22 /21 /20 /19 /18 /17 /16 ; Sat, 14 Sep 1996 23:26:20 +0900 (JST) Received: from ts900-2415.singnet.com.sg (ts900-3329.singnet.com.sg [165.21.151.145]) by sunflower.singnet.com.sg (8.6.12/8.6.9) with SMTP id WAA11015 for ; Sat, 14 Sep 1996 22:29:20 +0800 Received: by ts900-2415.singnet.com.sg with Microsoft Mail id <01BBA294.4C1C4040@ts900-2415.singnet.com.sg>; Sat, 14 Sep 1996 23:27:29 -0000 Message-ID: <01BBA294.4C1C4040@ts900-2415.singnet.com.sg> From: Barry Raveendran Greene To: "'apops@apnic.net'" Subject: FW: as1849 peering policy change Date: Sat, 14 Sep 1996 19:56:43 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Sender: owner-apops@apnic.net Precedence: bulk FYI Route filter are becoming more and more common place. The faster people = move from advertising /23s & /24s from the AP region, the better for = everyone. Barry ---------- From: Tony Barber[SMTP:tonyb@uunet.pipex.com] Sent: Thursday, September 12, 1996 6:09 PM To: ripe-op@ripe.net Cc: peering@uunet.pipex.com; routing@uunet.pipex.com Subject: as1849 peering policy change Hi UUNETPIPEX (AS1849) will be filtering inbound routing announcements and blocking all routes which have a prefix of /25 or greater. At the moment this will be indefinate unless otherwise specified. =20 Regards --Tony =20 From owner-apops Sun Sep 15 00:54:16 1996 Received: (from daemon@localhost) by teckla.apnic.net (8.7.1/8.7.1) id AAA09282 for apops-outgoing; Sun, 15 Sep 1996 00:54:16 +0900 (JST) Received: from alumni.cuhk.edu.hk (root@purple.alumni.cuhk.edu.hk [202.45.188.17]) by teckla.apnic.net (8.7.1/8.7.1) with SMTP id AAA09277 for ; Sun, 15 Sep 1996 00:54:08 +0900 (JST) Received: from chcheng.csc.cuhk.edu.hk (ppp066.alumni.cuhk.edu.hk) by alumni.cuhk.edu.hk (5.x/SMI-SVR4) id AA28744; Sat, 14 Sep 1996 23:57:02 +0800 Message-Id: <323AD527.606D@cuhk.edu.hk> Date: Sat, 14 Sep 1996 23:54:15 +0800 From: Che-Hoo Cheng Organization: The Chinese University of Hong Kong X-Mailer: Mozilla 3.0 (Win95; I) Mime-Version: 1.0 To: Barry Raveendran Greene Cc: "'apops@apnic.net'" Subject: Re: Kick off discussion - CIDR problem from the APNIC region. References: <01BBA263.81F37A20@ts900-2415.singnet.com.sg> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-apops@apnic.net Precedence: bulk Barry Raveendran Greene wrote: > > Hello All, > > Lets kick off the work. The global routing table is now in the +40K region. Something is not working. From discussion on several list, I noticed the following statistic: > > Block #Rts >=/24 /23 /22 /21 /20 /19 /18 /17 /16 > 202 1556 718 228 204 125 110 56 66 19 25 5 3787 35.12 > > 203 1444 902 146 127 47 57 56 40 34 33 2 5852 50.38 > > Given that APNIC's policy is to allocate a /22 to each ISP, we should not see many routes below /22. Yet, this data clearly shows that a huge number of routes are not aggregated. > > Is there any reason why? Any thoughts? > > If we can get people aggregating properly, then APOPs can reduce the routing table by at lease 1500 routes. I notice that some multi-homed ISPs in HK announce different sub-blocks (>=/22s) of their super-block to different upstreams just to achieve certain load-balancing for their inbound traffic. Of course, this contributes more routes to the routing table. Is it really healthy? I guess guidelines for multi-homing should be set up so that those ISPs can know more about what should be done and what shouldn't. Cheers, -- Che-Hoo Cheng | Email: chcheng@cuhk.edu.hk Data Comms and Networking Section | URL: http://www.cuhk.edu.hk/ Information Technology Service Unit | Tel: +852 2609-8848 The Chinese University of Hong Kong | Fax: +852 2603-5001 From owner-apops Sun Sep 15 02:26:17 1996 Received: (from daemon@localhost) by teckla.apnic.net (8.7.1/8.7.1) id CAA09743 for apops-outgoing; Sun, 15 Sep 1996 02:26:17 +0900 (JST) Received: from alumni.cuhk.edu.hk (root@purple.alumni.cuhk.edu.hk [202.45.188.17]) by teckla.apnic.net (8.7.1/8.7.1) with SMTP id CAA09738 for ; Sun, 15 Sep 1996 02:26:12 +0900 (JST) Received: from chcheng.csc.cuhk.edu.hk (ppp066.alumni.cuhk.edu.hk) by alumni.cuhk.edu.hk (5.x/SMI-SVR4) id AA29052; Sun, 15 Sep 1996 01:29:11 +0800 Message-Id: <323AEAC0.5F53@cuhk.edu.hk> Date: Sun, 15 Sep 1996 01:26:24 +0800 From: Che-Hoo Cheng Organization: The Chinese University of Hong Kong X-Mailer: Mozilla 3.0 (Win95; I) Mime-Version: 1.0 To: Barry Raveendran Greene , "'apops@apnic.net'" Subject: Re: Kick off discussion - CIDR problem from the APNIC region. References: <01BBA263.81F37A20@ts900-2415.singnet.com.sg> <323AD527.606D@cuhk.edu.hk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-apops@apnic.net Precedence: bulk Che-Hoo Cheng wrote: > I notice that some multi-homed ISPs in HK announce different sub-blocks > (>=/22s) of their super-block to different upstreams just to achieve ^^^^^^ Oops, should be <=/22s. Sorry! > certain load-balancing for their inbound traffic. Of course, this > contributes more routes to the routing table. Is it really healthy? > > I guess guidelines for multi-homing should be set up so that those ISPs > can know more about what should be done and what shouldn't. > > Cheers, > > -- > > Che-Hoo Cheng | Email: chcheng@cuhk.edu.hk > Data Comms and Networking Section | URL: http://www.cuhk.edu.hk/ > Information Technology Service Unit | Tel: +852 2609-8848 > The Chinese University of Hong Kong | Fax: +852 2603-5001 -- Che-Hoo Cheng | Email: chcheng@cuhk.edu.hk Data Comms and Networking Section | URL: http://www.cuhk.edu.hk/ Information Technology Service Unit | Tel: +852 2609-8848 The Chinese University of Hong Kong | Fax: +852 2603-5001 From owner-apops Sun Sep 15 08:18:24 1996 Received: (from daemon@localhost) by teckla.apnic.net (8.7.1/8.7.1) id IAA11196 for apops-outgoing; Sun, 15 Sep 1996 08:18:24 +0900 (JST) Received: from nico.aarnet.edu.au (nico.aarnet.edu.au [139.130.204.16]) by teckla.apnic.net (8.7.1/8.7.1) with SMTP id IAA11188 for ; Sun, 15 Sep 1996 08:18:20 +0900 (JST) Received: (from gih@localhost) by nico.aarnet.edu.au (8.6.10/8.6.10) id JAA24862; Sun, 15 Sep 1996 09:20:10 +1000 From: Geoff Huston Message-Id: <199609142320.JAA24862@nico.aarnet.edu.au> Subject: Re: Kick off discussion - CIDR problem from the APNIC region. To: barry@singnet.com.sg (Barry Raveendran Greene) Date: Sun, 15 Sep 1996 09:20:10 +1000 (EST) Cc: apops@apnic.net In-Reply-To: <01BBA263.81F37A20@ts900-2415.singnet.com.sg> from "Barry Raveendran Greene" at Sep 14, 96 05:37:21 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-apops@apnic.net Precedence: bulk Barry, The short answer is that the state of end user dyanmic address and/or prefix environments is a shambles and the harsh marketing reality is that provider-based addresses are anti-marketing (you want to switch to us and not change your IP address as you do so? SURE.) and the last harsh statement is that stable transit inter-provider mechansms are woefully immature and unstable. And there is no mechanism of enforcement: Getting people to aggregate properly can be done as a polite "please" (the marketing loonies will ignore this), it can be done as an impolite "you must" (the marketing loonies will say "where's your authority?"), it can be done as a "pay for your routes (which is economically sensible if only we knew what this statement actually meant!), or we can all buy bigger routers next year and sign up as a new convert into a convenient religion. Personally I can only offer the depressing view that the latter appears to be the most promising course of action. g > > Hello All, > > Lets kick off the work. The global routing table is now in the +40K = > region. Something is not working. From discussion on several list, I = > noticed the following statistic: > > Block #Rts >=3D/24 /23 /22 /21 /20 /19 /18 /17 /16 of spc > > 202 1556 718 228 204 125 110 56 66 19 25 5 3787 = > 35.12 > > 203 1444 902 146 127 47 57 56 40 34 33 2 5852 = > 50.38 > > Given that APNIC's policy is to allocate a /22 to each ISP, we should = > not see many routes below /22. Yet, this data clearly shows that a huge = > number of routes are not aggregated. > > Is there any reason why? Any thoughts? > > If we can get people aggregating properly, then APOPs can reduce the = > routing table by at lease 1500 routes.=20 > > Barry > > From owner-apops Sun Sep 15 10:15:43 1996 Received: (from daemon@localhost) by teckla.apnic.net (8.7.1/8.7.1) id KAA11660 for apops-outgoing; Sun, 15 Sep 1996 10:15:43 +0900 (JST) Received: from sunflower.singnet.com.sg (sunflower.singnet.com.sg [165.21.1.58]) by teckla.apnic.net (8.7.1/8.7.1) with SMTP id KAA11655 for ; Sun, 15 Sep 1996 10:15:39 +0900 (JST) Received: from ts900-6411.singnet.com.sg (ts900-6411.singnet.com.sg [165.21.163.95]) by sunflower.singnet.com.sg (8.6.12/8.6.9) with SMTP id JAA27712; Sun, 15 Sep 1996 09:17:21 +0800 Received: by ts900-6411.singnet.com.sg with Microsoft Mail id <01BBA2EE.D305A7E0@ts900-6411.singnet.com.sg>; Sun, 15 Sep 1996 10:15:30 -0000 Message-ID: <01BBA2EE.D305A7E0@ts900-6411.singnet.com.sg> From: Barry Raveendran Greene To: "'Che-Hoo Cheng'" Cc: "'apops@apnic.net'" Subject: Re: Kick off discussion - CIDR problem from the APNIC region. Date: Sun, 15 Sep 1996 10:09:33 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-apops@apnic.net Precedence: bulk Hello Che-Hoo, Che-Hoo Cheng wrote: >I notice that some multi-homed ISPs in HK announce different sub-blocks >(>=/22s) of their super-block to different upstreams just to achieve >certain load-balancing for their inbound traffic. Of course, this >contributes more routes to the routing table. Is it really healthy? > >I guess guidelines for multi-homing should be set up so that those >ISPs can know more about what should be done and what shouldn't. Here is a list of dual advertisements: *** conflict 202.0.10.0 in AS4648 and AS681 *** conflict 202.0.84.0 in AS4648 and AS681 *** conflict 202.6.5.0 in AS4648 and AS681 *** conflict 202.6.93.0 in AS4648 and AS681 *** conflict 202.12.91.0 in AS4648 and AS681 *** conflict 202.12.101.0 in AS4648 and AS681 *** conflict 202.14.69.0 in AS4648 and AS681 *** conflict 202.14.72.0 in AS4648 and AS681 *** conflict 202.14.96.0 in AS4648 and AS681 *** conflict 202.14.99.0 in AS4648 and AS681 *** conflict 202.14.100.0 in AS4648 and AS681 *** conflict 202.14.102.0 in AS4648 and AS681 *** conflict 202.14.106.0 in AS4648 and AS681 *** conflict 202.14.216.0 in AS4648 and AS681 *** conflict 202.14.218.0 in AS4648 and AS681 *** conflict 202.20.80.0 in AS4648 and AS681 *** conflict 202.20.104.0 in AS4648 and AS681 *** conflict 202.20.113.0 in AS4648 and AS681 *** conflict 202.21.143.0 in AS4648 and AS681 *** conflict 202.21.157.0 in AS4648 and AS681 *** conflict 202.242.127.0 in AS2907 and AS4706 *** conflict 202.244.4.0 in AS2713 and AS4680 *** conflict 203.11.123.0 in AS2044 and AS4175 *** conflict 203.24.54.0 in AS2044 and AS4175 *** conflict 203.24.152.0 in AS2044 and AS4742 *** conflict 203.66.154.0 in AS4747 and AS4780 This accounts for a few, but not all. I'm wondering if people know: - The tricks to lock you BGP CIDR routes up? - How to check your advertisements once they get past you upstream provider? - Bandwidth management trick (i.e. like asymmetrical routing)? - Not to redistribute you IGP into eBGP and still get what you want? Q. Should we launch into a discussion on how these can be done? Barry From owner-apops Tue Sep 17 02:44:19 1996 Received: (from daemon@localhost) by teckla.apnic.net (8.7.1/8.7.1) id CAA24506 for apops-outgoing; Tue, 17 Sep 1996 02:44:19 +0900 (JST) Received: from charon.gsl.net (charon.gsl.net [204.59.155.42]) by teckla.apnic.net (8.7.1/8.7.1) with ESMTP id CAA24501 for ; Tue, 17 Sep 1996 02:44:14 +0900 (JST) Received: (from jian@localhost) by charon.gsl.net (8.7.1/8.7.1) id NAA04324; Mon, 16 Sep 1996 13:42:09 -0400 (EDT) From: "Jian Q. Li" Message-Id: <199609161742.NAA04324@charon.gsl.net> Subject: Re: Kick off discussion - CIDR problem from the APNIC region. To: chcheng@cuhk.edu.hk (Che-Hoo Cheng) Date: Mon, 16 Sep 1996 13:42:08 -0400 (EDT) Cc: barry@singnet.com.sg, apops@apnic.net In-Reply-To: <323AD527.606D@cuhk.edu.hk> from "Che-Hoo Cheng" at Sep 14, 96 11:54:15 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-apops@apnic.net Precedence: bulk ==> Che-Hoo Cheng wrote: > > I notice that some multi-homed ISPs in HK announce different sub-blocks > (>=/22s) of their super-block to different upstreams just to achieve > certain load-balancing for their inbound traffic. Of course, this > contributes more routes to the routing table. Is it really healthy? > > I guess guidelines for multi-homing should be set up so that those ISPs > can know more about what should be done and what shouldn't. > > Cheers, > I think local exchange points should have guidelines or policy to deal with such "smart players". If a local exchange point is really for promotion of local traffic exchange, the more specific announcement for load-balancing purpose violates the intent of local traffic exchange. Such smart plays therefore should be forbidden in any exchange point ( for local traffic exchange only). We do filtering on more specific in local exchange points. The problem is how to keep the filter list updated since it is a static configuration. Cheers, jian -- Jian Q. Li Global IP Engineering Phone: 703-689-6878 Global One Communications L.L.C. E-Mail: jian@gsl.net From owner-apops Wed Sep 18 10:49:07 1996 Received: (from daemon@localhost) by teckla.apnic.net (8.7.1/8.7.1) id KAA10068 for apops-outgoing; Wed, 18 Sep 1996 10:49:07 +0900 (JST) Received: from diablo.cisco.com (diablo.cisco.com [171.68.223.106]) by teckla.apnic.net (8.7.1/8.7.1) with SMTP id KAA10056; Wed, 18 Sep 1996 10:49:00 +0900 (JST) Received: from bgreene-pc.cisco.com ([171.68.85.216]) by diablo.cisco.com (8.6.12/CISCO.SERVER.1.1) with SMTP id SAA04407; Tue, 17 Sep 1996 18:49:47 -0700 Received: by bgreene-pc.cisco.com with Microsoft Mail id <01BBA54E.D510C9E0@bgreene-pc.cisco.com>; Wed, 18 Sep 1996 10:47:48 -0000 Message-ID: <01BBA54E.D510C9E0@bgreene-pc.cisco.com> From: Barry Raveendran Greene Subject: Cisco Systems Advises Industry On Security Against Possible Hacker Attacks Date: Wed, 18 Sep 1996 10:47:47 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-apops@apnic.net Precedence: bulk Hello All, Please, everyone read the follow and take action. If you would like to discuss details of need help, please let me know. http://cio.cisco.com/warp/public/707/3.html -- Barry Raveendran Greene | || || | Consulting Engineering | || || | Singapore | |||| |||| | tel: +65 738-5535 ext 235 | ..:||||||:..:||||||:.. | e-mail: bgreene@cisco.com | c i s c o S y s t e m s | Cisco Systems Advises Industry On Security Against Possible Hacker Attacks SAN JOSE, Calif. (September 17, 1996) - Following several reports of assaults on commercial Web sites and network devices by anonymous hacker(s), Cisco Systems Inc. is taking several steps to inform its customers how they might address a potential threat to their networks. Cisco called more than 40 leading Internet service providers (ISPs) worldwide Monday to notify them of the possibility of isolated electronic attacks targeted at Web sites and network devices connected to the Internet. Cisco informed the ISPs of software capabilities that could be implemented to resist attacks of the type seen recently. One problem occurs when a hacker floods a Web server or network device with a huge volume of requests for connection. Because these messages have false return addresses, however, the connections cannot be established. The large volume of unresolved open connections eventually overwhelms the server or network device and may cause the server or network device to deny service. In the past week, Cisco has collaborated with ISP customers to understand the implications of potential attacks and share information on how they can be resisted. At least one ISP has installed a Cisco-recommended software implementation that successfully restored network service after having been attacked. The same implementation is currently in place to resist future attacks on the same system. This implementation has been shared with ISPs as a preventive measure. "We view it as our responsibility to lead the industry in helping customers resist malicious attacks," said Don Listwin, senior vice president of Cisco IOS development and marketing for Cisco Systems. "We are applying our expertise in Internet technology and large-scale networking to help ISPs develop both short- and long-term solutions for increased network security and reliability." Web sites on the Internet are typically connected by network devices called routers. Thus, Cisco engineers believe an ISP or corporate network could be targeted by attacks at the network level in addition to the server level. Because of the potential threat to their networks, Cisco has initiated discussions with ISPs to share what Cisco knows and suggest immediate steps that can be taken to reduce vulnerability. Cisco has existing security products throughout networks worldwide and is continuously developing new products to continue to address the need for increased network security. Due to the intelligence of routers and firewall products, they are key technologies for resisting attacks of the nature that have been launched in recent days. By design, routers and firewalls are intelligent devices with the ability to examine the source of traffic and block traffic from unauthorized sources. The ubiquitous role routers play in the Internet makes them a natural place to implement security capabilities. Cisco provides more than 80 percent of the routers in the global Internet. In addition to working with ISPs, Cisco also has initiated contacts with other networking device and server manufacturers, to share information and coordinate activity. Cisco Systems (NASDAQ:CSCO) is the leading global supplier of internetworking solutions for corporate intranets and the global Internet. Cisco's products -- including routers, LAN and WAN switches, dial-up access servers and network management software -- are integrated by Cisco IOS software to link geographically dispersed LANs, WANs and IBM networks. Company news and product/service information are available at World Wide Web site http://www.cisco.com. Cisco is headquartered in San Jose, Calif. ### From owner-apops Wed Sep 18 15:30:24 1996 Received: (from daemon@localhost) by teckla.apnic.net (8.7.1/8.7.1) id PAA12351 for apops-outgoing; Wed, 18 Sep 1996 15:30:24 +0900 (JST) Received: from hp715a.csc.cuhk.edu.hk (hp715a.csc.cuhk.edu.hk [137.189.6.58]) by teckla.apnic.net (8.7.1/8.7.1) with SMTP id PAA12331 for ; Wed, 18 Sep 1996 15:28:44 +0900 (JST) Received: from pc29107.csc.cuhk.edu.hk (pc29107.csc.cuhk.hk [137.189.29.107]) by hp715a.csc.cuhk.edu.hk (8.6.13/8.6.12) with SMTP id OAA10029; Wed, 18 Sep 1996 14:30:56 +0800 Message-ID: <323F96CD.3C67@cuhk.hk> Date: Wed, 18 Sep 1996 14:29:33 +0800 From: Che-Hoo Cheng Organization: The Chinese University of Hong Kong X-Mailer: Mozilla 2.02 (Win95; I) MIME-Version: 1.0 To: hk-nsp@cuhk.edu.hk, apops@apnic.net Subject: Cisco Systems Advises Industry On Security Against Possible Hacker Attacks X-URL: http://www.cisco.com/warp/public/146/917_security.html Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-apops@apnic.net Precedence: bulk Pls take a look at http://www.cisco.com/warp/public/146/917_security.html. Disclaimer: I am not associated with Cisco. :) -- Che-Hoo Cheng | Email: chehoocheng@cuhk.hk or Data Comms and Networking Section | ch@csc.msmail.cuhk.hk Computer Services Center | Phone: +852 2609-8848 The Chinese University of Hong Kong | Fax: +852 2603-5001 From owner-apops Fri Sep 20 20:58:47 1996 Received: (from daemon@localhost) by teckla.apnic.net (8.7.1/8.7.1) id UAA05332 for apops-outgoing; Fri, 20 Sep 1996 20:58:47 +0900 (JST) Received: from marikit.iphil.net (map@marikit.iphil.net [203.176.0.4]) by teckla.apnic.net (8.7.1/8.7.1) with ESMTP id UAA05326 for ; Fri, 20 Sep 1996 20:58:40 +0900 (JST) Received: (from map@localhost) by marikit.iphil.net (8.7.5/8.6.9) id FAA20202 for apops@apnic.net; Fri, 20 Sep 1996 05:01:30 -0700 From: "Miguel A.L. Paraz" Message-Id: <199609201201.FAA20202@marikit.iphil.net> Subject: Squeezing out more address space To: apops@apnic.net Date: Fri, 20 Sep 1996 20:01:29 +0800 (GMT+0800) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-apops@apnic.net Precedence: bulk -----BEGIN PGP SIGNED MESSAGE----- Hi, I'm thinking of how to allocate space such that we get to use as much as it as possible, while trying to limit the routing table entries needed to carry this space. We have a freshly allocated /19; only the lower /20 is used. Now, I'm looking out for space to reclaim from the lower /20. Our company sells access to other ISPs (who by contract can only sell single-user dialup access), as well as corporations. We are already implementing the following: - - Corporate customers by default do not get any address space at all, but use RFC 1918 space (typically just 192.168.0.0/24), and application level gateways. The only customers that could not use this are one who has a chaotic network structure, though we intend to reclaim their /24 in the future, and those who insist upon it, or have trouble with the routing/proxying, as they're using NT. This works for mail, which is picked up by Taylor UUCP over TCP from our mailserver, which acts like a fixed maildrop for these customers. It also works with FTP/HTTP/Gopher, through Squid, which is an excellent WWW proxy cache. For Usenet, we have tried various proxies, but even the simple plug-gw from the TIS toolkit works since we don't carry much of a newsfeed anyway. However, it does not work for apps like IRC. We tried a plug-gw to the Undernet server, but this limits the user's choice of servers. And, the Undernet people didn't seem to like many users logging into IRC under the same ident. For future allocations, I want to: - - keep the lower /20 for ISP network infrastructure (routers, servers) only. Dynamic IP space for dial-up ports will be allocated from the upper /20. This way, ISPs can have as small as a /28 for their router and servers, while allocating as much as they need from the upper pool, since we're not constrained to allocate on even bit boundaries. However, since this means multiple networks per customer, it will require a sensible choice of IGP. Currently, we're still getting along with static routing, as there are no multiple paths to the same customer. - - use NSP (Sprint, MCI) space instead for dialups. Currently, we do not do BGP, given the low speed of our circuits and the additional complexity. Plus, the current economics does not encourage us to get two equally- sized international links. Thus, we will be tending to singly-homing for the bulk of our connections, while using another connection for backup purposes, through application-level routing of WWW, e-mail, Usenet, and possibly others. Thus, we can allocate networks instead from the upstream CIDR space. Since we are statically routed, it is in our interest to keep our route announcements to a minimum. In short my goal is to maximize the use of IP space, considering that there is a relatively smaller amount of actual bandwidth available per IP address. Any thoughts on this? Thanks. -----BEGIN PGP SIGNATURE----- Version: 2.6.i iQB1AgUBMkKHl7sCsZ1D8NARAQFFdgL9EaDiJ5tcvwYmaXjbB4gpTvZLCeztdq6L 3tdFgjmJXh+S7IFextroseka3Gp16HtW4/0+2aHMURHuRixyXYYodstLt7G67FP0 pEcAYSiOBcWpn9kZ5Mw72SpGrVXMWc+U =SAHd -----END PGP SIGNATURE----- -- miguel a.l. paraz PGP keyID: 0x43F0D011 iphil communications, makati city, philippines http://www.iphil.net From owner-apops Wed Sep 25 16:12:50 1996 Received: (from daemon@localhost) by teckla.apnic.net (8.7.1/8.7.1) id QAA16559 for apops-outgoing; Wed, 25 Sep 1996 16:12:50 +0900 (JST) Received: from nostromo.jp.apnic.net (root@[192.244.184.5]) by teckla.apnic.net (8.7.1/8.7.1) with ESMTP id QAA16546 for ; Wed, 25 Sep 1996 16:11:13 +0900 (JST) Received: from ronin.apnic.net (davidc@localhost [127.0.0.1]) by nostromo.jp.apnic.net (8.7.3/8.7.3) with ESMTP id CAA01966 for ; Wed, 25 Sep 1996 02:00:21 GMT Resent-Message-Id: <199609250200.CAA01966@nostromo.jp.apnic.net> Received: from dragon.jp.apnic.net (firewall-user@apnic.hq.unu.edu [202.253.138.44]) by teckla.apnic.net (8.7.1/8.7.1) with SMTP id LAA23889 for ; Mon, 23 Sep 1996 11:32:33 +0900 (JST) Received: by dragon.jp.apnic.net; id LAA13353; Mon, 23 Sep 1996 11:21:21 +0900 Received: from moonsky.jp.apnic.net(10.0.10.4) by dragon.jp.apnic.net via smap (g3.0.3) id xma013351; Mon, 23 Sep 96 11:20:53 +0900 Received: from dragon.jp.apnic.net (firewall-user@firewall.jp.apnic.net [10.0.10.1]) by moonsky.jp.apnic.net (8.7.1/8.7.1) with SMTP id LAA26463 for ; Mon, 23 Sep 1996 11:29:36 +0900 (JST) Received: by dragon.jp.apnic.net; id LAA13347; Mon, 23 Sep 1996 11:20:51 +0900 Received: from teckla.apnic.net(202.12.28.129) by dragon.jp.apnic.net via smap (g3.0.3) id xma013345; Mon, 23 Sep 96 11:20:39 +0900 Received: from ncc.ripe.net (ncc.ripe.net [193.0.0.129]) by teckla.apnic.net (8.7.1/8.7.1) with SMTP id LAA23879 for ; Mon, 23 Sep 1996 11:31:39 +0900 (JST) Received: by ncc.ripe.net id AA13102 (5.65a/NCC-2.38); Mon, 23 Sep 1996 04:13:35 +0200 Received: from Strul.Stupi.SE by ncc.ripe.net with SMTP id AA13094 (5.65a/NCC-2.38); Mon, 23 Sep 1996 04:13:33 +0200 Received: from Slaptoy.Stupi.SE (lgb111.ppp.uni-c.dk [130.228.6.111]) by Strul.Stupi.SE (8.6.12/8.6.9) with ESMTP id EAA07799for ; Mon, 23 Sep 1996 04:13:30 +0200 Received: (from roll@localhost) by Slaptoy.Stupi.SE (8.7.4/8.7.3) id DAA00718 for ripe-list@ripe.net; Mon, 23 Sep 1996 03:43:34 +0200 (MET DST) Date: Mon, 23 Sep 96 3:43:31 MET DST From: Peter Lothberg To: ripe-list@ripe.net Subject: Very fast IP, no ATM... Message-Id: Resent-To: apops@apnic.net Resent-Date: Wed, 25 Sep 1996 02:00:00 +0000 Resent-From: "David R. Conrad" Sender: owner-apops@apnic.net Precedence: bulk On Monday 23 September 1996 00:15Z.. Was the worlds first transatlantic 155Mbit native IP service brought into operation by Sprint/USA and Tele2/Sweden. The circiut wich is part of Sprintlink and ICMnet runs between the NY-Nap in Pennsauken, NJ, USA and Tele2 in Sweden and uses cisco packet-over-sonet/sdh technology. (Native IP over SDH/VC4) In 1995 the same team from Sprint and Tele2 brought up the worlds first transatlantic E3 service between the same endpoints. For more information; Sprint: Tricia Schibler, +1 703 904 2042, Tele2: Olle Wallner, +46 8 5626 4058, --Peter From owner-apops Sat Sep 28 04:00:38 1996 Received: (from daemon@localhost) by teckla.apnic.net (8.7.1/8.7.1) id EAA15498 for apops-outgoing; Sat, 28 Sep 1996 04:00:38 +0900 (JST) Received: from lovefm.cisco.com (lovefm.cisco.com [171.68.228.35]) by teckla.apnic.net (8.7.1/8.7.1) with SMTP id EAA15490 for ; Sat, 28 Sep 1996 04:00:19 +0900 (JST) Received: from cisco.com (localhost.cisco.com [127.0.0.1]) by lovefm.cisco.com (8.6.12/8.6.5) with ESMTP id MAA07306; Fri, 27 Sep 1996 12:01:15 -0700 Message-Id: <199609271901.MAA07306@lovefm.cisco.com> To: nanog@merit.edu cc: tbates@cisco.com, eof@ripe.net, apops@apnic.net Subject: The Cidr Report Date: Fri, 27 Sep 1996 12:01:15 -0700 From: Tony Bates Sender: owner-apops@apnic.net Precedence: bulk This is an auto-generated mail on Fri Sep 27 12:01:14 PDT 1996 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. In the future I hope to put some (or most) of this report up on the web. ------------------------------------------------------------------------------ CIDR REPORT for 27Sep96 0) General Status Table History ------------- Date Prefixes 210996 43100 220996 42436 230996 42636 240996 42498 250996 41621 260996 42422 270996 42323 Possible Bogus Routes --------------------- *** Bogus 211.199.11.0 from AS6176 AS Summary ---------- Number of ASes in routing system: 1630 Number of ASes announcing only one prefix: 644 (330 cidr, 314 classful) Largest number of cidr routes: 493 announced by AS3561 Largest number of classful routes: 1268 announced by AS174 1) Gains by aggregating at the origin AS level --- 27Sep96 --- ASnum NetsNow NetsCIDR NetGain % Gain Description AS719 1011 601 410 40.6% LANLINK autonomous system AS174 1268 924 344 27.1% Performance Systems International AS279 850 508 342 40.2% SURAnet Southern AS AS2493 756 479 277 36.6% i*internet AS3602 586 335 251 42.8% Intergrated Network Services Inc. AS3397 300 98 202 67.3% EMI-AS AS3749 273 73 200 73.3% Tennessee Board of Regents AS2048 342 153 189 55.3% State of Louisiana/Office of Tele AS1 426 281 145 34.0% BBN Planet backbone AS86 379 236 143 37.7% SURAnet Northern AS AS3804 384 241 143 37.2% WorldLinx 3 AS1691 294 157 137 46.6% ANS-BLK1 AS4230 350 214 136 38.9% Embratel Brazil AS568 370 259 111 30.0% JIS (Joint Interconnection Servic AS2386 231 136 95 41.1% INS-AS AS1790 335 250 85 25.4% SprintLink Washington D.C. AS2704 266 186 80 30.1% HOOKUP-NET-A AS721 335 259 76 22.7% DLA-ASNBLOCK-AS AS3215 132 57 75 56.8% RAIN AS560 399 325 74 18.5% BBN Planet, New England Region (N AS3819 98 29 69 70.4% SIGNET AS225 127 61 66 52.0% University of Virginia (VIRnet) AS813 228 164 64 28.1% UUNET Canada (ASN-UUNETCA-AS1) AS3450 110 47 63 57.3% UTK AS3996 113 51 62 54.9% FIRN AS1791 199 137 62 31.2% SprintLink Fort Worth TX AS1785 285 225 60 21.1% NYSERNet Backbone AS2711 109 50 59 54.1% SUNBELT-AS AS855 125 67 58 46.4% NBTel AS2871 139 82 57 41.0% Internet Services GmbH & Co --- 26Sep96 --- ASnum NetsNow NetsCIDR NetGain % Gain Description AS719 1009 601 408 40.4% LANLINK autonomous system AS174 1277 931 346 27.1% Performance Systems International AS279 841 497 344 40.9% SURAnet Southern AS AS2493 755 478 277 36.7% i*internet AS3602 585 335 250 42.7% Intergrated Network Services Inc. AS3749 274 73 201 73.4% Tennessee Board of Regents AS2048 344 149 195 56.7% State of Louisiana/Office of Tele AS3397 286 104 182 63.6% EMI-AS AS1 425 280 145 34.1% BBN Planet backbone AS86 379 236 143 37.7% SURAnet Northern AS AS3804 385 242 143 37.1% WorldLinx 3 AS1691 293 156 137 46.8% ANS-BLK1 AS4230 346 211 135 39.0% Embratel Brazil AS568 367 257 110 30.0% JIS (Joint Interconnection Servic AS2386 232 137 95 40.9% INS-AS AS1790 334 249 85 25.4% SprintLink Washington D.C. AS721 349 268 81 23.2% DLA-ASNBLOCK-AS AS2704 265 185 80 30.2% HOOKUP-NET-A AS3215 132 57 75 56.8% RAIN AS3819 98 29 69 70.4% SIGNET AS813 228 161 67 29.4% UUNET Canada (ASN-UUNETCA-AS1) AS225 127 61 66 52.0% University of Virginia (VIRnet) AS3450 112 49 63 56.2% UTK AS1791 202 140 62 30.7% SprintLink Fort Worth TX AS3996 113 52 61 54.0% FIRN AS1785 286 226 60 21.0% NYSERNet Backbone AS2711 110 51 59 53.6% SUNBELT-AS AS855 124 67 57 46.0% NBTel AS2871 139 82 57 41.0% Internet Services GmbH & Co AS560 369 313 56 15.2% BBN Planet, New England Region (N --- 25Sep96 --- ASnum NetsNow NetsCIDR NetGain % Gain Description AS4230 1100 347 753 68.5% Embratel Brazil AS174 1281 931 350 27.3% Performance Systems International AS279 838 498 340 40.6% SURAnet Southern AS AS2493 753 476 277 36.8% i*internet AS3602 583 335 248 42.5% Intergrated Network Services Inc. AS3749 279 75 204 73.1% Tennessee Board of Regents AS3397 290 102 188 64.8% EMI-AS AS2048 340 156 184 54.1% State of Louisiana/Office of Tele AS1 456 294 162 35.5% BBN Planet backbone AS86 365 224 141 38.6% SURAnet Northern AS AS1691 287 153 134 46.7% ANS-BLK1 AS568 363 255 108 29.8% JIS (Joint Interconnection Servic AS3804 325 218 107 32.9% WorldLinx 3 AS719 545 450 95 17.4% LANLINK autonomous system AS2386 232 137 95 40.9% INS-AS AS2704 271 184 87 32.1% HOOKUP-NET-A AS1790 336 251 85 25.3% SprintLink Washington D.C. AS721 346 265 81 23.4% DLA-ASNBLOCK-AS AS3215 129 55 74 57.4% RAIN AS3819 98 29 69 70.4% SIGNET AS813 227 160 67 29.5% UUNET Canada (ASN-UUNETCA-AS1) AS225 127 61 66 52.0% University of Virginia (VIRnet) AS3450 111 46 65 58.6% UTK AS1791 203 141 62 30.5% SprintLink Fort Worth TX AS1785 283 223 60 21.2% NYSERNet Backbone AS3996 110 51 59 53.6% FIRN AS2711 109 50 59 54.1% SUNBELT-AS AS855 123 67 56 45.5% NBTel AS839 90 35 55 61.1% North West Territories Regional N AS2551 348 293 55 15.8% NETCOM On-line Communication Serv --- 24Sep96 --- ASnum NetsNow NetsCIDR NetGain % Gain Description AS4230 1100 347 753 68.5% Embratel Brazil AS174 1281 931 350 27.3% Performance Systems International AS279 838 498 340 40.6% SURAnet Southern AS AS2493 753 476 277 36.8% i*internet AS3602 583 335 248 42.5% Intergrated Network Services Inc. AS3749 279 75 204 73.1% Tennessee Board of Regents AS3397 290 102 188 64.8% EMI-AS AS2048 340 156 184 54.1% State of Louisiana/Office of Tele AS1 456 294 162 35.5% BBN Planet backbone AS86 365 224 141 38.6% SURAnet Northern AS AS1691 287 153 134 46.7% ANS-BLK1 AS568 363 255 108 29.8% JIS (Joint Interconnection Servic AS3804 325 218 107 32.9% WorldLinx 3 AS719 545 450 95 17.4% LANLINK autonomous system AS2386 232 137 95 40.9% INS-AS AS2704 271 184 87 32.1% HOOKUP-NET-A AS1790 336 251 85 25.3% SprintLink Washington D.C. AS721 346 265 81 23.4% DLA-ASNBLOCK-AS AS3215 129 55 74 57.4% RAIN AS3819 98 29 69 70.4% SIGNET AS813 227 160 67 29.5% UUNET Canada (ASN-UUNETCA-AS1) AS225 127 61 66 52.0% University of Virginia (VIRnet) AS3450 111 46 65 58.6% UTK AS1791 203 141 62 30.5% SprintLink Fort Worth TX AS1785 283 223 60 21.2% NYSERNet Backbone AS3996 110 51 59 53.6% FIRN AS2711 109 50 59 54.1% SUNBELT-AS AS855 123 67 56 45.5% NBTel AS839 90 35 55 61.1% North West Territories Regional N AS2551 348 293 55 15.8% NETCOM On-line Communication Serv --- 23Sep96 --- ASnum NetsNow NetsCIDR NetGain % Gain Description AS4230 1065 348 717 67.3% Embratel Brazil AS279 903 520 383 42.4% SURAnet Southern AS AS174 1271 924 347 27.3% Performance Systems International AS2493 725 454 271 37.4% i*internet AS3602 582 335 247 42.4% Intergrated Network Services Inc. AS3749 280 72 208 74.3% Tennessee Board of Regents AS3397 290 102 188 64.8% EMI-AS AS3804 387 244 143 37.0% WorldLinx 3 AS2048 259 126 133 51.4% State of Louisiana/Office of Tele AS1691 285 152 133 46.7% ANS-BLK1 AS568 373 264 109 29.2% JIS (Joint Interconnection Servic AS719 542 447 95 17.5% LANLINK autonomous system AS2386 230 136 94 40.9% INS-AS AS1790 337 250 87 25.8% SprintLink Washington D.C. AS1717 461 374 87 18.9% RENATER AS2704 267 182 85 31.8% HOOKUP-NET-A AS721 342 263 79 23.1% DLA-ASNBLOCK-AS AS3215 129 55 74 57.4% RAIN AS3819 98 29 69 70.4% SIGNET AS813 227 162 65 28.6% UUNET Canada (ASN-UUNETCA-AS1) AS3450 112 47 65 58.0% UTK AS1791 204 142 62 30.4% SprintLink Fort Worth TX AS1785 283 223 60 21.2% NYSERNet Backbone AS3996 111 52 59 53.2% FIRN AS2711 110 51 59 53.6% SUNBELT-AS AS855 123 67 56 45.5% NBTel AS839 90 35 55 61.1% North West Territories Regional N AS2551 349 294 55 15.8% NETCOM On-line Communication Serv AS701 789 739 50 6.3% Alternet AS560 348 298 50 14.4% BBN Planet, New England Region (N --- 22Sep96 --- ASnum NetsNow NetsCIDR NetGain % Gain Description AS4230 1090 343 747 68.5% Embratel Brazil AS719 1002 595 407 40.6% LANLINK autonomous system AS279 898 517 381 42.4% SURAnet Southern AS AS174 1256 913 343 27.3% Performance Systems International AS2493 724 454 270 37.3% i*internet AS3602 582 335 247 42.4% Intergrated Network Services Inc. AS3749 281 73 208 74.0% Tennessee Board of Regents AS3397 290 102 188 64.8% EMI-AS AS2048 337 154 183 54.3% State of Louisiana/Office of Tele AS3804 382 241 141 36.9% WorldLinx 3 AS1 407 268 139 34.2% BBN Planet backbone AS1691 288 152 136 47.2% ANS-BLK1 AS568 349 249 100 28.7% JIS (Joint Interconnection Servic AS2386 230 136 94 40.9% INS-AS AS1717 460 370 90 19.6% RENATER AS1790 337 250 87 25.8% SprintLink Washington D.C. AS2704 268 182 86 32.1% HOOKUP-NET-A AS721 342 263 79 23.1% DLA-ASNBLOCK-AS AS3215 129 55 74 57.4% RAIN AS3819 98 29 69 70.4% SIGNET AS3450 112 47 65 58.0% UTK AS1791 204 142 62 30.4% SprintLink Fort Worth TX AS1785 284 222 62 21.8% NYSERNet Backbone AS3996 111 52 59 53.2% FIRN AS2711 109 50 59 54.1% SUNBELT-AS AS813 215 158 57 26.5% UUNET Canada (ASN-UUNETCA-AS1) AS855 122 67 55 45.1% NBTel AS839 90 35 55 61.1% North West Territories Regional N AS2551 350 295 55 15.7% NETCOM On-line Communication Serv AS4454 61 11 50 82.0% OIR Telecommunications, State of --- 21Sep96 --- ASnum NetsNow NetsCIDR NetGain % Gain Description AS4230 961 354 607 63.2% Embratel Brazil AS719 1004 596 408 40.6% LANLINK autonomous system AS279 873 513 360 41.2% SURAnet Southern AS AS174 1273 926 347 27.3% Performance Systems International AS2493 724 454 270 37.3% i*internet AS3602 582 335 247 42.4% Intergrated Network Services Inc. AS3749 280 75 205 73.2% Tennessee Board of Regents AS3397 290 102 188 64.8% EMI-AS AS1 461 297 164 35.6% BBN Planet backbone AS2048 309 148 161 52.1% State of Louisiana/Office of Tele AS3804 387 244 143 37.0% WorldLinx 3 AS1691 288 152 136 47.2% ANS-BLK1 AS568 371 261 110 29.6% JIS (Joint Interconnection Servic AS86 298 189 109 36.6% SURAnet Northern AS AS2386 230 136 94 40.9% INS-AS AS1717 461 369 92 20.0% RENATER AS560 429 339 90 21.0% BBN Planet, New England Region (N AS1790 338 251 87 25.7% SprintLink Washington D.C. AS2704 271 185 86 31.7% HOOKUP-NET-A AS721 345 265 80 23.2% DLA-ASNBLOCK-AS AS3215 129 55 74 57.4% RAIN AS3819 98 29 69 70.4% SIGNET AS813 225 159 66 29.3% UUNET Canada (ASN-UUNETCA-AS1) AS3450 112 47 65 58.0% UTK AS1791 204 142 62 30.4% SprintLink Fort Worth TX AS1785 284 222 62 21.8% NYSERNet Backbone AS3996 111 52 59 53.2% FIRN AS2711 108 49 59 54.6% SUNBELT-AS AS855 123 68 55 44.7% NBTel AS839 90 35 55 61.1% North West Territories Regional N --- 20Sep96 --- ASnum NetsNow NetsCIDR NetGain % Gain Description AS279 985 560 425 43.1% SURAnet Southern AS AS719 1004 596 408 40.6% LANLINK autonomous system AS174 1305 944 361 27.7% Performance Systems International AS2493 725 454 271 37.4% i*internet AS3602 582 335 247 42.4% Intergrated Network Services Inc. AS2048 344 150 194 56.4% State of Louisiana/Office of Tele AS3749 264 74 190 72.0% Tennessee Board of Regents AS3397 290 102 188 64.8% EMI-AS AS1 462 298 164 35.5% BBN Planet backbone AS3804 383 242 141 36.8% WorldLinx 3 AS1691 288 155 133 46.2% ANS-BLK1 AS4230 336 206 130 38.7% Embratel Brazil AS86 299 190 109 36.5% SURAnet Northern AS AS568 356 257 99 27.8% JIS (Joint Interconnection Servic AS2386 233 138 95 40.8% INS-AS AS1717 458 367 91 19.9% RENATER AS560 429 340 89 20.7% BBN Planet, New England Region (N AS2704 272 184 88 32.4% HOOKUP-NET-A AS1790 338 251 87 25.7% SprintLink Washington D.C. AS721 345 264 81 23.5% DLA-ASNBLOCK-AS AS3215 129 55 74 57.4% RAIN AS813 232 161 71 30.6% UUNET Canada (ASN-UUNETCA-AS1) AS3819 98 29 69 70.4% SIGNET AS3450 112 47 65 58.0% UTK AS701 874 812 62 7.1% Alternet AS1791 204 142 62 30.4% SprintLink Fort Worth TX AS1785 284 222 62 21.8% NYSERNet Backbone AS3996 114 53 61 53.5% FIRN AS2711 110 51 59 53.6% SUNBELT-AS AS855 125 68 57 45.6% NBTel 2) Weekly Delta This a daily snapshot of changes in classfull routes being withdrawn and added. the deltas are calculated over a rolling 7 day period. Please bear in mind this is purely a "snapshot" and a large flucuation could be caused by a connectivity problem for example. However, this does give some indication of service providers that are moving to classless routing. Top 20 Withdrawn Routes from 20Sep96 to 27Sep96 -394 AS1717 RENATER -135 AS279 SURAnet Southern AS -103 AS1740 CERFnet -68 AS701 Alternet -59 AS2941 CSCNS-AS -55 AS4262 CERFnet Los Angeles SMDS -37 AS174 Performance Systems International -36 AS1 BBN Planet backbone -35 AS3930 FERC-FED-US -32 AS2551 NETCOM On-line Communication Serv -30 AS560 BBN Planet, New England Region (N -26 AS2914 RGnet/TLGnet SF -24 AS3491 CAIS-ASN -17 AS3566 JRIVER-LINK -16 AS1257 SWIPnet Swedish IP Network -15 AS1263 NSN-TEST-AS -11 AS200 BBN Planet Western Region -10 AS721 DLA-ASNBLOCK-AS -9 AS71 Hewlett-Packard -7 AS2277 ECUANET Top 20 Added Routes from 20Sep96 to 27Sep96 80 AS86 SURAnet Northern AS 45 AS4175 CONNECT-NCM 31 AS2493 i*internet 30 AS1275 DFN-IP 29 AS4387 RECYT 24 AS8001 UNKNOWN 21 AS3915 Best Internet Communications, Inc 20 AS225 University of Virginia (VIRnet) 19 AS6536 MOUNTAINNET 18 AS4433 ACCESS-ONE 14 AS568 JIS (Joint Interconnection Servic 11 AS6401 eConnect 10 AS3397 EMI-AS 9 AS3749 Tennessee Board of Regents 8 AS4174 CONNECT-COM 7 AS6739 Autonomous System number for Belg 6 AS3561 MCI 5 AS549 ONet Backbone 4 AS3720 TIMS-AS 3 AS5746 Celestar 3) Interesting aggregates List of possibly interesting aggregates --------------------------------------- aggregate origin-AS AS Description 9.2.0.0/16 AS1747 IBM Watson, Yorktown Heights, 9.20.0.0/17 AS2686 Autonomous System number for I 9.67.0.0/19 AS3561 MCI 24.0.0.0/14 AS6172 @Home Corp 24.48.0.0/18 AS1677 ANS Hartford - CNSS 53 24.64.0.0/19 AS6327 Shaw Fiberlink Ltd. 24.64.32.0/19 AS6327 Shaw Fiberlink Ltd. 24.96.0.0/18 AS6541 GTE Intelligent Network Servic 24.112.0.0/18 AS6463 Rogers Network Services 24.113.0.0/18 AS6177 SPRINTLINK11 24.124.0.0/18 AS3561 MCI 24.128.0.0/18 AS7015 UNKNOWN 24.129.0.0/18 AS7017 UNKNOWN 24.131.0.0/18 AS7016 UNKNOWN 38.231.198.0/24 AS3951 ICONNET 57.12.0.0/16 AS5384 Etisalat Emirates Internet 128.145.228.0/24 AS174 Performance Systems Internatio 128.167.1.0/24 AS1 BBN Planet backbone 128.188.1.0/24 AS560 BBN Planet, New England Region 128.193.0.0/19 AS4201 Oregon State University 129.181.216.0/22 AS517 Xlink 130.168.105.0/24 AS1270 EUnet Germany 130.168.115.0/24 AS1270 EUnet Germany 130.168.125.0/24 AS1270 EUnet Germany 130.188.2.0/24 AS565 VTT autonomous system 130.188.3.0/24 AS565 VTT autonomous system 130.188.150.0/24 AS565 VTT autonomous system 130.188.252.0/24 AS565 VTT autonomous system 130.205.64.0/18 AS3561 MCI 130.252.178.0/24 AS1321 ANS San Francisco - DNSS 11 131.114.192.0/18 AS2598 Consiglio Nazionale delle Rice 131.115.211.0/24 AS3301 TeliaNet Sweden 131.117.0.0/17 AS559 SWITCH, Swiss Academic and Res 132.235.204.0/24 AS3561 MCI 134.33.100.0/24 AS701 Alternet 134.198.8.0/21 AS3593 Eastern Pennsylvania Internet 134.198.16.0/21 AS3593 Eastern Pennsylvania Internet 134.198.24.0/21 AS3593 Eastern Pennsylvania Internet 134.198.32.0/21 AS3593 Eastern Pennsylvania Internet 134.198.40.0/21 AS3593 Eastern Pennsylvania Internet 134.198.48.0/21 AS3593 Eastern Pennsylvania Internet 134.198.56.0/21 AS3593 Eastern Pennsylvania Internet 134.198.64.0/21 AS3593 Eastern Pennsylvania Internet 134.198.72.0/21 AS3593 Eastern Pennsylvania Internet 134.198.96.0/21 AS3593 Eastern Pennsylvania Internet 134.198.168.0/21 AS3593 Eastern Pennsylvania Internet 134.198.192.0/21 AS3593 Eastern Pennsylvania Internet 134.198.232.0/21 AS3593 Eastern Pennsylvania Internet 134.198.240.0/21 AS3593 Eastern Pennsylvania Internet 134.204.14.0/24 AS3561 MCI 134.204.176.0/24 AS3561 MCI 134.241.109.0/24 AS560 BBN Planet, New England Region 135.14.65.0/24 AS3111 Internet Direct Inc. (ASN-DIRE 135.16.150.0/24 AS560 BBN Planet, New England Region 135.37.2.0/24 AS3561 MCI 135.37.4.0/24 AS3561 MCI 135.37.10.0/24 AS3561 MCI 135.37.14.0/24 AS3561 MCI 135.40.66.0/24 AS3561 MCI 136.140.9.0/24 AS3561 MCI 137.62.197.0/24 AS1794 SprintLink Pennsauken NJ 138.95.80.0/24 AS701 Alternet 138.108.100.0/24 AS3561 MCI 138.182.252.0/24 AS5855 Secretary of the Navy 138.182.254.0/24 AS5855 Secretary of the Navy 139.46.35.0/24 AS560 BBN Planet, New England Region 139.61.102.0/24 AS3111 Internet Direct Inc. (ASN-DIRE 139.61.103.0/24 AS3111 Internet Direct Inc. (ASN-DIRE 139.162.128.0/17 AS1136 Unisource Internet Service NL 140.10.12.0/24 AS701 Alternet 140.188.86.0/24 AS174 Performance Systems Internatio 140.188.129.0/24 AS174 Performance Systems Internatio 140.188.198.0/24 AS174 Performance Systems Internatio 140.231.44.0/24 AS3561 MCI 141.227.111.0/24 AS2529 Demon Internet Ltd 142.77.19.0/24 AS813 UUNET Canada (ASN-UUNETCA-AS1) 142.77.248.0/24 AS813 UUNET Canada (ASN-UUNETCA-AS1) 143.93.32.0/19 AS517 Xlink 143.222.116.0/24 AS3407 Interpath 143.252.80.0/24 AS2856 BTnet UK Regional network 144.192.181.0/24 AS4200 AGIS (Apex Global Information 144.199.161.0/24 AS1238 ICM Malaysia (MIMOS) connectee 144.224.10.0/24 AS1239 SprintLink Backbone 144.224.11.0/24 AS1239 SprintLink Backbone 144.224.12.0/24 AS1239 SprintLink Backbone 144.224.13.0/24 AS6176 SPRINTLINK10 144.224.14.0/24 AS6176 SPRINTLINK10 144.224.15.0/24 AS6176 SPRINTLINK10 144.224.16.0/24 AS6176 SPRINTLINK10 144.224.20.0/24 AS1239 SprintLink Backbone 144.224.21.0/24 AS1239 SprintLink Backbone 144.224.22.0/24 AS1239 SprintLink Backbone 144.224.23.0/24 AS6175 SPRINTLINK9 144.224.24.0/24 AS6175 SPRINTLINK9 144.224.25.0/24 AS6175 SPRINTLINK9 144.224.26.0/24 AS6175 SPRINTLINK9 144.228.20.0/24 AS1239 SprintLink Backbone 144.228.22.0/24 AS1790 SprintLink Washington D.C. 144.228.23.0/24 AS1790 SprintLink Washington D.C. 144.228.25.0/24 AS1790 SprintLink Washington D.C. 144.228.29.0/24 AS1790 SprintLink Washington D.C. 144.228.30.0/24 AS1239 SprintLink Backbone 144.228.37.0/24 AS1791 SprintLink Fort Worth TX 144.228.38.0/24 AS1791 SprintLink Fort Worth TX 144.228.39.0/24 AS1791 SprintLink Fort Worth TX 144.228.40.0/24 AS1239 SprintLink Backbone 144.228.41.0/24 AS1239 SprintLink Backbone 144.228.42.0/24 AS1239 SprintLink Backbone 144.228.44.0/24 AS1239 SprintLink Backbone 144.228.47.0/24 AS1792 SprintLink Stockton CA 144.228.48.0/24 AS1792 SprintLink Stockton CA 144.228.49.0/24 AS1792 SprintLink Stockton CA 144.228.50.0/24 AS1239 SprintLink Backbone 144.228.54.0/24 AS1239 SprintLink Backbone 144.228.55.0/24 AS1793 SprintLink Chicago IL 144.228.57.0/24 AS1793 SprintLink Chicago IL 144.228.58.0/24 AS1793 SprintLink Chicago IL 144.228.59.0/24 AS1793 SprintLink Chicago IL 144.228.60.0/24 AS1239 SprintLink Backbone 144.228.63.0/24 AS1794 SprintLink Pennsauken NJ 144.228.64.0/24 AS1794 SprintLink Pennsauken NJ 144.228.65.0/24 AS1794 SprintLink Pennsauken NJ 144.228.66.0/24 AS1794 SprintLink Pennsauken NJ 144.228.67.0/24 AS1794 SprintLink Pennsauken NJ 144.228.68.0/24 AS1794 SprintLink Pennsauken NJ 144.228.69.0/24 AS1794 SprintLink Pennsauken NJ 144.228.70.0/24 AS1239 SprintLink Backbone 144.228.73.0/24 AS1795 SprintLink Anaheim CA 144.228.74.0/24 AS1795 SprintLink Anaheim CA 144.228.75.0/24 AS1795 SprintLink Anaheim CA 144.228.76.0/24 AS1795 SprintLink Anaheim CA 144.228.77.0/24 AS1795 SprintLink Anaheim CA 144.228.78.0/24 AS1795 SprintLink Anaheim CA 144.228.79.0/24 AS1795 SprintLink Anaheim CA 144.228.80.0/24 AS1239 SprintLink Backbone 144.228.83.0/24 AS6174 SPRINTLINK8 144.228.84.0/24 AS6174 SPRINTLINK8 144.228.85.0/24 AS6174 SPRINTLINK8 144.228.86.0/24 AS6174 SPRINTLINK8 144.228.90.0/24 AS1239 SprintLink Backbone 144.228.91.0/24 AS1239 SprintLink Backbone 144.228.92.0/24 AS1239 SprintLink Backbone 144.228.93.0/24 AS6177 SPRINTLINK11 144.228.94.0/24 AS6177 SPRINTLINK11 144.228.95.0/24 AS6177 SPRINTLINK11 144.228.96.0/24 AS6177 SPRINTLINK11 144.228.103.0/24 AS1239 SprintLink Backbone 144.228.104.0/24 AS1239 SprintLink Backbone 144.228.120.0/24 AS1790 SprintLink Washington D.C. 144.228.121.0/24 AS1790 SprintLink Washington D.C. 144.228.122.0/24 AS1790 SprintLink Washington D.C. 144.228.123.0/24 AS1790 SprintLink Washington D.C. 144.228.124.0/24 AS1790 SprintLink Washington D.C. 144.228.125.0/24 AS1790 SprintLink Washington D.C. 144.228.126.0/24 AS1790 SprintLink Washington D.C. 144.228.127.0/24 AS1790 SprintLink Washington D.C. 144.228.128.0/24 AS1790 SprintLink Washington D.C. 144.228.130.0/24 AS1791 SprintLink Fort Worth TX 144.228.131.0/24 AS1791 SprintLink Fort Worth TX 144.228.132.0/24 AS1791 SprintLink Fort Worth TX 144.228.133.0/24 AS1791 SprintLink Fort Worth TX 144.228.134.0/24 AS1791 SprintLink Fort Worth TX 144.228.135.0/24 AS1791 SprintLink Fort Worth TX 144.228.140.0/24 AS1792 SprintLink Stockton CA 144.228.141.0/24 AS1792 SprintLink Stockton CA 144.228.142.0/24 AS1792 SprintLink Stockton CA 144.228.143.0/24 AS1792 SprintLink Stockton CA 144.228.144.0/24 AS1792 SprintLink Stockton CA 144.228.145.0/24 AS1792 SprintLink Stockton CA 144.228.146.0/24 AS1792 SprintLink Stockton CA 144.228.148.0/24 AS1792 SprintLink Stockton CA 144.228.150.0/24 AS1793 SprintLink Chicago IL 144.228.151.0/24 AS1793 SprintLink Chicago IL 144.228.152.0/24 AS1793 SprintLink Chicago IL 144.228.153.0/24 AS1793 SprintLink Chicago IL 144.228.154.0/24 AS1793 SprintLink Chicago IL 144.228.155.0/24 AS1239 SprintLink Backbone 144.228.156.0/24 AS1793 SprintLink Chicago IL 144.228.157.0/24 AS1793 SprintLink Chicago IL 144.228.158.0/24 AS1793 SprintLink Chicago IL 144.228.160.0/24 AS1794 SprintLink Pennsauken NJ 144.228.161.0/24 AS1239 SprintLink Backbone 144.228.162.0/24 AS1794 SprintLink Pennsauken NJ 144.228.163.0/24 AS1794 SprintLink Pennsauken NJ 144.228.164.0/24 AS1794 SprintLink Pennsauken NJ 144.228.165.0/24 AS1794 SprintLink Pennsauken NJ 144.228.166.0/24 AS1792 SprintLink Stockton CA 144.228.170.0/24 AS1795 SprintLink Anaheim CA 144.228.214.0/24 AS1792 SprintLink Stockton CA 145.17.100.0/24 AS2856 BTnet UK Regional network 145.72.32.0/19 AS5484 BT Netherlands Regional Servic 145.72.64.0/19 AS5484 BT Netherlands Regional Servic 145.246.16.0/24 AS2856 BTnet UK Regional network 145.246.17.0/24 AS2856 BTnet UK Regional network 145.248.112.0/24 AS2706 HKSUPER 145.248.155.0/24 AS2706 HKSUPER 145.248.157.0/24 AS2706 HKSUPER 145.248.159.0/24 AS2706 HKSUPER 145.248.161.0/24 AS2706 HKSUPER 145.248.165.0/24 AS2706 HKSUPER 146.75.251.0/24 AS3301 TeliaNet Sweden 146.75.253.0/24 AS1257 SWIPnet Swedish IP Network 146.75.254.0/24 AS3301 TeliaNet Sweden 146.188.254.0/24 AS1849 PIPEX, Public IP EXchange 147.85.21.0/24 AS3951 ICONNET 147.85.25.0/24 AS3951 ICONNET 147.85.39.0/24 AS3951 ICONNET 147.85.44.0/24 AS3951 ICONNET 147.85.51.0/24 AS3951 ICONNET 147.85.115.0/24 AS3951 ICONNET 147.160.0.0/17 AS3561 MCI 147.160.128.0/18 AS3561 MCI 147.160.192.0/20 AS3561 MCI 147.160.208.0/20 AS3561 MCI 147.160.224.0/20 AS3561 MCI 147.160.224.0/19 AS3561 MCI 147.206.20.0/24 AS3561 MCI 148.59.5.0/24 AS2015 Msen, Inc. 148.59.242.0/24 AS2015 Msen, Inc. 148.59.242.0/24 AS1717 RENATER 148.94.210.0/24 AS5714 EDS-WEB 148.185.45.0/24 AS1849 PIPEX, Public IP EXchange 148.252.1.0/24 AS1849 PIPEX, Public IP EXchange 149.20.4.0/24 AS1239 SprintLink Backbone 149.20.64.0/24 AS701 Alternet 149.212.64.0/20 AS1759 Telecom Finland iNET 149.236.92.0/24 AS6292 FCI 150.185.128.0/18 AS1800 ICM-Atlantic 150.185.192.0/18 AS1800 ICM-Atlantic 151.185.7.0/24 AS279 SURAnet Southern AS 151.185.10.0/24 AS279 SURAnet Southern AS 152.129.186.0/24 AS4478 PNET-STL 152.163.199.0/24 AS2056 AOL-AS 152.163.200.0/24 AS2056 AOL-AS 152.163.231.0/24 AS2056 AOL-AS 152.163.232.0/23 AS2056 AOL-AS 152.163.234.0/23 AS2056 AOL-AS 152.179.0.0/17 AS1321 ANS San Francisco - DNSS 11 152.184.0.0/17 AS1333 ANS Atlanta - DNSS 107 152.184.128.0/17 AS1330 ANS St. Louis - DNSS 83 152.185.0.0/17 AS1332 ANS Denver - DNSS 99 152.185.128.0/17 AS1328 ANS Houston - DNSS 67 152.186.0.0/18 AS1328 ANS Houston - DNSS 67 152.186.64.0/18 AS1335 ANS Honolulu - CNSS 120 152.186.128.0/17 AS1322 ANS Los Angeles - DNSS 19 152.187.0.0/17 AS1321 ANS San Francisco - DNSS 11 152.187.128.0/17 AS1326 ANS Hartford - DNSS 51 152.189.0.0/18 AS1329 ANS Greensboro - DNSS 75 152.189.128.0/17 AS1327 ANS Washington D.C. - DNSS 59 152.189.184.0/22 AS1667 ANS-BLK1 152.190.0.0/17 AS1323 ANS Chicago - DNSS 27 152.191.0.0/17 AS1331 ANS Seattle - DNSS 91 152.191.128.0/17 AS1334 ANS Albuquerque - CNSS 112 153.2.164.0/24 AS3561 MCI 153.96.80.0/21 AS517 Xlink 153.96.92.0/24 AS517 Xlink 153.96.188.0/22 AS517 Xlink 153.96.230.0/24 AS517 Xlink 155.39.191.0/24 AS2685 IGN OpenNet - US 155.134.60.0/24 AS701 Alternet 155.140.124.0/24 AS1849 PIPEX, Public IP EXchange 155.173.244.0/24 AS3561 MCI 155.203.254.0/24 AS3561 MCI 155.229.176.0/22 AS7045 UNKNOWN 156.46.0.0/17 AS4550 Alpha.net Corporation (ASN-AN- 156.46.128.0/17 AS4550 Alpha.net Corporation (ASN-AN- 156.51.204.0/24 AS3301 TeliaNet Sweden 156.114.200.0/24 AS2529 Demon Internet Ltd 157.25.64.0/23 AS1887 NASK 157.25.98.0/24 AS1887 NASK 157.184.150.0/24 AS1330 ANS St. Louis - DNSS 83 157.232.100.0/24 AS3561 MCI 158.43.200.0/24 AS701 Alternet 158.118.51.0/24 AS701 Alternet 158.155.24.0/22 AS1221 AARNET-AS 158.174.254.0/24 AS2856 BTnet UK Regional network 159.24.7.0/24 AS4286 IMCI 159.87.34.0/24 AS200 BBN Planet Western Region 159.179.0.0/24 AS3561 MCI 159.197.158.0/23 AS2529 Demon Internet Ltd 159.245.84.0/22 AS1849 PIPEX, Public IP EXchange 159.245.104.0/22 AS1849 PIPEX, Public IP EXchange 160.92.0.0/17 AS3215 RAIN 160.92.128.0/24 AS3215 RAIN 160.92.129.0/24 AS2917 OLEANE - PIPEX International 160.92.130.0/23 AS3215 RAIN 160.92.132.0/22 AS3215 RAIN 160.92.136.0/21 AS3215 RAIN 160.92.144.0/20 AS3215 RAIN 160.92.160.0/19 AS3215 RAIN 160.92.192.0/18 AS3215 RAIN 160.104.0.0/17 AS701 Alternet 160.104.128.0/17 AS1290 PSINet UK Ltd. 161.22.0.0/24 AS1790 SprintLink Washington D.C. 161.51.224.0/20 AS1849 PIPEX, Public IP EXchange 161.52.192.0/19 AS2845 SUNET-LUND 161.120.6.0/24 AS3561 MCI 161.223.220.0/22 AS1 BBN Planet backbone 161.223.224.0/24 AS1 BBN Planet backbone 162.81.141.0/24 AS3561 MCI 163.12.0.0/23 AS3576 PREPnet-EAST 163.12.5.0/24 AS3576 PREPnet-EAST 163.12.16.0/22 AS3576 PREPnet-EAST 163.12.21.0/24 AS3576 PREPnet-EAST 163.12.22.0/24 AS3576 PREPnet-EAST 163.12.23.0/24 AS3576 PREPnet-EAST 163.12.24.0/21 AS3576 PREPnet-EAST 163.12.32.0/19 AS3576 PREPnet-EAST 163.12.64.0/20 AS3576 PREPnet-EAST 163.12.81.0/24 AS3576 PREPnet-EAST 163.12.84.0/22 AS3576 PREPnet-EAST 163.12.88.0/21 AS3576 PREPnet-EAST 163.12.96.0/19 AS3576 PREPnet-EAST 163.12.128.0/21 AS3576 PREPnet-EAST 163.12.136.0/22 AS3576 PREPnet-EAST 163.12.144.0/20 AS3576 PREPnet-EAST 163.12.160.0/19 AS3576 PREPnet-EAST 163.12.192.0/21 AS3576 PREPnet-EAST 163.12.240.0/20 AS3576 PREPnet-EAST 163.49.131.0/24 AS3561 MCI 163.49.132.0/22 AS3561 MCI 163.49.136.0/22 AS3561 MCI 163.49.140.0/23 AS3561 MCI 163.49.142.0/24 AS3561 MCI 163.168.212.0/24 AS3303 Unisource Business Networks (S 163.168.212.0/24 AS1717 RENATER 163.249.43.0/24 AS3739 NEWNET 163.249.53.0/24 AS3739 NEWNET 163.249.54.0/24 AS3739 NEWNET 163.249.57.0/24 AS3739 NEWNET 163.249.140.0/22 AS3739 NEWNET 163.249.160.0/21 AS3739 NEWNET 163.249.168.0/24 AS3739 NEWNET 163.249.169.0/24 AS3739 NEWNET 163.249.170.0/24 AS3739 NEWNET 164.99.56.192/26 AS2041 CRL-GATE 164.100.64.0/20 AS3561 MCI 164.100.80.0/24 AS4755 Videsh Sanchar Nigam Ltd. Indi 164.100.81.0/24 AS3561 MCI 164.100.82.0/23 AS3561 MCI 164.100.84.0/22 AS3561 MCI 164.100.88.0/21 AS3561 MCI 164.100.96.0/19 AS3561 MCI 164.100.167.0/24 AS3561 MCI 164.100.199.0/24 AS4755 Videsh Sanchar Nigam Ltd. Indi 164.103.3.0/24 AS3561 MCI 164.131.247.0/24 AS3215 RAIN 164.131.248.0/24 AS3215 RAIN 164.224.208.0/20 AS5855 Secretary of the Navy 165.108.130.0/24 AS3561 MCI 165.113.197.0/24 AS6006 UNKNOWN 165.113.198.0/24 AS6006 UNKNOWN 165.113.199.0/24 AS6006 UNKNOWN 165.113.211.0/24 AS6006 UNKNOWN 165.113.219.0/24 AS6006 UNKNOWN 165.166.123.0/24 AS3561 MCI 165.215.64.0/18 AS4183 CompuServe, Incorporated 165.215.191.0/24 AS5090 CWI-NYD 165.247.33.0/24 AS5696 Primary AS for GoodNet 166.38.40.0/24 AS3561 MCI 166.147.0.0/18 AS3561 MCI 166.147.64.0/18 AS3561 MCI 166.147.128.0/18 AS3561 MCI 166.147.192.0/18 AS3561 MCI 166.150.0.0/18 AS3561 MCI 166.150.64.0/18 AS3561 MCI 166.150.128.0/18 AS3561 MCI 166.150.192.0/18 AS3561 MCI 166.151.0.0/18 AS3561 MCI 166.151.64.0/18 AS3561 MCI 166.151.128.0/18 AS3561 MCI 166.151.192.0/18 AS3561 MCI 167.72.128.0/24 AS3561 MCI 167.77.32.0/24 AS3561 MCI 167.105.232.0/24 AS3561 MCI 167.170.6.0/23 AS3313 I.Net S.p.A. 167.170.32.0/23 AS3313 I.Net S.p.A. 167.208.125.0/24 AS3561 MCI 168.14.1.0/24 AS3561 MCI 168.14.2.0/23 AS3561 MCI 168.14.4.0/22 AS3561 MCI 168.14.8.0/21 AS3561 MCI 168.14.16.0/20 AS3561 MCI 168.29.0.0/17 AS3492 ATLANTA 168.175.70.0/24 AS3561 MCI 168.175.170.0/24 AS3561 MCI 168.175.171.0/24 AS3561 MCI 168.175.172.0/24 AS3561 MCI 168.224.128.0/24 AS2856 BTnet UK Regional network 168.247.253.0/24 AS174 Performance Systems Internatio 168.247.254.0/24 AS174 Performance Systems Internatio 169.132.80.0/24 AS5000 IDT Corporation 169.137.170.0/24 AS3407 Interpath 169.200.1.0/24 AS3561 MCI 170.115.249.0/24 AS4969 Net Access 170.194.51.0/24 AS1849 PIPEX, Public IP EXchange 170.215.192.0/20 AS5650 Electric Lightwave Inc. and XM 171.25.128.0/20 AS3301 TeliaNet Sweden 171.25.144.0/21 AS3301 TeliaNet Sweden 171.25.152.0/21 AS3301 TeliaNet Sweden 171.30.170.0/24 AS2856 BTnet UK Regional network 192.103.70.0/26 AS1673 ANS-BLK1 192.103.74.0/27 AS1673 ANS-BLK1 194.23.1.36/30 AS3305 Internet Service Provider back 194.51.28.152/30 AS1667 ANS-BLK1 194.178.245.32/28 AS5417 Demon Internet Ltd 194.237.174.0/29 AS3301 TeliaNet Sweden 194.237.174.8/29 AS3301 TeliaNet Sweden 194.237.174.32/27 AS3308 TeliaNet Denmark 195.38.9.6/32 AS6739 Autonomous System number for B 195.212.2.0/28 AS2686 Autonomous System number for I 195.212.6.0/26 AS2686 Autonomous System number for I 195.212.48.0/27 AS2686 Autonomous System number for I 195.212.69.0/26 AS2686 Autonomous System number for I 195.212.74.0/27 AS2686 Autonomous System number for I 195.212.78.0/28 AS2686 Autonomous System number for I 195.212.106.0/26 AS2686 Autonomous System number for I 195.212.110.0/27 AS2686 Autonomous System number for I 195.212.198.0/25 AS2686 Autonomous System number for I 195.212.226.0/28 AS2686 Autonomous System number for I 198.83.24.0/26 AS1673 ANS-BLK1 198.83.47.0/26 AS1673 ANS-BLK1 198.83.195.0/26 AS1673 ANS-BLK1 198.83.209.0/26 AS1673 ANS-BLK1 198.83.210.0/26 AS1673 ANS-BLK1 199.99.247.32/27 AS174 Performance Systems Internatio 199.221.28.0/26 AS1673 ANS-BLK1 199.221.38.0/27 AS1673 ANS-BLK1 199.221.47.0/25 AS1673 ANS-BLK1 199.222.34.0/26 AS1673 ANS-BLK1 199.233.98.0/25 AS6082 MAI Network Services 199.233.98.128/25 AS6082 MAI Network Services 202.50.137.64/27 AS2687 OpenNet-AP 204.148.62.0/26 AS1673 ANS-BLK1 204.148.68.0/26 AS1673 ANS-BLK1 204.151.106.0/26 AS1673 ANS-BLK1 204.151.152.0/26 AS1673 ANS-BLK1 205.156.223.176/28 AS2702 Spry AS From owner-apops Sat Sep 28 20:06:52 1996 Received: (from daemon@localhost) by teckla.apnic.net (8.7.1/8.7.1) id UAA22567 for apops-outgoing; Sat, 28 Sep 1996 20:06:52 +0900 (JST) Received: from marikit.iphil.net (map@marikit.iphil.net [203.176.0.4]) by teckla.apnic.net (8.7.1/8.7.1) with ESMTP id UAA22562 for ; Sat, 28 Sep 1996 20:06:45 +0900 (JST) Received: (from map@localhost) by marikit.iphil.net (8.7.6/8.6.9) id EAA32358 for apops@apnic.net; Sat, 28 Sep 1996 04:09:39 -0700 From: "Miguel A.L. Paraz" Message-Id: <199609281109.EAA32358@marikit.iphil.net> Subject: Very fast IP, no ATM... To: apops@apnic.net Date: Sat, 28 Sep 1996 19:09:38 +0800 (GMT+0800) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-apops@apnic.net Precedence: bulk -----BEGIN PGP SIGNED MESSAGE----- Hi, Peter Lothberg wrote: > Was the worlds first transatlantic 155Mbit native IP service brought into > operation by Sprint/USA and Tele2/Sweden. David, did you forward this here to get us jealous? :) Anyway, besides cost, provisioning is also a problem. We want to order a T1 but apparently it can't be available very quickly, since it affects how our international line provider allocates from the cable people. Thus, we have to get it in increments. -----BEGIN PGP SIGNATURE----- Version: 2.6.i iQB1AgUBMk0Hb7sCsZ1D8NARAQErKwMApF+GxyTKqGlWw2M05UokolgCDVNCMgPB 0POt+t4LlF5zAz3eXLsvaW3aSBMnhxOgziKEzBtOTy+4CnHaWa4TVwRYnv4jRg93 pfsU1sSKdZf5b44Of/8CpLJ+9dljuiVa =rfir -----END PGP SIGNATURE----- -- miguel a.l. paraz iphil communications, makati city, ph PGP ID: 0x43F0D011 http://www.iphil.net isp/intranet design & implementation From owner-apops Sat Sep 28 20:10:39 1996 Received: (from daemon@localhost) by teckla.apnic.net (8.7.1/8.7.1) id UAA22614 for apops-outgoing; Sat, 28 Sep 1996 20:10:39 +0900 (JST) Received: from marikit.iphil.net (map@marikit.iphil.net [203.176.0.4]) by teckla.apnic.net (8.7.1/8.7.1) with ESMTP id UAA22607 for ; Sat, 28 Sep 1996 20:10:34 +0900 (JST) Received: (from map@localhost) by marikit.iphil.net (8.7.6/8.6.9) id EAA32412 for apops@apnic.net; Sat, 28 Sep 1996 04:13:31 -0700 From: "Miguel A.L. Paraz" Message-Id: <199609281113.EAA32412@marikit.iphil.net> Subject: The Cidr Report To: apops@apnic.net Date: Sat, 28 Sep 1996 19:13:30 +0800 (GMT+0800) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-apops@apnic.net Precedence: bulk -----BEGIN PGP SIGNED MESSAGE----- Hi, Tony Bates wrote: > 1) Gains by aggregating at the origin AS level Looks like there are no Asia-Pacific routes here - are we doing a good job, or are we all hidden under the our transit providers' AS's? -----BEGIN PGP SIGNATURE----- Version: 2.6.i iQB1AgUBMk0IWLsCsZ1D8NARAQE0lwL7BGLMwnDVUbMu3i2QNuoIDiJF7EDZBS/Y 2eGwnR2cw3iod2lanadttcraEBWOVyuDqj7OImtGQBuwnAbLgcPFS15yMA8TyHh/ r30Pgmc9i0jubKT0XAujcgo99XcyGHot =edbd -----END PGP SIGNATURE----- -- miguel a.l. paraz iphil communications, makati city, ph PGP ID: 0x43F0D011 http://www.iphil.net isp/intranet design & implementation From owner-apops Sun Sep 29 11:16:30 1996 Received: (from daemon@localhost) by teckla.apnic.net (8.7.1/8.7.1) id LAA27541 for apops-outgoing; Sun, 29 Sep 1996 11:16:30 +0900 (JST) Received: from nostromo.jp.apnic.net (root@[192.244.184.5]) by teckla.apnic.net (8.7.1/8.7.1) with ESMTP id LAA27528; Sun, 29 Sep 1996 11:16:26 +0900 (JST) Received: from ronin.apnic.net (davidc@localhost [127.0.0.1]) by nostromo.jp.apnic.net (8.7.3/8.7.3) with ESMTP id VAA20718; Sat, 28 Sep 1996 21:48:31 GMT Message-Id: <199609282148.VAA20718@nostromo.jp.apnic.net> To: "Miguel A.L. Paraz" cc: apops@apnic.net Subject: Re: Very fast IP, no ATM... In-reply-to: Your message of "Sat, 28 Sep 1996 19:09:38 +0800." <199609281109.EAA32358@marikit.iphil.net> Date: Sat, 28 Sep 1996 21:47:41 +0000 From: "David R. Conrad" Sender: owner-apops@apnic.net Precedence: bulk Hi, >David, did you forward this here to get us jealous? :) More foreshadowing the future... :-). >Anyway, besides cost, provisioning is also a problem. We want to >order a T1 but apparently it can't be available very quickly, since it >affects how our international line provider allocates from the cable >people. Thus, we have to get it in increments. The provisioning of trans-oceanic cable gets quite twisted -- I believe there will be a session on this at APRICOT in HK. Barry and/or Geoff Huston might be able to discuss this a bit as they have had some experiences in this area... Regards, -drc From owner-apops Sun Sep 29 16:27:55 1996 Received: (from daemon@localhost) by teckla.apnic.net (8.7.1/8.7.1) id QAA29003 for apops-outgoing; Sun, 29 Sep 1996 16:27:55 +0900 (JST) Received: from sunflower.singnet.com.sg (sunflower.singnet.com.sg [165.21.1.58]) by teckla.apnic.net (8.7.1/8.7.1) with SMTP id QAA28995 for ; Sun, 29 Sep 1996 16:26:39 +0900 (JST) Received: from ts900-1114.singnet.com.sg (ts900-1114.singnet.com.sg [165.21.160.66]) by sunflower.singnet.com.sg (8.6.12/8.6.9) with SMTP id PAA05779; Sun, 29 Sep 1996 15:28:18 +0800 Received: by ts900-1114.singnet.com.sg with Microsoft Mail id <01BBAE22.E0B1F260@ts900-1114.singnet.com.sg>; Sun, 29 Sep 1996 16:25:50 -0000 Message-ID: <01BBAE22.E0B1F260@ts900-1114.singnet.com.sg> From: Barry Raveendran Greene To: "'apops@apnic.net'" , "'Miguel A.L. Paraz'" Subject: Re: The Cidr Report Date: Sun, 29 Sep 1996 16:01:08 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Sender: owner-apops@apnic.net Precedence: bulk Hello Miguel, Miguel A.L. Paraz wrote: >Looks like there are no Asia-Pacific routes here - are we doing a good >job, or are we all hidden under the our transit providers' AS's? Need to put it perspective. Yes, no one with allocations from APNIC (in = 202/8 and 203/8) are in the top 50. What we're looking for is whether = the allocations that are going out (default /22) stay /22s or better.=20 Barry