|
3.1. Introduction
|
In this chapter we will describe how an Internet Registry (for future reference, this concept encompasses Internet Service Providers and National Internet Registries) can obtain IP address allocation and how the allocated space must be administered.
IP address space is allocated to Internet Registries (IR) using a slow-start model. Allocations are based on justifiable need, not only on the grounds of client prediction.
Due to the fact that the number of IP addresses is limited, many factors must be considered for the delegation of IP address space.
As mentioned earlier, LACNIC's allocations to IRs are based on RFC 2050's slow-start concept. The idea is to allocate IP address space to Internet Registries in the same proportion as they will assign the IP addresses among their users.
The size of an allocation to a particular IR is based on the rate with which it has previously assigned IP address space among its clients. The aim is to avoid the existence of large blocks that are not assigned to end users.
Due to technical restrictions and the possibility of overcharging the routing tables, certain policies must be implemented in order to ensure that the preservation and routeability objectives are fulfilled.
This chapter mentions prefix sizes and block sizes. Standard notation implies that longer prefixes reference blocks of smaller size. For example, when it is said that certain policy applies to blocks with a prefix longer than /20, this means that blocks smaller than 16 class C networks are being discussed.
|
|
3.2. Aspects to Consider in relation to IP Address Administration
|
|
This section describes a number of aspects on which relationships must be based, both between Internet Registries and their clients as well as between Internet Registries and LACNIC.
|
|
3.2.1. IP Addresses are Delegated
|
|
LACNIC shall allocate Internet resources within a delegation plan. This resource delegation plan shall be valid for one year. This delegation is renewable, and shall be subject to the conditions established at the time of renewal.
|
|
3.2.2. Slow-Start Policy
|
IP address blocks are allocated to IRs using a procedure called slow-start based on RFC 2050.
Internet Service Providers applying for portable (provider-independent) IP address blocks for the first time shall receive a minimal amount based on immediate requirement, with the exceptions established in Section
3.3.3 "Direct Allocations to Internet Service Providers".
After this initial allocation, allocated blocks may be increased based on the verification of block usage according to information provided to LACNIC. Thus, LACNIC shall be responsible for determining initial and subsequent allocations. Additional IP address allocations shall enable the IRs to operate for at least three months without requiring further allocations.
Initial allocations shall not be based on any current or future routing restrictions, but on actual and demonstrated use of IP addresses.
Likewise, the number of addresses projected by the applicant is useful for planning future requirements.
|
|
3.2.3. Allocated blocks
|
|
In order to ensure an efficient implementation and use of classless technologies (CIDR), LACNIC shall allocate IP address blocks based on the limits supported by this technology. To facilitate an efficient deployment of the CIDR, Internet Service Providers (ISPs) and End Users are encouraged to initially request IP address space from their upstream providers. The upstream provider shall maintain control of the allocated blocks upon termination of their clients' contracts.
|
|
3.2.4. Avoid Block Fragmentation
|
|
IP addresses under CIDR technology are allocated to IRs in blocks. It is recommended that the publication of these blocks on the routing tables remain intact. More specifically, ISPs shall treat IP address suballocation to their clients as a loan for the duration of the connectivity. Upon termination of the Internet connectivity contract, e.g., if a customer moves to another ISP, the client shall return the IP addresses currently in use and renumber them with the new IP addresses of the new provider. New requests for addresses shall be conditioned to the completion of this task. The IR shall allow sufficient time for the renumbering process to be completed before these IP addresses are reused with another client.
|
|
3.2.5 Documentation
|
Internet Registries shall use the group of IP addresses they have been allocated in an efficient manner. To this end, IRs shall document the justification for each IP address suballocation. At the request of LACNIC, the corresponding IR shall make this information available. LACNIC shall not make complementary allocations to those Internet Registries that do not have the use of the blocks already allocated properly documented. In these cases, current allocations may also be reviewed.
According to what is established in RFC 2050, the documentation LACNIC may require includes:
- Engineering plans.
- Subnetting and aggregation plan
- Description of network topology
- Description of network routing plans.
- Receipts documenting investments (equipment).
- Other relevant documents.
|
|
3.2.6 Use of Classless Technology (CIDR)
|
|
Due to the requirement to increase the efficiency of the use of IP address space, all assignments are made under the assumption that organizations use variable length subnet masks (VLSMs) and classless technology (CIDR) within their networks. Any request for address space based on the use of classless technology shall require a detailed justification. The use of classfull technologies is generally unacceptable due to the limited availability of free IP address space.
|
|
3.2.7 Static Addressing
|
|
Due to restrictions on the availability of IP addresses, LACNIC shall in no way endorse the use of static IP address assignments for dial-up users (e.g., one address per customer). It is understood that the use of static addressing may simplify some administrative aspects. However, the current rate of consumption of IP addresses does not allow the assignment of static addresses for administrative reasons. Because of this, organizations that are considering the use of static IP address assignment are encouraged to investigate and implement dynamic assignment technologies.
|
|
3.2.8 Web Hosting
|
The development of the http 1.1 protocol has eliminated the need of assigning an IP address for each web domain in case of multiple websites on the same server. LACNIC promotes the development of web page hosting based on name usage, as opposed to IP addresses.
Therefore, this last case shall not be accepted as justification for using IP addresses. LACNIC shall consider exceptions where applications require the use of web hosting based on IP addresses, which must be duly described and justified.
|
|
3.2.9 Non-Guaranteed Routeability
|
Portable (provider-independent) IP addresses issued by LACNIC or NIRs are not guaranteed to be globally routable.
These problems shall be solved by those possessing the IP addresses involved, together with their connectivity provider or providers.
In those cases deemed necessary, LACNIC shall provide the necessary guidance.
|
|
3.2.10 Validity of IP Address Allocation
|
IP address allocations are valid as long as the objectives of exclusivity, conservation, routeability, and information continue to be met. LACNIC may invalidate any IP address allocation if it is determined that the requirements for IP address space no longer exist or any of the objectives stated in this document have ceased to be satisfied.
There are a number of practices that might be considered grounds for losing the allocations received. These are:
- Not using the allocated IP address space during a period of one month following registration.
- Not updating the inverse resolution registry of IP address space.
- Not updating the suballocation information on LACNIC's Whois database.
- Not satisfying contractual obligations towards LACNIC.
- Not applying correctly LACNIC's policies on suballocations and administration of resources received from LACNIC.
In the event of IP address space invalidation, reasonable effort shall be made by LACNIC to inform the community that the IP addresses have been returned and are once again available IP address blocks.
|
|
3.2.11 Submission of Application Templates
|
|
IRs request IP address space from LACNIC through address application templates for IRs or End Users. Any application deemed as lacking information or insufficiently detailed shall be returned to the applicant for its completion.
|
|
3.2.12 Suballocation Supervision
|
|
3.2.12.1 Suballocation Window
|
ISPs may suballocate to their clients blocks smaller than 16 class C networks, i.e., blocks with prefixes longer than /20, following the policy defined by LACNIC in this document. In some cases, suballocations shall be consulted with LACNIC or with the corresponding NIR in order to ensure optimization of the use of IP address space and the correct application of LACNIC policies.
An allocation window is defined by LACNIC as the suballocation of blocks with prefixes shorter than or equal to /23 (larger blocks). These suballocations shall be consulted with LACNIC or the corresponding IR. In these cases, communication between the ISPs and LACNIC or the corresponding NIR shall include the same information and justifications required in this document for end users.
|
|
3.2.12.2 NIR Suballocation
|
NIRs are exempt from complying with item 3.2.12.1. Instead, they shall be subject to more severe audit programs according to the provisions of the contracts between LACNIC and NIRs.
These audits shall be carried out at least once a year and, if necessary, with greater frequency.
|
|
3.2.13. Submission of Suballocation Information
|
Allocations are based on the requirement of three months of Internet Registries, in addition to other information considered relevant by LACNIC such as that described in item 3.2.5 - "Documentation". Thus, initial allocations may be relatively small. The justification for requiring new allocations must be based on the information transmitted by the corresponding Internet Registry to LACNIC's WHOIS database.
Suballocation information shall be sent to LACNIC within a period of seven days following the allocation, so that the WHOIS database may be updated in due time.
Submission of suballocation information is also necessary for the following reasons:
- To ensure that an IR has exhausted, or is about to exhaust, the allocated IP address space, thereby justifying the allocation of new additional space.
- To provide the Internet community with information as to which organization is using the IP address space and to provide a point of contact in case of operational, security, or other problems.
- To assist in the study of IP address allocation within the region.
|
|
3.2.14 Security and Confidentiality
|
|
LACNIC shall maintain systems and practices that ensure and protect the confidentiality of all information entrusted to LACNIC in the documentation submitted to justify allocation or assignment of IP addresses.
|
|
3.2.15 Equal Processing of All Applications
|
|
LACNIC shall process every application strictly in the order they are received, regardless of geographical factors, demographic factors, language, etc. Under no circumstance shall LACNIC grant special treatment or make exceptions to the norm established for application processing. To this end, LACNIC shall use an application numbering system that will allow their proper administration.
|
|
3.2.16 Micro Allocations
|
|
LACNIC shall micro allocate blocks with prefixes longer than the standard (smaller blocks) in special cases listed in Section 3.3 - "Initial IP Address Space Allocation Policies".
|
|
3.2.17 Merger, Acquisition, or Sale of ISPs or End Users
|
LACNIC's policies do not recognize the non-authorized transference of IP address space and shall consider such transferences invalid.
Should an ISP or end user change owner due to a merger, sale, or acquisition, the new entity shall register these changes with LACNIC. If the name of the company is modified, legal documentation validating this change of name shall be submitted.
The information that may be requested includes, but is not limited to, the following:
1.A copy of the legal document validating the transference of assets.
2.A detailed inventory of all assets used by the applicant for maintaining the IP address space in use.
3.A list of the applying party's clients that use portions of the allocated space.
|
| 3.3. Initial IP Address Space Allocation Policies |
LACNIC shall allocate IP addresses to organizations covered by the following cases:
- Allocations to Internet Service Providers.
- Micro-Allocations to Critical Infrastructure.
- Direct allocations to Internet Service Providers.
- End user Assignments.
This section contains a detailed description of the policies LACNIC shall apply for initial allocation of portable (provider-independent) IP addresses in each of the abovementioned cases.
Due to the limited number of IP addresses available on the Internet, many factors must be considered for determining IP address space allocation. Therefore, IP address space is allocated to ISPs following a slow-start model. Allocations are based on current justifiable need, not on prediction of number of clients, market research, etc. |
| 3.3.1. Initial Allocations to Internet Service Providers |
The minimum size for initial allocations applicable to Internet Service Providers established within the region covered by LACNIC is a /21.
In order to qualify for the allocation of a /21 block, the requesting ISP must satisfy the following requirements;
1.Prove usage or immediate necessity of a /23.
2.Submit a detailed one-year usage plan for a /22.
3.Agree to renumber previously allocated space and return those IP addresses to their ISPs no later than 12 months after the allocation of the /21.
Should the requesting ISP require an initial IP address allocation of a /20 or larger space, the following requirements must be satisfied:
Provide information on suballocations of blocks with prefixes equal to a /29 (8 IP addresses) or smaller (more than 8 IP addresses) on LACNIC's WHOIS database.
Provide documentation that justifies the initial address space allocation (Completion of the IP address application form for ISPs). This must include detailed information showing how the /20 block will be used within a period of three, six and twelve months.
Agree to renumber their providers' allocated blocks within a period no longer than 12 months and return the space to its original provider.
Additionally, if the initial request is for a /20 block or larger space, the following requirements shall be considered depending of the multihomed or non-multihomed status of the applicant:
If the applicant is multihomed:
Efficient usage of at least a /22 block (contiguous or not).
An ISP is considered multi-homed if it receives full-time connectivity from more than one Internet Service Provider and has one or more routing prefixes published by at least two of its connectivity providers. Those ISPs that will acquire this status within a period no longer that one month also qualify as multihomed ISPs. In this case, copies of the contracts or documents that validate this status will be required.
If the applicant is non-multihomed:
Efficient usage of at least a /21 block (contiguous or not). |
| 3.3.2 Micro-Allocations to Critical Infrastructure |
| Micro-allocation is the name given to those allocations that imply blocks smaller than /20 but always larger than or equal to /24.
LACNIC may grant this type of allocation in case of network projects and infrastructure that are key or critical for the region, such as IXPs (Internet Exchange Points), NAPs (Network Access Points), RIRs, ccTLDs, among others.
In the case of IXPs or NAPs, in order to be eligible for this type of allocation, an organization must meet the following requirements:
1. Duly document the following aspects:
1.1 Prove by means of their bylaws their IXP or NAP capacity. The organization shall have at least three members and an open policy for the association of new members.
1.2 Submit a network structure diagram of the organization.
1.3 Document the numbering plan to be implemented.
2. Provide a usage plan for the following three and six months.
The rest of the applications shall be studied based on the analysis of the documentation justifying the critical and/or key aspects of the project.
Organizations receiving micro-allocations shall not suballocate these IP addresses. |
| 3.3.3 Direct Allocations to Internet Service Providers |
| LACNIC acknowledges that there may exist circumstances under which there is justifiable need for an initial allocation such that infrastructure and service investment levels merit the allocation of a /20 or shorter prefix.
LACNIC may to grant this type of allocation to those organizations that meet the following requirements:
1.The organization is currently multi-homed or will be multi-homed in the near future (contracts or letters of intention subscribed with their access providers).
2.Submit a detailed description of their network topology.
3.Submit a portfolio with a detailed description of the services the organization will offer.
4.Submit a detailed plan of the deployment of address space usage for three, six, and twelve months.
5.Submit a copy of receipts or purchase orders for the equipment that will support the previously described services.
It should be noted that this type of allocations shall be handled as exceptions and are not covered by the response times guaranteed for processing normal IP address applications. For these allocations LACNIC may, at any time, request additional information to help justify a minimal allocation. |
| 3.3.4 Policies for Initial IP Address Assignment to End Users |
|
LACNIC shall assign IP address blocks to end users requiring IP address space for internal use, for the operation of their networks, but not for sub-delegation outside their organization.
Typically, end users receive IP address space from their upstream providers, not directly from LACNIC. Portable (provider-independent) IP addresses obtained directly from LACNIC or other Regional Registries are not guaranteed to be globally routable. For this reason, end users should contact their Internet Service Providers to ensure their connectivity within the network.
End users not connected to an ISP and/or not planning to be connected to the Internet are advised to use private IP addresses. The description of these IP addresses may be found in RFC 1918.
When assigning IP addresses to end users, LACNIC follows the guidelines of the assignment Policies established in RFC 2050. These guidelines and policies were developed to satisfy the needs of the growing Internet community in relation to preserving the limited IP address space and allowing the continuity and existence of Internet routing technologies.
LACNIC shall request the following information from all end users requesting IP address blocks:
1.Provide detailed information showing how the requested block will be used within the following three, six and twelve months.
2.Submit subnetting plans for a period not shorter than one year, including subnet masks and host numbers on each subnet. Use of VLSM is required.
3.Submit a detailed description of the network topology.
4.Prepare a detailed description of the network routing plans, including the routing protocols to be used as well as any existing limitations.
Usage rate is a key factor that must be justified in order to dimension the size of the assignment. Usage rate is the percentage of IP addresses that the organization will utilize within a specified period of time. The rate established according to RFC 2050 and adopted by LACNIC is:
25% immediate usage rate of the requested block.
50% one-year usage rate of the requested block.
A larger usage rate may be required based on individual requirements. Should the organization presenting the application fail to comply with these parameters, addresses may be withdrawn and a reasonable period negotiated for their renumbering.
In addition, the multihomed or non-multihomed status also affects the evaluation of the application.
If the applicant is a multihomed end user:
The size of the minimum IP address allocation to a multihomed end user is a /24. In order to qualify for a block the applicant must also satisfy the following requirements.
1.Have received an assignment equivalent to a /25 from its Internet Service Providers.
2.Agree to renumber all the blocks allocated by Providers within a period of 3 months and return the space to its original provider.
The minimum block that may be assigned shall be a /24 and the maximum a /21. Initial assignments larger than a /21 must follow the additional requirements established for non-multihomed end users described below.
Multihomed users are those organizations that have at least two permanent Internet accesses, with at least two providers independent of each other. Independent providers refers to the fact that one does not utilize the other to reach the Internet. Those users that are planning to become a multihomed user within a period of one month may also apply. In this case, copies of the contracts or documents that validate this status will be required.
If the applicant is a non-multihomed end user:
The size of the minimum IP address assignment allocated by LACNIC to a non-multihomed end user is a /20. Should the need for IP address space be smaller than a /20, in order to obtain the required addresses end users should contact their corresponding Internet Service Providers.
In order to allocate a /20 block to an end user, in addition to the previous requirements, the following shall be satisfied:
1.Have received a minimum assignment of a /21 block from its Internet Service Provider.
2.Agree to renumber the /21 block within a period of 12 months and return the space to its original provider. This requirement is essential for obtaining the requested /20 block. The allocated /20 block must be used to renumber the previously allocated /21 block.
The policies included in Section 3.4 applicable to end users shall be followed for additional assignments. |
|
3.4 Additional IP Address Space Allocation Policies
|
This policy is presented with the aim of assisting Internet Registries in the process of applying for additional IP address space. The most important factor in the evaluation of additional IP address space applications is the revision of the current IP address space of the organization presenting an application. In order to receive additional space, an organization presenting an application must have used at least 80% of the IP address space previously assigned by the corresponding RIR or NIR. This includes the space reallocated to its clients. Therefore, it is important that IRs demand that their clients follow the efficient usage practices described in these policies.
The steps that must be completed for the allocation of new IP address blocks are the following:
1.The first step of the process is to verify the usage of at least 80% of previous allocations. This usage percentage shall be based solely on those networks publicized with IP addresses connected to the Internet. For IRs that have allocated IP addresses to their clients, the available method to prove this usage is through the records kept in LACNIC's WHOIS database. Until the usage of at least 80% of the previously allocated block is verified, the application shall not continue to be considered. Use of 80% of previously allocated addresses also covers those addresses dedicated to internal use and dial-up clients of the company. In this case, usage may be justified through the report included in Annex 3 [Additional Report for IP Address Space Allocation].
The application process for additional space shall continue once the usage of at least 80% of the previously assigned space has been verified.
2.Organizations shall prove they are using LACNIC policies in suballocating space to their clients, particularly in relation to:
-
Issuing prefixes longer than /24, wherever possible.
-
Verifying that suballocation of blocks within the allocation window were previously submitted to LACNIC for approval.
3. Organizations shall demand that their clients adhere to the following criteria:
-
The information on suballocations smaller than /29 must be available through WHOIS and they must comply with the 80% space usage requirement before assigning additional space to their clients.
-
LACNIC policies for the Internet community are generally communicated to and followed by their clients.
4.When reviewing applications for additional IP addresses, LACNIC shall also review whether the space designated for its return was actually returned in due time as described in this document.
5.Keep the registry of inverse resolution of administered IP address space updated. The inverse resolution registry shall also agree with the 80% usage.
6.For allocating additional blocks, LACNIC shall verify that the organization presenting the application is in compliance with contractual obligations.
7.The final step is to determine the appropriate allocation. In order to determine the size of the allocation, detailed information must be provided showing how the IP address space shall be used within the following three, six and twelve-month periods. The policy for determining the size of additional space allocations is based on the efficient usage of space within a time frame of 12 months.
|
