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
7,555 articles
History
Evelyn Berezin and the Boundary Between Uptime and Inventory Truth
Teleregister's United Airlines system could lose a processor and keep answering. That was a landmark of online engineering. It was not, however, proof that every answer about an available seat was true.
History
The Browser Remembered the Session. It Did Not Prove the Person: RFC 2109
In RFC 2109’s model shop, a server called a browser-held value `Customer="WILE_E_COYOTE"`. Later requests returned that value while separate cookies accumulated for a rocket launcher and a shipping method. The exchange made stateless HTTP remember a sequence. It did not make the…
CASE FILE
Internet Society Approved Its 2026–2027 Election Clock. Now It Needs an Activation Record
On 14 September, Internet Society’s Board completed two acts in one written resolution: it added four people to the committees supervising the next trustee-selection cycle, and it approved that cycle’s timetable “as attached”. The corporate decision is visible. The exact public…
History
The MIB Located the Address. The Repeater Still Had No MAC
A management station could ask which hub port had carried a source address, rank the busiest ports and reconstruct a shared-Ethernet topology. RFC 2108 made those answers comparable without pretending that the repeater itself understood a packet.
History
Kathleen Booth and the Line Between a Symbol and a Machine Order
In 1947, Kathleen Britten and Andrew Booth described a way to move from a mathematical plan to the exact fields their calculator would obey. The abbreviated notation made that crossing legible. It did not make the machine understand what the calculation meant.
CASE FILE
W3C’s LLM Note Assigns Personal Responsibility—but Not an Accountability Process
The W3C Advisory Board’s new note contains a strong sentence: each person remains responsible for work they share, whether or not a large language model helped produce it. The status paragraph contains an equally important limit. The document is an Advisory Board Group Note…
Story
RIPE NCC Closed the Test API Incident. The Recovery Join Is Missing
Four status updates show a pilot service moving from investigation to resolution in 37 minutes. They do not show the small set of facts that would let a user connect that green status to a particular test operation, a checked isolation boundary and a completed reconciliation.
History
The Address Said Home. The Dial-Up Line Said Away: RFC 2107
RFC 2107 let a remote dial-in client borrow the routing appearance of home. The illusion depended on a Foreign Agent, a Home Agent, a shared secret, a Tunnel ID and state that had to be created and destroyed in the right order.
History
Karen Spärck Jones Made Rarity Count; IDF Did Not Make It True
The same word can be commonplace in one document collection and unusual in another. Karen Spärck Jones turned that difference into a useful retrieval signal. Her achievement was not to discover a universal measure of importance, but to show how a collection can disclose which…
History
The Router Gave the Workstation an Address. It Did Not Give It an Identity: RFC 2106
RFC 2106 solved a real scaling problem by placing many remote SNA and NetBIOS workstations behind one DRAP server. The bargain was precise: fewer backbone peers, more state and judgment concentrated at the boundary.
History
The Tag Moved the Packet. It Did Not Prove the Path: RFC 2105
A packet entered a switch carrying a short tag. The machine used that value as an exact index, selected an interface, replaced the tag and sent the packet onward. That was the elegant part of Cisco’s 1997 Tag Switching proposal. The harder truth sat elsewhere: routing protocols…
CASE FILE
W3C’s Browser Portability Group Starts With a Report, Not a Standard
An iPhone user can now move selected Safari data into another browser through a documented export-and-import path. That is a real product capability. The W3C Browser Data Portability Community Group, launched on 15 September, is something else: a place to discuss principles and…
IETF
An Open Meeting Is Not an Antitrust Alibi: RFC 9680
RFC 9680 is most useful when read as a map of separated responsibilities. IETF procedure can make technical coordination open, contestable and reviewable. It cannot turn a published RFC, a declaration of rough consensus or a crowded meeting into proof that competitors never…
IETF
When Fast Reroute Must Stop: RFC 9791 and the Responsibility Boundary Behind NFFRR
RFC 9791 gives a deceptively simple answer to a hard failure problem: once fast reroute has already redirected a packet, a downstream node may need to refuse another local repair. The difficult part is not the idea of a marker. It is the authority embedded in that marker—the…
CASE FILE
The Grammar Changed. Your Acceptance Boundary Might Not.
RFC 9682 repairs CDDL’s collected grammar and adds a cleaner hexadecimal escape form, but the important compatibility boundary is not the publication date of the RFC. It is the point at which a particular source model meets a particular parser, becomes a particular validator…
History
Two Hash Passes Made a Reusable MAC. The Tag Did Not Make a Trust Decision: RFC 2104
RFC 2104 gave protocol designers a compact way to turn existing iterative hash functions into a message authentication code: one keyed inner pass, one differently keyed outer pass, and an interface that could survive replacement of the hash beneath it. What endured was the…
History
The Locator Moved. Then the Network Moved: RFC 2103
Nimrod’s mobility paper began with an elegant separation: keep the endpoint’s identity stable and update the locator that says where it can be reached. Then it found the case that broke the elegance—a network could move while the endpoint’s locator stayed the same, leaving the…
IETF
When “Lease” Stops Meaning “Address Assigned”
An operator upgrades a DHCPv6 inventory schema and discovers that one familiar dashboard label—“lease”—now conceals two different origins of authority. In one record, the server selected or delegated the resource. In another, the device selected a SLAAC or static address and…
History
The Tree Was Not Standardized. The Forwarding State Was: RFC 2102
Nimrod declined to choose one multicast tree algorithm. Its narrower bargain was more durable: different methods could coexist if routers agreed on the shape and meaning of the state that actually replicated packets.
History
The Cell Skipped the Router’s Work. It Did Not Inherit the Route: RFC 2098
At a Cell Switch Router, one tiny lookup decided whether an arriving ATM cell stayed a cell or became an IP datagram again. A matching VPI/VCI entry sent it straight through the switch; a miss returned it to reassembly and IP forwarding. RFC 2098 built a fast path from that…
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