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 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
7,645 articles

IETF
IETF Opened an AI Standards List Without Defining Its Decision Path
The IETF has given a disputed question a dedicated address. On 9 September, its Secretariat created `[email protected]` for discussion of artificial intelligence in the standards process. That is a useful institutional act: it makes participation and the public archive…

ICANN
ICANN’s Authority Is Contractual Before It Is Public
ICANN can influence the global identifier system without being a government and without possessing unilateral control over every technical action that follows its decisions. Its authority is assembled from several instruments: corporate bylaws, operational agreements, registry…

IETF
The Diff Was Classified. The Upgrade Was Not Proven
Revision 09 of the YANG schema-comparison draft can produce a disciplined account of what changed between two schema revisions. Its editorial, backwards-compatible and non-backwards-compatible labels are valuable precisely because they are narrow: they describe the comparison…

Story
ARIN’s 2026 Candidate Forum Page Still Carries the 2025 Voting Window
ARIN opened registration for an October forum on its 2026 Board candidates. The event page gets the year, forum date and subject right, then tells readers that voting runs from 30 October through 7 November—the window ARIN published for 2025, not the 22–30 October window on its…

IETF
A YANG Service Model Can Match While Its Lifecycle Semantics Diverge
At 18:00, a time-bounded network service reaches the end written in its order. The BSS marks it complete. The orchestrator begins decommissioning. One controller still calls the connection active, another has already removed a segment, and the assurance system reports a healthy…

Story
RIPE NCC's Admin WebUI Fills Automation Gaps. Retirement Needs an Exception Ledger
The revealing phrase in RIPE NCC’s current registry plan is not “technical debt” but “admin-like capabilities”: the old interface carries operational exceptions that a cleaner replacement could otherwise erase from view.

History
The UDP Table Knew the Port, Not the Conversation: RFC 2013
RFC 2013 gave a network manager two kinds of sight: four odometers for an entire UDP engine and a list of local doors where applications were listening. It could say that a door existed and that traffic totals moved. It could not say who stood outside, which process answered, or…

History
A CHAP Success Proved One Comparison, Not the Connection: RFC 1994
The decisive packet in CHAP was called Success. Its name sounded broader than its evidence: one authenticator had compared one response with one locally calculated value for one challenge. RFC 1994 made that comparison useful by binding it to time and direction—and left every…

IETF
Tim Bruijnzeels and the RPKI Overclaim That No Longer Invalidated the Whole Subtree
A certificate can be wrong in one place without being worthless everywhere. That proposition sounds modest, yet it changed the failure geometry of the Resource Public Key Infrastructure. In RFC 8360, Tim Bruijnzeels and five co-authors replaced one all-or-nothing consequence with…

CASE FILE
When a BIND Fix Is Not Yet a Repair
A resolver vulnerability becomes an institutional accountability test when the patch is available but the evidence of recovery is not. ISC’s public record establishes how two BIND failures can turn hostile DNS input into an availability risk—and identifies a remediation…

IETF
The Hidden Service Answered. The Onion Key Had Not Yet Spoken: RFC 9799
The hidden service answered over Tor, the ACME account was valid, and the final CSR was ready. None of those facts yet proved that the applicant controlled the `.onion` identity. RFC 9799 makes that missing proof explicit—and shows why issuance authority, descriptor visibility…

ICANN
ICANN Kept Its Strategy Unchanged Without Showing the Trigger Test
ICANN’s latest annual strategy review ended with a clear Board decision and an incomplete public chain of reasoning. After eight environmental-scan sessions involving nearly 210 entities, the Board affirmed on 6 September that its FY26–30 Strategic Plan would remain unchanged.…

IETF
IETF–W3C: A Relationship Record, Not a Single Institution
The label “IETF–W3C” compresses two standards institutions into one directory entry. The public record supports a narrower description: the organizations have documented channels of cooperation, but the evidence reviewed does not establish one legal entity, one administrative…

IETF
A Company-Certs Endpoint Cannot Prove Who Approved a Trust-Anchor Rollover
At 10:00, an application retrieves two valid private-CA chains from its company’s well-known HTTPS endpoint. The older chain still works; the newer chain has the later `valid_from`, so the client selects it exactly as the draft describes. TLS validation passed, the JSON parsed…

Story
LACNIC Listed 32 Resources for December Revocation. That Is Not 32 Cases.
A new LACNIC cohort places 32 number-resource records on one 90-day clock. The table is useful precisely because it is public. Its limit is just as important: a row identifies a resource, not the recovery case behind it.

IETF
The Cursor Knew the Position. It Did Not Know the Moment
YANG list pagination can preserve the exact filter, sort field, locale, direction and continuation token used to reach the next page. That makes the traversal auditable. It does not make nine requests one observation, or an ordered page a frozen dataset.

Story
APNIC Closed Its CentOS Workstream. The Evidence Chain Still Has Four Open Joins
APNIC can point to a genuine finish line: in the second quarter of 2026 it completed a multi-year move away from end-of-life CentOS hosts. Its wider security record is less linear. Tests, findings, classifications and exercises appear in separate reports, but the public evidence…

History
One Packet Became Several Frames, and Several Packets Became One: RFC 1993
RFC 1993 recorded a compression design in which the most intuitive boundary on a serial link—the frame edge—stopped being the boundary that mattered. Its Gandalf FZA stream could gather several original PPP packets into one compressed frame or carry a single original packet…

History
The State Table Was Also a Kill Switch: RFC 2012
In RFC 2012, a manager could inspect a TCP connection in one moment and erase its host-side existence in the next. The same row that reported state also accepted `deleteTCB(12)`, turning a table of observations into a remote intervention surface whose consequences extended well…

IETF
Michael Tüxen and the Zero SCTP Checksum That Still Needed Error Detection
Zero usually looks like absence. In RFC 9653, a zero in SCTP's checksum field means something narrower: one endpoint may omit the correct CRC32c only after its peer has named an acceptable alternative error-detection method for that association. Michael Tüxen's work on the…
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