Public Network Address Space Allocation Policy

In June of 2001, NJEDge.Net was officially assigned a Class B network by the American Registry for Internet Numbers (ARIN) to be used as needed by its participating member institutions and for management of the core infrastructure. During the September 21st meeting of the Network Advisory Board, a motion was passed to accept the recommendations of the Data Architecture committee suggesting that NJEDge.Net follow the best practices and guidelines established by ARIN for the allocation of IP address space and to establish an entity to review address assignment requests. These best practices have been documented in rfc2050 and are available at the following NJEDge.Net web site: http://www.njedge.net/documents/rfc2050.html

This document is intended to provide an overview and summary of the best practices established by ARIN and to outline the process for requesting IP address space from NJEDge.Net. It should be noted that some institutions already have network address space allocations from ARIN will not need to use NJEDge.Net IP addresses. However, those institutions that have network address space assigned by their current Internet Service Provider and are joining NJEDge.Net, will be required to return those addresses to the provider and will need to apply for address space allocations from NJEDge.Net.

The assignment of public address space is to be considered on loan to NJEDge.Net members for the purpose of participating in the NJEDge statewide network. The addresses cannot be sold or reassigned by participating members, and must be returned if the member terminates their contract with NJEDge.Net and moves to another provider.

Due to the explosive growth of the Internet and the constraints on the available public pool of IPv4 address space, a number of best practices have been established to increase utilization efficiency in the allocation of IPv4 address space:

• All assignments are made with the assumption that members requesting NJEDge.Net address space will make use of variable length subnet masks (VLSM) and classless technologies within their network. NJEDge.Net will be arranging seminars concerning guidelines and recommendations for managing campus networks and will provide detailed information concerning methods for implementing VLSM.
• Members should consider and plan on implementing private addresses and network and/or port address translation (NAT/PAT) as described in rfc1918 where appropriate, rfc1918 can be found at:
  http://www.njedge.net/documents/rfc1918.html Recommendations and strategies for implementing NAT/PAT will also be discussed in upcoming seminars focusing on managing campus networks.
• The following specific guidelines have been established by ARIN to govern the allocation of addresses based on utilization rates. Requestors must show how previous address allocations have been utilized and provide appropriate details to verify their one-year growth projection. The basic criteria that must be met to receive network numbers are:
  • A 25% immediate utilization rate, and
  • A 50% utilization rate within one year.

The utilization rate is to be used as a guideline; there may be occasions when the 1-year rate does not fall exactly in this range. Members must exhibit a high confidence level in its 1-year utilization rate and supply documentation to justify the level of confidence.

Procedures for Requesting Address Space

To request IP network numbers, members must complete the NJEDge.Net IP Request Template, available at the following web site:
http://www.njedge.net/documents/ip-request-template.html

Those requests lacking in sufficient or relevant detail will be returned to the requestor for additional information. The following documentation, as specified in the template, must be provided:

• Subnetting plans for at least one year, including subnet masks and number of hosts on each subnet - use of variable length subnet masks (VLSM) is required.
• A description of the network topology and diagram, and
• A description of the network routing plans, including routing protocols to be used as well as any limitations.

End of Policy