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
8,075 articles
IETF
FANN Has Adopted a Problem Statement. It Has Not Coordinated a Network Action.
FANN’s chairs have closed an adoption call by saying that the Fast Network Notifications Problem Statement will become a working-group document. That is a meaningful process event: it gives a defined group a text to improve and asks its authors to carry adoption-call feedback…
Story
LACNIC’s fee schedule and the price of a durable registry
*By Nia Okafor*
NPNOG
Two Hours Online: What npNOG’s Pandemic Experiment Changed About Access
npNOG kept a public technical programme alive on 9 December 2020 by moving it online. The official record supports a narrower achievement than the language of digital inclusion often implies: no one had to travel to a named physical event venue to join, and npNOG says more than…
IETF
Lucas Pardue and the Priority Signal That Could Not Schedule the Page
A web request can carry a highly specific expression of urgency and still leave the page’s fate open. RFC 9218, co-authored by Lucas Pardue, gives HTTP/2 and HTTP/3 a common way to express response-priority preferences. It does not turn that preference into a command over the…
History
The Relay Changed the Message. It Had to Call Itself a Gateway: RFC 1344
A carrier can claim neutrality while the entity in its custody remains untouched. The claim becomes harder after it changes an image, replaces a reference with a copy or divides one message into several. RFC 1344 gave that moment a name in 1992: the intermediary was no longer…
CASE FILE
The Response Named a Group. The Cache Fleet Received No Common Order: RFC 9875
An origin can label related HTTP responses and ask a receiving cache to invalidate the group after a state-changing request. RFC 9875 makes that local relationship legible; it does not turn one header into a synchronized purge across a hierarchy, a mesh or the user's screen.
History
The Test Bed Could Demonstrate a Future. It Could Not Decide the Public Network: RFC 1259
RFC 1259 imagined the NREN as a new subdivision built before the surrounding city. Its mistakes could teach later builders, but its streets, prices and residents could not decide the whole metropolis. The crucial Internet-history lesson was not prediction. It was the design of a…
IETF
MLS Can Reopen a Call for Adoption After an IPR Disclosure. It Cannot Turn Disclosure into a Verdict.
An IPR notice is a change to the information set, not an oracle. The MLS chairs have extended a Call for Adoption for the two-party MLS profile after a third-party disclosure arrived. That extension is useful precisely because it gives entities a new opportunity to state a…
IETF
Eric Rescorla and the Encrypted Hello That Could Not Name the Server
An encrypted ClientHello can make a familiar public clue disappear from the first TLS flight. That does not turn the remaining handshake into an identity ledger. RFC 9849, co-authored by Eric Rescorla, specifies a carefully bounded privacy envelope: it can hide the private…
CASE FILE
W3C’s New Agent Benchmark Group Needs More Than the Same Score Twice
The new Agent Conformance and Benchmarking Community Group gives itself a crisp test: two independent parties should be able to reproduce a published score to the same value. That would be useful evidence that a procedure can be rerun. It would not yet answer whether the…
IETF
DNSOP Can Signal a Zone Cut to Nowhere. It Cannot Publish a Private Namespace.
DNSOP is considering a modest DNS mechanism for a difficult operational fact: a child zone can exist for one network while being deliberately unavailable through the public namespace. The proposed parent-side signal could help a resolver avoid confusing that fact with public…
IETF
Wesley George and the Old ASN Key That Could Not Announce a Merger
Wesley George and the Old ASN Key That Could Not Announce a Merger intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may follow. The…
CASE FILE
The Package Held Both Forms. They Were Not Yet One Key: RFC 9935
An ML-KEM key package can carry a compact seed and a full decapsulation key together. That convenience creates an import decision: until the recipient regenerates one from the other and compares them, a well-formed package has shown two values, not one coherent key.
History
The Network Did Not Have to Keep the Beat. The Receiver Rebuilt It: RFC 1257
In 1991, a voice sample could arrive early, the next one late, and the listener could still hear a regular cadence—if the receiver knew the deadline, kept enough memory and woke at the right time. RFC 1257 used that construction to move a costly promise out of every subnetwork…
IETF
HTTPbis Can Consider Signature Keys. The Call Does Not Choose an Application Trust Model
HTTPbis is asking whether it should adopt work on a draft for distributing verification keys with HTTP Message Signatures. That is a real and consequential technical question. It does not decide which party a bank, marketplace, device fleet, agent platform or internal service…
History
The Packet Got a New Lifetime at Every Border: RFC 1326
A tunnel is often described as a clean bargain: put one protocol inside another, cross a network that understands the outer wrapper, then recover the original packet at the exit. RFC 1326 asked what happens when two such bargains face each other and routing sends the packet back…
CASE FILE
The Hash Was Fast. Collision Recovery Was the Real Control: RFC 9923
FNV can put an item into a table quickly and consistently. It cannot promise that hostile inputs will remain evenly dispersed. RFC 9923 turns that narrow limitation into an operational question: can the operator see concentration early, change the hashing epoch and rebuild the…
IETF
Martin Duke and the QUIC Version That Could Not Declare Its Deployment
QUIC version 2 has an official RFC, an IANA entry and a memorable wire value. None of those things puts it on an endpoint. Martin Duke’s RFC 9369 makes the distinction unusually visible: “version 2” is merely the published document’s informal name, while the protocol uses a…
CASE FILE
The Diagram Had a Bit. The Registry Did Not: RFC 9927’s C-Flag Repair
RFC 8928 drew a C-flag into a compact wire field without registering its position. A later standard properly allocated that same position to another field. RFC 9927 repairs the collision before known deployment made compatibility expensive—but publication cannot update a parser…
History
The Analysis Could Not Stand In for the Test Network: RFC 1245 and RFC 1246
In July 1991, OSPF arrived with more than a protocol specification. Its supporting case was deliberately divided into an analysis and an experience report. That division preserved a distinction Internet engineering still needs: a model can bound expected behaviour, but only…
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