Topic
Registry Governance
Within the Topic facet, Registry Governance 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 1,024-Number Rule: What AFRINIC Actually Approved in 2008
The 1,024-Number Rule: What AFRINIC Actually Approved in 2008 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 follow. The Story…
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
AFRINIC’s Receiver exit has remained an application for 307 days
AFRINIC said in October 2025 that its Receiver had begun the process for formal release. On 11 August 2026, AFRINIC’s own public case list still labelled the discharge application “Ongoing”, after the announced Board had formed committees and management structures with Receiver…
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 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 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
AFRINIC’s 2007 Fee Clause Made Discretion a Continuing Duty to Account
Article 4 of the instrument archived as AFRINIC’s 2007 bylaws gave the Board continuing authority to review a portfolio of recurring charges. That was adaptable private-company financing, not taxation; but where operators depend in practice on reliable registry coordination…
Story
Resolution 200605.28: When a Board Calendar Creates Capacity but Not Accountability
In May 2006, AFRINIC’s Board fixed a recurring teleconference date for its own work. The choice was practical and potentially valuable. But a date on a calendar is only the space in which oversight might happen; the public record needed to show whether that space was used is a…
Story
ASO turned AFRINIC’s disputed appointment into a working global-policy seat
The NRO welcomed AFRINIC’s post-election Board, that Board announced a representative with the Receiver’s consent, and ASO records later show the appointee doing council work. What the 16-reference does not supply is the underlying appointment resolution, minutes, vote roll or…
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
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
Resolution 200605.30: A Chair, a Term and the Limits of Office
One terse entry from May 2006 names Pierre Dandjinou, records an internal board vote and gives his chairmanship an endpoint; what it leaves out is precisely what makes the appointment useful for understanding how a private registry should contain authority, preserve continuity…
Story
The ASN Transition Ledger: What Resolution 200605.27 Did—and Did Not—Approve
AFRINIC's 2006 record set a staged route from two-octet to four-octet AS numbers, but the surviving chronology, compatibility design and later exceptions show why a resolution was only the beginning of implementation.
Story
The assent that completed AFRINIC’s part of the IPv6 supply chain
In May 2006, a short corporate resolution made AFRINIC a necessary entity in a common rule for supplying IPv6 space to the world’s regional registries. The rule was operationally valuable and its limits were just as important: approval inside a private coordination system was not…
Story
The One-Month Instrument Inside Resolution 200605.27
In May 2006, Resolution 200605.27 ratified AFPUB-2006-GEN-002: a renewable, one-month arrangement for temporary unicast IPv4 addresses, unicast IPv6 addresses and AS numbers. It required public evidence of the activity, a plan for use and an intended return, yet the surviving…
Story
The Eligibility Line Behind AFRINIC's 2006 ASN Decision
The Eligibility Line Behind AFRINIC's 2006 ASN Decision 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 follow. The Story…
Story
AFRINIC's 2006 infrastructure waiver: a zero price, a guarded gate
In January 2006, AFRINIC waived an unspecified resource-assignment fee for internet exchange points and critical infrastructure, but it did not waive judgment: the small resolution left behind a revealing question about who qualified, who absorbed the cost and what “until further…