IPv6 PI Clarification

Current

Proposed

6.8   PI Assignments

This policy is aimed at providing IPv6 address space to end-sites.

6.8   PI Assignments

This policy is aimed at providing IPv6 address space to end-user organizations.

6.8.1 Introduction

This policy allows 'end-sites' to be assigned IPv6 provider independent (PI) addresses. 'End-sites' include End-Users and critical Infrastructure providers such as TLD root server operators and public Internet exchange Points (IXP's).

6.8.1 Introduction

This policy allows 'end-sites' of end-user organizations to be assigned IPv6 provider independent (PI) addresses. These include critical Infrastructure providers such as TLD root server operators and public Internet exchange Points (IXP's).

6.8.2 Assignment Criteria

1. Assignment target - End-sites which provide Public Internet services for a single administrative organisations' network, regardless of their size.
2. Assignment criteria:
   
   1. The end-site must not be an LIR
   2. The end-site must become an AFRINIC End User Member and pay the normal AFRINIC fee for its membership category
   3. The end-site must justify the need for the IPv6 PI address space.
   4. The end-site must show a plan to use 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.
   5. The IPv6 provider independent address space to be announced by the end-site should not be disaggregated.

6.8.2 Assignment Criteria

1. Assignment target - End-user organizations which provide services for their administrative organizations’ network, regardless of their size.
2. Assignment criteria:
   
   1. The organization must not be an LIR.
   2. The organization must be or become an AFRINIC End User Member.
   3. The organization must justify the number of end-sites and the need for the IPv6 PI address space.
   4. The organization must deploy the IPv6 provider independent address space at each of the end-sites, for which addresses are obtained, within twelve (12) months.
   5. If the addressing space issued under this policy is to be announced, to the extent practicable, the organization should aggregate any announcements of prefixes so as to minimize global routing table growth.

6.8.3 Provider Independent (PI) address space:

1. The provider independent (PI) assignment should be made from a specific block.
2. 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.
3. Subsequent assignments must be documented and justified. Where possible, such assignments will be made from a contiguous address block (i.e., extending the existing assignment "n" bits to the left).

6.8.3 Provider Independent (PI) address space:

1. The provider independent (PI) assignment should be made from a specific block.
2. The initial provider independent assignment size for each organization shall be at least a /48 per end site. If multiple end sites are requested and will be connected to each other, a nibble-aligned prefix shall be issued sufficient to allow at least one /48 per end-site. Valid justification for a shorter prefix for any end sites shall be accommodated.
3. The organization assignment will be calculated on the basis of the number of end-sites and adjusted to the nearest nibble-boundary.
4. Subsequent assignments must be documented and justified. Where possible, such assignments will be made from a contiguous address block (i.e., extending the existing assignment "n" bits to the left).
5. AFRINIC shall use a sparse allocation algorithm when issuing space to maximize the likelihood of success for the mechanism defined in the preceding paragraph.

6.8.4 Rectifying the size of an initial assignment

1. An End-site may submit a new addressing plan to AFRINIC if the plan initially submitted to justify the initial assignment no longer satisfies their current needs.
2. The new assignment will be consistent with the new plan and comply with 6.8.2 and 6.8.3.
3. If possible, the same address block will be “upgraded” to the new required prefix size. However, if the adjacent prefixes are already being used by other organizations or if such assignment would not leave sufficient space for subsequent assignments, AFRINIC will inform to the requesting organization, which will have the following options:
   i. Receive a new block with the new requested prefix size, with the commitment to renumber its network and return the original block within a period of 6 months;
   ii. Receive a new block which, together with the block that has already been assigned, covers the new justified need, and keep both blocks.
   This procedure can only be used once by each end-site.

6.8.4 Rectifying the size of an initial assignment

1. An organization may submit a new addressing plan to AFRINIC if the plan initially submitted to justify the initial assignment no longer satisfies their current needs.
2. The new assignment will be consistent with the new plan and comply with 6.8.2 and 6.8.3.
3. If possible, the same address block will be “upgraded” to the new required prefix size. However, if the adjacent prefixes are already being used by other organizations or if such assignment would not leave sufficient space for subsequent assignments, AFRINIC will inform to the requesting organization, which will have the following options:
   i. Receive a new block with the new requested prefix size, with the agreement to utilize the new block for all future deployment and deprecate the old block through attrition, returning when empty. There is no deadline for return at this time;
   ii. Receive a new block which, together with the block that has already been assigned, covers the new justified need, and keep both blocks.
   This procedure can only be used once by each organization. 

Date

Details

09 April 2019

Version 1: AFPUB-2019-v6-DRAFT01

Initial Draft Posted to rpd

14 May 2019

Version 2: AFPUB-2019-v6-DRAFT02

Comprehensive revisions to 6.8.2, 6.8.3 and 6.8.4