IPv6 as a criteria in IPv4 Soft Landing
Details
| Name of Proposal |
IPv6 as a criteria in IPv4 Soft Landing |
Status: | Under Discussion |
|
ID: |
AFPUB-2026-v6-001-DRAFT03 |
Date Submitted: |
17/09/2026 |
|
Author(s): |
Jordi Palet Martinez jordi.palet[at]theipv6company.com The IPv6 Company Jaco Kroon jaco[at]uls.co.za Ultimate Linux Solutions |
Version: |
3.0 |
|
Obsoletes: |
Amends: |
CPM |
1. Summary of the problem being addressed by this proposal
Current deployment of IPv6 in AFRINIC service region is very low compared with other parts of the world, despite the continuous efforts undertaken by AFRINIC.
Data from APNIC Labs:
- Average IPv6 World capability 44% (including Africa)
- 37%-51% depending on the region, about 50 countries exceed 50%)
- Africa IPv6 World capability 6%
- Only 8 countries exceed 20%, 15 countries 10-19%, 15 countries below 1%
At the same time, AFRINIC is under the Soft Landing policy, Phase 2 since 2020 and since then, 3 million IPv4 addresses have been recovered.
The Soft Landing policy restricts the requests of IPv4 addresses, and despite that, it has not clearly proven an increase of the IPv6 deployment, so it looks like further measures need to be enforced towards giving a strong push on that direction, aligned with the Soft Landing policy.
Community discussions often come back to the same question: Should we mandate IPv6 deployment for new IPv4 requests? It seems there is no plausible reason for not doing so.
2. Summary of how this proposal addresses the problem
This proposal adds a paragraph to the existing Soft Landing policy in order to enforce IPv6 deployment for those requesting new IPv4 resources, regardless of being an initial or subsequent request.
Proposal
3. Proposal
Amend article 5.4.4 of the CPM, as follows:
| Current | Proposed |
|---|---|
|
5.4.4 For any LIR or End User requesting IPv4 address space during the Exhaustion There is no explicit limit on the number of times an organization may request additional IPv4 address space during the Exhaustion Period. |
5.4.4 For any LIR or End User requesting IPv4 address space during the Exhaustion There is no explicit limit on the number of times an organization may request additional IPv4 address space during the Exhaustion Period. Any IPv4 request must be done with a simultaneous IPv6 request if the requesting party does not already have IPv6 space. Regardless of if the IPv6 request was already done previously or simultaneously with the IPv4 request, the relevant allocation/assignment criteria conditions must be met. In addition to the compliance with section 6.5, a credible IPv6 deployment and addressing plan, must be presented clearly showing specifically how will be met:
When applying for additional IPv4 space, the following conditions must be met as per the time frames from issuance of the first IPv6 space to LIRs and EUs, or {policy implementation date}, whichever is later. In the case of access networks, the percentage of customers that have access to global IPv6 delegations “without interference required from the Network Operator” must be at or above the following thresholds:
In the case of content hosting networks, the percentage of assigned IPv4 space assigned to those networks “also covered by IPv6 assignments” must reach:
In the case where a network provides both access and content hosting services, both criteria must be independently complied with. AFRINIC will establish as much as possible automated testing to verify the compliance, which will be complemented with existing public tools and measurements. Failure to comply with the IPv6 deployment plan according to the relevant criteria, once verified by AFRINIC, constitutes a policy violation. Notes, for the avoidance of doubt:
|
5. References
In other regions, all IPv4 addresses have been exhausted and it seems that the equivalent to the soft-landing is not any more an issue, because most of the existing members only can access IPv4 addresses via transfers. Some of them have waiting lists,
ARIN has a dedicated IPv4 pool (NRPM 4.10.) to facilitate IPv6 deployment, which only can be used for specific IPv6 deployment needs.
In LACNIC, a request for IPv4 must be accompanied by an IPv6 request (if it was not already done for that member). This was already part of the IPv4 policy even before the equivalent to the “Soft Landing” policy.
There are some other exceptions, like for example the mandatory deployment of IPv6 in IXPs.
Revision History
4. Revision History
| Date | Details |
|---|---|
| 22/05/2026 |
Version 1: AFPUB-2026-v6-001-DRAFT01 Initial Draft Posted to RPD |
| 14/06/2026 |
Version 2: AFPUB-2026-v6-001-DRAFT02 Updated following RPD discussion |
| 17/09/2026 |
Version 3: AFPUB-2026-v6-001-DRAFT03 Updated following RPD discussion and IA. Changed the criteria. |
AFRINIC Policy Impact Assessment
1. DPP Details
| Field | Details |
|---|---|
| Policy ID | AFPUB-2026-v6-001-DRAFT03 |
| Policy Name | IPv6 as a criteria in IPv4 Soft Landing |
| URL of Policy Proposal | https://www.afrinic.net/afpub-2026-v6-001-draft03 |
| Affected CPM Section | 6.4.4, 6.5.1.1.1, 6.5.1.1.2, 6.5.1.1.3, 6.5.1.1.4, 6.8.2.2.d |
| Version of IA | 1 |
2. Previous Versions — Impact Assessments
| Version | URL |
|---|---|
| v1 | This is the first recorded impact assessment for this proposal version. |
| AFPUB-2026-v6-001-DRAFT02 | https://www.afrinic.net/afpub-2026-v6-001-draft02#impact |
3. AFRINIC Staff Assessment
3.1 Staff Interpretation & Understanding of the Proposal
- The proposal keeps the current soft-landing approach that still allows IPv4 requests during the exhaustion period, but adds new eligibility conditions tied to IPv6 adoption. In practice, a new member requesting IPv4 would also need to request and justify IPv6. An existing member without IPv6 would need to do the same before qualifying for IPv4. The proposal further requires the requester to satisfy the relevant IPv6 allocation or assignment criteria and to submit a credible IPv6 deployment plan. For existing members that already hold IPv6, any additional IPv4 request would trigger a retrospective review of the member’s IPv6 needs and use.
- Any applicant requesting IPv4 must submit a simultaneous request for IPv6 address space if they do not already hold an IPv6 allocation or assignment. Regardless of whether IPv6 space is requested concurrently or was obtained previously, the applicant must satisfy the relevant IPv6 qualification criteria under CPM Section 6.5 (for LIRs) or Section 6.8 (for End-Users), notably sections 6.5.1.1.3, 6.5.1.1.4, and 6.8.2.2.d. The applicant must submit a credible IPv6 deployment and addressing plan. When applying for additional IPv4 space, the member must demonstrate progressive IPv6 rollout measured against explicit milestone thresholds. The compliance timeline begins from the date of issuance of the organisation’s first IPv6 space or the policy implementation date, whichever is later.
- The Resource members shall also self declare their access and hosting networks in their IPv6 request submission.
| Milestone Window | Access Networks (Customers with Global IPv6 Delegations) | Content Hosting Networks (IPv4 Space Covered by IPv6) | Combined Networks |
|---|---|---|---|
| Within 12 Months | 25% | 25% | Must independently satisfy both criteria (25% access / 25% hosting) |
| Within 24 Months | 50% | 50% | Must independently satisfy both criteria (50% access / 50% hosting) |
| Within 36 Months | 75% | 75% | Must independently satisfy both criteria (75% access / 75% hosting) |
| Within 48 Months | 95% | 95% | Must independently satisfy both criteria (95% access / 95% hosting) |
Measurement Unit for Content Hosting Networks:
The policy requires measuring the percentage of “assigned IPv4 space assigned to those networks also covered by IPv6 assignments.” This is calculated based on:
- Formal valid IPv4 sub-allocations and assignments (or assignments in the case of End-Users) registered in the AFRINIC WHOIS database
- Validity above is subject to BGP route origin announcements in the global routing table; or
- Active, reachable host infrastructure (e.g., matching DNS A and AAAA resource records for public service endpoints).
Measurement Criteria Definitions
- Access Networks: Measured as the percentage of customers with access to global IPv6 delegations “without interference required from the Network Operator” (all access network devices permit working IPv6 configurations, reachable from the global routing table).
- Content Hosting Networks: Measured as the percentage of assigned IPv4 space that is “also covered by IPv6 assignments” and reachable from the global routing table.
- Combined Networks: Networks providing both access and hosting services must independently track and comply with both tracks simultaneously.
Verification & Enforcement: AFRINIC is tasked with establishing automated testing mechanisms to verify compliance, supplemented by public measurement tools and routing data. Failure to meet IPv6 eligibility or to follow through on the deployment plan would make the organisation ineligible for IPv4 and would be treated as a breach of the Soft Landing Policy. Policy non-compliance triggers broader compliance enforcement under the contractual RSA framework.
Benefit to AFRINIC: The proposal aims to encourage concrete IPv6 deployment rather than passive IPv6 holdings, and introduces stronger accountability for organisations seeking scarce IPv4 resources during exhaustion. It may support AFRINIC’s broader policy and stewardship objectives by linking remaining IPv4 access to demonstrated IPv6 transition intent.
Impact on Resource Members:
Table below shows how IPv4 requests shall be treated:
| Applicant scenario | Current resources | IPv6 requirement before IPv4 evaluation | IPv4 evaluation / approval trigger | Notes |
|---|---|---|---|---|
| 1. Not yet a member | None | Submit a simultaneous IPv6 request and satisfy existing IPv6 policy conditions, with a credible IPv6 deployment plan based on access, content, or both criteria. | IPv4 prefix request is evaluated only after successful evaluation of the IPv6 request. | Applies to new applicants requesting IPv4. |
| 2. Resource member with IPv4 and/or ASN, but no IPv6 prefix | IPv4 and/or ASN; no IPv6 prefix | Submit a simultaneous IPv6 request and satisfy existing IPv6 policy conditions, with a credible IPv6 deployment plan based on access, content, or both criteria. | Additional IPv4 request is evaluated only after successful evaluation of the IPv6 request. | Applies to existing members requesting additional IPv4. |
| 3. Resource member with IPv4 and/or ASN and one IPv6 prefix not in use | IPv4 and/or ASN; one IPv6 prefix not in use | Submit addressing and deployment plans that satisfy existing IPv6 policy conditions and the proposal’s access, content, or both criteria. | Additional IPv4 request is evaluated after successful evaluation of the submitted addressing and deployment plans. | AFRINIC first assesses usage of the existing IPv6 prefix. |
| 4. Resource member with IPv4 and/or ASN and one IPv6 prefix in use | IPv4 and/or ASN; one IPv6 prefix in use | IPv6 usage is evaluated in accordance with the policy, and registered IPv6 assignments may need to be restructured to fit access, hosting, or both criteria. | Additional IPv4 request proceeds after IPv6 usage has been evaluated and assignments are aligned with the criteria. | Restructuring of IPv6 assignments may be required before IPv4 evaluation can continue. |
| 5. Subsequent additional IPv4 request before 12 months have lapsed | Previously allocated IPv4; IPv6 deployment plan on record | For the previous prefix allocated/assigned post implementation date, AFRINIC verifies access, content, or both deployment against the submitted IPv6 deployment plan. | Additional IPv4 evaluation can happen against applicable IPv4 policies after AFRINIC verifies deployment against the plan. | Verification is conducted against the submitted plan prior to the first annual milestone window. |
| 6. Subsequent additional IPv4 request after 12 months have lapsed | Previously allocated IPv4; IPv6 deployment plan on record | AFRINIC verifies IPv6 deployment progress according to the relevant yearly milestones, such as 25%, 50%, etc. | Additional IPv4 can be approved after AFRINIC verifies milestone-based deployment progress. | Verification is tied to the elapsed period and expected deployment percentage. |
| 7. No subsequent additional IPv4 request | Existing resource member | Resource member remains required to comply with the policy. | No new IPv4 evaluation is triggered. | Compliance obligation continues even without a further IPv4 request. |
| 8. Standalone IPv6 request or renumbering request | Any existing resource status | Not impacted by this proposal. | No IPv4 evaluation is triggered by the standalone IPv6 or renumbering request. | Recommended to maintain a deployment plan aligned with the proposal in case of future IPv4 requests. |
Constraints
- Resource Members without immediate IPv6 deployment plans would be required to justify IPv6 resources and provide additional operational evidence of IPv6 deployment before receiving IPv4. This creates a more demanding request process, especially for members with limited IPv6 capability, limited expertise, or infrastructure constraints.
- Increasing the operational complexity of obtaining additional IPv4, both at AFRINIC and resource members level, may also push resource members to consider leasing IPv4 from the market potentially undermining registry accuracy and the role of AFRINIC as the authoritative RIR.
- The policy may disproportionately affect smaller operators, including WISPs, whose device compatibility, commercial realities, or technical readiness could delay IPv6 deployment even where the need for IPv4 remains operationally genuine. Staff considers that this may create tension with CPM fairness objectives, particularly where otherwise justified applicants are denied IPv4 because of practical barriers to IPv6 rollout.
3.2 Areas of Impact
3.2.1 Interaction with Existing CPM
- CPM 6.5.1.1.1 to 6.5.1.1.4: These LIR-related IPv6 qualification clauses become directly relevant to IPv4 eligibility under the proposal, creating a tighter policy coupling between IPv4 exhaustion handling and IPv6 allocation conditions.
- CPM 6.8.2.2.d: End-user IPv6 qualification also becomes a gating condition for IPv4, expanding the operational scope of IPv6 evaluation.
This interaction materially changes how staff would assess IPv4 requests during exhaustion by making IPv6 readiness and deployment evidence part of the decision path.
3.2.2 Interaction with Other DPPs Under Discussion
No direct interaction with other DPPs under discussion has been identified at this stage.
3.2.3 Impact on IP Numbers Registry Systems
| System | Impact |
|---|---|
| WHOIS | None |
| RDAP | None |
| MyAFRINIC (Hostmaster, Member Portal, Transfer Tool) | Workflow and user-interface changes will be required to support linked IPv4 and IPv6 request handling, capture deployment and addressing plans, trigger retrospective reviews, and generate internal notifications or compliance tasks. |
| NetSuite | Billing and integration updates may be required depending on whether simultaneous IPv4 and IPv6 evaluation or additional review steps affect membership and resource processing flows. |
| NMRP | Process updates will be required to reflect new resource request criteria and retrospective review conditions. |
| IPv6 addressing Plan tool | Updates to ensure that Resource Members also add their deployment plans. |
| RPKI | None |
3.2.4 Member Services Operations
- Procedures: The Member Services IPv4 and IPv6 resource evaluation procedures will require revision. Retrospective evaluation of previously allocated or assigned IPv6 resources, together with review of deployment plans and compliance evidence, will add significant workload and complexity.
- Contractual Agreements: No contractual updates have been identified from the current text.
- Website & Communications: Public web content, process guidance, FAQs, and implementation communications will need updates. Members will need clear explanations of new evidence requirements, review triggers, and the consequences of non-compliance.
3.2.5 IT
IT changes are expected primarily in MyAFRINIC and related internal workflow tooling. The request flow would need to support simultaneous or linked IPv4 and IPv6 submissions, structured capture of deployment-plan information, review checkpoints, and internal status tracking. Depending on implementation choices, IT may also need to support reminder notifications, compliance milestone tracking, and auditable decision records.
3.2.6 HR
The proposal is likely to require additional staff capacity and targeted training, particularly for Hostmasters involved in evaluating request justification and deployment evidence. Training would need to cover the new policy logic, interpretation standards, evidence assessment, and consistent handling of retrospective reviews. If the expected case volume increases materially, additional recruitment may be required.
3.2.7 Legal
No obvious or direct contravention of the Companies Act 2001 or AFRINIC’s Bylaws in the proposal has been observed, yet the following two points require attention and clarification for certainty reasons:
- It is recommended that the requirement to submit a “credible” IPv6 deployment plan be sufficiently clear to allow applicants to understand what evidence is required and how AFRINIC will assess it. Put simply, the assessment criteria must be known in advance and sufficiently objective to prevent arbitrary or inconsistent decisions at operational level.
- The proposal provides that “Regardless of if the IPv6 request was already done previously or simultaneously with the IPv4 request, the relevant allocation/ assignment criteria conditions must be met”. It is unclear, from the present text, whether this requirement is intended to apply retrospectively to existing allocations or assignments, or prospectively to new requests only. In my view, retrospective application may raise concerns regarding legal certainty, legitimate expectations and the proportionality of imposing new obligations on resources validly allocated under the existing policy framework. In case the intention is to impose additional compliance obligations on existing resource holders, the proposal should explain the justification for doing so and specify any applicable transitional arrangements. This is particularly important if non-compliance could affect existing resource entitlements.
3.2.8 Finance
Financial impact is expected from staff training, and potentially increased operational headcount. Ongoing costs may include additional review time per request, and member support effort. A detailed cost estimate would depend on the final policy wording and the level of automation required.
4. Recommendations on Policy Wording
- The use of the term “credible” is open to different interpretations and may introduce unnecessary ambiguity. The existing sections of CPM already prescribe minimum initial allocation (/32) and assignment sizes (/48), while we have the IPv6 planner developed internally and shared with the applicants, and other BCPs provide guidance for evaluating larger resource requests. Furthermore, the proposal explicitly defines the minimum deployment expectations with thresholds from 25% and upwards over a 48-month period. In view of this, we recommend that the term “credible” be removed as it opens an additional subjective criterion.
- The automated testing and verification of policy compliance are not straightforward. AFRINIC is likely to encounter networks with strict filtering policies, making it difficult to establish whether IPv6 deployment milestones have been achieved. Furthermore, there is no guarantee that resource members will relax their network security or filtering rules to facilitate this verification. Consequently, manual verification of content hosting network assignments, while possible, would place a substantial operational burden on both AFRINIC staff and resource members.
5. Staff Clarification Requests
The following clarification is requested from the DPP authors:
- How should AFRINIC treat cases where IPv6 deployment delays are caused by upstream dependencies, customer equipment limitations, vendor supply constraints, or market conditions outside the member’s direct control?
- Could the author clarify how the deployment compliance in the proposal eases the resource members access to IPv4 during exhaustion?
- Taking into consideration that a resource member may have received one or more IPv4 prefixes in the initial 12 months upon providing an IPv6 deployment plan, can the author clarify what consequences or reclaim procedures apply to these allocations if the member is subsequently found to be in breach of this policy (i.e. by failing to meet the IPv6 deployment milestones)? In addressing this, the author is requested to refer to the legal considerations outlined in Section 3.2.7 (point 2) of this assessment.
- Could the author clarify if the proposal also applies to intra and inter RIR transfers where the recipient is in the AFRINIC service region?
6. Implementation Plan
6.1 Timeline
A high-level implementation period of approximately 6 months is anticipated from ratification to production readiness.