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
4,349 articles
NANOG
Who Gets the Scarce Minutes?
A conference agenda is not merely a timetable. It is a budget of collective attention. NANOG's published materials show technical talks, parallel rooms, workshops, keynotes, community coordination and commercial networking sharing a finite clock. The public record can show how…
ICANN
GAC Consensus Advice Starts a 21-Day Response Record, Not an Automatic Board Outcome
Formal GAC Consensus Advice changes the applicant's procedural position, but it does not itself supply the ICANN Board's decision.
AFNOG
AIS 2026 Promises Selected Recordings Without Naming the Selector
AIS 2026 is presented as a hybrid summit whose virtual entities will receive live-streamed sessions, interactive discussions and access to selected recordings. The word “selected” creates a governance question: who decides which sessions become part of the accessible record…
IETF
When a Drone ID Becomes a DNS Delegation: RFC 9886 and the Registry Chain Behind Remote ID
A Broadcast Remote ID can carry a compact DRIP Entity Tag (DET), while the public evidence needed to authenticate registry inclusion is distributed across reverse-DNS delegations, HHIT and BRID records, and a certificate chain. The practical question is therefore not only whether…
History
The Header Described an Archive. It Did Not Authorize the Decoder to Run It: RFC 1505
The line counts agree. The archive expands. The checksum closes. A shell command now waits in a directory created from an email message. In 1993, RFC 1505 drew the most important boundary at exactly this point: successful decoding was not permission to execute.
Story
AFRINIC Invited Members and Stakeholders to a Survey. Results-Publication Status Is Unknown in the Frozen Source Set
AFRINIC published a survey invitation to members and stakeholders, but the frozen source set does not establish whether results were published or what decisions followed.
IETF
The QUIC Spin Bit Is a Sample, Not a Latency SLA
A passive latency graph can go blank while a QUIC service remains healthy. The signal may have disappeared because an endpoint did not participate, traffic paused, or connection context changed—not because round-trip time became infinite.
CASE FILE
The Challenge Released the Message. It Still Had Not Reached the List
The IETF plans to replace the machinery behind its email services on 11 September. The design usefully separates challenges, list handling, identity rewriting, signing and outbound transport. It also makes the central operating question unavoidable: when one component reports…
Number Resource Society
A ROA maxLength Is Not a Traffic-Engineering Policy
A route can be RPKI Valid because a ROA’s maxLength admits its prefix length. That result proves a bounded origin authorization. It does not prove that the more-specific route was planned, approved, currently announced or preferred by the operator. Those are separate facts, and…
Story
LACNIC’s IPv6 allocation rules make scale plannable
**BTW analysis:** IPv6 offers a vast address space, but abundance alone does not tell a network operator what it may request, how need will be assessed, or what obligations follow an allocation. In Latin America and the Caribbean, those practical questions meet LACNIC’s published…
IETF
When 255 Octets Stop Being Enough: RFC 9885 and Multi-Part IS-IS TLVs
A syntactically valid IS-IS LSP can leave a receiver with an incomplete entity when information crosses the 255-octet limit and the receiver processes only one TLV occurrence. RFC 9885 defines how to recognize and process those related occurrences without changing the underlying…
IETF
Happy Eyeballs Is a Racing Budget, Not Proof of Dual-Stack Health
A page can load normally while one address family is unusable. Happy Eyeballs protects the user by letting another candidate win, but that success becomes misleading when operators treat it as evidence that the whole dual-stack service is healthy.
NANOG
The Late-Submission Exception
Urgency is a legitimate reason to keep a technical programme open. It is not, by itself, a sufficient rule for deciding who gets the remaining stage time. NANOG's public record offers both sides of that problem: a historical late-submission process governed by committee…
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…
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