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,083 articles
History
The Box Dropped No Frames. It Had Not Passed the Other Tests: RFC 1242
A clean throughput trial is seductive because it ends in one number. RFC 1242 gave that number a strict meaning, then surrounded it with other terms that refused to disappear. Zero loss at one offered rate did not answer latency, burst tolerance, overload, restart, filtering or…
History
The Counter Was Total. Subscription Discards Were Somewhere Else: RFC 1304
A number labelled total looks like the end of an investigation. In RFC 1304, it was the beginning of one. The 1992 MIB could count SIP packets discarded for protocol or bit errors, list other address-related failures and remember the latest disagreement of each syntactic type.…
CASE FILE
The CA Was Trusted. Its Other Certificates Entered the Control Plane: RFC 9918
A NETCONF server can trust the right certification authority for the wrong breadth of purpose. RFC 9918 warns that if the listed CA also issues certificates for unrelated uses, those certificates can be accepted into the management channel. The TLS chain may validate perfectly…
IETF
Jari Arkko and the Registry Field That the Protocol Did Not Need
A protocol registry is often read as a durable record, which makes every old column look like a permanent requirement. RFC 8602 takes the opposite discipline: an inherited postal-address field in two TRIP registration procedures had no identified use, so IANA stopped collecting…
History
The Tunnel Carried the Packet. The Error Lost the Question: RFC 1241
A tunnel can look transparent in the forward direction and become opaque the moment something fails. RFC 1241 drew that asymmetry with unusual precision. Its outer packet could carry an untouched IP datagram through a separate routing space. But an ICMP error from inside that…
CASE FILE
The Error Was Seen in Reverse. The Forward Link Was Removed: RFC 9917
A router at the far end records receive-side errors. Policy turns that observation into a colour on the reverse directed edge. Another router can then remove the forward edge from a Flex-Algorithm topology. RFC 9917 makes this chain computable; it does not make the colour a…
NPNOG
Broken Dates, Empty Lists and Missing Slides: Can npNOG Preserve Its Own Memory?
npNOG’s public websites preserve a useful record of programmes, teaching materials and event continuity, but they also contain date conflicts, unfinished download promises and pages whose headings outlive their visible data. Those gaps do not prove that an event failed, a…
ICANN
ICANN’s Specific Reviews Are Paused. The Pause Needs a State Record
ICANN has not erased its Specific Reviews. It has put a temporary rule beside the old duty, with a known effective date, a first expiry, two possible routes to a further pause, a maximum outer limit and a prescribed route back into the reviews. That is a more disciplined response…
CASE FILE
APA Wants One W3C Charter-Review Queue, Not Two. The Review Duty Remains.
W3C’s accessibility reviewers have asked to stop receiving duplicate charter-review tickets because they already work from the central Strategy queue. Privacy reviewers, meanwhile, say their local copies are useful. The disagreement is not about whether horizontal review matters.…
IETF
Lars Eggert and the UDP Datagram That Did Not Escape Shared Costs
UDP gives an application a small transport contract. It does not give it a private network. Lars Eggert's work on RFC 8085 makes that distinction operational: the freedom to choose datagrams leaves congestion responsibility with the traffic that actually shares a path.
History
The MIB Arc Changed. Vendors Still Had to Revise: RFC 1239
Nothing in a management console announces that a number has become architecture. RFC 1239 did. Five MIBs kept describing familiar interfaces, yet their entity identifiers moved from an experimental branch to standard branches. The standards record changed in two pages; every…
CASE FILE
The Reply Omitted the Option. Retirement Was Still Unproven: RFC 9915
The NTP option was gone from the new DHCPv6 Reply, yet the client kept sending packets to the old time server. That is not a contradiction in the standard. It is a warning that a server-side withdrawal, a client-side state change and an observed service outcome are three…
CASE FILE
The Latest TLS Version Won. The First PCEP Message Still Had to Wait: RFC 9916
RFC 9916 makes a narrow security judgment with large operational consequences: PCEPS should negotiate the newest TLS version it can, but it must not let PCEP application data travel before the handshake is complete.
IETF
VELOCE’s Call Chose an IANA Pointer. The WG Draft Still Says No IANA Actions
On 25 August, an attributed VELOCE project-call summary said that an IANA indirection model had been confirmed: a registry would point to the repository rather than place the module itself inside an RFC. The Working Group revision issued the same day ends with a contrary-looking…
IETF
Heather Flanagan and the RFC Archive That Cannot Freeze
An RFC can look unchanged to a reader while its publication machinery has changed underneath it. It can also acquire a cleaner HTML rendering, repaired XML or a regenerated PDF without acquiring a new protocol meaning. The two statements are easy to say and hard to govern.…
History
The Master Said Accepted. The Applications Had Not Reported an Outcome: RFC 1301
Twelve small verdicts travelled inside every Multicast Transport Protocol packet. One could say accepted, another pending, a third rejected. They looked like receipts, but they were not votes from twelve receivers. RFC 1301 gave one master the right to set those values after…
CASE FILE
The Track Was Acknowledged. No Packet Had Used It Yet: RFC 9914
RFC 9914 gives constrained networks a disciplined way to project a routed Track through an RPL topology. Its acknowledgments establish specific control-plane facts. They do not certify that traffic has traversed the Track, met a deadline or reached an application.
CASE FILE
W3C’s Data-Governance Workshop Can Reroute a Proposal. That Is an Agenda Decision.
W3C’s call for a TPAC 2026 mini-workshop on Data Governance & Ownership asks a useful question: what is broken, and what should Web standards do next? It also reserves a quieter power. Because the subject overlaps AI and Society and Age Assurance, organisers may ask a contributor…
CASE FILE
The Link Named the Parent. It Had Not Frozen the Hierarchy: RFC 9910
RFC 9910 gives RDAP clients typed paths through number-resource hierarchies. Those paths are useful navigation, but they are not sealed records of what the registry would have returned at an earlier time.
History
The Agent Spoke with One Voice. The Subtree Had Another Owner: RFC 1227
To a management station, an SNMP agent looked like one speaker. RFC 1227 placed a switchboard behind that voice: local processes registered branches of the MIB, priorities chose which process answered, and a broader branch could hide a narrower one. The reply was real, but its…
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