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
4,359 articles
History
The Address That Recruited a Subnet: Why Routers Stopped Forwarding Directed Broadcasts
One IPv4 datagram could cross the Internet as an ordinary routed packet, reach the router responsible for a remote network and become a local broadcast there. With a victim's address forged as the source, that last-hop conversion could turn willing hosts on someone else's subnet…
History
The Area Learned the Route. The Backbone Had Not: RFC 1587
Published on the Standards Track in March 1994, RFC 1587 described how one external route could be present, current and usable inside an OSPF area while the backbone had no advertisement for it. That was not necessarily delay or failure. In the Not-So-Stubby Area, it was the…
CASE FILE
The Firewall Did Not Recognize the TLS Parameter. Blocking It Would Have Broken Extensibility: RFC 9761
A new ClientHello value can mean malware, a legitimate update, deliberate GREASE or simply that the firewall is older than the endpoint. RFC 9761 makes that uncertainty operational: compare the device's declared profile with what the firewall actually understands, then keep…
CASE FILE
An OpenSSF Scorecard Is Not a Dependency Decision
OpenSSF Scorecard turns selected repository signals into a compact public measurement. That is useful precisely because it is narrow. A number can focus a dependency conversation; it cannot decide whether a particular release belongs in a particular system.
IETF
A Finality Sink Cannot Protect the API That Routes Around It
Put the strongest possible verifier in front of one tool call. Bind the exact act, check the signer, reject stale authority and consume every nonce once. The result may still be an unprotected system if the same agent holds a credential for a second endpoint. A new individual…
CASE FILE
A CODEOWNERS File Is Not a Review Receipt
A `CODEOWNERS` file can tell GitHub where review responsibility should be routed for a changed path. That is useful machinery. It is not a historical record of who was selected for a particular pull request, whether the eligible person received or completed a review, or whether…
History
The Link That Borrowed Its Address: How Relative URLs Made Documents Movable
A short hyperlink is not a small absolute address. It is an instruction to borrow missing components from a base. That dependency let authors omit repeated schemes, hosts and path prefixes, and it let a collection of pages move while preserving its internal edges. The economy…
CASE FILE
The Chain Passed. The Header That Said So Was Unsigned
A new DKIM2 draft gives mail systems a compact way to report a verified custody chain. Its sharper contribution is the warning attached to that convenience: the report is a local, unprotected memo, not evidence that can be inherited by the next hop.
CASE FILE
The Router Set the P Flag. No Prefix Had Been Delegated Yet: RFC 9762
An IPv6 Router Advertisement can now tell a capable host to prefer a delegated prefix over another address from the shared link. That one bit arrives early enough to prevent a disruptive double start. It still cannot stand in for the DHCP exchange, the relay route or a packet…
History
The Line Went Silent. The Route Stayed Reachable: RFC 1581
A quiet circuit used to look like missing evidence. Demand RIP made quietness the intended operating state. In February 1994, RFC 1581 and RFC 1582 described how routers on X.25 and ISDN could stop waking every peer with periodic updates, close idle calls, and keep the last…
CASE FILE
An SPDX License Expression Is Not a Compliance Verdict
An SPDX expression can make a licensing statement easier to exchange, compare and correct. That is valuable precisely because the statement has limits. A syntax-valid string can identify information that an author declared, information someone found in a file, or a conclusion…
History
The Sender Named the File. The Receiver Still Owned the Disk: RFC 1806
An attachment can arrive with a name and an instruction to stay closed until requested. Neither statement proves that a file was created, that the name is safe, or that the recipient surrendered control of the machine. Content-Disposition became durable because it carried intent…
IETF
PT-03 Puts Its Trust Summary Inside the Signed Request. The Hash Is Not the Authority
A human is asked whether an agent may proceed. Beside the action sits a tidy trust summary: judgment 0.88, self-assessment 0.82, trend improving. The summary's hash matches. That still does not answer the governing question: was this the summary the enforcement component signed…
CASE FILE
A Rust Trademark Permission Is Not a Rust Project Decision
A permission to use the Rust name or logo can be important: it tells a reader something constrained about how an identity claim may be presented. It cannot, by itself, make its holder part of the Rust Project, establish that a team reviewed code, turn a repository into an…
History
The School Got a Connection. Its Policy Still Had to Be Written: RFC 1578
The circuit could come up before the institution was ready. In February 1994, RFC 1578 explained Internet access to primary and secondary schools by separating things that the verb “connect” made too easy to merge: a path, a set of usable applications, trained people, technical…
Story
RIPE NCC’s Fibre Returned in Minutes. Access Recovery Took About Thirty Minutes
On 27 May, a supplier’s work in a manhole disconnected RIPE NCC’s fibre for only a couple of minutes. The connection came back and recovery was automatic. Yet RIPE NCC says it took about thirty minutes for everything to recover. The useful question is not whether automation…
CASE FILE
The Large BFD Packet Stayed Up. The Whole Path Was Not Proven: RFC 9764
A green BFD session can now say something useful about packet size, but only if the claim stays as narrow as the packets that earned it. RFC 9764 turns padded control traffic into a recurring lower-bound test. It does not turn one forwarding treatment into a certificate for every…
CASE FILE
The Packet Carried a Resource ID. The Path Did Not Promise to Obey
An IPv6 packet may name the resource partition it wants at every hop and still emerge without proof that every router recognized the request, used the intended queue or preserved the promised isolation.
History
The Provider Was Written into the Address. Then the Field Disappeared
IPv6 did not begin with a timeless answer to who should sit between a site and the global routing table. Its early documents tried several physical layouts for that authority—and left a remarkably frank account of who would pay when aggregation, portability and resilience pulled…
History
Three Telnet Options Made a Terminal. None Named the Session: RFC 1576
A standard had already designed one explicit switch into 3270 mode. Running systems chose three switches instead. By 1994, Terminal-Type, Binary and End of Record could make an ordinary Telnet connection carry a block-oriented IBM display stream, even though the client still…
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