Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!decvax!ucbvax!TOPAZ.RUTGERS.EDU!hedrick
From: hedrick@TOPAZ.RUTGERS.EDU.UUCP
Newsgroups: mod.protocols.tcp-ip
Subject: Re: Becomming an Internet site
Message-ID: <8701021025.AA04489@topaz.rutgers.edu>
Date: Fri, 2-Jan-87 05:25:58 EST
Article-I.D.: topaz.8701021025.AA04489
Posted: Fri Jan  2 05:25:58 1987
Date-Received: Fri, 2-Jan-87 18:46:44 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 14
Approved: tcp-ip@sri-nic.arpa

Authorization is required to connect a network to the Arpanet, whether
the connection is direct or indirect.  More paperwork and time is
needed to connect directly to it, but you must register even if you
use a friendly local University as an intermediary, or connect to some
other network with indirect connections to the Arpanet (e.g. NSFnet).
Note that even such indirect connections require your network to
appear in the Arpanet's routing tables.  I.e. some Arpanet gateway
must advertise your network to the core gateways using EGP.

Note that it is not just your network that must be authorized to
connect to the Arpanet.  Individual users who use the Arpanet must be
using it for authorized purposes.  So when you connect a network to
the Arpanet, even indirectly, you are accepting the responsbility to
monitor your users and make sure that their use is appropriate.