[ NETINFO:INTERNET-NUMBER-TEMPLATE.TXT ] [4/90, LM] 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 EJ210 333 Ravenswood Avenue Menlo Park, CA 94025 1) If the network will be connected to the Internet, you must provide the name of the 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), Defense Advanced Research Projects Agency (DARPA), 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 administrative POC for the network requesting the number. This is the POC for administrative and policy questions about the network itself. If the network is associated with a research project this POC should be the Principal Investigator of the project. The online mailbox and NIC Handle (if any) of this person should also be included. 2a. NIC handle (if known): 2b. Administrator name (Lastname, Firstname): 2c. Administrator title: 2d. Mail address : 2e. Phone : 2f. Net Mailbox : 3) 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. 3a. NIC handle (if known): 3b. Technical POC name (Lastname, Firstname): 3c. Technical POC title: 3d. Mail address : 3e. Phone : 3f. Net Mailbox : 4) 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. 4. Network name: 5) Identify the network geographic location and the responsible organization establishing the network. 5a. Geographical address: 5b. Name of Organization: 6) Provide a citation to a document that describes the technical aspects of the network. If the document is online, give a pathname suitable for online retrieval. 6. Citation: 7) Gateway information required: If the network is to be connected to the Internet, answer questions 7a and 7b. 7a) Describe the Gateway that connects the new network to the Internet, and the date it will be operational. The gateway must be either a core gateway supplied and operated by BBN, or a gateway of another Autonomous System. If this gateway is not a core gateway, then an identifiable gateway in this gateway's Autonomous System must exchange routing information with a known core gateway via EGP. A good way to answer this question is to say "Our gateway is supplied by person or company X and does whatever their standard issue gateway does". 7a. Gateway description: 7b) Describe the gateway machine, including: 7b. Hardware: 7c. Network address: 7d. Software: 8) Estimate the number of hosts that will be on the network: 8a. Initially: 8b. Within one year: 8c. Within two years: 8d. Within five years: 9) 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]) 9. Reason: 10) Networks are characterized as being either Research, Defense, Government - Non Defense, or Commercial, and the network address space is shared between these three areas. Which type is this network? 10. Type of network: 11) What is the purpose of the network? 11. Purpose: PLEASE ALLOW AT LEAST 10 WORKING DAYS FOR PROCESSING THIS APPLICATION For further information contact the DDN/ARPANET 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 EJ210 Menlo Park, CA 94025 RECOMMENDED READING (available from the NIC) 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; 219 p. AD A214 698. Dorio, N.; Johnson, M.; Lederman, S.; Redfield, E.; Ward, C.A., eds. DDN Protocol Implementations and Vendors Guide. Menlo Park, CA: SRI International, DDN Network Information Center; 1989 February; NIC 50002 (February 1989). 386 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). 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). Romano, S.; Stahl, M.K.; Recker, M. Internet Numbers. Menlo Park, CA: SRI International, DDN Network Information Center; 1989 August; RFC 1117. 109 p. (NIC.DDN.MIL RFC:RFC1117.TXT).