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,160 articles
ICANN
ICANN Completes String Similarity Before Priority Batches. What Does the All-Strings Rule Protect?
A late Priority Number does not place a proposed string outside the comparison universe. ICANN's 2026 Round rules require the similarity review to cover every applied-for string before evaluation batches are formed.
Story
AFRINIC’s IPv6 Condition Names Three Percentages but Not the Meter
The proposal’s benign ambition is understandable: turn passive IPv6 holdings into actual, gradual deployment while using traffic information operators may already collect. The unresolved question is whether the proposed percentages can be reproduced, checked and fairly reviewed.
CASE FILE
The Registration Began with a Surname; Later Use Still Had a Separate Record: Nissan Motor v Nissan Computer
The label stayed the same while the page behind it changed. That difference—between the provenance of `nissan.com` and the later uses made of it—became the organising fact of a dispute that lasted through preliminary relief, a sweeping injunction, appeal and remand.
History
The Receiver That Chose What Came First
Before SMTP, a mail receiver could answer `MRSQ ?` with `215 T Text first, please`. It was asking for the complete message before it learned a single recipient. Another receiver could prefer to collect every address and accept one shared body afterward. This was more than syntax.…
CASE FILE
The Zone Went Dark. The Resolver Made the Outage Louder
When authoritative DNS stops answering, the first failure belongs to the zone. The next thousand queries may belong to the resolver. RFC 9520 draws a narrow but consequential line between the two: silence is not proof that a name does not exist, yet a resolver that has exhausted…
Story
AFRINIC Extended Its Bylaws Consultation. Its Only Named Form Went Down Four Days Before the Deadline
A deadline is a promise about access, not merely a date printed on a page. AFRINIC gave contributors until 17 May to use a designated constitutional-comment form; on 13 May it announced that the form host was unavailable, leaving the public record without the timestamps and…
CASE FILE
PP-26 Registration Does Not Accredit a State to Vote
A person can be admitted to an international conference while the authority to cast a State’s vote is still unresolved. PP-26 makes that separation unusually explicit: online registration opens an access process, an original diplomatic instrument opens an accreditation process…
CASE FILE
The Block Was Explained. The Policy Was Still a Claim.
The night shift sees an authenticated DNS response that says a name was blocked, identifies a policy category and offers a support route. The explanation is orderly, machine-readable and intact. It still does not reveal whether the upstream classification was right, who had…
History
The Byte the Sender Did Not Send: How FTP MODE C Reconstructed Filler from TYPE
A decoder reads a run count and reaches the next item without finding a value to repeat. Nothing has been lost. In FTP's compressed mode, that absence was a complete instruction: the missing byte had already been chosen elsewhere, by the representation type negotiated on the…
CASE FILE
IEEE 802's WRC-27 Comment Expires in Five Years. Its Public Record Should Not
IEEE 802 LMSC sent European spectrum policymakers a position on WRC-27 on 21 August. Its own rules put an unusually clear limit on that act: public statements to government bodies expire five years after issue. The limit is valuable only if two records stay separate—the…
ICANN
ICANN’s Priority Number Does Not Order String Evaluation. Which Five Checks Run Outside the Queue?
An applicant draws a low Priority Number and immediately gains a story to tell: its application is near the front of ICANN’s processing queue. That story is useful, but incomplete. The number does not place every part of the application near the front of every line. ICANN’s own…
History
The Route That Moved Backward at Every Relay
ONE received a forward-path that already contained its own name: `@ONE,@TWO:JOE@THREE`. It removed `@ONE`, then prepended to the reverse-path the name by which the next mail environment knew it. The route still waiting to be followed became one step shorter. The route available…
Story
The 27 August Redline: Reading APNIC’s prop-165 Through Its Assessment Delta
APNIC’s canonical `prop-165` record now points to `prop-165-v004`, published on 27 August 2026, while the Secretariat analysis displayed on that record is expressly introduced as applying to version 3. With the APNIC 62 Open Policy Meeting scheduled for 10 September 2026, the…
History
The Byte That Had to Appear Twice: How FTP Put Record Boundaries Inside a Stream
Two identical all-ones bytes could cross an FTP data connection side by side and emerge as one byte of file data. Change only the second byte to a small control value and the first became an escape announcing the end of a record, a file, or both. Early FTP solved a problem that a…
CASE FILE
The Proof Verified. The Fork Was Still Private.
Every response on Alice’s device verifies. Every later tree head extends the one before it. Across town, Bob sees the same tidy sequence—except his latest head commits to a different key for Alice. The log has not broken either local proof chain. It has separated the witnesses.
IETF
Ray Bellis and the Proxy That Had to Forward the Unknown
A small gateway often presents itself as a helpful DNS interpreter: one address for the household, one upstream resolver, one place to cache an answer. RFC 5625, authored by Ray Bellis, starts from the more difficult premise. The gateway cannot know what DNS will mean after its…
Story
RIPE-861 Recommends Off-List Nominations. The Candidate List Needs a Receipt
RIPE's new guide gives a quiet volunteer a private way to approach a continuing working-group chair. That can widen participation. It also moves the first step outside the public archive, making the later conversion from interest to a complete candidate list the part that needs…
ICANN
ICANN’s Prioritization Draw Sets the Queue. What Can a Low Number Actually Guarantee?
A physical ticket costing USD 100 will help determine when a 2026 new gTLD application is processed. The mechanism sounds almost ceremonial beside an application system built around technical evaluations, objections and contracts. Its effect is not ceremonial.
CASE FILE
The Handshake Succeeded. The DNS Question Was Already Exposed
RFC 9539 lets a recursive resolver encrypt its next hop to an authoritative server without waiting for the server to advertise a new policy or present a verifiable identity. That modest bargain can hide many DNS questions from passive observers. It also creates an unusually…
History
The Missing Page That Was Not Zero: How FTP STRU P Carried Holes Across Hosts
An FTP transfer could move from one indexed page to a later one without sending anything for the position between them. That gap was not a dropped packet and it was not a page full of zeros. In FTP's page structure, absence itself belonged to the file map—and preserving it…
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