AFRINIC saga currently tracked end-to-end.
Governance / Case File
CASE FILE
Case File governance intelligence tracks institutions, policy processes, standards activity, registry operations, accountability disputes, and implementation signals that affect internet infrastructure. BTW.
Institutional BreakdownLegal and Policy ConflictElection and Control Risk
Institution legitimacy and continuity risk mapping.
Primary-source based timeline and risk analysis.
Used for continuity and policy exposure planning.
Latest Coverage
Latest from CASE FILE
1,341 articles
CASE FILE
ODRL’s Next Test Is Whether Two Policy Engines Agree
W3C’s workshop report asks for more than a common rights vocabulary. It proposes a way to compare what independent software actually decides when it processes the same policy.
CASE FILE
When the Monitors Disagree: AS210973's 194.0.132.0/24 and the Limits of Routing Evidence
When the Monitors Disagree: AS210973's 194.0.132.0/24 and the Limits of Routing Evidence intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences…
Afrinic SAGA
The Receiver's Own Instruments: What AFRINIC's Undischarged Custodian Still Controls
Since 12 September 2023 the recorded deciding organ over AFRINIC's control surface has not been the elected Board but a court-appointed receiver — and on the public record located at publication, that receiver's own discharge remains undetermined.
Afrinic SAGA
What Deciding Bodies Record: ICANN's .WEB IRP Playbook and AFRINIC's Vanishing Public Record
When a governance body loses an Independent Review Panel case, the test of its legitimacy is not the finding — it is what the body records next. Two internet-governance institutions faced that test within the same week in January 2022, and their records diverged in ways that…
CASE FILE
The Optus Triple Zero case now sits in court, and the stake sale makes the remedy the open question
On 30 July 2026 the Australian Communications and Media Authority (ACMA) filed civil penalty proceedings in the Federal Court against Optus Mobile Pty Limited over the 18 September 2025 Triple Zero outage. The same day, Singtel confirmed discussions about selling a stake in…
CASE FILE
ACMA's court action against Optus: what a filed proceeding can prove that statements cannot
On 30 July 2026, the Australian Communications and Media Authority filed a civil penalty proceeding in the Federal Court against Optus Mobile Pty Limited, a wholly owned subsidiary of SingTel Optus Pty Limited, over the 18 September 2025 Triple Zero outage. The filing converts…
Afrinic SAGA
AFRINIC's control over its registry stays conditional as the discharge ruling waits
Authority over African Network Information Center - (AfriNIC) Ltd is split and conditional in September 2026: a court-appointed receiver still consents to board decisions, the receiver's discharge application has no published outcome, ICANN has joined a contested winding-up…
Afrinic SAGA
AFRINIC under receivership: who can authorise, detect and reverse a change to its routing-security machinery
An operator in Nairobi or Lagos who validates a route with AFRINIC's RPKI tools, or signs a zone through its DNSSEC service, is relying on a registry that a Mauritian court placed under an official receiver and that ICANN has twice intervened to defend. The visible question in…
Afrinic SAGA
AFRINIC's authority over African number resources: contract, court, receiver
A member's addresses can be taken away by a clause, a court order or a board vote — and African internet governance is currently living through the argument about which of those three actually applies to any individual holder.
CASE FILE
The SID Was Compact. The Path Authority Was Not: RFC 9631
RFC 9631 can express an IPv6 path with 16- or 32-bit segment identifiers. The saving is real, but the meaning of each short number lives in a local forwarding table whose version, owner and execution are not carried in the packet.
CASE FILE
The Reference Graph Arrived. The Picture Did Not: RFC 9628
VP9 over RTP can disclose how one picture depends on another, packet by packet or through a recurring structure. That map is valuable, but it is not a receipt for complete delivery, successful decoding or the image a viewer actually saw.
Afrinic SAGA
From RIPE NCC to AFRINIC: the instruments that moved registry authority, and the court that holds the ring
Africa's Internet number resources changed registry in 2004 and 2005 through a short chain of dated instruments. The chain moved authority. What it left with resource holders was a contract. Twenty years later the body that received that authority answers to a court-appointed…
CASE FILE
The Sequence Number Did Not Decode the Picture: RFC 9627
A Layer Refresh Request can name the exact upgrade a receiver wants and repeat that command reliably. It still cannot certify the encoder's action, the packet path or the layer that finally reached the screen.
CASE FILE
The Video Was Encrypted. Its Frame Decisions Were Not: RFC 9626
An RTP switch can make useful forwarding decisions without seeing a conference's video. RFC 9626 gives it a small map of frame boundaries and dependencies. That map is authenticated metadata, not an independent witness to what the encrypted picture actually contains or what a…
CASE FILE
Who Authorises the Receiver: The Mauritian Court's Power Over AFRINIC
AFRINIC is a Mauritius-registered company, and the orders that have governed its assets since 2023 come from Mauritian company law. Read together, the judgment that ended the registry's first appeal, the statute that defines the court, and the two Orders in Council that carry…
CASE FILE
The Connection Was Ready. The Policy Decision Was Still Hidden: RFCs 9621–9623
A transport abstraction can choose among addresses, interfaces and protocols without forcing the application to know every mechanism. That is a genuine engineering gain. It also means that a green `Ready` event can arrive after a consequential choice whose inputs, rejected…
CASE FILE
The Verdict Stayed the Same. The Validator Ran Out of Memory: RFC 9618
A certificate regression suite can return every expected verdict and still miss the failure that matters in production. RFC 9618 shows why semantic correctness and bounded execution are separate obligations: the old X.509 policy tree and the new policy graph can accept the same…
CASE FILE
The Route Cost Fell. The Service Did Not Improve: RFC 9616
The routing dashboard marked the new path as cheaper after its RTT samples settled. The application trace still showed slower transactions and deeper queues. Nothing was necessarily broken: RFC 9616 standardises a disciplined way to turn neighbour delay into a Babel cost, not a…
CASE FILE
The Data Was Split. The Operator Could Still Reassemble the Person: RFC 9614
The relay could identify the client but could not read the request. The gateway could read the request but could not see the client's address. Then one operator aligned the two logs by time and size. Every box kept its local promise; the system did not keep the privacy promise.…
CASE FILE
The Alarm Fired. It Still Did Not Name the Failed Path: RFC 9612
A return code says the requested reverse path was not found, yet BFD remains up over an IP fallback. Nothing is contradictory. The two receipts answer different questions. RFC 9612 makes that separation operable, but it does not let a fast round-trip detector identify a failed…
Member Unlock
Restricted Profile Intelligence
Login is required to unlock full profile briefings and deep-dive sections.
Strategic Circle Briefing
Join to unlock strategic briefings after signing in.
Join Strategic CircleLeadership Alliance Briefing
For qualified IP-asset owners and management; sign in to unlock alliance briefings.
Join Leadership AllianceSession Map
Active Dossiers
AFRINIC Saga
Multi-year governance and legal crisis with implications for RIR accountability worldwide.
Open AFRINIC Saga