Content Type
Research Analysis
Within the Content Type facet, Research Analysis intelligence gathers BTW.MEDIA articles that share the same editorial format, helping readers compare briefings, profiles, risk notes, market analysis, and event coverage without mixing different kinds of evidence. The page explains how this content type frames internet infrastructure events, company movements, governance decisions, operational signals, and public evidence across the site. Readers can compare which actors or infrastructure systems appear most often, how source quality changes interpretation, and whether the material is a durable profile, a time-sensitive event, a strategic market signal, or a governance development. The result is a useful search page for operators, investors, customers, analysts, and policy stakeholders who need to understand the consequence, timing, and evidence behind similar article formats.
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's 2009 accounts showed only USD 14,157 of surplus after a foreign-exchange loss
AFRINIC's registry services produced a positive operating result in 2009, yet almost nine tenths of it disappeared through the net effect of foreign exchange and interest. The arithmetic is unusually clear; the authority and treasury trail behind it is not.
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
AFRINIC-11's ASN consensus met its real test in compatibility
AFRINIC-11's ASN consensus met its real test in compatibility 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
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
AFRINIC-10's 59% mailing-list finding—and the participation it could not prove
At AFRINIC-10 in Cairo, a small survey finding exposed a large governance problem: opening a channel is not the same as carrying people across it. The meeting report said 59 percent were subscribed to an unspecified AFRINIC mailing list, but supplied neither the item count nor…
Story
The Rule AFRINIC Had Not Changed
At AFRINIC's 21 May 2009 meeting, a dispute over whether a candidate could vote became a precise test of institutional authority: a new bylaw could empower the Board to change an election regulation, counsel said, but neither expectation nor practice could perform the Board's…
Story
AFRINIC-10's useful survey—and the denominator that limits its claims
AFRINIC's post-meeting report preserved something more valuable than an uncomplicated satisfaction story: enough arithmetic to show both what 42 respondents could teach the registry and what they could never authorise on behalf of 135 event entities, a membership, or a continent.
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…