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
5,134 articles
Story
One Revoked Certificate, Three Browser Outcomes at APNIC 62
The certificate was on the revocation list. That was not the end of the story. Geoff Huston's APNIC 62 demonstration put the same adverse record in front of three browser policies and obtained different results—a useful warning about the distance between publishing a security…
History
The Record Was There. RWhois Could Not Find It: RFC 2167
A 1997 directory design exposed an uncomfortable difference between storing a record and putting it where a query can discover it. RWhois could refer a reader toward the responsible area; neither the referral nor an answer certified the underlying claim.
History
A Fast Bus Was Not an Ethernet: RFC 2143’s Missing Peer
The attraction was obvious in 1997: put nearby workstations on a fast SCSI cable and carry IP between them. The hard part was not fitting an IPv4 datagram into a command. It was making a peripheral bus accept an unsolicited message from another host—and finding a neighbor when…
IETF
Composite ML-KEM for CMS Cleared the IESG — Its Operational Dependency Chain Did Not
The IETF’s 18 September 2026 approval of `draft-ietf-lamps-cms-composite-kem-03` is an important standards milestone, but it is not the end of the delivery chain. The CMS companion is now in the RFC Editor queue while its normative Composite ML-KEM/X.509 dependency remains under…
IETF
A Batch Receipt Is Not a Security Action: The IETF’s Multi-SET Push Test
An IETF draft would send many security-event tokens in one HTTPS request. Its individual receipts may cut transport cost, but they leave a separate question for every receiving organisation: which event actually changed a local account or credential, and when?
History
The Connection Closed. Its Measurements Stayed: RFC 2140 and TCP's Host-Pair Memory
A short TCP exchange can finish before it has learned much about the route it used. In 1997, Joe Touch asked why the next exchange between the same hosts should have to forget everything the first had observed. The answer was not to preserve the entire connection. It was to…
IETF
Two “Not Ready” Reviews Put ACTN’s Packet–Optical Control Boundary on Trial
The IETF’s packet–optical ACTN draft has reached Last Call with an extensive map of controller interactions. Security and operations reviewers now ask what the map cannot settle: who trusts a topology update, and what survives when only one layer completes a change.
History
The Cheque Was Not the Ballot: What ISOC’s 1996 By-Laws Actually Allocated
An organization could finance the Internet Society at a level far above an individual subscription and still not acquire the trustee franchise described in its 1996 by-laws. RFC 2135 preserved a dated corporate arrangement in which money opened membership categories, regular…
History
The Socket Call Survived; the Address Contract Did Not: RFC 2133
A program could keep calling `connect()` after IPv6 arrived and still misunderstand the address it was sending. RFC 2133 preserved the familiar socket verbs while moving compatibility into the structures, families and kernel state those verbs carried.
IETF
The Last Call Is for the Question, Not the Filter
The IESG has opened a final comment period on how to describe the limits of inter-domain source address validation. The October 1 deadline concerns an Informational problem statement and requirements, not approval of a universal filtering protocol. The distinction matters at the…
History
One DHCP Packet, Four Different Claims: What RFC 2132 Did Not Identify
A client could put a vendor class, a binding key and a shopping list into the same DHCP message. RFC 2132 gave each a different job. Reading them as one trustworthy portrait of a machine mistakes a configuration exchange for proof of identity or operation.
History
The Command Stayed ASCII. The Reader Needed More Than Bytes: RFC 2130
A mail server's command and the explanation a person reads after it fails can travel in the same conversation. The 1996 IAB character-set workshop insisted they were not the same design problem. Its report, RFC 2130, treated international text as a chain of explicit choices, not…
History
The Circuit Answered. The Flow Was Not Ready Yet: RFC 2129
In Toshiba’s 1997 cut-through proposal, a router could hear that its neighbour recognized a virtual circuit and still have no permission to send a particular IP flow over it. RFC 2129 put those answers in two different exchanges—and made both answers expire.
History
Mary Shaw and the Protocol Between the Boxes
In 1994, Mary Shaw argued that software design had become fluent about the boxes and strangely inarticulate about the lines. Calling one procedure from another was useful machinery, but it was too small a language for the flows, events, shared representations, synchronization and…
IETF
JPEG XS Approval Does Not Prove a Working Upgrade
The IESG has approved the third-edition JPEG XS RTP revision, but a standards decision is only the first checkpoint. RFC publication, IANA registration, endpoint capability, SDP agreement, decoded samples and production enablement still require separate evidence.
History
One Call Became Many Interfaces. Several Channels Became One Call: RFC 2127
RFC 2127 made an ISDN connection legible by separating its physical access, signaling, bearer channels and upper protocol into distinct managed interfaces. That clarity came with a warning still useful today: a topology row, a call counter, a channel allocation and a service…
IETF
RFC 10040 Deprecates LCAF Type 5. Experimental Is Not a Migration Plan
RFC 10040 gives LISP a new Geo-Location encoding and marks the older Geo-Coordinates type deprecated. The publication is real, but it does not collapse document maturity, registry state, implementation support, interoperability, migration and responsible location-data use into…
History
Susan Eggers and the Core That Learned to Share Its Empty Slots
A wide processor can look powerful on a block diagram while leaving execution units idle whenever one instruction stream runs out of independent work. Susan Eggers and her collaborators asked a sharper question: what if several independent threads could compete for those…
History
RFC 2169: An HTTP Route Is Not a Resource Authority
In 1997, RFC 2169 made an intentionally modest proposal: use ordinary HTTP requests to ask a resolver about a URN. Its value was not that HTTP could settle identity. It was that a familiar transport could carry a narrowly defined question while leaving authority, access and…
History
Version 3 Stayed. The Service Changed: RFC 2126’s Compatibility Trap
An old peer could return a perfectly parseable Class 0 confirmation to a Class 2 request that offered no alternative. The TCP connection was open, the TPKT version was familiar, and the reply was still unacceptable. RFC 2126 made that difference explicit.
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