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,372 articles
ICANN
Sixteen Voting Directors and the Scale of Global Claims
Sixteen directors can lawfully govern ICANN and competently decide matters within its corporate Mission. They cannot turn a mixed nomination structure into an electorate for the world's Internet users. The Board's strongest claim to legitimacy is therefore bounded authority…
ICANN
ICANN's Articles Without Members
ICANN coordinates consequential parts of the Internet's naming system as a California public-benefit corporation whose governing documents expressly deny statutory membership. That choice is lawful, but it leaves participation doing work it cannot legally perform. The…
ICANN
The 1998 White Paper's Narrow Bargain
The document that cleared the path for ICANN was neither a world constitution nor an empty privatisation slogan. It proposed a single private coordinator for a defined set of Internet identifier functions, under principles meant to constrain capture and preserve national-law…
Story
A Thin Ledger With Rich Proofs
A registry does not become trustworthy by knowing everything about everyone. It becomes trustworthy when it records the few facts needed to establish unique authority, preserves every consequential change, separates the people who request and approve those changes, and lets…
Story
NRS Advocacy for a Portable Trust-Anchor Model
Number-resource recognition should survive a change of registry, certificate authority, repository or corporate form without forcing a holder to begin its history again. Number Resource Society can advocate this continuity and scrutinise the institutions responsible for it; NRS…
Story
Data Accuracy SLAs the RIRs Do Not Publish
An address record can remain reachable while being wrong, and a registry service can meet every uptime target while the wrong answer continues to circulate. Public dependence on number-resource data now deserves correction commitments measured from a reported defect to a verified…
Story
The Registry API Rate Limit as a Market Barrier
An RDAP or Whois quota can be a sensible defence against scraping and denial of service. It can also decide which broker completes diligence, which abuse analyst follows a campaign, and which new research firm can afford to enter. The legitimate control is not a secret number at…
Story
A Maintenance Window Across Twelve Time Zones
A registry engineer may schedule a change for the quietest hour at headquarters and still place the busiest hour of somebody else's network inside the blast radius. Fair maintenance is not the search for a universally convenient clock time. It is an institutional discipline that…
Story
Registry Logs as Evidence After an Incident
Registry Logs as Evidence After an Incident 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…
Story
Publication-as-a-Service and the New Middleman
Running an RPKI certificate authority no longer requires running the repository from which validators retrieve its entities. That separation can reduce a network operator's infrastructure burden and place global distribution with a specialist. It also inserts a service provider…
Story
Delegated RPKI and the Right to Hold Your Own Keys
Delegated RPKI promises that a resource holder can operate its own certification authority and retain the private key used to sign routing authorizations. The promise is technically substantial but institutionally incomplete. Key autonomy is usable only when the option is…
Story
RPKI MaxLength and the Cost of a Typo
A single prefix-length choice can turn an intended routing authorization into evidence that a legitimate route is unauthorized. The error then travels through certificates, repositories, validators and the policies of networks the resource holder cannot direct. Calling this user…
Story
AS0 ROAs: Conservation Tool or Pre-Emptive Denial?
An AS0 ROA says that a prefix and its more-specifics should not be used for public routing. Applied to genuinely unallocated space, it can turn a registry's conservation duty into a machine-readable warning against misoriginations. Applied to a wrongly classified or newly…
Story
RPKI-to-Router Deployment and the Missing Governance Layer
RPKI can tell a router that a route origin is Valid, Invalid or NotFound, but it does not command the router to carry or reject the route. Between a registry's signed statement and a packet's path sits a succession of validators, caches, router implementations, peering contracts…
Story
The Source Attribute That Became a Trust Label
In RPSL, `source:` was meant to identify the routing registry in which an entity was registered. Operators gradually made it do more. A short name such as ARIN, APNIC, RIPE or RADB now helps determine which declarations enter filters and which are ignored. That practical…
Story
IRR Route Objects After the Network Has Moved
A network can change transit provider, origin AS, corporate owner or regional registry while an old Internet Routing Registry route object remains where it was first lodged. That residue matters whenever an operator still turns registry declarations into prefix filters. Migration…
Story
The Parent Zone and the Power to Refuse a Child
A reverse-DNS operator can serve a technically perfect child zone and still remain invisible if the parent will not publish its delegation. In the hierarchy beneath `in-addr.arpa` and `ip6.arpa`, refusal can occur at more than one boundary, for more than one reason, under more…
Story
Reverse DNS as a Quiet Sanction
An address block can remain routed, its servers can keep answering and its forward names can still resolve, yet a small deletion higher in the reverse-DNS tree can make its mail look untrustworthy and its network harder to operate. That is why reverse delegation should not be…
Story
WHOIS History and the Right to Prove a Chain of Control
A current WHOIS or RDAP answer can identify the organisation recorded against an address today. It cannot, by itself, prove how that state came to be. Transfers, mergers, name changes, legacy allocations and disputed updates require a historical proof layer: one that preserves…
Story
The RDAP Bootstrap File as a Governance Map
The RDAP Bootstrap File as a Governance Map 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…
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