From tdunk@icm1.icp.net Wed Sep  1 15:04:00 1993
Received: from icm1.icp.net by fido.wps.com (5.67/wps.com-hackery)
	id AA21667; Wed, 1 Sep 93 15:03:10 -0700
Received: from [144.224.5.45] by icm1.icp.net (5.65/1.34)
	id AA00179; Wed, 1 Sep 93 18:04:45 -0500
X-Mailer: InterCon TCP/Connect II 1.1
Message-Id: <9309011805.AA06459@Tom Dunkenberger.icm1.icp.net>
Date: Wed,  1 Sep 1993 18:05:06 -0500
From: Tom Dunkenberger <tdunk@icm1.icp.net>
To: tomj@wps.com
Cc: tdunk@icm1.icp.net, syoung@icm1.icp.net, rcollet@icm1.icp.net,
        /dd.un=m.cravens/o=us.sprint/admd=telemail/c=us/@sprint.com,
        /dd.un=d.stevens/o=us.sprint/admd=telemail/c=us/@sprint.com
Subject: RGnet Proposal - Appendices (2 of 2) (part 1 of 2)
Status: OR

************************************************************************
                              APPENDIX A:
************************************************************************

THE NSFNET BACKBONE SERVICES ACCEPTABLE USE POLICY-June 1992
(<NIC.MERIT.EDU> /nsfnet/acceptable.use.policies/nsfnet.txt)
 
GENERAL PRINCIPLE:

(1) NSFNET Backbone services are provided to support open research and 
education in and among US research and instructional institutions, plus 
research arms of for-profit firms when engaged in open scholarly 
communication and research.  Use for other purposes is not acceptable.

SPECIFICALLY ACCEPTABLE USES:

(2) Communication with foreign researchers and educators in connection with 
research or instruction, as long as any network that the foreign user employs 
for such communication provides reciprocal access to US researchers and 
educators.

(3) Communication and exchange for professional development, to maintain 
currency, or to debate issues in a field or subfield of knowledge.

(4) Use for disciplinary-society, university-association, government-
advisory, or standards activities related to the user's research and 
instructional activities.

(5) Use in applying for or administering grants or contracts for research or 
instruction, but not for other fundraising or public relations activities.

(6) Any other administrative communications or activities in direct support 
of research and instruction.

(7) Announcements of new products or services for use in research or 
instruction, but not advertising of any kind.

(8) Any traffic originating from a network of another member agency of the 
Federal Networking Council if the traffic meets the acceptable use policy of 
that agency.

(9) Communication incidental to otherwise acceptable use, except for illegal 
or specifically unacceptable use.

UNACCEPTABLE USES:

(10) Use for for-profit activities, unless covered by the General Principle 
or as a specifically acceptable use.

(11) Extensive use for private or personal business.


This statement applies to use of the NSFNET Backbone only.  NSF expects that 
connecting networks will formulate their own use policies.  The NSF Division 
of Networking and Communications Research and Infrastructure will resolve any 
questions about this Policy or its interpretation.
------------------------------------------------------------------------




************************************************************************
                              APPENDIX B:
************************************************************************

INTERNET NUMBER TEMPLATE

[ netinfo/internet-number-template.txt ]                     [ 04/93 ]

This form must be completed as part of the application process for obtaining 
an Internet Protocol (IP) Network Number.  To obtain an Internet number, 
please provide the following information on-line, via electronic mail, to 
HOSTMASTER@INTERNIC.NET.  If electronic mail is not available to you, please 
fax to:

                                Mr. Robert Castelli
                                Sprint
                                13221 Woodland Park Road
                                Herndon, VA 22071

                                Fax: 703-904-2252
                                Tel: 703-904-2453

                                ATTN:  IP Address Request

or, mail hard copy to:

                                Network Solutions               
                                InterNIC Registration Services 
                                505 Huntmar Park Drive 
                                Herndon, VA 22070 

Once the INTERNIC Registration Services receives your completed application 
they will send you an acknowledgment, via electronic or postal mail.

NOTE: This application is solely for obtaining a legitimate IP network number 
assignment.  If you're interested in officially registering a domain please 
complete the domain application found in netinfo/domain-template.txt.  If FTP 
is not available to you, please contact HOSTMASTER@INTERNIC.NET or phone the 
NIC at (800) 444-4345 (703) 742-4777 for further assistance. 

YOUR APPLICATION MUST BE TYPED. 

1) If the network will be connected to the Internet, you must provide the 
name of the governmental sponsoring organization, and the name, title, 
mailing address, phone number, net mailbox, and NIC Handle (if any) of the 
contact person (POC) at that organization who has authorized the network 
connection. This person will serve as the POC for administrative and policy 
questions about authorization to be a part of the Internet.  Examples of such 
sponsoring organizations are: DISA DNSO, the National Science Foundation 
(NSF), or similar military or government sponsors.

NOTE: If the network will NOT be connected to or routed to the US 
R&E/Government Internet, then you do not need to provide this information.

      1a.  Sponsoring Organization:
      1b.  Contact name (Lastname, Firstname):
      1c.  Contact title:
      1d.  Mail Address :

      1e.  Phone :
      1f.  Net mailbox :
      1g.  NIC handle (if known):


2) Provide the name, title, mailing address, phone number, and organization 
of the technical POC.  The on-line mailbox and NIC Handle (if any) of the 
technical POC should also be included.  This is the POC for resolving 
technical problems associated with the network and for updating information 
about the network.  The technical POC may also be responsible for hosts 
attached to this network.

      2a.  NIC handle (if known):
      2b.  Technical POC name (Lastname, Firstname):
      2c.  Technical POC title:
      2d.  Mail address :

      2e.  Phone :
      2f.  Net Mailbox :


3) Supply the short mnemonic name for the network (up to 12 characters). This 
is the name that will be used as an identifier in internet name and address 
tables.

      3.  Network name:


4) Identify the network geographic location and the responsible organization 
establishing the network.

      4a.  Postal address for main/headquarters network site:
      4b.  Name of Organization:


5) RESERVED


6) Estimate the number of hosts that will be on the network:

      6a. Initially:
      6b. Within one year:
      6c. Within two years:
      6d. Within five years:


7) Unless a strong and convincing reason is presented, the network (if it 
qualifies at all) will be assigned a class C network number.  If a class C 
network number is not acceptable for your purposes state why. (Note: If there 
are plans for more than a few local networks, and more than 100 hosts, you 
are strongly urged to consider subnetting. [See RFC 950])

      7.  Reason:


8) Networks are characterized as being either Research, Defense, Government - 
Non Defense, or Commercial, and the network address space is shared between 
these four areas.  Which type is this network?

      8. Type of network: 


9) What is the purpose of the network?
    
      9.  Purpose: 


For further information contact INTERNIC Registration Services:  

      Via electronic mail:  HOSTMASTER@INTERNIC.NET 
      Via telephone:        (800) 444-4345
      Via postal mail:      Network Solutions             
                            INTERNIC Registration Service 
                            505 Huntmar Park Drive          
                            Herndon, VA 22070 
------------------------------------------------------------------------




************************************************************************
                              APPENDIX C:
************************************************************************

INTERNET DOMAIN REGISTRATION

[ NETINFO:DOMAIN-TEMPLATE.TXT ]                           [ 04/93 ]

To establish a domain, the following information must be sent to the INTERNIC 
Domain Registrar (HOSTMASTER@INTERNIC.NET). Questions may be addressed to the 
Hostmaster by electronic mail at the above address, or by phone at (703) 742-
4777 or (800) 444-4345.

   If electronic mail is not available to you, please fax to:

                                Mr. Robert Castelli
                                Sprint
                                13221 Woodland Park Road
                                Herndon, VA 22071

                                Fax: 703-904-2252
                                Tel: 703-904-2453

                                ATTN:  DOMAIN Request

NOTE: The key people must have electronic mailboxes and "handles," unique NIC 
database identifiers.  If you have access to "WHOIS", please check to see if 
you are registered and if so, make sure the information is current.  Include 
only your handle and any changes (if any) that need to be made in your entry.  
If you do not have access to "WHOIS", please provide all the information 
indicated and a handle will be assigned.

(1) The name of the top-level domain to join (EDU, COM, MIL, GOV, NET, ORG).

        1.  Top-level domain:


(2) The name of the domain (up to 12 characters).  This is the name that will 
be used in tables and lists associating the domain with the domain server 
addresses.  [While, from a technical standpoint, domain names can be quite 
long we recommend the use of shorter, more user-friendly names.]

        2.  Complete Domain Name: 


(3) The name and address of the organization establishing the domain.

        3a.  Organization name:


        3b.  Organization address:  



(4) The date you expect the domain to be fully operational.

        4.  Date operational: 


(5) The handle of the administrative head of the organization -- or this 
person's name, mailing address, phone number, organization, and network 
mailbox. This is the contact point for administrative and policy questions 
about the domain.  In the case of a research project, this should be the 
principal investigator.

NOTE: Both the Administrative and the Technical/Zone contact of a domain MUST 
have a network mailbox, even if the mailbox is to be within the proposed 
domain.


         Administrative Contact

     5a.  Handle (if known) : 
     5b.  Name (Last, First) : 
     5c.  Organization: 
     5d.  Mail Address: 

     5e.  Phone Number: 
     5f.  Net Mailbox : 


(6) The handle of the technical contact for the domain -- or the person's 
name, mailing address, phone number, organization, and network mailbox.  This 
is the contact point for problems concerning the domain or zone, as well as 
for updating information about the domain or zone.

    Technical and Zone Contact

     6a.  Handle (if known): 
     6b.  Name (Last, First) :  
     6c.  Organization:  
     6d.  Mail Address:  

     6e.  Phone Number: 
     6f.  Net Mailbox : 


(7) Domains must provide at least two independent servers on Government-
sponsored networks that provide the domain service for translating names to 
addresses for hosts in this domain. 

* If you are applying for a domain and a network number assignment 
simultaneously and a host on your proposed network will be used as a server 
for the domain, you must wait until you receive your network number 
assignment and have given the server(s) a netaddress before sending in the 
domain application. Sending in the domain application without complete 
information in Sections 7 and 8 of this template will result in the delay of 
the domain registration.
 
Also, establishing the servers in physically separate locations and on 
different PSNs and/or networks is strongly recommended.
 
NOTE: All new hosts acting as servers will appear in the DNS root servers but 
will not appear in the HOSTS.TXT file unless otherwise requested.

      Primary Server: HOSTNAME, NETADDRESS, HARDWARE, SOFTWARE

      7a.  Primary Server Hostname:
      7b.  Primary Server Netaddress: 
      7c.  Primary Server Hardware: 
      7d.  Primary Server Software: 


   (8) The Secondary server information.

      8a.  Secondary Server Hostname: 
      8b.  Secondary Server Netaddress: 
      8c.  Secondary Server Hardware:
      8d.  Secondary Server Software:


9) If any currently registered hosts will be renamed into the new domain, 
please specify old hostname, netaddress, and new hostname.

      For example:

         BAR-FOO2.XYZ.COM (26.8.0.193) -> FOO2.BAR.COM
         BAR-FOO3.XYZ.COM (192.7.3.193) -> FOO3.BAR.COM
         BAR-FOO4.ARPA (34.6.0.193) -> FOO4.BAR.COM

(10) Please describe your organization briefly.  
 
For example: Our Corporation is a consulting  organization of people working 
with UNIX and the C language in an electronic networking environment.  It 
sponsors two technical conferences annually and distributes a bimonthly 
newsletter.


For further information contact INTERNIC Registration Services:  

      Via electronic mail:  HOSTMASTER@INTERNIC.NET 
      Via telephone:        (800) 444-4345 or (703) 742-4777
      Via postal mail:      Network Solutions             
                            INTERNIC Registration Services
                            505 Huntmar Park Drive         
                            Herndon, VA  22070   
------------------------------------------------------------------------




************************************************************************
                              APPENDIX D:
************************************************************************
AUTONOMOUS SYSTEM NUMBER

[ netinfo/asn-template.txt ]                           [ 04/93 ]

Registering for an Autonomous System Number implies that you plan to 
implement one or more gateways and use them to connect networks in the 
Internet.  Please provide us with further details about your plans, and with 
information about the administrative authority you have for participating in 
the Internet. 

It is strongly advised that you follow the development of inter-autonomous 
systems protocols in the IAB task forces.

Send the completed application on-line to HOSTMASTER@INTERNIC.NET Or, if 
electronic mail is not available to you, please fax to:

                                Mr. Robert Castelli
                                Sprint
                                13221 Woodland Park Road
                                Herndon, VA 22071

                                Fax: 703-904-2252
                                Tel: 703-904-2453

                                ATTN:  ASN Request

Or, mail paper copy to:

        Network Solutions             
        ATTN: INTERNIC Registration Services 
        505 Huntmar Park Drive            
        Herndon, VA  22070

Questions may be addressed to the Registration Services Hostmaster by 
electronic mail at the above address, or by phone at (800) 444-4345 or (703) 
472-4777.

To obtain an Autonomous System Number the following information must be
provided:

NOTE: The key people must have electronic mailboxes and NIC "Handles," unique 
NIC database identifiers.  If you have access to WHOIS, please check to see 
if you are registered and if so, make sure the information is current.  
Include only your Handle and any changes (if any) that need to be made in 
your entry.  If you do not have access to WHOIS, or are not registered in the 
NIC WHOIS database, please provide all the information requested and a NIC 
Handle will be assigned.

1) The name, title, mailing address, phone number, and organization of the 
administrative head of the organization.  This is the contact point for 
administrative and policy questions about the autonomous system.  In the case 
of a research project this should be the Principal Investigator.  The on-line 
mailbox and Handle (if any) of this person should also be included.

      Example:

      Administrator

         Organization  Network Solutions, Inc.
         Name          Lastname, Firstname
         Title         Principal Investigator
         Mail Address  Network Solutions, Inc.
                       505 Huntmar Park Drive           
                       Herndon, VA 22090 
         Phone Number  (XXX) XXX-XXXX
         Net Mailbox   pi@INTERNIC.NET 
         NIC Handle    BB34 

   2) The name, title, mailing address, phone number, and organization of the 
technical contact.  The on-line mailbox and NIC Handle (if any) of the 
technical contact should also be included.  This is the contact point for 
problems with the autonomous system and for updating information about the 
autonomous system.

Also, the technical contact may be held responsible for the behavior of 
gateways in this autonomous system.

      Example:
  
         Technical Contact

            Organization  Network Solutions, Inc.
            Name          Lastname, Firstname
            Title         Computer Scientist
            Mail Address  Network Solutions         
                          505 Huntmar Park Drive          
                          Herndon, VA  22070 
            Phone Number  (XXX) XXX-XXXX
            Net Mailbox   cs@INTERNIC.NET 
            NIC Handle    CC56

3) The name of the autonomous system (up to 12 characters).  This is the name 
that will be used in tables and lists associating autonomous systems and 
numbers.

      Example: ALPHA-BETA

4) A description of the gateway that implements the inter-autonomous system 
protocol for interaction with other autonomous systems. Currently the 
exterior gateway protocol (EGP) is being used for this purpose (RFC 904).  
This gateway should comply with RFC 1009, Requirements for Internet Gateways.

Example: This is a new gateway developed by the XYZ Group at the ABC 
Corporation.

      or

Example: This is an instance of the well known IJK company gateway, but set 
up as a distinct autonomous system.

5) A description of the gateway hardware, including CPU and interfaces.

Example: DEC PDP-11/23, ARPANET Interface by ACC, Ethernet Interfaces by 3COM.

6) A description of the gateway software, including operating system and 
languages.

Example: The gateway is implemented using language "C" and runs Berkeley 4.2 
Unix.

7) The deployment schedule for the autonomous system.
         (a) initially,
         (b) within one year,
         (c) two years, and
         (d) five years.

            Example:

            (a) initially  =   1
            (b) one year   =   3
            (c) two years  =   5
            (d) five years =  10

8) What networks will be interconnected by these gateways?  What are the 
internet addresses of each gateway?

Example: One gateway, interconnecting BNET and LEWIS-PRNET2, with address 
192.8.15.3 on BNET  and 128.108.12.10 on LEWIS-PRNET2.


For further information contact Registration Services. 


              Via electronic mail:  HOSTMASTER@INTERNIC.NET 
              Via telephone:        1-800-444-4345  
              Via postal mail:      InterNIC Registration Services
                                    505 Huntmar Park Drive
                                    Herndon, VA 22070
------------------------------------------------------------------------




************************************************************************
                              APPENDIX E:
************************************************************************

IN-ADDR.ARPA REGISTRATION

[netinfo/in-addr-template.txt]                         [ 04/93 ]


The Internet uses a special domain to support gateway location and Internet 
address to host mapping.  The intent of this domain is to provide a 
guaranteed method to perform host address to host name mapping, and to 
facilitate queries to locate all gateways on a particular network in the 
Internet.

The following information is needed for delegation of registered networks in 
your domain for inclusion in the IN-ADDR.ARPA zone files:

        * the IN-ADDR.ARPA domain
        * the Network name
        * the Hostnames of the two hosts on networks
           that will be acting as IN-ADDR servers

IN-ADDR domains are represented using the network number in reverse.  For 
example, network 123.45.67.0's IN-ADDR domain is represented as 67.45.123.IN-
ADDR.ARPA.

        For example:

        IN-ADDR domain        Network Name     IN-ADDR Servers
                                               (Hostname)
                                               (NetAddress)
                                               (CPUType/OpSys)

        41.192.IN-ADDR.ARPA   NET-TEST-ONE     BAR.FOO.EDU
                                               123.45.67.89
                                               VAX-II/VMS
                                               ONE.ABC.COM
                                               98.76.54.32
                                               SUN/UNIX

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

NOTE: Unless specified, new hosts registered as IN-ADDR servers will be
registered in the root servers only and will not appear in the HOSTS.TXT file.


Please have the Network Coordinator complete and return the following
information for those networks needing IN-ADDR registration.



         IN-ADDR domain        Network Name    IN-ADDR Servers
         ==============        ============    ===============





- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Completed templates and questions can be directed to Hostmaster at
HOSTMASTER@INTERNIC.NET, or faxed/mailed to:

                                Mr. Robert Castelli
                                Sprint
                                13221 Woodland Park Road
                                Herndon, VA 22071

                                Fax: 703-904-2252
                                Tel: 703-904-2453

                                ATTN:  IN-ADDR.ARPA Request

Or, mail paper copy to:

        Network Solutions 
        INTERNIC Registration Service 
        505 Huntmar Park Drive  
        Herndon, VA 22070                


---------------------------------------------------------------------




************************************************************************
                              APPENDIX F:
************************************************************************

INTERNIC WHOIS REGISTRATION

This is the new WHOIS user template.  Please read all instructions carefully 
and do not make any changes to the template itself!  Please address comments 
and questions to registrar@nic.ddn.mil.

[ templates/user-template.txt ]                 [ Version U1.2  9/92 ]

This file contains information for individual users and for Host 
Administrators (HAs) who want to register their users in the WHOIS database 
maintained by the INTERNIC Registration Services  on the host RS.INTERNIC.NET 
(198.41.0.5).The user registration template below has been created to 
standardize the registration procedure and help ensure that Registration 
Services will receive complete information about each user in a format that 
can be processed quickly and reliably by the registration software.  You may 
retrieve the file from Registration Services  NIC via FTP.  Simply log on 
with username "anonymous" and password "guest".  Then change to the templates 
directory and request the file by executing a getfile procedure for filename 
user-template.txt at the prompt. 

The file contains five sections, as follows:

     A.  General Instructions
     B.  Instructions for Individual Field Entries
     C.  Instructions for Submitting Registration Data
     D.  Sample Template
     E.  Blank Template (Use for Submission) 
 
Section A below provides general instructions for filling out the user 
templates.  Acceptable formats and instructions for individual field entries 
follow in Section B.  PLEASE READ ALL INSTRUCTIONS CAREFULLY.


HOW TO FILL IN THE USER REGISTRATION TEMPLATE

A.  General Instructions

NOTE: UPDATEs and DELETEs *always* require the entry of a NIC handle and Last 
Name.

1. To ADD a new user record to the database, fill out all required fields 
except for the handle, line U1.  Required fields are marked with a plus (+).  
Include in the non-required fields any additional information that is 
applicable to the new user.

2. To MODIFY or UPDATE the record of an existing user, enter the appropriate 
NIC handle and include data for the fields that need to be changed.  Enter 
"NONE" in any non-required field to erase previous data. 

U3A through U3D are grouped fields. Each of these fields are processed as a 
whole.  A change to any one field within the group requires entries of all 
fields for the group.  (i.e., entry in any field causes all fields in the 
group to be updated from the template.) 

3. To DELETE a user record from the database, enter the NIC handle (U1), 
enter the name information (U2A and U2B), and enter "Y" in the "Delete  
User?" field (U5A).

4. City, State, and Zip code information must be supplied for all United 
States addresses.  If the address is an APO or FPO address, use the City 
field to specify the letters "APO" or "FPO" and use the State field to enter 
the APO/FPO two-letter code.

5. Please note that NO USER is allowed more that one record in the NIC 
database.  Each user should be registered only on his/her primary or "home" 
host. 


B.  Instructions for Individual Field Entries

+  U1. NIC Handle (See A2,3)......:

Required only for UPDATEs and DELETEs.  DO NOT include a handle when you are 
registering a new user.  The NIC registration software automatically 
generates a handle for all user records that are newly added to the database. 
Example:  RM64 (handle for NIC.DDN.MIL user)

NAME INFORMATION
+  U2A. Last Name..................:
+  U2B. First Name.................:
   U2C. Middle Name or Initial.....:
   U2D. Name Suffix................:
   U2E. Title/Rank.................:

Both first and last names are required.  We strongly suggest including a 
middle name or initial, as that helps to eliminate duplication of names in 
the database.  Suffix line should include identifiers such as Jr., Sr.,II, 
III, etc. A title or rank may be included.

ADDRESS INFORMATION
+  U3A. Address Line 1.............:
   U3B. Address Line 2.............:
   U3C. Address Line 3.............:
   U3D. Address Line 4.............:
+  U3E. City or FPO/APO (See A.4)..:
+  U3F. State or FPO/APO Code (A.4):
+  U3G. Zip Code (See A.4).........:
   U3H. Country....................:
   U3I. Network Mailbox............:
+  U3J. Hostname...................:

Required. At least one line of address information is required.  This address 
should be the U.S. postal mailing address for any correspondence directed to 
you.  Enter as many lines as necessary, up to a maximum of four.
 
Enter the city and the standard two-letter state abbreviation if your host is 
located in the United States. If you have an APO/FPO address, enter only the 
two-letter APO/FPO code in line U3F (i.e., AE for New York, AP for 
California, AA for Florida).
 
The zip code entry is REQUIRED for APO/FPO and U.S. mailing addresses.  
Please supply a nine-digit zip code for APO/FPO addresses; you may enter 
either a five or nine-digit zip for other U.S. addresses.
 
U3H. Country....................:
Enter the country if it should appear in your mailing address.

U3I. Network Mailbox............: 
Enter the Fully Qualified Domain Name (full hostname).  Separate the username 
and hostname parts of the mailbox by "@".  Otherwise, follow the syntax 
required for routing mail to your network.

+  U3J. Hostname...................:

This is the name of your "home" host.  Enter the full hostname, not the 
numeric host address.

PHONE INFORMATION
+  U4A. Commercial Phone...........:
   U4B. Commercial Phone Extension.:
   U4C. Alternate Phone............:
   U4D. Alternate Phone Extension..:
   U4G. Fax Phone..................:

Each user must provide at least one phone number.  Other numbers may also be 
listed.  Please include a Fax number.

USER STATUS
U5A. Delete User? (See A.3)[Y/N]: 

This field is used to permanently remove a user's record from the WHOIS 
database.  Do not answer "Y" if the user is moving to another host.  The 
default is N.

C.  Instructions for Submitting Registration Data

Please forward all user registration data directly to 
"REGISTRAR@NIC.DDN.MIL".  You may address questions to the same mailbox or 
you may call the NIC Help Desk at 1-800-365-DNIC for assistance.  All 
submissions will be acknowledged on receipt.  User registrations will be 
processed within eight working days of receipt if all data is properly 
formatted and there are no problems with the information you have supplied.

If you do not have access to electronic mail facilities, you may fax/mail to:

                                Mr. Robert Castelli
                                Sprint
                                13221 Woodland Park Road
                                Herndon, VA 22071

                                Fax: 703-904-2252
                                Tel: 703-904-2453

                                ATTN:  INTERNIC WHOIS REGISTRATION Request

Or, mail hard copy applications to the following address:

     Network Information Center
     14200 Park Meadow Drive
     ATTN:  Registrar, Suite 200
     Chantilly, VA  22021
 
Because hard copy registrations require manual input, this method of
transmission is strongly discouraged!

The following section consists of a sample template with data entered in the 
required format.  A blank user template concludes the file. 
 


D.  Sample Template

---------------------------------------------------------------
Sample User Registration Template Version U1.2 - 9/92
----------------------------------------------------------------
Do Not Change Format!              |        Enter Data Here
----------------------------------------------------------------
+  U1. NIC Handle (See A2,3).......: XYZ23
NAME INFORMATION
+  U2A. Last Name..................: Zosters
+  U2B. First Name.................: Xary
   U2C. Middle Name or Initial.....: Y.
   U2D. Name Suffix................:
   U2E. Title/Rank.................:
ADDRESS INFORMATION
+  U3A. Address Line 1.............: Fictitious Solutions, Inc.
   U3B. Address Line 2.............: 505 Huntmar Dr.
   U3C. Address Line 3.............:
   U3D. Address Line 4.............:
+  U3E. City or FPO/APO (See A.4)..: Imaginary
+  U3F. State or FPO/APO Code (A.4): VA
+  U3G. Zip Code (See A.4).........: 22079
   U3H. Country....................: USA
   U3I. Network Mailbox............: xyz@nic.ddn.mil
+  U3J. Hostname...................: NIC.DDN.MIL
PHONE INFORMATION
+  U4A. Commercial Phone...........: 1-703-999-8484
   U4B. Commercial Phone Extension.: 1134
   U4C. Alternate Phone............:
   U4D. Alternate Phone Extension..:
   U4G. Fax Phone..................:
USER STATUS
   U5A. Delete User? (See A.3)[Y/N]: 
----------------------------------------------------------------


E.  Blank Template (Use for Submission) 

<<<<<<<<<<<<<<<<<<<<<<<< CUT HERE >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
-----------------------------------------------------------------
User Registration Template Version U1.2 - 9/92
-----------------------------------------------------------------
Do Not Change Format!              |        Enter Data Here
-----------------------------------------------------------------
+  U1. NIC Handle (See A.2,3)......: 
NAME INFORMATION
+  U2A. Last Name..................:
+  U2B. First Name.................:
   U2C. Middle Name or Initial.....:
   U2D. Name Suffix................:
   U2E. Title/Rank.................:
ADDRESS INFORMATION
+  U3A. Address Line 1.............:
   U3B. Address Line 2.............:
   U3C. Address Line 3.............:
   U3D. Address Line 4.............:
+  U3E. City or FPO/APO (See A.4)..: 
+  U3F. State or FPO/APO Code (A.4):
+  U3G. Zip Code (See A.4).........:
   U3H. Country....................:
   U3I. Network Mailbox............:
+  U3J. Hostname...................:
PHONE INFORMATION
+  U4A. Commercial Phone...........: 
   U4B. Commercial Phone Extension.:
   U4C. Alternate Phone............:
   U4D. Alternate Phone Extension..:
   U4G. Fax Phone..................:
USER STATUS
   U5A. Delete User? (See A.3)[Y/N]:
------------------------------------------------------------------------




************************************************************************
                              APPENDIX G:
************************************************************************

SPRINTLINK TERMS AND CONDITIONS

The Following terms and conditions govern Sprint's provision of SprintLink 
Products and Services ('Products and Service') to Customer.  The Term 
'Products and Services' is limited to the equipment, facilities, programming 
or software provided by Sprint to facilitate SprintLink Services but does not 
include special access lines which may be utilized with the SprintLink 
Services.  If Products and Services are or become subject to a tariff filed 
with the Federal Communications Commission or any other regulatory 
institution ('Tariff'), the terms and conditions of such Tariff, including 
rates, shall govern Customer's use of the Products and Services.

1.  Term
The initial Term begins on the first day of the month following Sprint's 
installation of equipment of facilities, or acceptance of previously 
installed equipment or facilities, according to Sprint's then current policy.  
The Term for Products and Services ('Term') will be stated on the SprintLink 
Order for Data Communications Services ('Order') and shall automatically 
renew for successive ninety (90) day Terms, regardless of the Term of the 
original Order, unless (1) Customer or Sprint notifies the other by thirty 
(30) days written notice that it does not wish to renew, or (2) Customer 
renews a long-term Order for the same or a different Term by executing a new 
Order no less than thirty (30) days prior to the end of the current Term, or 
(3) Customer converts an automatic renewal Term to a Long-Term Order by 
executing a new Order.  A 'Long-Term' Order is one whose Term is one year or 
longer.

2.  Rates
Rates are as set forth on Customer's Order, Sprint will provide sixty (60) 
days' written notice of increase in base prices.  In the event of increases 
in base prices, Customer has Fourteen (14) days from the date of the 
effective increase to provide Sprint Contracts Administration with a written 
request to terminate service and incur no termination liability.  Otherwise, 
Customer's existing Orders will be billed according to the new base prices. 
Customer will be responsible for all charges for up to thirty (30) days from 
the date notice is received.

Discount percentages, if applicable, are fixed for Long-Term Orders.  For all 
other Orders and upon renewal of Long-Term Orders, the discount percentage(s) 
are subject to change upon sixty (60) days prior written notice. 

3.  Payment
Customer agrees to pay all charges incurred.  Charges shall be invoiced 
monthly and payment in US currency shall be due upon receipt.  Interest 
charges of 1 3/4 percent per month or the highest rate permitted by law will 
accrue daily on all amounts not paid within thirty (30) days of the date of 
the invoice.  Customer will pay all sales and use taxes, as well as duties or 
levies, on Products and Services.  Customer agrees to pay all charges 
according to Sprint's then current Cancel Before start Policy and Billing 
Initiation Policy.

4.  Termination
To terminate Products and Services, Customer must provide Sprint with thirty 
(30) days prior written notice.  In the event of early termination of any 
Long-Term Order, Customer will pay a lump sum equal to one hundred percent 
(100%) of the monthly base price for each service terminated for the 
unexpired portion of the Term's first year plus fifty percent (50%) of the 
monthly base price for each service terminated for each month remaining in 
the Term. Customer will not be liable for termination charges if Products and 
Services of the same or greater monthly base price and term is ordered at the 
same time as the notice of termination is received.

5.  Rights and Obligations of Customer

  A. Customer shall at its own expense provide all necessary   
  preparations required to comply with Sprint's installation and 
  maintenance specifications, shall be responsible for the costs of 
  relocation of Products and Services once installed by Sprint, and 
  shall provide to Sprint and to suppliers of communications lines 
  reasonable access to Customer's premises to perform any acts required  
  by this Agreement.

  B. Customer shall properly use equipment provided by Sprint and shall 
  surrender the equipment to Sprint upon termination. Customer shall be 

  liable for damages to Products and Services caused by the negligence 
  or willful acts of Customer's officers, employees, agents or  
  contractors for loss through theft or vandalism of Products and 
  Services on Customer's premises, and for damages caused by the use of 
  equipment or supplies not provided by Sprint.

  C. Customer shall neither permit or assist others to use Products and 
  Services for any purpose other than that for which they are intended; 
  fail to maintain a suitable environment as specified by Sprint; or 
  alter, tamper with, adjust or repair the Products and Services.  In 
  the event of such alterations, tampering, adjustments or repairs by 
  Customer, Sprint shall be completely released from any liability or 
  obligation (including any warranty or indemnity obligation) to 
  Customer relative to the Products and Services; and Customer shall be 
  liable to Sprint for costs or damages incurred by Sprint.

  D. Customer shall not nor shall it permit or assist others to abuse or 
  fraudulently use Products and Services, including but not limited to 
  the following:

    1. Obtaining or attempting to obtain service by any fraudulent means  
    or device with intent to avoid payment;

    2. Accessing, altering, or destroying any information of another 
    Sprint Customer by any raudulent means or device, or attempting to 
    do so; or

    3. Using Products and Services so as to interfere with the use of 
    the Sprint network by other customers or authorized users; or in 
    violation of the law or in aid of any unlawful act.

6.  Equipment or Software not Provided by Sprint

  A. Sprint shall not be responsible for the installation, operation or     
  maintenance of equipment or software not provided by Sprint; nor shall 
  Sprint be responsible for the transmission or reception of information 
  by equipment or software not provided by Sprint. 

  B. Customer shall be responsible for the use and compatibility of  
  equipment or software not provided by Sprint.  In the event that 
  Customer uses equipment or software not provided by Sprint which  
  impairs the Customer's use of Products and Services, Customer shall  
  nonetheless be liable for payment for Products and Services.  Upon  
  notice from Sprint that the equipment or software not provided 
  by Sprint is causing or is likely to cause hazard, interferences or 
  service obstruction, Customer shall eliminate the likelihood of 
  hazard, interference or service obstruction.  Customer shall if 
  necessary pay Sprint to troubleshoot difficulties caused by equipment 
  or software not provided by Sprint. 

  C. Sprint shall not be responsible if any changes in Products and 
  Services cause equipment or hardware not provided by Sprint to become  
  obsolete, require modification or alteration, or otherwise affect  
  performance of equipment or hardware not provided by Sprint.

  D. The following terms apply specifically to scenarios where the 
  customer provides the router that will interface to SprintLink. Sprint  
  includes the terms and conditions so that Sprint can control the 
  performance of SprintLink on an end-to-end basis and protect the 
  SprintLink network.  Sprint's intent is to manage the router on a 
  cooperative basis with the customer.

    1. Sprint reserves the right to allow or refuse the make, model and 
    or software revision of customer-provided router to be used as the 
    gateway to SprintLink.

    2. Sprint and the customer will cooperatively set the initial 
    configuration for the router's interface into SprintLink.

    3. The customer must permit Sprint to access the router's SNMP 
    variables, and the customer must, at Sprint's request, permit one or 
    more Sprint network management systems to be the recipient of SNMP 
    TRAP messages.

    4. The customer must offer Sprint read/write access to the router's 
    configuration tables.  Either the customer or Sprint can administer 

    the access controls (i.e., login and password) to the router's 
    configuration editor.  Sprint will only modify that part of the 
    router's configuration which controls the interface into the 
    SprintLink network.
                
7.  Rights and Obligations of Sprint
   A. Sprint shall install, operate and maintain Products and Services.  
   Sprint shall not be responsible for cabling that connects equipment 
   not provided by Sprint to Sprint Products and Services.

   B. Sprint warrants that Products and Services will be in good working 
   order and will conform to Sprint's service specifications upon the 
   date installed.

   THE FOREGOING WARRANTIES ARE IN LIEU OF ALL OTHER WARRANTIES, EXPRESS 
   OR IMPLIED, INCLUDING BUT NOT  LIMITED TO THE IMPLIED WARRANTIES OF 
   MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

   C.  Customer's sole remedy for performance or non-performance of 
   Products and Services pursuant to Sprint's service specifications 
   shall be repair or replacement of the Products and Services.

   D.    Sprint shall not be liable, either in contract or in tort, for 
   protection from unauthorized access of Customer's transmission 
   facilities or Customer premise equipment; or for unauthorized access 
   to or alteration, theft or destruction of Customer's data files, 
   programs, procedure or information through accident, fraudulent means 
   or devices, or any other method, even should such access occurs as a 
   result of Sprint's negligence.

   E. Sprint shall not be liable for claims or damages caused by 
   Customer's fault, negligence or failure to perform Customer's 
   responsibilities; claims against Customer by any other party; any act 
   or omission of any other party furnishing products or services; or 
   installation or removal of equipment furnished by any service 
   provider or Sprint, except where caused by the gross negligence of 
   Sprint.

   F.  For any other claim, Customer's damages, if any, shall be limited 
   to those actually proven as directly attributable to Sprint, subject 
   to the following limitation:  Sprint will not be liable under any 
   circumstances for any lost profits or other consequential damages, 
   even if Sprint has been advised of the possibility of such damages. 
   Sprint's  liability for damages to Customer for any cause whatsoever, 
   regardless of the form of action, and whether in contract or in tort, 
   including negligence, shall be limited to the lesser of $100,000 or 
   the monthly charges paid for Products and Services from the date   
   damages were incurred, but in no event more than twelve (12) month's 
   charges for the Products and Services that cause the damage

   G.  Upon default by Customer, Sprint may terminate Products and 
   Services and retake possession of Products and Services (before, 
   during or after action to recover sums hereunder), in which case 
   Customer shall provide Sprint full and free access to Products and 
   Services for this purpose, retain all payments made hereunder, and 
   recover charges and costs owed by Customer as well as any other 
   damages Sprint may have sustained because of Customer's default.  
   'Default' shall mean where Customer becomes subject of a voluntary or 
   involuntary bankruptcy, insolvency, reorganization or liquidation 
   proceeding; makes an assignment for the benefit of creditors; admits 
   in writing its inability to pay debts when due; or fails within ten  
   (10) days after written notice to remedy any breach of these Terms 
   and Conditions.

8. Proprietary Rights and Information Protection
   A.  Where Customer utilizes Products and Services containing 
   programming or software.  Sprint grants to Customer a non-exclusive 
   and non-transferable license to use such programming or software for 
   the sole purpose of enabling Customer to use such Products and 
   Services.

   B.  Title and property rights including all intellectual property  

   rights to Products and Services are and shall remain with Sprint, 
   whether or not embedded in the programming or software. 

   C.  Customer recognizes that Products and Services, programming and 
   software used hereunder constitute valuable trade secrets of Sprint.  
   Customer shall use its best efforts to protect and keep confidential 
   all programming and software used by it and shall make no attempt to 
   examine, copy, alter, reverse engineer, tamper with, or otherwise 
   misuse such Products and Services programming and software.

9. Indemnities 
   A. If promptly notified in writing of any action brought against 
   Customer based on a claim that Products and Services used by Customer 
   infringes a United States patent or copyright, Sprint will defend 
   such action at its expense and will pay any and all fees, costs or 
   damages that may be finally awarded in such action or resulting 
   settlement.  In the event that a final injunction is obtained against 
   Customer prohibiting use of Products and Services of any part thereby 
   by reason of infringement of a United States patent or copyright, 
   Sprint will at its option either:

      1.  At its expense, procure the right for Customer to continue 
      using the Products and Services: or

      2.  Procure alternative Products and Services which furnish the 
      same or similar functionality; or 

      3.  Direct Customer to return such Products and Services to Sprint 
      at Sprint's expense, and in such  event, the Order relating to 
      such returned Products and Services shall terminate and any 
      prepaid charges will be refunded to Customer.

   B.   Sprint will be indemnified and saved harmless by the Customer from 
   and against all loss, liability, damage and expense, including  
   reasonable counsel fees, caused by:

      1.  Negligent acts or omissions of officers, employees, agents or       
      contractors of Customer which  arise out of or are caused by the  
      construction, installation, maintenance, presence, use or removal
      of systems, channels or terminal equipment or software not
      provided by Sprint which are connected or are to be connected to 
      Sprint Products and Services and which result in claims and 
      demands for damages to property or for injury or death to persons 
      including payments made under any Worker's Compensation Law or 
      under any plan for employee's disability or death benefits:
        
      2. Claims for liable, slander, invasion of privacy of infringement 
      of copyright, and invasion and/or alteration of private records or 
      data arising from any information, data or message transmitted 
      over the network by Customer, and

      3. Claims for infringement of patents arising from the use of 
      equipment and software, apparatus and systems not provided by 
      Sprint in connection with Products and Services.

10. General 
   A. Customer shall not assign or transfer the Order without the prior 
   written consent of Sprint.  Sprint may however assign this Agreement 
   to its parent company or an affiliate with 30 days notice.

   B. Sprint will not be responsible for performance of its obligations 



From tdunk@icm1.icp.net Wed Sep  1 15:03:20 1993
Received: from icm1.icp.net by fido.wps.com (5.67/wps.com-hackery)
	id AA21669; Wed, 1 Sep 93 15:03:12 -0700
Received: from [144.224.5.45] by icm1.icp.net (5.65/1.34)
	id AA00182; Wed, 1 Sep 93 18:05:10 -0500
X-Mailer: InterCon TCP/Connect II 1.1
Message-Id: <9309011805.AA06459@Tom Dunkenberger.icm1.icp.net>
Date: Wed,  1 Sep 1993 18:05:06 -0500
From: Tom Dunkenberger <tdunk@icm1.icp.net>
To: tomj@wps.com
Cc: tdunk@icm1.icp.net, syoung@icm1.icp.net, rcollet@icm1.icp.net,
        /dd.un=m.cravens/o=us.sprint/admd=telemail/c=us/@sprint.com,
        /dd.un=d.stevens/o=us.sprint/admd=telemail/c=us/@sprint.com
Subject: RGnet Proposal - Appendices (2 of 2) (part 2 of 2)
Status: OR

   hereunder where delayed or hindered by war, riots, embargoes, strikes 
   or other concealed acts of workmen (whether of Sprint or others), 
   casualties, accidents or other occurrences beyond Sprint's control  
   Sprint shall notify Customer in the event of any of the foregoing 
   occurrences.  Should such occurrence continue for more than sixty 
   (60) days, Sprint or Customer may cancel the Order for the affected 
   Products and Services with no further liability.

   C. The provision of Products and  Services by  Sprint is subject to 
   Sprint's continuing approval of Customer's credit-worthiness.  
   Customer shall furnish financial information as Sprint may from time
   to time request to determine Customer's credit-worthiness.


   D. Any legal action arising out of failure, malfunction or defect in 
   Products and Services shall be brought within one (1) year of the 
   occurrence or is deemed waived.

   E. These Terms and Conditions may not be modified except by written 
   amendment by the parties.  No agent, employee or representative of 
   Sprint or Customer has authority to bind the parties to any 
   representation or warranty unless such is specifically included in 
   these Terms and Conditions, the Order, or written amendments thereto.

   F.  Notice to the parties of disputes arising under this Agreement 
   shall be sent by registered mail to the parties to the address shown 
   on the most recent Order.  All other notices may be sent by regular 
   mail.  Notice to Sprint shall be to:

    Sprint
    13221 Woodland Park Road
    Herndon, Virginia   22071
    Attention: Contracts Administration

   G.  All orders subject to Acceptable Use Policy attached to this 
   Agreement.

   H.  This Agreement shall be governed by the laws of the State of 
   Kansas.


CUSTOMERS WHO REQUEST TO HAVE THEIR NETWORK ANNOUNCED TO THE NSFNET MUST 
COMPLY WITH THE FOLLOWING NSFNET ACCEPTABLE USAGE POLICY.



