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,552 articles
Story
LACNIC 46 Registrations More Than Doubled. That Is Not Attendance
The public count moved from 348 to 763–766 in about four weeks. It is a sign of registration momentum before the Mendoza meeting, not a record of who will attend or take part in its policy forum.
CASE FILE
Philippines’ cable outage: three clocks behind one “restored” notice
On 2 October, public probes saw a sharp rise in latency between the Philippines and Singapore, but could not identify a cable. InfiniVAN later reported its C2C segment restored; carriers then described their own rerouting and service recovery. These are connected events, not…
History
The Plug Had Four Pins: NORDUnet and Europe’s Protocol Choice
In May 1988, a Nordic research network asked the United States for a route into NSFNET while promising to carry several rival network services at home. Its four-pin plug became a practical answer to a harder question: could researchers share a backbone before they agreed on one…
Story
The Legacy Host Went Quiet. Its IPv4 Lease Did Not.
A /32 DHCPv4 mask can quiet an old client that cannot use IPv6-Only Preferred. The address it receives, the inbound packets it can still accept and the pool that supplies its lease remain operational questions.
History
A Language Tag Was One Token, Not a Navigation Map: RFC 1766
RFC 1766 split a language tag into a primary value and hyphenated subtags, then told applications to treat the complete string as one token. Its consequential boundary was administrative: the parts helped organize a shared namespace, but did not become a universal route through…
IETF
Syslog Could Report Clock Quality. Operators Still Had to Set Its Bounds: RFC 5424
A timestamp can travel farther than the conditions that made it credible. RFC 5424 gave a syslog originator a compact way to describe those conditions, but the description was only as sound as the clock configuration and monitoring behind it.
NANOG
Five Candidates, Two Seats: NANOG’s Ballot Outlasts Its Meeting
NANOG’s 2026 Board contest puts five candidates before members for two staggered seats. Candidate presentations are scheduled during NANOG 98 in Miami, but voting opens on the same date and stays open after the meeting ends: the published window runs from 20 through 26 October…
History
WAIS Let a Document Become Its Own Query: RFC 1625’s Relevance Loop
A reader could type a few seed words, add a document or even one passage, and ask WAIS to find similar material. What came back was a ranked citation, not a durable result set or the document itself. RFC 1625’s small but consequential design was to make a selected text entity…
IETF
Inside EAP-FAST, Type 6 Meant Something Else: RFC 5421
RFC 5421 placed a familiar EAP method code inside a new frame: Type 6 still looked like Generic Token Card, but inside an EAP-FAST tunnel it selected a differently formatted inner exchange. The specification drew a strict boundary between those meanings; its IESG note warned that…
History
Who Chose the Branch? TAT-8's Capacity Bargain in Internet History
TAT-8 was planned for digital voice, computer and video traffic, not for an Internet protocol. Its branch to Britain and France, supplier contracts and capacity rules show how later data networks inherited physical decisions made for a broader telecommunications system.
Story
Jamaica’s Internet Exchange Turns on the Terms of Participation
A 2026 relaunch brings JAIXP back into view, but its durable value will depend on why independent operators choose to connect, exchange traffic and remain.
IETF
Provisioning Success Still Needed an Access Decision: RFC 5422
RFC 5422 separates completed credential provisioning from permission to use network resources; its server-unauthenticated mode is explicitly provisioning-only.
History
Publishing the Flaw Was Not Publishing the Worm: RFC 1135’s Disclosure Debate
The 1988 Internet worm left a question that was easy to flatten into “publish or conceal.” Contemporary records show a narrower choice: explain the defects and the program’s methods, distribute fixes, or release a working decompilation that lowered the effort needed to make…
History
Who Chose the Address? RFC 4014 Carried RADIUS Authorization into DHCP
A successful access decision does not hand a device an address. In 2005, RFC 4014 gave a network access server a narrow way to carry selected RADIUS authorization attributes into a later DHCP exchange, joining two decisions without pretending they were one.
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.
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