- NANOG - lists.nanog.org

isp cooperation
by Ehud Gavron 17 Jan '96

17 Jan '96

I hate to break from the thread of > Hi, thank you. > Herb. However, I've got a question for the community at large. In a recent client switchover, we discovered The Other ISP had no clue about DNS. Despite our best efforts to get their "technical" support involved, we discovered they had none. When we asked them to enable DNS zone transfers, they said "We don't allow that. Edit your files; if you don't know how to do that then you shouldn't be running DNS." This haughty attitude punctuated their incompetence and lack of technical savvy. Now stuck in the middle of this is the customer, who just wants the service transfered, and really doesn't want to hear things like "Domain zone transfer," "file editing," or "variable shield frequency modulation." Any ideas on how to gain cooperation from what is clearly a "two-kid" shop of a few teenagers pretending to run an ISP with a holier-than-thou attitude and the technical knowhow of a Newt (with apologies to Mr. Speaker)? Ehud p.s. I don't mean any of my comments to imply that Iserver.Com is run by a bunch of teenagers with no technical savvy. It just appears that way.

2 1

Network Access Points
by Canadian IP Registration 17 Jan '96

17 Jan '96

Hi, is there a list of ISPs that are connected to the Network Access Points? Please, if there is such an animal, can you tell me where it is or send it to me, I need it asap. Thanks Herb

3 6

Definitions, please....
by Canadian IP Registration 17 Jan '96

17 Jan '96

Hi, can somebody point me at or give me some sort of at least semi-formal definition of the following terms: NAP MAE-EAST MAE-WEST Anything would help. Thank you. Herb Kugel

3 4

None
by Vir Lagua 17 Jan '96

17 Jan '96

subscribe nanog capprove gators subscribe nanaog russ(a)ism.net

1 0

Re: Welcome to nanog
by owen＠DeLong.SJ.CA.US 16 Jan '96

16 Jan '96

> Err, just one question ... > > > > > Welcome to the nanog mailing list! > > > > If you ever want to remove yourself from this mailing list, > > you can send mail to "Majordomo" with the following command > > in the body of your email message: > > Why the impossible to remember unsubscribe command below ?! > The command below is the result of someone sending a similar subscribe command which subscribed the nanog list to itself, causing the welcome message to be sent to the entire list. Majordomo apparently accepts lists of people to subscribe or treats everything after the mailing list name as part of the name subscribing. Either way, the effect is the same. > > unsubscribe nanog capprove gators subscribe nanog russ(a)ism.net > > It seems that for many, just sending an 'unsubscribe nanog' command > without sending to the list is difficult. > > Certainly the algorithm above is no easier to remember :-) > > Hmmmm. > > Tim > Again, disregard it. It's an error. > > > Here's the general information for the list you've > > subscribed to, in case you don't already have it: > > > > North American Network Operators Group > > > > Owen

3 2

Welcome to nanog
by Majordomo＠merit.edu 16 Jan '96

16 Jan '96

-- Welcome to the nanog mailing list! If you ever want to remove yourself from this mailing list, you can send mail to "Majordomo" with the following command in the body of your email message: unsubscribe nanog capprove gators subscribe nanog russ(a)ism.net Here's the general information for the list you've subscribed to, in case you don't already have it: North American Network Operators Group

2 1

Re: meeting agenda
by Sean Donelan 15 Jan '96

15 Jan '96

>Hello Alan - Here's a PARTIAL list of presentations we've planned so far: I hesitate to suggest a presentation, because I don't have any solutions only problems. A couple of months ago this list had a thread on communicating network outage information, network usability, and generally keeping network operators and users informed about the current state of the net. - Overall network reliability tracking, better or worse? While individual network providers track their own network reliability, is there a need to report and track some data on an Internet-wide basis similar to the reliability reporting done in other industries (telephone, airline, etc)? While anyone could track network outages on their own through massive invasive testing, it usually doesn't reveal the cause of the outage. What is the biggest threat to network reliability? A farmer with a backhoe, or a network engineer at a console? Is there a neutral third-party which could blind and summarize the data? I'm not an academic type, so I don't know what would be involved in getting funding at one of the national labs for such a project. Or do we wait the the FCC to mandate something? - No one is perfect Everyone should plan for the disaster which will hit their network at some point. Whenever a network melts down, the next thing to go is the NOC communication lines. I haven't seen a network provider with sufficient staff to answer all the calls, and repair their network at the same time when it goes down. Either calls go unanswered, or the network doesn't get repaired, or sometimes both. The 1-800 problem reporting method isn't scaling well. Alternatives? - Everything hasn't failed at once [for a long time] I don't think there has been an Internet-wide ('net-wide) failure since BBN made Butterfly gateways and one lost its mind. This means, even though one network provider is wiped out, other networks could pass along reports about the current state of the network. How can this reporting function be decentralized? - Finally, keep network users informed Since we have a hard time tracking who is using what (if we even wanted to track users), out-of-band notification isn't great for notifying users. Ideally the network itself could be used to inform just those users affected why things aren't working. Any chance of wedging a "user information" field into the IPng ICMP destination unreachable message? It would be nice to tell the user in the ICMP message: "Beep BOOP BEEP, We're sorry your packet could not be delivered as addressed due to a ...." Instead of waiting for the users to call the NOC which probably is already snowed under with calls. Since the 'net as a whole doesn't fail that often, but pieces of the 'net fail frequently, in-band notification isn't as crazy an idea as it seems. Any thoughts how to turn this into a presentation topic? -- Sean Donelan, Data Research Associates, Inc, St. Louis, MO Affiliation given for identification not representation

3 2

Next NANOG Meetings...
by William B. Norton 12 Jan '96

12 Jan '96

Someone suggested a posting about the subsequent NANOG meetings. THis is what we have tentatively planned: Host Location Date --------------------------------- SDSC San Diego, CA Feb 15-16 CIX Washington, DC May ?? Merit Ann Arbor, MI Oct ?? Hope this helps. More details as they become available. Bill BTW - We are looking for sites interested in hosting a NANOG meeting in the future. If you are interested, we have installed a "Tips for Hosting a NANOG Meeting" document on the NANOG home page. NANOG Home Page: http://www.ra.net/routing.arbiter/NANOG/NANOG.html ------------------------------------------------------------------------- William B. Norton Merit Network Inc. e-mail: wbn(a)merit.edu phone: (313) 936-2656 WWW: http://home.merit.edu/~wbn

1 0

Hotels for NANOG
by Pam Ciesla 11 Jan '96

11 Jan '96

When registering at the hotels in San Diego mention the NANOG Meeting, if there is a problem let them know it is a meeting being held at SDSC. Pam

1 0

Tutorial Announcement
by Ed DeHart 11 Jan '96

11 Jan '96

Hello, Enclosed is an announcement for a tutorial that the CERT Coordination Center will be presenting at the Software Engineering Institute in Pittsburgh four times this year. A registration form is included after the announcement. Thanks, Ed DeHart P.S. If you plan to use a credit card, please do not e-mail your registration form. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= ANNOUNCING ---------- INTERNET SECURITY FOR SYSTEM AND NETWORK ADMINISTRATORS First offering... February 15 at the Software Engineering Institute Pittsburgh, PA Who should attend? * practitioners (UNIX system and network administrators) who need to build and maintain trustworthy networked systems. * UNIX system programmers * practitioners who evaluate or initiate Internet connectivity This one-day seminar teaches practical strategies and techniques to combat the threat of intrusions and improve the security of operating systems connected to the Internet. Participants typically have at least one thing in common: the need, the desire, and the organizational mandate to provide trustworthy network services. They also typically share a lack of understanding of the issues related to network security and do not know how to protect their systems from the level of threat that exists on the Internet today. The seminar will cover fundamental security practices for UNIX system administration. Participants will learn about the latest information on security problems, defensive strategies, offensive strategies, network security, and establishing appropriate site security policy. After completing the seminar, participants will be able to establish and maintain a secure Internet site that allows the benefits of connectivity to the Internet while protecting the organization's data. Participants will also gain familiarity with tools that assist them in securing their systems. Seminar topics include: * latest information on security problems * UNIX system security * network security * site security policies REGISTRATION ------------ RETURN TO --------- SEI Events Software Engineering Institute Carnegie Mellon University Pittsburgh, PA 15213-3890 FAX: 412 / 268-7401 Internet: registration(a)sei.cmu.edu REGISTRATION INQUIRES --------------------- To inquire about registration, payment, or logistics, contact-- Registration Phone: 412 / 268-7388 Internet: registration(a)sei.cmu.edu COURSE INQUIRES --------------- To inquire about the course, contact-- Customer Relations Phone: 412 / 268-5800 Internet: customer-relations(a)sei.cmu.edu TERMS ----- The SEI will only accept registrations that are accompanied by payment or an acceptable authorization form. The SEI will refund cancellations received in writing up to three weeks before the course, minus a $100 administrative service charge or a 20% credit card transaction fee. Less than three weeks before the event, cancellations are subject to the entire registration fee, but you may apply the fee toward a future course. If you do not cancel and do not attend, you are still responsible for payment. Substitutions may be made at any time. After the early registration date, registrants must pay an additional $50 to attend. The SEI reserves the right to cancel courses that are insufficiently subscribed. If it is necessary to cancel, the SEI will notify registrants three weeks prior to the course and will refund registration fees. LODGING INFORMATION ------------------- Holiday Inn Select - University Center A block of room has been reserved at the Holiday Inn Select - University Center, 100 Lytton Avenue, Pittsburgh, PA 15213. The hotel will hold these room until three weeks prior to the course. Arrangements must be made directly with the hotel. 412 / 682-6200. To receive the group rate or the government rate, please mention the course name. 1996 Group Rate: $94, Government: $78 TRAVEL INFORMATION ------------------ The Airlines Transportation Company serves the hotel between 7:00 a.m. and 8:00 p.m. with departures every hour. The stop is located outside the USAir baggage claim area and the fare is $12.50 if the departure schedule and your arrival time are incompatible, taxi service is available 24 hours a day. Taxi fare from the airport to the Holiday Inn is approximately $35.00. COURSE LOCATION --------------- Software Engineering Institute Carnegie Mellon University Pittsburgh, Pennsylvania 15213-3890 ---Internet Security for System and Network Administrators Registration Form--- COURSE DATES (mark one) Internet Security for System and Network Administrators (mark one) _____February 15, 1996 Deadline for Early Registration: January 25, 1996 Add $50 to registrations sent after January 25, 1996 _____April 11, 1996 Deadline for Early Registration: March 21, 1996 Add $50 to registrations sent after March 21, 1996 _____July 11, 1996 Deadline for Early Registration: June 20, 1996 Add $50 to registrations sent after June 20, 1996 _____December 12, 1996 Deadline for Early Registration: November 21, 1996 Add $50 to registrations sent after November 21, 1996 FEES _____Academic $ 400 _____Government $ 400 _____Industry $ 500 _____International $1,000 _____After early registration deadline add $ 50 The registration fee includes course materials, continental breakfast, lunch and breaks. PAYMENT OPTIONS (mark one) ____Agency Authorization Form (e.g., DD 1556) ____Purchase Order ____Check (payable to SEI/CMU) ____Mastercard Expiration Date: ____Visa Expiration Date: ____American Express Expiration Date: Credit Card Number: PARTICIPANT INFORMATION Last name: First name, middle initial: (Mr., Mrs., Ms., Dr., other): First name as you would like it to appear on name tag: Title/organization.company/division: Street address: City, state, zip: Business phone: FAX number: Emergency number: Email address: Dietary/access requirements: Signature: Are you a U.S. citizen? yes/no: Identify country where citizenship is held if not the U.S.: How did you hear about the event? INTERNAL USE ONLY ________________________________________________________________________ Received Entered Check# PO# J/E# Sub# PL App Amount

1 0