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.
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…
Story
No Reverse Unless Assigned: Draft 1 Put a Database Error in the DNS Decision Path
On 10 April 2012, Tim McGinnis submitted the first “No Reverse Unless Assigned” proposal, asking AFRINIC to condition a new reverse-DNS delegation on a registered assignment or sub-allocation. The draft confronted a genuine weakness in public network records, but it also exposed…
Story
Resolution 201111.138 ratified IPv4 Soft Landing after a 34-month process
One sentence adopted on 21 November 2011 purported to close 1,048 days of argument over AFRINIC's dwindling IPv4 pool. The sentence matters less as a ceremony of authority than as a pointer to the exact draft, allocation limits and scope correction that the Board said it…
Story
The Returned Envelope and the Locked Drawer
AFRINIC’s 2012 WHOIS cleanup proposal began with a sensible ledger problem and ended with an authority it could not possess. The useful question was how a private registry should keep contact records accurate and make its own maintenance work visible. The dangerous one was…
Story
Regional Internet Registry Privacy Draft 2 proposed a six-month retention limit
AFRINIC’s 2012 privacy proposal put a simple clock on personal data and a public test on transfers abroad. Its failure to win consensus reveals a harder question: how should a number-resource policy restrain a registry’s demands on applicants without pretending to legislate the…
Story
The Abuse-Contact Resolution That Ratified a Doorbell, Not a Police Power
AFRINIC’s June 2011 ratification improved the public path for reaching a network operator, but it did not authorize the registry to decide whether an allegation was true or to punish the holder of Internet number resources. Reading the resolution at its actual scale reveals a…
Story
JAWUG's waived fee exposed the missing terms of a named exception
In February 2011, AFRINIC's Board recorded in Resolution 201102.112 that, following a formal request from JAWUG, which it described as a South African non-profit network, it agreed to waive JAWUG's membership fee. That concise act shows who received relief and names the fee…
Story
The Rulebook That Worked Before Its Machinery Was Ready
At its first meeting under AFPUB-2010-GEN-005, AFRINIC enforced a new safeguard against late policy text and improvised the selection of the people meant to administer it. That contrast reveals both the value and the unfinished limits of a private registry’s redesigned control…
Story
The objections that reversed AFRINIC's Soft Landing last call
On 14 July 2010, a short procedural conclusion stopped a numerically consequential IPv4 proposal from moving toward ratification. The significance lies neither in the volume of mailing-list traffic nor in a claim that private entities spoke for Africa. It lies in the specific…
Story
The Policy AFRINIC Called Implemented Before the World Could Use It
On 11 November 2010 AFRINIC’s policy archive says that a plan for recovered IPv4 space was “Implemented”. The word sounds conclusive. The instrument was not. Its operative global machinery depended on a common text, ICANN Board ratification and action by IANA; the common proposal…
Story
The Mandate in the Margin: What AFRINIC-13 Actually Agreed on Soft Landing
On 25 November 2010, AFRINIC’s public-policy meeting did not approve a finished Soft Landing policy. It agreed to move an identifiable proposal to Last Call while assigning three changes to be incorporated afterward and deliberately leaving a disputed /27 minimum unchanged. That…
Story
The Notice Was Part of the Soft Landing Decision
The decisive entity in June 2010 was not only a proposal about scarce IPv4 space. It was the notice that told people which proposal they were being asked to examine. By carrying a complete draft into a dated review window, then allowing corrections and objections to change the…
Story
AFRINIC changed Soft Landing's reference and left the redline to readers
On 12 May 2010, a materially revised scarcity proposal acquired a new documentary identity in AFRINIC's later history, but the message that carried the text did not carry the identifier. That mismatch shows both the value of version numbers and their limit: metadata can locate a…
Story
The rulebook that audited itself: what GEN-004 admitted about AFRINIC’s 2008 PDP
AFRINIC’s 2010 replacement policy did more than propose new procedure. It recorded the faults of the procedure it was meant to replace—and a later implementation note revealed how much discretion survived the repair.
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…