IP Address Request Information

Syringa Networks strictly follows ARINs Number Resource Policy Manual on the allocation of IP address space as described in RFC 2050. The Policy can be located by visiting their web site at www.arin.net or by clicking the following link; www.arin.net/policy/nrpm.html

To request additional IP's please contact the Syringa Networks sale team at 208-229-6100 or send an email to sales@syringanetworks.net

Creed

IP Addresses are available from Syringa Networks for directly connected Syringa Networks Internet customers ONLY. IP addresses assigned by Syringa Networks are not transferable. A Syringa Networks Sales Engineer will assist you in completing the IP address request. Once the form is completed, the Sales Engineer will submit the request for processing.

IPV4 Allocation to End users (non-ISP)

ARINs Number Resource Policy Manual (Version 2006.3 – 20 December 2006 section 4.3 specifically outlines the end user requirements. Please review these requirements when submitting a request for IP addresses. Specifically the “Utilization Rate” section 4.3.3. ARINs Number Resource Policy Manual can be found on ARINs web site www.arin.net or directly by clicking the following link. www.arin.net/policy/nrpm.html

If you are in need of IP addresses please contact Syringa Networks Sales Team at 208-229-6100 or send an email to sales@syringanetworks.net

IPV4 Allocation to ISPs

ARINs Number Resource Policy Manual (Version 2006.3 – 20 December 2006 section 4.2 specifically outlines the allocation process for ISPs. If you are an ISP and in need of IP addresses please contact your Syringa Networks Sales Team.

ISPs are strongly advised to read and understand ARIN's policies on the administration of IP space before submitting a request for IP addresses.

Requesting Additional Address Space

End user organizations (non-ISP)

Syringa Networks customers will be assigned address space based on immediate utilization plus a 1 year projected utilization. Internet Registries (Syringa Networks) must examine each address space request in terms of `the requesting organization's networking plans. These plans should be documented, and the following information should be included as outlined in section 3.2 of RFC 2050:

1. subnetting plans for at least one year:

2. a description of the network topology

3. a description of the network routing plans, including the routing protocols to be used as well as any limitations.

The subnetting plans should include:

1. a tabular listing of all subnets on the network

2. its associated subnet masks

3. the estimated number of hosts

4. a brief descriptive remark regarding the subnet

This information should be submitted along with the End User request template when requesting additional address space.

ISPs

Section 2. of RFC 2050 outlines the Framework of how ISPs allocate IP addresses. ISP must have documented justification available for each assignment. There are two options for providing reassignment information to ARIN: Shared WHOIS Project (SWIP) and/or Referral WHOIS (RWhois). Detailed information on these two reassignment processes can be found on the ARIN web site or by clicking on the link. www.arin.net/registration/guidelines/report_reassign.html .

SWIP templates can be found on the ARIN web site or by clicking on the following link. www.arin.net/registration/templates/index.html

ISP customers will be assigned address space based on immediate utilization plus a 1 year projected utilization. Internet Registries (Syringa Networks) must examine each address space request in terms of `the requesting organization's networking plans. These plans should be documented, and the following information should be included as outlined in section 3.2 of RFC 2050:

1. subnetting plans for at least one year:

2. a description of the network topology

3. a description of the network routing plans, including the routing protocols to be used as well as any limitations.

The subnetting plans should include:

1. a tabular listing of all subnets on the network

2. its associated subnet masks

3. the estimated number of hosts

4. a brief descriptive remark regarding the subnet