AFRINIC · RIR Watchdog
AFPUB-2020-GEN-006-DRAFT03
Start here for the proposal-by-proposal record: what changed, why it mattered, who argued for what, how positions evolved, what was decided, and where the evidence still has gaps.
Source facts
- Policy ID
- AFPUB-2020-GEN-006-DRAFT03
- RIR
- AFRINIC
- Official status
- Ratified
- Normalized status
- Accepted
- Introduced
- Nov 22, 2021
- Last source update
- Oct 15, 2026
- Coverage
- Partial
Who actually shaped the debate?
Policy evolution
Definition of scarce resources · Draft 2 splits the resource definition into a reference to scarce resources and a definition covering IPv4 addresses and ASNs, renumbering the following definitions. Draft 1 already covered those two resource classes. This is a terminology clarification, not a newly introduced ASN-transfer power or an extension to IPv6. The regional, reserved, legacy and global categories and the direction-specific transfer rules remain.
Source facts −
3.1.1 "Resource" refers to IPv4 Address space or Autonomous System Numbers.Source facts ↗
Source facts +
3.1.1 “Resource” refers to "scarce resource" 3.1.2 "Scarce resource" are IPv4 Address space and Autonomous System Numbers.Source facts ↗
First retained staff assessment and unresolved abuse controls · The first-draft capture says its staff assessment is still to come. The second includes an assessment dated 27 October 2021, which identifies ambiguities in resource categories and transfer types and warns that the absence of a hold-down period could permit repeated transfers before justified use. These are newly available staff findings; the draft does not thereby acquire a hold-down rule or prove that any abuse occurred.
Source facts +
Absence of “hold down” time of new allocations/assignments and transferred resources may lead to abuse of the registry before a resource can be put to an effective justified need.Source facts ↗
Legal assessment of legacy resources and responsibility · The added legal assessment questions the practical reach of obligations over legacy holders who do not register voluntarily, the treatment of legacy status on inward transfer, and the allocation of due-diligence responsibility. It proposes a limited facilitating role for AFRINIC. These are the assessment’s concerns and recommendations, not a judicial determination or proof that the proposed allocation of responsibility became binding.
Source facts +
Thus, the authors should bear in mind that obligations impacting on legacy resource holders may not necessarily achieve the intended results if the legacy resource holders refuse to opt for voluntary registration of the transfer with AFRINIC.Source facts ↗
Counterpart transfer compatibility · The new assessment records full reciprocity with APNIC, compatibility with RIPE NCC without a reciprocity requirement, unconfirmed compatibility with LACNIC, and a reciprocity problem with ARIN because some outbound categories remain prohibited. Those differences qualify the proposal’s inter-regional transfer objective. They are recorded assessments for this version, not evidence that transfers were operational or that another registry accepted a later version.
Source facts +
ARIN - This proposal continues to allow general inward transfer of number resources from ARIN-region entities but prohibits the transfer out of some categories. Thus, this proposal is not reciprocal with ARIN, as ARIN does not have a restriction on outgoing Inter-RIR transfers (apart from those resources in our reserved pools.)Source facts ↗
Implementation estimate and operational work · The second-draft assessment describes changes to transfer workflows, tagging, forms, hostmaster tools, staffing and agreements, and gives Q4 2022 on MyAFRINIC V2 as its earliest implementation estimate. The first-draft capture contains no completed assessment or comparable timetable. The estimate and planned work must remain distinct from a deployment date or proof that those systems were delivered.
Source facts +
4.0 Implementation Timeline - Earliest we can implement same will be in Q4 2022 on MyAFRINIC V2 based on the updated planSource facts ↗
Draft dates and retained archival status · The revision history places draft 1 on 17 October 2020 and draft 2 on 8 October 2021, while their submitted-date headers show 27 October 2020 and 14 October 2021. Preserve that disagreement instead of presenting either header as an uncontested revision date. Both captures are marked Archived; that label does not establish a rejection, ratification or implementation decision.
Source facts −
17 Oct 2020 Version 1: AFPUB-2020-GEN-006-DRAFT01 - Initial draft submitted to RD mailing list.Source facts ↗
Source facts +
8 Oct 2021 Version 2: AFPUB-2020-GEN-006-DRAFT02 * Change author email address. * Update the referencesSource facts ↗
Scope of the definitions and inbound resource category · Draft 3 expressly limits its definitions to this proposal section and replaces the inbound-transfer term Any with the defined category Others. This responds to wording concerns in the earlier assessment without changing the basic regional, reserved, legacy and global framework. The later assessment still calls the definition of Others vague, including how incoming legacy resources lose legacy status; the substitution does not resolve every interpretation issue.
Source facts −
3.3.5 If the source is from another region and the recipient is AFRINIC member, then allow "Any", and then mark the transferred resources as "Global".Source facts ↗
Source facts +
3.3.5 If the source is from another region and the recipient is an AFRINIC member, then allow "Others", and then mark the transferred resources as "Global".Source facts ↗
Transfer qualification cross-reference · The resource-qualification condition now points expressly to section 3.3. The earlier assessment had called the unqualified reference to a type of transfer ambiguous, and the corresponding comment is absent from the later assessment. The new cross-reference makes the existing selection rules easier to apply; it does not add a new transfer category, remove reserved-pool restrictions or change the /24 minimum.
Source facts −
3.4 Conditions on resources to be transferred The size of the IPv4 address prefix should be a minimum of /24. The resource must qualify for the type of transfer requested.Source facts ↗
Source facts +
3.4 Conditions on resources to be transferred The size of the IPv4 address prefix should be a minimum of /24. The resource must qualify for the type of transfer requested as defined in 3.3.Source facts ↗
Source-holder entitlement and contemplated disputes · Draft 3 replaces the short requirement for the right holder with no disputes with an explicit rightful-holder requirement covering disputes that are known or contemplated. This follows the earlier staff wording recommendation and makes the condition more explicit. It does not determine ownership in a particular case or establish how a contemplated dispute would be proved.
Source facts −
3.5 Conditions on the source Must be the right holder of the resources to be transferred with no disputes.Source facts ↗
Source facts +
3.5 Conditions on the source The source holder must be the rightful holder of the resources being the subject of the transfer and that the resources must not be the subject of any dispute, known or contemplated.Source facts ↗
Assessment timetable and outstanding implementation issues · The assessment attached to draft 3 is dated 28 February 2022 and replaces the earlier Q4 2022 estimate with an estimate of twelve months. It retains concerns about the absent hold-down period, legacy-resource treatment and operational changes. Its legal subsection still calls the proposal Draft 2, and its reciprocity section contains an April 2026 update placeholder. Those internal date and version inconsistencies limit what the capture establishes; neither timetable proves implementation.
Source facts −
4.0 Implementation Timeline - Earliest we can implement same will be in Q4 2022 on MyAFRINIC V2 based on the updated planSource facts ↗
Source facts +
4.0 Implementation Timeline: The proposal will take 12 months to be implemented.Source facts ↗
Ratified status and authorship; unchanged third-draft rules · The later third-draft capture changes the header from Archived to Ratified, names Gregoire Olaotan Ehoumi, Noah Maina and Adeola A. P. Aina, and explicitly identifies version 3 as superseding CPM section 5.7. Its submitted-date header now agrees with the revision history’s 22 November 2021. The operative transfer rules and attached staff assessment are unchanged. The added ratified-policy table also lists other proposals; their dates and implementation remarks must not be attributed to this one. These changes establish the capture’s reported ratification status, not an implementation date or completed reciprocal transfer arrangements.
Source facts −
ID AFPUB-2020-GEN-006-DRAFT03 Date Submitted 2021-10-14 Author(s) Refer to Proposal Tab Status ArchivedSource facts ↗
Source facts +
ID AFPUB-2020-GEN-006-DRAFT03 Date Submitted 22 Nov 2021 Author(s) Gregoire Olaotan Ehoumi, Noah Maina, Adeola A. P. Aina Version 3 Obsoletes IPv4 Resources transfer within the AFRINIC Region (Section 5.7 of the CPM) Status RatifiedSource facts ↗
Debate timeline
Entities
- Discussion messages0First activityUnknownLast activityUnknownFirst explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies0Freshness: Stale
Last research attempt: Sep 11, 2026
Identity verified: Sep 11, 2026
· Historical Policy Policy Development (PDP) Global Policies Consolidated Policy Manual Current Proposals Policy Archive PPM Minutes Appeal Committee AF 37 Presentation 2026 Proposals IPv4 Soft Landing Amendment of Utilisation AS-SETs Hierarchical Names PDP WG Guidelines IPv6 in Soft Landing Policy Compliance Dashboard IPv4 Pools Exhaustion AFPUB-2020-GEN-006-DRAFT03: AFRINIC Number Resources Transfer Policy Details Proposal Revision History AFRINIC Policy Impact Assessment Implementation Proposal Details Proposal Name AFRINIC Number Resources Transfer Policy ID AFPUB-2020-GEN-006-DRAFT03 Date Submitted 22 Nov 2021 Author(s) Gregoire Olaotan Ehoumi, Noah Maina, Adeola A.
www.afrinic.netVerified public profiles
- Discussion messages
- 0
- First activity
- Unknown
- Last activity
- Unknown
- First explicit stance
- Unknown
- Latest explicit stance
- Unknown
- Stance changes
- 0
- Viewpoint consistency
- No explicit position stated
- Other policies
- 0
First explicit stance: Unknown → Latest explicit stance: Unknown · Stance changes: 0
Viewpoint consistency: No explicit position stated
- Oct 15, 2026
author
Source facts ↗
Per-policy stance timelines:AFPUB-2020-GEN-006-DRAFT03 · Unknown · No explicit position statedTotal policy messages: 0
- Discussion messages0First activityUnknownLast activityUnknownFirst explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies3
- Discussion messages0First activityUnknownLast activityUnknownFirst explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies2
Sources and coverage
Official policy sources
Public discussion archives
- afrinic-rpd
- Earliest captured
- Aug 4, 2004
- Latest captured
- Aug 25, 2026
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 13,088
- Known gaps
- 0
- www.afrinic.net
- afrinic-africann
- Earliest captured
- Aug 3, 2026
- Latest captured
- Oct 2, 2026
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,478
- Known gaps
- 0
- afrinic-afripv6-discuss
- Earliest captured
- Aug 17, 2015
- Latest captured
- Sep 18, 2026
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,538
- Known gaps
- 0
- afrinic-announce
- Earliest captured
- Aug 18, 2015
- Latest captured
- Sep 18, 2026
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,497
- Known gaps
- 0
- afrinic-community-discuss
- Earliest captured
- Sep 11, 2015
- Latest captured
- Dec 29, 2019
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,127
- Known gaps
- 0
- afrinic-dbwg
- Earliest captured
- Aug 4, 2026
- Latest captured
- Oct 6, 2026
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 966
- Known gaps
- 0
- afrinic-dnssec-ops
- Earliest captured
- Aug 18, 2015
- Latest captured
- Dec 1, 2016
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 307
- Known gaps
- 0
- afrinic-icp2-review
- Earliest captured
- Apr 10, 2025
- Latest captured
- Nov 10, 2025
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 0
- Known gaps
- 0
- afrinic-measurement-wg
- Earliest captured
- Feb 1, 2018
- Latest captured
- Nov 22, 2024
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 138
- Known gaps
- 0
- afrinic-mira
- Earliest captured
- Nov 17, 2020
- Latest captured
- Nov 22, 2024
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 0
- Known gaps
- 0
- afrinic-ois-wg
- Earliest captured
- Sep 9, 2021
- Latest captured
- Nov 22, 2024
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 0
- Known gaps
- 0
- afrinic-rpki-discuss
- Earliest captured
- Jan 15, 2016
- Latest captured
- Apr 23, 2026
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 154
- Known gaps
- 0
Coverage
Partial
Earliest captured: Aug 4, 2004
Latest captured: Oct 15, 2026
Freshness
Known gaps
- www.afrinic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- www.afrinic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- afrinic-rpd: Source coverage is incomplete. · The source boundary has not yet been reached.
- www.afrinic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- afrinic-africann: Source coverage is incomplete. · The source boundary has not yet been reached.
- afrinic-afripv6-discuss: Source coverage is incomplete. · The source boundary has not yet been reached.
- afrinic-announce: Source coverage is incomplete. · The source boundary has not yet been reached.
- afrinic-community-discuss: Source coverage is incomplete. · The source boundary has not yet been reached.
- afrinic-dbwg: Source coverage is incomplete. · The source boundary has not yet been reached.
- afrinic-dnssec-ops: Source coverage is incomplete. · The source boundary has not yet been reached.
- afrinic-measurement-wg: Source coverage is incomplete. · The source boundary has not yet been reached.
- afrinic-rpki-discuss: Source coverage is incomplete. · The source boundary has not yet been reached.
