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
5,016 articles
CASE FILE
The CRL Number Was Higher. RPKI Still Had to Ignore It: RFC 9829
A relying party retrieves two signed revocation lists from one publication point. The first carries the larger CRL Number. The second is the file named by the certificate and hashed on the issuer’s current manifest. A generic PKI instinct says to trust the larger counter. RFC…
AFNOG
AfNOG Publishes Fellowship Criteria, Not the Procedure That Applies Them
AfNOG’s published Abha Ahuja Bursary application page tells candidates what the fellowship is looking for. It identifies a selecting committee, lists eligibility criteria and says incomplete applications will not be considered. The reviewed page does not set out how those…
CASE FILE
The Trace Linked the Action. It Did Not Prove the Authority
A new IETF discussion list asks how an agent’s intent, delegation, changing permissions and external actions can be followed across services. The hard part is not inventing a universal trace identifier. It is preventing that identifier—and the agent’s own account of events—from…
Story
A TTL Jump Can Make a RIPE Atlas Trace Invent an AS Link
A traceroute can place a destination directly after one visible network even when several unseen routers still forwarded the packet. The missing segment is not always silence or a tunnel. New RIPE Atlas research shows that an on-path device can raise the probe's TTL and let it…
Number Resource Society
A BGPsec Router Certificate Is Not Route-Origin Authority
A BGPsec Router Certificate Is Not Route-Origin Authority intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may follow. The Number…
History
The Router Saw a New Network. It Was a Shadow of Its Own Mapping: RFC 1504
The route looked newly learned and the number was locally valid. The awkward fact was that no second network had appeared. A number invented at one translation boundary had travelled around a redundant path, lost its lineage and returned as if it belonged to a stranger.
History
The Key That Could Change Mid-Connection: TCP-AO's Rollover Signal
Long-lived routing sessions made a simple operational question unusually dangerous: how can two endpoints replace an authentication key without dropping the TCP connection or guessing the same switching instant? TCP-AO answered with visible key identifiers and directional…
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…
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