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
4,427 articles
CASE FILE
Both Connections Reached OPEN; Only One Could Remain: BGP Collision Detection and the Authority of a Stable Identifier
Both routers dial at once. Two TCP connections complete between the same pair of addresses, and each carries a valid BGP OPEN. Neither transport is broken. Yet one configured peering cannot keep two competing finite-state machines and two versions of its session history. BGP…
History
The Write That Had to Name Its Past: Why HTTP Needed 428
A write request can be perfectly formed and still be too ignorant to trust. HTTP 428 gave an origin a precise way to demand the missing fact: which version of this resource did the writer actually see?
History
The Name That Chose a Service: How DNS SRV Found Servers
A domain once led clients toward one address and a remembered port. DNS SRV made service location an explicit, bounded choice among hosts.
CASE FILE
The Peer Kept Sending but Stopped Receiving: BGP SendHoldTimer and the Authority to End a One-Way Session
The neighbour is still sending KEEPALIVEs, so the BGP dashboard remains green. Yet its TCP receive window has collapsed to zero and none of the local withdrawals can leave the socket. The session is established, inbound liveness is real, and the route information held by the…
CASE FILE
Internet Society Seated Four Trustees. The Challenge Record Still Stops at “Rejected”
Four Internet Society trustees began three-year terms in July after an election cycle that included one formal challenge. The Board disclosed that it reviewed background material and associated audit results before unanimously rejecting that challenge. What the public still…
CASE FILE
The Route Was Accepted So Packets Would Die: BGP BLACKHOLE and the Authority to Destroy Reachability
A blackhole announcement is a rare routing message whose success is measured by non-delivery. That inversion can save a network during a DDoS attack, but only if the right to sacrifice one destination is narrower, more observable and more reversible than the emergency that…
CASE FILE
The Session Could Carry It; the Next One Could Not: BGP Extended Messages and the Authority of a Shared Size Budget
A BGP speaker accepts a 12-kilobyte UPDATE, selects the route and prepares to propagate it. The next neighbour accepts only the old 4,096-octet envelope. Nothing is malformed, the policy still prefers the path and the prefix is valid—yet the complete announcement cannot cross the…
IETF
Hannes Gredler and the OSPF Link That Had to Drain Both Ways
An operator makes one end of a circuit prohibitively expensive, watches routes leave, and calls the link drained. Yet packets can still enter from the neighbour because OSPF does not advertise one indivisible circuit: each router originates its own directional state. Hannes…
Story
LACNIC's ASO AC Result Became Official Without a Closure Receipt
At 18:00 UTC on 20 August, one public election table crossed a consequential boundary. The names and 144 votes did not change. The page's status did: the provisional result became the official result after two audit windows. What did not appear beside that new status was the…
History
The Request That Had to Wait for Proof: Why HTTP Needed 425
TLS 1.3 let returning clients send requests before a new handshake finished. HTTP 425 made replayable early data wait without changing the request itself.
CASE FILE
The Monitor Saw the Route, Not the Packet: BGP BMP and the Authority of a Control-Plane Witness
A monitoring feed can be accurate and still support a false conclusion. BGP Monitoring Protocol gives operators structured views of routes before policy, after policy, at export and after selection. Those views are not interchangeable. The first duty of a BMP system is therefore…
CASE FILE
The Metric Crossed the AS Boundary: BGP AIGP and the Authority to Define One Interior Cost
Two autonomous systems can belong to one operator and still speak different mathematical languages. If one calls a 10-millisecond link “10” and the other calls a high-capacity link “10,” adding their metrics produces a precise number with no coherent meaning. BGP AIGP can carry a…
History
The Alias That Could Not Move Authority: DNS DNAME
DNAME redirects descendant lookups by replacing one suffix. The owner, zone apex and NS delegation stay put even when many queries follow the new subtree.
CASE FILE
The Backup Was Chosen Before the Failure: BGP PIC and the Authority of Precomputed Forwarding
When a backbone link fails, the first packets do not wait for a committee of routing processes to reconsider millions of destinations. On a router using BGP Prefix Independent Convergence, they may follow a backup that was selected and installed hours earlier. The speed comes…
Story
ARIN's New “Sole Use” Definition Has No Observation Window
Imagine one address prefix serving three anycast sites: one inside ARIN's service region and two outside it. The inside site is withdrawn for maintenance, then restored an hour later. The holder, service design and prefix have not changed. Under the wording of a new ARIN…
History
The Save That Left the Page Intact: HTTP 204
HTTP 204 says an action finished without replacing its active view. Status marks completion, while headers carry post-action identity without response content.
History
The Connection That Was Not Authority: Why HTTP Needed 421
HTTP learned to save time by letting several named origins share one authenticated connection. Status 421 preserved the limit of that bargain: a channel can be reachable, secured and reusable in principle without being the connection context through which a particular origin is…
History
The Copy That Arrived as a Difference: HTTP 226
HTTP 226 lets a changed representation travel as instructions for a cached base. Base, delta message and reconstructed result retain separate identities.
CASE FILE
The Reflector Chose from the Wrong City: BGP ORR and the Authority to Compute Another Router’s Best Exit
A centralized route reflector can make a path decision from a place where no customer traffic ever flows. BGP Optimal Route Reflection lets it calculate from a client’s logical position instead. The mechanism restores a missing perspective, but it also creates a new delegated…
History
The Alias That Did Not Need a Second Walk: HTTP 208
WebDAV could expose one collection through two paths. HTTP 208 keeps the second path visible while omitting descendants already reported through the first.
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