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,558 articles
IETF
AAA Knew the Subscriber. The Home Agent Still Needed a Key: RFC 5419
RFC 5419 explains why some Mobile IPv6 operators wanted subscriber authentication to ride on an existing AAA relationship. Its more revealing question is what happens after that decision: the home AAA server may recognize the subscriber, yet the selected Home Agent still needs a…
History
Routine Did Not Mean Unreviewed: RFC 6709’s Test for Protocol Extensions
In protocol design, “routine” can sound like a verdict that a change is too small to matter. RFC 6709 used it more narrowly. An extension was routine only when the base protocol and deployed implementations could treat it as opaque without harm. That says something about…
Story
RPKI’s Sub-One-Per-Cent BGP Result Is Useful. It Is Not a Stability Verdict.
A peer-reviewed study finds that RPKI-associated updates remain a small share of observed BGP UPDATE volume. That matters, but message volume is only one meaning of network stability.
IETF
A CAPWAP Credential Did Not Enroll a Device in the Network: RFC 5418
RFC 5418’s 802.11 threat model separates WTP–AC authentication from deployment membership, device role and the path client traffic takes. A valid session settles only part of the operating question.
ICANN
Five `.agent` Applicants Recur Across ICANN’s Contention Sets
ICANN’s first 2026-round CSV places 13 named applicants in the `.agent` group. Five of those applicant entities appear in at least 11 of the file’s numbered contention sets, giving the crowded name a portfolio dimension that a single application count misses.
History
One Internet, Many Operators: RFC 1462’s Telephone Analogy
The 1993 FYI used a familiar phone call to explain an unfamiliar topology: users experienced one Internet service, while separate networks operated and repaired their own sections.
History
NAT Was a Function, Not an Interface: Why RFC 4008’s MIB Had to Change
In 2005, a management station configuring NAT through RFC 4008 had to begin with an interface index. Ten years later, the successor MIB described NAT as a logical function that could span interfaces, address realms, subscribers, and multiple instances. The change was a correction…
History
The Frame Crossed the Pseudowire. Its Service Role Did Not: RFC 7152
In 2014, an IETF requirements memo exposed a small but consequential gap in Layer 2 VPNs: a provider-edge router could receive an Ethernet frame across a pseudowire without knowing whether the frame had entered the remote network through a root or a leaf attachment. RFC 7152…
IETF
Before CAPWAP Discovery, DHCP Ordered the Controllers a WTP Could Try: RFC 5417
A DHCPv4 or DHCPv6 option can place one access controller ahead of another in a wireless termination point’s bootstrap search. RFC 5417 makes that sequence a configured preference; discovery and DTLS still determine which peer can become the control endpoint.
History
No AFI Meant “Any”: RFC 4012’s Four-Family RPSL Extension
RPSLng added an optional address-family clause to multiprotocol policy. Leaving it out was not silence: RFC 4012 gave the expression the scope “any,” while the older policy attributes kept their IPv4-unicast meaning.
CASE FILE
The Root DNS Saw Twice the Traffic. A Resolver Update Was the Clue.
For about a week, queries reaching the DNS root rose from roughly 1.6 million to 3.2 million per second. The traffic was valid, came from recursive-resolver networks, and did not measurably impair root service. The episode shows how a software change far upstream can become a…
IETF
RFC 5416: The 802.11 Binding Has an Era Boundary
RFC 5416 is easy to misread as a promise about every feature a modern Wi-Fi deployment may advertise. It is more precise than that: the CAPWAP binding fixes how an access point and controller exchange IEEE 802.11 information for the 802.11-2007 era. The leadership question is…
IETF
An IETF Appeal Can Be Denied or Unprocessed. The Docket Must Say Which.
The IETF’s active appeal rules distinguish a submission that never reaches review from a claim rejected after review. They also send those records to different public places. That difference changes what a reader can infer from the docket—and what a trustworthy account of the…
IETF
CAPWAP State Is Not Service Proof: RFC 5415
RFC 5415 gives wireless operators a structured CAPWAP control plane: an Access Controller manages Wireless Termination Points, establishes protected sessions, changes configuration and carries client data through defined modes. The useful leadership boundary is inside that…
IETF
WiCoP Is a Historic Control Record, Not a Deployment Baseline: RFC 5414
RFC 5414 describes WiCoP, a Wireless LAN Control Protocol for centrally managing and provisioning large WLANs. The RFC Editor marks it Historic and identifies RFC 5415 as the replacement. That status changes the question for a leadership team: a controller diagram or provisioning…
Story
AS24940’s RPKI Snapshot: 91 Routes, 63 Matches, 49 Broader Permissions
AS24940’s RPKI Snapshot: 91 Routes, 63 Matches, 49 Broader Permissions 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.…
IETF
SLAPP Security Is a Historical Boundary, Not Deployment Proof
RFC 5413 records the Secure Light Access Point Protocol as submitted during the CAPWAP work. Its discovery, authentication and secure transport ideas are useful historical evidence, but the RFC Editor says the document was published solely for the historical record, was not…
IETF
LWAPP Is a Historic Record, Not a Deployment Baseline
RFC 5412 documents the Lightweight Access Point Protocol as it was submitted during the CAPWAP work. It is valuable archival evidence about an access controller and wireless termination point model, but the RFC Editor explicitly labels it Historic and says it should not be used…
CASE FILE
PP-26’s Podium Has a Queue. Its Formal Record Needs a Second Track
Before the conference opens, ITU has defined a scarce public-speaking channel: one high-ranking delegate per Member State, a first-come queue tempered by official rank and physical presence, and two or three minutes at the microphone. The resulting speeches can shape strategic…
IETF
CATS Chose the Service Contact. The Backend Stayed Hidden: RFC 10053
CATS can steer a request toward a promising service contact using network and compute conditions. That choice still may not reveal which service instance handles the request behind the contact, or whether the reported metrics describe that instance alone.
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