Info! Please note that this translation has been provided at best effort, for your convenience. The English page remains the official version.

About Proposal "IPv4 Soft Landing BIS"

Print Friendly, PDF & Email

Summary of the Problem Being Addressed by this Policy Proposal

The soft-landing policy ratified by the board on the 11/11/2011 describes how AFRINIC should manage allocations/assignments from the last /8. It defines 2 phases of IPv4 exhaustion. During phase 1, it sets the maximum to be /13 instead of /10 and in phase 2, the maximum to /22 and the minimum to /24. It makes no difference between existing LIRs or End-Users and new ones. The policy also does not impose IPv6 deployment.

IPv4 exhaustion in other regions combined with other factors has imposed huge pressure on the AFRINIC IPv4 pool with requests for large IPv4 blocks, with very little IPv6 deployment. The pressure on the AFRINIC IPv4 pool has led to some policy proposals to reserve some blocks for certain sub-communities.

 

Ref. Name:
AFPUB-2016-V4-001-DRAFT07

Versions: 7.0 

Status: Withdrawn  

Author:

- Omo Oaiya, omo[at]wacren.net, WACREN
- Joe Kimaili, jkimaili[at]ubuntunet.net, Ubuntunet Alliance
- Alain P. Aina, aalain[at]trstech.net, TRS

 

Obsoletes: CPM 5.4

Submitted:
01 December 2017

 

 

Revision History

09 FEB 2016

AFPUB-2016-V4-001-DRAFT01 (Version 1.0)

Version 1 posted to the rpd mailing list

16 FEB 2016

AFPUB-2016-V4-001-DRAFT02 (Version 2.0):
A complete new version of the section 3 and so the policy proposal now obsoletes the existing IPv4 Soft landing policy instead of amending it.

22 JUL 2016

AFPUB-2016-V4-001-DRAFT03 (Version 3.0):

Maximum Allocation/Assignment size changed from /15 to /18 in phase 1 as per discussions at AFRINC-24 public policy meeting and follow on discussions on RPD.

14 APR 2017

AFPUB-2016-V4-001-DRAFT04 (Version 4.0):

  1. Updated version based on consensus from online and AFRINIC-25 discussions.
  2. Formatted for direct insertion to CPM
  3. “current Phase” replaced by “Pre-exhaustion Phase”
  4. No more direct reserve for critical Internet Infrastructures
  5. No more direct reserve for New entrants
  6. A dedicated reserve to facilitate IPv6 deployment

27 JUN 2017

AFPUB-2016-V4-001-DRAFT05 (Version 5.0):

  1. Introduced “Allowable Limits & Recurrence” – clauses 5.4.6.1 and 5.4.6.2 (a 24-month waiting period for a member that has received the maximum allocation limit per phase to return for more space).
  2. Restored minimum assignment/allocation size in exhaustion to /24
  3. Removed definition of “Core DNS Services provider” and other definitions that were not necessary.
  4. Addressed most issues in the staff assessment report of AFPUB-2016-V4-001-DRAFT04

 

22 SEP 2017

AFPUB-2016-V4-001-DRAFT06 (Version 6.0):

  1. Clarified 5.4.3 on the issue of demonstrated need applying to all phases, and in-line with other sections of the CPM
  2. Reworded 5.4.6 for better clarity.
  3. Reworded 5.4.7 to clarify some provisions of the /12 reserve (That the previous reserved /12 is replaced by the one in this proposal).

01 Dec 2017

AFPUB-2016-V4-001-DRAFT07 (Version 7.0):

(Last Call)

  1. Reword 5.4.7.1 to remove specific reference to “XLAT translators”
  2. Add “including IDN ccTLDs” to 5.4.7.5.3
Last Modified on -
Date and time in Mauritius -