April 2005 - Test - lists.nanog.org

(half OT) Tool for ASN statistic freaks: webalizer_asn
by Fredy Kuenzler 10 Apr '05

10 Apr '05

Webalizer_ASN v1.2b is available since a while, and according to my tests rather stable now. The ASN Data for Webalizer_ASN is based on Netlantis backend BGP engine (someone asked recently about Netlantis). If you experience a rainy lazy sunday, this might be a tool to play with a bit and build your personal Top-Ten ASN list. http://www.init7.net/webalizer_asn/ Debian Woody users could use the precompiled package. If you have existing orignal Webalizer statistics, you need to move webalizer.current file to webalizer.current.old before running the webalizer_asn - and please note: no warranty, you use the tool on your own risk - so have your statistics backuped first. Enjoy, F.

1 0

Re: djbdns: An alternative to BIND
by sthaug＠nethelp.no 10 Apr '05

10 Apr '05

> You need only count the lines of code needed by the daemon/s > servicing requests. That is, IMO, bind's only major failing. Too > much code, too many little used features (nobody I know needs or > wants rndc), and no way to compile without them. If you read Bruce > Schneier, as every developer should, you know how important that > "Amount of code" is. Ah, but how do you know what are the little used features? We use rndc a lot, just as we used ndc with BIND 8. Steinar Haug, Nethelp consulting, sthaug(a)nethelp.no

1 0

Call for Track Chairs - APRICOT 2006
by Suresh Ramasubramanian 10 Apr '05

10 Apr '05

APRICOT 2006 CALL FOR TECHNICAL CONFERENCE TRACK CHAIRS Asia Pacific Regional Internet Conference on Operational Technologies Perth, Australia Feb 22 - Mar 3, 2006 The APRICOT 2006 Program Committee is seeking interested and qualified Track Chairs to actively assist the Committee in recruiting speakers and organizing technical tracks for the 2006 Asia Pacific Regional Internet Conference on Operational Technologies. The main responsibility of the Track Chair is to identify, recruit high quality speakers to share their expertise on operationally relevent topics. As in past years, the APRICOT Program Committee will issue a general call for presentations, which typically elicits a large number of submissions. These proposals will be provided to the Track Chairs for consideration, but it is expected that the Track Chairs will primarily use their own personal networks to recruit speakers who may not have participated in past APRICOT events. Specific Track Chair responsibilities include: * Identifying and describing a track topic and relevant potential track components (panel discussions, pro/con debates, etc.) within the track that will be interesting and valuable to the APRICOT audience. Preliminary Track descriptions are due at the time of nomination, or by June 15, 2005. * Helping to publicize and recruit speakers, session moderators, and participants for their track and the conference in general. * Vetting and recommending speakers and their subjects for their Track to the Program Committee. Detailed Track content recommendations are due on August 29, 2005. * Requiring and confirming that speakers submit their proposed materials in a timely manner. Track chairs should submit speaker recommendations and abstracts to the Program Committee by September 26, 2005. Selected speakers will be announced by the Program Committee on or before October 10, 2005. * Evaluating submitted materials for content and quality suitable for an international technical/operations conference. Track chairs should submit full/detailed presentation outlines to the Program Committee by November 7, 2005. * Serving as a liaison between the Program Committee and the selected participants in your Track. Track chairs should submit all complete presentation materials to the Program Committee by January 9, 2006. * This year we will require that speakers must supply their program material in advance so that we can confirm operational content and that there is not inappropriate sales material. * Track Chairs are members of the Apricot Program Committee and will share the responsibility of determining overall program issues and planning. Track Chairs are encouraged to help find speakers for other tracks and tutorials as well. Workshop Chair and Tutorial Chair These positions are similar to the Track Chairs described above, but will be responsible for recruiting and facilitating instructors for five-day and half-day/full day instructional tutorials, respectively. A total of 5-6 Track Chairs will be selected by the Program Committee, along with a Tutorial Chair and Workshop Chair, with the expectation that 4-6 Tracks will ultimately be scheduled for presentation. Please feel free to nominate yourself or someone other than yourself who might be appropriate for either of these positions. The deadline for receiving Conference Track and Tutorial Track Chair nominations is May 2, 2005. Results of the selection process will be announced by May 18, 2005. ABOUT THE APRICOT AUDIENCE The APRICOT audience is mainly comprised of technical network operators and professional engineers with experience levels ranging from (almost) newbie to seasoned, senior technical management. APRICOT audiences always include native speakers of a dozen or more languages, so written materials and presentations should be tuned appropriately. Each year, the majority of APRICOT attendees travel internationally and commit considerable sums relative to their local economies to participate in APRICOT; they expect the highest possible quality in presentation content and delivery. APRICOT CONFERENCE TRACKS, SESSIONS, & TUTORIALS Historically, tutorials have focused on core operational skills and basic protocol knowledge, with conference sessions highlighting day-to-day operations and recent/emerging issues within a 12-18 month time horizon. APRICOT Conference Tracks are full-day events. Each Track typically encompasses three 90-minute Sessions composed of 3-4 presenters (speakers) per session; accordingly each presentation should be designed to be approximately 20-30 minutes in duration. On the recommendation of the Track Chair, individual Sessions may be moderated by persons with expertise appropriate to the subject matter of the session. Session Moderators may assist in managing speaker time and soliciting questions from the audience. APRICOT Tutorials are half or full day workshops which focus on a particular subject in-depth. They may be presented by a single Instructor, or a team of instructors working together. Tutorial attendance is typically charged separately from APRICOT conference attendance, so it is essential that tutorials are of the highest quality and deliver concrete operational value to participants. The above descriptions are suggestions only, based on past successful program offerings. Prospective Track and Tutorial Chairs are encouraged to suggest alternative schedules or structures for organizing Conference Tracks and Tutorials to the APRICOT Program Committee. *IMPORTANT NOTE* APRICOT is a TECHNICAL and OPERATIONAL conference. Marketing and commercial content is limited to the appropriate fora (e.g., designated demo areas, "Beer 'n Gear" events) and otherwise restricted from the official program. The Program Committee and Track Chairs are charged with maintaining the technical standards of APRICOT, and will therefore not accept inappropriate materials. To the greatest extent possible, all official conference materials will be designed and presented in a vendor neutral format. APRICOT attendees are technical professionals, and proposed conference materials should be appropriate to the audience. All sessions will provide time for Q&A, and presenters should be prepared to receive detailed technical questions, and to provide appropriately detailed technical responses. The APRICOT Program Committee reserves the right withdraw speaking invitations or to disallow presentations that are inconsistent with the goals and standards set forth in this call for proposals. APRICOT FUNDING AND SUPPORT APRICOT is a not-for-profit event. Every effort is made to keep attendances fee low in order to reach diverse target groups from both the developed and developing countries of the Asia Pacific region. Registration fees are waived for all Track Chairs, Tutorial instructors, and Speakers, however it is generally impossible for APRICOT to underwrite travel expenses for speakers. Only in exceptional hardship circumstances will APRICOT be able to consider assisting Track Chairs or Tutorial instructors with travel expenses. A small number of conference fellowships will be made available (on the basis of personal and local need) to prospective conference attendees from Asia Pacific region; additional information about these fellowships is available at http://www.2006.apricot.net/fellowship.html (TBA). APRICOT 2006 IMPORTANT MILESTONES: 02 May 2005: Receive all Track, Workshop, and Tutorial Chair nominations 18 May 2005: Track Chair selections announced 15 June 2005: Basic Track outlines submitted by Track Chairs to Program Committee General Presentation RFP distributed by Program Committee 29 August 2005: Initial presentation proposals submitted by Track Chairs to Program Committee 26 September 2005: Final presentation proposals submitted by Track Chairs to Program Committee 10 October 2005: Approved presentation tracks announced by Program Committee Selected APRICOT 2006 Presenters notified; 07 November 2005: Detailed presentations outlines submitted by Track Chairs to Program Committee Conference Track schedules finalized 09 January 2006: Full presentation materials submitted by Track Chairs to Program Committee 22 February 2006: APRICOT 2006 Workshops begin (through 26 February) 27 February 2006: APRICOT 2006 Conference Begins NOMINATING YOURSELF OR OTHERS AS A TRACK CHAIR If you would like to be considered as a TRACK CHAIR, please copy the following form, fill it in and email it to mailto:chair.submission@apricot.net If you know of someone else that you believe would make a good Track Chair, please forward this email to them and encourage them to submit the form, or fill in as much of the form as you can and include your contact info in the section for the "Nominator" and email it to mailto:program@apricot.net with the word "Nomination" in the subject line. -------------------- NOMINATOR CONTACT INFO (If nominating another person, please put your info here, if you are doing this for yourself you do not need to fill in this section) Nominator Name: Nominator Title: Nominator Voice Phone: Nominator Fax: Nominator email: ------------------------ TRACK CHAIR PERSONAL INFORMATION (This should be info about the person who would be the Track Chair) First (Given) Name: Middle Name: Last (Family) Name: Title: Company / School / Affiliation: Organization URL: City: State: Country: Voice Phone: Extension: Fax: email: Personal URL: Short Bio (please include enough information that we can determine that you are would be qualified as a track chair): Please also include a photo if possible. Assistant Name (Person who may be administratively submitting this for the speaker or someone who is an alternate contact for chair): Assistant Title: Assistant Voice Phone: Assistant Fax: Assistant email: ------------------------ CONTENT INFO (Select or suggest one or more Track subject you would be interested in Chairing): * Network security * Address planning, conservation, responsibility, IPv6 * Network planning, management and traffic engineering * Operation, NOC, Helpdesk and issues in deploying Internet Infrastructure * Internet exchanges, peering and collocation * Hot topics in future network protocols and techniques * BIND, DNSSEC, and Reverse and multilingual DNS * Broadband first/last mile access technologies * Mobile and wireless technologies * Content, Applications, Email, streaming and multimedia infrastructure * Service and server scaling, Redundancy and reliability, Open source * VoIP * Other Describe: Please put down any other thoughts, suggestions, ideas or comments: ------------------------ More information on the conference will be made available at http://www.2006.apricot.net/program.html Thanks for your interest in APRICOT 2006! Robert J. Berger, Chair (rberger at ibd dot com) Tom Vest, Co-Chair (tvest at pch dot net) APRICOT 2006 Program Committee

1 0

AS prepending
by Philip Lavine 09 Apr '05

09 Apr '05

To all, I am using AS prepending to favor one ISP over another, in a BGP multihomed/multiISP scenario. Why does the ISP receiving the prepends fail to add my network into their routing table? Is this a "feature" of BGP, or have I gone too far with 3 prepend statements. Thx Philip __________________________________ Yahoo! Messenger Show us what our next emoticon should look like. Join the fun. http://www.advision.webevents.yahoo.com/emoticontest

4 3

Re: Blog...
by Fergie (Paul Ferguson) 09 Apr '05

09 Apr '05

Thanks for the kind words. - ferg -- Bill Woodcock <woody(a)pch.net> wrote: I have to agree... Paul's been doing an excellent job of picking out the one or two things that really matter each day, and I've found it quite valuable. I think that unlike much of the administrivial chatter on the list lately, and the usual kids-ranting-at-each-other, this has been improving the signal-to-noise ratio quite a bit. -Bill -- "Fergie", a.k.a. Paul Ferguson Engineering Architecture for the Internet fergdawg(a)netzero.net or fergdawg(a)sbcglobal.net ferg's tech blog: http://spaces.msn.com/members/fergdawg/

1 0

Re: books every network operator should read?
by MARLON BORBA 09 Apr '05

09 Apr '05

Blueprints for High Availability Ewan Stern & Hal Marcus John Wiley & Sons . High Availability Network Fundamentals Chris Oggerino Cisco Press Fundamental readings for those 24x7 guys. Abraços, Marlon Borba, CISSP. "Você prefere sua estabilidade hoje ou sua felicidade amanhã?" --Max Gehringer, na CBN. >>> Kim Onnel <karim.adel(a)gmail.com> 04/09/05 6:55 AM >>> Internet Routing Arch. [...]

1 0

books every network operator should read?
by Janet Sullivan 09 Apr '05

09 Apr '05

I'd like to make a list for the BGP4.net wiki of books that are thought highly of by the network community. What books stand out for you as being excellent? If you could only own 5 network related books, what would they be? Feel free to reply to me offlist - I'll post a summary after a few days. Thanks! Janet

2 1

Re: Weekly Routing Table Report
by Joe Loiacono 09 Apr '05

09 Apr '05

Wha happen? Routing Table Report 04:00 +10GMT Sat 09 Apr, 2005 Analysis Summary ---------------- BGP routing table entries examined: 139674 Prefixes after maximum aggregation: 83474 Unique aggregates announced to Internet: 67116 Total ASes present in the Internet Routing Table: 17729 Origin-only ASes present in the Internet Routing Table: 15381 Origin ASes announcing only one prefix: 7282 Transit ASes present in the Internet Routing Table: 2348 Transit-only ASes present in the Internet Routing Table: 194 Average AS path length visible in the Internet Routing Table: 4.5 Max AS path length visible: 23 Prefixes from unregistered ASNs in the Routing Table: 38 Special use prefixes present in the Routing Table: 0 Prefixes being announced from unallocated address space: 13 Number of addresses announced to Internet: 1212269440 Routing Table Report 04:00 +10GMT Sat 02 Apr, 2005 Analysis Summary ---------------- BGP routing table entries examined: 158858 Prefixes after maximum aggregation: 92606 Unique aggregates announced to Internet: 76314 Total ASes present in the Internet Routing Table: 19277 Origin-only ASes present in the Internet Routing Table: 16774 Origin ASes announcing only one prefix: 7827 Transit ASes present in the Internet Routing Table: 2503 Transit-only ASes present in the Internet Routing Table: 68 Average AS path length visible in the Internet Routing Table: 4.5 Max AS path length visible: 23 Prefixes from unregistered ASNs in the Routing Table: 31 Special use prefixes present in the Routing Table: 0 Prefixes being announced from unallocated address space: 13 Number of addresses announced to Internet: 1394234240 ---------------------------------------------------------------------------------------- This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. ---------------------------------------------------------------------------------------- Routing Table Analysis <cscora To: apops(a)apops.net, nanog(a)nanog.org, routing-wg(a)ripe.net, afnog(a)afnog.org @apnic.net> cc: Sent by: Subject: Weekly Routing Table Report owner-nanog 04/08/2005 02:18 PM Please respond to pfs This is an automated weekly mailing describing the state of the Internet Routing Table as seen from APNIC's router in Japan. Daily listings are sent to bgp-stats(a)lists.apnic.net If you have any comments please contact Philip Smith <pfs(a)cisco.com>. Routing Table Report 04:00 +10GMT Sat 09 Apr, 2005 Analysis Summary ---------------- BGP routing table entries examined: 139674 Prefixes after maximum aggregation: 83474 Unique aggregates announced to Internet: 67116 Total ASes present in the Internet Routing Table: 17729 Origin-only ASes present in the Internet Routing Table: 15381 Origin ASes announcing only one prefix: 7282 Transit ASes present in the Internet Routing Table: 2348 Transit-only ASes present in the Internet Routing Table: 194 Average AS path length visible in the Internet Routing Table: 4.5 Max AS path length visible: 23 Prefixes from unregistered ASNs in the Routing Table: 38 Special use prefixes present in the Routing Table: 0 Prefixes being announced from unallocated address space: 13 Number of addresses announced to Internet: 1212269440 Equivalent to 72 /8s, 65 /16s and 195 /24s Percentage of available address space announced: 32.7 Percentage of allocated address space announced: 51.3 Percentage of available address space allocated: 63.7 Total number of prefixes smaller than registry allocations: 61623 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 27665 Total APNIC prefixes after maximum aggregation: 13807 Prefixes being announced from the APNIC address blocks: 25625 Unique aggregates announced from the APNIC address blocks: 13601 APNIC Region origin ASes present in the Internet Routing Table: 2170 APNIC Region origin ASes announcing only one prefix: 672 APNIC Region transit ASes present in the Internet Routing Table: 331 Average APNIC Region AS path length visible: 4.5 Max APNIC Region AS path length visible: 15 Number of APNIC addresses announced to Internet: 100659328 Equivalent to 5 /8s, 255 /16s and 240 /24s Percentage of available APNIC address space announced: 37.4 APNIC AS Blocks 4608-4864, 7467-7722, 9216-10239, 17408-18431 (pre-ERX allocations) 23552-24575 APNIC Address Blocks 58/7, 60/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: 79734 Total ARIN prefixes after maximum aggregation: 49337 Prefixes being announced from the ARIN address blocks: 61099 Unique aggregates announced from the ARIN address blocks: 21894 ARIN Region origin ASes present in the Internet Routing Table: 9396 ARIN Region origin ASes announcing only one prefix: 3492 ARIN Region transit ASes present in the Internet Routing Table: 886 Average ARIN Region AS path length visible: 4.3 Max ARIN Region AS path length visible: 21 Number of ARIN addresses announced to Internet: 229050368 Equivalent to 13 /8s, 167 /16s and 8 /24s Percentage of available ARIN address space announced: 65.0 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 ARIN Address Blocks 24/8, 63/8, 64/6, 68/7, 70/6, 198/7, 204/6, 208/7 and 216/8 RIPE Region Analysis Summary ---------------------------- Prefixes being announced by RIPE Region ASes: 22768 Total RIPE prefixes after maximum aggregation: 16764 Prefixes being announced from the RIPE address blocks: 19187 Unique aggregates announced from the RIPE address blocks: 13327 RIPE Region origin ASes present in the Internet Routing Table: 5289 RIPE Region origin ASes announcing only one prefix: 2902 RIPE Region transit ASes present in the Internet Routing Table: 966 Average RIPE Region AS path length visible: 5.1 Max RIPE Region AS path length visible: 23 Number of RIPE addresses announced to Internet: 154207424 Equivalent to 9 /8s, 49 /16s and 4 /24s Percentage of available RIPE address space announced: 54.1 RIPE AS Blocks 1877-1901, 2043, 2047, 2107-2136, 2585-2614 (pre-ERX allocations) 2773-2822, 2830-2879, 3154-3353, 5377-5631 6656-6911, 8192-9215, 12288-13311, 15360-16383 20480-21503, 24576-25599, 28672-29695 30720-31743, 33792-35839 RIPE Address Blocks 62/8, 80/5, 88/8, 188/8, 193/8, 194/7, 212/7 and 217/8 LACNIC Region Analysis Summary ------------------------------ Prefixes being announced by LACNIC Region ASes: 8378 Total LACNIC prefixes after maximum aggregation: 2926 Prefixes being announced from the LACNIC address blocks: 6986 Unique aggregates announced from the LACNIC address blocks: 4018 LACNIC Region origin ASes present in the Internet Routing Table: 609 LACNIC Region origin ASes announcing only one prefix: 187 LACNIC Region transit ASes present in the Internet Routing Table: 111 Average LACNIC Region AS path length visible: 5.1 Max LACNIC Region AS path length visible: 19 Number of LACNIC addresses announced to Internet: 18041856 Equivalent to 1 /8s, 19 /16s and 76 /24s Percentage of available LACNIC address space announced: 53.8 LACNIC AS Blocks 26592-26623, 27648-28671, plus ERX transfers LACNIC Address Blocks 200/7 Emerging AfriNIC Region Analysis Summary ---------------------------------------- Prefixes being announced by AfriNIC Region ASes: 1087 Total AfriNIC prefixes after maximum aggregation: 640 Prefixes being announced from the AfriNIC address blocks: 916 Unique aggregates announced from the AfriNIC address blocks: 732 AfriNIC Region origin ASes present in the Internet Routing Table: 84 AfriNIC Region origin ASes announcing only one prefix: 29 AfriNIC Region transit ASes present in the Internet Routing Table: 13 Average AfriNIC Region AS path length visible: 4.4 Max AfriNIC Region AS path length visible: 12 Number of AfriNIC addresses announced to Internet: 2198272 Equivalent to 0 /8s, 33 /16s and 139 /24s Percentage of available AfriNIC address space announced: 13.1 AfriNIC AS Blocks ERX transfers AfriNIC Address Blocks 196/8 APNIC Region per AS prefix count summary ---------------------------------------- ASN No of nets /20 equiv MaxAgg Description 1221 781 1193 555 Telstra Pty Ltd 9583 584 44 11 Sify Limited 4755 488 211 112 Videsh Sanchar Nigam Ltd. Aut 4134 430 1943 104 CHINANET-BACKBONE 9443 370 77 76 Primus Telecommunications 4766 366 1699 151 Korea Telecom (KIX) 7545 365 54 66 TPG Internet Pty Ltd 2907 348 1839 322 SINET Japan 17557 334 24 151 Pakistan Telecom 10036 308 28 281 C&M Communication Co. Ltd. 7474 296 268 214 SingTel Optus Pty Ltd 4802 282 47 166 Wantree Development 9498 261 82 53 BHARTI BT INTERNET LTD. 2764 251 238 200 AAPT Limited 703 250 273 205 UUNET - Commercial IP service 9929 246 94 19 China Netcom Corp. 4808 231 168 129 CNCGROUP IP network: China169 18302 218 34 128 SK Global co., Ltd 17488 213 15 11 Hathway IP Over Cable Interne 17974 193 47 11 PT TELEKOMUNIKASI INDONESIA ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 7018 1408 6477 922 AT&T WorldNet Services 174 1065 5544 905 Cogent Communications 721 1019 15619 312 DLA Systems Automation Center 701 966 8209 821 UUNET Technologies, Inc. 4323 961 635 212 Time Warner Telecom 1239 874 2864 627 Sprint 6197 838 365 384 BellSouth Network Solutions, 2386 817 528 616 AT&T Data Communications Serv 18566 788 224 7 Covad Communications 209 624 3372 479 Qwest 20115 599 495 310 Charter Communications 852 534 1069 393 Telus Advanced Communications 3356 524 10745 394 Level 3 Communications, LLC 3602 507 119 92 Sprint Canada, Inc. 3561 506 2199 384 Savvis 27364 504 43 18 Armstrong Cable Services 5668 482 115 25 CenturyTel Internet Holdings, 22773 471 1180 20 Cox Communications, Inc. 7132 427 8385 370 SBC Internet Services 6198 419 372 193 BellSouth Network Solutions, RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 702 524 1674 447 UUNET - Commercial IP service 3320 293 2057 229 Deutsche Telekom AG 3301 286 902 276 TeliaNet Sweden 680 252 2025 237 DFN-IP service G-WiN 8220 239 309 235 COLT Telecommunications 3246 206 388 201 Song Networks 8708 194 243 177 Romania Data Systems S.A. 786 174 1776 174 The JANET IP Service 5515 174 743 124 Sonera Solution Autonomous Sy 1257 172 587 163 SWIPnet Swedish IP Network 719 153 288 96 LANLINK autonomous system 3300 148 168 84 AUCS Communications Services 6746 139 44 121 Dynamic Network Technologies, 3269 138 1273 58 TELECOM ITALIA 25186 136 137 94 France Telecom Transpac's Tra 5400 126 236 112 BT Ignite European Backbone 2856 115 1948 104 BTnet UK Regional network 3215 114 963 68 France Telecom Transpac 3303 106 471 101 Swisscom Ltd 5511 106 157 76 France Telecom LACNIC Region per AS prefix count summary ----------------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 349 527 145 UniNet S.A. de C.V. 16814 266 16 7 NSS, S.A. 11172 216 99 52 Servicios Alestra S.A de C.V 6147 204 100 22 Telefonica Del Peru 19632 190 14 7 Metropolis Intercom S.A. 7303 156 68 25 Telecom Argentina Stet-France 11664 155 19 23 Keytech SA 22047 122 96 6 VTR PUNTO NET S.A. 6503 106 146 75 AVANTEL, S.A. 6505 105 84 68 Global One Communicaoes Ltda 13999 103 52 9 Mega Cable S.A. de C.V. 18822 103 6 15 TELEFONICA MANQUEHUE 11556 99 49 5 Cable-Wireless Panama 19169 95 6 16 Telconet 14117 86 6 3 Telefonica del Sur S.A. 5639 84 12 9 Telecommunications Services o 10481 82 32 7 Prima S.A. 4270 79 18 9 Red de Interconexion Universi 22927 79 65 20 TELEFONICA DE ARGENTINA 23216 78 23 15 RAMtelecom Telecomunicaciones AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 3741 268 635 225 The Internet Solution 2018 90 295 87 Tertiary Education Network 5536 85 13 16 Internet Egypt Network 2905 67 264 61 The Internetworking Company o 8452 54 16 3 TEDATA 24835 53 28 4 RAYA Telecom - Egypt 5713 35 141 28 Telkom SA Ltd 6713 29 46 8 Itissalat Al-MAGHRIB 9129 27 2 2 UUNET Kenya 12455 24 5 4 Jambonet Autonomous system 16637 22 10 19 Johnnic e-Ventures 10798 19 1 11 Standard Bank of South Africa 7460 17 3 4 LIA Internet Access 12258 17 3 11 Vodacom Internet Company 15808 16 1 1 Communication Solutions Ltd i 21491 14 1 1 UTL On-line is RF broadband I 17148 13 1 7 First National Bank 11845 12 9 11 Data Pro Business Online 17400 12 1 1 Pacomm-LDA 21280 12 1 2 Swift Global Kenya Ltd.Is an Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 0 0 65531 * 18566 788 781 Covad Communications 4323 961 749 Time Warner Telecom 721 1019 707 DLA Systems Automation Center 9583 584 573 Sify Limited 27364 504 486 Armstrong Cable Services 5668 482 457 CenturyTel Internet Holdings, 6197 838 454 BellSouth Network Solutions, 22773 471 451 Cox Communications, Inc. 3602 507 415 Sprint Canada, Inc. 4755 488 376 Videsh Sanchar Nigam Ltd. Aut 4134 430 326 CHINANET-BACKBONE 6140 395 324 ImpSat 6467 345 313 E.Spire Communications, Inc. 7545 365 299 TPG Internet Pty Ltd 9443 370 294 Primus Telecommunications 20115 599 289 Charter Communications 6478 378 288 AT&T Worldnet Services 376 391 276 Reseau Interordinateurs Scien 16814 266 259 NSS, S.A. List of Unregistered ASNs (Global) ---------------------------------- Bad AS Designation Network Transit AS Description 35864 UNALLOCATED 38.117.202.0/24 174 Cogent Communication 35884 UNALLOCATED 38.118.171.0/24 10912 InterNAP Network Ser 35894 UNALLOCATED 63.118.207.0/24 6128 Cablevision Systems 35884 UNALLOCATED 64.74.164.0/24 10912 InterNAP Network Ser 35884 UNALLOCATED 64.74.165.0/24 10912 InterNAP Network Ser 35884 UNALLOCATED 64.74.166.0/24 10912 InterNAP Network Ser 35892 UNALLOCATED 64.124.52.0/24 6461 AboveNet Communicati 35892 UNALLOCATED 64.125.105.0/24 6461 AboveNet Communicati 35892 UNALLOCATED 64.125.106.0/24 6461 AboveNet Communicati 35892 UNALLOCATED 64.125.110.0/24 6461 AboveNet Communicati 35890 UNALLOCATED 64.193.55.0/24 209 Qwest 35868 UNALLOCATED 65.88.163.192/26 6395 Broadwing Communicat 35871 UNALLOCATED 66.7.178.0/23 6517 Yipes Communications 35868 UNALLOCATED 68.143.179.64/26 6395 Broadwing Communicat 33507 UNALLOCATED 70.183.41.0/24 15218 COX Communications 35895 UNALLOCATED 72.5.143.0/24 10910 InterNAP Network Ser 64500 RESERVED 85.114.96.0/21 1680 NetVision Ltd. 65503 PRIVATE 193.125.183.0/24 3217 SIMBIRSK 35857 UNALLOCATED 199.107.188.0/24 4323 Time Warner Telecom 65004 PRIVATE 200.0.113.0/24 28477 Universidad Autonoma 65004 PRIVATE 200.4.0.0/24 28477 Universidad Autonoma 65004 PRIVATE 200.4.1.0/24 28477 Universidad Autonoma 65004 PRIVATE 200.4.2.0/24 28477 Universidad Autonoma 65004 PRIVATE 200.4.3.0/24 28477 Universidad Autonoma 65004 PRIVATE 200.4.4.0/24 28477 Universidad Autonoma 65004 PRIVATE 200.4.5.0/24 28477 Universidad Autonoma 65004 PRIVATE 200.4.6.0/24 28477 Universidad Autonoma 35875 UNALLOCATED 204.117.76.0/24 1239 Sprint 35892 UNALLOCATED 208.184.1.0/24 6461 AboveNet Communicati 35850 UNALLOCATED 209.139.6.0/24 3356 Level 3 Communicatio 35850 UNALLOCATED 209.139.22.0/23 3356 Level 3 Communicatio 35850 UNALLOCATED 209.139.56.0/22 3356 Level 3 Communicatio 35850 UNALLOCATED 209.139.108.0/23 3356 Level 3 Communicatio 35850 UNALLOCATED 209.139.110.0/24 3356 Level 3 Communicatio 35850 UNALLOCATED 209.139.180.0/24 3356 Level 3 Communicatio 35892 UNALLOCATED 209.249.93.0/24 6461 AboveNet Communicati 35892 UNALLOCATED 209.249.94.0/24 6461 AboveNet Communicati 35892 UNALLOCATED 209.249.95.0/24 6461 AboveNet Communicati Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 132.0.0.0/10 721 DLA Systems Automation Center 137.0.0.0/13 721 DLA Systems Automation Center 158.0.0.0/13 721 DLA Systems Automation Center 172.32.0.0/24 7011 Citizens Utilities 192.43.230.0/24 7575 Australian Academic and Rease 192.44.0.0/24 5501 Fraunhofer Gesellschaft 192.44.0.0/19 702 UUNET - Commercial IP service 192.70.164.0/24 25689 National Research Council of 192.84.205.0/24 719 LANLINK autonomous system 192.119.135.0/24 270 NASA 192.135.50.0/24 7018 AT&T WorldNet Services 192.172.0.0/19 721 DLA Systems Automation Center 192.200.100.0/24 7018 AT&T WorldNet Services Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:17 /9:2 /10:8 /11:13 /12:60 /13:127 /14:260 /15:472 /16:7497 /17:2028 /18:3414 /19:7717 /20:8814 /21:7649 /22:10537 /23:11751 /24:78503 /25:252 /26:228 /27:130 /28:68 /29:37 /30:61 /31:0 /32:29 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 18566 772 788 Covad Communications 6197 683 838 BellSouth Network Solutions, 7018 610 1408 AT&T WorldNet Services 2386 572 817 AT&T Data Communications Serv 27364 491 504 Armstrong Cable Services 9583 406 584 Sify Limited 4323 402 961 Time Warner Telecom 5668 402 482 CenturyTel Internet Holdings, 1239 348 874 Sprint 702 327 524 UUNET - Commercial IP service 10036 308 308 C&M Communication Co. Ltd. 6198 300 419 BellSouth Network Solutions, 6517 288 311 Yipes Communications, Inc. 7011 270 318 Citizens Utilities 15270 251 269 PaeTec.net -a division of Pae 3320 245 293 Deutsche Telekom AG 20115 244 599 Charter Communications 23126 239 250 KMC Telecom, Inc 22773 236 471 Cox Communications, Inc. 11456 228 268 Carolina Online, Inc. Number of /24s announced per /8 block (Global) ---------------------------------------------- 4:4 8:11 10:6 12:1516 13:1 15:9 16:2 17:3 18:4 20:4 24:794 28:2 31:1 32:64 33:4 38:104 40:53 44:7 47:2 50:1 52:11 54:1 55:3 56:3 57:23 58:37 59:22 60:17 61:738 62:574 63:1879 64:2648 65:2079 66:2734 67:519 68:508 69:961 70:83 71:6 72:128 80:535 81:528 82:369 83:225 84:137 85:160 128:141 129:160 130:89 131:281 132:33 133:1 134:145 135:41 136:191 137:67 138:164 139:56 140:193 141:103 142:137 143:130 144:172 145:32 146:272 147:102 148:293 149:169 150:97 151:63 152:107 153:87 154:4 155:144 156:69 157:89 158:167 159:172 160:73 161:60 162:199 163:83 164:203 165:159 166:154 167:228 168:416 169:137 170:311 171:8 172:1 192:5674 193:3146 194:2326 195:1536 196:638 198:3934 199:3268 200:4010 201:113 202:5443 203:6136 204:3818 205:2006 206:2439 207:2731 208:2075 209:3278 210:1675 211:759 End of report

4 3

RE: books every network operator should read?
by Paul Jasa 09 Apr '05

09 Apr '05

I'd have to say: TCP/IP Illustrated, especially Volume 1 (the other volumes are great too) by W. Richard Stevens pj -----Original Message----- From: owner-nanog(a)merit.edu [mailto:owner-nanog@merit.edu]On Behalf Of Janet Sullivan Sent: Saturday, April 09, 2005 12:37 AM To: nanog(a)nanog.org Subject: books every network operator should read? I'd like to make a list for the BGP4.net wiki of books that are thought highly of by the network community. What books stand out for you as being excellent? If you could only own 5 network related books, what would they be? Feel free to reply to me offlist - I'll post a summary after a few days. Thanks! Janet The information contained in this e-mail and any attached documents may be privileged, confidential and protected from disclosure. If you are not the intended recipient you may not read, copy, distribute or use this information. If you have received this communication in error, please notify the sender immediately by replying to this message and then delete it from your system.

1 0

The power of default configurations
by Sean Donelan 08 Apr '05

08 Apr '05

On Mon, 4 Apr 2005, Paul Vixie wrote: > adding more. oh and as long as you're considering whether to restrict > things to your LAN/campus/ISP, i'm ready to see rfc1918 filters deployed... Why does BIND forward lookups for RFC1918 addresses by default? Why isn't the default not to forward RFC1918 addresses (and martian addresses). If a sysadmin is using BIND in a local network which uses RFC1918 address, those sysdmins can change their configuration?

9 15