Your IP address is 3.233.219.62

Filters

IPv6 PI Update

Details
  • Ref. Name:AFPUB-2018-V6-004-DRAFT01
  • Status: Ratified - Pending Implementation
  • Submitted:28 March 2018
  • Versions: 1.0
  • Amends: CPM art 6.8
  • Obsoletes:
  • Author:
    - Jordi Palet Martinez, jordi.palet[at]theipv6company.com  The IPv6 Company

1.0 Summary of the Problem Being Addressed by this Policy Proposal

Since this policy was developed, the IPv4 addressing space has been exhausted, and the IPv6 deployment has evolved, so it doesn’t make sense to tie an IPv6 policy to the existence or IPv4 (same way as it is not tied the initial allocation policy).

In addition to that, because AFRINIC provided IPv6 PI at no cost to existing IPv4 PI holders, it may happen that the “default” assignment was requested without a proper addressing plan and this may not be the correct one at the implementation time.

 

2.0 Summary of how this proposal addresses the problem

This proposal updates the relevant text to accommodate the possibility to obtain IPv6 PI even if there is not IPv4 PI.

This proposal also adds a new section in order to allow a rectification of the initial assignment.

 

3. Proposal

Article 6.8 of the CPM will be modified as follows:

Current Proposed

6.8 PI Assignments

The current policy does not allow IPv6 provider independent (PI) address assignment to any 'end-sites'. In addition, lack of IPv6 transport will compel many 'end-sites' to tunnel. Thus, to avoid renumbering when IPv6 transport will be available, a provider independent assignment seems reasonable. More so, not all LIR's have IPv6 address space allocations. This makes it impossible for end-users to get PA IPv6 address space from such upstream (LIR's). This policy is also aimed at providing IPv6 address space to such end-users as long as they already have or qualify to get PI IPv4 addresses.

6.8 PI Assignments

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

6.8.1 Introduction

This policy 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.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.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 IPv6 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 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.
  4. The end-site must justify the need for the IPv6 PI address space.
  5. 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.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. If the 'end-site' plants to announce the IPv6 provider independent address space, it should not be disaggregated.

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.

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).

[Introduce new clause 6.8.4]

6.8.4. Rectifying the size of an initial assignment

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.

The new assignment will be consistent with the new plan and comply with 6.8.2 and 6.8.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:

  • 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;
  • 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.

 

4. Revision History

Date Details

28 March 2018

Version 1: AFPUB-2018-V6-004-DRAFT01

Initial Draft Posted to rpd.

 

5. References

Similar text exists and/or has been proposed in related policy documents at other RIR communities.

Discussions are taking place on the policy working group mailing list if you want to subscribe to the mailing send your subscription request to rpd-request [at] afrinic.net with 'Subscribe' as subject line


Mailing list archives can be found at https://lists.afrinic.net/pipermail/rpd