- NANOG - lists.nanog.org

Operational Advisement...
by Jeff Barrows 16 Dec '99

16 Dec '99

Beginning on Friday, the 17th of December, we will begin adjusting the AS 1673 infrastructure such that AS 1673 routes will only be heard from behind AS 701. If you have any questions, you can contact us outside of this forum by sending e-mail to inter-eng(a)uu.net. Thank you. - jsb -- Jeff Barrows Director, Internetwork Engineering UUNET, an MCI-Worldcom Company

1 0

1q2000 in-addr walk - first notice
by Bill Manning 16 Dec '99

16 Dec '99

Hi, I appologize for duplicates. The next audit of the in-addr.arpa. tree will begin 01 january 2000. Since 1997, I've been walking the in-addr tree every quarter, looking for numbers of delegations, accurate delegations, and types and styles of error conditions. So... this is a heads up that you will be seeing zone transfers being generated by a couple of the collecter machines here. For those of you who utilize BINDs access controls, I'd appreciate your inclusion of the collector machines in allowed transfers. Queries will be from the following IP addresses: 128.9.160.57 and 198.32.4.13 If there are any questions or concerns, I'd be happy to talk about them. Past data has been presented at IEPG, Apricot and RIPE meetings. The expectation is that future data will be presented in the same and similar forums. Online summaries can be found at: www.isi.edu/~bmanning/in-addr-audit.html --bill

1 0

Re: Peering
by William B. Norton 16 Dec '99

16 Dec '99

>At 10:23 AM 12/15/99 +0200, Hank Nussbacher wrote: >At 19:30 14/12/99 -0500, David Diaz wrote: > >For peering, the most recent thorough analysis would be: >http://www.data.com/issue/991007/peering.html >They cover private and public peering. Too bad Data Communications is now >defunct and folded into some other network wannabbe rag. Robin did a nice job of raising some of the peering politics in this article. The positioning of the peering issues however as "the little guys vs. big guys" is counterproductive. It makes for good drama, but doesn't get us closer to a scalable well-connected well-engineered global Internet. There continue to be movements backstage to break the free peering vs. paid transit extremes into more of a continuum of options (like real cheap peering or settlement-based transit). This is where the parameters quantify "value" each ISP brings to the table. (But we won't go there lest I fetch my asbestos attire ;) ) >-Hank > >> >>Well at the last nanog there was a get together to exchange peering >>contract info. Bill Norton has compiled that into a list. That >>would get you a long way there for getting peering information. Right. The URL below includes the slides and an early draft of the paper that is basically the narrative that describes the Peering Process slides: http://www.nanog.org/mtg-9910/peering.html The paper describes (in rough terms) the peering coordinator mindset - how they think of and approach peering, the decision-making process, etc. This paper was initially written for some non-US ISP friends who were interested in establishing a US presence to use the US as a backhaul to another continent and obtain peering as an aside. If any ISP Peering Coordinator wants to get listed and obtain a copy of the Peering Contact Database, send me e-mail (wbn(a)umich.edu) with the relevant contact information (Contact Name & Title, Company Name, address, AS #, peering@<ispdomain>.net address for peering, phone numbers, etc.). I'll send back the Peering Contact Database & the latest version of the Peering Decision Tree document (v1.1 now). Note: These are Excel & Word documents today. >>The major backbones usually have peering@ setup. That along with >>the boardwatch should be a good start. Agreed - as a side note, I found it interesting that almost all ISP listed have a peering(a)ispdomain.net pseudo-standard in addition to their own e-mail address. Peering is both a systematic and personal interaction today. I'm also seeing a lot more AP ISPs coming in. Hope this helps - Bill

2 1

Re: 16 days and counting
by Dean Anderson 15 Dec '99

15 Dec '99

Most customers (us at least) were mailed a notification months ago. Actually, I found the equipment list quite useful for my own use. ;-) --Dean At 12:42 AM 12/15/1999 -0500, Jim Mercer supposedly said: > > >geez, nothing like cutting it to the wire. > >-- >[ Jim Mercer jim(a)reptiles.org +1 416 506-0654 ] >[ Reptilian Research -- Longer Life through Colder Blood ] >[ Don't be fooled by cheap Finnish imitations; BSD is the One True Code. ] > >----- Forwarded message from UUNET Canadian Support <support(a)uunet.ca> ----- > >Date: Tue, 14 Dec 1999 20:18:26 -0500 >From: UUNET Canadian Support <support(a)uunet.ca> >To: announce(a)uunet.ca >Subject: UUNET Year 2000 Customer Premise Equipment Information Notification > >Dear Valued Customer: > >UUNET Year 2000 Customer Premise Equipment Information Notification > >UUNET is currently engaged in a project to evaluate its readiness for Year >2000. The UUNET Year 2000 Program Office manages program activities that >encompass the customer global network and value-added services as well as >internal systems. > >UUNET is taking this opportunity to communicate with its customers >concerning their joint responsibilities for evaluating whether the >Customer Premise Equipment (CPE) used in conjunction with UUNET services >is Y2K compliant. This equipment includes routers, CSU/DSU's, firewalls, >servers and desktops. > >Although UUNET does not make any claim or warranty as to the Year 2000 >compliance of this third-party equipment, we are providing you with the >sources of vendor compliance information in the web so that you can >evaluate the CPE's Year 2000 status. We encourage you to contact the >manufacturers of your CPE for information on their Year 2000 programs and >the Year 2000 readiness of this equipment. > >The table on the next pages shows the type of equipment, the manufacturer >and the URL through which you may be able to obtain more information. This >list includes CPE that UUNET currently ships and supports. You may own >other equipment that was not supplied by UUNET or that is not currently >shipped and supported by UUNET. > >We hope that you will use this information to examine your CPE, assess its >Year 2000 readiness, and upgrade any equipment that may require such >action. Should you have questions concerning CPE, please call UUNET at >1-888 886 3865. > >If you have questions concerning UUNET's Year 2000 Program, we hope you >will read our Year 2000 information at : >http://www.wcom.com/about_the_company/year_2000_compliance/uunet_y2k/index.…. >Direct inquiries to the Year 2000 Program Office can be made to >year2000(a)uu.net. > >The information provided by UUNET in this letter constitutes a year 2000 >readiness disclosure under the Year 2000 Information and Readiness >Disclosure Act (October 19, 1998, 105 U.S. Public Law 271, 112 Stat. >2386). This Year 2000 readiness disclosure includes a republication of >Year 2000 statements originally made by the third party manufacturers of >the equipment listed below. UUNET is not the source of these republished >statements, which have been supplied by another entity, which are based on >information UUNET has not verified. Accordingly, UUNET is not responsible >for the republished information's accuracy, completeness, or currency. > >"UUNET" as used herein and the references to various networks, services, >and systems, refers only to UUNET and its networks, services, and systems, >and should not be construed as applying to MCI WORLDCOM Inc. ("MCI >WorldCom") in general or to any other WorldCom or MCI companies or their >networks, services, or systems. > >We look forward to servicing you well into the new millenium! > >Sincerely, >Andrew Ordin >Y2K Project Coordinator > >Category Manufacturer and URL to Obtain Vendor's > Model Number Recommendations > >Router Cisco 2501, 2514 www.cisco.com > > Cisco 2524 www.cisco.com > > Cisco 2610 www.cisco.com > > Cisco 3640 www.cisco.com > > Cisco 4500,4700 www.cisco.com > > Cisco 7200 series www.cisco.com > > OpenROUTE GTX1000 www.openroute.com > > Xedia AP 45 www.xedia.com > > Xedia AP ATM www.xedia.com > > Xedia AP T1/E1 www.xedia.com > > Ascend Pipeline 130 www.ascend.com > > Intel Express 8100 www.intel.com > > >CSU/DSU Kentrox D-SERV 56k and T1 > (78220, 78282 and 78222) www.adc.com > > Kentrox DataSmart D-SERV www.adc.com > > Verilink HDM2182 in the > AS2000 CSU/DSU www.verilink.com > > Larscom Access T45 www.larscom.com > > Digital Link DL3100 www.dl.com > > Cisco POET serial port > adaptor (1 &2 port) www.cisco.com > > >Firewall >Software Checkpoint Firewall-1 www.checkpoint.com > > Checkpoint SecuRemote www.checkpoint.com > > Axent Raptor Firewall www.axent.com > > Axent Raptor Mobile www.axent.com > > Gauntlet Firewall www.nai.com > > Ascend SecureConnect Firewall (SCF) > 3.0 (in Ascend Pipeline products) > www.ascend.com > > >Firewall >Platforms Sun Ultra or Sparc www.sun.com > > Patriot Black Box - > Pentium II PC www.patriot.com > > Ascend Pipeline 85, Pipeline 75 www.ascend.com > > >Firewall >Operating >Systems Sun Solaris www.sun.com > > Microsoft NT www.microsoft.com > > BSD www.bsdi.com > > >Dial >Access Ascend Pipeline 85, Pipeline 75 www.ascend.com > > Adtran ISU128 www.adtran.com > > 3COM Impact IQ Terminal Adaptor www.3com.com > > 3COM 56K Voice Fax modem Pro www.3com.com > > Cisco 1005 www.cisco.com > > Cisco 804 www.cisco.com > > Cisco 1604 (ISDN/T1) www.cisco.com > > Bay Instant Internet 100 > www.nortelnetworks.com > > Hayes Accura 56K external > data fax modem www.hayes.com > > US Robotics FX-BRI-U www.3com.com > > Whistle IJ100, IJ140 www.whistle.com > > >-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= >UUNET Canadian Technical Support / Support Technique Canadien >support(a)uunet.ca / soutien(a)uunet.ca >Phone: (888) 886 3865 fax: (416) 368-5473 >----- End forwarded message ----- > > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Plain Aviation, Inc dean(a)av8.com LAN/WAN/UNIX/NT/TCPIP http://www.av8.com ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

3 2

Y2K status list - apology/mail issue
by Sean Donelan 15 Dec '99

15 Dec '99

I found out Critical Path's mail system silently swallows e-mail with too many addresses. I don't know if this was spam prevention, or just a system limitation. In any case, it swallowed my messages for the last two weeks to the ISPs who asked to participate in the Y2K new year's rollover status list. I did get your mail, and I am now cutting and pasting your addresses to a different system. I will be sending individual messages to everyone today. If you don't receive a message by Friday December 17, do not hesitate to contact me. I guess its a good thing I tested it before the end of the year.

1 0

16 days and counting
by Jim Mercer 15 Dec '99

15 Dec '99

geez, nothing like cutting it to the wire. -- [ Jim Mercer jim(a)reptiles.org +1 416 506-0654 ] [ Reptilian Research -- Longer Life through Colder Blood ] [ Don't be fooled by cheap Finnish imitations; BSD is the One True Code. ] ----- Forwarded message from UUNET Canadian Support <support(a)uunet.ca> ----- Date: Tue, 14 Dec 1999 20:18:26 -0500 From: UUNET Canadian Support <support(a)uunet.ca> To: announce(a)uunet.ca Subject: UUNET Year 2000 Customer Premise Equipment Information Notification Dear Valued Customer: UUNET Year 2000 Customer Premise Equipment Information Notification UUNET is currently engaged in a project to evaluate its readiness for Year 2000. The UUNET Year 2000 Program Office manages program activities that encompass the customer global network and value-added services as well as internal systems. UUNET is taking this opportunity to communicate with its customers concerning their joint responsibilities for evaluating whether the Customer Premise Equipment (CPE) used in conjunction with UUNET services is Y2K compliant. This equipment includes routers, CSU/DSU's, firewalls, servers and desktops. Although UUNET does not make any claim or warranty as to the Year 2000 compliance of this third-party equipment, we are providing you with the sources of vendor compliance information in the web so that you can evaluate the CPE's Year 2000 status. We encourage you to contact the manufacturers of your CPE for information on their Year 2000 programs and the Year 2000 readiness of this equipment. The table on the next pages shows the type of equipment, the manufacturer and the URL through which you may be able to obtain more information. This list includes CPE that UUNET currently ships and supports. You may own other equipment that was not supplied by UUNET or that is not currently shipped and supported by UUNET. We hope that you will use this information to examine your CPE, assess its Year 2000 readiness, and upgrade any equipment that may require such action. Should you have questions concerning CPE, please call UUNET at 1-888 886 3865. If you have questions concerning UUNET's Year 2000 Program, we hope you will read our Year 2000 information at : http://www.wcom.com/about_the_company/year_2000_compliance/uunet_y2k/index.…. Direct inquiries to the Year 2000 Program Office can be made to year2000(a)uu.net. The information provided by UUNET in this letter constitutes a year 2000 readiness disclosure under the Year 2000 Information and Readiness Disclosure Act (October 19, 1998, 105 U.S. Public Law 271, 112 Stat. 2386). This Year 2000 readiness disclosure includes a republication of Year 2000 statements originally made by the third party manufacturers of the equipment listed below. UUNET is not the source of these republished statements, which have been supplied by another entity, which are based on information UUNET has not verified. Accordingly, UUNET is not responsible for the republished information's accuracy, completeness, or currency. "UUNET" as used herein and the references to various networks, services, and systems, refers only to UUNET and its networks, services, and systems, and should not be construed as applying to MCI WORLDCOM Inc. ("MCI WorldCom") in general or to any other WorldCom or MCI companies or their networks, services, or systems. We look forward to servicing you well into the new millenium! Sincerely, Andrew Ordin Y2K Project Coordinator Category Manufacturer and URL to Obtain Vendor's Model Number Recommendations Router Cisco 2501, 2514 www.cisco.com Cisco 2524 www.cisco.com Cisco 2610 www.cisco.com Cisco 3640 www.cisco.com Cisco 4500,4700 www.cisco.com Cisco 7200 series www.cisco.com OpenROUTE GTX1000 www.openroute.com Xedia AP 45 www.xedia.com Xedia AP ATM www.xedia.com Xedia AP T1/E1 www.xedia.com Ascend Pipeline 130 www.ascend.com Intel Express 8100 www.intel.com CSU/DSU Kentrox D-SERV 56k and T1 (78220, 78282 and 78222) www.adc.com Kentrox DataSmart D-SERV www.adc.com Verilink HDM2182 in the AS2000 CSU/DSU www.verilink.com Larscom Access T45 www.larscom.com Digital Link DL3100 www.dl.com Cisco POET serial port adaptor (1 &2 port) www.cisco.com Firewall Software Checkpoint Firewall-1 www.checkpoint.com Checkpoint SecuRemote www.checkpoint.com Axent Raptor Firewall www.axent.com Axent Raptor Mobile www.axent.com Gauntlet Firewall www.nai.com Ascend SecureConnect Firewall (SCF) 3.0 (in Ascend Pipeline products) www.ascend.com Firewall Platforms Sun Ultra or Sparc www.sun.com Patriot Black Box - Pentium II PC www.patriot.com Ascend Pipeline 85, Pipeline 75 www.ascend.com Firewall Operating Systems Sun Solaris www.sun.com Microsoft NT www.microsoft.com BSD www.bsdi.com Dial Access Ascend Pipeline 85, Pipeline 75 www.ascend.com Adtran ISU128 www.adtran.com 3COM Impact IQ Terminal Adaptor www.3com.com 3COM 56K Voice Fax modem Pro www.3com.com Cisco 1005 www.cisco.com Cisco 804 www.cisco.com Cisco 1604 (ISDN/T1) www.cisco.com Bay Instant Internet 100 www.nortelnetworks.com Hayes Accura 56K external data fax modem www.hayes.com US Robotics FX-BRI-U www.3com.com Whistle IJ100, IJ140 www.whistle.com -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= UUNET Canadian Technical Support / Support Technique Canadien support(a)uunet.ca / soutien(a)uunet.ca Phone: (888) 886 3865 fax: (416) 368-5473 ----- End forwarded message -----

1 0

Whois
by David Lesher 15 Dec '99

15 Dec '99

So where do we look up handles nowadaze? I tried a couple of obvious ways to no avail... -- A host is a host from coast to coast.................wb8foz(a)nrk.com & no one will talk to a host that's close........[v].(301) 56-LINUX Unless the host (that isn't close).........................pob 1433 is busy, hung or dead....................................20915-1433

2 2

Peering
by Alba, Victor 15 Dec '99

15 Dec '99

I hope this question belong to this list. I was wondering if there is a place where I could find peering information (public) among the different providers as well as the general description of each one of the major providers IP backbones (UUNet, C&W, Sprint, GTE, etc.) -Victor

3 2

more NSI whois changes
by Patrick Evans 14 Dec '99

14 Dec '99

I've not noticed any outcry over the latest set of changes to NSI's whois server yet, but some people might find these notes from our man at the NIC useful...the web interface, which doesn't currently make any mention of the changes (or didn't when I looked earlier), also needs careful use now... "The new Whois server requires additional qualifiers now be used: This affects both Whois on the NSI web site and Whois from domreg>. To ask WHOIS to search a certain field in the database, use the following three keywords (shown with their minimum abbreviation in all BLUECAPS): Examples: HOst [HO my.dotcomblues.com] or [HO 208.213.203.161] or [HO DCBLUES-HST] HAndle or '!' [!cxk9] or [HA cxk9] or [HA KC86-ORG] NAme or leading '.' [.kim, charles] or [NA Charles Kim] Mailbox or contains '@' ckim(a)netsol.com (no qualifier needed) (ho, hos, host, ha, han, hand, handle, na, nam, name in lower case work as well) Full details can be found by clicking 'Need Help? Click here' from the Whois web interface." -- Patrick Evans - Sysadmin, bran addict and couch potato pre at pre dot org www.pre.org/pre

1 0

Re: BGP Blowup?
by Tim Wolfe 14 Dec '99

14 Dec '99

So far the data is as follows: 1. My BGP session to Sprint (1239) exceeded 75000 routes at approx 5:39pm PST 2. Telestra seems to have had a similar surge from Uknown provider (or possibly on their own network) 3. Another individual reported that their GTEI (7176) session had a similar surge. 4. Yet another individual reported that their Digex session had a surge as well. I guess I'm confused. While 4 similar surges in table size at 3 distinct locations is not by any means conclusive evidence that the global table was experiencing wackiness, it certainly points a finger in the that direction. What perhaps bothers me more than the surge itself is that I have gotten very few (read 1) responses to indicate that there were NOT a problem similar to what I've reported. I get the feeling that many people are not tracking prefix counts so I'm am very nervous about future occurences. At what point does an event like this become a problem that gets noticed? Does it take a full meltdown of BGP speakers in a large providers network before this is worth looking at? I would think that a sudden random addition of 10,000 routes would be of concern to people who claim to be so worried about the size of the world's routing tables. Or is it only a concern if actually affects your network? I'm not attacking anyone, just concerned over the apparent lack of concern... It is interesting that all of the individuals that had direct UUNet sessions didn't see any of the surge on those sessions. Maybe they learned from the MCI experience awhile back? -- Tim -------------------------------------------------- * Timothy M. Wolfe, Chief Network Engineer * * ClipperNet Corporation / It's a wireless world * * tim(a)clipper.net 800.338.2629 x 402 * * Sufficient for today = Inadequate for tomorrow * --------------------------------------------------

2 1