.fo off

.bf x0mira

Received: (from CUNYVM.BITNET for <SERVICE-REPLY@NIC.DDN.MIL> via BSMTP)

Received: (from MAILER@CUNYVMV2 for MAILER@YUBGSS21 via NJE)

 (UCLA/Mail V1.410 M-MAILER-9002-219); Mon, 08 Jul 91 13:51:38 GMT

Received: from CUNYVM by CUNYVM.BITNET (Mailer R2.07) with BSMTP id 4657; Mon,

 08 Jul 91 07:47:16 EDT

Received: from NIC.DDN.MIL by CUNYVM.CUNY.EDU (IBM VM SMTP R1.2.2MX) with TCP;

 Mon, 08 Jul 91 07:47:14 EDT

Date: Mon,  8 Jul 91 04:16:36 PST

From: "SRI-NIC Mail Service 2.4(319)-1" <SERVICE-REPLY@NIC.DDN.MIL>

To: Mirjana Tasic +38-11-419-895

 <SYSTEM3%YUBGSS21.BITNET@CUNYVM.CUNY.EDU>

Subject: re: INTERNET-NUMBER-TEMPLATE.TXT

 

[ NETINFO:INTERNET-NUMBER-TEMPLATE.TXT ]                        [7/90, SK]

 

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 online, via

electronic mail, to HOSTMASTER@NIC.DDN.MIL.  If electronic mail is not

available to you, please mail hardcopy to:

 

			DDN Network Information Center

			SRI International

			Room EJ286

			333 Ravenswood Avenue

			Menlo Park, CA 94025

 

Once the NIC receives your completed application we will send you an

acknowledgement, via electronic or postal mail.  PLEASE ALLOW AT LEAST 8

WORKING DAYS FOR PROCESSING YOUR REQUEST.

 

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@NIC.DDN.MIL or phone the NIC at (800) 235-3155 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: Defense

Communications Agency (DCA), the National Science Foundation (NSF), or

similar military or government sponsors.

 

NOTE: If the network will NOT be connected to the 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 online 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) Question #5 is for MILITARY or DOD requests, ONLY.

 

If you require that this connected network be announced to the NSFNET

please answer questions 5a, 5b, and 5c.

 

5a.  Do you want MILNET to announce your network to the NSFNET? (Y/N):

 

5b.  Do you have an alternate connection, other than MILNET, to the

NSFNET?  (please state alternate connection if answer is yes):

 

 

 

5c.  If you've answered yes to 5b, please state if you would like the

MILNET connection to act as a backup path to the NSFNET? (Y/N):

 

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:

 

PLEASE ALLOW AT LEAST 8 WORKING DAYS FOR PROCESSING THIS APPLICATION

 

For further information contact the DDN Network Information

Center (NIC):

 

      Via electronic mail:  HOSTMASTER@NIC.DDN.MIL

      Via telephone:        (800) 235-3155

      Via postal mail:      SRI International

			    DDN Network Information Center

			    333 Ravenswood Avenue

			    EJ286

			    Menlo Park, CA 94025

 

 

  	      RECOMMENDED READING (available from the NIC)

 

Bjork, S.; Marine, A., eds.  Network Protocol Implementations and

  Vendors Guide. Menlo Park, CA: SRI International, DDN Network

  Information Center; 1990 August; NIC 50002 (August 1990). 242 p.

  (NIC.DDN.MIL NETINFO:VENDORS-GUIDE.DOC).

 

Braden, R.T.; Postel, J.B.  Requirements for Internet Gateways. Marina

  del Rey, CA: University of Southern California, Information Sciences

  Inst.; 1987 June; RFC 1009. 55 p. (NIC.DDN.MIL  RFC:RFC1009.TXT).

 

Defense Advanced Research Projects Agency, Internet Activities Board.

  IAB Official Protocol Standards.  1991 April; RFC 1200.  31 p.

  (NIC.DDN.MIL  RFC:RFC1200.TXT).

 

Feinler, E.J.; Jacobsen, O.J.; Stahl, M.K.; Ward, C.A., eds.  DDN

  Protocol Handbook: Menlo Park, CA: SRI International, DDN Network

  Information Center; 1985 December; NIC 50004 and NIC 50005 and NIC

  50006. 2749 p.

 

Garcia-Luna-Aceves, J.J.; Stahl, M.K.; Ward, C.A., eds.  Internet

  Protocol Handbook: The Domain Name System (DNS) Handbook. Menlo Park,

  CA: SRI International, Network Information Systems Center; 1989

  August; NIC 50007. 219 p. AD A214 698.

 

Kirkpatrick, S.; Stahl, M.K.; Recker, M.  Internet Numbers. Menlo Park, CA:

  SRI International, DDN Network Information Center; 1990 July; RFC

  1166. 182 p. (NIC.DDN.MIL  RFC:RFC1166.TXT).

 

Mogul, J.; Postel, J.B.  Internet Standard Subnetting Procedure.

  Stanford, CA: Stanford University; 1985 August; RFC 950. 18 p.

  (NIC.DDN.MIL  RFC:RFC950.TXT).

 

Postel, J.B.  Internet Control Message Protocol. Marina del Rey, CA:

  University of Southern California, Information Sciences Inst.; 1981

  September; RFC 792. 21 p. (NIC.DDN.MIL  RFC:RFC792.TXT).

 

Postel, J.B.  Transmission Control Protocol. Marina del Rey, CA:

  University of Southern California, Information Sciences Inst.; 1981

  September; RFC 793. 85 p. (NIC.DDN.MIL  RFC:RFC793.TXT).

 

Postel, J.B.  Address Mappings. Marina del Rey, CA: University of

  Southern California, Information Sciences Inst.; 1981 September; RFC

  796. 7 p. (NIC.DDN.MIL  RFC:RFC796.TXT).

    Obsoletes: IEN 115 (NACC 0968-79)

 

Postel, J.B.  User Datagram Protocol. Marina del Rey, CA: University

  of Southern California, Information Sciences Inst.; 1980 August 28;

  RFC 768. 3 p. (NIC.DDN.MIL  RFC:RFC768.TXT).

 

Postel, J.B.  Internet Protocol. Marina del Rey, CA: University of

  Southern California, Information Sciences Inst.; 1981 September; RFC

  791. 45 p. (NIC.DDN.MIL  RFC:RFC791.TXT).

 

Reynolds, J.K.; Postel, J.B.  Assigned Numbers. Marina del Rey, CA:

  University of Southern California, Information Sciences Inst.; 1990

  March; RFC 1060. 86 p. (NIC.DDN.MIL  RFC:RFC1060.TXT).

 

Reynolds, J.K.; Postel, J.B.  Official Internet Protocols. Marina del

  Rey, CA: University of Southern California, Information Sciences

  Inst.; 1987 May; RFC 1011. 52 p. (NIC.DDN.MIL  RFC:RFC1011.TXT).

 

 

