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
Five seats, one Board: AFRINIC’s 2017 appeal contradiction
A entity challenging a PDWG-chair action had fourteen calendar days to appeal, yet the five-seat body receiving that appeal depended on the AFRINIC Board for every appointment and remained exposed to Board replacement power. The 2017 design therefore solved one problem while…
Story
Draft 5’s selective answer to the AFRINIC-26 floor
On 31 May 2017, the AFRINIC-26 meeting room did not give Soft Landing BIS Draft 4 a consensus. What followed is more revealing than either a simple story of acceptance or one of rejection. Draft 5 appeared under two unreconciled official dates—27 June in the revision history and…
Story
The Gate Draft 4 Did Not Change
AFRINIC’s fourth Resources Review draft is a lesson in why institutional power must be read through redlines, not impressions. The politically sensitive review gate was plainly present in Draft 4, but it was inherited from Draft 3. Draft 4’s own changes came later in the…
CASE FILE
RIR enforcement stops where the contract ends
The practical question behind **Why RIRs lack enforcement power** is not whether regional registries can take administrative action. They can. The sharper question is what happens when policy expectations reach an organisation that is not legally bound by the registry’s contract.…
Africa Cloud Services Trends
CAIGA’s real test is who controls AFRINIC decisions
Smart Africa’s continental governance proposal is often framed as digital sovereignty. The more immediate question is whether a new governmental layer would strengthen coordination without weakening the technical and member-led checks on Africa’s internet registry.
Story
A stronger complaint gate cannot carry the whole weight of due process
Draft 3 made an evidence-free complaint less able to trigger an AFRINIC resource review, but left the far more consequential stages after entry substantially where Draft 2 had put them. That asymmetry matters because procedural legitimacy is not secured at the threshold alone: it…
Story
The Eightfold Cut That Still Had No Mandate: Soft Landing BIS Draft 3 at AFRINIC-25
On 22 July 2016, Soft Landing BIS Draft 3 reduced its proposed Phase 1 ceiling from a `/15` to a `/18`, cutting the maximum request from 131,072 IPv4 addresses to 16,384. The proposal kept the rest of its scarcity machinery substantially in place and went to AFRINIC-25 on 29…
Story
The Unwritten Rule at AFRINIC’s Review Gate
In August 2016, the second draft of an AFRINIC resource-review proposal altered a single verb in the clause governing community complaints. That small edit matters because a private technical registry does not need to reach a final finding before a review begins to impose costs.…
Story
When an audit becomes a claim to power: AFRINIC’s first resource-review draft
On 18 May 2016, four authors published a proposal for AFRINIC to audit the number-resource records of its members. The administrative premise was serious: a registry cannot keep a dependable ledger if it cannot test stale, contradictory or false information. But…
Story
The Boundary in the Room: What AFRINIC’s 2016 Conduct Code Could—and Could Not—Do
AFRINIC’s Board adopted Resolution 201605.283 to govern behaviour in meetings and mailing lists, where a well-aimed intervention can protect participation but an overextended one can redistribute institutional power. The enduring significance of the code lies in that boundary. A…
Story
Seven Days, a Different Instrument: How Soft Landing BIS Draft 2 Turned a Patch into a Replacement
The most consequential change between the first two Soft Landing BIS drafts was not a newly tightened address threshold. It was a change in form: within seven days, a selective amendment became a self-contained replacement, altering how readers would identify, interpret and audit…
Story
The Final Pool Was a Ledger, Not a Realm
Soft Landing BIS Draft 1 offered a concrete bargain for the dwindling IPv4 pool: cut the largest Phase 1 award, move to the next phase at a declared pool threshold, and preserve separate routes for shared infrastructure, first-time applicants and needs not yet foreseen. The…
Story
A Clock at the Service Desk: AFRINIC Draft 1 Without Sovereignty
On 26 October 2014, a proposal marked `Under Discussion` tried to turn delay, shifting evidence demands and intrusive questions into measurable service problems. Its importance lies not in making AFRINIC a regulator, but in showing how firm private obligations could constrain a…
Story
The Authority Map Missing from AFRINIC’s Collated Policy Manual
In October 2014, AFRINIC’s Board approved an already collated Policy Manual. The short public act records consolidation and approval, but not the manual’s identity, sources, hierarchy or operative history. That gap matters because a corporate manual is most useful when it makes…
Story
The Seven-Day Ledger: AFRINIC’s 2014 Registration Proposal and the Line It Could Not Cross
An assignment of eight IPv4 addresses could have started a seven-business-day countdown: under a 2014 proposal, an AFRINIC member would have had to turn that customer or infrastructure allocation into a documented WHOIS record. The discipline was practical and potentially…
Story
The Treasury Policy AFRINIC Approved but Did Not Show
In February 2013, AFRINIC’s Board approved investment policies and guidelines submitted by the Secretariat. The surviving resolution proves that the organisation created a treasury-governance instrument, but it does not disclose a single operative rule. That gap matters because…
Global Cloud Services Trends
Blockchain interoperability needs a trust-boundary map
Moving an asset between chains does not remove trust. It relocates trust into messages, validators, contracts, keys and emergency controls.
Story
What AFRINIC’s 2012 Africa Internet Summit launch did—and did not—create
AFRINIC says it officially launched the Africa Internet Summit on 15 May 2012 during AFRINIC-16 in Serekunda, The Gambia; its May media archive dates the launch item 17 May. The distinction matters because the institutional act was a launch on the 15th, while the 17th identifies…
Story
The Khartoum Line Between Maintenance and Consequence
At AFRINIC-17, a practical dispute over inaccurate registry contacts exposed a harder institutional question: when does responsible database maintenance become a rule that changes a member’s position? The meeting record shows why the answer matters to both network continuity and…
Story
The D1-to-D2 Redline in “No Reverse Unless Assigned”
One line in AFRINIC’s second draft made the proposed reverse-DNS rule more precise; another made it reach further. Draft 2 said that one registered assignment or sub-allocation within a /24 would be enough for that /24, and it gave an affected LIR twelve months after a reminder…