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,434 articles
IETF
DNS Serve-Stale Lets the Recursive Resolver Decide When Expired Data Is Better Than Failure
A DNS record reaches the end of its TTL just as every authoritative server becomes unreachable. The old address may still preserve a working service—or it may lead users back to infrastructure the zone owner meant to retire. Serve-stale keeps resolution alive by giving the…
CASE FILE
Two Answers Said NOERROR. Only One Carried the New Zone
RFC 9660 can bind a DNS answer to the zone version that produced it. That makes a mismatch visible without pretending that one version token proves the zone is correct, the fleet has converged or users saw the same path.
Story
Where Member Notice Stops: RIPE-865 and the Burden of a Public Record
RIPE-865 preserves the general position that RIPE NCC members are informed when authorities seek their data or registry action, unless notice is expressly prohibited. Its eEvidence section creates a different notification state: confidentiality applies, and the RIPE NCC cannot…
Story
LACNIC and the economics of IANA recognition and franchise risk
IANA recognition is not a commercial franchise, yet it creates a similarly scarce institutional position: one regional registry becomes the globally accepted gateway between an upstream numbering system and a defined community.
Story
APNIC’s Service-Term Delegation Has No Public Classification Receipt
APNIC’s Executive Council gave the Secretariat room to change service terms without turning routine administration into policy making. The delegation is sensible and expressly bounded. What the public record lacks is the small entity that would let a later reader test the…
CASE FILE
Internet Society Has a $329,000 Board Budget. Payment Disclosures Stay Internal
Internet Society's 2026 plan gives the public one Board number: $329,000. Its newly revised policies create real controls over trustee travel and other funding, but the disclosure chain ends with the Chair and the Board. The missing record is not a receipt folder on the open web.…
IETF
Brian Carpenter and the Boundary That Needed Proof
A network diagram can draw a clean perimeter around a campus, cloud overlay or industrial system. A packet cannot rely on the ink. Brian Carpenter and Bing Liu's RFC 8799 asks what must replace that intuition when a protocol has meaning only inside: verifiable membership…
History
The Number Two Peers Never Negotiated
The client placed 1,460 in its SYN. The server returned 1,200 in the SYN-ACK. Neither side yielded, because the numbers were not competing offers. Each endpoint was describing the largest TCP data segment it could receive. What either side would actually send remained a separate…
CASE FILE
The Timestamp Got Sharper. The Clock Did Not Gain Authority.
Send one NTP request through ordinary UDP port 123 and its arrival may be timestamped after software and queueing have already left fingerprints on the measurement. Wrap the same logical request in a PTP event message, and a compatible network card can timestamp it at the wire.…
CASE FILE
The Service Vanished. Its DNS Lease Did Not
A DNS Update Lease can make stale records expire without a cleanup command. It can also keep an authoritative answer valid long after the advertised service has stopped, because the server—not the requester—sets the operative publication horizon.
History
The Post That Had to Keep Its Name: How NNTP Bounded a Lost Final Reply
The article is already inside the server when the connection breaks. Perhaps the server said `240`; the posting client never heard it. On the next connection, absence from the reading view proves little, because moderation may still be under way. NNTP's answer to that uncertainty…
IETF
Three Supporters Would Buy an IETF Appeal a Hearing, Not Prove It Right
Imagine an appeal arriving at a review room with three tokens clipped to its cover. The tokens do not certify the facts inside. They do not say the appellant is right. They say three qualified people believe the institution should spend its scarce review time opening the file. A…
IETF
The Server Delayed the Cost of Belief: TCP's SYN-Flood Defenses
A TCP listener used to spend memory as soon as a stranger knocked. RFC 4987 explains how defenders moved that cost until the supposed client offered better evidence that it could hear the reply.
Story
AFRINIC Opened a Third Constitution Round. Every Comment Needs a Versioned Intake Record
AFRINIC’s Bylaws Review Committee continued constitutional consultation after the second-round deadline and narrowed attention to dispute resolution and safeguards around Resource Member termination. More time can improve the draft. It also creates a new recordkeeping duty: every…
Story
AFRINIC’s $20,790 MyAFRINIC Line Cannot Count Its Staff Work
AFRINIC’s half-year accounts put USD 20,790 of capital expenditure against MyAFRINIC v2. Six days before the reporting cut-off, its policy-meeting record said human resources had been channelled to the same project. The statements can both be accurate because they count different…
ICANN
ICANN Received 1,100-Plus Replacement Strings. What Can the 14-Day Switch Actually Escape?
An applicant can arrive at Reveal Day with a second-choice gTLD string and still discover that the backup is unusable before anybody has activated it. Under ICANN's 2026 Applicant Guidebook, a replacement string cannot be selected if it is identical to another applicant's…
Story
LACNIC and the economics of NRO coordination incentives
A regional Internet registry is not a shop that customers can abandon when service disappoints them. Internet number resources must remain unique, and each registry serves a defined region. That makes coordination indispensable. It also removes the most familiar market…
History
The Command Authentication Could Not Resume: How NNTP Made the Client Ask Again
An NNTP client asks for a restricted newsgroup and receives `480`. It authenticates successfully, yet the requested group does not open. The command must be sent a second time. That small repetition preserved a consequential boundary: proving an identity could change the…
History
The Acknowledgement That Retired a Memory
The sender still had data to send, but its peer had stopped sending data back. One ordinary packet now had an extra job: carry an acknowledgement of the peer's acknowledgements. In DCCP, that small addition could let the receiver release an old history. It did not recover a…
JPNOG
The RPKI Trial That Asked How to Fail Safely
Japan’s 2023 ROV exercise treated recovery as part of the security control, not as an apology after the control went wrong.
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