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,381 articles
IETF
Paul Wouters and the IKEv2 Requirement That Was Not a Negotiation Receipt
“MUST implement” can sound like a deployment report. RFC 8247, co-authored by Paul Wouters, uses it for a narrower purpose: ensuring that IKEv2 implementations have a shared algorithmic baseline. It does not say which transform two peers offered, which one they selected under…
Story
The Refill Behind LACNIC’s Falling ASN Forecast
The Refill Behind LACNIC’s Falling ASN Forecast 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 intelligence…
ICANN
ICANN’s Diacritics Plan Would Tie Registry Exits Together
A new GNSO report would let certain ASCII and Latin-diacritic top-level domains operate together. The price of that exception is a shared operating future: related suffixes would move together when providers or control change, while removal would follow a different set of rules.
IETF
Bernie Volz and the DHCPv6 Trigger That Did Not Yet Configure a Client
A server log can make the word “Reconfigure” look final: the server issued the message, so a client must now have new settings. RFC 9915, co-authored by Bernie Volz, is more exact. Reconfigure is a carefully authenticated trigger for a later exchange. It is not, by itself, a…
History
The Route Named a Next Hop. The Link Still Had to Agree: RFC 1433
Two machines could occupy the same data-network service and still be unable to exchange a frame. RFC 1433 began from that uncomfortable fact: routing could identify a shorter next hop, while address resolution and link filters retained the power to make the route usable—or turn…
IETF
CATS OAM Can Verify a Steering Policy. It Cannot Choose a Remedy.
The active CATS OAM draft is trying to close a real visibility gap. A service instance can remain reachable at the network layer while the application behind it is slow, exhausted or unavailable. A system that steers traffic only by network reachability may therefore send clients…
CASE FILE
The Capability Was Advertised. The Protocol Was Not Authorized: RFC 9885
A zero-length IS-IS capability can be visible on every change-board screen and still be limited public evidence to authorize one configuration command. RFC 9885 makes that limit explicit: the advertisement is management information, not a protocol trigger, while safe MP-TLV…
ICANN
ICANN Checks Every Applied-for String for Geographic Meaning. What Must a Support Letter Prove?
ICANN’s 2026 Round checks every applied-for string for geographic meaning. Applicants need an authoritative, authentic and scope-correct support record—not merely a letter.
IETF
Wassim Haddad and the Prefix That Did Not Yet Authorize Forwarding
A mobile router can have a home-agent registration before it knows which mobile-network prefix it may use. RFC 6276, co-authored by Wassim Haddad, makes the next boundary explicit: only a valid DHCPv6 Prefix Delegation lease allows that prefix into the home agent's binding cache…
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…
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…
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…
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.
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…
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…
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…
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…
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…
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…
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.
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