Summary
- On 17 June 2016 Andrew Alston and Christopher Mwangi filed AFPUB-2016-GEN-002-DRAFT-01, the Inbound Transfer Policy, whose clause 3.2 required whoever received transferred address space to plan the use of at least half of it within five years.
- The proposal drew no consensus at AFRINIC-25 and again at AFRINIC-26, then expired in 2017 under section 3.4.1 of the Consolidated Policy Manual. Section 5.7, implemented on 22 February 2018, imposes twelve-month bars on the party giving space up.
A header block with two names on it
The document is short. The interesting part is the top of it. AFRINIC's proposal record lists AFPUB-2016-GEN-002-DRAFT-01, the Inbound Transfer Policy, submitted 17 June 2016, with Andrew Alston and Christopher Mwangi named as authors (proposal record). The same day, Alston posted the draft to the registry's policy discussion list: "The following has been submitted to policy-submission and I am also posting it here for discussion in the mean time" (rpd, 17 June 2016).
Two names, no split. Nothing in the record assigns a proportion of the drafting to either author, and this article does not invent one. What the record does show is who filed it, when, and where it went next.
What the draft would have required
Three clauses carry the design. Clause 3.1 provides that "AfriNIC shall accept all inbound transfers of all resources explicitly referred to in section 2". Clause 3.2 is the one to read twice: for transfers into the region, "the recipient of IP space (v4 or v6) must provide a plan to AfriNIC for the use of at least 50% of the transferred resource within the next 5 years." Clauses 3.3 and 3.4 extend the logic, counting transferred space in the recipient's normal allocations for membership-size evaluation and in any later allocation evaluation (draft text).
Read as a design, that is a rule about what happens after the space arrives. The obligation sits on the organisation that receives the resource, and it is measured in future utilisation over a stated period.
The room said no, twice
The proposal went to a public policy meeting and came back. The AFRINIC-25 minutes record the Inbound Transfers Policy presented by Alston and Mwangi with a co-chair decision of "No Consensus" and the proposal returned to the mailing list (AFRINIC-25). The AFRINIC-26 minutes record the same proposal, AFPUB-2016-GEN-002-DRAFT-01, again decided No Consensus and again returned to the list (AFRINIC-26).
The minutes state the decisions. They do not, in the passages read, state the grounds. What the floor argued about on each occasion is therefore not something this article characterises; the minutes are cited for the outcome, not for a rationale the captured text does not carry.
Then the clock ran out
At this point the record stops being about consensus and becomes procedural. In 2017 the Policy Development Working Group co-chairs announced that, "in line with section 3.4.1 of the Consolidated Policy Manual", the Inbound Transfers Policy "completed the timeout period of one calendar year without updates to the draft version", that the only version received was dated June 17, 2016, and that the proposal had been moved from Proposals Under Discussion to Obsolete Proposals (expiry notice). The status field on the proposal's own record reads Expired.
An expired proposal writes nothing into the manual. That is the negative result at the centre of this piece, and it is a fact about a document, not a verdict on a person.
What actually governs
The governing section is written the other way round. The Consolidated Policy Manual, version 1.6, published 17 November 2020 and labelled Current, carries section 5.7, "IPv4 Resources transfer within the AFRINIC Region" (manual). The clauses, as that page returns them:
- 5.7.1 applies the policy to "an organization with a justified need for IPv4 resources that cannot be satisfied by AFRINIC";
- 5.7.2 requires the resources to come "from an existing AFRINIC member's account or from a Legacy Resource Holder in the AFRINIC service region";
- 5.7.3.1 requires the source to be "the current rights holder of the IPv4 address resources recognized by AFRINIC, and not be involved in any dispute as to the status of those resources";
- 5.7.3.2 bars the source from further AFRINIC IPv4 allocations or assignments for 12 months after approval;
- 5.7.3.3 bars the source where it received an AFRINIC IPv4 transfer, allocation or assignment in the 12 months before approval, with mergers and acquisitions excluded;
- 5.7.4.1 requires AFRINIC to approve the recipient's need and the recipient to justify its usage;
- 5.7.4.2 requires the recipient to be an AFRINIC member and to sign the Registration Services Agreement;
- 5.7.4.3 provides that transferred IPv4 legacy resources cease to be regarded as legacy.
AFRINIC announced implementation of that policy on 22 February 2018 (implementation notice). Its operational transfer page still points at section 5.7 and adds a minimum transferable size of a /24 for end-site recipients and a /22 for LIR recipients "as per current policies" — figures that appear on the service page and not in the manual passage read, so they are quoted as operational guidance rather than as manual text (transfer service).
The asymmetry, stated plainly
Here the two documents stop resembling each other. The draft asked the receiver for a five-year utilisation plan. Section 5.7 asks nothing of the sort. It asks the giver to be the rights holder, to be free of a status dispute, and to accept a twelve-month exclusion on both sides of the approval date.
Our reading, and it is a reading rather than a registry rule: 5.7 treats the party leaving with the resources as the risk-bearing party. Approval is a conjunction, and the heavy terms sit on the source. The two time bars are the plainest expression of it, since a member that transfers space accepts a cost for having recently acquired it and a further cost for acquiring more.
That is a defensible design for a registry administering scarcity: every source-side predicate is checkable on the day of the request, while a five-year utilisation plan is checkable only much later. It is also a different design from the one filed in 2016, and the difference is available to anyone with both pages open.
The edge that is still open
One complication belongs in the body, not a footnote. A later unified policy, AFPUB-2020-GEN-006-DRAFT03, dated 22 November 2021 and authored by Gregoire Olaotan Ehoumi, Noah Maina and Adeola A. P. Aina, states that it obsoletes section 5.7 and appears on its page with the status Ratified (unified policy). AFRINIC's current policy-proposals table lists the same document as Ratified with the remark "Awaiting Implementation" (proposals table). The operational transfer page still cites section 5.7.
No page read establishes that the 2021 policy has taken effect. Until one does, section 5.7 remains the section AFRINIC's own paperwork points operators toward, and it is the text this comparison runs against.
What an operator should take from it
Before signing a transfer into or out of the region, read the time bars, not the utilisation language. 5.7.3.2 and 5.7.3.3 decide whether a member can transfer now and still receive allocations later, and both attach to the source. The recipient's exposure is narrower: need justification, membership, the Registration Services Agreement, and the loss of legacy status on the transferred block.
The 2016 draft would have put a five-year clock on the buyer. It expired, and nothing replaced it in the manual.
Member Briefing
Read the full trend briefing
Members read the full briefing with the source notes behind every finding.
Strategic Circle
A daily briefing in your language, built from changes we have verified.
Join for USD 20/monthCancel anytime.
Members also get the full research library, a daily briefing on the networks they follow and the private forum.






