BGP Update Report
BGP Update Report Interval: 01-Sep-06 -to- 14-Sep-06 (14 days) Observation Point: BGP Peering with AS4637 TOP 20 Unstable Origin AS Rank ASNUpds % Upds/PfxAS-Name 1 - AS413453702 4.7% 123.2 -- CHINANET-BACKBONE No.31,Jin-rong Street 2 - AS17974 17267 1.5% 34.1 -- TELKOMNET-AS2-AP PT TELEKOMUNIKASI INDONESIA 3 - AS855 15835 1.4% 27.9 -- CANET-ASN-4 - Aliant Telecom 4 - AS9121 9843 0.9% 9.5 -- TTNET TTnet Autonomous System 5 - AS156119766 0.8% 92.1 -- Iranian Research Organisation 6 - AS175579308 0.8% 25.1 -- PKTELECOM-AS-AP Pakistan Telecom 7 - AS9583 8396 0.7% 12.6 -- SIFY-AS-IN Sify Limited 8 - AS8685 7949 0.7% 240.9 -- DORUKNET DorukNet Istanbul / Turkey 9 - AS337837420 0.7% 69.3 -- EEPAD 10 - AS180497117 0.6% 49.8 -- TINP-TW Taiwan Infrastructure Network Technologie 11 - AS6147 6607 0.6% 28.4 -- Telefonica del Peru S.A.A. 12 - AS4787 6556 0.6% 24.6 -- ASN-CBN ASN CBNnet 13 - AS702 6347 0.6% 8.7 -- AS702 MCI EMEA - Commercial IP service provider in Europe 14 - AS154646261 0.5% 260.9 -- IHLASNET IHLASNET Autonomous System 15 - AS8866 6080 0.5% 119.2 -- BTC-AS Bulgarian Telecommunication Company Plc. 16 - AS199165803 0.5% 25.8 -- ASTRUM-0001 - OLM LLC 17 - AS9471 5745 0.5% 56.9 -- MANA-PF-AP MANA S.A. 18 - AS5839 5549 0.5% 346.8 -- DDN-ASNBLK - DoD Network Information Center 19 - AS8386 5542 0.5% 241.0 -- KOCNET KOCNET-AS 20 - AS239185525 0.5% 42.8 -- CBB-BGP-IBARAKI Connexion By Boeing Ibaraki AS TOP 20 Unstable Origin AS (Updates per announced prefix) Rank ASNUpds % Upds/PfxAS-Name 1 - AS174703714 0.3%3714.0 -- CELLTEL-AS Celltel Lanka (Pvt) Ltd. 2 - AS3043 3168 0.3%3168.0 -- AMPHIB-AS - Amphibian Media Corporation 3 - AS129221022 0.1%1022.0 -- MULTITRADE-AS Bank Outsourcer 4 - AS30298 982 0.1% 982.0 -- FIRST-AMERICAN-BANK-SSB - First American Bank 5 - AS34378 898 0.1% 898.0 -- RUG-AS Razguliay-UKRROS Group 6 - AS39042 752 0.1% 752.0 -- GLOBAL63RU-AS CJSC Global Telecom Co AS 7 - AS39298 492 0.0% 492.0 -- SERI Seri Bilgi Teknolojileri ve Destek Hizmetleri 8 - AS14857 477 0.0% 477.0 -- MOTOROLA-ICSD - Motorola 9 - AS3217 424 0.0% 424.0 -- SIMBIRSK 10 - AS31085 413 0.0% 413.0 -- VIKINGNET-AS VIKING TUR 11 - AS31526 409 0.0% 409.0 -- TEKOFAKS-AS TEKOFAKS 12 - AS34984 403 0.0% 403.0 -- BITEL-AS BILISIM TELEKOM 13 - AS35080 402 0.0% 402.0 -- OYAK-TELEKOM-AS Oyak Telekom Hizm. BGP AS 14 - AS29666 400 0.0% 400.0 -- TRHENKEL Turk Henkel Kimya Sanayi 15 - AS29635 398 0.0% 398.0 -- BANVIT-AS Banvit A.S 16 - AS39080 396 0.0% 396.0 -- SIMETRI-AS SIMETRI YAZILIM 17 - AS39807 391 0.0% 391.0 -- ASREYSAS Reysas Logistics 18 - AS23917 765 0.1% 382.5 -- BRIBIE-NET-AS-AP Bribie Island Net Multihomed, Brisbane 19 - AS39623 380 0.0% 380.0 -- PROFILOTELRAAS ProfiloTelraNetwork 20 - AS5424 378 0.0% 378.0 -- ATNET-AT ATnet TOP 20 Unstable Prefixes Rank Prefix Upds % Origin AS -- AS Name 1 - 203.189.184.0/21 3714 0.3% AS17470 -- CELLTEL-AS Celltel Lanka (Pvt) Ltd. 2 - 209.140.24.0/243171 0.2% AS3043 -- AMPHIB-AS - Amphibian Media Corporation AS9121 -- TTNET TTnet Autonomous System 3 - 208.0.225.0/24 3106 0.2% AS11139 -- CWRIN CW BARBADOS 4 - 202.125.147.0/24 2916 0.2% AS17557 -- PKTELECOM-AS-AP Pakistan Telecom 5 - 61.4.0.0/192247 0.2% AS9899 -- ICARE-AP iCare.com Ltd. 6 - 83.210.15.0/24 1321 0.1% AS23918 -- CBB-BGP-IBARAKI Connexion By Boeing Ibaraki AS AS29257 -- CBB-IE-AS Connexion by Boeing Ireland, Ltd. AS30533 -- CONNEXION-BY-BOEING-LTN - Connexion by Boeing AS31050 -- CBB-RU-ASN Connexion by Boeing Eastern Europe, Ltd. AS33697 -- CONNEXION-BY-BOEING-VBC - Connexion by Boeing 7 - 143.81.0.0/21 1064 0.1% AS6034 -- DDN-ASNBLK - DoD Network Information Center 8 - 203.112.154.0/24 1062 0.1% AS17783 -- SRILRPG-AS SRIL RPG Autonomous System 9 - 194.105.61.0/241022 0.1% AS12922 -- MULTITRADE-AS Bank Outsourcer 10 - 130.36.88.0/21 1011 0.1% AS2686 -- ATT Global Network Services - EMEA 11 - 209.189.231.0/24983 0.1% AS19366 -- MNS - Managed Network Solutions
The Cidr Report
This report has been generated at Fri Sep 15 21:45:30 2006 AEST. The report analyses the BGP Routing Table of an AS4637 (Reach) router and generates a report on aggregation potential within the table. Check http://www.cidr-report.org/as4637 for a current version of this report. Recent Table History Date PrefixesCIDR Agg 08-09-06194527 126897 09-09-06194454 126908 10-09-06194571 126959 11-09-06194648 127145 12-09-06194896 127236 13-09-06195022 127054 14-09-06195038 127221 15-09-06195282 127113 AS Summary 23037 Number of ASes in routing system 9681 Number of ASes announcing only one prefix 1482 Largest number of prefixes announced by an AS AS7018 : ATT-INTERNET4 - ATT WorldNet Services 91268096 Largest address span announced by an AS (/32s) AS721 : DISA-ASNBLK - DoD Network Information Center Aggregation Summary The algorithm used in this report proposes aggregation only when there is a precise match using the AS path, so as to preserve traffic transit policies. Aggregation is also proposed across non-advertised address space ('holes'). --- 15Sep06 --- ASnumNetsNow NetsAggr NetGain % Gain Description Table 195049 1270806796934.8% All ASes AS4134 1274 270 100478.8% CHINANET-BACKBONE No.31,Jin-rong Street AS4755 980 65 91593.4% VSNL-AS Videsh Sanchar Nigam Ltd. Autonomous System AS18566 961 123 83887.2% COVAD - Covad Communications Co. AS4323 1009 293 71671.0% TWTC - Time Warner Telecom, Inc. AS9498 850 157 69381.5% BBIL-AP BHARTI BT INTERNET LTD. AS721977 306 67168.7% DISA-ASNBLK - DoD Network Information Center AS22773 696 51 64592.7% CCINET-2 - Cox Communications Inc. AS6197 1029 488 54152.6% BATI-ATL - BellSouth Network Solutions, Inc AS7018 1482 960 52235.2% ATT-INTERNET4 - ATT WorldNet Services AS19262 693 189 50472.7% VZGNI-TRANSIT - Verizon Internet Services Inc. AS19916 565 68 49788.0% ASTRUM-0001 - OLM LLC AS17488 530 48 48290.9% HATHWAY-NET-AP Hathway IP Over Cable Internet AS855545 82 46385.0% CANET-ASN-4 - Aliant Telecom AS11492 737 291 44660.5% CABLEONE - CABLE ONE AS17676 497 62 43587.5% JPNIC-JP-ASN-BLOCK Japan Network Information Center AS18101 453 23 43094.9% RIL-IDC Reliance Infocom Ltd Internet Data Centre, AS3602 512 104 40879.7% AS3602-RTI - Rogers Telecom Inc. AS4766 703 310 39355.9% KIXS-AS-KR Korea Telecom AS15270 462 76 38683.5% AS-PAETEC-NET - PaeTec.net -a division of PaeTecCommunications, Inc. AS812407 26 38193.6% ROGERS-CABLE - Rogers Cable Inc. AS4812 397 60 33784.9% CHINANET-SH-AP China Telecom (Group) AS6467 394 70 32482.2% ESPIRECOMM - Xspedius Communications Co. AS16852 366 53 31385.5% FOCAL-CHICAGO - Focal Data Communications of Illinois AS16814 329 45 28486.3% NSS S.A. AS9583 951 672 27929.3% SIFY-AS-IN Sify Limited AS19115 375 97 27874.1% CHARTER-LEBANON - Charter Communications AS14654 284 15 26994.7% WAYPORT - Wayport AS6167 370 106 26471.4% CELLCO-PART - Cellco Partnership AS17849 423 161 26261.9% GINAMHANVIT-AS-KR hanvit ginam broadcasting comm. AS6198 502 245 25751.2% BATI-MIA - BellSouth Network
Re: IPv6 PI block is announced - update your filters 2620:0000::/23
Gert Doering wrote: Does the policy really permit /40.../47 assignments? http://www.arin.net/registration/guidelines/ipv6_assignment.html#step2 -- If you're never wrong, you're not trying hard enough
Weekly Routing Table Report
This is an automated weekly mailing describing the state of the Internet Routing Table as seen from APNIC's router in Japan. Daily listings are sent to [EMAIL PROTECTED] For historical data, please see http://thyme.apnic.net. If you have any comments please contact Philip Smith [EMAIL PROTECTED]. Routing Table Report 04:00 +10GMT Sat 16 Sep, 2006 Analysis Summary BGP routing table entries examined: 197928 Prefixes after maximum aggregation: 107946 Unique aggregates announced to Internet: 95928 Total ASes present in the Internet Routing Table: 23141 Origin-only ASes present in the Internet Routing Table: 20180 Origin ASes announcing only one prefix:9686 Transit ASes present in the Internet Routing Table:2961 Transit-only ASes present in the Internet Routing Table: 66 Average AS path length visible in the Internet Routing Table: 3.6 Max AS path length visible: 29 Max AS path prepend of ASN (36728) 27 Prefixes from unregistered ASNs in the Routing Table: 1 Unregistered ASNs in the Routing Table: 1 Special use prefixes present in the Routing Table:1 Prefixes being announced from unallocated address space: 9 Number of addresses announced to Internet: 1588413004 Equivalent to 94 /8s, 173 /16s and 66 /24s Percentage of available address space announced: 42.9 Percentage of allocated address space announced: 60.8 Percentage of available address space allocated: 70.5 Total number of prefixes smaller than registry allocations: 99068 APNIC Region Analysis Summary - Prefixes being announced by APNIC Region ASes:43365 Total APNIC prefixes after maximum aggregation: 17398 Prefixes being announced from the APNIC address blocks: 40969 Unique aggregates announced from the APNIC address blocks:18335 APNIC Region origin ASes present in the Internet Routing Table:2695 APNIC Region origin ASes announcing only one prefix:756 APNIC Region transit ASes present in the Internet Routing Table:402 Average APNIC Region AS path length visible:3.5 Max APNIC Region AS path length visible: 24 Number of APNIC addresses announced to Internet: 262327904 Equivalent to 15 /8s, 162 /16s and 206 /24s Percentage of available APNIC address space announced: 82.0 APNIC AS Blocks4608-4864, 7467-7722, 9216-10239, 17408-18431 (pre-ERX allocations) 23552-24575, 37888-38911 APNIC Address Blocks 58/7, 60/7, 121/8, 122/7, 124/7, 126/8, 202/7 210/7, 218/7, 220/7 and 222/8 ARIN Region Analysis Summary Prefixes being announced by ARIN Region ASes:100132 Total ARIN prefixes after maximum aggregation:59256 Prefixes being announced from the ARIN address blocks:73331 Unique aggregates announced from the ARIN address blocks: 27657 ARIN Region origin ASes present in the Internet Routing Table:10980 ARIN Region origin ASes announcing only one prefix:4159 ARIN Region transit ASes present in the Internet Routing Table:1008 Average ARIN Region AS path length visible: 3.3 Max ARIN Region AS path length visible: 29 Number of ARIN addresses announced to Internet: 298082048 Equivalent to 17 /8s, 196 /16s and 95 /24s Percentage of available ARIN address space announced: 77.2 ARIN AS Blocks 1-1876, 1902-2042, 2044-2046, 2048-2106 (pre-ERX allocations) 2138-2584, 2615-2772, 2823-2829, 2880-3153 3354-4607, 4865-5119, 5632-6655, 6912-7466 7723-8191, 10240-12287, 13312-15359, 16384-17407 18432-20479, 21504-23551, 25600-26591, 26624-27647, 29696-30719, 31744-33791 35840-36863, 39936-40959 ARIN Address Blocks24/8, 63/8, 64/5, 72/6, 76/8, 199/8, 204/6, 208/7 and 216/8 RIPE Region Analysis Summary Prefixes being announced by RIPE Region ASes: 39951 Total RIPE prefixes after maximum aggregation:26595 Prefixes being announced from the RIPE address blocks:36913 Unique aggregates announced from the RIPE address blocks: 24868 RIPE Region origin ASes present in the Internet Routing Table: 8518 RIPE Region origin ASes announcing only one prefix:4480 RIPE Region transit ASes present in the
SC and PC Nominations, Charter Amendments, and Elections
In accordance with the NANOG Charter, we announce the 2006 NANOG Steering Committee nominations, Charter Amendments, and call for new Program Committee nominations. Many thanks to Merit Network for their impartial support and involvement with the NANOG community. The partnership we have developed enables transparent management and continued evolution of NANOG. On behalf of the SC, 2006 Steering Committee nominations will be accepted September 16 through October 1, 2006. To nominate an SC candidate, send the nominee's name and email address with a brief statement supporting the nomination to [EMAIL PROTECTED] Merit will confirm the nominee's acceptance and request a short bio from the candidate. Once complete, the list of candidates and their bios will be posted no later than Monday, October 2, 2006. The Steering Committee candidates will be given a brief opportunity to make comments and/or accept questions from the community at the NANOG 38 Community Meeting, Sunday, October 8, beginning at 6 PM, EST. In addition to Steering Committee elections, proposed revisions to the NANOG charter can be found at http://www.nanog.org/charter. Eligible voters may also propose additional charter amendments to [EMAIL PROTECTED] by September 30, 2006. Submissions to include names and email addresses of petition signatories, which Merit may verify. Final recommendations for voting will be presented on the 2006 NANOG ballot. Elections will commence Monday, October 9 at 1:00 PM EST, and conclude on Tuesday, October 10 at 3 PM EST. The results will be shared at the close of NANOG38 in St. Louis. The voting mechanism is designed to ensure that each registered voter casts only one ballot. To respect privacy and protect confidentiality, the identity of the voter and the choices made on the ballot will be decoupled so there is not a way to know who voted for whom. To vote you will need a NANOG username and password. 2006 Program Committee nominations will be accepted October 3 through October 11, 2006. To nominate a PC candidate, send the nominee's name and email address with a brief statement supporting the nomination to [EMAIL PROTECTED] Merit will confirm the nominee's acceptance and request a short bio from the candidate to be posted to the NANOG web site. Refer to http://www.nanog.org/elections06 for current information. Additional links are: 2006 Eligible Voters: http://www.nanog.org/voters06.epl 2006 SC Candidate Bios: http://www.nanog.org/candidates06 2006 Charter Amendments: http://www.nanog.org/charter 2006 NANOG Election Ballot: http://www.nanog.org/ballot06 2006 NANOG Election and Charter results: http://www.nanog.org/results06 2006 NANOG PC Candidate Bios: http://www.nanog.org/pccandidates06 randy, for the SC
Re: IPv6 PI block is announced - update your filters 2620:0000::/23
On Fri, 15 Sep 2006, Gert Doering wrote: Hi, On Thu, Sep 14, 2006 at 12:05:16AM +0200, Jeroen Massar wrote: It's update your IPv6 filters time: http://www.arin.net/reference/ip_blocks.html 8- IPv6 Assignment Blocks CIDR Block 2620::/23 -8 Expect blocks in between /40 and /48 there. Filter recommendation document updated. Could you also add blocks like 2800::/23 from LACNIC issued Nov 2005 by IANA? Does the policy really permit /40.../47 assignments? The only thing I found so far is [1] which really only defines the =48 end. It's talking about _at least_ a /44 reserved for future growth and it says When possible, [subsequent] assignments will be made from an adjacent address block.. Considering what we see with v4 PI (direct assignments) today and had seen with /8 PA and an undefined (open) other end in ARIN policy I wouldn't trust any =40 rule being the maximum for this block. I have so far decided to use (also see [2]): ! + ARIN PI (chose whatever one you think is worse) !ipv6 prefix-list ipv6-ebgp-strict seq 135 deny 2620::/23 le 128 ipv6 prefix-list ipv6-ebgp-strict seq 135 permit 2620::/23 ge 32 le 48 Happy weekend. /bz References: [1] http://www.arin.net/policy/nrpm.html#six582 6.5.8. Direct assignments from ARIN to end-user organizations 6.5.8.2. Initial assignment size 6.5.8.3. Subsequent assignment size [2] http://sources.zabbadoz.net/ipv6/v6-prefix-filter-20060913-public.cfg -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT
Re: IPv6 PI block is announced - update your filters 2620:0000::/23
[...] Call me naive, but could somebody enlighten me as to what tangible benefit filtering out bogon space actually achieves? It strikes me that it causes more headaches than it solves.
Re: IPv6 PI block is announced - update your filters 2620:0000::/23
Yes, please, let's have that flamewar all over again... Or you could just read one or more of the previous flamewars and spare us another round. Here's a starting point: http://merit.edu/cgi-bin/swish/swish.cgi?query=bogon+filteringsubmit=Search%21si=0si=6dr_o=12dr_s_mon=9dr_s_day=15dr_s_year=2006dr_e_mon=9dr_e_day=15dr_e_year=2006 Peter Corlett wrote: [...] Call me naive, but could somebody enlighten me as to what tangible benefit filtering out bogon space actually achieves? It strikes me that it causes more headaches than it solves.
Re: IPv6 PI block is announced - update your filters 2620:0000::/23
On Fri, 15 Sep 2006, Randy Bush wrote: Call me naive, but could somebody enlighten me as to what tangible benefit filtering out bogon space actually achieves? It strikes me that it causes more headaches than it solves. the theory is that it means you have no route to send responses back to an attacker who uses tcp, i.e. a spammer. IANA-based data bogon filters are in fact mostly useful to filter attack issues using udp-based and similar protocols that don't require session establishment. the practice is that spammers use holes or super-blocks of allocated, i.e. not bogon, space. they are not stupid. It is still bogon space and completewhois bogon list catches most of those. Those that don't get caught are the ones where allocation exists but ip space is not being used (i.e. not advertised in bgp) and then doing super-block works for the spammer (there are ways to filter that as well actually but you ran risk of filtering those doing aggregation). And do remember that original question was about IPv6 allocation. Personally I don't know any spammers using ipv6 bogon space [yet]... so your point is well taken. randy
Re: Removal of name
On Fri, 15 Sep 2006, Tash wrote: Dear Sirs/Madams, Please remove my name Tashfeen Imdad from this site below. It is slanderous towards me and it does not involve me. I am no Dr. Phil has a saying: When you find yourself in a hole, stop digging. You do realize you mailed this out to a mailing list with a few thousand people on it, right ? So that you've just reminded everyone who had forgotten about it. In any case, this is an archive of a mailing list, where this discussion originally took place. None of us run it, and there are probably multiple archives of Nanog out there, so you'll never get rid of them all. In fact I'll bet there are people who read your message and are making copies of the page now, just in case the others do come down. longer involved with telecommunications and I am not associated with Qwest anymore and it is also slanderous towards Qwest. I would appreciate this act of kindness. It is gone on too long this is from 2002. This defames my character from 2002 and it does not properly represent me. Dude, you did it. Be a man and own up to it. Figure out a way in Interviews to show you learned from it, though this post will make it harder. http://www.ibiblio.org/Dave/Dr-Fun/df9601/df960124.jpg thanks Tash http://www.cctec.com/maillists/nanog/historical/0202/msg00446.html Re: OT: spam from Globix to ARIN POCs - To: Kai Schlichting [EMAIL PROTECTED] Subject: Re: OT: spam from Globix to ARIN POCs From: Christopher X. Candreva [EMAIL PROTECTED] Date: Mon, 25 Feb 2002 15:26:36 -0500 (EST) Cc: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] In-Reply-To: [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] - On Mon, 25 Feb 2002, Kai Schlichting wrote: And on another note, that little spamming jerk from Qwest's NYC sales office, Tashfeen Imdad, should start finding himself a new job while there is time. And don't count on collecting unemployment.What, did he spam your users through the whois database, and copy you on it since you are the tech contact ? [EMAIL PROTECTED] went right in the filters. == Chris Candreva -- [EMAIL PROTECTED] -- (914) 967-7816 WestNet Internet Services of Westchester http://www.westnet.com/ - References: OT: spam from Globix to ARIN POCs From: Kai Schlichting [EMAIL PROTECTED] - Prev: Re: DNS timeline Next: Re: DNS timeline Index(es): Main Thread - Want to be your own boss? Learn how on Yahoo! Small Business. == Chris Candreva -- [EMAIL PROTECTED] -- (914) 967-7816 WestNet Internet Services of Westchester http://www.westnet.com/
Re: IPv6 PI block is announced - update your filters 2620:0000::/23
Call me naive, but could somebody enlighten me as to what tangible benefit filtering out bogon space actually achieves? It strikes me that it causes more headaches than it solves. All packets arriving from bogon space have the evil bit set. There's nobody there you want to talk to, and there's nobody there that your users really want to talk to, even if they got the address from some legitimate source like the DNS server for examplebank.com. IPv6 bogons aren't likely to be spammers, because there's not enough critical mass there yet to make it worthwhile, but that just means that the greedy6 bit hasn't been implemented widely, and that'll eventually get fixed. -- Thanks; Bill Note that this isn't my regular email account - It's still experimental so far. And Google probably logs and indexes everything you send it.