[URL ftp://rs.internic.net/templates/internet-number-template.txt ] [08/95] ********************** PLEASE DO NOT REMOVE Version Number ******************** Network Version Number: 2.0 ****************** Please see attached detailed instructions ****************** 1a. Approximate date of Internet connection.....................: 1b. Name of Internet access provider (if known)............: Technical POC 2a. NIC handle (if known)..........: 2b. Name (Last, First).............: 2c. Title..........................: 2d. Postal address.................: 2e. Phone Number...................: 2f. E-Mailbox......................: 3. Network name...................: 4a. Name of Organization...........: 4b. Postal address of Organization.: 5. Previously assigned addresses..: Explain how addresses have been utilized, to include: 5a. Number of hosts.................: 5b. Number of subnets...............: 5c. Subnet mask.....................: Justification Host Information 6a. Initially.......................: 6b. Within 1 year...................: Subnet Information 6c. Initially.......................: 6d. Within one year.................: 7a. Number of addresses requested...: 7b. Additional supporting justification...................: If requesting 16 C's or more, you are required to submit the network topology plan in the format of the example below: ---------------------------------------------------------------------------- Subnet# Subnet Mask Max Now 1yr Description ---------------------------------------------------------------------------- 1.0 255.255.255.224 30 8 16 Network Group (use 0!) 1.1 255.255.255.224 30 17 22 Engineering 1.2 255.255.255.224 30 12 12 Manufacturing 1.3 255.255.255.224 30 5 9 Management 1.4 255.255.255.224 30 10 15 Sales 1.5 255.255.255.224 30 7 8 Finance 1.6 255.255.255.224 30 0 0 (spare) ---------------------------------------------------------------------------- Totals 210 59 82 ---------------------------------------------------------------------------- If requesting a Class B or 256 C's (/16 prefix) a network diagram should also be included with your request. 8. Type of network..................: INSTRUCTIONS FOR REQUESTING INTERNET (IP) NUMBERS The internet-number-template.txt must be completed as part of the application process for obtaining Internet Protocol (IP) Network Numbers. To obtain one or more Internet numbers, please submit the template via electronic mail, to HOSTMASTER@INTERNIC.NET. In the subject of the message, use the words, "IP REQUEST". Once Registration Services receives your completed application we will send you an acknowledgement, via electronic mail. If electronic mail is not available to you, please mail hardcopy to: Network Solutions InterNIC Registration Services 505 Huntmar Park Drive Herndon, VA 22070 -- OR -- FAX to (703) 742-4811 Please do not modify the form nor remove the version number. European network requests should use the european template located at (ftp://ftp.ripe.net/ripe/forms/netnum-appl.txt). Please follow their instructions for submission. Networks that will be connected/located within the geographic region maintained by the Asian-Pacific NIC should use the APNIC template located at ftp://ftp./apnic/docs/english/apnic-001.txt. Please follow their instructions for submission. ***PLEASE READ THE FOLLOWING INFORMATION PRIOR TO REQUESTING AN IP NUMBER FROM THE INTERNIC: Due to technical and implementation constraints on the Internet routing system and the possibility of routing overload, certain policies may need to be enforced by the major transit providers in order to reduce the number of globally advertised routes. These potential policies may include setting limits on the size of CIDR prefixes added to the routing tables, filtering of non-aggregated routes, etc. Therefore, addresses obtained directly from the InterNIC (non-provider-based, also known as portable) are not guaranteed to be routable on the Internet. It is for this reason, you are encouraged to request an IP address from your service provider. If you have not selected a service provider, but plan to connect in the future or your network will never be connected to the Internet, you are encouraged to use IP numbers reserved for non-connected networks set forth in RFC1597 until you can utilize address space from your chosen Internet provider. Also, please note, your organization will only be assigned address space for their immediate to one (1) year requirement. A prefix longer than /24 may be issued if deemed appropriate. Section 1 - Internet connection Please supply information on the approximate date of your connection to the Internet and the name of your Internet access provider, if known. Again, if you have a service provider, you should be contacting them for IP addresses. Section 2 - Technical Point of Contact The technical POC is the person who tends to the technical aspects of maintaining the IP addresses. This person should be able to answer any utilization questions the InterNIC may have. Each person in the InterNIC database is assigned a "handle" - a unique tag consisting of the person's initials and a serial number. This tag is used on records in the database to indicate a point of contact for a network, domain, or other entity. If the technical POC's nic handle is unknown, please leave question 2a. blank. When completing question 2b, place the city, state, and zip code on a separate line. Use a comma to separate the city and state. Do not insert a period following the state abreviation. For example: Organization address.: Street or PO Box Herndon, VA 22070 If the organization is in a country other than the United States, please include the name of the country on the last line by itself. Contacts must list phone numbers and e-mail addresses. Section 3 - Network name 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. The only special character that may be used in a network name is a dash (-). PLEASE DO NOT USE PERIODS OR UNDERSCORES. The syntax XXXX.com and XXXX.net are not valid network naming conventions and should only be used when applying for a domain. Section 4 - Organization name and postal address Identify the name and geographic location of the organization that will be utilizing the network address. Please make sure your response on 4b is to the right of the colon. Section 5 - Previously assigned addresses Please list all IP addresses previously assigned to your entire organization. Also give the specifics regarding the utilization of those addresses in questions 5a thru 5c. Section 6 - Justification Estimate the size of the network to include the number of hosts and subnets that will be supported by the network. A "host" is defined as any device (PC, printer, etc) that will be assigned an address from the host portion of the network number. A host may also be characterized as a node or device. Section 7 - Number of addresses requested Please state exactly how many addresses you are requesting along with any additional justification necessary. As stated on the template, if you are requesting 16 C's or more (/19 prefix) you will need to complete the network topology plan in the format shown on the template. If you are requesting 256 C's or a Class B (/16 prefix) or more, please include a copy of your network diagram. Your organization is strongly encouraged to subnet where feasible. Section 8 - Type of network Networks are characterized as being either Research, Educational, Government-Non Defense or Commercial. Which type is this network? For further information contact InterNIC Registration Services: Via electronic mail: HOSTMASTER@INTERNIC.NET Via telephone: (703) 742-4777 Via postal mail: Network Solutions InterNIC Registration Service 505 Huntmar Park Drive Herndon, VA 22070 RECOMMENDED READING (available via anonymous FTP from DS.INTERNIC.NET (198.49.45.10), or call 1-619-455-4600 Gerich, E. Guidelines for Management of IP Address Space, Ann Arbor, MI: Merit Network, Inc.; May 1993; RFC 1466. 10 p. (DS.INTERNIC.NET RFC1466.TXT). Rekhter, Y., Moskowitz. B., Karrenberg, D., de Groot, G. Address Allocation for Private Internets, IBM Corp., Chrysler Corp., RIPE NCC; March 1994; RFC 1597. 8 p. (DS.INTERNIC.NET RFC1597.TXT). 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. (DS.INTERNET.NET POLICY RFC1009.TXT). Internet Engineering Task Force, Braden, R.T. Requirements for Internet Hosts -- Communication Layers. Marina del Rey, CA: University of Southern California, Information Sciences Inst.; October 1989; RFC 1122. 116 p. (DS.INTERNIC.NET RFC1122.TXT). Internet Engineering Task Force, Braden, R.T. Requirements for Internet Hosts -- Application and Support. Marina del Rey, CA: University of Southern California, Information Sciences Inst.; October 1989; RFC 1123. 98 p. (DS.INTERNIC.NET RFC1123.TXT). Internet Activities Board. Internet Official Protocol Standards. 1994 March; RFC 1600. 34p. (DS.INTERNIC.NET POLICY RFC1600.TXT). [Note: the current version is always available as "STD 1".] Postel, J.B. Internet Standard Subnetting Procedure. Stanford, CA: Stanford University; 1995 March; Obsoletes RFC1720 RFC 1780 (DS.INTERNIC.NET RFC1780.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. (DS.INTERNIC.NET POLICY 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. (DS.INTERNIC.NET POLICY RFC793.TXT). Postel, J.B. User Datagram Protocol. Marina del Rey, CA: University of Southern California, Information Sciences Inst.; 1980 August 28; RFC 768. 3 p. (DS.INTERNIC.NET POLICY RFC768.TXT). Postel, J.B. Internet Protocol. Marina del Rey, CA: University of Southern California, Information Sciences Inst.; 1981 September; RFC 791. 45 p. (DS.INTERNIC.NET POLICY RFC791.TXT). Reynolds, J.K.; Postel, J.B. Assigned Numbers. Marina del Rey, CA: University of Southern California, Information Sciences Inst.; 1994 October; RFC 1700. (DS.INTERNIC.NET POLICY RFC1700.TXT). (Obsoletes RFC1340)