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 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,910 articles

IETF
The New IETF Steering Draft Says Drop. A Legacy Headend May Still Redirect
A failed steering instruction can now produce two opposite-looking outcomes. Revision 18 tells a supporting headend not to fall back to ordinary IP redirection when explicit Segment Routing intent is incomplete or unresolved; it must drop the matching traffic or use a declared…

AFNOG
AIS 2026 Calls Distance No Barrier Without Publishing a Hybrid Participation Standard
AIS 2026 promises live streams and interactive discussions and says distance is not a barrier. The current first-party page reviewed here does not publish the service and remedy standard behind that commitment.

NANOG
The Hybrid Denominator
Hybrid access is easy to announce and hard to measure. NANOG’s official record shows a progression from an exclusively virtual meeting in 2020 to hybrid events and persistent webcast participation. It documents real channels for questions, chat and remote presentation. It does…

History
The Reset That Could Not Be Trusted: TCP-AO After a Peer Reboot
TCP normally has a blunt way to tell a peer that an old connection no longer exists: send a reset. TCP-AO makes that answer harder to trust on purpose. When a protected peer reboots and forgets its connection state, the reset it can still send may be precisely the reset the…

AFNOG
AIS 2026 Names the Power to Exclude but Not a Meeting Appeal Route
AIS 2026 makes one end of its conduct system clear: AFRINIC may exclude a registrant from the meeting, including chat or other communication channels. The public pages reviewed for this article do not make the full meeting-specific decision and review chain equally visible.

IETF
An Extended DNS Error Explains Failure Without Authorizing a Different Answer
A DNS failure can be technically correct and operationally opaque. RFC 8914 lets a responder attach a more precise explanation to the result, but it deliberately leaves the result itself unchanged. That separation gives operators a useful observability channel—and creates a…

Story
AFRINIC's Monitoring Button Is Deployed and Disabled
AFRINIC's deployment monitor contains the control announced in its August release, but not the address that would make the control usable. The public code handles that absence carefully: it leaves the button hidden. That is good failure behaviour. It is also evidence that a…

Story
LACNIC’s RPKI controls make route origin authority operable
LACNIC’s RPKI controls make route origin authority operable 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 Story…

Number Resource Society
An ASPA Is Not a Complete AS-Path Attestation
An ASPA can help an operator test whether an AS path is consistent with published customer-to-provider authorizations. That is valuable route-leak evidence. It is not a signature over every hop, a proof of route origin, a commercial contract, or a guarantee that the published…

AFNOG
AIS 2026 Can Change Its Attendance Terms Without Publishing a Notice Rule
AIS 2026 says its attendance terms may be amended and become valid upon publication. It also treats attendance after a change as confirmation that a registrant has accepted it. The reviewed terms do not say how a consequential change will be brought to each registrant's attention…

NANOG
A Meeting Room Is Not North America
NANOG can convene an unusually useful concentration of network expertise. That does not turn the people in one room—or on one stream—into the electorate of North American network operations. The distinction protects the value of the forum by making its claims more exact.

ICANN
A Material Change to Public Application Content Opens 30 Days of Comment, Not Automatic Approval
When ICANN finds that a requested change materially affects public application content, the request enters a 30-day comment process but has not crossed the approval line.

Story
AFRINIC Offered In-Person Registry Checks at AfPIF. The Frozen Page Does Not Report Outcomes
AFRINIC promoted face-to-face help with registry records, identity checks and open requests at AfPIF 2026; the frozen source set does not show what was completed.

IETF
QUIC Migration Can Fail Before the Connection Does
A QUIC connection can remain cryptographically alive while becoming unable to use a new path. The missing resource may be neither keys nor congestion window, but an unused connection ID supplied by the peer.

AFNOG
AIS 2026 Requires an ID Upload Without Publishing Its Handling Rule
AIS 2026 asks every registrant to upload a passport or other government-issued identity document. The public registration and terms pages explain several uses of attendee information, but the reviewed text does not explain the specific lifecycle of that required file.

Number Resource Society
An RPKI Cache Serial Is Not a Freshness Timestamp
Two RPKI caches can report perfectly accurate serial numbers and still tell an operator nothing about which cache holds newer global data. RFC 8210 scopes a serial to one cache session and protocol version. Treating the larger number as the fresher view manufactures a chronology…

IETF
The Insecure Middle of a Secure TACACS+ Migration: RFC 9887 and the Cost of Dual-Stack Authentication
A TACACS+ client using TLS must not fall back to non-TLS when TLS negotiation fails. Yet a migration can temporarily keep separate non-TLS TACACS+ servers for devices that cannot move at once. That coexistence is not a secure dual stack: RFC 9887 considers the mixed phase…

History
The Segment That Returned to the Same Number: TCP-AO's Sequence Number Extension
A TCP sequence number can come back during one long-lived connection. TCP-AO had to ensure that the repeated 32-bit value did not also repeat the evidence presented to its authenticator.

CASE FILE
The Notification Arrived. One Backend Still Had Nothing to Serve
The IETF is asking for final comments on a proposed operating guide for RPKI publication services. Its sharpest rule is also the easiest to violate during a routine rollout: do not expose the new notification until every snapshot and delta it names is already available. An index…

IETF
QUIC's Three-Times Limit Is an Address-Validation Budget, Not DDoS Protection
A QUIC server can have the next handshake bytes ready and still be forbidden to send them. Before it knows that a client can receive packets at its claimed address, every received byte grants only a bounded amount of transmission credit.
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