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,337 articles
IETF
Paul Hoffman and the Root Copy That Could Answer Only Its Own Host
A recursive resolver can keep the entire DNS root zone close enough that a root query never leaves its machine. RFC 8806 permits that local execution path, then surrounds it with unusual restraints: the service cannot answer the next host, cannot invent a byte of root data…
Number Resource Society
A ROA Change Needs an Authorization-and-Withdrawal Ledger
A route can be Valid while the organization behind it has already forgotten who approved the authorization, what changed, or how to reverse it. ROA governance needs evidence that joins intent, publication, observation and withdrawal—not another screenshot of a green status.
History
The Counter That Fell While Traffic Kept Rising: How SNMP Marked a New Measurement Epoch
A link can carry traffic continuously while its byte counter suddenly becomes smaller. SNMP made that apparent contradiction manageable by separating normal numeric wrap, wider observation windows and an explicit marker for the moment a measurement history breaks.
CASE FILE
The Route Advertised 70. The Local Link Could Carry 50: RFC 10005 and Bandwidth Authority
One upstream says it has 70 units of capacity. The receiving router can reach that upstream only across a 50-unit local link, yet policy assigns it 70% of the traffic. The BGP UPDATE is valid, every session remains established, and congestion is still the expected result. RFC…
Story
RIPE NCC’s Two Voting Codes Need a Credential Map
RIPE NCC tells October’s voters to expect two codes in two emails. That is a useful instruction, but it is not yet an account of the control. The names “Code 1” and “Code 2” describe a user journey; they do not show what each credential proves, who can recreate it, or when a…
Story
ARIN’s 29 August Stats Pair Split Across Two 2023 Filenames
ARIN’s public statistics directory contained a small but unusually legible publishing error on 29 August. The current data and checksum were available under their correct 2026 names, yet current-period artifacts also appeared through two extra paths dated 2023—and those two paths…
Story
AFRINIC Is Shrinking Its Data-Centre Footprint. Recovery Now Crosses a Cloud Boundary
AFRINIC's 2025 infrastructure report describes a sensible modernisation: retire obsolete equipment, use a smaller physical estate, place backups off site and test restoration every quarter. The harder question begins after the backup succeeds. Can the registry show that an…
ICANN
ICANN Tests Two-Character gTLDs Against Two-Letter ASCII Codes. What Does That Gate Actually Protect?
A two-character label can be valid enough to enter the 2026 Round and still be stopped because it resembles a two-letter ASCII code. The important question is not simply whether ICANN says no. It is which gate said no, which label or variant caused the comparison, and whether the…
History
The Socket Closed Before the Command Finished: How FTP Kept Completion on the Control Connection
An FTP data socket can go quiet at the exact moment an operator most wants a verdict. The bytes have stopped, the connection has closed, and a file may even be visible on disk. Yet the protocol has not asked any of those observations to decide the command. FTP kept that decision…
CASE FILE
The DNS Said the Domain Was for Sale. It Did Not Have Authority to Close the Deal
RFC 10023 makes a registered domain’s availability visible in DNS. Its compact signal can open a negotiation while the domain remains in use; it cannot identify the rightful seller, bind a price or complete the transfer.
History
The Number That Changed While the Session Stayed: How SDP Separated Identity from Revision
A multimedia description can change its address, codec, direction and timing without becoming a different conversation. SDP made that continuity testable with two deliberately separate coordinates: one names the session lineage, the other names the description's revision.
CASE FILE
Internet Society's Resolution 2026-13 Points to Two Different Policies
The Internet Society's public records currently make one resolution number perform two jobs. Its trustee-selection procedures say they were modified by Resolution 2026-13. Its travel policy and formal e-vote register assign the same number to travel-policy amendments approved on…
IETF
Stuart Cheshire and the Half-TTL Rule for Silence
The strangest useful mDNS query is one that already contains answers. A host puts its cached records into the question so nearby responders can decide not to repeat them. RFC 6762 makes that silence conditional: the record must still carry at least half its proper TTL, and nobody…
Number Resource Society
A RIR Representation Mandate Needs a Scope-and-Revocation Ledger
A public member list can show who has appointed a representative, but it cannot by itself show what that representative may do today. When the subject is Regional Internet Registry governance, authority needs a versioned record of scope, time, action and revocation rather than an…
Story
APNIC's Firewall Reboot Put Registry Writes and Repository Reads Under One Clock
APNIC says a network firewall detected a hardware fault and rebooted on 28 August, interrupting six named service surfaces for an incident window of eight minutes. The short duration is reassuring. The single clock is not a complete recovery statement, because the list stretches…
History
The Hash That Stayed While the Keys Changed: How SSH Bound Authentication to One Session
An SSH connection can replace the cryptographic machinery protecting it without making every shell, file transfer or forwarded channel begin again. The protocol made that continuity explicit: the first key exchange left behind a hash that later keys could not rename.
History
The Number That Grew at Every Cache: How HTTP Age Estimated a Response Without Dating the Object
A browser can receive `Age: 120` for a document written years ago. The apparent contradiction disappears once the field is read narrowly: HTTP did not ask caches to date content. It asked each cache to carry forward, correct and extend an estimate about one stored response.
CASE FILE
The Zone Was Online. One Address Family Could Not Reach Its Authority: RFC 10001 and DNS Partition
The dashboard stayed green because its resolver quietly used IPv4. An IPv6-only resolver followed the same published delegation, reached a missing dependency and stopped. The name had not disappeared; its authority existed on one transport path and not the other. RFC 10001 turns…
CASE FILE
The Route Tree Remembered Every Target It Saw. It Did Not Authorize the Detour
SIP History-Info can show how a request moved from one target to another. That makes it valuable evidence. It does not make the resulting route complete, truthful, permitted or successful.
History
The Bit That Ended the Record: How ONC RPC Put Message Boundaries Back on TCP
A TCP reader can receive half a header, three complete calls or the tail of one reply. None of those read sizes says where an RPC message ends. ONC RPC solved the problem with four bytes: 31 bits counted one fragment, while the remaining bit closed one record after that…
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