Topic
IPv4 Scarcity Economics
Within the Topic facet, IPv4 Scarcity Economics topic intelligence connects articles that share a specific subject, signal focus, or monitoring theme. The page gives readers a richer path through related reporting, source evidence, market actors, and infrastructure implications, with enough context to understand why the topic matters across company movements, governance decisions, regional exposure, and operational risk. Readers can compare recurring signals, affected organisations, public evidence, market context, service continuity, procurement, competition, compliance, and strategic planning questions behind the subject instead of stopping at a thin list of matching articles. It explains what the topic covers, which infrastructure actors or policies are involved, what evidence supports the coverage, and why the subject may matter for operators, customers, investors, and policy readers.
Story
The text that consensus had not yet finished: AFRINIC-12 and Soft Landing
In Kigali, the decisive word was not simply “consensus” but the qualification that followed it: the IPv4 Soft Landing proposal had consensus with modifications. That formulation moved the proposal forward while leaving consequential language to be settled after the room had…
Story
AFRINIC called the ASN amendment implemented before it became global policy
AFRINIC called the ASN amendment implemented before it became global policy intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may…
Story
AFRINIC-11 sent Soft Landing back a second time
On 27 November 2009 in Dakar, a substantially revised IPv4 Soft Landing proposal failed to reach consensus for the second public meeting, leaving evidence consistent with a dispute that had moved beyond drafting detail to the limits of what a private registry should decide when…
Story
After the Withdrawal: AFRINIC-11 and the Missing Fiscal Handoff Ledger
In Dakar, a technical policy proposal was withdrawn and its affordability problem was handed to an author, staff and a private Board; the enduring question is not whether that boundary was sensible, but whether the alternative ever became visible enough to audit.
Story
The Cairo no-consensus finding AFRINIC’s record cannot reconstruct
On 21 May 2009 in Cairo, the IPv4 Soft Landing proposal was recorded as having failed to reach consensus and was returned to the RPD mailing list for further discussion. That procedural disposition is clear. The official record does not preserve the objections, the assessment…
Story
A /48 for local networks—and a subsidy with no named payer
AFPUB-2009-v6-001 tried to solve a precise access problem with a technically disciplined IPv6 offer. Its unresolved question was not the size of the address block, but who would finance the special path and on whose authority.
Story
Soft Landing's 13 May revision and the eight-day review window
Douglas Onyango’s 13 May 2009 revision of Soft Landing did more than polish a familiar proposal. It changed the practical test for further IPv4 allocations, fixed /23 as both minimum and maximum, introduced overlapping four-allocation limits, removed a critical-infrastructure…
Story
AFPUB-2009-v4-001 implemented the final-/8 allocation formula
On 6 March 2009, AFRINIC recorded AFPUB-2009-v4-001 as implemented while the ICANN Board ratified the same global policy and directed staff to implement it. The rule protected one final /8 for each of the five regional Internet registries, but it did not attempt to make the needs…
Story
AFRINIC-10 and the Recovered-IPv4 Return Formula
In Cairo on 21 May 2009, AFRINIC-10 recorded approval of AFPUB-2009-v4-002, a proposal for returning recovered IPv4 blocks to an IANA pool and reallocating them among eligible Regional Internet Registries. The proposal offered an unusually precise answer to a real scarcity…
Story
The first Soft Landing proposal turned AFRINIC's future final /8 into a rationing instrument
On 7 January 2009, an email to AFRINIC's policy list converted a distant shortage into a design problem: when ordinary allocation could no longer avoid the prospective final /8, who should receive how much, under which conditions, and with what protection for whoever arrived…
Story
The Number AFRINIC-7 Did Not Decide
AFRINIC-7 exposed a consequential gap between agreement on an IPv4-exhaustion policy direction and authorization of the quantity that would make the proposal operative.
Story
AFPUB-2007-GEN-001 cut the allocation and assignment planning horizon from two years to one
AFRINIC’s 2007 change looked like a simple adjustment to a forecast period. In operation, however, the difference between accepting two years of prospective need and accepting one year changed both how much uncertain demand could enter a single decision and how soon a growing…
Story
What AFRINIC’s 9–5–1 hand count did—and could not—establish
On 27 September 2007, a show of hands at AFRINIC-7 gave one IPv4-exhaustion proposal the larger recorded response, but the surviving numbers cannot answer the question later claims of mandate would require: larger among whom, under what response rules, and with what checkable…
Story
The bylaw bridge from registry policy to membership termination arrived in 2012, not 2007
AFRINIC’s archive reveals a consequential constitutional change in two stages: a broad Associate Member termination-and-return structure in the instrument labelled 2007, followed in 2012 by an express clause making compliance with Number Resources Management Policies a condition…
Story
The name behind the ledger: what AFRINIC’s 2007 Article 2.2 put in Board hands
A single sentence in AFRINIC’s archived 2007 bylaws separated the company’s registered identity from a direct member vote. Reading that sentence as an authority chain—not as either harmless branding or constitutional grandeur—shows where efficient corporate administration ends…
Story
AFRINIC implemented AFPUB-2005-v4-001 as its regional IPv4 allocation rule
On 17 May 2006, a dense allocation manual became the practical interface between an African Local Internet Registry and new IPv4 supply: a /22 floor, or 1,024 addresses, an additional-allocation test at about 80% use, and assignment benchmarks of 25% immediately and 50% after one…
Story
Six gates in Dakar: AFRINIC’s first LIR admission-and-allocation sequence
On 24 May 2004 in Dakar, AFRINIC presented a compact route into LIR membership and a first resource decision: complete a form, sign an agreement, pay fees, undergo evaluation, obtain approval and, optionally, undergo evaluation of a first suballocation. The order made the process…
Story
Two Sets of Eyes, One Temporary Control: AFRINIC’s 2005 Second-Opinion Interval
For a few weeks in 2005, an African numbering-resource request could be evaluated at AFRINIC’s own operating desk while an established regional registry still looked over the conclusion. That narrow arrangement—not the wider transfer of registry operations—is the revealing part…
Story
When AFRINIC’s Rule Stops but Its Earlier Acts Survive
AFRINIC’s proposed constitution carries forward a deceptively simple rule: an emergency policy that fails endorsement at the next Public Policy Meeting stops for the future, yet actions already taken under it remain valid. That split can protect address uniqueness and people who…
Story
The USD 6,000 Question Behind AFRINIC’s Large-LIR Fee Rise
AFRINIC’s reported decision in Maputo to lift the Large IPv4 LIR annual fee from USD 7,000 to USD 13,000 was arithmetically clear and economically consequential, yet the surviving record leaves the essential implementation ledger unfinished: which members were billed, when the…