From owner-apops@lists.apnic.net Mon Oct 2 13:21:14 2000 Received: (from majordom@localhost) by ns.apnic.net (8.9.3/8.9.3) id NAA109906; Mon, 2 Oct 2000 13:21:14 +1000 (EST) Received: from lint.cisco.com (lint.cisco.com [171.68.224.209]) by ns.apnic.net (8.9.3/8.9.3) with ESMTP id NAA109901 for ; Mon, 2 Oct 2000 13:21:11 +1000 (EST) Received: from pfs-laptop.cisco.com (bne-dhcp-66.cisco.com [144.254.153.66]) by lint.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id UAA09915; Sun, 1 Oct 2000 20:20:23 -0700 (PDT) Message-Id: <5.0.0.25.2.20001002131724.00a44da0@lint.cisco.com> X-Sender: philsmit@lint.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Mon, 02 Oct 2000 13:18:16 +1000 To: Neale Banks From: Philip Smith Subject: Re: [apops] using NTP/etc to measure n/w latency? Cc: apops@lists.apnic.net In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-apops@lists.apnic.net Precedence: bulk You could check out the Test Traffic project run by the RIPE NCC. More info at http://www.ripe.net/ripencc/mem-services/ttm/. It's some what more sophisticated than using NTP though... philip -- At 21:28 29/09/00 +1100, Neale Banks wrote: >Greetings all, > >Does anyone have any pointers to using the likes of NTP to sample network >latency? > >Needless to say, I'm looking for something more worthwhile than ping. > >Thanks, >Neale. > >* APOPS: Asia Pacific Operations Forum * >* To unsubscribe: send "unsubscribe" to apops-request@apnic.net * * APOPS: Asia Pacific Operations Forum * * To unsubscribe: send "unsubscribe" to apops-request@apnic.net * From owner-apops@lists.apnic.net Mon Oct 2 18:21:27 2000 Received: (from majordom@localhost) by ns.apnic.net (8.9.3/8.9.3) id SAA85714; Mon, 2 Oct 2000 18:21:27 +1000 (EST) Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by ns.apnic.net (8.9.3/8.9.3) with ESMTP id SAA85709 for ; Mon, 2 Oct 2000 18:21:24 +1000 (EST) Received: from x49.ripe.net (x49.ripe.net [193.0.1.49]) by birch.ripe.net (8.8.8/8.8.8) with ESMTP id KAA01097; Mon, 2 Oct 2000 10:13:31 +0200 (CEST) Received: from localhost (henk@localhost) by x49.ripe.net (8.8.8/8.8.5) with ESMTP id KAA29429; Mon, 2 Oct 2000 10:13:31 +0200 (CEST) X-Authentication-Warning: x49.ripe.net: henk owned process doing -bs Date: Mon, 2 Oct 2000 10:13:31 +0200 (CEST) From: "Henk Uijterwaal (RIPE-NCC)" To: Philip Smith cc: Neale Banks , apops@lists.apnic.net Subject: Re: [apops] using NTP/etc to measure n/w latency? In-Reply-To: <5.0.0.25.2.20001002131724.00a44da0@lint.cisco.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-apops@lists.apnic.net Precedence: bulk On Mon, 2 Oct 2000, Philip Smith wrote: > You could check out the Test Traffic project run by the RIPE NCC. More info > at http://www.ripe.net/ripencc/mem-services/ttm/. It's some what more > sophisticated than using NTP though... Thanks for posting the pointer! > At 21:28 29/09/00 +1100, Neale Banks wrote: > >Greetings all, > > > >Does anyone have any pointers to using the likes of NTP to sample network > >latency? The (fundamental) problem with using NTP is that the accuracy of NTP depends on the network latencies, which is also the quantity that you want to measure. Henk ------------------------------------------------------------------------------ Henk Uijterwaal Email: henk.uijterwaal@ripe.net RIPE Network Coordination Centre WWW: http://www.ripe.net/home/henk Singel 258 Phone: +31.20.535-4414, Fax -4445 1016 AB Amsterdam Home: +31.20.4195305 The Netherlands Mobile: +31.6.55861746 ------------------------------------------------------------------------------ A man can take a train and never reach his destination. (Kerouac, well before RFC2780). * APOPS: Asia Pacific Operations Forum * * To unsubscribe: send "unsubscribe" to apops-request@apnic.net * From owner-apops@lists.apnic.net Mon Oct 2 18:38:53 2000 Received: (from majordom@localhost) by ns.apnic.net (8.9.3/8.9.3) id SAA87883; Mon, 2 Oct 2000 18:38:52 +1000 (EST) Received: from marina.lowendale.com.au ([203.26.242.120]) by ns.apnic.net (8.9.3/8.9.3) with ESMTP id SAA87876 for ; Mon, 2 Oct 2000 18:38:49 +1000 (EST) Received: from localhost (neale@localhost) by marina.lowendale.com.au (8.9.3/8.9.3/Debian/GNU) with ESMTP id TAA23770; Mon, 2 Oct 2000 19:54:46 +1100 Date: Mon, 2 Oct 2000 19:54:44 +1100 (EST) From: Neale Banks To: apops@lists.apnic.net cc: "Henk Uijterwaal (RIPE-NCC)" , Philip Smith Subject: Re: [apops] using NTP/etc to measure n/w latency? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-apops@lists.apnic.net Precedence: bulk Thanks for the suggestions so far. On Mon, 2 Oct 2000, Henk Uijterwaal (RIPE-NCC) wrote: > The (fundamental) problem with using NTP is that the accuracy of NTP > depends on the network latencies, which is also the quantity that you want > to measure. Yes, I still haven't wrapped my brain around how NTP gets around this apparent paradox. Reading over the RFCs-various hasn't helped me so far. Assuming that NTP does solve this problem, My logic is that if it reliably extracts the one-way latency (how else do you set your clock from the remote? ;-) then this latency is indeed the holy grail I seek. I'm fast concluding that ideally both ends would have some kind of external reference (e.g. each of "nearby" stratum-1 or, better still, their own non-network reference like GPS) for my purposes, but I would prefer to solve this with a minimum number of such references. Regards, Neale. * APOPS: Asia Pacific Operations Forum * * To unsubscribe: send "unsubscribe" to apops-request@apnic.net * From owner-apops@lists.apnic.net Fri Oct 6 04:05:34 2000 Received: (from majordom@localhost) by ns.apnic.net (8.9.3/8.9.3) id EAA120865; Fri, 6 Oct 2000 04:05:34 +1000 (EST) Received: from whois3.apnic.net (whois3.apnic.net [203.37.255.102]) by ns.apnic.net (8.9.3/8.9.3) with ESMTP id EAA120851 for ; Fri, 6 Oct 2000 04:05:32 +1000 (EST) Received: from dev.apnic.net (IDENT:root@dev.apnic.net [203.37.255.120]) by whois3.apnic.net (8.10.1/UW7.1.1-NSC) with ESMTP id e95I5WI24631 for ; Fri, 6 Oct 2000 04:05:32 +1000 (EST) Received: (from cscora@localhost) by dev.apnic.net (8.9.3/8.9.3) id EAA21261 for apops@lists.apnic.net; Fri, 6 Oct 2000 04:05:31 +1000 From: Routing Analysis Message-Id: <200010051805.EAA21261@dev.apnic.net> Subject: [apops] Asia Pacific Weekly Routing Report Date: Fri, 6 Oct 2000 04:05:31 +1000 (EST) Reply-To: pfs@cisco.com To: apops@lists.apnic.net X-Mailer: fastmail [version 2.5 PL1] Sender: owner-apops@lists.apnic.net Precedence: bulk This is an automated weekly mailing sent to the APOPS list describing the state of the Internet Routing Table in the Asia Pacific Region. Daily listings are sent to bgp-stats@lists.apnic.net For a graphical representation, please see http://www.apnic.net/stats/bgp. If you have any comments please contact Philip Smith . Asia Pacific Report 06 Oct, 2000 Analysis Summary ---------------- BGP routing table entries examined: 90555 Origin ASes present in the Internet Routing Table: 8690 Origin ASes announcing only one prefix: 2924 Transit ASes present in the Internet Routing Table: 1173 Average AS path length visible in the Internet Routing Table: 5.3 Max AS path length visible: 16 Illegal AS announcements present in the Routing Table: 3 Non-routable prefixes present in the Routing Table: 0 Prefixes being announced from the IANA Reserved Address blocks: 1 Number of addresses announced to Internet: 1188470963 Equivalent to 70 /8s, 214 /16s and 160 /24s Percentage of available address space announced: 32.1 Percentage of allocated address space announced: 62.9 Percentage of available address space allocated: 51.0 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 13598 Prefixes being announced from the APNIC address blocks: 12122 APNIC Region origin ASes present in the Internet Routing Table: 1017 APNIC Region origin ASes announcing only one prefix: 338 APNIC Region transit ASes present in the Internet Routing Table: 161 Average APNIC Region AS path length visible: 5.1 Max APNIC Region AS path length visible: 13 Number of APNIC addresses announced to Internet: 56349981 Equivalent to 3 /8s, 91 /16s and 213 /24s Percentage of available APNIC address space announced: 66.3 APNIC AS Blocks 4608 - 4864, 7467 - 7722, 9216 - 10239, 17408 - 18431 APNIC Address Blocks 61/8, 202/7 and 210/7 APNIC Region per AS prefix count summary ---------------------------------------- ASN No of nets /19 equiv Description 1221 921 998 Telstra 2764 465 130 connect.com.au pty ltd 4740 376 84 Ozemail 2907 367 892 SINET Japan 7657 358 15 The Internet Group Limited 4755 346 131 VSNL India 9269 214 23 Hong Kong CTI 4618 207 56 Internet Thailand 4763 197 44 Telstra New Zealand 703 174 86 UUNET Technologies, Inc. 7545 171 6 TPG Internet Pty Ltd 4433 168 126 Access One Pty Ltd 7474 159 58 Optus Communications 9318 151 129 AS Object of HANARO Telecom i 4134 136 357 Data Communications Bureau 4786 136 7 NetConnect Communications Pty 7496 133 8 Power Up 9304 129 15 Hutchcity 4766 126 423 KORnet Powered BY Korea Telec Global Per AS prefix count summary ---------------------------------- ASN No of nets /19 equiv Description 701 2020 3318 UUNET Technologies, Inc. 1 994 4559 BBN Planet 1221 921 998 Telstra 7018 868 3024 AT&T 1785 834 787 Sprint ICM 7046 767 518 UUNET Technologies, Inc. 2914 702 1323 Verio, Inc. 1239 691 1740 Sprint ICM-Inria 816 667 160 UUNET Canada4 3561 614 1458 Cable & Wireless USA 174 608 2733 PSINet Inc. 705 552 34 UUNET Technologies, Inc. 8013 512 65 PSINet Ltd. Canada 3549 500 413 Frontier GlobalCenter 209 474 544 Qwest 271 466 380 BCnet Backbone 2764 465 130 connect.com.au pty ltd 3908 447 289 Supernet, Inc. 4293 434 63 Cable & Wireless USA List of Illegal AS's (Global) ----------------------------- Bad AS Designation Network Transit AS Description 65005 PRIVATE 63.101.102.0/24 7407 MCI Telecom. State G 64602 PRIVATE 63.236.57.0/24 209 Qwest 64605 PRIVATE 208.47.206.0/24 209 Qwest Advertised IANA Reserved Addresses ---------------------------------- Network Origin AS Description 27.0.0.0/16 1221 Telstra Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:23 /9:4 /10:5 /11:9 /12:29 /13:59 /14:172 /15:276 /16:6556 /17:934 /18:1873 /19:5958 /20:3784 /21:3849 /22:5832 /23:7833 /24:52421 /25:180 /26:335 /27:87 /28:74 /29:88 /30:87 /31:0 /32:87 End of report * APOPS: Asia Pacific Operations Forum * * To unsubscribe: send "unsubscribe" to apops-request@apnic.net * From owner-apops@lists.apnic.net Sat Oct 7 05:03:42 2000 Received: (from majordom@localhost) by ns.apnic.net (8.9.3/8.9.3) id FAA120110; Sat, 7 Oct 2000 05:03:41 +1000 (EST) Received: from lovefm.cisco.com (lovefm.cisco.com [171.71.217.41]) by ns.apnic.net (8.9.3/8.9.3) with SMTP id FAA120104 for ; Sat, 7 Oct 2000 05:03:39 +1000 (EST) Received: from cisco.com (localhost.cisco.com [127.0.0.1]) by lovefm.cisco.com (8.6.12/8.6.5) with ESMTP id MAA25302; Fri, 6 Oct 2000 12:00:02 -0700 Message-Id: <200010061900.MAA25302@lovefm.cisco.com> To: nanog@merit.edu cc: tbates@cisco.com, eof-list@ripe.net, apops@apnic.net, routing-wg@ripe.net Subject: [apops] The Cidr Report Date: Fri, 06 Oct 2000 12:00:02 -0700 From: Tony Bates Sender: owner-apops@lists.apnic.net Precedence: bulk This is an auto-generated mail on Fri Oct 6 12:00:00 PDT 2000 It is not checked before it leaves my workstation. However, hopefully you will find this report interesting and will take the time to look through this to see if you can improve the amount of aggregation you perform. The report is split into sections: 0) General Status List the route table history for the last week, list any possibly bogus routes seen and give some status on ASes. 1) Gains by aggregating at the origin AS level This lists the "Top 30" players who if they decided to aggregate their announced classful prefixes at the origin AS level could make a significant difference in the reduction of the current size of the Internet routing table. This calculation does not take into account the inclusion of holes when forming an aggregate so it is possible even larger reduction should be possible. 2) Weekly Delta A summary of the last weeks changes in terms of withdrawn and added routes. Please note that this is only a snapshot but does give some indication of ASes participating in CIDR. Clearly, it is generally a good thing to see a large amont of withdrawls. 3) Interesting aggregates Interesting here means not an aggregate made as a set of classful routes. Thanks to xara.net for giving me access to their routing tables once a day. Please send any comments about this report directly to me. Check http://www.employees.org/~tbates/cidr-report.html for a daily update of this report. ------------------------------------------------------------------------------ CIDR REPORT for 06Oct00 0) General Status Table History ------------- Date Prefixes 290900 88909 300900 88195 011000 88325 021000 88317 031000 88456 041000 88428 051000 88525 061000 88980 Check http://www.employees.org/~tbates/cidr.plot.html for a plot of the table history. Possible Bogus Routes --------------------- AS Summary ---------- Number of ASes in routing system: 8668 Number of ASes announcing only one prefix: 4969 (2769 cidr, 2200 classful) Largest number of cidr routes: 907 announced by AS701 Largest number of classful routes: 1086 announced by AS701 1) Gains by aggregating at the origin AS level --- 06Oct00 --- ASnum NetsNow NetsCIDR NetGain % Gain Description AS271 431 153 278 64.5% BCnet Backbone AS1785 592 379 213 36.0% AppliedTheory Communications AS1221 621 454 167 26.9% TELSTRA-AS AS816 579 434 145 25.0% UUNET Canada (ASN-UUNETCA-AS4) AS9269 177 47 130 73.4% Hong Kong CTI AS7046 405 283 122 30.1% COQUI-NET PRTC Internet AS2609 128 8 120 93.8% EUnet-TN AS9304 125 15 110 88.0% Hutchcity AS4755 224 116 108 48.2% Videsh Sanchar Nigam Ltd. India AS7657 324 220 104 32.1% The Internet Group Limited AS7545 159 55 104 65.4% TPG Internet Pty Ltd AS705 363 263 100 27.5% ALTERNET-AS AS9706 103 9 94 91.3% Pusan Metropolitan City Office of AS6429 210 116 94 44.8% FirstCom Internet AS7496 126 35 91 72.2% Power Up AS8013 492 406 86 17.5% PSINET-CA AS174 539 453 86 16.0% Performance Systems International AS4293 340 257 83 24.4% Internal ASN for C&W AS13999 91 9 82 90.1% UNKNOWN AS6595 138 57 81 58.7% DODDSEUR AS3908 256 177 79 30.9% Supernet, Inc. AS577 248 175 73 29.4% Bell Backbone AS8895 107 37 70 65.4% Saudi Arabia AS AS724 223 156 67 30.0% DLA-ASNBLOCK-AS AS7018 579 512 67 11.6% AT&T WorldNet Service Backbone AS701 1086 1021 65 6.0% Alternet AS5106 99 36 63 63.6% AADS-COLUMBUS AS1727 139 76 63 45.3% MRMS-WEST AS3749 119 57 62 52.1% TECNET AS226 170 108 62 36.5% USC/Information Sciences Institut For the rest of the previous weeks gain information please see http://www.employees.org:80/~tbates/cidr-report.html 2) Weekly Delta Please see http://www.employees.org:80/~tbates/cidr-report.html for this part of the report 3) Interesting aggregates Please see http://www.employees.org:80/~tbates/cidr-report.html for this part of the report * APOPS: Asia Pacific Operations Forum * * To unsubscribe: send "unsubscribe" to apops-request@apnic.net * From owner-apops@lists.apnic.net Fri Oct 13 04:02:51 2000 Received: (from majordom@localhost) by ns.apnic.net (8.9.3/8.9.3) id EAA109323; Fri, 13 Oct 2000 04:02:50 +1000 (EST) Received: from whois3.apnic.net (whois3.apnic.net [203.37.255.102]) by ns.apnic.net (8.9.3/8.9.3) with ESMTP id EAA109301 for ; Fri, 13 Oct 2000 04:02:48 +1000 (EST) Received: from dev.apnic.net (IDENT:root@dev.apnic.net [203.37.255.120]) by whois3.apnic.net (8.10.1/UW7.1.1-NSC) with ESMTP id e9CI2mI14503 for ; Fri, 13 Oct 2000 04:02:48 +1000 (EST) Received: (from cscora@localhost) by dev.apnic.net (8.9.3/8.9.3) id EAA22657 for apops@lists.apnic.net; Fri, 13 Oct 2000 04:02:48 +1000 From: Routing Analysis Message-Id: <200010121802.EAA22657@dev.apnic.net> Subject: [apops] Asia Pacific Weekly Routing Report Date: Fri, 13 Oct 2000 04:02:48 +1000 (EST) Reply-To: pfs@cisco.com To: apops@lists.apnic.net X-Mailer: fastmail [version 2.5 PL1] Sender: owner-apops@lists.apnic.net Precedence: bulk This is an automated weekly mailing sent to the APOPS list describing the state of the Internet Routing Table in the Asia Pacific Region. Daily listings are sent to bgp-stats@lists.apnic.net For a graphical representation, please see http://www.apnic.net/stats/bgp. If you have any comments please contact Philip Smith . Asia Pacific Report 13 Oct, 2000 Analysis Summary ---------------- BGP routing table entries examined: 90952 Origin ASes present in the Internet Routing Table: 8767 Origin ASes announcing only one prefix: 2970 Transit ASes present in the Internet Routing Table: 1189 Average AS path length visible in the Internet Routing Table: 5.3 Max AS path length visible: 14 Illegal AS announcements present in the Routing Table: 3 Non-routable prefixes present in the Routing Table: 0 Prefixes being announced from the IANA Reserved Address blocks: 1 Number of addresses announced to Internet: 1185086224 Equivalent to 70 /8s, 162 /16s and 251 /24s Percentage of available address space announced: 32.0 Percentage of allocated address space announced: 62.7 Percentage of available address space allocated: 51.0 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 13418 Prefixes being announced from the APNIC address blocks: 11964 APNIC Region origin ASes present in the Internet Routing Table: 1023 APNIC Region origin ASes announcing only one prefix: 347 APNIC Region transit ASes present in the Internet Routing Table: 165 Average APNIC Region AS path length visible: 5.2 Max APNIC Region AS path length visible: 14 Number of APNIC addresses announced to Internet: 56749128 Equivalent to 3 /8s, 97 /16s and 236 /24s Percentage of available APNIC address space announced: 66.8 APNIC AS Blocks 4608 - 4864, 7467 - 7722, 9216 - 10239, 17408 - 18431 APNIC Address Blocks 61/8, 202/7 and 210/7 APNIC Region per AS prefix count summary ---------------------------------------- ASN No of nets /19 equiv Description 1221 903 999 Telstra 2764 458 129 connect.com.au pty ltd 4740 377 84 Ozemail 2907 361 875 SINET Japan 4755 342 131 VSNL India 7657 341 16 The Internet Group Limited 9269 216 23 Hong Kong CTI 4618 210 56 Internet Thailand 4763 200 44 Telstra New Zealand 703 174 87 UUNET Technologies, Inc. 7545 170 6 TPG Internet Pty Ltd 7474 168 58 Optus Communications 4433 164 126 Access One Pty Ltd 4134 137 365 Data Communications Bureau 4786 136 7 NetConnect Communications Pty 4766 135 433 KORnet Powered BY Korea Telec 7496 132 8 Power Up 9304 129 15 Hutchcity 7617 125 37 One.Net Pty Ltd Global Per AS prefix count summary ---------------------------------- ASN No of nets /19 equiv Description 701 2007 3341 UUNET Technologies, Inc. 7018 1233 3041 AT&T 1 987 4549 BBN Planet 1221 903 999 Telstra 2914 700 1332 Verio, Inc. 1239 686 1675 Sprint ICM-Inria 7046 684 498 UUNET Technologies, Inc. 816 622 143 UUNET Canada4 174 621 2997 PSINet Inc. 3561 603 1448 Cable & Wireless USA 705 552 34 UUNET Technologies, Inc. 8013 513 65 PSINet Ltd. Canada 3549 504 413 Frontier GlobalCenter 209 481 560 Qwest 271 469 380 BCnet Backbone 2764 458 129 connect.com.au pty ltd 3908 443 289 Supernet, Inc. 4293 437 71 Cable & Wireless USA 3602 428 82 Sprint Canada List of Illegal AS's (Global) ----------------------------- Bad AS Designation Network Transit AS Description 65005 PRIVATE 63.101.102.0/24 7407 MCI Telecom. State G 64602 PRIVATE 63.236.57.0/24 209 Qwest 64605 PRIVATE 208.47.206.0/24 209 Qwest Advertised IANA Reserved Addresses ---------------------------------- Network Origin AS Description 27.0.0.0/16 1221 Telstra Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:22 /9:4 /10:5 /11:9 /12:29 /13:62 /14:175 /15:287 /16:6692 /17:933 /18:1894 /19:5975 /20:3814 /21:3860 /22:5882 /23:7838 /24:52534 /25:181 /26:333 /27:82 /28:73 /29:89 /30:87 /31:0 /32:92 End of report * APOPS: Asia Pacific Operations Forum * * To unsubscribe: send "unsubscribe" to apops-request@apnic.net * From owner-apops@lists.apnic.net Sat Oct 14 05:03:51 2000 Received: (from majordom@localhost) by ns.apnic.net (8.9.3/8.9.3) id FAA109212; Sat, 14 Oct 2000 05:03:50 +1000 (EST) Received: from lovefm.cisco.com (lovefm.cisco.com [171.71.217.41]) by ns.apnic.net (8.9.3/8.9.3) with SMTP id FAA109207 for ; Sat, 14 Oct 2000 05:03:48 +1000 (EST) Received: from cisco.com (localhost.cisco.com [127.0.0.1]) by lovefm.cisco.com (8.6.12/8.6.5) with ESMTP id MAA11903; Fri, 13 Oct 2000 12:00:06 -0700 Message-Id: <200010131900.MAA11903@lovefm.cisco.com> To: nanog@merit.edu cc: tbates@cisco.com, eof-list@ripe.net, apops@apnic.net, routing-wg@ripe.net Subject: [apops] The Cidr Report Date: Fri, 13 Oct 2000 12:00:04 -0700 From: Tony Bates Sender: owner-apops@lists.apnic.net Precedence: bulk This is an auto-generated mail on Fri Oct 13 12:00:01 PDT 2000 It is not checked before it leaves my workstation. However, hopefully you will find this report interesting and will take the time to look through this to see if you can improve the amount of aggregation you perform. The report is split into sections: 0) General Status List the route table history for the last week, list any possibly bogus routes seen and give some status on ASes. 1) Gains by aggregating at the origin AS level This lists the "Top 30" players who if they decided to aggregate their announced classful prefixes at the origin AS level could make a significant difference in the reduction of the current size of the Internet routing table. This calculation does not take into account the inclusion of holes when forming an aggregate so it is possible even larger reduction should be possible. 2) Weekly Delta A summary of the last weeks changes in terms of withdrawn and added routes. Please note that this is only a snapshot but does give some indication of ASes participating in CIDR. Clearly, it is generally a good thing to see a large amont of withdrawls. 3) Interesting aggregates Interesting here means not an aggregate made as a set of classful routes. Thanks to xara.net for giving me access to their routing tables once a day. Please send any comments about this report directly to me. Check http://www.employees.org/~tbates/cidr-report.html for a daily update of this report. ------------------------------------------------------------------------------ CIDR REPORT for 13Oct00 0) General Status Table History ------------- Date Prefixes 061000 88980 071000 89153 081000 89078 091000 89463 101000 88806 111000 88726 121000 88590 131000 88713 Check http://www.employees.org/~tbates/cidr.plot.html for a plot of the table history. Possible Bogus Routes --------------------- AS Summary ---------- Number of ASes in routing system: 8744 Number of ASes announcing only one prefix: 5030 (2804 cidr, 2226 classful) Largest number of cidr routes: 919 announced by AS701 Largest number of classful routes: 1123 announced by AS701 1) Gains by aggregating at the origin AS level --- 13Oct00 --- ASnum NetsNow NetsCIDR NetGain % Gain Description AS271 431 153 278 64.5% BCnet Backbone AS1221 611 443 168 27.5% TELSTRA-AS AS9269 178 45 133 74.7% Hong Kong CTI AS816 535 406 129 24.1% UUNET Canada (ASN-UUNETCA-AS4) AS2609 128 8 120 93.8% EUnet-TN AS9304 125 15 110 88.0% Hutchcity AS6429 222 112 110 49.5% FirstCom Internet AS4755 221 112 109 49.3% Videsh Sanchar Nigam Ltd. India AS7545 158 54 104 65.8% TPG Internet Pty Ltd AS705 363 262 101 27.8% ALTERNET-AS AS7046 345 252 93 27.0% UUNET-CUSTOMER AS7496 124 33 91 73.4% Power Up AS7657 308 221 87 28.2% The Internet Group Limited AS174 541 455 86 15.9% Performance Systems International AS4293 342 260 82 24.0% Internal ASN for C&W AS13999 91 9 82 90.1% UNKNOWN AS8013 441 360 81 18.4% PSINET-CA AS6595 137 56 81 59.1% DODDSEUR AS3908 254 175 79 31.1% Supernet, Inc. AS701 1123 1045 78 6.9% Alternet AS577 248 175 73 29.4% Bell Backbone AS724 222 155 67 30.2% DLA-ASNBLOCK-AS AS7018 574 508 66 11.5% AT&T WorldNet Service Backbone AS1727 150 85 65 43.3% MRMS-WEST AS5106 100 37 63 63.0% AADS-COLUMBUS AS3749 122 60 62 50.8% TECNET AS226 168 106 62 36.9% USC/Information Sciences Institut AS16758 63 6 57 90.5% UNKNOWN AS376 129 74 55 42.6% RISQ AS8151 179 125 54 30.2% UNINET-MX For the rest of the previous weeks gain information please see http://www.employees.org:80/~tbates/cidr-report.html 2) Weekly Delta Please see http://www.employees.org:80/~tbates/cidr-report.html for this part of the report 3) Interesting aggregates Please see http://www.employees.org:80/~tbates/cidr-report.html for this part of the report * APOPS: Asia Pacific Operations Forum * * To unsubscribe: send "unsubscribe" to apops-request@apnic.net * From owner-apops@lists.apnic.net Fri Oct 20 04:03:02 2000 Received: (from majordom@localhost) by ns.apnic.net (8.9.3/8.9.3) id EAA71751; Fri, 20 Oct 2000 04:03:01 +1000 (EST) Received: from whois3.apnic.net (whois3.apnic.net [203.37.255.102]) by ns.apnic.net (8.9.3/8.9.3) with ESMTP id EAA71742 for ; Fri, 20 Oct 2000 04:02:59 +1000 (EST) Received: from dev.apnic.net (IDENT:root@dev.apnic.net [203.37.255.120]) by whois3.apnic.net (8.10.1/UW7.1.1-NSC) with ESMTP id e9JI2xI14538 for ; Fri, 20 Oct 2000 04:02:59 +1000 (EST) Received: (from cscora@localhost) by dev.apnic.net (8.9.3/8.9.3) id EAA24063 for apops@lists.apnic.net; Fri, 20 Oct 2000 04:02:58 +1000 From: Routing Analysis Message-Id: <200010191802.EAA24063@dev.apnic.net> Subject: [apops] Asia Pacific Weekly Routing Report Date: Fri, 20 Oct 2000 04:02:58 +1000 (EST) Reply-To: pfs@cisco.com To: apops@lists.apnic.net X-Mailer: fastmail [version 2.5 PL1] Sender: owner-apops@lists.apnic.net Precedence: bulk This is an automated weekly mailing sent to the APOPS list describing the state of the Internet Routing Table in the Asia Pacific Region. Daily listings are sent to bgp-stats@lists.apnic.net For a graphical representation, please see http://www.apnic.net/stats/bgp. If you have any comments please contact Philip Smith . Asia Pacific Report 20 Oct, 2000 Analysis Summary ---------------- BGP routing table entries examined: 92123 Origin ASes present in the Internet Routing Table: 8838 Origin ASes announcing only one prefix: 2987 Transit ASes present in the Internet Routing Table: 1204 Average AS path length visible in the Internet Routing Table: 5.3 Max AS path length visible: 14 Illegal AS announcements present in the Routing Table: 2 Non-routable prefixes present in the Routing Table: 0 Prefixes being announced from the IANA Reserved Address blocks: 3 Number of addresses announced to Internet: 1186197556 Equivalent to 70 /8s, 179 /16s and 240 /24s Percentage of available address space announced: 32.0 Percentage of allocated address space announced: 62.8 Percentage of available address space allocated: 51.0 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 14046 Prefixes being announced from the APNIC address blocks: 12587 APNIC Region origin ASes present in the Internet Routing Table: 1027 APNIC Region origin ASes announcing only one prefix: 344 APNIC Region transit ASes present in the Internet Routing Table: 167 Average APNIC Region AS path length visible: 5.3 Max APNIC Region AS path length visible: 13 Number of APNIC addresses announced to Internet: 57024224 Equivalent to 3 /8s, 102 /16s and 30 /24s Percentage of available APNIC address space announced: 67.1 APNIC AS Blocks 4608 - 4864, 7467 - 7722, 9216 - 10239, 17408 - 18431 APNIC Address Blocks 61/8, 202/7 and 210/7 APNIC Region per AS prefix count summary ---------------------------------------- ASN No of nets /19 equiv Description 1221 872 998 Telstra 9768 655 17 Korea Telecom 2764 462 129 connect.com.au pty ltd 4740 377 84 Ozemail 2907 358 867 SINET Japan 7657 341 16 The Internet Group Limited 4755 317 128 VSNL India 9269 216 24 Hong Kong CTI 4618 212 56 Internet Thailand 4763 201 44 Telstra New Zealand 7474 173 58 Optus Communications 7545 170 6 TPG Internet Pty Ltd 703 161 86 UUNET Technologies, Inc. 4433 157 117 Access One Pty Ltd 4786 139 7 NetConnect Communications Pty 4134 138 367 Data Communications Bureau 9304 136 16 Hutchcity 7496 134 8 Power Up 4766 129 439 KORnet Powered BY Korea Telec Global Per AS prefix count summary ---------------------------------- ASN No of nets /19 equiv Description 701 2041 3358 UUNET Technologies, Inc. 7018 1228 3041 AT&T 1 996 4550 BBN Planet 1221 872 998 Telstra 2914 699 1334 Verio, Inc. 1239 697 1628 Sprint ICM-Inria 7046 679 498 UUNET Technologies, Inc. 816 677 145 UUNET Canada4 9768 655 17 Korea Telecom 174 622 2989 PSINet Inc. 3561 578 1407 Cable & Wireless USA 705 560 34 UUNET Technologies, Inc. 209 488 552 Qwest 8013 478 63 PSINet Ltd. Canada 3549 476 417 Frontier GlobalCenter 271 469 380 BCnet Backbone 2764 462 129 connect.com.au pty ltd 3908 441 289 Supernet, Inc. 4293 435 55 Cable & Wireless USA List of Illegal AS's (Global) ----------------------------- Bad AS Designation Network Transit AS Description 64602 PRIVATE 63.236.57.0/24 209 Qwest 64605 PRIVATE 208.47.206.0/24 209 Qwest Advertised IANA Reserved Addresses ---------------------------------- Network Origin AS Description 27.0.0.0/16 1221 Telstra 50.50.50.0/30 6713 Itissalat Al-MAGHRIB 110.0.253.88/30 9768 Korea Telecom Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:22 /9:4 /10:5 /11:9 /12:29 /13:61 /14:175 /15:290 /16:6694 /17:942 /18:1906 /19:5995 /20:3871 /21:3880 /22:5903 /23:7858 /24:52955 /25:363 /26:549 /27:212 /28:111 /29:101 /30:96 /31:0 /32:92 End of report * APOPS: Asia Pacific Operations Forum * * To unsubscribe: send "unsubscribe" to apops-request@apnic.net * From owner-apops@lists.apnic.net Sat Oct 21 05:03:46 2000 Received: (from majordom@localhost) by ns.apnic.net (8.9.3/8.9.3) id FAA128108; Sat, 21 Oct 2000 05:03:45 +1000 (EST) Received: from lovefm.cisco.com (lovefm.cisco.com [171.71.217.41]) by ns.apnic.net (8.9.3/8.9.3) with SMTP id FAA128087 for ; Sat, 21 Oct 2000 05:03:43 +1000 (EST) Received: from cisco.com (localhost.cisco.com [127.0.0.1]) by lovefm.cisco.com (8.6.12/8.6.5) with ESMTP id MAA02324; Fri, 20 Oct 2000 12:00:03 -0700 Message-Id: <200010201900.MAA02324@lovefm.cisco.com> To: nanog@merit.edu cc: tbates@cisco.com, eof-list@ripe.net, apops@apnic.net, routing-wg@ripe.net Subject: [apops] The Cidr Report Date: Fri, 20 Oct 2000 12:00:02 -0700 From: Tony Bates Sender: owner-apops@lists.apnic.net Precedence: bulk This is an auto-generated mail on Fri Oct 20 12:00:00 PDT 2000 It is not checked before it leaves my workstation. However, hopefully you will find this report interesting and will take the time to look through this to see if you can improve the amount of aggregation you perform. The report is split into sections: 0) General Status List the route table history for the last week, list any possibly bogus routes seen and give some status on ASes. 1) Gains by aggregating at the origin AS level This lists the "Top 30" players who if they decided to aggregate their announced classful prefixes at the origin AS level could make a significant difference in the reduction of the current size of the Internet routing table. This calculation does not take into account the inclusion of holes when forming an aggregate so it is possible even larger reduction should be possible. 2) Weekly Delta A summary of the last weeks changes in terms of withdrawn and added routes. Please note that this is only a snapshot but does give some indication of ASes participating in CIDR. Clearly, it is generally a good thing to see a large amont of withdrawls. 3) Interesting aggregates Interesting here means not an aggregate made as a set of classful routes. Thanks to xara.net for giving me access to their routing tables once a day. Please send any comments about this report directly to me. Check http://www.employees.org/~tbates/cidr-report.html for a daily update of this report. ------------------------------------------------------------------------------ CIDR REPORT for 20Oct00 0) General Status Table History ------------- Date Prefixes 131000 88713 141000 88736 151000 88773 161000 88779 171000 88976 181000 89084 191000 89049 201000 89411 Check http://www.employees.org/~tbates/cidr.plot.html for a plot of the table history. Possible Bogus Routes --------------------- AS Summary ---------- Number of ASes in routing system: 8803 Number of ASes announcing only one prefix: 5049 (2823 cidr, 2226 classful) Largest number of cidr routes: 930 announced by AS701 Largest number of classful routes: 1133 announced by AS701 1) Gains by aggregating at the origin AS level --- 20Oct00 --- ASnum NetsNow NetsCIDR NetGain % Gain Description AS271 431 152 279 64.7% BCnet Backbone AS1221 590 439 151 25.6% TELSTRA-AS AS816 595 454 141 23.7% UUNET Canada (ASN-UUNETCA-AS4) AS9269 177 46 131 74.0% Hong Kong CTI AS2609 128 8 120 93.8% EUnet-TN AS9304 130 17 113 86.9% Hutchcity AS6429 222 112 110 49.5% FirstCom Internet AS7545 159 55 104 65.4% TPG Internet Pty Ltd AS8013 467 364 103 22.1% PSINET-CA AS7046 355 254 101 28.5% UUNET-CUSTOMER AS4755 200 101 99 49.5% Videsh Sanchar Nigam Ltd. India AS705 356 259 97 27.2% ALTERNET-AS AS7657 313 220 93 29.7% The Internet Group Limited AS7496 126 35 91 72.2% Power Up AS174 539 453 86 16.0% Performance Systems International AS4293 341 259 82 24.0% Internal ASN for C&W AS13999 91 9 82 90.1% UNKNOWN AS701 1133 1052 81 7.1% Alternet AS6595 137 56 81 59.1% DODDSEUR AS3908 251 172 79 31.5% Supernet, Inc. AS577 249 176 73 29.3% Bell Backbone AS724 220 153 67 30.5% DLA-ASNBLOCK-AS AS7018 574 508 66 11.5% AT&T WorldNet Service Backbone AS5106 100 37 63 63.0% AADS-COLUMBUS AS226 168 106 62 36.9% USC/Information Sciences Institut AS3749 121 61 60 49.6% TECNET AS16758 63 6 57 90.5% UNKNOWN AS8151 181 126 55 30.4% UNINET-MX AS8895 97 43 54 55.7% Saudi Arabia AS AS7568 78 24 54 69.2% C.S. Communications Co., Ltd. For the rest of the previous weeks gain information please see http://www.employees.org:80/~tbates/cidr-report.html 2) Weekly Delta Please see http://www.employees.org:80/~tbates/cidr-report.html for this part of the report 3) Interesting aggregates Please see http://www.employees.org:80/~tbates/cidr-report.html for this part of the report * APOPS: Asia Pacific Operations Forum * * To unsubscribe: send "unsubscribe" to apops-request@apnic.net * From owner-apops@lists.apnic.net Wed Oct 25 01:06:12 2000 Received: (from majordom@localhost) by ns.apnic.net (8.9.3/8.9.3) id BAA112215; Wed, 25 Oct 2000 01:06:11 +1000 (EST) Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by ns.apnic.net (8.9.3/8.9.3) with ESMTP id BAA112211 for ; Wed, 25 Oct 2000 01:06:08 +1000 (EST) Received: from x49.ripe.net (x49.ripe.net [193.0.1.49]) by birch.ripe.net (8.8.8/8.8.8) with ESMTP id RAA11553; Tue, 24 Oct 2000 17:04:52 +0200 (CEST) Received: from localhost (henk@localhost) by x49.ripe.net (8.8.8/8.8.5) with ESMTP id RAA24676; Tue, 24 Oct 2000 17:04:52 +0200 (CEST) X-Authentication-Warning: x49.ripe.net: henk owned process doing -bs Date: Tue, 24 Oct 2000 17:04:52 +0200 (CEST) From: "Henk Uijterwaal (RIPE-NCC)" To: apops@lists.apnic.net cc: Neale Banks , Philip Smith Subject: Re: [apops] using NTP/etc to measure n/w latency? In-Reply-To: <5.0.0.25.2.20001002131724.00a44da0@lint.cisco.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-apops@lists.apnic.net Precedence: bulk Neale, > At 21:28 29/09/00 +1100, Neale Banks wrote: > >Does anyone have any pointers to using the likes of NTP to sample network > >latency? On Mon, 2 Oct 2000, Philip Smith wrote: > You could check out the Test Traffic project run by the RIPE NCC. More info > at http://www.ripe.net/ripencc/mem-services/ttm/. It's some what more > sophisticated than using NTP though... If you are still interested in this, then it might be good to know that since last Friday, we're offering our measurement devices ("Test-boxes") (as well as a service for operating them) to everybody, against the cost of the hardware, Please see the attached mail for details, mail me if you have any further questions, Henk ------------------------------------------------------------------------- Date: Fri, 20 Oct 2000 15:17:10 +0200 (CEST) From: "Henk Uijterwaal (RIPE-NCC)" To: tt-host@ripe.net, tt-wg@ripe.net, ripe-list@ripe.net Subject: RIPE NCC Test-boxes and Test Traffic Measurements Service Dear colleagues, (Apologies for any duplicate mails). The New Projects group at the RIPE NCC is pleased to announce that 25 new test-boxes have been delivered, tested and are ready to be installed at your site. More test-boxes will be assemble as soon as these 25 machines have been shipped. These test-boxes measure delays and losses on the Internet by sending time-stamped packets to each other. A more detailed description is available in RIPE document 209 (see below). At this moment, we are also moving the Test Traffic Measurements from an experimental product to a regular membership service offered by the RIPE NCC. Under this service, the RIPE NCC will operate the test-box and analyze the measurement data for you. With the introduction of this service, 2 restrictions will be removed: * The TTM service will be available to everybody interested, not just the current LIR members, * Any organization can apply for more than 1 test-box, and, for example, install a box at every major PoP. Another change is that you will have to pay for the hardware of the boxes. A test-box currently costs 2750 Euro. This includes the installation costs, but does not include shipping, taxes and import/export duties. The RIPE NCC has been asked to introduce a service fee (of approximately 3000 Euro/Year) for the operation of the boxes. However, for tax-reasons, it is currently not possible to do this. Therefore: * There will be NO service fee for the remainder of 2000 and the first months of 2001. For those of you familiar with the project, it is worth noticing that the hardware of the boxes has been improved. The most important change is in the design of the antenna. In the new machines, the HF-unit has been moved to the antenna, thus eliminating the need for expensive coax cable between the antenna and the test-box itself. Instead, regular CAT-5 cable can be used and cable lengths of (at least) 200 to 300 meters are possible. Also, the boxes have more CPU and memory available and this feature will be exploited in the future do other measurements and analyze the data on the box, thus reducing the time between data-taking and availability of the results. In short, this means: * Easier installation * More freedom in installing the antennas. If you are interested in hosting a test-box, please start by reading the following documents, all available from the test-traffic web-site at http://www.ripe.net/test-traffic/: * RIPE-209, "Providing Test Traffic Measurements as a membership service". This document describes the model the RIPE-NCC will use for selling the test-boxes and the related service for operating them. * RIPE-214, "General Terms to the RIPE-NCC Test Traffic Measurements and Test-Box Purchase Agreement". This document contains the contract used to sell the test-boxes. It is the translation of RIPE-209 into "legalise". * RIPE-168 (Version 2.1 or later). This is the installation guide for the test-boxes. The current document is somewhat outdated, in particular the section on the antenna installation. An update will be published early November. A document that is presently being written is a "2 page glossy summary" of RIPE-209, describing the advantages of hosting a test-box for your manager. If you are interested in hosting one or more test-boxes, please fill out the application sheet at http://www.ripe.net/test-traffic/Host_testbox. If anything is unclear or you have questions that are not answered in the documents, do not hesitate to contact us. The application procedure has become a little more complex than before, but still shouldn't take much more than a few minutes to complete. Sites that have already expressed interest in hosting a box will be contacted in a separate mail. As announced before, we will give the existing test-box hosts a possibility to upgrade your hardware. This will announced, when we are ready to do this, in a separate mail. There is no deadline for applying. Applications will be processed in the order as they come in and processed as soon as our production schedule permits. If you have any questions about this project, please do not hesitate to contact me. Kind regards, Henk Uijterwaal ------------------------------------------------------------------------------ Henk Uijterwaal Email: henk.uijterwaal@ripe.net RIPE Network Coordination Centre WWW: http://www.ripe.net/home/henk Singel 258 Phone: +31.20.535-4414, Fax -4445 1016 AB Amsterdam Home: +31.20.4195305 The Netherlands Mobile: +31.6.55861746 ------------------------------------------------------------------------------ A man can take a train and never reach his destination. (Kerouac, well before RFC2780). * APOPS: Asia Pacific Operations Forum * * To unsubscribe: send "unsubscribe" to apops-request@apnic.net * From owner-apops@lists.apnic.net Wed Oct 25 07:46:02 2000 Received: (from majordom@localhost) by ns.apnic.net (8.9.3/8.9.3) id HAA102784; Wed, 25 Oct 2000 07:46:02 +1000 (EST) Received: from nico.bway.net (nico.bway.net [216.220.96.3]) by ns.apnic.net (8.9.3/8.9.3) with ESMTP id HAA102761 for ; Wed, 25 Oct 2000 07:45:58 +1000 (EST) Received: from bway.net (port035.lilly.isdn.bway.net [216.220.110.241] (may be forged)) by nico.bway.net (8.11.1/8.11.1/Debian 8.11.0-6) with ESMTP id e9OLjX701107; Tue, 24 Oct 2000 17:45:33 -0400 X-Authentication-Warning: nico.bway.net: Host port035.lilly.isdn.bway.net [216.220.110.241] (may be forged) claimed to be bway.net Message-ID: <39F60373.407055B9@bway.net> Date: Tue, 24 Oct 2000 17:47:31 -0400 From: "Robert B. Cohen" X-Mailer: Mozilla 4.7 [en]C-CCK-MCD NSCPCD47 (Win95; I) X-Accept-Language: en,pdf MIME-Version: 1.0 To: "Henk Uijterwaal (RIPE-NCC)" CC: apops@lists.apnic.net, Neale Banks , Philip Smith Subject: Re: [apops] using NTP/etc to measure n/w latency? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-apops@lists.apnic.net Precedence: bulk Is there any way to measure traffic volumes on specific circuits with this, not just delays? Bob Cohen "Henk Uijterwaal (RIPE-NCC)" wrote: > Neale, > > > At 21:28 29/09/00 +1100, Neale Banks wrote: > > > >Does anyone have any pointers to using the likes of NTP to sample network > > >latency? > > On Mon, 2 Oct 2000, Philip Smith wrote: > > > You could check out the Test Traffic project run by the RIPE NCC. More info > > at http://www.ripe.net/ripencc/mem-services/ttm/. It's some what more > > sophisticated than using NTP though... > > If you are still interested in this, then it might be good to know that > since last Friday, we're offering our measurement devices ("Test-boxes") > (as well as a service for operating them) to everybody, against the cost > of the hardware, > > Please see the attached mail for details, mail me if you have any further > questions, > > Henk > > ------------------------------------------------------------------------- > Date: Fri, 20 Oct 2000 15:17:10 +0200 (CEST) > From: "Henk Uijterwaal (RIPE-NCC)" > To: tt-host@ripe.net, tt-wg@ripe.net, ripe-list@ripe.net > Subject: RIPE NCC Test-boxes and Test Traffic Measurements Service > > Dear colleagues, > > (Apologies for any duplicate mails). > > The New Projects group at the RIPE NCC is pleased to announce that 25 new > test-boxes have been delivered, tested and are ready to be installed at > your site. More test-boxes will be assemble as soon as these 25 machines > have been shipped. These test-boxes measure delays and losses on the > Internet by sending time-stamped packets to each other. A more detailed > description is available in RIPE document 209 (see below). > > At this moment, we are also moving the Test Traffic Measurements from an > experimental product to a regular membership service offered by the RIPE > NCC. Under this service, the RIPE NCC will operate the test-box and > analyze the measurement data for you. With the introduction of this > service, 2 restrictions will be removed: > > * The TTM service will be available to everybody interested, not just > the current LIR members, > * Any organization can apply for more than 1 test-box, and, for example, > install a box at every major PoP. > > Another change is that you will have to pay for the hardware of the boxes. > A test-box currently costs 2750 Euro. This includes the installation > costs, but does not include shipping, taxes and import/export duties. The > RIPE NCC has been asked to introduce a service fee (of approximately 3000 > Euro/Year) for the operation of the boxes. However, for tax-reasons, it > is currently not possible to do this. Therefore: > > * There will be NO service fee for the remainder of 2000 and > the first months of 2001. > > For those of you familiar with the project, it is worth noticing that the > hardware of the boxes has been improved. The most important change is in > the design of the antenna. In the new machines, the HF-unit has been > moved to the antenna, thus eliminating the need for expensive coax cable > between the antenna and the test-box itself. Instead, regular CAT-5 cable > can be used and cable lengths of (at least) 200 to 300 meters are > possible. > > Also, the boxes have more CPU and memory available and this feature will > be exploited in the future do other measurements and analyze the data on > the box, thus reducing the time between data-taking and availability of > the results. In short, this means: > > * Easier installation > * More freedom in installing the antennas. > > If you are interested in hosting a test-box, please start by reading the > following documents, all available from the test-traffic web-site at > http://www.ripe.net/test-traffic/: > > * RIPE-209, "Providing Test Traffic Measurements as a membership > service". This document describes the model the RIPE-NCC will use for > selling the test-boxes and the related service for operating them. > > * RIPE-214, "General Terms to the RIPE-NCC Test Traffic Measurements and > Test-Box Purchase Agreement". This document contains the contract > used to sell the test-boxes. It is the translation of RIPE-209 > into "legalise". > > * RIPE-168 (Version 2.1 or later). This is the installation guide for > the test-boxes. The current document is somewhat outdated, in > particular the section on the antenna installation. An update will > be published early November. > > A document that is presently being written is a "2 page glossy summary" of > RIPE-209, describing the advantages of hosting a test-box for your > manager. > > If you are interested in hosting one or more test-boxes, please fill out > the application sheet at http://www.ripe.net/test-traffic/Host_testbox. > If anything is unclear or you have questions that are not answered in the > documents, do not hesitate to contact us. The application procedure has > become a little more complex than before, but still shouldn't take much > more than a few minutes to complete. > > Sites that have already expressed interest in hosting a box will be > contacted in a separate mail. > > As announced before, we will give the existing test-box hosts a > possibility to upgrade your hardware. This will announced, when we are > ready to do this, in a separate mail. > > There is no deadline for applying. Applications will be processed in the > order as they come in and processed as soon as our production schedule > permits. > > If you have any questions about this project, please do not hesitate > to contact me. > > Kind regards, > > Henk Uijterwaal > > ------------------------------------------------------------------------------ > Henk Uijterwaal Email: henk.uijterwaal@ripe.net > RIPE Network Coordination Centre WWW: http://www.ripe.net/home/henk > Singel 258 Phone: +31.20.535-4414, Fax -4445 > 1016 AB Amsterdam Home: +31.20.4195305 > The Netherlands Mobile: +31.6.55861746 > ------------------------------------------------------------------------------ > > A man can take a train and never reach his destination. > (Kerouac, well before RFC2780). > > * APOPS: Asia Pacific Operations Forum * > * To unsubscribe: send "unsubscribe" to apops-request@apnic.net * * APOPS: Asia Pacific Operations Forum * * To unsubscribe: send "unsubscribe" to apops-request@apnic.net * From owner-apops@lists.apnic.net Wed Oct 25 08:19:20 2000 Received: (from majordom@localhost) by ns.apnic.net (8.9.3/8.9.3) id IAA107814; Wed, 25 Oct 2000 08:19:20 +1000 (EST) Received: from marina.lowendale.com.au ([203.26.242.120]) by ns.apnic.net (8.9.3/8.9.3) with ESMTP id IAA107809 for ; Wed, 25 Oct 2000 08:19:17 +1000 (EST) Received: from localhost (neale@localhost) by marina.lowendale.com.au (8.9.3/8.9.3/Debian/GNU) with ESMTP id JAA10874; Wed, 25 Oct 2000 09:38:23 +1100 Date: Wed, 25 Oct 2000 09:38:22 +1100 (EST) From: Neale Banks To: "Robert B. Cohen" cc: "Henk Uijterwaal (RIPE-NCC)" , apops@lists.apnic.net, Philip Smith Subject: Re: [apops] using NTP/etc to measure n/w latency? In-Reply-To: <39F60373.407055B9@bway.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-apops@lists.apnic.net Precedence: bulk On Tue, 24 Oct 2000, Robert B. Cohen wrote: > Is there any way to measure traffic volumes on specific circuits with > this, not just delays? What/how are you hoping to measure that can't be better/easier measured with the likes of router interface octet counters etc? Ah...... if the RIPE box could use SNMP to measure traffic volumes then there might be some interesting correlations to be observed. Is that your motivation? Regards, Neale. * APOPS: Asia Pacific Operations Forum * * To unsubscribe: send "unsubscribe" to apops-request@apnic.net * From owner-apops@lists.apnic.net Wed Oct 25 09:32:28 2000 Received: (from majordom@localhost) by ns.apnic.net (8.9.3/8.9.3) id JAA117045; Wed, 25 Oct 2000 09:32:28 +1000 (EST) Received: from nico.bway.net (nico.bway.net [216.220.96.3]) by ns.apnic.net (8.9.3/8.9.3) with ESMTP id JAA117039 for ; Wed, 25 Oct 2000 09:32:24 +1000 (EST) Received: from bway.net (port029.lilly.isdn.bway.net [216.220.110.235] (may be forged)) by nico.bway.net (8.11.1/8.11.1/Debian 8.11.0-6) with ESMTP id e9ONVp725967; Tue, 24 Oct 2000 19:31:51 -0400 X-Authentication-Warning: nico.bway.net: Host port029.lilly.isdn.bway.net [216.220.110.235] (may be forged) claimed to be bway.net Message-ID: <39F61C5D.B95EBF65@bway.net> Date: Tue, 24 Oct 2000 19:33:49 -0400 From: "Robert B. Cohen" X-Mailer: Mozilla 4.7 [en]C-CCK-MCD NSCPCD47 (Win95; I) X-Accept-Language: en,pdf MIME-Version: 1.0 To: Neale Banks CC: "Henk Uijterwaal (RIPE-NCC)" , apops@lists.apnic.net, Philip Smith Subject: Re: [apops] using NTP/etc to measure n/w latency? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-apops@lists.apnic.net Precedence: bulk YES, it's the SNMP angle! Could the RIPE box use SNMP to measure traffic volumes. That is my motivation. I would like to see the measures of bandwidth volumes directly so we could see exactly how much traffic is moving, but also some correlations with QOS and traffic volumes. Part of the motivation is I would like to see how much of certain circuits is actually filled and how the fill percent is changing. There is some anecdotal evidence to suggest that while there is more bandwidth getting put in place, the fill rates are a bit lower than they have been in the past. Bob Cohen Neale Banks wrote: > On Tue, 24 Oct 2000, Robert B. Cohen wrote: > > > Is there any way to measure traffic volumes on specific circuits with > > this, not just delays? > > What/how are you hoping to measure that can't be better/easier measured > with the likes of router interface octet counters etc? > > Ah...... if the RIPE box could use SNMP to measure traffic volumes then > there might be some interesting correlations to be observed. Is that your > motivation? > > Regards, > Neale. * APOPS: Asia Pacific Operations Forum * * To unsubscribe: send "unsubscribe" to apops-request@apnic.net * From owner-apops@lists.apnic.net Fri Oct 27 01:26:11 2000 Received: (from majordom@localhost) by ns.apnic.net (8.9.3/8.9.3) id BAA129186; Fri, 27 Oct 2000 01:26:11 +1000 (EST) Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by ns.apnic.net (8.9.3/8.9.3) with ESMTP id BAA129166 for ; Fri, 27 Oct 2000 01:26:08 +1000 (EST) Received: from x49.ripe.net (x49.ripe.net [193.0.1.49]) by birch.ripe.net (8.8.8/8.8.8) with ESMTP id RAA29866; Thu, 26 Oct 2000 17:25:59 +0200 (CEST) Received: from localhost (henk@localhost) by x49.ripe.net (8.8.8/8.8.5) with ESMTP id RAA18473; Thu, 26 Oct 2000 17:25:59 +0200 (CEST) X-Authentication-Warning: x49.ripe.net: henk owned process doing -bs Date: Thu, 26 Oct 2000 17:25:59 +0200 (CEST) From: "Henk Uijterwaal (RIPE-NCC)" To: "Robert B. Cohen" cc: Neale Banks , apops@lists.apnic.net, Philip Smith Subject: Re: [apops] using NTP/etc to measure n/w latency? In-Reply-To: <39F61C5D.B95EBF65@bway.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-apops@lists.apnic.net Precedence: bulk Bob, Neale, > > > Is there any way to measure traffic volumes on specific circuits with > > > this, not just delays? > > > > What/how are you hoping to measure that can't be better/easier measured > > with the likes of router interface octet counters etc? No, we don't measure this. We looked at it, but the RIPE community wasn't too enthousiastic about both snooping packets from the piece of ethernet just before the border router, or having a black box talk directly to the router. > > Ah...... if the RIPE box could use SNMP to measure traffic volumes then > > there might be some interesting correlations to be observed. Is that your > > motivation? > YES, it's the SNMP angle! Could the RIPE box use SNMP to measure > traffic volumes. That is my motivation. I would like to see the > measures of bandwidth volumes directly so we could see exactly how > much traffic is moving, but also some correlations with QOS and > traffic volumes. We've always said that we are interested in reporting our measurements via SNMP, then integrate them with existing monitoring systems. There is/was also some interest in the RIPE TT Working Group, but when we the current test-box hosts to provide us with more details on what they would like to see, nobody replied. I'm also aware that this topic is being discussed in the IETF SNMPconf WG. At the moment, my idea is to wait until this group has come up with a draft, then see if we can do an implementation. The correlations are something one could already do today. As a first approach, record the info from the router, take our analyzed data, and try to correlate them off-line. Then, if there is a correlation, one can talk to a port on our box and get the data as it is being recorded, then do the correlations real-time. Henk ------------------------------------------------------------------------------ Henk Uijterwaal Email: henk.uijterwaal@ripe.net RIPE Network Coordination Centre WWW: http://www.ripe.net/home/henk Singel 258 Phone: +31.20.535-4414, Fax -4445 1016 AB Amsterdam Home: +31.20.4195305 The Netherlands Mobile: +31.6.55861746 ------------------------------------------------------------------------------ A man can take a train and never reach his destination. (Kerouac, well before RFC2780). * APOPS: Asia Pacific Operations Forum * * To unsubscribe: send "unsubscribe" to apops-request@apnic.net * From owner-apops@lists.apnic.net Fri Oct 27 04:02:46 2000 Received: (from majordom@localhost) by ns.apnic.net (8.9.3/8.9.3) id EAA86259; Fri, 27 Oct 2000 04:02:45 +1000 (EST) Received: from whois3.apnic.net (whois3.apnic.net [203.37.255.102]) by ns.apnic.net (8.9.3/8.9.3) with ESMTP id EAA86237 for ; Fri, 27 Oct 2000 04:02:43 +1000 (EST) Received: from dev.apnic.net (IDENT:root@dev.apnic.net [203.37.255.120]) by whois3.apnic.net (8.10.1/UW7.1.1-NSC) with ESMTP id e9QI2hF16040 for ; Fri, 27 Oct 2000 04:02:43 +1000 (EST) Received: (from cscora@localhost) by dev.apnic.net (8.9.3/8.9.3) id EAA07004 for apops@lists.apnic.net; Fri, 27 Oct 2000 04:02:43 +1000 From: Routing Analysis Message-Id: <200010261802.EAA07004@dev.apnic.net> Subject: [apops] Asia Pacific Weekly Routing Report Date: Fri, 27 Oct 2000 04:02:43 +1000 (EST) Reply-To: pfs@cisco.com To: apops@lists.apnic.net X-Mailer: fastmail [version 2.5 PL1] Sender: owner-apops@lists.apnic.net Precedence: bulk This is an automated weekly mailing sent to the APOPS list describing the state of the Internet Routing Table in the Asia Pacific Region. Daily listings are sent to bgp-stats@lists.apnic.net For a graphical representation, please see http://www.apnic.net/stats/bgp. If you have any comments please contact Philip Smith . Asia Pacific Report 27 Oct, 2000 Analysis Summary ---------------- BGP routing table entries examined: 89649 Origin ASes present in the Internet Routing Table: 8834 Origin ASes announcing only one prefix: 2990 Transit ASes present in the Internet Routing Table: 1244 Average AS path length visible in the Internet Routing Table: 5.5 Max AS path length visible: 17 Illegal AS announcements present in the Routing Table: 0 Non-routable prefixes present in the Routing Table: 0 Prefixes being announced from the IANA Reserved Address blocks: 1 Number of addresses announced to Internet: 1184446165 Equivalent to 70 /8s, 153 /16s and 54 /24s Percentage of available address space announced: 32.0 Percentage of allocated address space announced: 62.7 Percentage of available address space allocated: 51.0 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 13145 Prefixes being announced from the APNIC address blocks: 11720 APNIC Region origin ASes present in the Internet Routing Table: 1025 APNIC Region origin ASes announcing only one prefix: 349 APNIC Region transit ASes present in the Internet Routing Table: 174 Average APNIC Region AS path length visible: 5.7 Max APNIC Region AS path length visible: 13 Number of APNIC addresses announced to Internet: 57078750 Equivalent to 3 /8s, 102 /16s and 243 /24s Percentage of available APNIC address space announced: 67.2 APNIC AS Blocks 4608 - 4864, 7467 - 7722, 9216 - 10239, 17408 - 18431 APNIC Address Blocks 61/8, 202/7 and 210/7 APNIC Region per AS prefix count summary ---------------------------------------- ASN No of nets /19 equiv Description 1221 739 989 Telstra 2764 419 129 connect.com.au pty ltd 4740 379 85 Ozemail 2907 361 883 SINET Japan 7657 359 17 The Internet Group Limited 4755 306 125 VSNL India 9269 218 24 Hong Kong CTI 4618 213 56 Internet Thailand 7545 171 6 TPG Internet Pty Ltd 703 166 89 UUNET Technologies, Inc. 4433 159 125 Access One Pty Ltd 7474 155 58 Optus Communications 4786 148 7 NetConnect Communications Pty 4134 138 367 Data Communications Bureau 9304 136 16 Hutchcity 7496 135 8 Power Up 4766 123 431 KORnet Powered BY Korea Telec 7617 122 37 One.Net Pty Ltd 9768 120 6 Korea Telecom Global Per AS prefix count summary ---------------------------------- ASN No of nets /19 equiv Description 701 2066 3354 UUNET Technologies, Inc. 1 889 4537 BBN Planet 7018 879 3014 AT&T 1221 739 989 Telstra 7046 702 508 UUNET Technologies, Inc. 2914 696 1333 Verio, Inc. 1239 688 1635 Sprint ICM-Inria 705 650 37 UUNET Technologies, Inc. 816 634 143 UUNET Canada4 174 602 2717 PSINet Inc. 3561 569 1390 Cable & Wireless USA 8013 500 63 PSINet Ltd. Canada 209 496 560 Qwest 3549 479 418 Frontier GlobalCenter 271 458 300 BCnet Backbone 3908 448 290 Supernet, Inc. 4293 432 55 Cable & Wireless USA 2548 425 528 Digital Express Group, Inc. 3602 425 81 Sprint Canada Advertised IANA Reserved Addresses ---------------------------------- Network Origin AS Description 50.50.50.0/30 6713 Itissalat Al-MAGHRIB Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:22 /9:4 /10:5 /11:9 /12:31 /13:56 /14:174 /15:289 /16:6683 /17:949 /18:1903 /19:6015 /20:3908 /21:3881 /22:5780 /23:7519 /24:52008 /25:93 /26:133 /27:42 /28:22 /29:62 /30:24 /31:0 /32:37 End of report * APOPS: Asia Pacific Operations Forum * * To unsubscribe: send "unsubscribe" to apops-request@apnic.net * From owner-apops@lists.apnic.net Sat Oct 28 05:03:51 2000 Received: (from majordom@localhost) by ns.apnic.net (8.9.3/8.9.3) id FAA101208; Sat, 28 Oct 2000 05:03:51 +1000 (EST) Received: from lovefm.cisco.com (lovefm.cisco.com [171.71.217.41]) by ns.apnic.net (8.9.3/8.9.3) with SMTP id FAA101188 for ; Sat, 28 Oct 2000 05:03:48 +1000 (EST) Received: from cisco.com (localhost.cisco.com [127.0.0.1]) by lovefm.cisco.com (8.6.12/8.6.5) with ESMTP id MAA14715; Fri, 27 Oct 2000 12:00:04 -0700 Message-Id: <200010271900.MAA14715@lovefm.cisco.com> To: nanog@merit.edu cc: tbates@cisco.com, eof-list@ripe.net, apops@apnic.net, routing-wg@ripe.net Subject: [apops] The Cidr Report Date: Fri, 27 Oct 2000 12:00:04 -0700 From: Tony Bates Sender: owner-apops@lists.apnic.net Precedence: bulk This is an auto-generated mail on Fri Oct 27 12:00:00 PDT 2000 It is not checked before it leaves my workstation. However, hopefully you will find this report interesting and will take the time to look through this to see if you can improve the amount of aggregation you perform. The report is split into sections: 0) General Status List the route table history for the last week, list any possibly bogus routes seen and give some status on ASes. 1) Gains by aggregating at the origin AS level This lists the "Top 30" players who if they decided to aggregate their announced classful prefixes at the origin AS level could make a significant difference in the reduction of the current size of the Internet routing table. This calculation does not take into account the inclusion of holes when forming an aggregate so it is possible even larger reduction should be possible. 2) Weekly Delta A summary of the last weeks changes in terms of withdrawn and added routes. Please note that this is only a snapshot but does give some indication of ASes participating in CIDR. Clearly, it is generally a good thing to see a large amont of withdrawls. 3) Interesting aggregates Interesting here means not an aggregate made as a set of classful routes. Thanks to xara.net for giving me access to their routing tables once a day. Please send any comments about this report directly to me. Check http://www.employees.org/~tbates/cidr-report.html for a daily update of this report. ------------------------------------------------------------------------------ CIDR REPORT for 27Oct00 0) General Status Table History ------------- Date Prefixes 201000 89411 211000 89037 221000 89088 231000 89255 241000 89314 251000 89441 261000 89651 271000 89717 Check http://www.employees.org/~tbates/cidr.plot.html for a plot of the table history. Possible Bogus Routes --------------------- AS Summary ---------- Number of ASes in routing system: 8876 Number of ASes announcing only one prefix: 5070 (2831 cidr, 2239 classful) Largest number of cidr routes: 923 announced by AS701 Largest number of classful routes: 1138 announced by AS701 1) Gains by aggregating at the origin AS level --- 27Oct00 --- ASnum NetsNow NetsCIDR NetGain % Gain Description AS271 421 148 273 64.8% BCnet Backbone AS1221 590 439 151 25.6% TELSTRA-AS AS9269 180 47 133 73.9% Hong Kong CTI AS816 549 421 128 23.3% UUNET Canada (ASN-UUNETCA-AS4) AS2609 128 8 120 93.8% EUnet-TN AS6429 226 112 114 50.4% FirstCom Internet AS9304 130 17 113 86.9% Hutchcity AS8013 464 360 104 22.4% PSINET-CA AS7545 159 55 104 65.4% TPG Internet Pty Ltd AS4755 200 102 98 49.0% Videsh Sanchar Nigam Ltd. India AS705 356 259 97 27.2% ALTERNET-AS AS7657 312 217 95 30.4% The Internet Group Limited AS7046 347 255 92 26.5% UUNET-CUSTOMER AS7496 128 37 91 71.1% Power Up AS174 542 456 86 15.9% Performance Systems International AS701 1138 1055 83 7.3% Alternet AS4293 340 258 82 24.1% Internal ASN for C&W AS13999 91 9 82 90.1% UNKNOWN AS6595 138 57 81 58.7% DODDSEUR AS3908 251 172 79 31.5% Supernet, Inc. AS577 247 176 71 28.7% Bell Backbone AS724 218 151 67 30.7% DLA-ASNBLOCK-AS AS7018 582 516 66 11.3% AT&T WorldNet Service Backbone AS5106 100 37 63 63.0% AADS-COLUMBUS AS226 169 107 62 36.7% USC/Information Sciences Institut AS3749 118 57 61 51.7% TECNET AS1727 149 88 61 40.9% MRMS-WEST AS16758 63 6 57 90.5% UNKNOWN AS376 131 75 56 42.7% RISQ AS8151 180 126 54 30.0% UNINET-MX For the rest of the previous weeks gain information please see http://www.employees.org:80/~tbates/cidr-report.html 2) Weekly Delta Please see http://www.employees.org:80/~tbates/cidr-report.html for this part of the report 3) Interesting aggregates Please see http://www.employees.org:80/~tbates/cidr-report.html for this part of the report * APOPS: Asia Pacific Operations Forum * * To unsubscribe: send "unsubscribe" to apops-request@apnic.net *