Skip to main content

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
CASE FILE signal visual
Governance / Case FileCASE FILE
Active Dossiers1 Live Case

AFRINIC saga currently tracked end-to-end.

Primary DomainGovernance

Institution legitimacy and continuity risk mapping.

MethodSignal + Timeline + Failure Paths

Primary-source based timeline and risk analysis.

Decision ValueHigh

Used for continuity and policy exposure planning.

Latest Coverage

Latest from CASE FILE

187 articles

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.

Sep 1, 2026

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…

Sep 1, 2026

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…

Sep 1, 2026

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…

Sep 1, 2026

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…

Sep 1, 2026

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.

Sep 1, 2026

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…

Sep 1, 2026

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…

Sep 1, 2026

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…

Sep 1, 2026

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…

Sep 1, 2026

CASE FILE

The Device Left SCIM. Its Network Access Still Needed a Decision: RFC 9944

A deleted Device record can settle what a SCIM service will show. It cannot, on its own, settle what a network will enforce. RFC 9944 makes that distinction unusually plain: removal is an application's signal of intent, while a SCIM server and its back-end policy decide whether…

Sep 1, 2026

CASE FILE

The Map Reached a Router. It Did Not Decide the Path: RFC 9962 and LISP-Decent

A network can reduce a control-plane dependency and still retain a decision boundary. RFC 9962 makes that distinction unusually visible. It lets LISP Tunnel Routers participate in distributing the EID-to-RLOC mappings they use, rather than leaving all mapping state with a…

Sep 1, 2026

CASE FILE

The Alarm Changed State. The Cause Still Had to Be Found: RFC 9940 and the Evidence Boundary

An alert can be prompt, honest and operationally useful without being a verdict. RFC 9940 gives network teams a vocabulary for that restraint: a measurement, an event, a fault, a problem, a suspected cause and a decision are related, but they are not interchangeable.

Sep 1, 2026

CASE FILE

The DNS ID Was Zero. The Cache Still Needed a Clock: RFC 9953 and DoC Evidence

A cache can make a constrained network quieter without becoming the authority that decided what the answer means. RFC 9953 makes that line unusually precise: it lets equivalent DNS-over-CoAP requests share a representation, then requires a separate clock before anyone may rely on…

Sep 1, 2026

CASE FILE

The Token Named the Chip. It Did Not Decide the Door: RFC 9783 and PSA Attestation Authority

A signed attestation token can arrive at a policy boundary looking more decisive than it is. Its nonce matches the challenge. Its client identifier is familiar. It describes an instance, an implementation, a lifecycle state and the software components in the measured PSA scope. A…

Sep 1, 2026

CASE FILE

The Contact Lost Its UID. It Did Not Lose Its Boundaries: RFC 9982 and Record Identity Authority

A contact card without a globally convenient identifier can make a synchronization team uncomfortable. The usual reflex is to manufacture one: a string is easy to add, relational tables prefer stable keys, and downstream software wants a value to point at. RFC 9982 takes a more…

Sep 1, 2026

CASE FILE

The Group Key Reached the Devices. It Did Not Assign the Act: RFC 10020 and CoAP Group Authority

A protected message can leave one sender and be intelligible to a group. It cannot make five receivers one decision-maker. RFC 10020 matters because it gives constrained systems a disciplined way to speak to a group without erasing the separate evidence required for membership…

Sep 1, 2026

CASE FILE

W3C’s WebMCP Charter Patch Adds HTML Scope Without Naming HTML or ARIA Groups

W3C’s open Web Machine Learning charter patch does more than add an AI-labelled deliverable. It would put JavaScript tool registration, browser mediation and declarative annotations on HTML forms inside the Working Group’s proposed scope. Yet the same diff leaves the charter’s…

Sep 1, 2026

CASE FILE

The Model Named an Endpoint. It Did Not Start a Service: RFC 10009 and HTTP Configuration Authority

An HTTP endpoint can look settled long before it exists in practice. A URI is present in a management tree; permitted versions are listed; TLS parameters and a proxy are named; a server has a name and an apparent stack. Those are useful, reviewable decisions. RFC 10009 makes…

Sep 1, 2026

CASE FILE

The Call Connected. The Identity Still Had to Be Earned: RFC 9970 and the Local Authority Boundary

A call can arrive at a real endpoint and still arrive at the wrong decision. That is the uncomfortable gap RFC 9970 brings into view. STIR made it possible to carry cryptographic information about the originator of a SIP request. A caller, however, has a different question after…

Sep 1, 2026

Member Unlock

Restricted Profile Intelligence

Login is required to unlock full profile briefings and deep-dive sections.

Only for Strategic Circle

Strategic Circle Briefing

Join to unlock strategic briefings after signing in.

Join Strategic Circle
Only for Leadership Alliance

Leadership Alliance Briefing

For qualified IP-asset owners and management; sign in to unlock alliance briefings.

Join Leadership Alliance

Session Map

Active Dossiers

AFRINIC Saga

Multi-year governance and legal crisis with implications for RIR accountability worldwide.

Open AFRINIC Saga