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
3,256 articles
History
NSFNET Put IP Inside an OSI Address. Policy Still Chose the Route: RFC 1074
Thirteen T1 sites did not become one routing domain by choosing a pure protocol family. The 1988 NSFNET backbone carried IS-IS control packets over IP, fitted Internet addresses into NSAP-shaped fields, and let a policy database decide which EGP claims could become interior…
IETF
IETF Marks Two Capture Controls Incomplete. Their Q4 Proof Needs a Public Map
One line in the IETF Administration LLC’s 2026 Risk Register names the institutional failure that open technical organizations are often least comfortable naming: “The IETF, or a key part of it, is captured.” The same line says two controls are complete and two remain unfinished…
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…
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…
IETF
Sean Turner and the Private-Key Proof That Did Not Authorize a Certificate
A certification request can carry a valid signature and still have no right to become the certificate it asks for. The signature answers a narrow question about a key; identity, namespace entitlement, intermediary action and issuance remain separate decisions.
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…
History
The Client Owned the Window. The Server Owned the Reaction: RFC 1073 and Telnet NAWS
An 80-by-24 terminal window became 80-by-64 without opening a new Telnet connection. Four small values crossed the link, and the remote host gained a better chance of placing its cursor correctly. Nothing in that exchange required the host to use the new geometry. RFC 1073 made…
History
The Name Was Local. The Number Still Needed a Record: RFC 1101’s DNS Mapping Boundary
In 1989, DNS could already distribute host information, but it did not yet offer a standard way to ask what a network number was called. RFC 1101 proposed a small answer: use PTR records, host-zero names and masks in `IN-ADDR.ARPA`. Its lasting discipline is equally small. A…
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…
CASE FILE
What the Aggregate Report Actually Knows: RFC 9990 and the Boundary Before Enforcement
A DMARC dashboard can make a narrow observation look like a verdict. One receiver reports a large count from a source range, records an evaluated policy and shows a disposition. That is valuable operational evidence. It is not a global traffic census, proof of a sender's intent…
History
The Internet Was the Link, Not the Network: RFC 1070's Experimental OSI Boundary
In one of RFC 1070's imagined laboratories, two machines could exchange their OSI roles without changing either Internet address or cable. Every host would remain reachable by IP. Yet the experimental network could briefly lose its new router because an old list still pointed…
IETF
Lukasz Kondrad and the RTP Group That Was Not Yet a Reconstructed Scene
A session description can place an atlas, occupancy, geometry and colour stream inside one V3C group. That is a precise statement about membership—not evidence that a receiver rebuilt the same three-dimensional scene.
CASE FILE
W3C WebRTC Patch Says SFrame Covers Only Part of Retired Identity Work
An open correction to W3C’s next WebRTC charter separates two decisions that its public draft had joined together. WebRTC Identity may be discontinued because implementors have shown too little interest. SFrame may cover a limited subset of its use cases. But the Working Group…
IETF
IETF Tools Kept Every-Line Review for AI Code. Its Next Boundary Is Still Unwritten
The IETF Tools Team has named a genuine capacity problem: AI can produce ambitious pull requests faster than maintainers can safely absorb them. Yet the contribution guide it actually adopted in August still puts every submitted line in front of a human maintainer. That is a…
History
The Request Was Queued. The File Still Had to Move: RFC 1068 and BFTP's Completion Boundary
In 1988, an Internet file-transfer experiment made the instruction outlive the terminal session. A user could leave after submitting a job; a daemon would remember, retry and report later. That persistence solved a human waiting problem, but it also created a new fact that was…
CASE FILE
The Preference Was Published. It Was Not an AI Control: RFC 9969
RFC 9969 records an Internet governance problem without pretending to solve it by publication. A preference attached to content can tell another actor what an owner wants considered. It does not identify that actor, bind a downstream model, prove a use was compliant, create an…
CASE FILE
W3C’s Security IG Draft Excludes Standards Work but Retains Specification-Editor Roles
W3C opened refinement of a new Security Interest Group charter on 19 August. The draft draws a clear outer boundary: the group will advise, review and publish in-scope material, while Recommendation-track opportunities move to a competent Working Group or an incubation group. Yet…
IETF
Panos Kampanakis and the SSH Session with Three Different Security Receipts
An SSH client can negotiate a hybrid ML-KEM key exchange, verify the server through a conventional host key, and admit a user through a still separate credential. The session is one connection; the evidence is not one claim.
ICANN
ICANN’s $1 Million IGF Offer Draws an Advocacy Firewall
ICANN’s Board did more than authorize a large contribution to the Internet Governance Forum. Its published rationale drew a boundary around what the money was for, what it was not for, who would have to consent to a different use and how much institutional overhead should be…
CASE FILE
The Provisioning Realm Was Requested. It Was Not Network Access: RFC 9965
RFC 9965 gives an uncredentialed EAP peer a disciplined way to ask for a provisioning path. The `eap.arpa` realm and its provisioning identifier make a request legible; they do not authenticate the peer, prove a route, issue a credential or grant general network access.
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