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
Four Repairs, Four Gates: The Private Authority Map Inside AFRINIC’s PDP Bis Draft 4
On 29 October 2018, AFRINIC published a proposed rulebook in which PDWG chairs would have up to two weeks to pronounce on consensus, yet their decision still sat inside a longer chain: a Board-appointed committee could review process, the Board could remand a proposal on…
Story
The Million-Address Switch: What SL-Update Draft 1 Actually Changed
On 28 October 2018, three authors published a proposal that would rewrite a single paragraph in AFRINIC’s Soft Landing policy. The change was compact, but the reserve behind it was not: an unused /12, containing 1,048,576 IPv4 addresses. SL-Update Draft 1 proposed taking the…
Story
The record outside the contract: AFRINIC’s first legacy-transfer draft
AFRINIC said it maintained inherited Internet number records for organisations with which it had no ordinary contract. That arrangement could persist while an address block stayed put. A proposed transfer made the anomaly urgent: the registry needed reliable evidence of who could…
Story
A routing identity without a second upstream: how Draft 1 challenged AFRINIC’s multihoming proxy
A routing identity without a second upstream: how Draft 1 challenged AFRINIC’s multihoming proxy intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…
Story
What the Simple PDP Update Took Away—and Where Its Discretion Went
AFRINIC’s Simple PDP Update Draft 1 approached process reform with a red pen: shorten notices, move the moment of decision, narrow the objections that counted at Last Call, and make mailing-list participation less subordinate to a meeting room. That subtraction offered a credible…
Story
The resolution with two numbers: what AFRINIC’s IPv6 PI ratification did — and did not — put into effect
AFRINIC’s August 2018 adoption of an IPv6 provider-independent addressing update removed an obsolete eligibility barrier and added a useful correction route, but the organisation’s own records disagree over the resolution number and show that implementation continued after the…
Story
The five-day mailbox: when AFRINIC Draft 1 turned contactability into compliance
Two messages, one code and five business days separated a useful registry check from a proposed breach finding. AFRINIC’s first Abuse Contact Policy Update draft began with the practical need for a reachable network-abuse desk, then crossed into prescribing how that desk must…
Story
The IPv6 door that opened without an IPv4 past
An African enterprise planning a second upstream faces a deceptively simple choice: accept provider-assigned IPv6 and prepare to renumber if the commercial relationship changes, or seek a provider-independent prefix that can preserve its public network identity across both paths.…
Story
AFRINIC's 2017 accounts: approval before completion
Resolution 201803.403 fixed an important responsibility: AFRINIC's Board approved the 2017 financial statements before the auditors signed their report, then authorised the chief executive and chair to sign both the accounts and a representation letter. That sequence was orderly…
Story
The seven-year error in AFRINIC’s IPv6 manual
Seven years after newer Internet guidance had displaced an old formula for sizing IPv6 assignments, AFRINIC’s working manual still directed members and staff towards the obsolete text. The proposal that repaired the mistake looked like housekeeping. In fact, it exposed a serious…
Story
The narrow door through AFRINIC’s secrecy wall
Resolution 201803.402 did something modest but indispensable: it allowed directors and former directors to give an independent investigation committee confidential information that was reasonably necessary for its work. That permission stopped AFRINIC’s own secrecy rule from…
Story
The Seat That Members Refused to Fill
Resolution 201803.401 solved a real nomination conflict by building a one-seat route back to AFRINIC’s members, but its unwritten bylaw foundation and the Board’s proximity to the candidate gate made refusal—not institutional confidence—the decisive test of legitimacy.
Story
Ratification was not implementation: the 107-day chain behind AFRINIC’s IPv6 manual repair
A unanimous Board vote on 8 August 2018 settled one institutional question but left two practical jobs visibly unfinished. AFRINIC still had to notify the policy chairs and put the adopted IPv6 reference update into its working manual. The resulting chain—from recommendation to…
Story
The Forecast at the Registry Door: AFRINIC’s 2018 IPv6 Allocation Rewrite
AFRINIC’s second draft of the IPv6 Initial Allocation Update tried to make the registry fit real networks rather than force every applicant through a narrow service-provider model. It widened who an LIR could serve, allowed evidence for an initial block larger than `/32`, offered…
Story
The constitution in the quiet room
PDP Bis Draft 3 tried to make AFRINIC’s policy machinery legible: four phases, named objections, reasons at the Board gate and a timed internal appeal. Its clarity was real. So was its deeper problem. A private technical registry can organise deliberation and protect the…
Story
The Fairer Lottery That Could Not Supply AFRINIC’s Missing Mandate
Draft 6 widened AFRINIC’s proposed random resource-review lottery from a few named membership categories to the entire membership. That was a genuine correction of unequal exposure. Yet a fairer pool cannot answer the prior question: what may a private registry inspect, on whose…
Story
When a /64 crosses a device boundary but control stays put
A visitor joins an office Wi-Fi network and receives a temporary IPv6 /64 from the organisation that runs the access point, router and upstream link. The address space has reached a third party, but the network has not changed hands. In March 2018, the first draft of AFRINIC’s…
Story
When resignation waited for a signature: the narrow strength and wider silence of AFRINIC Resolution 201803.397
Two emailed intentions to leave AFRINIC’s leading Board offices created the appearance of a transition before they created an effective one. Resolution 201803.397 handled that immediate problem with unusual care: successors could be chosen, but not activated until signed letters…
Story
AFRINIC’s 2026 budget reached members after the decision
At AFRINIC’s 2026 annual meeting, members were shown an annual plan that the Board had already approved and were asked to vote on accounts from earlier years. That sequence may fit the company’s Bylaws, but it leaves a harder question unanswered: when nearly all operating revenue…
Story
The rule beneath the rewrite: AFRINIC’s Draft 2 and the threshold of reverse-DNS cleanup
A resolver is sent to a nameserver that is dead, silent or unable to answer authoritatively. The apparent remedy is modest: correct the parent record so that it no longer points towards a service that is not there. Yet the correction is not consequence-free. In reverse DNS…