August 2000 - Test - lists.nanog.org

Formal study: How many points networks share
by Sean Donelan 28 Aug '00

28 Aug '00

After the thread a couple of weeks ago on how many nexuses are needed for the Internet to work, the MIB (actually a woman, but that's a different thread) asked if there were any formal studies. Have any providers done a formal study of how many points they share in common with other networks? I know most providers consider their competition, if nothing else for how peering will be done. There seems to be a tremendous amount of overlap between networks. Almost every major network map looks identical. And there are some third-party consultants selling network maps. But I was wondering if anyone had a formal study from "the horses mouth."

5 5

Re: Follow-up to "ROOT SERVERS"
by Sean Donelan 26 Aug '00

26 Aug '00

I'm confused again after reading Network Solutions press release. The press release makes it sound like the problem was with the four other root servers. On the other hand the technical description sounds like the original problem was with NSI's root-server. NSI's server dropped the COM zone from the root name file. The other servers simply copied the information provided by NSI's server to their servers, and are only cupable so far as NSI's server provided a root zone file missing information. Is this correct? If the mistake was four independent root servers made the same mistake at the same time, I'd like to know how. Further the Network Solutions press release statesthe impact was negligible because DNS resolvers look for multiple servers. This is only partially true. DNS resolvers look for other servers only when a server is unavailable. However, when a server has incorrect information, such as a root zone missing a delegated zone, won't the other servers return NXDOMAIN which resolvers will assume is an authoritative answer? Therefore any user of those four other servers would have received authoratative answers that .COM did not exist? How many queries do those four servers normally handle? Is this correct? I realize that press releases aren't intended to convey technical information, and therefore it is important to release the technical information through other channels. But a press release should keep close to what happened.

3 2

Broadwing Problems
by Ido Dubrawsky 26 Aug '00

26 Aug '00

Last night at 6:07 p.m. Broadwing appears to have had two problems occur: 1. A line card in a router near Chicago, IL failed and 2. A switch in Haywood, CA. had significant congestion Has anyone else had problems because of this? My network was pretty much cut off from the rest of the internet. Ido -- Ido Dubrawsky Team Lead, UNIX and Network Systems E-mail: ido(a)globeset.com Information Services/Facilities Globeset.com Austin, TX

1 0

Now the idiots at ORBS are probing random dial-ups
by Barry Shein 26 Aug '00

26 Aug '00

Obviously random dial-ups have different hosts logged on each time they try, often no one is logged on. So of course they get to imagine whatever they like (e.g., when no one is dialed up that maybe they've been firewalled.) Somehow their broken software imagines it sees the same open relay repeatedly on some random dialup IP, which of course is incredibly unlikely. Is there any reasonable way to tell these ORBS and MAPS losers "possibly good intentions, but so badly run that: no thanks" from the net administrator community. I'm really getting sick of these incompetent self-promoters wasting peoples' times. Maybe if they heard enough voices telling them "no thanks" they'd get the hint their efforts are not appreciated and not wanted. Oh, and a word from ORBS' fearless leader: From alan(a)manawatu.gen.nz Sun Feb 7 23:11:52 1999 >As for you, fuck off. Your attitude has got you a permanent entry in ght >shub list. No doubt something to do with all the attention I get from these jerks. -- -Barry Shein Software Tool & Die | bzs(a)world.std.com | http://www.TheWorld.com Purveyors to the Trade | Voice: 617-739-0202 | Login: 617-739-WRLD The World | Public Access Internet | Since 1989 *oo*

15 25

Cyber-Biz Secrets
by Successfulone＠aol.com 26 Aug '00

26 Aug '00

The Truth Is Finally Revealed.... How Does The Richest Man In The World Use The Greatest Business Secrets Of All Time To Make Over 32.4 Million Dollars A Day?!! No matter who you are, where you live or what your sex, age or race is by the time you finish reading this special article, you will know: * How to start a proven money making business that requires no inventory, no shipping and no employees within 7 days, guaranteed! * How to get a $300 professionally designed Web Site for FREE! * How to increase your sales by more than 137% in 30 days regardless of your business! * How to get paid for a 1000-hour workweek, without going to work! * How to turn 50 cents into $50, with a simple click of a button! * How to get a $179 business-building CD-ROM for FREE! * If you ever wanted a business where you could hit the ground running.... a business where you could just open a box and start making immediate profits.... a business that's completely set up and ready to pull in maximum sales.... with a product that sells itself... then I've got some great news for you! Act NOW <<<<<< There is A DEADLINE!!! >>>>>> Instant Information Request Directions: **>NOTE: You may also just Click Below to send it through your normal e-mail program. mailto:itsyourchoice@netease.com?subject=send_info_on_infomax825 It's much easier to do it this way, it will fill in the return e-mail and subject for you. 2. You will receive the complete info on the reports via e-mail within 24 hours. P.S. Act NOW!-- Only the first 75 requests will be granted to receive this Special Web Site e-Report for *FREE* titled "The Greatest Business Secrets Of All Time" P.P.S. *FREE Download Bonus e-Manual* "Microsoft, Viagra & Your Business Success" given to the first 35 people to respond within the next 24 hours, Your FREE reports will be fulfilled in the order in which they were received. Privacy Policy: We respect your privacy and your e-mail address/name will be kept strictly private it will never be sold, shared or given away for any reason. Simple Removal Instructions: To Be Removed: mailto:unsubscribe@netease.com?subject=remove825 You will then be deleted from our e-mail database forever. NO FLAMES!! You will not be added to the remove database unless you do this. No Exceptions, anything but "remove" in the subject will generate an automatic response. Thank You!!

1 0

Follow-up to "ROOT SERVERS"
by Verd, Brad 25 Aug '00

25 Aug '00

EXECUTIVE SUMMARY ----------------- At 1830 EDT on 8/23/2000, the Network Solutions Registry was notified of a problem with four root name servers--b.root-servers.net, g.root-servers.net, j.root-servers.net and m.root-servers.net. The root zone on each of these servers was missing delegation information (NS records) for the com zone. The NSI Registry took immediate action, working with the operators for each of these root name servers to correct the problem. B.root, g.root and j.root were corrected by 1900 EDT; m.root by 1950 EDT. At no point did NSI make any changes to the root zone. The absence of the com zone delegation information on these name servers resulted from BIND name server behavior that is described in greater detail below. NSI acted immediately to resolve the problem, implemented immediate procedures to avoid recurrence in the short term, and has an action plan to implement a more robust longer-term solution. ROOT CAUSE ---------- If a BIND name server is authoritative for both a child zone and its parent zone, and the name server is restarted or reloaded with a missing zone database file for the child zone, the name server removes the child zone's delegation information from the in-memory copy of the parent zone. As part of NSI's zone generation process, there is a small time interval when the com zone database is not present on the NSI name server in question (during the backup of the old database and copying of the new database). On Wednesday, the name server was manually restarted during this interval; therefore, the name server removed the com zone delegation information from the root zone held in memory. NSI had never encountered this BIND behavior before, nor were several BIND experts we contacted aware of its existence. Subsequent investigation by NSI has revealed that BIND versions 8.1.2 and 8.2.2-P5 exhibit this behavior, but BIND 9.0.0rc4 does not. Nominum has indicated it will pursue a patch to BIND 8. CORRECTIVE ACTIONS ------------------ To restore service, NSI immediately reinstated the com zone database file on our server, increased the root zone's serial number and restarted the name server. B.root, g.root, and j.root immediately loaded the new root zone and were correctly issuing referrals to the com zone within minutes. M.root (in Japan) took nearly an hour to load the new root zone. NSI is modifying the current zone generation process to eliminate the existing small interval during which the com zone database file is not present on this nameserver. Until then, NSI is manually querying the root zone to ensure no delegations have been automatically dropped. -------------------------------------- Brad Verd gTLD Operations Manager Network Solutions Registry Email - bverd(a)netsol.com ---------------------------------------

2 1

Re: NRIC Monitoring ISPs
by Kelly J. Cooper 25 Aug '00

25 Aug '00

On Aug 25, 12:43pm, Sean Donelan wrote: > Subject: Re: NRIC Monitoring ISPs * *On Fri, 25 August 2000, Roy wrote: *> Since the NRIC is contacting industry groups, it seems to me that they should *> contact NANOG! Perhaps NRIC will present at the next meeting? * *I've only been to one NRIC meeting. What a snore. Not even any good *hallway/bar conversations. * *The problem with the Internet is it either has too many industry groups *or not enough. CIX, ITAA, ISP/C, TISPA, ISOC, IETF, ICANN, IOPS, ASPF, *etc. And AOL is a industry representative of one. The reality is NRIC *or the FCC has no idea who to contact about Internet issues. I suspect, *but don't know, NRIC sent a letter to IOPS and considers that the industry. Close! But no cigar. Although IOPS communicates with NRIC through the CNRI-based IOPS coordinator (Ira Richer) who earns that by attending their meetings, NRIC is actually planning on contacting around 50 ISPs, Telcos doing ISP-like stuff, some of the larger vendors as well as some industry groups - all independently. Kelly J. -- Kelly J. Cooper - Internet Security Officer GENUiTY - Main # - 800-632-7638 3 Van de Graaff Drive - Fax - 781-262-2819 Burlington, MA 01803 - http://www.genuity.net

1 0

Re: NRIC Monitoring ISPs
by Robert Cannon 25 Aug '00

25 Aug '00

I think Sean is correct. Ira Ritcher was on NRIC IV and I understand from Ira the original proposal to include ISP monitoring came from Ira. Ira was not actually representing IOPS before NRIC IV and neither Ira nor IOPS are members of the current NRIC, NRIC V. Nothing on the IOPS webpage reflects any news in this regard. More to come. -B www.cybertelecom.org ------Original Message------ From: Sean Donelan <sean(a)donelan.com> To: garlic(a)garlic.com Sent: August 25, 2000 7:43:26 PM GMT Subject: Re: NRIC Monitoring ISPs On Fri, 25 August 2000, Roy wrote: > Since the NRIC is contacting industry groups, it seems to me that they should > contact NANOG! Perhaps NRIC will present at the next meeting? I've only been to one NRIC meeting. What a snore. Not even any good hallway/bar conversations. The problem with the Internet is it either has too many industry groups or not enough. CIX, ITAA, ISP/C, TISPA, ISOC, IETF, ICANN, IOPS, ASPF, etc. And AOL is a industry representative of one. The reality is NRIC or the FCC has no idea who to contact about Internet issues. I suspect, but don't know, NRIC sent a letter to IOPS and considers that the industry. ______________________________________________ FREE Personalized Email at Mail.com Sign up at http://www.mail.com/?sr=signup

1 0

Re: NRIC Monitoring ISPs
by Sean Donelan 25 Aug '00

25 Aug '00

On Fri, 25 August 2000, Roy wrote: > Since the NRIC is contacting industry groups, it seems to me that they should > contact NANOG! Perhaps NRIC will present at the next meeting? I've only been to one NRIC meeting. What a snore. Not even any good hallway/bar conversations. The problem with the Internet is it either has too many industry groups or not enough. CIX, ITAA, ISP/C, TISPA, ISOC, IETF, ICANN, IOPS, ASPF, etc. And AOL is a industry representative of one. The reality is NRIC or the FCC has no idea who to contact about Internet issues. I suspect, but don't know, NRIC sent a letter to IOPS and considers that the industry.

1 0

The Cidr Report
by Tony Bates 25 Aug '00

25 Aug '00

This is an auto-generated mail on Fri Aug 25 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 25Aug00 0) General Status Table History ------------- Date Prefixes 180800 85012 190800 84653 200800 84576 210800 84539 220800 86440 230800 85617 240800 85297 250800 85144 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: 6240 Number of ASes announcing only one prefix: 3082 (1039 cidr, 2043 classful) Largest number of cidr routes: 589 announced by AS705 Largest number of classful routes: 1076 announced by AS701 1) Gains by aggregating at the origin AS level --- 25Aug00 --- ASnum NetsNow NetsCIDR NetGain % Gain Description AS12935 12 3 9 75.0% Nocom.net AB, HQ Stockholm AS9655 11 3 8 72.7% Startvision AS12540 10 2 8 80.0% IdecNet Autonomous System AS9867 10 3 7 70.0% CHONJU TECHNICAL COLLEGE AS9772 8 1 7 87.5% Mighty Information Systems AS7980 9 2 7 77.8% Global One Communications AS7959 12 5 7 58.3% VICON AS7888 12 5 7 58.3% CSI Health Autonomous System Obje AS7453 8 1 7 87.5% GTINET AS6630 9 2 7 77.8% LOA AS6614 8 1 7 87.5% USCC-ASN AS3753 10 3 7 70.0% NSCEE AS3339 9 2 7 77.8% AT&T Israel AS14677 11 4 7 63.6% UNKNOWN AS14659 8 1 7 87.5% LivePerson, Inc. AS14204 8 1 7 87.5% UNKNOWN AS14062 11 4 7 63.6% UNKNOWN AS13894 10 3 7 70.0% UNKNOWN AS13761 8 1 7 87.5% IMPSAT Brasil AS13418 10 3 7 70.0% UNKNOWN AS12671 8 1 7 87.5% Jordan Internet Network Autonomou AS11950 8 1 7 87.5% UNKNOWN AS11900 9 2 7 77.8% UNKNOWN AS11699 10 3 7 70.0% Blue Mountain Internet AS10647 10 3 7 70.0% UNKNOWN AS10242 12 5 7 58.3% USINTERNET AS10044 10 3 7 70.0% Wonkwang Health Science College AS8221 12 6 6 50.0% Isabel-Belgium AS7699 10 4 6 60.0% Weblink Philippines Inc AS6296 12 6 6 50.0% MIND 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

1 0