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,529 articles
IETF
The IETF Approved Dynamic Flooding as an Experiment. “Acceptable” Still Needs a Measure
The IETF has authorized a test, not crowned a winner. Dynamic flooding may give dense link-state networks a much smaller graph over which to distribute updates, but the approved draft leaves operators with the hardest word in the evaluation: what counts as acceptable when the…
IETF
A Local Root Makes DNS Resilience an Operator-Controlled Failover Decision
RFC 8806 lets a recursive resolver answer root-zone questions from a complete local copy. The design can reduce dependence on a reachable remote root server and keep root queries off intervening networks. It also moves a consequential decision inside the operator’s own system…
CASE FILE
The Tag List Kept Its Order. It Still Lost Part of the Policy: RFC 9825
Four administrative tags left an OSPF area in the intended order. The next router supported only two. Its log said the list had been preserved; its policy engine therefore looked healthy. Yet the action-bearing tag had occupied the third position. No field was reordered, no…
ICANN
A GAC Early Warning Is a Signal, Not a Veto: The Applicant's Response Record
The 2026 Round gives a government representative a way to flag a concern without turning that notice into an automatic decision on the application.
IETF
The Label Arrived, but Did It Reach the Right Path? RFC 9884 and PSID Validation
A label can arrive at the intended egress and be popped there, yet still be associated with the wrong SR Policy, candidate path, or segment list. RFC 9884 makes that control-plane correlation testable with LSP Ping instead of treating reachability as proof of path identity.
Story
LACNIC’s 2025 Path Study Does Not Date Its Measurements
A year in a report title tells readers when an edition belongs on the shelf. It does not tell a network operator when the packets behind its charts crossed the wire. LACNIC’s regional path study offers a useful view of routes and latency, but leaves that second clock unstated.
CASE FILE
The Token Authorized the Tool. It Did Not Authorize These Arguments
OAuth can establish that an agent may call a payment, messaging or infrastructure tool. The dangerous decision comes one layer later: whether the exact destination, amount, command and live form state produced by the model are the act a principal or governed policy approved. An…
History
The RFC Published a Straw Poll. It Did Not Create a Constituency: RFC 1501
Two electronic addresses at the end of a two-page RFC offered individual OS/2 users a way to be counted. They were doors into a proposed organisation, not proof that the people behind those doors had already become members, chosen representatives or moved IBM.
IETF
The IETF Approved an IoT TLS Profile. It Still Does Not Authorize the Device
A constrained device can complete the right handshake, present an accepted credential and still have no right to perform the next action. The newly approved IETF profile makes that separation unusually explicit. It standardizes a secure transport baseline; it does not inherit the…
CASE FILE
The Header Said NOERROR. The Signed Body Said the Name Did Not Exist: RFC 9824
A security pipeline closed a nonexistent-domain alert because the DNS header said `NOERROR`. The validating resolver had reached the opposite conclusion from the signed NSEC evidence: the queried name did not exist. Neither observation was fabricated. One component had read the…
Story
LACNIC 46's Machine Records Still Say LACNIC 39 and LACNIC 45
The closing entry in LACNIC 46's current agenda belongs to the right event when read through its canonical taxonomy and presentation title. Three other fields still name LACNIC 45. A separate homepage field goes further back, to LACNIC 39. This is a small data-integrity problem…
CASE FILE
The Older Service Record Won. The Service Had Already Moved
A name collision is supposed to stop a newcomer from impersonating an established local service. Put two registration proxies between the service and that local link, however, and the same safeguard can protect yesterday’s address from today’s legitimate update. DNSSD’s proposed…
History
The Gateway Kept the Message. It Could Not Preserve Every Meaning: RFC 1496
RFC 1496 gave an X.400(84)–MIME gateway an admirably stubborn rule: convert what it can, encapsulate what it cannot, and never discard an entire message merely because one body part is unfamiliar. That discipline protected the carrier. It did not make every heading survive, every…
IETF
MOPS’ Draft Drops the Experimental Clause Without Recording the Verdict
The IETF is reviewing a light recharter for its Media OPerationS Working Group. The draft preserves the venue and its work, but removes the sentence that made the group an experiment. The old review is marked complete; the public change does not say what was learned.
Story
ARIN’s IRR Objects Keep the Channel That Created Them
An IRR object migrated from ARIN’s email service can be deleted in ARIN Online but not edited there. The asymmetry is defensible as a record of provenance. The trouble begins when the web remedy—delete and recreate—changes that provenance without a visible continuity receipt.
CASE FILE
The EAP Method Succeeded. The Protected Session Still Needed a Second Witness: RFC 9820
The access controller displayed three green facts: the EAP method had succeeded, the Master Session Key had been exported, and the constrained device had been placed in the security domain. Only the first two facts could be reconstructed. No one could produce the protected…
CASE FILE
The IESG Approved Three ML-KEM Groups. The Registry Recommended None
An approved IETF document can define exactly how three post-quantum groups travel through TLS while leaving the deployment verdict deliberately unresolved. That is not bureaucratic ambiguity. It is a precise boundary between an interoperable mechanism, a registry coordinate and…
ICANN
ICANN’s New “Time to Mitigation” Metric Does Not Time a Mitigation Act
Domain Metrica now estimates how long a reported domain keeps resolving. Its label sounds like an intervention stopwatch, but its start and finish are DNS observations—not the report and not the responsible actor’s action.
History
The Table Moved the Service. It Did Not Rename It: RFC 1498
A 1993 RFC recovered an older lesson: a table can change where a service runs while its name survives. Reaching it still requires separate evidence for the node, attachment point and path—and none of those bindings alone proves identity, authority or delivery.
History
The Code Was Available. The Original Specification Was Not: RFC 1492
The original TACACS specification existed, and the author of RFC 1492 could not obtain it because of copyright issues. What reached the public record in July 1993 was therefore an Informational reconstruction, constrained by running code and candid about the possibility that the…
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