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
8,859 articles
Story
A Correct RIR Record Did Not Fix One Geo-IP Error After Two Months
An APNIC 62 case study exposed a small but consequential accountability gap: the registry data could be right, several geolocation databases could agree, and one downstream service could still send a customer to the wrong country.
IETF
A Valid CoSERV Result Is Not a Completeness Proof
A relying party asks for the reference material needed to judge attestation evidence. The query is deterministic, the response is signed, the contents are still valid and every cryptographic check succeeds. That is a strong result—but a bounded one. The exchange proves what was…
Story
ARIN Can Attach a Ticket to an Org ID. That Does Not Make It the Organization’s Decision.
ARIN fixed a mundane but costly support problem: staff no longer need to begin every ambiguous question by asking which organization it concerns. The resulting Org ID selector gives a ticket context and a durable home. That is good service design. It also makes one distinction…
History
The Zero Handle Opened a Door. It Did Not Grant Entry
In 1996, RFC 2054 tried to remove two conversations that stood between an NFS client and its first useful file reference. Its answer was not a new permission system. It was a disciplined gamble: try the port most servers already used, try the newer protocol first, and present a…
History
A Cipher Name Was Not Enough: RFC 2040 and the Missing Identity of RC5
RFC 2040 reads less like a manifesto for a cipher than a parts ledger for agreement. Its lasting historical value is the discipline with which it separates a family name from an executable identity: word size, rounds, key length, expanded state, chaining state and the rule used…
IETF
INTAREA Adopted a Registry Cleanup. IANA Has Not Applied It.
An Internet-Draft can acquire a working group without changing a single live registry. That is what happened on 11 September: INTAREA published its version of a proposal to close one legacy list, assign procedures to three others and remove a fifth. The institutional handoff is…
History
Kees Neggers and the Backbone Europe Built in Parallel
On 26 September 1992, one link between London and Montpellier completed Ebone’s initially defined backbone. The more revealing number was not its line rate but its age: 390 days since a small group had first met outside Amsterdam to ask whether Europe could operate a shared IP…
IETF
A Token Status Bit Is Not a Revocation Timeline
A relying party reads one compact value and declines a credential. The decision may be correct. Yet the bit alone cannot say when the underlying state changed, who authorised that change, when the list exposed it, which cached copy was consulted or why this application treated…
Story
APNIC’s Priority Survey Has Three Bases: 1,039, 1,038 and 1,037.
APNIC asked its community to divide exactly 100 points among eight strategic activities. The resulting chart looks unusually complete: every point is accounted for and no priority overwhelms the rest. The publication trail is less settled. Three official artifacts attach three…
History
The Configuration Row Vanished. RFC 2051 Kept the Session Alive
RFC 2051 turned an obscure APPC management model into a durable lesson about evidence: the record of what should exist can disappear while the record of what is already running remains true.
IETF
The Zone Was Still Answering. The Signing Key Was Already Gone
A correctly signed zone can outlive the private key that produced it. That interval is not recovery; it is a perishable option whose value depends on preserving old cryptographic state while proving, clock by clock, that a replacement chain has taken over.
Story
AFRINIC-38 Has a Named Safety Concern. A Hybrid Format Is Not a Risk Assessment.
A public message from an experienced Malawian operator does not prove that Cape Town is unsafe. It does something more precise: it puts a concrete delegate concern into AFRINIC-38’s record. AFRINIC’s own meeting guide already treats security as a location-selection input. The…
History
Karen Banks and the Gateway That Did Not Need to Stay Online
A message could wait on a local machine, travel during one brief telephone call and still reach an international public. Karen Banks’s work on GreenNet’s GnFido gateway shows why early access was a chain of queues, operators and partners—not a light that simply switched from…
History
The Decoder Could Restart Before the Picture Was Whole: RFC 2038’s MPEG Slice Boundary
RFC 2038 turned an MPEG slice into a visible transport boundary. A receiver that saw an RTP sequence gap could wait for a packet declaring the next slice start and rebuild limited picture context from repeated fields—but that restart said nothing about whether the earlier picture…
IETF
DANCE 14 Turns Four TLSA Outcomes Into a Two-Way Server Decision
Four DNS observations can now enter the same TLS policy gate. The latest DANCE client-authentication draft tells a server what to do when it receives anything other than a DNSSEC-validated TLSA record set: abort, or continue while treating the client as unauthenticated. Revision…
IETF
A Signed Transaction Token Does Not Attest Every Claim
A service accepts a correctly signed Transaction Token and treats every nested value as independently verified by the signer. The signature is real, the token is intact, and the conclusion is still too broad. What the Transaction Token Service chose to carry is not the same…
History
The Registry Issued the Address. RFC 2050 Refused to Promise the Route
In 1996, an organisation could receive globally unique address space, appear in the public registry and still lack the one thing a casual reader might assume came with both: a route across the Internet. RFC 2050 made that limit explicit because the registry was only one actor in…
Story
RIPE Atlas Put Reconnects and Liveness Through One Event Processor. A Slow Backend Blocked Both.
A RIPE Atlas software probe could have working Internet access on 8 June and still be shut out of the measurement network after a routine disconnect. The public incident record explains why: reconnect work and controller-liveness evidence passed through the same event processor.…
History
Yvonne Marie Andrés and the Classroom That Had to Write Back
A school could own a computer, find a telephone line and deliver a message without yet creating a networked classroom. Yvonne Marie Andrés understood the missing test early: somewhere beyond the school, another class had to care enough to write back.
IETF
A TLS Flag Is Not a Feature-State Record
A monitor stores flag 8 as `true`. That compact fact does not say whether a client proposed a feature, a server announced it in a ticket, an acknowledgement was required, early data was involved, or the feature was ever exercised. The bit can be exact while the state inferred…
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