Template: TransAria-NET-Request-1.0.0 ## As of July 2004 ####################### JUSTIFICATION SECTION ######################## ##-------------------- CONNECTIVITY SUB-SECTION ---------------------- 1. Peering Points: ## List any peering or exchange points to which your network ## directly connects. 2. Internet Connectivity: ## List ISPs providing your connectivity. ##--------------------- UTILIZATION SUB-SECTION ---------------------- ## If necessary, repeat lines 3 through 8. 3. Existing IP Networks: ## List all IP addresses issued to your organization. 4. Assigned: ## Enter the amount of address space issued to customers. 5. Internal: ## Provide internal utilization information. 6. Unassigned: ## Enter the amount of unassigned or available address space. 7. Type of Service: ## List the number of IP addresses that utilize each type of ## service listed below. Dial-up: Cable: Web Hosting: Leased Line: xDSL: Co-location: Wireless: Other (please specify): ##----------------- 3-MONTH PROJECTION SUB-SECTION ------------------- 8. Host Information: ## List the number of IP addresses that will be needed for ## each type of service within the next three months. Dial-up: Cable: Web Hosting: Leased Line: xDSL: Co-location: Wireless: Other (please specify): 9. Additional Information: ## Provide additional information for TransAria to consider for ## this network request. ######################## REGISTRATION SECTION ######################## 10. Prefix Length Requested: ## Enter the prefix length of the network requested, ## e.g. /30, /29. **REQUIRED** 11. Org Name: ## Provide the organization name using no more than 150 ## characters. 12a. IN-ADDR Name Server: 12b. IN-ADDR Name Server: ## If the network has in-addr.arpa servers, list the hostnames ## of at least two name servers. Do not provide IP addresses. ## Duplicate line 15b to specify additional servers. END OF TEMPLATE -----------------------------CUT HERE ---------------------------------------- Instructions for Completing the TransAria Network Request Template Please complete the template and submit via e-mail to ipadmin@transaria.com The TransAria Network Engineering Department will acknowledge receipt of your completed request via e-mail. ******************************IMPORTANT****************************** Request for larger blocks (/26 or shorter) shall be evaluated more stringently and therefore must be accompanied by: · Network Topology (Description and/or Drawings) · Utilization Forecasting (0-3 months) · Subnet Plans (use of VLSM) · Descriptions of all Routing Protocols implemented This documentation should be included in the request to ipadmin@cutthroatcom.com Failure to provide this information will result in you request being returned. ********************************************************************* BACKGROUND Internet Service Providers (ISPs), and Businesses, and end users submit this template as part of the application process for obtaining a block of Internet Protocol (IP) Numbers. Prior to requesting an initial or additional allocation of addresses, please refer to: a. ARIN IPV4 Polices http://www.arin.net/policy/ipv4.html b. Address Allocation for Private Internets http://asg.web.cmu.edu/rfc/rfc1918.html c. INTERNET REGISTRY IP ALLOCATION GUIDELINES http://asg.web.cmu.edu/rfc/rfc2050.html The action of requesting addresses from TransAria indicates you have read and agree to abide by these guidelines. In order to ensure prompt and accurate processing of your Network Request Template, please follow the instructions below. Any errors found may result in the template being returned for correction. If after reading these instructions, you still have questions, contact the TransAria Network Operations Center (NOC): via e-mail: ipadmin@transaria.com via phone: +1-406-556-1778 ======================================================================== TEMPLATE INSTRUCTIONS Please enter "IP REQUEST" in the subject line of the e-mail message. JUSTIFICATION SECTION The JUSTIFICATION SECTION is divided into three sub-sections. They include: - CONNECTIVITY SUB-SECTION to supply detailed information describing your organization's connection to the Internet. - UTILIZATION SUB-SECTION to supply how previous network allocations have been utilized. - 3-MONTH PROJECTION SUB-SECTION to supply information detailing how you intend on using the new allocation. CONNECTIVITY SUB-SECTION 1. List any peering or exchange points to which your network directly connects. 2. List the Internet Service Provider(s) providing your organization's connectivity to the Internet. UTILIZATION SUB-SECTION All sub-delegations must be submitted to TransAria using a request-on-demand template within seven (7) calendar days of the sub-delegation of IP address space. Sub- delegations must be up to date in order for additional address space to be allocated. TransAria will review previously allocated blocks for efficient utilization prior to allocating additional addresses. You may list each allocation separately, by repeating lines 3 through 8. 3. List all IP addresses previously delegated to your organization. Include IP addresses directly delegated from an Internet Registry as well as IP addresses delegated to you from an ISP. 4. List the networks that have been issued to your customers. 5. List the networks used internally by your organization. 6. List the networks that are unassigned or available for reassignment. 7. Indicate the type of services that have utilized the space listed in field 3. Either provide the number of /24s or mark the type of services with an 'X'. 3-MONTH PROJECTION SUB-SECTION 8. List your projections and indicate the type of service you will provide. These projections must be listed as the number of /24s needed. 9. Include any additional information pertaining to this request. REGISTRATION SECTION If your requirement for address space is for a prefix shorter than a /20 (more than 16 /24s), or your orginztion has 16 or more /24's allocated to it you do not qualify for address space from TransAria. We recommend that you contact ARIN to obtain address space directly from them. Allocations are made based on a slow-start model. Subsequent allocated blocks may be increased based on utilization verification supplied to TransAria. 10. Depending on the projections outlined in the 3-MONTH PROJECTION SECTION, provide the prefix length that you expect will meet your needs. 11. Provide the legal name of your organization as it is registered with local, regional or national authorities. 12. Networks should provide at least two, but not more than thirteen distinct name servers for providing address-to-name mapping for hosts in the network. To specify more than two, duplicate line 15b for each additional server. Do not list multiple servers on a single line. Provide fully-qualified host names for the servers that will be providing in-addr name services. END