[9976] in Commercialization & Privatization of the Internet
Re: attaching a network to the Internet (was Re: Confusion
daemon@ATHENA.MIT.EDU (Steven K. Widmayer)
Mon Jan 31 21:41:21 1994
Date: Mon, 31 Jan 1994 21:39:42 -0500
From: "Steven K. Widmayer" <skw@merit.edu>
To: NORDLUND@ccstaff.cc.ukans.edu, com-priv@psi.com
>From: Dave Nordlund <NORDLUND@ccstaff.cc.ukans.edu>
> Date sent: Sun, 30 Jan 1994 20:08:56 -0500
> From: "Steven K. Widmayer" <skw@merit.edu>
> To: NORDLUND@ccstaff.cc.ukans.edu, adamfast@u.washington.edu
> Subject: Re: attaching a network to the Internet (was Re: Confusion)
> Copies to: com-priv@psi.com
> ...
>
> >
> > to get your network announced to the NSFnet, you fill out the NACR form
> >and send it to MERIT. the two main pieces of information on the NACR are
> >your ASN and the ASN(s) of your provider. (your provider has to tell you
> >their ASN.)
>
> A correction. We (Merit) only accept NACRs from service providers who
> have a peering relationship with the NSFNET/ANSnet. So send your NACRs
> to your NSFNET- or ANSnet-connected service provider, who may or may not
> forward them on to Merit for inclusion in the PRDB, depending upon their
> policies and agreement to the NSFNET AUP for NSFNET service subscribers,
> or ANS policies for ANS subscribers, etc.
>
>
OK, Now how do I become a NSFNET-connect service provider? That what
is desired.
Dave,
I don't believe there are any plans to add any new NSFNET hosting sites
to the existing architecture. So you would need to attach to the NSFNET
service at one of the existing hosting sites. You would need the agreement
of one of the existing hosting sites:
ENSS# City
----- -------------
128 NSF-Palo Alto, CA (Bay Area Regional Research Net - BARRnet)
129 NSF-Urbana-Champaign, IL (University of Illinois at Urbana-
Champaign - UIUC)
130 NSF-Chicago, IL (Argonne Labs)
131 NSF-Ann Arbor, MI (MERIT Computer Network)
132 NSF-Pittsburgh, PA (Pittsburgh Supercomputing Center - PSCNET)
133 NSF-Ithaca, NY (Cornell Regional network)
134 NSF-Boston, MA (NEARnet Regional Network)
135 NSF-San Diego, CA (San Diego Supercomputer Center - SDSC
Regional network)
136 NSF-College Park, MD (SURANET Regional Network)
137 NSF-Princeton, NJ (JvNCnet / Global Enterprise Services)
138 NSF-Atlanta, GA (SURANET Regional Network at Georgia Tech)
139 NSF-Houston, TX (SESQUINET Regional Network)
140 NSF-Lincoln, NE (MIDnet)
141 NSF-Boulder, CO (NCAR Regional Network)
142 NSF-Salt Lake City, UT (Westnet Regional Network)
143 NSF-Seattle, WA (NorthWestNet Regional Network)
144 NSF-Palo Alto, CA #2 - Ames (FIX-West at NASA)
145 NSF-College Park #2 - Fix-East (FIX-East at SURAnet)
146 NSF-Arlington, VA (DARPA)
Merit would then need to get the approval of NSF before direct peering
with the NSFNET service could be established.
--Steve Widmayer (skw@merit.edu)
