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
The Route Reflector Hid the Choice: BGP ADD-PATH and the Authority to Expose Alternatives
A route reflector can make a large network easier to operate by showing each client only the route it selected. That economy also removes choices. ADD-PATH creates a way to carry several paths for one prefix, but the protocol does not decide which alternatives deserve exposure…
IETF
John Scudder and the BGP Session That Had to Declare Its Capabilities
Two routers may complete a TCP connection and still be unfit for the BGP job expected of them. One may understand an optional extension that the other has never implemented; both may understand it while only one admits support in the OPEN message; or an older peer may reject the…
CASE FILE
The Route Was Valid. The Reflector Called It a Loop: BGP Cluster IDs and the Authority to Discard Reachability
Every BGP session was Established. The customer prefix was valid at its source. Yet a regional reflector refused the route because a four-octet value in `CLUSTER_LIST` matched its own. The protocol had done exactly what it was told: an identity meant to stop loops had been reused…
History
The Preference Allowed to Lose: How Happy Eyeballs Races Paths
A valid IPv6 answer can still lead nowhere. Happy Eyeballs lets IPv6 start first, then allows observed reachability to win before the user pays a long timeout.
CASE FILE
The Policy Changed; the Routes Did Not: BGP Route Refresh and Re-evaluation Authority
Editing an inbound BGP policy changes a rule, not the routes already judged under the old one. To apply the new rule, a router needs the inputs again. Route Refresh lets it ask a capable neighbor to re-advertise the neighbor's current export set without destroying the session—but…
History
The Connection Beyond Its Address: Why QUIC Uses Connection IDs
Addresses and UDP ports can change while work remains. A QUIC Connection ID preserves continuity, but path validation and fresh identifiers bound trust.
CASE FILE
The Route Carried a Request, Not a Restraint: BGP NO_EXPORT and the Authority to Propagate
A route can arrive carrying `NO_EXPORT`, a name that sounds like a lock. It is nothing of the kind. The community tells a receiving network where the route is meant to stop, but the receiver's running policy still decides whether the value survives and whether the route leaves…
Story
APNIC's SIG Review Lists Twelve Changes Before It Has Decision Text
Twelve headings can make a governance review look nearly finished. They can also hide the one thing a consensus call must actually decide: the precise rules that will replace the current ones. APNIC's July SIG Guidelines draft has diagnosed a connected set of problems; its next…
History
The Name Created by a Question: How DNS Wildcards Stay Bounded
A DNS wildcard can synthesize a name never stored in the zone. Exact nodes, empty non-terminals and delegation still decide when that default may answer.
CASE FILE
The Neighbor Suggested a Door; We Chose Whether to Enter: BGP MED and Advisory Authority
The Neighbor Suggested a Door; We Chose Whether to Enter: BGP MED and Advisory Authority intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences…
History
The Name the Connection Could Not Carry: Why HTTP Needed Host
TCP reached an address and HTTP named a path, but a shared server still lacked the site name the user chose. HTTP/1.1 made that authority explicit in `Host`.
CASE FILE
The Route Chose Three Times, the Neighbor Heard Once: BGP MRAI and Temporal Authority
A BGP router can change its mind several times while saying nothing new to one neighbor. The silence is not indecision. MRAI deliberately separates local route selection from external disclosure, trading the peer's freshest possible view for bounded UPDATE traffic and processing…
IETF
Ketan Talaulikar and the Prefix That Kept Its First Router's Name
An OSPF prefix can cross an area boundary without losing reachability and still lose part of its history. The new LSA names the Area Border Router that relayed it, not necessarily the router that first originated it. RFC 9084, edited by Ketan Talaulikar with four co-authors, adds…
History
The Header That Disappeared Between Packets
RFC 1144 made a 40-byte TCP/IP header nearly vanish on slow serial links by letting adjacent endpoints remember shared state and send only changes.
Story
AFRINIC's Survey Can Count Replies. It Cannot Count Representation Yet
A response box can fill quickly and still leave the room outside it invisible. AFRINIC's new member and stakeholder survey may produce useful service evidence, but its eventual weight will depend on a record the launch has not yet supplied: who could answer, who was reached, what…
History
The Line That Looked Like the End in SMTP
SMTP ended unknown-length mail with a one-period line. Dot stuffing made that sentinel reversible; CHUNKING later moved the boundary to exact octet counts.
ICANN
ICANN Named Seven Leaders. The Selection Crosswalk Is Still Missing
ICANN's 2026 Nominating Committee has disclosed seven selectees, the size and demographics of a 223-person applicant pool, and part of the route from applications to final interviews. It has not yet shown, role by role, how published needs and a new Board-skills methodology…
CASE FILE
The Server That Remembered Nothing: SYN Cookies and Stateless Admission
A listening server usually spends memory after the first knock and before it knows whether anyone can hear the answer. A SYN cookie changes that order. The server places a compact receipt for the unfinished connection inside its own sequence number, then waits for the requester…
History
Permission Was Not Acceptance: Why HTTP Added 100 Continue
HTTP 100 Continue let a server reject from headers before a large body crossed the network, while keeping interim permission separate from final acceptance.
Story
RIPE's IPv6 PI Draft Has a Trigger but No Transition Receipt
Nine `/48` assignments can remain a valid deployed state while nothing changes. The next request for address space is different: it can activate a next-nibble decision, a contiguity test, a new prefix and a six-month return clock. Proposal 2024-01 names that trigger but does not…
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