Important information regarding ISP requests: www.arin.net has information regarding the proposed creation of a non-profit IP Registry known as the American Registry for Internet Numbers (ARIN). If created, ARIN will be responsible for the allocation of IP numbers in North America, South America and all other regions currently administered by the InterNIC. ARIN will be funded by fees for registration services and membership dues. As this may impact your decision to request address space directly from the InterNIC, we ask that you review the ARIN website before requesting address space. Please note that end-users and ISPs receiving address space from their upstream ISP will not be directly impacted by these fees. [ ftp://rs.internic.net/templates/isp-ip-template.txt ] [07/97] ********************** PLEASE DO NOT REMOVE Version Number ******************** ISP Network Version Number: 3.0 ****************** Please see attached detailed instructions ****************** Internet Connections 0a. Directly connecting to peering points? Please list 0b. Connectivity via service providers? Please list 0c. Other Reassignment Information 1a. Block..........................: 1b. Assigned.......................: 1c. Reserved.......................: 1d. Available......................: 1e. Reassignment option............: 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.: 4c. Maintainer ID (if known).......: 5. CIDR Block requested...........: 6. Portable (P) Non-portable (N)..: Host Information 7a. 3 month projection for dial up customers..............: 7b. 3 month projection for leased line customers..........: 7c. Additional information.........: Primary Name Server 8a. Primary Server Hostname........: 8b. Primary Server Netaddress......: Secondary Name Server(s) 9a. Secondary Server Hostname......: 9b. Secondary Server Netaddress....: -----------------------------CUT HERE ---------------------------------------- INSTRUCTIONS FOR REQUESTING AN ISP CIDR BLOCK The isp-ip-template.txt must be completed by Internet Service Providers (ISP) as part of the application process for obtaining a CIDR block of Internet Protocol (IP) Network Numbers. To obtain a CIDR block of Internet numbers, please submit the template via electronic mail, to HOSTMASTER@INTERNIC.NET. In the subject of the message, use the words, "ISP CIDR REQUEST". Once Registration Services receives your completed application we will send you an acknowledgement, via electronic mail. Please do not modify the form nor remove the version number. Prior to requesting your initial allocation of addresses, please read the InterNIC Procedures Guidelines found under the following URL: ftp://rs.internic.net/policy/internic/internic-ip-1.txt. If you are requesting addresses from the InterNIC it is assumed you have read and agree to abide by the guidelines. Section 0 - Internet connection Please supply detailed information on exactly how your organization is connected to the Internet. One of the following options should be completed. Please complete this section on every CIDR block requested. a) Directly connecting to peering points? Please list b) Connectivity via service providers? Please list c) Other Section 1 - Aassignment information Previously allocated blocks will be reviewed for efficient utilization prior to allocating additional addresses. Please follow the example below when listing previously allocated blocks. block: 204.123.0.0/16 assigned: 192 (/24 prefixes) reserved: 40 available: 24 (network numbers available for customer use) reassignment option: (RWhois rwhois.provider.net:4321) (options are SWIP or RWhois if using RWhois please include host and port number) Additional addresses will not be allocated until SWIP (Shared WHOIS Project) assignment information has been submitted to REASSIGN@INTERNIC.NET. OR To place your RWhois server in the RWhois tree, a referral template needs to be sent to rwhoisreg@internic.net. A referral template can be found at the following URL: ftp://rs.internic.net/templates/rwhois-template.txt. Section 2 - Technical Point of Contact The technical POC is the person who tends to the technical aspects of maintaining the allocated CIDR blocks. 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 item 2a. blank. 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. Preferably, all future network names should be a continuation of the original name, i.e., Internet-blk-1, Internet-blk-2, Internet-blk-3, etc. Section 4 - ISP/Organization Name/Location/Maintainer ID Identify the name and geographic location of the Internet Service Provider requesting the CIDR block. All ISPs are issued a maintainer id to enable them to SWIP their reassignment information. Please list your maintainer id on question 4c. If this is your first request, leave it blank and a maintainer id will be assigned to your organization. Section 5 - Size of CIDR Block requested If your immediate to 3 month requirement is less than /19, you are encouraged to contact your upstream provider for address space. This will aid in the efficient deployment of CIDR. Please keep in mind that allocations are made based on a slow-start model. The initial allocations will be relatively small. Subsequent allocated blocks may be increased based on utilization verification supplied to the InterNIC. Section 6 - Portable/Non-Portable address space If you allow your customers to take their assigned IP numbers with them when they change providers, please check (P) for Portable. If you require the IP addresses assigned from your CIDR block to be returned, please check (N) for non-portable. Section 7 - Justification Please list your 3 month projections for dial up customers and leased line customers. It is preferred that ISPs issue classless assignments whenever possible to help preserve the remaining address space. Please include any additional information you feel is pertinent to help detail your requirement. Sections 8 and 9 - New IN-ADDR registration To register your inverse mapping on the CIDR block you are requesting complete this section of the template. Neither the name nor the number of a registered name server will be changed as a result of a new IN-ADDR registration. A Modify registration request must be sent to change either of these values. Any modification to the inverse mapping must be sent via the SWIP template version 1.4 to REASSIGN@INTERNIC.NET. Networks are required to provide at least two independent servers for translating address to name mapping for hosts in the domain. The servers should be in physically separate locations and on different networks if possible. Section 8a-b - Primary Name Server Please provide the fully-qualified name of the machine that is to be the name server; for example: "machine.domainame.com" and the IP address of the name server. It is suggested that the fourth octet of the IP address of a server should be neither 0 nor 255. Section 9a-b - Secondary Name Server(s) The same procedures for specifying primary servers apply as to secondary servers. If several secondary servers are required, copy Section 9 as many times as needed. DO NOT RENUMBER OR CHANGE THE COPIED SECTION. A maximum of six name servers may be added to a network record. For further information contact InterNIC Registration Services: Via electronic mail: HOSTMASTER@INTERNIC.NET Via telephone: (703) 742-4700 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 Hubbard, K., Kosters, M., Conrad, D., Karrenberg, D., Postel, J. Internet Registry IP Allocation Guidelines; November 1996 BCP 12 RFC 2050. 13 p. < URL: ftp://ds.internic.net/rfc/rfc2050.txt> Rekhter, Y., Moskowitz. B., Karrenberg, D., de Groot, G. Address Allocation for Private Internets, IBM Corp., Chrysler Corp., RIPE NCC; February 1996; RFC 1918. 9 p. < URL: ftp://ds.internic.net/rfc/rfc1918.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. < URL: ftp://ds.internic.net/rfc/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. < URL: ftp://ds.internic.net/rfc/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. < URL: ftp://ds.internic.net/rfc/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".] < URL: ftp://ds.internic.net/rfc/rfc1600.txt> Postel, J.B. Internet Standard Subnetting Procedure. Stanford, CA: Stanford University; 1995 March; Obsoletes RFC1720 RFC 1780 < URL: ftp://ds.internic.net/rfc/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. < URL: ftp://ds.internic.net/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. < URL: ftp://ds.internic.net/rfc/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. < URL: ftp://ds.internic.net/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. < URL: ftp://ds.internic.net/rfc/rfc1791.txt> Reynolds, J.K.; Postel, J.B. Assigned Numbers. Marina del Rey, CA: University of Southern California, Information Sciences Inst.; 1994 October; RFC 1700. < URL: ftp://ds.internic.net/rfc/rfc1700.txt>