IP Address Public Policy

IP addresses are loaned  from the Regional Internet Registries (RIRs) such as ARIN and RIPE. In turn,  those IP addresses are lent to our customers for use while connected to our network. The size of the IP address loan varies and is solely based on the continually demonstrated and documented need of the customer.

Table of Contents

  1. Introduction

    This IP Address Policy has been created with guidance from various Request For Comments documents (RFCs) and the existing policies of the RIRs from which we obtain IP addresses. See www.arin.net/policy/nrpm.html

    Due to the dynamic nature of the internet, We reserve the right to change this document at any time without prior notice. Please check the Appleget Associates Inc. website for the latest version of this policy, as the latest version of the policy will supersede all others.

    Appleget Associates Inc. distributes IP addresses with three goals in mind:

    1. Conservation: The objective distribution of globally unique IP address space according to the operational needs of customers. We try to prevent stockpiling in order to maximize the utilization of IP address space.
    2. Routability: The distribution of globally unique IP address space in a hierarchical manner, which permits scalability in the internet routing table. The loan of IP address space by us does not guarantee routability, due to other ISPs routing policies.
    3. Registration: We are required by ARIN (American Registry for Internet Numbers) to provide information on which entity is using the IP space. This information can be provided to ARIN either via SWIP or an RWhois server. We document the loan of IP addresses to a customer via a publicly available Referral WHOIS (rwhois) server. If a customer is assigned static IP addresses, the customer information will be added to our RWhois server. This information includes: customer’s name, company name if a business, postal address, e-mail address, IP address, and telephone number.

    We realize that conservation and routability can be conflicting goals. We will review individual cases when there are conflicts to try to work out an appropriate compromise.

  2. Guidelines for Customers

    We have developed the following guidelines that will be applied to customer requests for IP address space:

      1. IP addresses are loaned in blocks that conform to Classless Inter-Domain Routing (CIDR) boundaries. Customers should use classless technologies and routing protocols that support variable length subnet mask (VLSM).
      2. IP addresses are loaned for the duration of the customer’s connection to the our network and must be routed on our network. In the event that the customer disconnects from our network or stops routing the addresses on our network, a 30 day grace period will be given for the customer to renumber out of their loaned IP address space.
      3. In the event that our customer (Customer A) acquires/merges/takesover another customer (Customer B) of ours, the resulting customer of record will be required to renumber “Customer B” into IP address space assigned to “Customer A”. Should the resulting customer require additional space to accomodate this renumbering, they will need to complete an IPJ (documenting their address space utilization) for review and approval by us.
      4. At any time, we may require a customer to justify its IP address loan. If the customer is unable to do so, its ability to obtain future loans may be jeopardized and its existing loan may be revoked.
      5. IP addresses are loaned to customers using a “slow-start” process. New customers will receive a minimal loan based on their immediate requirement. Thereafter, the size of loaned IP address blocks may be increased based on the speed that the customer utilizes all previously loaned IP address blocks.
      6. RIRs may set a maximum size of the IP address loan that we are allowed to make. If a customer requests an increase in loan size that is above the RIR size limit, the RIR reserves the right to review and approve the loan. The RIR may have different guidelines than we dos for reviewing and approving the loan and the customer would be required to adhere to the RIR’s guidelines in this instance.

    When a customer requests an IP address space loan from us that will be used for IP-based web hosting, the customer will need to provide technical justification as to why they are providing IP-based web hosting instead of name-based web hosting. We are required to provide this information to the RIRs.

  3. Documentation Required

    Before we make an IP address loan to a customer, the following documentation must be submitted by the customer. We will not begin the IP address loan process until all of the required documentation has been submitted. A sample set of documentation is provided at the end of this document.

    1. Documentation of existing IP address space usage. This shows how any space the customer has is currently being used, along with projections for the next 3 and 6 months. 
    2. Documentation showing how the requested IP space will be used. This shows how the customer plans to use the space immediately, along with projections for the next 3 and 6 months. 
    3. A network topology map for all requests of 128 IP addresses (/25) or larger.
    4. A description of the network routing plans, along with any protocols used and the protocol limitations.
    5. For customers requesting space for web hosting, a list of IP addresses currently being used for web hosting, and a list of domains being hosted. If IP-based hosting is being done, a list of technical reasons why named-based hosting cannot be done must be included.

    This information will be used by us ONLY to justify the loan of IP addresses to a customer. The information may also be given to the RIRs if they request it as part of reviewing their loans to us..

  4. References

    [RFC 2050] Hubbard, K., Kosters, M., Conrad, D., Karrenberg, D., and Postel, J.,
    INTERNET REGISTRY IP ALLOCATION GUIDELINES“, November 1996.

    www.arin.net/policy/ipv4.html
    www.ripe.net/ripe/docs/iprequestform.html
    www.ripe.net/ripe/docs/ipv4-policies.html