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
794 articles
CASE FILE
The Timestamp Reached the Payload. It Did Not Date the Signature: RFC 9921
A protected COSE header can carry a perfectly valid RFC 3161 timestamp token and still tell a verifier nothing about when the COSE signature was created. RFC 9921 draws that line so a system does not accept a post-revocation signature merely because the payload was stamped…
CASE FILE
The Field Parsed. It Did Not Decide the Request: RFC 9651’s Semantic Boundary
A machine-readable HTTP field can make a system easier to inspect without making it entitled to act. RFC 9651 is valuable precisely because it keeps that distinction visible: it gives HTTP a disciplined way to express a List, Dictionary or Item, then leaves the meaning and…
CASE FILE
The Client Had the Dictionary. It Did Not Have the Response: RFC 9842
RFC 9842 lets an HTTP client and server coordinate around a cached compression dictionary. That is a useful, tightly bounded fact. It is not proof that the server selected a particular response, that a cache variant was semantically current, that a decoder reached meaningful…
CASE FILE
The Federation Signed the Member. It Did Not Authorize the Session: RFC 9932’s MATF Boundary
A signed federation file can make a peer easier to recognize. It cannot make a service call permissible by itself. RFC 9932 is most useful when read as a deliberately bounded chain: it describes how a federation distributes metadata and pins, how a TLS peer can be identified, and…
CASE FILE
The UDP Payload Was Protected. The Option Was Not: RFC 9868
RFC 9868 gives UDP a place for transport options. It does not place that option area inside the UDP user data that DTLS protects, turn an option checksum into a security decision, or prove that an endpoint, path or application acted on an option.
CASE FILE
The Client Sent the Bytes. The New Protocol Had Not Accepted Them: RFC 9931’s Optimistic-Transition Boundary
An HTTP/1.1 client can make a transition look nearly complete before the party that must interpret it has accepted anything. RFC 9931 is valuable because it refuses that compression: a request may be finished, a client may offer early bytes, and the server may still reject the…
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…
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