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.

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
748 articles
CASE FILE
Internet Society Scheduled Nine Board Meetings Without an Open Forum
From 14 May 2025 through 25–26 July 2026, nine consecutive Internet Society Board agenda pages offered the public a place to listen but scheduled no Open Forum where attendees could question or address trustees. That is a real form of transparency. It is not participation. And…
CASE FILE
The Cursor Continued the List. It Did Not Continue the Right: RFC 9865
RFC 9865 gives SCIM a cleaner way to traverse a long result set. It does not convert a continuation value into a portable permission, a complete inventory, or a decision already made.
CASE FILE
The Inventory Found the Algorithm. It Did Not Migrate the System: RFC 9958 and Cryptographic Agility
An organisation can catalogue every algorithm name it knows and still be unable to say which cryptographic path protects a consequential transaction. RFC 9958 makes the inventory indispensable. It does not allow the inventory to pronounce a migration complete.
CASE FILE
W3C’s Profiles Draft Can Inherit Conformance. The Proof Layer Is Still Unsettled
A machine can follow two RDF links and produce a third: a resource conforms to a profile; that profile is a profile of a specification; therefore the resource conforms to the specification. The W3C’s new Profiles Vocabulary draft makes that inference explicit. It also exposes why…
CASE FILE
The Color Reached PCEP. It Did Not Reach the Service: RFC 9863
RFC 9863 lets PCEP carry a color for a TE path. That is useful coordination data. It is not a guarantee that a service was mapped, a latency objective was met, or a customer received a result.
CASE FILE
The UUID Sorted. The Event Was Not Proven: RFC 9562 and the Boundary Between Identifier Order and Evidence Time
At 14:03, a review screen puts two rows in an immaculate order. The smaller UUIDv7 belongs to `reversal-requested`; the larger one belongs to `reversal-completed`. It looks like a ready-made account of what happened. But the first identifier may have been allocated before a…
CASE FILE
DNS Received the Hint. The Parent Still Had to Decide: RFC 9859’s Delegation Boundary
RFC 9859 can make delegation maintenance faster. It cannot make a notification into a parent-side decision, or turn a received response into proof that DNSSEC or delegation state has changed.
CASE FILE
The Router Repaired the Path. It Did Not Restore the Service: RFC 9855 and TI-LFA’s Local Boundary
A router can react to a directly attached failure in milliseconds and still know nothing about whether a customer service has recovered. RFC 9855 gives Segment Routing deployments a disciplined way to precompute and activate a loop-free repair path at the Point of Local Repair.…
CASE FILE
WCAG-EM’s 10% Random Check Is Not 10% of the Product
An accessibility report can contain a precise percentage and still leave its denominator invisible. W3C’s new WCAG Evaluation Methodology says the random part of a representative sample should equal 10% of the structured part. It does not say that evaluators inspect 10% of the…
CASE FILE
The Collector Received a Delay. It Did Not Receive a Verdict: RFC 9951
At 09:17, a collector receives a Flow Record with a mean delay, a maximum delay and an identifier for the transit point that exported them. By 09:20, someone wants the record to settle three larger questions: whether a customer suffered, whether a path changed, and which team…
CASE FILE
The Resource Named Its Authorization Server. It Did Not Grant a Right: RFC 9728’s Discovery Boundary
A resource can accurately publish where a client should look next and still have made no decision to let that client do anything. RFC 9728 gives protected resources a disciplined way to publish OAuth metadata. Its value is coordination: it narrows a discovery problem. It is not…
CASE FILE
The Authorization Conversation Was Still Pending. It Was Not an API Right: GNAP’s Continuation Boundary
A client can be entitled to continue an authorization conversation without being entitled to call the API it asked about. RFC 9635 makes the distinction unusually explicit: a continuation credential advances one grant request at the authorization server; a resource right appears…
CASE FILE
Internet Society Added ‘Obedience’ to Its Policy Opening. The Duty Runs to Mission, Not Management
One word can make a governance document look more authoritarian just as the underlying rule becomes easier to read. Internet Society’s Board added the duty of obedience to the opening paragraph of its Trustee fiduciary policy in July 2026. Yet the Board’s own resolution says the…
CASE FILE
W3C Calls Sustainability ‘Ratings.’ One Total Still Ranks 71 Guidelines
On 6 August, a W3C repository changed one word: “Measurement” became “Ratings.” Twelve days later, the Sustainable Web Interest Group published its first Group Note Draft under the narrower name. The distinction is honest. The document combines evidence and expert judgment, not…
CASE FILE
After a Reboot, “Secure” Must Not Mean “Resume”: RFC 10021 and Group OSCORE Recovery
A controller can regain a safe cryptographic footing after a power loss without regaining permission to continue the process it interrupted. RFC 10021 makes that distinction operational: restore the security context first; decide separately whether anything should resume.
CASE FILE
The Benchmark Found a Limit. It Did Not Grant a Capacity Claim: RFC 9971
A network benchmark often arrives in a meeting as a single number. That number then begins doing work it was never designed to do. It is used to imply that a cloud function has production headroom, that a supplier has met an obligation, that a release is safe, or that a customer…
CASE FILE
The Hybrid Signature Arrived. The Verification Rule Still Had to Be Chosen: RFC 9955
Two signature components can travel together without forcing every receiver to treat them as one indivisible verification event. RFC 9955 makes the distinction useful: a hybrid artifact records a design choice; the receiver's verification rule still decides what was actually…
CASE FILE
The Queue Found a Flow. It Did Not Find a Culprit: RFC 9957 and DOCSIS QProt
When a low-latency queue begins to grow, an operator wants a fast answer to a hard question: which traffic should lose the privileged path first? RFC 9957 describes a careful local answer for DOCSIS. It is not an answer to the wider and more tempting questions. A Queue Protection…
CASE FILE
ITU’s Proposed Video-Traffic Metric Needs a Public Measurement Contract
One line in ITU’s proposed 2028–2031 strategy would turn the world’s video streams into evidence of institutional impact. The 5 August paper proposes measuring the share of global video traffic carried by ITU-standardized codecs. That may be a useful reach statistic. Yet the…
CASE FILE
The Packet Carried a Mark. It Did Not Deliver an Operations Verdict: RFC 9947 and SRv6 Measurement Authority
A marked packet is compelling because it seems to turn an invisible path into a fact. A loss bit, a delay bit, an identifier, a timestamp and a sequence value can all travel inside the same Segment Routing Header that tells the packet which segment endpoint to visit next. That is…
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