Skip to main content

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
Governance signal visual
GovernanceGovernance
FocusInstitutional Governance

Policy continuity, legitimacy, and accountability signals across internet governance institutions.

CurrentSeven Governance Tracks

RIR Watchdog, Case File, NRS, ICANN, IETF, History of Internet, and NOG sessions.

SignalExecution over Statement

Coverage prioritizes implementation evidence and institutional behavior over declarative positions.

Latest Coverage

Latest from Governance

4,128 articles

History

The Name Service Was Almost a Negotiator: How RFC 830 Separated Domains from Capabilities

A file-transfer program asks for NIFTP. The destination has no NIFTP implementation, but it does offer FTP. In the architecture proposed by RFC 830, that mismatch did not have to end the attempt. One part of the name service found the destination domain; another part asked what…

Aug 30, 2026

IETF

Tero Kivinen and the New IKE SA That Inherited Live Child SAs

In IKEv2, the word “rekey” can describe two materially different successions. Replacing the protected control association creates a new IKE SA, yet the Child SAs carrying ESP or AH traffic can remain exactly the ones already in service. The distinction documented in RFC 7296…

Aug 30, 2026

IETF

The Old Segment Killed the New Connection: TCP's TIME-WAIT Assassination

A TCP connection can close before every copy of its packets has disappeared. TIME-WAIT is the protocol's quarantine between incarnations of the same conversation; RFC 1337 showed how an old segment could provoke the reset that ended that quarantine early.

Aug 30, 2026

CASE FILE

The Collection Held Every Evidence Item. It Had Not Bound Them to One Machine: RFC 9999 and the Composite Attestation Boundary

A verifier can receive a neat package labelled CPU, SmartNIC and GPU, decode every member and validate several signatures. None of those facts alone proves that the three reports describe the machine requesting access now. RFC 9999 makes remote-attestation messages portable; it…

Aug 30, 2026

CASE FILE

The Envelope Named the Evidence. It Did Not Bind the Device: RFC 9999 and the Authority Inside an Attestation Collection

A server can present signed reports from its CPU, SmartNIC and accelerator in one neat package. The package may be well typed, easy to route and validly encoded while still failing the question that matters: do all three reports describe this device, in this appraisal, under one…

Aug 30, 2026

ICANN

ICANN’s IRP Proposal Can Start the Outer Clock Before Claimants Are Affected

ICANN’s proposed Rule 4 gives a materially affected claimant 120 days after awareness to file for Independent Review. It also starts a 24-month outside clock on the date of ICANN’s action or inaction, whether the effect has reached that claimant or not. A four-year absolute…

Aug 30, 2026

Story

AFRINIC Has 3,573 Address Objects Pointing to Geofeeds. Its Schema Still Has No Geofeed Field

AFRINIC’s public database already carries geofeed pointers at material scale, but it carries them as prose. The fallback is valid and useful. The missing question is whether a convention used by thousands of address records should remain a string that the schema cannot identify…

Aug 30, 2026

CASE FILE

W3C's Interim CEO Also Sits on the Board That Oversees the Office

W3C restored executive continuity in one sentence on 28 May: its Board appointed Dominique Hazaël-Massieux Interim CEO with immediate effect. The current public roster adds a second fact. He is also a Partner-selected Director on the Board that oversees W3C Management and the…

Aug 30, 2026

History

The Number Did Not Make It a Standard: How RFC 825 Made Intent Part of the Record

A procurement clause says a product is “RFC 825 compliant.” The number looks precise, the link is public and the document is real. Yet none of those facts tells the buyer whether the cited memo was a standard, a discussion, a status report or merely information. In 1982, RFC 825…

Aug 30, 2026

Story

RIPE NCC Reports a 467-Day IPv4 Wait. The Queue Needs a Flow Ledger

RIPE NCC’s August member update says 757 LIRs were waiting for IPv4 space and the first LIR had been in line for 467 days. Its public chart records the queue’s size and its oldest wait, but those two stocks cannot show whether movement came from allocations, new requests…

Aug 30, 2026

IETF

Roy Fielding and the Method That Named an Intention, Not a Permission

An HTTP request begins with a compact public word. That word can tell a client, cache or intermediary what kind of result is being sought. It cannot say who is entitled to obtain it, whether the target will comply, or what happened after a connection failed. The architecture…

Aug 30, 2026

CASE FILE

WebTransport's Review Runs Past Its Published Working Group Charter

The WebTransport Candidate Recommendation still has two months of public review ahead of it. The public charter record for the group that published it stopped at 30 August. That is not proof of an unauthorized group or an invalid technical report. It is a public-state gap—and an…

Aug 30, 2026

CASE FILE

W3C Let a Paywalled Standard Stay Normative. The Exception Needs a Review Clock

In June, a W3C Council unanimously allowed the Digital Credentials specification to keep a normative reference to ISO/IEC TS 18013-7:2025 Annex C even though the ISO publication is not freely available. The Council called the result a narrow exception, grounded it in…

Aug 30, 2026

History

The Layer Was Not the Module: How RFC 817 Cut Across the Stack

One typed character could make three answers leave a server: a TCP acknowledgement, a window update and a Telnet echo. The protocol layers were each behaving correctly. The implementation was still wasting packets. RFC 817 used that small inefficiency to make a larger…

Aug 30, 2026

Story

RIPE NCC Needed 394 Supporters Before a Member Resolution Could Reach the Agenda

The number 394 was not a vote result. It was the price of admission to the vote: a cycle-specific calculation deciding whether a member-authored subject and its verbatim resolution would enter the General Meeting agenda. The rule has a sound institutional purpose. The public…

Aug 30, 2026

Story

LACNIC Published a 98% Outreach Score. The Response Count Is Missing

LACNIC says more than 330 organizations attended its 2025 member gatherings and that 98% of the feedback it received fell in the highest satisfaction levels. Both statements may be accurate. The public post does not disclose the number of responses, so the percentage cannot be…

Aug 30, 2026

ICANN

ICANN Routed India's Three DNS Requests. Only One Has Dated Milestones

India asked ICANN to treat three DNS-safety measures as immediate priorities. The formal reply did not simply say yes or no: it placed policy choice with the GNSO, implementation support with ICANN org, advisory participation with governments and technical testing with a separate…

Aug 30, 2026

IETF

Mark Nottingham and the User Agent That Could Not Speak for Every User

The browser can deny a service direct access to a person's machine, carry a narrow preference and make another implementation possible. Those powers make the user agent a valuable intermediary. They do not turn software, its vendor or a standards entity into the authorized voice…

Aug 30, 2026

IETF

IETF Invoked Its Emergency Plan. The Trigger Must Survive the One-Page Guide

The IETF Administration LLC says its Disaster/Emergency Recovery Plan was rolled out for IETF 126 and invoked when a hotel guest stole equipment. For IETF 127, one page will guide staff, contractors and volunteers. That is a promising conversion of experience into operating…

Aug 30, 2026

CASE FILE

The Address Was Unique. The Wire Still Saw a Collision: RFC 10019 and the Authority to Reconcile Zeroconf Multicast

Two isolated network segments can each make a locally correct multicast allocation. Join them, and both histories may remain truthful while the merged wire can no longer honour both claims. RFC 10019 turns that edge case into an operating principle: an address is not unique until…

Aug 30, 2026

Session Map

Governance Branch

RIR Watchdog

Five regional sessions tracking allocation policy, board legitimacy, and institutional continuity.

Open RIR Watchdog

Case File

Long-cycle governance dossiers with legal, election, and institutional stress analysis.

Open Case File

Number Resource Society

Membership, charter, and resource-governance intelligence from the NRS ecosystem.

Open NRS Session

ICANN

DNS coordination, accountability frameworks, and global multi-stakeholder process dynamics.

Open ICANN Session

IETF

Protocol standardization trajectory and interoperability risk under fragmented policy conditions.

Open IETF Session

History of Internet

Long-cycle infrastructure history used for governance interpretation and structural forecasting.

Open History Session

NOGs

Operator-level implementation intelligence from APRICOT plus regional and national NOG ecosystems.

Open NOGs Session