Topic
Consensus Capture
Within the Topic facet, Consensus Capture 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
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 policy chain AFRINIC made visible—and the powers it left unresolved
On 27 February 2008, AFRINIC announced and implemented a new policy-development process that replaced its transitional model. The enduring question is not whether the new process looked open, orderly or communal, but who acquired power at every handoff from proposal to running…
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
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 Six Rows Missing From AFRINIC-6
AFRINIC’s surviving account of its sixth policy meeting offers a memorable result—three proposals reached consensus, two were withdrawn and one did not reach consensus—but not the decision ledger needed to verify it at a glance. Reconstructing the six proposal lines shows that…
Story
The IPv6 PI Choice AFRINIC-4 Could Not Settle
In Nairobi on 17 May 2006, a proposal for provider-independent IPv6 space forced an unusually clear argument about what a registry can record, what operators will route, and who should pay when those two realities do not align. The answer was not adoption or rejection, but an…
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
The Open Address and the Missing Public
In January 2004, AFRINIC opened a dedicated policy mailing address to anyone who wanted to take part before a public meeting. That was a meaningful expansion of access. Yet the surviving record cannot tell us who entered, who remained outside, or whether those visible in the…
Story
The constituency that arrived before AFRINIC
In January 2004, before AFRINIC had completed even the next visible step of becoming a Mauritian membership corporation, it created an open working group to develop number-resource policy. That unusual sequence made participation an early source of technical knowledge and…
Story
Fifteen Days Beyond Cairo: AFRINIC’s Last Call and the Limits of Consensus
AFRINIC’s post-meeting last call was designed to stop a physical room from becoming the final word on resource policy. After the AFRINIC-3 meeting described four proposals as having consensus, a public mailing-list interval offered people outside Cairo 15 days to propose final…
Story
The Missing Day in AFRINIC’s April Disclosure
A funding milestone required AFRINIC to publish a broad supporting-document bundle four weeks before its first open policy and member meeting. The surviving record shows that meaningful disclosure occurred in April 2004, yet it does not preserve the one fact needed to test the…
Story
The Rule in the Gap: AFRINIC’s Borrowed Standard for End-User PI Requests
In Maputo, a policy proposal was too new to have completed AFRINIC’s own adoption process, but end-user requests could not simply be wished out of the queue. The answer recorded on 27 April 2005—use each member’s respective former RIR policy until AFRINIC adopted its own—solved…
Story
The Undated Promise Ledger: What AFRINIC Put on the Record in March 2005
The most useful feature of AFRINIC’s updated recognition application is not the status it sought but the promises it made testable: who supported the registry, who would control it, how policy would move, where the database would run, how the organisation would pay its way, and…
Story
The Decision AFRINIC-2 Did Not Make
At Maputo in April 2005, a concern about recovering unused Internet number resources was sent to the policy working group rather than converted into an immediate decision. That modest procedural choice still offers a demanding test of registry legitimacy: how to protect…
Story
AFRINIC’s constitutional rewrite leaves its emergency-policy shortcut intact
The August proposed Constitution presents Article 11 as substantively unchanged, but that is precisely the problem: it preserves a clause that allows the Board to bypass the ordinary policy process on its own judgment of necessity and urgency, without defining the emergency…