Policy continuity, legitimacy, and accountability signals across internet governance institutions.
Governance
Governance
Internet governance intelligence tracks institutions, policy processes, standards activity, registry operations, accountability disputes, and implementation signals that affect internet infrastructure. BTW.
RIR WatchdogCase FileNumber Resource SocietyICANNIETFHistory of InternetNOGs
RIR Watchdog, Case File, NRS, ICANN, IETF, History of Internet, and NOG sessions.
Coverage prioritizes implementation evidence and institutional behavior over declarative positions.
Latest Coverage
Latest from Governance
7,625 articles
History
Eric Brewer’s FirstGov: A Search Box, Not a Government Record
On 22 September 2000, FirstGov opened after a ninety-day push to give federal information one public entrance. Eric Brewer’s search technology helped make that promise tangible. But the engine, the index it maintained and the agencies’ own pages were different things—with…
CASE FILE
The Canary Decoded. The Cached Variant Still Asked for More Memory: RFC 9659’s Missing Receipt
An eight-megabyte ceiling can make HTTP compression interoperable only when the bytes that reached the client were produced under that ceiling. RFC 9659 defines the contract; it does not certify every origin worker, recompressing intermediary, cached variant or recipient process…
CASE FILE
NIST’s Open RAN Draft Exposes the Gap Between a Component Claim and Agency Risk
A radio component may meet a specification while the network around it still lacks an accountable risk decision. NIST’s new federal Open RAN profile puts that handoff in plain view.
IETF
The configuration arrived. The public zone did not: RFC 9527
RFC 9527 can deliver the domain and manager coordinates an automated Homenet Naming Authority needs. The harder claim begins after that success: whether the delegated name is authoritative, signed, current and reachable from outside the home.
Story
APNIC’s 93% Service Score Needs a Member-Only Comparator
APNIC’s published service-quality line reads 94%, 95%, then 93%. The numbers remain high, but the 2026 endpoint brings a broader respondent mix into a measure previously reported for Members. A Member-only bridge would preserve the trend without erasing the wider community’s…
CASE FILE
The Root Address Was the Same. The Tree Was Not: RFC 9658 and Multipoint Identity
Two multipoint trees can begin at the same router and carry the same opaque value yet be different forwarding entities. Change the topology or the algorithm, and the eligible path and branches can change with it. RFC 9658 gives that difference a wire identity. It does not prove…
CASE FILE
NIST’s OT Draft Puts Version Custody Inside the Risk Decision
NIST plans to separate parts of its operational-technology guide into updateable web resources and companion documents. That may keep guidance fresher, but a plant’s risk record will need to say which versions actually informed its decision.
IETF
Every reference byte matched. The device still reused its ephemeral key: RFC 9529
RFC 9529 turns EDHOC into an unusually inspectable computation by publishing complete traces. That makes disagreement easier to locate. It does not make a matching implementation secure outside the fixed inputs the trace exercised.
CASE FILE
The Contact Was on the Schedule. The Adjacency Never Arrived: RFC 9657 and Forecast Authority
A route engine can know that a satellite should cross a ground station's view at 12:03, reserve that contact and hold data for it. At 12:03, the clock may be wrong, the terminal may not acquire, the data rate may collapse or the adjacency may never form. RFC 9657 makes…
History
John Day and the Seven-Layer Model That Could Not Order Deployment
Seven boxes can look like a build plan. John Day’s account of the OSI reference model offers a different reading: a framework for standards work, not an implementation order. His later RINA proposal made a recursive IPC design explicit; a small prototype showed that research code…
IETF
The path label returned with the data. It did not name the producer: RFC 9531
RFC 9531 can return a forwarding path to a consumer and let a later Interest try that path again. The label is valuable operational evidence, but it is neither a producer credential nor a promise that the next exchange will reach the same cache, route or result.
CASE FILE
The Model Said 800 Megabits. The Air Did Not: RFC 9656 and the Microwave Capacity Boundary
A path engine can ingest a microwave link's nominal bandwidth, select the route and produce a coherent topology explanation. Meanwhile, the carrier's actual signal-to-noise-and-interference ratio can deteriorate and the usable service capacity can fall. RFC 9656 makes the radio…
IETF
An Agent Evidence Request Should Not Have a Different Answer for Each Audience
An individual Internet-Draft proposes that a verifiable record requested against the same checkpoint must be identical for every recipient. That rule makes tailored evidence detectable, but only if someone keeps the checkpoint and compares the answers.
ICANN
What the IGF's Paper Trail Says About Its Permanence
The Internet Governance Forum never had a constitution. Its authority comes from a chain of documents, each of which can be read for what it actually grants, orders or refuses. Reading that chain in full — the 2005 Tunis Agenda paragraph that created the forum, the General…
Story
DFINFRA and AS210860: the lifecycle ledger of a silent network
DFINFRA and AS210860: the lifecycle ledger of a silent network intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may follow. The…
History
The Exchange Was Authenticated. The Shared Secret Was Still “Uncomputed”
OAKLEY's fastest signed exchange could leave behind an authenticated name, a complete transcript and a proof of communication before either of those facts proved that usable key material existed. RFC 2412 made that gap explicit—and gave Internet security engineering an unusually…
CASE FILE
The Reply Came from an Egress. It Did Not Prove the Path: RFC 9655 and the Nil FEC Boundary
A green MPLS echo reply can be perfectly real and still answer a smaller question than the dashboard claims. RFC 9655 lets a headend verify that the final receiver owns the intended egress address when Nil FEC hides the rest of the forwarding equivalence. That closes a dangerous…
Story
RIPE NCC’s October Vote Sends Surplus and Deficit in Opposite Directions
The draft resolution for RIPE NCC’s October General Meeting assigns a 2026 surplus to reserves but a deficit to members in 2027. If members reject it, the agenda describes the reverse allocation; the 2025 meeting approved that alternative.
Story
RIPE ABUSE 2025-2026: The Enforcement Record That Still Never Fires
The RIPE NCC's abuse-contact regime ran at full volume through 2025, and the numbers are now on the record: 2,320 validation investigations, 86,959 validated email addresses, 2,825 assisted registry checks. What the same 2026-dated documents do not show is a single enforcement…
IETF
The proxy exposed the alias chain. It did not authenticate the host: RFC 9532
RFC 9532 gives an HTTP intermediary a precise way to disclose the DNS aliases it encountered on the way to its next hop. That visibility can reveal cloaking and explain routing, but it remains the proxy’s account of one resolver view—not a credential for the resource behind the…
Session Map
Governance Branch
RIR Watchdog
Five regional sessions tracking allocation policy, board legitimacy, and institutional continuity.
Open RIR WatchdogCase File
Long-cycle governance dossiers with legal, election, and institutional stress analysis.
Open Case FileNumber Resource Society
Membership, charter, and resource-governance intelligence from the NRS ecosystem.
Open NRS SessionICANN
DNS coordination, accountability frameworks, and global multi-stakeholder process dynamics.
Open ICANN SessionIETF
Protocol standardization trajectory and interoperability risk under fragmented policy conditions.
Open IETF SessionHistory of Internet
Long-cycle infrastructure history used for governance interpretation and structural forecasting.
Open History SessionNOGs
Operator-level implementation intelligence from APRICOT plus regional and national NOG ecosystems.
Open NOGs Session