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 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,572 articles

CASE FILE
The Controller Said Done. The Packets Had Not Testified: RFC 9757
RFC 9757 gives a PCE an experimental vocabulary for coordinating Native IP paths, but its acknowledgements end inside the controller–client conversation. Leadership still needs independent proof that BGP, routing policy, forwarding hardware and live traffic enacted the same…

History
Eight Bytes Drew a Recovery Boundary: RFC 2029 and CellB After Packet Loss
RFC 2029 gave every CellB packet its own spatial address: the first 4×4 cell’s coordinates and the image dimensions. That small repeated header let a receiver resume at a known place after loss, but it did not replace the missing cells or prove that the resulting frame was…

IETF
One MAC Address, Four Spellings: A YANG Draft Redraws the Duplicate Boundary
The proposed rule is easy to miss because nothing on screen has to change. A value can keep the colon, hyphen and letter case that arrived over the wire, while a second, invisible form decides whether another configuration entry is a duplicate.

History
One Agent, Many Machines: RFC 2037 Put the Scope Back into the Name
RFC 2037 treated an index as a local coordinate, not a universal identity: the agent, naming scope and mapping path had to travel with the number.

Story
APNIC Prop-173 Would Make Every Directory Query an Agreement. The Response Would Carry No Version.
An acceptable-use policy can change while the response governed by it remains in a cache for years. APNIC's prop-173 would make ordinary WHOIS, RDAP and web queries subject to a clear, versioned policy and would tell users that querying or using the service means agreeing to…

History
Elise Gerich and the Backbone Shutdown That Needed a Dress Rehearsal
The NSFNET backbone did not disappear when someone threw a master switch. Its retirement was a year-long exercise in proving that exchange points, commercial providers, route servers, databases and regional networks could stand without the system they were replacing. Elise…

IETF
The IETF Approved an ML-DSA RFC, Not a Deployment Recommendation
A standards body can finish a specification without finishing everybody’s risk decision. On 10 September, the IETF released the hold on *Use of ML-DSA in TLS 1.3* and approved it for publication as an Informational RFC. Three identifiers are already visible in the TLS registry.…

Story
RIPE Atlas Firmware 5130 Added an OpenWrt Hardware Architecture. The Rollout Needs More Than a Version Number
Firmware 5130 gives RIPE Atlas a new `openwrt-hwprobe` architecture for next-generation firmware on existing hardware probes. That is a concrete engineering change, not merely a roadmap line. Yet the number 5130 can identify a release without proving which source, toolchain…

IETF
The Highest-CoS Probe Does Not Measure Every BIER Service
A green continuity result can be both correct and dangerously overinterpreted. RFC 9974 allows an operator, in a particular composite-flow case, to test the highest Class of Service and derive the continuity state of lower classes. The sentence is operationally useful. It is not…

CASE FILE
The Receipt Behind the Cipher: What RFC 9771 Makes AEAD Buyers Prove
An authenticated-encryption label can be correct and still leave the decisive deployment question unanswered. RFC 9771 gives operators the vocabulary to distinguish a mathematical property, an implementation convenience, and an interface with different security rules. The next…

IETF
The Requirements Were Written. The Solution Was Not Proven
Revision 14 gives YANG versioning work a disciplined list of obligations: evolve modules without detonating dependency graphs, disclose compatibility, protect old clients, clarify retired nodes and explain migration. Its value is the questions it preserves. A requirements…

History
Mary Ann Horton and the Dial-Up Network That Had to Publish Its Own Map
Before an email address became a name, it could look like a set of directions. Every exclamation mark told a queued message which machine to visit next — and every omitted or stale hop could leave it stranded.

History
One Class A Subnet Could Defeat the Default: RFC 2036’s Compatibility Test
Opening unused Class A space in 1996 was not just a registry decision. It changed what every provider, customer domain and peer had to mean by a route: once a small component of an old classful parent appeared, inherited assumptions could send the rest of that parent away from an…

ICANN
ICANN’s New gTLD On-Call Contract Needs a Public Sunset Test
An emergency rota can succeed so well that nobody notices when it becomes the operating model. In May, ICANN described enhanced out-of-hours support for the 2026 new gTLD round as a six-month response to a defined period of pressure, followed by a return to regular business…

Story
AFRINIC Can Close a Support Ticket After About Ten Working Days. It Never Ranks the Risk.
A registry is right to ask who is touching its records. AFRINIC's public Contractual Obligations Check makes that defence concrete: the sender must be registered, the member must be in good standing and a signed agreement must be on file. The problem begins after a check fails.…

IETF
The eap.arpa Lane Must Close After Provisioning
The dangerous moment in device onboarding is not always the first packet. It can be the quiet minute after a certificate has been delivered, the dashboard has marked provisioning successful and the temporary access rule is still alive. RFC 9965 gives an uncredentialed EAP peer a…

Story
LACNIC's Open-Source Election Lookup Puts the Email Address in the Request Path
LACNIC's open-source election system authenticates a participation lookup before returning its answer. Yet the documented interface has already placed the entity identifier in the part of the request most likely to be copied by infrastructure. The distinction is not a disclosed…

History
Jean Armour Polly and the Internet Connection That Still Needed a Librarian
In 1992, “going online” at a public library did not begin with a browser. It began with a desk computer, communications software, a modem, a telephone line — and somebody who could turn that fragile stack into a public service.

IETF
Two YANG Versions Can Coexist While the Effective Schema Still Diverges
An upgrade can look calm precisely when its most consequential uncertainty has moved downstream: `draft-ietf-netmod-yang2-00` lets an older importer and a YANG 2.0 dependency remain together, but that accommodation proves far less than a shared client view of the network.

IETF
The Router Remembered a Listener. The Receiver Saw Nothing: RFC 9777
MLDv2 gives an IPv6 router a disciplined account of multicast interest on one attached link. The danger begins when that local, aging account is promoted into proof that an authorized application still wants the traffic—or that the traffic arrived.
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