- Test - lists.nanog.org

Re: Advanced topic seminar -- ride from airport?
by Vince Fuller 15 Jan '92

15 Jan '92

Is there anyone else attending the Advanced Topics Seminar on the 23rd/24th who will be arriving at the Detroit airport at around 5:30pm? If so, a ride from the airport (or even splitting cab fare) would be appreciated. (I'm willing to help pay for the mileage to the University). Thanks, Evan I'm looking to make similar arrangements if anyone is arriving in Detroit at around 7:30PM on Wednesday the 22nd... Thanks, --Vince

2 1

Whoops: Advanced topic seminar -- ride from the airport
by evan＠is.rice.edu 15 Jan '92

15 Jan '92

Whoops, I just realized that my previous posting regarding a ride from the Detroit airport to Ann Arbor didn't specify the date. I'm looking for a ride on the 22nd, at about 5:30 pm. -- Evan

1 0

Advanced topic seminar -- ride from airport?
by evan＠is.rice.edu 14 Jan '92

14 Jan '92

Hi, Is there anyone else attending the Advanced Topics Seminar on the 23rd/24th who will be arriving at the Detroit airport at around 5:30pm? If so, a ride from the airport (or even splitting cab fare) would be appreciated. (I'm willing to help pay for the mileage to the University). Thanks, -- Evan

1 0

Additions to the NSFNET policy-based routing database
by Steven K. Widmayer 14 Jan '92

14 Jan '92

database: T1 Network: Net # Net Name Primary Secondary Location -------- ----------- ------- --------- -------- 130.226 DENET-226 1238 701 Danish Network for Research and Education, UNI-C, DK-2800 Lyngby, DENMARK 137.108 OPEN-UNI 274 60 Open University, Walton Hall, Milton Keynes MK7 6AA, UNITED KINGDOM 141.55 FH-MITTWEIDA 174 Ingenieurhochschule Mittweida, Rechenzentrum, Technikumplatz 17, D-O-9250 Mittweida, GERMANY 147.29 DC-DK 1238 701 Datacentralen, Retortvej 8, DK-1790 Kbh. V., DENMARK 147.143 BANGOR 274 60 University College of North Wales, Sackville Road Bangor Gwynedd LL57 1LD, UNITED KINGDOM 150.254 POZPOLIP 1238 701 Technical University of Poznan, 60-965 POZNAN, POLAND 157.24 LUT 1238 701 Lappeenranta University of Technology, Lappeenranta University of Technology, Computing Centre, Box 20, SF-53851 LAPPEENRANTA, FINLAND 157.98 NIEHS2 86 279 National Institute of Environmental Health Sciences, 111 Alexander Drive, Research Triangle Park, NC 27709 192.67.251 DAASNET 184 164 Defense Automatic Addressing Systems Office, Gentile Station - Bldg 1, 1080 Franklin Street, Dayton, Ohio 45444-5320 192.77.174 PSINET-C-174 174 PSI, Inc., 165 Jordan Road, Troy, NY, 12180 192.77.175 PSINET-C-175 174 Performance Systems International, 165 Jordan Road, Troy, NY 12180 192.129.62 WSMR-NET9 164 184 US Army Atmospheric Sciences Lab, SLCAS-D, WSMR, NM 88002 192.129.64 RUCKER-NET2 184 164 US Army Information System Command, Ft. Rucker (USAISC-FR), Cdr, USAISC-FR, ASQNB-ZQ, Ft. Rucker, AL 36362-5298 192.129.69 CSE-AIN 184 164 Center for Software Engineering, Army Interoperability Network Branch, US Army-CECOM, AMSEL-RD-SE-AIN-E, FT. Monmouth, NJ 07703 192.131.102 ROWLAND-NET 560 281 Rowland Institute for Science, 100 Cambridge Parkway, Cambridge, MA 02142 192.131.103 CHPC-NET 560 281 Center for High-Performance Computing, 293 Boston Post Road West, Marlboro, MA 01752 192.131.106 CHPC-NET2 560 281 Center for High-Performance Computing, 293 Boston Post Road West, Marlboro, MA 01752 192.131.155 LU 1206 204 Lincoln University, Lincoln, PA 19352 192.132.35 OBSN 293 291 CNPz Observatorio Nacional, Rua General Jose Cristino, 77 - Rio de Janeiro, CEP 20921, BRAZIL 192.132.57 TELEBASE 1206 204 Telebase Systems, 435 Devon Park Drive, Suite 600, Wayne, PA 19087 192.132.246 MCI-SOUTHFLD 750 756 MCI Telecommunications, Inc., 26913 Northwestern Highway, Suite 300, Southfield, MI 48034 Total NSFNET T1 announced networks: 4354 The following T1 gates have also been added: Router Internet Address: 192.70.246.9 Router Internet Name: cern-spare.easi.net Router AS Number: 697 (EASINet-AS2) NSS number colocated with router: 10 Router type: IBM PC/RT T3 Network: Network IP: 192.131.102 Network Name: ROWLAND-NET Location: Rowland Institute for Science, 100 Cambridge Parkway, Cambridge, MA 02142 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network Network IP: 192.131.103 Network Name: CHPC-NET Location: Center for High-Performance Computing, 293 Boston Post Road West, Marlboro, MA 01752 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network Network IP: 192.131.106 Network Name: CHPC-NET2 Location: Center for High-Performance Computing, 293 Boston Post Road West, Marlboro, MA 01752 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network Network IP: 192.131.155 Network Name: LU Location: Lincoln University, Lincoln, PA 19352 1:1206 PSCNET Network IP: 192.132.57 Network Name: TELEBASE Location: Telebase Systems, 435 Devon Park Drive, Suite 600, Wayne, PA 19087 1:1206 PSCNET Network IP: 192.132.246 Network Name: MCI-SOUTHFLD Location: MCI Telecommunications, Inc., 26913 Northwestern Highway, Suite 300, Southfield, MI 48034 1:1663 MCI, Southfield, MI Total NSFNET T3 announced networks: 968 The following T3 gates have also been added: AS Number: 174 AS Notes: NYSERNET Regional Network / PSI AS Country Code: US BkBn: 690 NSS: 140.222.133 - it-enss Cornell, Ithaca, NY Gate: 192.35.82.1 - lan.cornell.site.psi.net Cornell University - Ithaca, NY AS Number: 1663 AS Notes: MCI, Southfield, MI AS Country Code: US BkBn: 690 NSS: 140.222.158 - MCI Southfield MCI, Southfield, MI Gate: 192.132.246.2 - mci-gw.mci.com MCI, Southfield, MI The configuration reports, map information sheets, and configuration files which reflect these changes are available for anonymous ftp on nis.nsf.net as usual. nsfsites - configuration reports latest report for: - NSFNET T1 has the file extension .now - NSFNET T3 has the file extension 3.now nsfconfg - configuration files for the routing software for each NSS latest report for: - NSFNET T1 has the file format config.nss# - NSFNET T3 has the file extension .t3p Please send all requests for configuration changes to nsfnet-admin(a)merit.edu using the NSFNET configuration forms. The forms are available on-line from the nis.nsf.net machine. Use ftp and the anonymous login to get on the machine. Do a "cd nsfsites" and grab the files TEMPLATE.NET, TEMPLATE.GATE, and TEMPLATE.AS. --Steve Widmayer Merit/NSFNET

1 0

CERFnet Weekly Report for the week of Monday, January 6, 1992.
by Donna Bigley 13 Jan '92

13 Jan '92

############################################################################### This is the CERFnet weekly activity report for the period of Monday, January 6th through Sunday, January 12th, 1992. This report is also available through anonymous FTP from NIC.CERF.NET [192.102.249.3] in the cerfnet/cerfnet_stats subdirectory. The filename is: 12-january-92.txt All times are in Pacific Standard Time, and in the 24-hour format. Please direct any questions or comments to: donnab(a)cerf.net or help(a)cerf.net ****************************************************************************** NETWORK OUTAGES: SITE: SERI/KOREA SITES AFFECTED: SERI/KOREA TIME STARTED: TUE. 1-7-92 03:16 TIME ENDED: TUE. 1-7-92 03:32 TIME ELAPSED: 16 min REASON: Unknown SITE: SWRL (CSUCO) SITES AFFECTED: SWRL (CSUCO) TIME STARTED: TUE. 1-7-91 05:09 TIME ENDED: TUE. 1-7-91 06:05 TIME STARTED: TUE. 1-7-91 06:09 TIME ENDED: TUE. 1-7-91 08:00 TIME ELAPSED: 2 hours 47 min REASON: Unscheduled Site Maintenance SITE: UCI SITES AFFECTED: UCI, UCI Dial n' CERF, CSUCO, HUGHES, EMULEX, UNOCAL, MTI, SPARTA, FULLERTON, and CMD. TIME STARTED: TUE. 1-7-91 20:47 TIME ENDED: TUE. 1-7-91 20:50 TIME ELAPSED: 3 min REASON: Power Outage SITE: SPARTA SITES AFFECTED: SPARTA TIME STARTED: TUE. 1-7-92 20:48 TIME ENDED: WED. 1-8-92 07:14 TIME ELAPSED: 10 hours 26 min REASON: Power Outage SITE: UCI-UCLA T1 SITES AFFECTED: UCI-UCLA T1 TIME STARTED: TUE. 1-7-91 20:48 TIME ENDED: WED. 1-8-91 08:44 TIME ELAPSED: 11 hours 56 min REASON: Link Failure SITE: CISCO SITES AFFECTED: CISCO TIME STARTED: THU. 1-9-92 08:56 TIME ENDED: THU. 1-9-92 09:16 TIME ELAPSED: 20 min REASON: Site Activity SITE: UCI SITES AFFECTED: UCI, UCI Dial n' CERF, CSUCO, HUGHES, EMULEX, UNOCAL, MTI, SPARTA, FULLERTON, and CMD. TIME STARTED: THU. 1-9-92 09:42 TIME ENDED: THU. 1-9-92 09:52 TIME ELAPSED: 10 min REASON: CERFnet Scheduled Maintenance SITE: QUALCOMM SITES AFFECTED: QUALCOMM TIME STARTED: THU. 1-9-92 21:06:56 TIME ENDED: THU. 1-9-92 21:08:03 TIME ELAPSED: 1 min 7 sec. REASON: Site Scheduled Maintenance SITE: GA SITES AFFECTED: GA TIME STARTED: SUN. 1-12-92 20:36 TIME ENDED: SUN. 1-12-92 21:34 TIME ELAPSED: 58 min REASON: Unknown ------------------------------------------------------------------------ CERFNET TRAFFIC CAPACITY USAGE AT EACH CIRCUIT LINK LINK SPEED CAPACITY PEAK HOUR (PDT) SDSC/CALTECH 1.544 mbps 06.3% 09:00 SDSC/UCI 1.544 mbps 04.6% 06:00 SDSC/UCLA 1.544 mbps 06.2% 15:00 SDSC/UCOP 1.544 mbps 03.1% 15:00 SDSC/UCR 1.544 mbps 00.6% 21:00 UCI/UCLA 1.544 mbps 03.5% 06:00 UCLA/UCSB 512 kbps 06.1% 16:00 SDSC/AGI 1.544 mbps 00.2% 15:00 SDSC/BIOSYM 1.544 kbps 00.1% 14:00 SDSC/GA 1.544 mbps 01.3% 22:00 SDSC/GD 1.544 mbps 01.3% 23:00 SDSC/SAIC 1.544 mbps 01.7% 14:00 SDSC/SCAQMD 1.544 mbps 00.02% 13:00 SDSC/SDSU 1.544 mbps 00.9% 10:00 UCI/CSU CO(SWRL) 1.544 mbps 01.6% 15:00 UCOP/APPLE 1.544 mbps 00.8% 09:00 UCOP/CISCO 1.544 mbps 00.1% 06:00 UCR/LLUMC 1.544 mbps 00.04% 15:00 CALTECH/CADAM 56 kbps 00.6% 05:00 CALTECH/CLAREMONT 56 kbps 14.4% 06:00 CALTECH/DISNEY 56 kbps 10.4% 07:00 CALTECH/OXY 56 kbps 04.0% 21:00 SDSC/AJS 56 kbps 02.1% 14:00 SDSC/KOREA 56 kbps 03.6% 20:00 SDSC/QUALCOMM 56 kbps 26.9% 10:00 SDSC/SCIH 56 kbps 03.8% 09:00 SDSC/USD 56 kbps 05.4% 15:00 SDSC/USIU 56 kbps 03.7% 09:00 SDSC/XEROX 56 kbps 00.8% 06:00 UCI/CMD 56 kbps 01.8% 06:00 UCI/EMULEX 56 kbps 07.8% 13:00 UCI/FULLERTON 56 kbps 02.7% 07:00 UCI/HUGHES 56 kbps 04.4% 16:00 UCI/MTI 56 kbps 05.1% 06:00 UCI/SPARTA 56 kbps 02.9% 10:00 UCI/UNOCAL 56 kbps 04.4% 09:00 UCLA/ISX 56 kbps 01.1% 15:00 UCLA/PEPPERDINE 56 kbps 01.0% 06:00 UCLA/QUOTRON 56 kbps 07.3% 06:00 UCLA/SMC 56 kbps 00.9% 16:00 UCOP/FARALLON 56 kbps 03.4% 06:00 UCOP/INTEL 56 kbps 11.2% 13:00 UCOP/LSIL 56 kbps 02.1% 06:00 UCOP/NETLABS 56 kbps 15.8% 19:00 ------------------------------------------------------------------------------ SITE CISCO BOX UPTIME SINCE LAST REBOOT (as of 00:15 PST on Jan. 13, 1992): CERFnet BACKBONE CALTECH [131.215.139.253] Up: 248 days 22 hours 43 minutes SDSC Drzog [132.249.16.13] Up: 29 days 08 hours 25 minutes SDSC Hang10 [132.249.16.15] Up: 25 days 07 hours 11 minutes UCI [128.200.1.101] Up: 03 days 16 hours 07 minutes [CERFnet Scheduled Maintenance] UCLA [128.97.130.10] Up: 16 days 00 hours 45 minutes UCOP [134.24.52.112] Up: 51 days 08 hours 41 minutes UCR [134.24.108.105] Up: 58 days 12 hours 36 minutes CERF 1544 AGI [134.24.202.110] Up: 16 days 17 hours 54 minutes APPLE [134.24.70.200] Up: 77 days 06 hours 15 minutes BIOSYM [134.24.57.200] Up: 35 days 09 hours 14 minutes CISCO Systems [134.24.54.200] Up: 40 days 14 hours 09 minutes CSUCO/SWRL [130.150.102.200] Up: 26 days 18 hours 15 minutes GA [134.24.221.200] Up: 86 days 16 hours 34 minutes GD [134.24.60.200] Up: 11 days 04 hours 14 minutes LLUMC [134.24.208.200] Up: 54 days 12 hours 22 minutes SAIC [134.24.53.208] Up: 08 days 08 hours 34 minutes UCSB [134.24.107.107] Up: 54 days 07 hours 38 minutes CERF 56 AJS [134.24.225.101] Up: 55 days 15 hours 50 minutes CADAM [134.24.229.200] Up: 09 days 13 hours 06 minutes CLAREMONT [134.24.206.109] Up: 14 days 06 hours 49 minutes CMD [134.24.218.200] Up: 05 days 03 hours 28 minutes [Power Outage] DATAPRODUCTS [134.24.211.104] Up: 159 days 10 hours 48 minutes DISNEY [134.24.207.211] Up: 09 days 10 hours 20 minutes EMULEX [134.24.209.212] Up: 29 days 15 hours 48 minutes FARALLON [134.24.56.200] Up: 38 days 11 hours 43 minutes FULLERTON [134.24.214.217] Up: 27 days 15 hours 33 minutes HUGHES [134.24.204.200] Up: 59 days 07 hours 21 minutes INTEL [134.24.55.200] Up: 15 days 03 hours 19 minutes LSIL [134.24.72.200] Up: 15 days 14 hours 14 minutes MTI [134.24.216.100] Up: 09 days 13 hours 39 minutes NETLABS [134.24.71.200] Up: 37 days 15 hours 07 minutes OXY [134.24.205.108] Up: 139 days 12 hours 51 minutes PEPPERDINE [134.24.203.218] Up: 08 days 13 hours 24 minutes QUALCOMM [134.24.200.201] Up: 33 days 18 hours 19 minutes QUOTRON [134.24.230.202] Up: 48 days 13 hours 44 minutes SANTA MONICA [134.24.210.219] Up: 03 days 01 hours 22 minutes [Power Outage] SCAQMD [134.24.234.200] Up: 24 days 14 hours 27 minutes SCI-HOR [134.24.109.205] Up: 45 days 11 hours 15 minutes SDSU [192.77.100.101] Up: 34 days 16 hours 31 minutes SERI/KOREA [134.24.223.200] Up: 111 days 00 hours 00 minutes SPARTA [134.24.215.200] Up: 04 days 17 hours 01 minutes [Power Outage] UNOCAL [134.24.217.200] Up: 21 days 22 hours 45 minutes USD [134.24.201.106] Up: 98 days 10 hours 55 minutes USIU [134.24.222.215] Up: 190 days 17 hours 07 minutes XEROX [134.24.51.207] Up: 74 days 23 hours 22 minutes DIAL n' CERF DNC-SDSC [134.24.1.2] Up: 28 days 14 hours 57 minutes DNC-UCI [134.24.2.2] Up: 05 days 03 hours 24 minutes [Power Outage] DNC-UCLA [134.24.3.2] Up: 16 days 00 hours 46 minutes DNC-CALTECH [134.24.4.2] Up: 74 days 21 hours 02 minutes DNC-UCOP [134.24.5.2] Up: 135 days 15 hours 10 minutes

1 0

Planning the new institutional backbones and interconnections
by Phil Urquiza 11 Jan '92

11 Jan '92

Subject: ------- Planning the new Institutional backbones and their inter-connectivities. Objective: --------- To determine the network backbones requirements for NREN and institutional applications. -------- Premises: -------- All present telecommunication and Local Area networks are not directly compatible with the new fiber based networks that will soon be activated, worldwide. Today's Video, LANS, WANS, POTS, Routers, Packets & Frame relays, etc, will all be carried transparently on the new fiber backbones. They will coexist for a while until all their functions are completely absorbed by Sonet, ATM, B-ISDN and F-CATV. The NREN and institutional backbones can all be build, today, using readily available Sonet fiber equipment and systems, from multiple sources and with full standards compatibility. We do not need to wait for the common carriers to build our applications, we can buy the same compatible equipment from the same sources that they do. The fibers are already installed across the country, between most of the metro area telephone central offices, on the outside plant subscriber loop carriers, on many CATV trunk distributions, and to many of our institutions. We need to lease the backbone fibers from the common carriers, now, before they deploy their Sonet and B-ISDN systems. If we wait then we will only be able to affoard leasing bandwidth from them. The NREN and other backbones need the fiber capabilities more than a conservative bandwidth increment. FDDI-2, Sonet(SMDS, ATM, FDDI-3, MAN, B-ISDN) and F-CATV backbones, they represent compatible technology, at different stages. All these LAN, MAN, WAN, RAN, NAN and GAN fiber based new implementations will be able to provide the same, or compatible, data and multimedia services, on the same telecomm media: single mode fiber media at 1300 and 1500 nm wavelengths. We could all learn how to apply the new fiber technology, from the NREN network backbone deployment and their applications. A full NREN backbone deployment, as described below, could be completed within a year. At that time many of today's backbones, Internet, Milnet, Fednet, Videonet, could be carried within it, and still have most of the large bandwidth left to develop the intended NREN applications. Recommendation: -------------- What should the NREN backbone fast evolution be like ?. Phase I, start national NREN backbone ----- Single mode fiber leased from common carriers, four fibers per node. Fiber shall terminate directly at NREN location nodes Install ED-Optical fiber amplifiers at common carrier locations. OC-48 Sonet transport fiber equipment installed at all NREN locations. All NREN equipment should be owned by NREN and have a distributed management organization, among non-commercial NREN regionals. Phase II, start state NREN backbones ----- Expand fiber NREN backbone between major cities, same as Phase I Phase III, connect regional members to NREN backbones ----- Add, common carrier provided, Sonet access service to NREN backbones nodes, for regional networks access. Phase IV, upgrade NREN backbone. ----- Upgrade existing fibers for dual wavelength multiplex, 1300/1500 nm. Upgrade for higer capacity Sonet transport, OC-96 through OC-256. Phase V, upgrade to ATM and B-ISDN ----- Install small B-ISDN switches with ATM at major NREN nodes. Install Local Sonet and Video distribution fiber, to the Desk/Station, using bidirectional B-ISDN fibers. Phase V, complete backbone for full research use ----- Upgrade inter node fiber for multiple Wavelength Multiplex Add common carrier provided B-ISDN access service, for regionals Phase VI, building the applications for the Future ----- This is the only phase that we can not buy, the research and development, from other vendors. Cost recovery: ------------- All cost could be recovered, if NREN wants, by selling the NREN back to the common carriers, at the end of the research exercise. NREN could even get some profit, by getting a free lease back for some years. ---- The end of the beginning.

1 0

Advanced Topics Seminar - Revised Agenda
by smr 11 Jan '92

11 Jan '92

Here is a revised agenda for the Advanced Topics Seminar, again to be held Jan 23 and 24th in Ann Arbor, MI. As a reminder, if you do plan on attending the seminar please rsvp to seminar(a)merit.edu. Sheri Repucci Merit/Internet Engineering AGENDA ==================================================================== Thursday Jan 23rd ----------------- 9:00-9:15 Opening Remarks 9:15-10:00 Gigabit Testbeds by Dick Binder of CNRI 10:00-10:45 High Speed Switching by Northern Telecommunications Inc/Bell Northern Research 10:45-11:00 Short break 11:00-12:00 Backbone Routing by Jessica Yu of Merit 12:00-1:30 Lunch 1:30-2:15 SMDS & SMDS Network Management by Dave Piscatello of Bellcore 2:15-3:00 SMDS WAN Implementation Plan for ESnet by Tony Hain of ESnet 3:00-3:15 Short break 3:15-3:45 T3 Summary and Overview by Mark Knopper of Merit 3:45-4:30 Future T3 Enhancements on Performance by Mathi Packiam of IBM 4:30-5:00 Open discussion on T3 status Friday Jan 24th --------------- 9:00-9:45 BGP3 by Dennis Ferguson of CA*net 9:45-10:45 NREN Engineering by Peter Ford of Los Alamos National Laboratory 10:45-11:00 short break 11:00-11:30 OSI by Sue Hares of Merit 11:30-1:00 Lunch 1:00-2:30 Informal and Open Discussion with Regional Techs 2:30-5:00 tours, discussions and meetings

1 0

Additions to the NSFNET policy-based routing database
by Belinda Sue Blair 10 Jan '92

10 Jan '92

The following networks have been added to the NSFNET policy-based routing database: T1 Network: Net # Net Name Primary Secondary Location -------- ----------- ------- --------- -------- 192.74.218 LOGANCOLTS 291 293 Logan High School, 1800 H St. Union City CA 94587, USA 156.63 OHIO 266 267 Ohio Data Network, 65 East State Street, Suite 810, Columbus, OH 43215, USA 155.246 STEVENS 97 Stevens Institute of Technology, Castle Point on the Hudson, Hoboken, NJ 07030, USA 192.135.67 TEA 280 114 Texas Education Agency, 1701 North Congress Avenue, Austin, TX 78701-1494, USA 192.133.7 TAINET 93 Tuebner & Associates, Inc., 324 South Husband, Stillwater, OK 74074, USA 155.92 MSOE 267 266 Milwaukee School of Engineering, Academic Computing Services, 1025 N. Milwaukee Street, Milwaukee, WI 53202, USA 144.60 FDDI-CMC 93 SBC Technology Resources, Incorporated, 550 Maryville Centre Drive, Suite 400, St. Louis, MO 63141, USA 138.47 LATECH 279 86 Louisiana Tech University, Nethkin Hall - Room 235, Arizona Avenue, Ruston, LA 71272, USA 134.84 UMN-GWNET 267 266 University of Minnesota, Minnesota Supercomputer Center, 1200 Washington Avenue South, Minneapolis, MN 55415, USA 192.133.2 KSC 209 210 Kaman Sciences Corporation, P.O. Box 7463, Colorado Springs, CO 80933, USA 192.131.107 MEIKO-NET 560 281 Meiko Scientific Corp., 1601 Trapelo Road, Waltham, MA 02154, USA 192.129.66 LWOOD-NET1 184 164 USAISC-FLW, ASQNB-ZTI B-404, Ft. Leonard Wood, MO 65473, USA Total NSFNET T1 announced networks: 4333 T3 Network: Network IP: 192.131.107 Network Name: MEIKO-NET Location: Meiko Scientific Corp., 1601 Trapelo Road, Waltham, MA 02154, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network Total NSFNET T3 announced networks: 962 The configuration reports, map information sheets, and configuration files which reflect these changes are available for anonymous ftp on nis.nsf.net as usual. nsfsites - configuration reports latest report for: - NSFNET T1 has the file extension .now - NSFNET T3 has the file extension 3.now nsfconfg - configuration files for the routing software for each NSS latest report for: - NSFNET T1 has the file format config.nss# - NSFNET T3 has the file extension .t3p Please send all requests for configuration changes to nsfnet-admin(a)merit.edu using the NSFNET configuration forms. The forms are available on-line from the nis.nsf.net machine. Use ftp and the anonymous login to get on the machine. Do a "cd nsfsites" and grab the files TEMPLATE.NET, TEMPLATE.GATE, and TEMPLATE.AS. **************************************************************************** -B. Sue Blair Merit Network Operations

1 0

Re: ANS Connectivity Agreement
by Manavendra K. Thakur 10 Jan '92

10 Jan '92

>>>>> On Thu, 09 Jan 92 08:39:30 -0500, jrugo(a)nic.near.net said: > I believe, however, that cost of providing service is not the only > issue to be considered. I believe that a most important parameter > in the equation is the number of connections a network brings. As > we already have access to the NSFnet, what you are offering NEARnet > is access to Dialog. What you want is access to 115 of New > England's premier research and educational institutions. Certainly ANS wants access to those "115 New England premier research and educational institutions." But ANS also intends to find institution #116 and sign them up to directly connect to ANSnet as CO+RE customers! Given that ANS plans to actively compete with NEARnet and other regionals for the same end customers, how long will ANS and NEARnet (in this specific example) be able to maintain an amicable business relationship? Makes you think, doesn't it? I don't know the answer to that question, but I'm very glad that John Rugo posted his message. Not only does his message prove to me that my regional's business manager is actively doing his job by asking the right questions, but maybe his message will help other regionals ask some of the right questions as well. Manavendra K. Thakur Internet: thakur(a)zerkalo.harvard.edu Systems Programmer, High Energy Division BITNET: thakur(a)cfa.BITNET Harvard-Smithsonian Center for DECNET: CFA::thakur Astrophysics UUCP: ...!uunet!mit-eddie!thakur

2 1

Re: ANS Connectivity Agreement
by jrugo＠nic.near.net 09 Jan '92

09 Jan '92

Hello Al, Thank you for responding to my note. > I am responding to your note to Al Weis regarding the exchange of commercial > traffic between ANS and NEARnet. The short answer to your question is no, > ANS will not accept commercial (CO) traffic generated by an attached network > under the Connectivity Agreement. There is a Gateway agreement that can be > signed whereby ANS and the attached network exchange CO traffic. Understood. > The thread of your question implies that the infrastructure of NEARnet and that > of ANSnet are symmetrical. I don't think so. I asked for a fair and equitable arrangement, which does not necessarily imply symmetry. > Providing national backbone services as well as > direct attachments and gateways positions ANSnet within a different economic > and operational structure. The scale of our operational and other commitments > does not allow ANSnet to provide transit services in exchange for the delivery > of CO traffic being accepted by NEARnet. I agree that the cost of leased lines is related to the length of the line. I also understand that the costs of field service, sales and other customer-related activities are greater in a national effort versus a regional effort. However, the costs of these activities are very real for a regional network. The problem I have with your stated position is that the costs a regional incurs in providing its infrastructure are not recognized by the terms of your proposed agreement. To reiterate, I do not consider them to be fair and equitable. I believe, however, that cost of providing service is not the only issue to be considered. I believe that a most important parameter in the equation is the number of connections a network brings. As we already have access to the NSFnet, what you are offering NEARnet is access to Dialog. What you want is access to 115 of New England's premier research and educational institutions. Please do not misinterpret me - some of NEARnet's clients have expressed an interest in access to Dialog. I am actively considering whether ANSnet is the best way to provide that service to them. On another note, ANS now finds itself in a competitive position. As the manager of a regional network, I must consider the value of competing options to determine the best option for NEARnet to offer to its members. Some of the criteria I am considering are: * Quality of service provided by the vendor * Responsiveness of vendor * Cost of service * Richness of connectivity (i.e. # of connections) * Terms of contract Your salesman and I will once again be sitting down tommorrow to discuss ANSnet as an option for NEARnet. I intend to negotiate with him in good faith for the benefit of NEARnet's membership. Now, let me say in closing that the reason that I have brought my thoughts on these topics to this public forum is that I objected to Al Weis' characterization of the connectivity agreement. I have made my objections clear to this audience. Absent of similar grandstanding in the future, I now intend to close this public discussion. Thank you for making your position clear and for answering my question. - John M. Rugo NEARnet Business Manager Bolt Beranek and Newman

1 0