Skip to main content

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
Governance signal visual
GovernanceGovernance
FocusInstitutional Governance

Policy continuity, legitimacy, and accountability signals across internet governance institutions.

CurrentSeven Governance Tracks

RIR Watchdog, Case File, NRS, ICANN, IETF, History of Internet, and NOG sessions.

SignalExecution over Statement

Coverage prioritizes implementation evidence and institutional behavior over declarative positions.

Latest Coverage

Latest from Governance

8,052 articles

A sculptural directory panel with two illuminated endpoints, detached pointers and one dark endpoint.

Story

Inside AFRINIC’s Reverse-DNS Cleanup

The registry’s public data distinguish delegation records, domain entities and resource holders. They also distinguish an error inventory from removal events. Those differences explain why a falling count can reflect worthwhile maintenance without measuring the restoration of…

Sep 3, 2026
Anonymous glass signal tokens pass through a measurement lens to a blank evidence sheet, a separate open decision frame, a routing card, an unfinished module and a review ring.

IETF

IETF's Survey Can Diagnose a Governance Problem. It Cannot Ratify a Repair.

The IETF Community Survey 2025 gives the organisation a more useful picture of itself than a slogan ever could: a large but imperfect sampling frame, a modest voluntary response, a clear account of what was counted, and a set of concerns that should not be wished away. That is…

Sep 3, 2026
Four parallel network work paths leave one early chassis, passing through a memory upgrade, route aggregation comb, unfinished address lattice and open future architecture beside a finite tray of amber engineering tokens.

History

The Interim Fix Bought Time. It Could Spend the Future: RFC 1380

The Internet of 1992 had more than one deadline. Router tables and Class B allocations were under immediate pressure; a larger address space and a richer Internet layer demanded slower architectural work. RFC 1380 refused to hide that mismatch inside one programme. It recommended…

Sep 3, 2026
A faceted core inside a glass test enclosure connects to three sockets beyond the enclosure

CASE FILE

ITU’s Agent-Security Agenda Makes Deployment Part of the Test

A draft programme for ITU’s 7 September workshop asks what evidence integrators should demand from suppliers of agents, tools and models. That puts the security claim where the system acquires its powers—and raises a question about how far a supplier’s earlier test can travel.

Sep 3, 2026
Conceptual map of a conference route moving from Colombo to Kolkata beside governance documents and an unresolved authority node.

SANOG

SANOG 34 Moved Cities Without Publishing Its Crisis Authority Chain

SANOG 34 did something operationally difficult: it moved a regional conference from Colombo to Kolkata for what SANOG described as the recent security situation in Sri Lanka, while keeping the dates intact. SANOG's own archive records the move, names the original and replacement…

Sep 3, 2026
An early-1990s terminal sends blank catalog cards through separate network paths and a dated amber plane toward files and an independently controlled bookshelf.

History

The Network Found the Book. It Could Not Keep the Shelf Current: RFC 1432

In March 1993, a bibliography about the Internet carried an unusually revealing provenance: much of its detail had arrived through the Internet itself. The network could help a reader discover a book, yet RFC 1432 also preserved the reasons discovery could never certify the…

Sep 3, 2026
An amber diagnostic packet and label stack cross several obscured branching transit planes before only the egress aperture confirms the endpoint in green.

CASE FILE

The Path Label Reached the Egress. The Transit Route Stayed Unseen: RFC 9884

One green LSP Ping result can answer a narrow and valuable question: the egress processed a Path Segment Identifier in the control-plane context named by the probe. It cannot reveal the transit route that delivered it. RFC 9884 makes that boundary operationally useful—provided…

Sep 3, 2026
Thomas Graf in an AI editorial portrait beside abstract MPLS label-stack forms and a restrained classification boundary.

IETF

Thomas Graf and the MPLS Label Number That Did Not Identify Its Control Plane

An MPLS label can look like an answer: a compact number at the top of a stack, captured in an export record and ready to be counted. Thomas Graf’s RFC 9160 begins with the smaller, more useful proposition. The number alone does not reliably tell an observer which control-plane…

Sep 3, 2026
A wordless fictional editorial scene: a sealed artifact capsule rests on a blue transparent ledger while a separate human hand pauses above an amber release control.

IETF

SCITT Can Log a Statement. It Cannot Authorize a Release.

RFC 9943 gives software-supply-chain evidence a useful public property: a signed statement can be recorded in a transparency service and accompanied by a verifiable receipt. That can make an issuer’s assertion easier to inspect and harder to rewrite quietly. It does not answer…

Sep 3, 2026
Blank IPv6 request cards split into automatic and reviewed paths before stopping at a gap beside a separate allocation ledger.

Story

ARIN Publishes IPv6 Requests Beside Delegations. The Cohorts Are Not Joined.

An IPv6 request can enter ARIN’s system, pass automatically or move into staff review, prompt a request for more information, receive approval, wait for fees and a signed agreement, and only then become an issuance. ARIN publishes useful numbers at the entrance and the exit of…

Sep 3, 2026
A teaching module separates into image, sound and caption layers beside a second maintenance cradle

IETF

IETF Separates Training Scripts From Slides. Now Test the Handover.

The IETF's latest training-procurement answers make captions, transcripts and narration scripts separate source assets. That is a useful move toward maintainable course material. Its value will become visible when someone other than the original producer has to correct a module.

Sep 3, 2026
Two autonomous network cabinets exchange message capsules through a transparent connection tube while a separate amber timing wheel and retry shuttle remain outside the transport path.

History

The Transport Opened a Connection. SNMP Still Owned the Retry: RFC 1283

A connection is an enticing piece of evidence. It has a beginning, a lifetime and an end. In 1991, RFC 1283 placed SNMP on an OSI connection-oriented transport and then warned implementers not to read too much into that new structure. The connection could carry one or more…

Sep 3, 2026
A cyan signing chamber marks blank request plates while a separate violet key-establishment core remains untouched beyond an amber policy gate and issued tiles retain return conduits to the signer.

CASE FILE

The Request Was Signed. The Other Private Key Was Still Only Asserted: RFC 9883

A certificate request can carry a valid signature and still offer no technical proof that the requester holds the private key named by its new public key. RFC 9883 does this deliberately. It turns the gap into an explicit policy choice—and a revocation dependency that operators…

Sep 3, 2026
Tommy Pauly in a fictional abstract editorial setting that distinguishes a QUIC transport acknowledgement from application processing.

IETF

Tommy Pauly and the QUIC ACK That Did Not Reach the Application

A QUIC acknowledgement can close one precise transport question while leaving the question an application actually cares about open. RFC 9221, co-authored by Tommy Pauly, makes that seam unusually visible for DATAGRAM frames: the receiver's transport processed a frame, but the…

Sep 3, 2026
An editorial illustration separates a few legitimate directory queries and a temporary cache from a blocked attempt to assemble a large substitute database, with a review path at the boundary.

Story

APNIC's Directory Terms Proposal Turns Query Access Into a Governance Question

Prop-173 would replace ambiguity around ordinary APNIC WHOIS and RDAP queries with a public, versioned acceptable-use policy. The consequential question is not whether terms should exist, but whether their rules distinguish legitimate operational reuse from a substitute data…

Sep 3, 2026
Editorial illustration of a time-bounded domain-control check beside a separate application identity lifecycle timeline

IETF

DNSOP Can Recommend a Domain-Control Check. It Cannot Govern an Application Identity’s Lifecycle.

The DNSOP working group is in Last Call on a useful document about applications that use global-DNS names as identifiers. Its central discipline is easy to miss. A service may need proof that a registrant or an authorized party controls a domain when an integration is…

Sep 3, 2026
Стенд каталога начала 1990-х отделяет подсвеченную целевую карточку, лоток дополнительных карточек и пять по-разному взвешенных механизмов в одном тестовом дереве.

History

The Client Found the Person. The Score Still Belonged to One Directory: RFC 1431

A successful search can be the beginning of an evaluation rather than its conclusion. In February 1993, RFC 1431 asked what an X.500 directory client had actually accomplished when a person's entry appeared—and what the answer had cost inside one particular directory.

Sep 3, 2026
Transparent governance records separating a contributor fee, eligibility, declared interests, recusal and appointment before an empty board chair.

Number Resource Society

When a Contributor Fee Opens a Governance Door, the Record Must Show Why

A contributor fee can support serious community work, and a fee-paying contributor can be qualified for leadership. The governance problem begins only when a public eligibility promise is not matched by a record showing how contributor status, nomination, interests, recusal and…

Sep 3, 2026
An amber message splits into a direct lattice-signing path and a digest-and-attribute path while an isolated blue token sits above the computation and a violet intermediate crosses into a separate custody chamber.

CASE FILE

RFC 9882 Put SHA-512 in the Field. It Did Not Always Use It

A CMS record can truthfully name SHA-512 while that algorithm contributes nothing to the signature being checked. RFC 9882 requires exactly that combination on one of its two ML-DSA paths. The apparent contradiction disappears only when an auditor follows the bytes rather than…

Sep 3, 2026
A newer cyan packet reaches an acknowledgment plane while an older amber packet remains behind a time boundary and one coral tail probe arcs through the path.

IETF

The Newer Packet Arrived First: How TCP RACK Used Time to Find Loss

RACK changes the evidence TCP can use when looking for loss: not only sequence-space gaps, but also the transmission times of data known to have arrived.

Sep 3, 2026

Session Map

Governance Branch

RIR Watchdog

Five regional sessions tracking allocation policy, board legitimacy, and institutional continuity.

Open RIR Watchdog

Case File

Long-cycle governance dossiers with legal, election, and institutional stress analysis.

Open Case File

Number Resource Society

Membership, charter, and resource-governance intelligence from the NRS ecosystem.

Open NRS Session

ICANN

DNS coordination, accountability frameworks, and global multi-stakeholder process dynamics.

Open ICANN Session

IETF

Protocol standardization trajectory and interoperability risk under fragmented policy conditions.

Open IETF Session

History of Internet

Long-cycle infrastructure history used for governance interpretation and structural forecasting.

Open History Session

NOGs

Operator-level implementation intelligence from APRICOT plus regional and national NOG ecosystems.

Open NOGs Session