CoreXchange - IP Address Space Administration v3.

5 Request for IPv4 and IPv6 Address Space

In assigning IPv4 and IPv6 address space to its Customers, CoreXchange takes guidance from assignment policies and procedures set forth by ARIN (American Registry for Internet Numbers) Number Resource Policy Manual, RFC 2050, and RFC 3177 (ARIN Adrdess Policies). CoreXchange provides each new Customer up to 8 IP addresses. Customer is required to complete the following Justification Form for its initial address assignment and any further address space allocations. CoreXchange must approve Customers submitted Justification Form, which must be fully completed by Customer in CoreXchanges reasonable determination, before allocating any additional IP address that Customer requests during the Service Term of the Enterprise Master Service Agreement (the MSA), and CoreXchange may withhold such approval if it determines in its sole discretion that Customers submitted Justification Form does not sufficiently demonstrate efficient current and/or projected use of the IP addresses or do not fully comply with ARIN Address Policies. CoreXchange is not responsible for, and does not have a duty to, allocate requested IP addresses to Customer if it does not approve Customers submitted Justification Form, and Customer is not excused from its obligations under the MSA, including its obligation to pay for all Services ordered under any current and effective Service Order Form(s) for the entire term of the MSA, if Customer cannot obtain IP addresses requested under a Justification Form that CoreXchange does not approve. In order to justify an IP address space assignment, please completely document all information requested below, CoreXchange will require applications for IPv4 address space to include an attestation of accuracy from an organizational officer. A complete set of instructions and examples are provided at the end of this document. Note: If you need additional space for any of the documentation requested below, please provide the information in a separate document with your request.

I. Customer Information
Company/ Client Name Address City FAX E-Mail State Zip

Date:

Please complete this section if you are requesting IPv4 and/or IPv6 address space.

Technical Contact Phone

Type of Internet service connection: (check appropriate services that apply)

Colocation Project Manager Connectivity Other

II. Current IPv4 Address Space Utilization

Please complete this section if you are requesting IPv4 address space. List ALL IPv4 address space currently assigned from all sources.
Network Size Assigned By Assign Date % in use

Page 1 of 8

Example:

200.22.22.0

/24

AIMNET ISP

5-30-95

80%

Will you be renumbering out of your current space?

Date when renumbering is expected to be completed:

Yes

No

III. IPv4 Address Space Request

Please complete this section if you are requesting IPv4 address space. IPv4 Block Size Requested

Describe your planned usage of the requested IPv4 address space. Please be concise.

How would you like your space advertised?

Statically Routed Customer

Customer Advertised BGP

IV. Planned Usage for Requested IPv4 Address Space

Please complete this section if you are requesting IPv4 address space. Provide detail about projected usage for the IPv4 address space you are requesting. See the instructions at the end of this document for a detailed example.
Number of Hosts Network Subnet Size Max Now 3-mo 6-mo Description

Example: 200.22.22.0

255.255.255.0

254

128

150

230

Campus Network
Totals

V. IPv6 Address Space Request

Please complete this section if you are requesting IPv6 address space. Prefix length requested Do you currently have IPv6 space?

Yes

No

- If you currently have IPv6 address space, please indicate current and planned usage for existing assignments, as well as planned usage for the requested prefix. Include network diagram (section VII). - If you are requesting more than a single /48, indicate planned usage. Include network diagram.
IPv6 Usage Plan Network Prefix Max Now 6-mo 1-yr Description

Page 2 of 8

Example: 3ffe:a00::

/48

/48

/64

/52

/48

Network infrastructure
Totals

VI. Reverse DNS

Please complete this section if you are requesting IPv4 and/or IPv6 address space. If name servers are specified below, they will be used for reverse delegation (in-addr.arpa). See instructions at the end of this document for further information.
Fully-qualified Domain Name: Ex: mynameserver.company.org

IP Address
Ex: 123.123.123.1

VII. Network Diagram

Please complete this section if you are requesting IPv4 and/or IPv6 address space. Provide a network topology in the space below or provide a Visio file.

VIII. Webhosting
Please complete this section if you are requesting IPv4 address space. If you are providing webhosting services, please indicate in section IV the IP addresses currently being used for this purpose and provide a list of domains being hosted below. If IP-based hosting is being done, a list of technical reasons why named-based hosting cannot be done must be included.

IX. Additional Comments

Page 3 of 8

Please return the completed form to your CoreXchange Account Executive or to your CoreXchange Project Manager. Failure to provide the requested detail may cause a delay in provisioning your IP Address Space Request.

Customer Acknowledgment:
Printed Name Signature Title Date

For CoreXchange Use Only

Comments:

Administrator Initials

Date

Page 4 of 8

Instructions for IPv4 and IPv6 Address Space Request Form

ARIN accounts for the efficient utilization of all IP address space allocated to ISPs (Internet Service Providers) for reassignment to customers. All IP address space is loaned to customers and must be routed on the COREXCHANGE network. Any IP address space assigned to your organization must be relinquished upon termination of subscriber service. All IP address space assignments must be registered in a publicly accessible database in accordance with ARIN guidelines. All IP address blocks will be registered and available publicly in the COREXCHANGE rWhois database server (rwhois://rwhois.corexchange.com:4321). The information provided in this document will be used by COREXCHANGE ONLY to justify the loan of IP addresses. The information may also be given to the RIRs if they request it as part of reviewing their loans to COREXCHANGE. Please note: failure to provide the information requested in this form may cause a delay in completing your request. Please be as concise as possible. If you have any questions while completing this form, please contact your Account Executive or Project Manager. Attestation of Accuracy Documentation Requirements All customers requesting IP address space allocation from CoreXchange are required to provide a signed letter from an organizational officer on company letterhead attesting to the accuracy of the information contained in the CoreXchange IP Justification Form. This ensures that organizations submitting legitimate requests based on documented need will have ongoing access to IPv4 address space to the maximum extent possible. Examples of organizational officers for corporations would be C Level (CEO, COO, CIO etc.) or President. For partnerships, Managing Directors, General Partners are examples. Below is a sample of the language for the attestation letter: [Date] CoreXchange Inc. 1950 Stemmons Frwy Suite 4006 Dallas, TX 75207 SUBJECT: Attestation of IP Justification Dear CoreXchange, I [Organizational Officer] attest to and certify the accuracy of the information contained in the IP Justification Form provided to CoreXchange for the purposes to requesting IP address space dated MM/DD/YYYY and signed by [Person completing IP Justification From]. [Signature of Organizational Officer] [Organizational Officer Name] [Title] [Company Name] I. Customer Information All customers should complete all information requested. This information will be included in the registration of the IP address assignment in the COREXCHANGE rWhois database. Page 5 of 8

II. Current IPv4 Address Space Utilization List all IP addresses assigned to your organization from ALL sources, not just COREXCHANGE assigned blocks. You do not need to include private IP address space. If you will be renumbering from your current space into the space you are requesting, please indicate so and include the date when renumbering is expected to be completed. III. IPv4 Address Space Request IP Block Size Requested may be in CIDR (e.g. /23) or number of IP addresses (e.g. 512). The planned usage description should be a detailed statement of how the requested space would be used. IV. Planned Usage for Requested IPv4 Address Space Show subnet detail if space has been subnetted. If you will be renumbering into the requested block, you do not need to indicate your current IP addresses in the Network column. If you currently have space and will not be renumbering, include the actual IP addresses that you are keeping on your network and use relative numbers for the new space being requested. If you do not currently have IP address space, please use relative numbers in the Network column, as shown below in the examples. Do not include private or NAT IP addresses.

Subnet Size may be designated as either subnet mask or CIDR notation. Include predicted IP address usage for today, three months, and six months. Indicate the use of each IP address block in the description field. Ex. 1: Requesting a /22 NetworkSubnet Size Max 0.0.0.0 255.255.254.0 0.0.2.0 255.255.255.0 0.0.3.0 255.255.255.0 Ex. 2: Requesting a /24 NetworkSubnet Size Max 0.0.0.0 /25 0.0.0.128 /26 0.0.0.192 /26 Now 512 256 256 1024 Now 128 64 64 256 3-mo 128 32 64 224 3-mo 64 24 12 100 6-mo 256 128 128 512 6-mo 100 32 24 156 Description 512 webhosting 256 customer /30s 192 infrastructure 960 Totals Description 128 webhosting 64 VoIP customers 64 server IPs 256 Totals

V. IPv6 Address Space Request Note: This section only needs to be completed by customers requesting IPv6 address space. Enter the prefix length requested. This will typically be a /48 unless you plan on re-assigning subnets. Mark whether you currently have IPv6 address space assigned. If you do not have current IPv6 address space and you are only requesting one /48, you may skip the remainder of this section. If you are requesting more than one /48, please complete the planned usage section and include a network diagram with your request. Page 6 of 8

If you currently have IPv6 address space, indicate current and planned usage for existing assignments, as well as planned usage for the requested prefix. Include a network diagram with your request. VI. Reverse DNS This section only needs to be completed if you will be doing your own reverse DNS for your IP address block. Include host name and IP address for each name server. Please note that COREXCHANGE WILL NOT register your name servers with ARIN for any reassigned IP address space. All DNS reverse look-up (in-addr.arpa) queries for your IP address space will be referred to COREXCHANGE name servers. The COREXCHANGE name servers will function as either the primary name server for your in-addr.arpa, provide responses based on a secondary zone transferred from your locally maintained RFC 2182 compliant name server, or delegate the in-addr.arpa to your name servers for administration. Please contact support@corexchange.com with any questions regarding how your reverse DNS will be set up. VII. Network Diagram Please include a network diagram in the space provided or attached in a separate document. You may include a network diagram for a smaller assignment if desired. A sample network diagram can be viewed at: http://www.corexchange.com/

Page 7 of 8

VIII. Webhosting This section only needs to be completed if you are providing webhosting services to your customers. Below is a sample of the webhosting documentation requested. The reason(s) we are not doing name-based hosting for all of our web hosting customers is/are: a) Reason1 b) Reason2 c) etc. The domains we are hosting are: example.com etc. IX. Additional Information Include any additional information that may be of use to justifying your request.

Page 8 of 8