- Test - lists.nanog.org

DNS contamination
by dvv＠sprint.net 24 Jan '97

24 Jan '97

To all DNS admins: please check that you don't have 199.0.55.3 and 144.228.8.227 mentioned anywhere in your files. If you do, remove such records and change your DNS server software to something more reasonable. Dima fed up his ears with named's chronic inability to filter out bogus additional records

7 11

NANOG Meeting
by Pam Ciesla 24 Jan '97

24 Jan '97

The NANOG Meeting will be February 10 & 11 in San Francisco at the Grand Hyatt. Information is available on the web page http://www.nanog.org. If you need more info send me e-mail. Pam

1 0

NANOG Registration
by Pam Ciesla 23 Jan '97

23 Jan '97

Please note that ALL attendees MUST register via the web page. Thanks Pam

1 0

NANOG MEETING REMINDER
by Pam Ciesla 23 Jan '97

23 Jan '97

Deadline for registration is Friday, January 31. All registered attendees should have payment in by January 31. This is to avoid delays at the meeting site. If you have registered and not given a form of payment please do so ASAP either by calling (313-936-0172) or faxing (313-647-3185). If you cannot make the payment deadline either call or send e-mail to make other arrangements. THANKS Pam

1 0

Draft NANOG agenda
by Susan R. Harris 23 Jan '97

23 Jan '97

Here's what we have so far ... --------------------------------------------------------------- North American Network Operators Group (NANOG) Draft Agenda Monday, February 10 Time Topic Presenter(s) ---- ----- --------------------- 9:00 am Welcome, Introductions, Bill Norton, Merit Future Meetings 9:30 am End-to-End TCP Packet Vern Paxson, Lawrence Dynamics Berkeley Lab 10:00 am TCP Response Under Loss Curtis Villamizar, ANS Conditions 10:30 am Break 10:45 am Common Metrics for Exchange Kim Claffy, NLANR, Points moderator 12-1:30 pm Lunch 1:30 pm Blocking in the GIGAswitch Bob Simcoe, Digital 2:00 pm Internet II: Pragmatic Steve Corbato, Views from Higher Education Univ. of Washington Dave Meyer, Univ. of Oregon 2:30 pm InterNIC Update Mark Kosters and Kim Hubbard, InterNIC 3:15 pm Using the IRR to Assist Curtis Villamizar, ANS With Aggregation 3:30 pm Break 3:45 pm Introducing Trawhoisd Xin Liu, Merit 4:15 pm Report on Inter-Provider Randy Bush, RGnet Cooperation 4:30 pm Consideration of Policy: Laura Cunningham, MCI What's Needed and Can RSVP Help? Tuesday, February 11 -------------------- 9:00 am RA Update Bill Norton, Merit Bill Manning, ISI 9:30 am Internet Routing Rob Malan, Univ. of Instability Michigan 10:00 am Squid Update Duane Wessels, NLANR 10:30 am Break 10:45 am Non-BGP Multihoming for Web Paul Vixie, CIX Sites 11:15 am Pathologic Applications in Curtis Villamizar, ANS the Internet 11:30 am Flow Switching Analysis Daniel McRobb, ANS 11:30-1:30 Lunch -------------- BOFs: Track 1 -------------- 1:30-2:30 pm TBA 2:30-3:30 pm Flow Switching Analysis John Hawkinson, BBN Planet Daniel McRobb, ANS moderators -------------- BOFs: Track 2 -------------- 1:30-2:30 pm Route Server Peering at the Jake Khuon and IXPs: Procedures, Policy, Abha Ahuja, Merit and Connectivity 2:30-3:30 MLPAs: All for One, One for Bill Woodcock, All Packet Clearing House, moderator 3:30 pm Break ----------------------- Back to Plenary Session ------------------------ 3:45 pm Controlling Network Abuse Paul Vixie, CIX Using BGP-4 4:15 pm Closing Remarks Bill Norton, Merit 4:30 pm Adjourn

1 0

cflowd-1.2alpha... whoops
by Daniel McRobb 23 Jan '97

23 Jan '97

Sorry, I missed a bad setsockopt() call and some stuff for Solaris and mmap(). Reload the WWW page at http://engr.ans.net/cflowd/index.html and grab cflowd-1.2-alpha3.tar.gz Still uncompiled/tested by me anywhere other than AIX. I'll put updates on the WWW page as we (mostly caida folks) finish ports. Daniel ~~~~~~

1 0

New cflowd bits
by Daniel McRobb 23 Jan '97

23 Jan '97

Hi folks. I just posted a new version of cflowd at: http://engr.ans.net/cflowd/index.html The new version (1.2-alpha) has a rewritten raw flow module using memory-mapped I/O. For those of you that have used it, you can now turn on raw flow logging and not thrash your machine with flow->disk I/O. The new version also has a bug fix for remote client connections; this is an old fix I never got around to posting. The code is still based on some old beta Cisco bits which include AS numbers in flow-export. I don't know the status of getting that code into ELC, but I'll try to find out (Paul? Dave? Anyone?). In about 5 minutes, I'll be deploying this new code on a few ANS machines and leaving raw flow logging turned on. Who knows, maybe I'll have a silly SYN flood story for San Francisco. I do have about 3 month's worth of AS matrix data (5-minute polling intervals) on-line and have a lot of charts. I'll put up some of my slides at the site above soon. Daniel ~~~~~~ P.S. - I've only tested the latest on AIX 3.2.5... in fact I've only *compiled* it on AIX 3.2.5. Hopefully it'll still compile/run fine on the platforms targetted in the original version. You can send bugs to me just like before; I make no guarantees I'll reply or have time to fix anything, but I do promise to at least tuck away the mail until I have a chance to look at it or I need the disk space back. ;-)

1 0

Power outage in San Francisco
by Rob Liebschutz 23 Jan '97

23 Jan '97

There is a power outage in San Francisco affecting a large area South of Market Street, including China Basin. The outage begain shortly after 12:00am PST Wednesday and was caused by flooding of an underground PG&E transformer. Current estimated restoral of power by PG&E is around 6:00pm Wednesday. (Prior estimates were for 12:00 noon). Whole Earth Networks has was down all night. We've been coming up slowly as we pull in power feeds from mobile generators. The China Basin complex where we are located has been quite a scene, with cables running out the to roof and down the side of the building to generators running in the courtyard below. There's been alot of cooperation amoungst providers with Sprint and TCG sharing spare power capacity on the generators and pulling wires to other providers in the building. MFS has also been helping their customers with power restoral. MCI has a big mobile generator in the courtyard as well. The power for the emergency lighting in the complex (multiple 6 story buildings) lasted only a few hours and we're all running around in the halls with flashlights. A big lesson to be learned by all. Rumor has it that we now have approval now for the purchase of our own generator. Rob

3 2

Re: random thoughts on how I can prevent spammers from using my net
by Barry Shein 22 Jan '97

22 Jan '97

We have had a similar pricing policy for years and have collected on it, a few times in the $1000 range. On January 20, 1997 at 17:07 dorn(a)atlanta.net (ALAN DORN HETZEL, Jr.) wrote: > Great idea. > > How many people have you collected on? :) > > - Jared > > > None yet. Haven't gotten contract language written > for it yet. That's why I'm bouncing it around here > before I go to that stage... > > > -Dorn -- -Barry Shein Software Tool & Die | bzs(a)world.std.com | http://www.std.com Purveyors to the Trade | Voice: 617-739-0202 | Login: 617-739-WRLD The World | Public Access Internet | Since 1989

1 0

Re: Suggestion for NANOG Meeting
by Sean Donelan 21 Jan '97

21 Jan '97

>As a carrier, we at ACSI have issued a statement that we cannot be >responsible for customer traffic. I know that legally we cannot filter >any customer traffic, but I am really getting sick of getting emails >about customers that continue to send unsolicited emails. We as a >community need to come up with a common carrier policy on how to handle >such customers and how to deal with complaints. Talk to you company lawyer about what you legally can and can not do. Even common carriers have a lot of leeway writing their tariffs. Yes, tariff writing is a business decision. Common carriers write the darndest things in their tariffs. And even more amazing, if you had a smart lawyer write the right things, you can get a court to enforce those darndest things too. Personally, I would be happy if the IETF-RUN group put out a document on the right and wrong way to complain. Spamming your complaint about spam is a bit hippocritical. -- Sean Donelan, Data Research Associates, Inc, St. Louis, MO Affiliation given for identification not representation

2 1