- Test - lists.nanog.org

Re: ANS Connectivity Agreement
by ahoover＠hoovermac.ans.net 07 Jan '92

07 Jan '92

John, 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. The thread of your question implies that the infrastructure of NEARnet and that of ANSnet are symmetrical. 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. The regional does get something in return for accepting the ANS CO traffic in the form of added value to the regional's members who presumably may want access to and benefit from the CO services available. This added value means more members and more revenue. If you need any additional information, please give me a call. Al Hoover (914) 789-5300 >Here is my question from last week, to which I have not heard a definitive >answer. I think the list has some inquiring minds that want to know its answer >from you. >>> OK, so NEARnet would agree to accept commercial traffic from ANS, does ANS >>> agree to accept commercial traffic from NEARnet under the same terms and >>> conditions? As I read it, a regional agrees to use its infrastructure as a >>> distribution mechanism for ANS and gets nothing in return. >Thanks in advance for your clarification. >Sincerely, >John M. Rugo >NEARnet Business Manager >Bolt Beranek and Newman

2 1

Re: NCR - a followup note
by Martin Lee Schoffstall 07 Jan '92

07 Jan '92

Milo, I also believe that nothing should be implemented until the new routing coordinator is done under the NSF RFP. At best a recommendation should be put into place to consider. marty Yes. I think with the proper mods, we can support the kind of environment whe re nets can change carriers and such. However, it is vital to note that some amount of hierarchy is required to keep the routing info manageable. There is a trade-off between flexibility and scalability. If every group demands lots of flexibility, then it will not be possible to build the system as large as everyone might want... Thanks, Milo

2 3

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

07 Jan '92

The following networks have been added to the NSFNET policy-based routing database: T1 Network: Net # Net Name Primary Secondary Location -------- ----------- ------- --------- -------- 131.231 LUT-AC-UK 274 60 Loughborough University, University of Technology, Loughborough LE11 3TU, UNITED KINGDOM 151.195 CHP 1206 204 Children's Hospital of Pittsburgh, 3705 Fifth Avenue, Pittsburgh, PA 15213 157.134 OAR 266 267 Ohio Academic Resources Network, 1224 Kinnear Road, Columbus, OH 43212 192.73.228 SILVACO 200 754 Silvaco Data Systems, 4701 Patrick Henry Drive, Building 6, Santa Clara, CA 95054 192.83.245 PORTAL1 200 754 Portal Communications Company, 10385 Cherry Tree Lane, Cupertino, CA 95014 192.132.95 FRANZNET 701 279 Franz Incorporated, 1995 University Ave, Berkeley, Ca 94704 192.135.47 CSISDN 200 754 Connective Strategies International, 465B Fairchild Drive, Suite 207, Mountain View, CA 94043 192.135.237 MPL106 22 Marine Physical Lab/UCSD, Univ of CA at San Diego, La Jolla, CA 92023-0704 192.135.238 MPL4 22 Marine Physical Lab/UCSD, Univ of CA at San Diego, La Jolla, CA 92023-0704 192.138.88 OVL 266 267 Ohio Supercomputer Center, 1224 Kinnear Road, Columbus, OH 43212 Total NSFNET T1 announced networks: 4320 The following T1 gates have also been added: Router Internet Address: 192.12.211.3 Router Internet Name: T3 enss 137 Router AS Number: 756 (T1-T3 Network Interconnect (Princeton, NJ)) NSS number colocated with router: 8 Router type: T3 ENSS RS 6000 T3 Network: Network IP: 128.2 Network Name: CMU-NET Location: Carnegie-Mellon University, Computer Science Department, Schenley Park, Pittsburgh, PA 15213 Country Code: US 1:1206 PSCNET Network IP: 151.195 Network Name: CHP Location: Children's Hospital of Pittsburgh, 3705 Fifth Avenue, Pittsburgh, PA 15213 Country Code: US 1:1206 PSCNET Network IP: 192.73.228 Network Name: SILVACO Location: Silvaco Data Systems, 4701 Patrick Henry Drive, Building 6, Santa Clara, CA 95054 Country Code: US 1:200 BARRNet Network IP: 192.83.245 Network Name: PORTAL1 Location: Portal Communications Company, 10385 Cherry Tree Lane, Cupertino, CA 95014 Country Code: US 1:200 BARRNet Network IP: 192.132.95 Network Name: FRANZNET Location: Franz Incorporated, 1995 University Ave, Berkeley, Ca 94704 Country Code: US 42:701 Alternet Router Network IP: 192.135.47 Network Name: CSISDN Location: Connective Strategies International, 465B Fairchild Drive, Suite 207, Mountain View, CA 94043 Country Code: US 1:200 BARRNet Total NSFNET T3 announced networks: 961 The following T3 gates have also been added: AS Number: 757 AS Notes: T1-T3 Network Interconnect (Princeton, NJ) AS Country Code: US BkBn: 690 NSS: 140.222.137 - ENSS137 Princeton, NJ Gate: 192.12.211.1 - NSS 8 JVNC, Princeton, NJ 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

NCR discussion
by Belinda Sue Blair 07 Jan '92

07 Jan '92

Sorry for not replying sooner. I had indeed become imbued with the holiday spirit :).. I will respond to all mail in this one response: >>Folks, >> >>Greetings. On the NCR discussion, I would just like to say that I >>appreciate everyone's input on this, including the non-US people. >>We are all internetworking cohorts affected by these issues and have >>an obligation to work out whatever solution is best for the network >>while giving commercial customers what they require. Everyone should > >To whom do you refer when you say commercial customers (PSI or NCR) Sorry to be unclear. I meant customers of the regionals such as NCR. >>feel free to work with each other on this since anything in the >>database can be changed. Yet again, I state the obvious while >>tip-toeing through the political tulips :-). > >Well its looks like that there needs to be some kind of policy >on how many routes one entity can have propogated, and of course >the requisite appeal proccess :-). This problem will be recoccurring >as larger places join to the net and are unwilling to change how they >do things, wether or not it hurts the rest of the world. The more >money becomes involved in netoworking the less likely it becomes >that everybody will be willing to play nice and share :-) I would agree that some kind of policy needs to be implemented if the equipment used to pass traffic cannot handle levels beyond certain thresholds. On the subject of technical solutions, if a viable one was presented to NCR, they could certainly implement that. In terms of administrative setup, it has been suggested that NCR be put on their own AS, so that regionals could ignore the NCR nets without ignoring all the PSINet traffic. Though no commercial organization has their own AS, I personally don't object to setting a precedent (again!) if it benefits the net. Perhaps others in nsfnet-admin and regional-techs, etc. could respond to this as well. You make a good point, though I would say that PSINet apparently did refuse NCR when first approached. The NIC granted NCR those nets. What does the NIC gain except continued roasting by people saying that they (the NIC, that is) don't know what they're doing? There is also the theory that PSINet gave the NIC some of their NCR $$$$ to get the NCR implementation which smells like musty Air Jordans to me (the theory, that is). Maybe we can get Joan Collins to play me in the made-for-tv version of this sordid little gem :-).. -B. Sue Blair Merit Network Operations

1 0

CERFnet Weekly Report for the week of Monday, December 30, 1991.
by Donna Bigley 06 Jan '92

06 Jan '92

############################################################################### This is the CERFnet weekly activity report for the period of Monday, December 30th through Sunday, January 5th, 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: 05-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: UCI SITES AFFECTED: UCI, UCI Dial n' CERF, CSUCO, HUGHES, EMULEX, UNOCAL, MTI, SPARTA, FULLERTON, and CMD. TIME STARTED: MON. 12-30-91 10:33 TIME ENDED: MON. 12-30-91 12:55 TIME STARTED: MON. 12-30-91 14:33 TIME ENDED: MON. 12-30-91 16:08 TIME ELAPSED: 3 hours 57 min (Intermittant Access) REASON: Link Failure SITE: SAIC SITES AFFECTED: SAIC TIME STARTED: MON. 12-30-91 10:34 TIME ENDED: MON. 12-30-91 13:56 TIME ELAPSED: 3 hours 22 min REASON: Site Activity SITE: GD SITES AFFECTED: GD TIME STARTED: WED. 1-1-92 10:36 TIME ENDED: WED. 1-1-92 20:00 TIME ELAPSED: 9 hours 24 min REASON: Site Scheduled Maintenance SITE: UCI SITES AFFECTED: UCI, UCI Dial n' CERF, CSUCO, HUGHES, EMULEX, UNOCAL, MTI, SPARTA, FULLERTON, and CMD. TIME STARTED: FRI. 1-3-92 07:30 TIME ENDED: FRI. 1-3-92 11:27 TIME ELAPSED: 3 hours 57 min (Intermittant Outages during scheduled upgrade) REASON: CERFnet/Site Scheduled Maintenance SITE: DISNEY SITES AFFECTED: DISNEY TIME STARTED: FRI. 1-3-92 13:20 TIME ENDED: FRI. 1-3-92 13:55 TIME ELAPSED: 35 min REASON: Power Outage SITE: PEPPERDINE SITES AFFECTED: PEPPERDINE TIME STARTED: SAT. 1-4-92 09:17 TIME ENDED: SAT. 1-4-92 09:50 TIME STARTED: SAT. 1-4-92 10:28 TIME ENDED: SAT. 1-4-92 10:51 TIME ELAPSED: 56 min REASON: Site Activity SITE: QUALCOMM SITES AFFECTED: QUALCOMM TIME STARTED: SAT. 1-4-92 12:57 TIME ENDED: SAT. 1-4-92 13:22 TIME ELAPSED: 25 min REASON: Unknown SITE: SAIC SITES AFFECTED: SAIC TIME STARTED: SAT. 1-4-92 14:38 TIME ENDED: SAT. 1-4-92 15:41 TIME ELAPSED: 1 hour 3 min REASON: Site Scheduled Maintenance SITE: EMULEX SITES AFFECTED: EMULEX TIME STARTED: SUN. 1-5-92 22:02 TIME ENDED: SUN. 1-5-92 22:13 TIME ELAPSED: 11 min REASON: Unknown ------------------------------------------------------------------------ CERFNET TRAFFIC CAPACITY USAGE AT EACH CIRCUIT LINK LINK SPEED CAPACITY PEAK HOUR (PDT) SDSC/CALTECH 1.544 mbps 04.3% 10:00 SDSC/UCI 1.544 mbps 03.6% 14:00 SDSC/UCLA 1.544 mbps 05.8% 14:00 SDSC/UCOP 1.544 mbps 02.1% 15:00 SDSC/UCR 1.544 mbps 00.5% 15:00 UCI/UCLA 1.544 mbps 03.1% 14:00 UCLA/UCSB 512 kbps 03.4% 12:00 SDSC/AGI 1.544 mbps 00.2% 16:00 SDSC/BIOSYM 1.544 kbps 00.1% 08:00 SDSC/GA 1.544 mbps 00.5% 16:00 SDSC/GD 1.544 mbps 00.2% 07:00 SDSC/SAIC 1.544 mbps 01.2% 07:00 SDSC/SCAQMD 1.544 mbps 00.02% 10:00 SDSC/SDSU 1.544 mbps 00.5% 17:00 UCI/CSU CO(SWRL) 1.544 mbps 01.2% 14:00 UCOP/APPLE 1.544 mbps 00.6% 17:00 UCOP/CISCO 1.544 mbps 00.5% 17:00 UCR/LLUMC 1.544 mbps 00.2% 15:00 CALTECH/CADAM 56 kbps 00.5% 11:00 CALTECH/CLAREMONT 56 kbps 13.0% 14:00 CALTECH/DISNEY 56 kbps 05.1% 14:00 CALTECH/OXY 56 kbps 02.9% 17:00 SDSC/AJS 56 kbps 01.5% 14:00 SDSC/KOREA 56 kbps 02.0% 18:00 SDSC/QUALCOMM 56 kbps 06.2% 11:00 SDSC/SCIH 56 kbps 03.9% 15:00 SDSC/USD 56 kbps 03.5% 14:00 SDSC/USIU 56 kbps 02.6% 11:00 SDSC/XEROX 56 kbps 00.8% 07:00 UCI/CMD 56 kbps 02.6% 11:00 UCI/EMULEX 56 kbps 03.8% 18:00 UCI/FULLERTON 56 kbps 02.2% 14:00 UCI/HUGHES 56 kbps 02.9% 13:00 UCI/MTI 56 kbps 05.1% 15:00 UCI/SPARTA 56 kbps 02.3% 17:00 UCI/UNOCAL 56 kbps 03.1% 22:00 UCLA/ISX 56 kbps 01.0% 14:00 UCLA/PEPPERDINE 56 kbps 02.4% 10:00 UCLA/QUOTRON 56 kbps 05.2% 10:00 UCLA/SMC 56 kbps 02.6% 21:00 UCOP/FARALLON 56 kbps 03.0% 11:00 UCOP/INTEL 56 kbps 11.3% 15:00 UCOP/LSIL 56 kbps 01.8% 16:00 UCOP/NETLABS 56 kbps 14.1% 19:00 ------------------------------------------------------------------------------ SITE CISCO BOX UPTIME SINCE LAST REBOOT (as of 00:15 PST on Jan. 6, 1992): CERFnet BACKBONE CALTECH [131.215.139.253] Up: 241 days 22 hours 43 minutes SDSC Drzog [132.249.16.13] Up: 22 days 08 hours 25 minutes SDSC Hang10 [132.249.16.15] Up: 18 days 07 hours 11 minutes UCI [128.200.1.101] Up: 02 days 12 hours 49 minutes [CERFnet/Site Scheduled Maintenance] UCLA [128.97.130.10] Up: 09 days 00 hours 45 minutes UCOP [134.24.52.112] Up: 44 days 08 hours 41 minutes UCR [134.24.108.105] Up: 51 days 12 hours 36 minutes CERF 1544 AGI [134.24.202.110] Up: 09 days 17 hours 54 minutes APPLE [134.24.70.200] Up: 70 days 06 hours 15 minutes BIOSYM [134.24.57.200] Up: 28 days 09 hours 14 minutes CISCO Systems [134.24.54.200] Up: 33 days 14 hours 09 minutes CSUCO/SWRL [130.150.102.200] Up: 19 days 18 hours 15 minutes GA [134.24.221.200] Up: 79 days 16 hours 34 minutes LLUMC [134.24.208.200] Up: 47 days 12 hours 22 minutes SAIC [134.24.53.208] Up: 01 days 08 hours 34 minutes [Site Scheduled Maintenance] UCSB [134.24.107.107] Up: 47 days 07 hours 38 minutes CERF 56 AJS [134.24.225.101] Up: 48 days 15 hours 50 minutes CADAM [134.24.229.200] Up: 02 days 13 hours 06 minutes [Power Outage] CLAREMONT [134.24.206.109] Up: 07 days 06 hours 49 minutes CMD [134.24.218.200] Up: 82 days 12 hours 25 minutes DATAPRODUCTS [134.24.211.104] Up: 152 days 10 hours 48 minutes DISNEY [134.24.207.211] Up: 02 days 10 hours 20 minutes [Power Outage] EMULEX [134.24.209.212] Up: 22 days 15 hours 48 minutes FARALLON [134.24.56.200] Up: 31 days 11 hours 43 minutes FULLERTON [134.24.214.217] Up: 20 days 15 hours 33 minutes GD [134.24.60.200] Up: 04 days 04 hours 14 minutes [Site Scheduled Maintenance] HUGHES [134.24.204.200] Up: 52 days 07 hours 21 minutes INTEL [134.24.55.200] Up: 08 days 03 hours 19 minutes LSIL [134.24.72.200] Up: 08 days 14 hours 14 minutes MTI [134.24.216.100] Up: 02 days 13 hours 39 minutes [Site Activity] NETLABS [134.24.71.200] Up: 30 days 15 hours 07 minutes OXY [134.24.205.108] Up: 132 days 12 hours 51 minutes PEPPERDINE [134.24.203.218] Up: 01 days 13 hours 24 minutes [Site Activity] QUALCOMM [134.24.200.201] Up: 26 days 18 hours 19 minutes QUOTRON [134.24.230.202] Up: 41 days 13 hours 44 minutes SANTA MONICA [134.24.210.219] Up: 268 days 14 hours 04 minutes SCAQMD [134.24.234.200] Up: 17 days 14 hours 27 minutes SCI-HOR [134.24.109.205] Up: 38 days 11 hours 15 minutes SDSU [192.77.100.101] Up: 27 days 16 hours 31 minutes SERI/KOREA [134.24.223.200] Up: 104 days 00 hours 00 minutes SPARTA [134.24.215.200] Up: 16 days 16 hours 24 minutes UNOCAL [134.24.217.200] Up: 14 days 22 hours 45 minutes USD [134.24.201.106] Up: 91 days 10 hours 55 minutes USIU [134.24.222.215] Up: 183 days 17 hours 07 minutes XEROX [134.24.51.207] Up: 67 days 23 hours 22 minutes DIAL n' CERF DNC-SDSC [134.24.1.2] Up: 21 days 14 hours 57 minutes DNC-UCI [134.24.2.2] Up: 06 days 13 hours 38 minutes [Site Activity] DNC-UCLA [134.24.3.2] Up: 09 days 00 hours 46 minutes DNC-CALTECH [134.24.4.2] Up: 67 days 21 hours 02 minutes DNC-UCOP [134.24.5.2] Up: 128 days 15 hours 10 minutes

1 0

Advanced Topics Seminar Travel Info
by smr 06 Jan '92

06 Jan '92

For those who will be attending the Advanced Topics Seminar on Jan 23 and 24th...specifically for those arriving by plane who do not wish to rent a car...below I've included airport limo and campus bus service. Let me know if you have questions on this. Sheri Repucci Merit/Internet Engineering ============================================================ Airport Limo ------------ Airport limo service to and from the Michigan Union on the University of Michigan campus. Ticket costs: $14.00 one way $25.00 round trip Departure times : The limo leaves Detroit Metro Airport once every hour on the top of the hour from 7:00 am until Midnight. Tickets can be purchased at any ground transportation center. The limo leaves the Michigan Union once every hour at 1/4 past the hour from 5:15 am until 7:15 pm. Travel time: Allow at least an hour travel time in each direction. ============================================================= Bus Service from Central Campus to North Campus ----------------------------------------------- For guests staying at the Campus Inn, Oxford housing (located within the Michigan League), or other central campus locations the following is information regarding the campus bus system. There is no fare for the University buses. >From either housing choice you will board the bus in front of the Power Center. From Oxford housing (in the Michigan League) you will simply cross the lawn, cross a street and you are at the bus stop. From the Campus Inn you have a longer walk. You walk one fairly long block down E. Huron Street to the Power Center bus stop. Take any bus that starts with the word "North" and it will drop you off at the right spot on North Campus. Your bus choices are: North Commuter, Northwood, and North Campus. It is highly recommended that you take the "North Commuter" bus, much less crowded than the "Northwood" bus. The North Campus bus runs only at night and on weekends. Any of the buses will drop you off in front of the Art and Architecture building on north campus. Directly across the street from the bus stop is the North Campus Commons. Chrysler Center is the building directly to the right of the Commons, assuming you are looking at the Commons from the bus stop in front of the Art and Architecture building. A one way trip is approximately 10 minutes. The "North Commuter" bus runs in both directions every 15 minutes. ----------------------------------------------------------------- It departs from the Power Center stop every 15 minutes from 7:00am until 6:15pm. It departs from the Commons every 15 minutes from 7:05am until 6:20pm. On the return trip from north campus the bus leaves from the stop in front of the North Campus Commons (directly across the street from the Art and Architecture stop). The "Northwood" bus runs in both directions every 10-20 minutes. -------------------------------------------------------------- It departs from the Power Center stop every 10 minutes from from 7:20am until 6:50pm. Then it runs every 20 minutes from 7:20 until midnight. On the return trip from north campus the bus leaves from the stop in front of the North Campus Commons (directly across the street from the Art and Architecture stop). It departs from the Commons every 10 minutes from 7:15am until 7:05pm. And every 20 minutes after that until midnight. Additional Evening Bus Service ------------------------------ After 6:50pm the "North Campus" bus runs until approximately 2:20am. The departure times vary significantly but are approximately every 10 to 20 minutes until 10:30pm.

1 0

December NSFNET T1 Usage by Service
by Susan.M.Horvath＠um.cc.umich.edu 03 Jan '92

03 Jan '92

NSFNET T1 Usage by Service December 1991 Service Type % Packets % Bytes ============ ========= ======= File exchange 28 51 Networked mail 19 22 Interactive 15 5 Name lookup 9 4 Other TCP/UDP services 27 17 Non TCP/UDP services 2 1 --- --- 100 100 The categories above are defined as follows: File exchange ftp: data and control (tcp ports 20, 21) Networked mail smtp, nntp, vmnet, uucp (tcp ports 25, 119, 175, 540) Interactive telnet, finger, who, login (tcp ports 23, 79, 513, udp port 513) Name lookup domain name service (udp port 53, tcp port 53) Other TCP/UDP services all tcp/udp ports not included above (e.g. irc, talk, X-windows, appletalk) Non-TCP/UDP services icmp, egp, etc. More detailed information is available for anonymous FTP from NIS.NSF.NET (the Merit/NSFNET Information Services machine) in the file NSF91-12.PORTS on the NSFSTATS directory.

1 0

Advanced topic seminar - ride from airport?
by Vince Fuller 03 Jan '92

03 Jan '92

Hi - is there anyone else attending the seminar on the 23rd/24th who will be arriving around 7:30PM on the 22nd...? If so, a ride from the airport would be appreciated (and I'll even kick-in $$ for the mileage to the University...) Thanks, --Vince

1 0

Re: Request processing
by scottw＠nic.ddn.mil 03 Jan '92

03 Jan '92

Bill, I assume that you are referring to calls to the NIC. The message was addressed to such a wide audience that it is hard to tell. Please identify your specific problems and I will look into to the holdup. I have been working with Dan Long to track down his outstanding problem. Please ensure that they are not the same. I have done an audit of outstanding registration actions and do not see any that are not on hold for a valid reason. Your responce will help me ensure that my information is correct. Thanks, Scott > > > Well, the Sesquinet regional has also benn having problems. The > best response I've had is to get on the phone and talk them through the > requet and then allocate time to call back at regular intervals (weekly) > to check on the status. We still have several outstanding items, one of > which goes back to October. Sigh... > > -- > Regards, > Bill Manning > 713-285-5415 > R.U. (o-kome) > >

1 0

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

03 Jan '92

Steve G., The change which you requested has been made to the NSFNET T1 policy-based routing database and will take effect by 08:00 EST Friday morning. -B. Sue Blair Merit Network Operations *********************************************************************** >To: "Steven K. Widmayer" <skw(a)merit.edu> >Cc: nwg(a)merit.edu >Subject: Re: Additions to the NSFNET policy-based routing database >In-Reply-To: Your message of "Tue, 31 Dec 91 08:25:37 EST." > <9112311325.AA17963(a)home.merit.edu> >Date: Wed, 01 Jan 92 16:11:30 EST >From: Steve Goldstein--Ph 202-357-9717 <sgoldste(a)cise.cise.nsf.gov> > > >Steve, > >If you will recall, I asked that you clear up the following: > >192.93.218 PHYNET-C-5 590 Institut National de > Recherche en > Informatische et > Automatique (IN2P3), BP > 105; F-78153 Le Chesnay > Cedex, FRANCE > > >The institution named (BTW, should be "Informatique" and not "Informatische"-- >We're getting to polyglot Europe too quickly here) is INRIA, and NOT IN2P3! >Important that we learn from EASINET/GMD just which one is the responsible >institution. INRIA is indeed in Le Chesnay. IN2P3 is in Lyon. GMD folk >keep mixing this "metaphor". > >Thanks, > >Steve G.

2 1