Resource Policy Manual - DRAFT
- Resource Policy Manual - DRAFT
- 2. General Definitions
- 3. The Policy Development Process (PDP)
- 4. Hierarchy of number resource distribution
- 5. IPv4
- 6. IPv6
- 7. ASN
- 8. “Abuse” Contact Information
- 9. Temporary Resource Allocation & Assignment
- 10. Reverse delegation
This section defines registry policies for the assignment and allocation of globally unique IPv6 addresses to Internet Service Providers (ISPs) and other organisations in the AFRINIC region. It provides recommendations to the addressing registries (AFRINIC, APNIC, ARIN, LACNIC and RIPE-NCC) on policies for assigning IPv6 address blocks to end sites.
In particular, it recommends the assignment of /48 in the general case, /64 when it is known that one and only one subnet is needed and /128 when it is absolutely known that one and only one device is connecting. For more details about this document, please read RFC-3177
Unlike IPv4, IPv6 is generally assigned to End Sites in fixed amounts (e.g. /48). The actual usage of addresses within each assignment will be low when compared to IPv4 assignments. In IPv6,"utilisation" is only measured in terms of the bits to the left of the /48 boundary. In other words, "utilisation" refers to the assignment of /48s to End Sites and not the number of addresses assigned within individual /48s at those End Sites.
Throughout this document, the term "utilisation" refers to the allocation of /48s to End Sites and not the number of addresses assigned within individual /48s within those End Sites.
The HD-Ratio is a way of measuring the efficiency of address assignment [RFC 3194]. It is an adaptation of the H-Ratio originally defined in [RFC1715] and is expressed as follows:
Log (number of allocated objects)
HD = ----------------------------------------------------------
Log (maximum number of allocatable objects)
where (in the case of this document) the objects are IPv6 site addresses (/48s) assigned from an IPv6 prefix of a given size.
6.3 Goals of IPv6 address space management
IPv6 address space is a public resource that must be managed in a prudent manner with regards to the long-term interests of the Internet. Responsible address space management involves balancing a set of sometimes competing goals. The following are the goals relevant to IPv6 address policy.
Every assignment and/or allocation of address space must guarantee uniqueness worldwide. This is an absolute requirement for ensuring that every public host on the Internet can be uniquely identified.
Internet address space must be registered in a registry database accessible to appropriate members of the Internet community. This is necessary to ensure the uniqueness of each Internet address and to provide reference information for Internet troubleshooting at all levels, ranging from all RIRs and IRs to End Users.
The goal of registration should be applied within the context of reasonable privacy considerations and applicable laws.
Wherever possible, address space should be distributed in a hierarchical manner, according to the topology of network infrastructure. This is necessary to permit the aggregation of routing information by ISPs and to limit the expansion of Internet routing tables.
This goal is particularly important in IPv6 addressing, where the size of the total address pool creates significant implications for both internal and external routing.
IPv6 address policies should seek to avoid fragmentation of address ranges.
Further, RIRs should apply practices that maximise the potential for subsequent allocations to be made contiguous with past allocations currently held. However, there can be no guarantee of contiguous allocation.
Although IPv6 provides an extremely large pool of address space, address policies should avoid unnecessarily wasteful practices. Requests for address space should be supported by appropriate documentation and stockpiling of unused addresses should be avoided.
All policies and practices relating to the use of public address space should apply fairly and equitably to all existing and potential members of the Internet community, regardless of their location, nationality, size, or any other factor.
6.3.6 Minimized overhead
It is desirable to minimise the overhead associated with obtaining address space. Overhead includes the need to go back to RIRs for additional space too frequently, the overhead associated with managing address space that grows through a number of small successive incremental expansions rather than through fewer, but larger, expansions.
6.3.7 Conflict of goals
The goals described above will often conflict with each other, or with the needs of individual IRs or End Users. All IRs evaluating requests for allocations and assignments must make judgments, seeking to balance the needs of the applicant with the needs of the Internet community as a whole.
In IPv6 address policy, the goal of aggregation is considered to be the most important.
6.4 IPv6 Policy Principles
To address the goals described in the previous section, the policies in this document discuss and follow the basic principles described below.
6.4.1 Address space not to be considered property.
It is contrary to the goals of this document and is not in the interests of the Internet community as a whole for address space to be considered freehold property.
The policies in this document are based upon the understanding that globally unique IPv6 unicast address space is licensed for use rather than owned.
6.4.2 Routability not guaranteed
There is no guarantee that any address allocation or assignment will be globally routable. However, RIRs must apply procedures that reduce the possibility of fragmented address space which may lead to a loss of routability.
6.4.3 Minimum allocation
RIRs will apply a minimum size for IPv6 allocations to facilitate prefix-based filtering. The minimum allocation size for IPv6 address space is /32.
6.4.4 Consideration of IPv4 infrastructure
Where an existing IPv4 service provider requests IPv6 space for eventual transition of existing services to IPv6, the number of present IPv4 customers may be used to justify a larger request than would be justified if based solely on the IPv6 infrastructure.
6.5 Policies for allocations and assignments
6.5.1 Initial allocation:
184.108.40.206 Initial allocation criteria
To qualify for an initial allocation of IPv6 address space, an organization must:
a. Be an LIR;
b. Not be an end site;
c. Show a detailed plan to provide IPv6 connectivity to organizations in the AFRINIC region.
d. Show a reasonable plan for making /48 IPv6 assignments to end sites in the AFRINIC region within twelve months.
220.127.116.11 Initial allocation size:
Organizations that meet the initial allocation criteria are eligible to receive a minimum allocation of /32.
Organizations may qualify for an initial allocation greater than /32 by submitting documentation that reasonably justifies the request. If so, the allocation size will be based on the number of existing users and the extent of the organization's infrastructure.
6.5.2 Subsequent allocation
Organizations that hold an existing IPv6 allocation may receive a subsequent allocation in accordance with the following policies.
18.104.22.168 Subsequent allocation criteria
Subsequent allocation will be provided when an organization (LIR) satisfies the evaluation threshold of past address utilization in terms of the number of sites in units of /48 assignments. The HD- Ratio [RFC 3194] is used to determine the utilization thresholds that justify the allocation of additional address as described below.
22.214.171.124 Applied HD-Ratio
The HD-Ratio value of 0.94 is adopted as indicating an acceptable address utilization for justifying the allocation of additional address space. Section 7 provides a table showing the number of assignments that are necessary to achieve an acceptable utilization value for a given address block size.
126.96.36.199 Subsequent Allocation Size
When an organization has achieved an acceptable utilization for its allocated address space, it is immediately eligible to obtain an additional allocation that results in a doubling of the address space allocated to it. Where possible, the allocation will be made from an adjacent address block, meaning that its existing allocation is extended by one bit to the left.
If an organization needs more address space, it must provide documentation justifying its requirements for a two-year period. The allocation made will be based on this requirement.
6.5.3 LIR-to-ISP allocations
There is no specific policy for an organization (LIR) to allocate address space to subordinate ISPs. Each LIR organization may develop its own policy for subordinate ISPs to encourage optimum utilization of the total address block allocated to the LIR. However, all /48 assignments to end sites are required to be registered either by the LIR or its subordinate ISPs in such a way that the RIR can properly evaluate the HD-Ratio when a subsequent allocation becomes necessary.
LIRs must make IPv6 assignments in accordance with the following provisions.
188.8.131.52 Assignment address space size
Assignments are to be made using the following guidelines:
- /48 in the general case, except for very large subscribers.
- /64 when it is known that one and only one subnet is needed by design
- /128 when it is absolutely known that one and only one device is connecting.
AFRINIC is not concerned about which address size an LIR actually assigns. Accordingly, AFRINIC will not request the detailed information on IPv6 user networks ( as in IPv4 ) , except for the cases described in Section 4.4 and for the purposes of measuring utilization as defined in this document.
184.108.40.206 Assignment of multiple /48s to a single end site
When a single end site requires an additional /48 address block, it must request the assignment with documentation or materials that justify the request. Requests for multiple or additional /48s will be processed and reviewed (i.e., evaluation of justification) at the RIR level.
Note: There is no experience at the present time with the assignment of multiple /48s to the same end site. Having AFRINIC review all such assignments is intended to be a temporary measure until some experience has been gained and some common policies can be developed. In addition, additional work at defining policies in this space will likely be carried out in the near future.
220.127.116.11 Assignment to operator's infrastructure
An organization (LIR) may assign a /48 per PoP as the service infrastructure of an IPv6 service operator. Each assignment to a PoP is regarded as one assignment regardless of the number of users using the PoP. A separate assignment can be obtained for the in-house operations of the operator.
When an organization (LIR) holding an IPv6 address allocation makes IPv6 address assignments, it must register assignment information in the AFRINIC database. Information is registered in units of assigned /48 networks. When more than a /48 is assigned to an organization, the assigning organization is responsible for ensuring that the address space is registered in the AFRINIC database.
AFRINIC will use registered data to calculate the HD-Ratio at the time of application for subsequent allocation and to check for changes in assignments over time.
AFRINIC shall maintain systems and practices that protect the security of personal and commercial information that is used in request evaluation, but which is not required for public registration.
6.5.6 Reverse lookup
When an AFRINIC delegates IPv6 address space to an organization, it also delegates the responsibility to manage the reverse lookup zone that corresponds to the allocated IPv6 address space. Each organization should properly manage its reverse lookup zone. When making an address assignment, the organization must delegate to an assignee organization, upon request, the responsibility to manage the reverse lookup zone that corresponds to the assigned address.
6.5.7 Existing IPv6 address space holders
Organizations that received /35 IPv6 allocations under the previous IPv6 address policy [RIRv6-Policies] are immediately entitled to have their allocation expanded to a /32 address block, without providing justification, so long as they satisfy the criteria above. The /32 address block will contain the already allocated smaller address block (one or multiple /35 address blocks in many cases) that was already reserved by the RIR for a subsequent allocation to the organization. Requests for additional space beyond the minimum /32 size will be evaluated as discussed elsewhere in the document.
6.6 Assignments for Internet Experiments
Organisations often require deployment tests for new Internet services and technologies. These require numbering resources for the duration of the test.
The policy goal of resource conservation is of reduced importance when resources are issued on a temporary basis.
6.6.1 Defining the experiment
An organisation receiving numbering resources must document the experiment. This may be in the form of a current IETF Experimental RFC (see Sec. 4.2.1 of RFC2026) or an "experiment proposal" detailing the resources required and the activities to be carried out.
The assignment size will be equal to the existing minimum allocation size on the date the request is received. Where the experiment requires a variation to this rule it should be noted in the resource request.
The experiment proposal must be made public (e.g. published on a web site), upon registration of the resources by AFRINIC. Following the conclusion of the experiment the results must be published free of charge and free from disclosure constraints.
6.6.3 Non-commercial basis
Resources issued for an experiment must not be used for commercial purposes.
6.6.4 Period of the Temporary Resource Registration.
The resources will be issued on a temporary basis for a period of one year. Renewal of the resources' registration is possible on receipt of a new request that details any continuation of the experiment during the extended period.
The resources issued cannot be used for a commercial service following the conclusion of the experiment.
AFRINIC will register the resources issued in the AFRINIC Whois Database.
6.7 HD-Ratio (HD) and Utilisation Threshold (T)
The HD-Ratio is not intended to replace the traditional utilisation measurement that ISPs perform with IPv4 today. Indeed, the HD-Ratio still requires counting the number of assigned objects. The primary value of the HD-Ratio is its usefulness at determining reasonable target utilisation threshold values for an address space of a given size. This document uses the HD-Ratio to determine the thresholds at which a given allocation has achieved an acceptable level of utilisation and the assignment of additional address space becomes justified.
The utilisation threshold T, expressed as a number of individual /48 prefixes to be allocated from IPv6 prefix P, can be calculated as:
((48-P)*HD) T = 2 [E4]
Thus, the utilisation threshold for an organisation requesting subsequent allocation of IPv6 address block is specified as a function of the prefix size and target HD ratio. This utilisation refers to the allocation of /48s to End Sites, and not the utilisation of those /48s within those End Sites. It is an address allocation utilisation ratio and not an address assignment utilisation ratio.
In accordance with the recommendations of [RFC 3194], this document adopts an HD-Ratio of 0.94 as the utilisation threshold for IPv6 address space allocations.
The following table provides equivalent absolute and percentage address utilisation figures for IPv6 prefixes, corresponding to an HD-Ratio of 0.94.
6.8 PI Assignments
This section provides for IPv6 provider independent (PI) address assignment to 'end-sites'.
Not all LIR's have IPv6 address space allocations, which makes it impossible for end-users to get PA IPv6 address space from such upstreams (LIR's). This section aims at providing IPv6 address space to such end-users as long as they already have or qualify to get PI IPv4 addresses.
This section allows 'end-sites' to be assigned IPv6 provider independent (PI) addresses.
'End-sites' include End-Users who already have or qualify to get IPv4 PI addresses and critical Infrastructure providers such as TLD root server operators and public Internet exchange Points (IXP's).
6.8.2 Assignment Criteria
a. Assignment target - End-sites which provide Public Internet services for a single administrative organisations' network, regardless of their size.
b. Assignment criteria:
- The end-site must not be an IPv6 LIR
- The end-site must become an AFRINIC End User Member and pay the normal AFRINIC fee for its' membership category
- The end site must either be a holder of IPv4 PI address space or qualify for an IPv4 PI assignment from AFRINIC under the IPv4 policy currently in effect
- The end-site must justify the need for the IPv6 PI address space.
- The 'end-site' must show a plan to use and announce the IPv6 provider independent address space within twelve (12) months. After that period, if not announced, the assigned IPv6 PI address space should be reclaimed and returned to the free pool by AFRINIC.
6.8.3 Provider Independent (PI) address space:
a. The provider independent (PI) assignment should be made from a specific block.
b. The initial provider independent assignment size to an end-site should be a /48, or a shorter prefix if the end-site can justify it