February 2000 - Test - lists.nanog.org

The Cidr Report
by Tony Bates 04 Feb '00

04 Feb '00

This is an auto-generated mail on Fri Feb 4 12:00:00 PST 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 04Feb00 0) General Status Table History ------------- Date Prefixes 280100 70416 290100 70627 300100 70736 310100 70866 010200 71239 020200 71006 030200 71078 040200 71335 Check http://www.employees.org/~tbates/cidr.plot.html for a plot of the table history. Possible Bogus Routes --------------------- *** Bogus 219.91.160.0/22 from AS7742 *** Bogus 219.91.164.0/23 from AS7742 AS Summary ---------- Number of ASes in routing system: 6584 Number of ASes announcing only one prefix: 3579 (1939 cidr, 1640 classful) Largest number of cidr routes: 714 announced by AS701 Largest number of classful routes: 982 announced by AS701 1) Gains by aggregating at the origin AS level --- 04Feb00 --- ASnum NetsNow NetsCIDR NetGain % Gain Description AS271 439 153 286 65.1% BCnet Backbone AS7046 426 280 146 34.3% UUNET-CUSTOMER AS9269 141 25 116 82.3% Hong Kong CTI AS1221 633 519 114 18.0% TELSTRA-AS AS2609 123 18 105 85.4% EUnet-TN AS7657 286 188 98 34.3% The Internet Group Limited AS4293 265 169 96 36.2% Internal ASN for C&W AS2715 155 61 94 60.6% REDERIO-AS AS7545 154 61 93 60.4% TPG Internet Pty Ltd AS9706 116 29 87 75.0% Pusan Metropolitan City Office of AS6429 204 119 85 41.7% RDC-INTERNET AS174 555 472 83 15.0% Performance Systems International AS7496 121 39 82 67.8% Power Up AS705 296 216 80 27.0% ALTERNET-AS AS577 255 178 77 30.2% Bell Backbone AS3749 137 61 76 55.5% TECNET AS9304 99 24 75 75.8% Hutchcity AS816 373 298 75 20.1% UUNET Canada (ASN-UUNETCA-AS4) AS3602 314 246 68 21.7% Sprint Canada Inc. AS7029 112 47 65 58.0% ALLTELNET AS4200 169 104 65 38.5% AGIS (Apex Global Information Ser AS4740 333 275 58 17.4% Ozemail Pty Ltd (ASN-OZEMAIL) AS7260 103 46 57 55.3% NORLIGHT AS1727 124 70 54 43.5% MRMS-WEST AS209 384 333 51 13.3% Qwest Communications AS4151 97 50 47 48.5% USDA Internet Access Network AS9557 67 21 46 68.7% Pakistan Telecommunication Compan AS7568 59 15 44 74.6% C.S. Communications Co., Ltd. AS4000 88 45 43 48.9% Global IP AS684 87 45 42 48.3% Manitoba Regional Network Backbon 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

Superbowl success?
by Sean Donelan 04 Feb '00

04 Feb '00

Not necessarily a major Internet event, but it appears superbowl releated web sites did well this year. According to Keynote's press release http://biz.yahoo.com/bw/000202/ca_keynote_1.html only one superbowl advertisor web site out of 35 was inaccessible during the superbowl. I didn't notice any significant correlation between the network provider and the performance of the web site. Are folks getting better at predicting advertising generated traffic? Or are people just massively over-provising their web sites, and praying?

3 2

Re: SERVER NAMES
by Jeff Weisberg 03 Feb '00

03 Feb '00

| This is a little off of the normal lines of the list. But I am at a loss as | to what naming convention I should use with my new set of servers. I have | already used Southpark, Jet sons,and Warner brothers cartoons. Does any one | have any good suggestions other than the Super Friends? you can do themes like: favorite RFCs, network protocols, or NANOG participants, ... the box on my desk is "rfc1178.op.net" --jeff

3 2

Re: SERVER NAMES
by Andrew Bender 03 Feb '00

03 Feb '00

At the risk of suggesting that Bellcore solved the problem, aren't there some prevailing standards here? Andrew Bender tns-inc.com > From: DeepBlue > > This is a little off of the normal lines of the list. But I am > at a loss as to what naming convention I should use with my new > set of servers.

4 3

RE: SERVER NAMES
by York, Tracy (CEI-Atlanta) 03 Feb '00

03 Feb '00

One word... BEER. McEwans Tennants John Courage ...you get the picture. -TY "Give beer to those who are perishing..." (Proverbs 31:6) -----Original Message----- From: Patrick Evans [mailto:pre@pre.org] Sent: Thursday, February 03, 2000 5:35 AM To: Patrick Greenwell Cc: nanog(a)merit.edu Subject: Re: SERVER NAMES On Wed, 2 Feb 2000, Patrick Greenwell wrote: > Not picking on you in particular, but isn't one of the greatest > advantages to having DNS to offer *meaningful* names to > machines(assuming anything other than a home network?) > > It's nice to be able to go in to a company and see machines named > "www1, www2, mx1, mx2" etc. which offer some indication as to > their purpose rather than "maverick, foozlebutt, blarg", etc. > which offers no such indication. I know it isn't as fun, but it > certainly seems to be much more useful (IMO of course...) > On our network we use "proper hostnames" for the machines and their base addresses, and then associate mundane things like 'www' or 'ns0' as logical interfaces - means we can swing a service from one machine to another without needing to mess with base addresses. As for what those proper hostnames are, historically we've used Pooh characters (tigger being the company's first server, because he who put it together wasn't entirely sure it wouldn't bounce regularly). We ran out of those a while back, so new internal servers are being named after muppets, office workstations are based after underground stations (guess who got cockfosters for an NT box), and the mail servers I'm putting together at the moment are named after appropriate chocolate bars (flake, timeout and so on...) One of our competitors seems to have servers named after cigarette brands, which was rather novel. There are few pleasures in day to day sysadmin/netadmin work, no reason to give up the chance to use original hostnames...original not applying to gods, chemical elements and the like! -- Patrick Evans - Sysadmin, bran addict and couch potato pre at pre dot org www.pre.org/pre

1 0

Re: inter-NOC communications (was:Re: Definition of Congestion)
by Sean Donelan 03 Feb '00

03 Feb '00

On Tue, 01 February 2000, Bill Woodcock wrote: > I agree entirely. I can't stand it when people are too sheepish to > publish Best Common Practices just because there are a few companies that > don't feel like putting in the effort to do a halfway decent job. God > knows we wouldn't want anyone to feel left out, even if they do insist on > running open relays, or redistributing their IGP or whatever. Bleah. Do you mean like http://dranet.dra.com/draft-donelan-rnmg-latest.txt

2 1

Re: SERVER NAMES
by Sean Donelan 03 Feb '00

03 Feb '00

On Thu, 03 February 2000, Steve Sobol wrote: > Jeff Weisberg wrote: > > you can do themes like: favorite RFCs, network protocols, > > or NANOG participants, ... > > Make sure you name the box containing your network monitoring software > "donelan.yourcompany.net" :) That should be "the-other-sean.yourcompany.net" However, some people might believe it will jinx their network, or attract undesirable backhoes. A bit like naming your ATM switch "sean-no-cells-doran.yourcompany.net."

1 0

Re: SERVER NAMES
by Patrick Greenwell 03 Feb '00

03 Feb '00

On Wed, 2 Feb 2000 owen(a)exodus.net wrote: > > OK... Now it's crossed into the arena of my pet peeves, so I'll vent my > opinion... > > > I believe that most machines should have at least two names... > > mx1 mx2 mx3... should be assigned as CNAME records to the > actual machine name (see below) that the > machine currently performing that function > is known by. Hmmmm... MX records are CNAMES? Doesn't that cause problems with a certain popular MTA? /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\ Patrick Greenwell Earth is a single point of failure. \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/

1 0

Request for Assistance
by ken.woods＠SWADMIN.SWEETWATER.TSTC.EDU 03 Feb '00

03 Feb '00

I am currently preparing to offer a bid package for OC-3 Internet access to several Tier 1 providers. Can anyone provide me with any hard learned lessons as to what I need to be using as a measure in evaluating vendor proposals other than SLA, mean uptime, redundancy, trouble ticket escalation, cost, etc. What I'm looking for are the things that you look back and say if only I had know about this six months ago. Please reply privately to: ken.woods(a)sweetwater.tstc.edu Thank You, Ken Woods Director of Network Administration Texas State Technical College 915-235-7326

2 1

early warning mailing list?
by Dan Hollis 02 Feb '00

02 Feb '00

Is there an 'early warning' mailing list for up-to-the-minute alerts about in-progress DoS attacks, portscanning, etc? -Dan

4 3