AFRINIC as Regional Internet Registry(RIR) commits to ensuring fairness and consistency in its operations and service delivery to the community. As the RIR has finally reached exhaustion which has subsequently triggered the softlanding policy found in section of 220.127.116.11 of the CPM, we find it imperative to revise the LIR guidelines in an effort to ensure that LIR's requesting for IPv4 resource allocation, are being policy compliant and, are able to provide complete or near to complete set of requirements.
This in turn shall make the evaluation process easier, quicker and seamless with the changes brought about by the exhaustion.
A complete IPv4 resource request shall be recognized as one that contains sufficient information as described in this document and it shall enable the Hostmasters to approve a prefix size for the Resource Member within minimal evaluation time frame.
This document is meant as a guideline to the LIR members. AFRINIC , at its own discretion, may exceptionally request for additional supporting documentation or clarifications that is not mentioned in this guideline.
The document is intended for prospective members and current AFRINIC members in the category of Local Internet Registries (LIR), who are in need of IPv4 resources. An LIR member as per section 2.3 of the Consolidated Policy manual is defined as "an Internet Registry that receives allocations from an RIR and primarily assigns address space to 'end-users'. LIRs are generally ISPs , but with time, Internet based services have evolved such that cloud and other hosted service providers also categorise as LIRs.
Their customers are end-users and possibly other ISPs . LIRs must be members of AFRINIC. and furthermore Section 18.104.22.168.1 of the Consolidated Policy manual highlights the responsibility for LIR as follows "All LIR's assigning address space allocated from AFRINIC are also advised to adopt a set of policies that are consistent with the policies described in this document.
Services that are associated with the LIR category include but are not limited to the following:
These terminologies are referenced from the CPM
To "allocate" means to distribute address space to LIRs for the purpose of subsequent distribution.
To "sub-allocate" means to distribute address space (by LIRs) to ISPs for the purpose of subsequent distribution.
An assignment is an IP block given by an LIR to the end-users for their own usage. To "assign" means to delegate address space to an ISP or End User for specific use within the Internet infrastructure they operate. Assignments must only be made for specific purposes documented by specific organisations and are not to be sub-assigned to other parties.
PA space is what has been allocated to LIRs from which they can assign or sub-allocate to end-users / downstream networks as non-portable block. If the end-user / downstream network changes provider, the address space assigned or sub-allocated by the previous service provider (LIR) should be returned and the network renumbered.
PI (or portable) space cannot be aggregated and can only be assigned by RIR through an LIR. PI space is expensive to route and might not be globally routable. Sub-allocations cannot be made from this type of address space by the end user or LIR.
AFRINIC has made all efforts to ensure that requestors read the guidelines before submitting any request for IPv4 resources. This will ensure that AFRINIC Hostmasters receive complete requests and there is no time wasted before the request evaluation begins. Any request that is missing any of the identified items below will be regarded as incomplete and no evaluation shall commence until it is complete. The Resource Member will be advised by the AFRINIC Hostmaster to furnish same via an email response.
Internet services providers mostly are authorized by national regulatory bodies before they can start operations in most of the countries in the region, as such, below is a checklist for requirements that would constitute a complete request:
Unlike the ISP's, these services providers do not require service license from the regulators in their country of operation. As such, below is a checklist of what is required for a complete request submission:
IPv4 additional resource requests are usually submitted by the AFRINIC LIR Resource Members.
Below is a checklist for what constitutes a complete IPv4 additional resources request:
AFRINIC resources are meant to be deployed for services originating from the AFRINIC service region and any use outside our service region should be solely in support of connectivity back to the AFRINIC region as per section 22.214.171.124 of the CPM
The IPv4 allocation policy mentioned that resource allocations will be a balance of the applicant's needs and the needs of the community as stipulated is Section 5.2.2 of the CPM Therefore, any change to the usage of the the allocated resources, different from what the allocation was approved for shall be communicated to AFRINIC in advance. The member shall send an email to email@example.com with subject " Change Request for IP address usage "based on the principle that 70% of an allocated resource will be deployed for the provision of new services. The AFRINIC hostmasters may at their discretion, evaluate the change of needs.
This condition is duly enforced in section 4.c(iv) and 6.d.(iii) - (v) of the Registration Service Agreement (RSA) which every Resource Member signs as a binding contract with AFRINIC.
As per section 126.96.36.199 of the CPM, LIR's must keep and maintain records of any documentation regarding assignments and sub-allocations to end-users.
It is needed for future reference when evaluating requests from the same organisation and for any audits being conducted by AFRINIC. These documents should be kept electronically for easier access. It's advisable that these records should include but not be limited to:
Electronic data refers to information kept on IT systems , based on real-time data and are verifiable. Verification by hostmasters can be conducted and the member shall be requested to demonstrate the usage in real-time in a remote session.
From experience, most AFRINIC members of category Medium and above have a system in place to provide this data. Those members who use their own proprietary applications are recommended to ensure that they have a dashboard (or other method) of being able to demonstrate the data. This is to ensure that "electronic data" are not tampered with , just to demonstrate 90% usage of current allocations.
AFRINIC Hostmasters reserve the right to stop the evaluation of an additional resource request , should they detect that fraudulent information is being provided. The hostmasters, upon consultation with AFRINIC management & legal team may then trigger a full audit of the resource member.