[1760] in Commercialization & Privatization of the Internet

home help back first fref pref prev next nref lref last post

Re: Policy routing end-user support

daemon@ATHENA.MIT.EDU (mak@merit.edu)
Tue Dec 17 00:12:11 1991

From: mak@merit.edu
To: morris@niwot.scd.ucar.EDU (Don Morris)
Cc: daniel@nstn.ns.ca, steve@ncri.cise.nsf.gov, com-priv@psi.com
In-Reply-To: Your message of "Mon, 16 Dec 91 11:00:47 MST."
Date: Tue, 17 Dec 91 00:10:54 -0500

Hi. I've placed a file describing the filtering restrictions on
merit.edu, pub/nsfnet/restricted. This currently only lists
the Dialog network, as I am nearly positive that NSFNET and
ANSNET do no other filtering. This will also be available on
nis.nsf.net at some point (those mainframes mystify me). I hope
this helps.

We will also look into providing a finger or other kind of server
to provide policy information (good idea).

	Mark


> From:    morris@niwot.scd.ucar.EDU (Don Morris)

> 
> 
> 
> 	->Could we perhaps compile a list of networks being filtered by NSF, as
 a
> 	->place to check when we get a "Can't Get There" support incident?
> 
> 	That's an excellent suggestion.  I have spoken to Merit who have agreed
 to
> 	maintain such a list.  It will be available by anonymous ftp on nis.nsf
.net.
> 
> 
> Since the list will be dynamic, and one would normally want
> to check to see if a given network is filtered, would it also
> be reasonable to have MERIT install a finger facility or
> something equivalent, so as to check things quickly?
> 
> --Don--

home help back first fref pref prev next nref lref last post