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
7,567 articles
IETF
The Port Was Saved. The Session Identity Was Spent: RFC 5382
A translator can make an excellent capacity graph by lending the same public address and port to more than one internal endpoint. The graph turns red only when two of those endpoints call the same server. Then the hidden distinction disappears, and an apparent efficiency becomes…
History
An Empty Field Was Not One Thing. RFC 3982 Made Absence Part of the Protocol
When a registry export turns every unavailable value into an empty cell, it destroys the most consequential fact about that cell: whether the datum never existed, could never be published, was withheld from this requester, or had been disclosed under conditions the export…
History
An OSI Address Had to Carry More Than a Route: RFC 1277
In 1991, OSI applications were already being tried over TCP/IP and X.25 networks that did not offer the OSI Network Service. RFC 1277 put the missing lower-layer clues inside an address the directory could already return. That made a connection attempt possible without making the…
CASE FILE
The ILC Has Put Erga Omnes on Its Agenda. The Doctrine Is Still Open.
The International Law Commission has opened a formal workstream on obligations owed to the international community as a whole. Its agenda decision starts expert work; it does not settle the law. The difference is a governance question in its own right.
IETF
The Empty Registry Row Was Not Permission to Use It
An engineer opens the DNS parameter table and finds a number marked unassigned. The field accepts it. A laboratory server answers it. A packet trace shows the value crossing the network. None of those facts says the Internet has granted that number a stable public meaning. RFC…
History
The Channel Was Ready. Identity Was Still a Separate Question: RFC 3983
RFC 3983 gave IRIS a precise moment when a negotiated BEEP channel became “ready.” That word described message capability, not a completed trust decision. Server identity, user authentication, encryption, query authorization and the registry result still had separate owners and…
CASE FILE
Three Parties, Ninety-Five Signatures: The Cybercrime Convention Runs on Two Clocks
The UN Treaty Collection lists 95 signatories and three parties to the new Convention against Cybercrime. Those figures describe different legal states. The treaty’s entry-into-force clock waits for deposited instruments, while a separate UN process is already preparing the rules…
Story
APNIC’s Helpdesk Averaged 7.47 Business Hours. The Average Has a Boundary.
APNIC’s first-quarter report puts two useful service results above their targets: a 7.47-business-hour average Helpdesk response time and 95.5% favorable ratings. The next question is not whether those numbers are good. It is what, exactly, they describe.
History
A Packet's Endpoints Could Not Name the Network in Between: RFC 1272
In 1991, an Internet provider could see a packet’s source and destination without learning which neighboring administration had carried it across a boundary. RFC 1272 made that gap the central problem for network accounting: to reconcile use between providers, the meter had to…
IETF
Both Sides Compiled. They Still Did Not Speak the Standard: RFC 5381
Automation can make two systems agree with each other while separating them from everyone else. RFC 5381 described a NETCONF client and server generated from the same Web Services description. The code worked as a pair. Its cookie-based session binding nevertheless did not…
History
The Universal Client Was a Lure. RFC 3981 Kept the Core Incomplete on Purpose
The IRIS core specification made an unusual virtue of being limited public evidence. It could identify registry types, carry lookups and follow references, but it refused to pretend that one query language or one data model could understand every Internet registry. RFC 3981…
ICANN
ICANN Board self-review keeps Delegation of Authority with BGC
The Governance Committee compared Board self-evaluation issues with the Board Efficiency Work Team’s remit. One subject—Delegation of Authority—stays with the committee, while the broader review remains unfinished.
History
SNMP Had to Cross Routers to Manage Them: RFC 1270's UDP/IP Choice
In October 1991, the argument for putting network management on the Internet's network layer was not just a matter of saving protocol code. The people watching a network often needed their messages to cross the same routers, media changes and localized faults as the equipment…
CASE FILE
Five ITU Management Posts Get Written Questions. Other Races Use Different Records.
PP-26’s candidate page brings executive candidates, Radio Regulations Board candidates and Council Member State candidatures into one navigable space. But the records are not interchangeable: optional campaign material sits beside required dossiers, and the later standardized…
IETF
The Address Never Moved. Everything Beneath It Did: RFC 5380
A stable endpoint can be the most misleading entity on an operations screen. RFC 5380 kept a Regional Care-of Address visible while local movement changed the address, binding and tunnel that made it reachable. The design reduced signaling. It also made continuity depend on state…
History
The Name Crossed Three Storage Transports. It Still Did Not Name an Address: RFC 3980
A storage array could expose Fibre Channel, SAS and iSCSI ports without becoming three different devices. RFC 3980 let one NAA identifier cross those transport boundaries as the basis of an iSCSI name. The gain was continuity of identity, not a shortcut to an IP address, a live…
IETF
The Branch Limit Slowed the Flood. It Did Not Reduce the Work.
A SIP proxy receives a request, sees eight possible destinations and has permission to run four branches. It opens four. One fails, so the released slot opens a fifth. Then a sixth, seventh and eighth follow. At no instant did the proxy exceed its concurrency limit. Across the…
Story
Botswana’s IPv6 Plan Sets a 2026 Target. What Counts Toward 100%?
BOCRA’s roadmap assigns IPv6 targets through 2026, while Botswana’s accelerator records engineers trained and projects chartered. The missing public question is not whether work began; it is how a reader can distinguish readiness from measured deployment without exposing…
ICANN
The Notification System Is Done. The IGO Acronym Moratorium Is Not.
ICANN’s latest advice register records a permanent notification system for intergovernmental organizations as complete. The same register still places the curative-rights work that stands between interim protection and release in implementation. One completed safeguard is not a…
IETF
A Privacy Token Was Not a Global Rewrite Warrant: RFC 5379
The most dangerous privacy control is sometimes the one that works too broadly. A SIP intermediary can see a field that appears to reveal identity, erase it in the name of protection, and still leave the caller worse off because the call transfer, route, signature, or return…
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