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
4,350 articles
History
The Code Was Available. The Original Specification Was Not: RFC 1492
The original TACACS specification existed, and the author of RFC 1492 could not obtain it because of copyright issues. What reached the public record in July 1993 was therefore an Informational reconstruction, constrained by running code and candid about the possibility that the…
Story
ARIN's SMS Country List Is Now an Attack-Cost Boundary
A request to make SMS authentication more convenient ended with a security-cost decision. ARIN says the limited numbers it supported outside its service region created a costly attack vector; the public record explains the boundary it chose, but not the attack it measured.
CASE FILE
The Switch Executed the Program. It Did Not Inherit the Right to Read, Rewrite or Decide: RFC 9817
A program that runs inside a switch or network interface card is no longer merely near the traffic. It can become part of the path by which traffic is classified, transformed, delayed, replicated or converted into a control action. RFC 9817 catalogs the opportunity and, more…
CASE FILE
All Three Attestations Were True. They Still Did Not Belong to the CSR Key
A certification request can arrive with one valid statement about an HSM, another about corporate ownership and a third about platform health. The dangerous moment comes when a certificate authority treats three successful checks as one joined fact. Revision 29 of an IETF draft…
CASE FILE
One Timer Drove Three IPv6 Decisions. The Counters Could Not Explain Which One
A network team changes one millisecond value on an IPv6 interface. Address resolution, reachability probing and duplicate-address detection all inherit it. The edit receipt is precise; the operational meaning is not, until the team joins the change to an interface, an epoch and…
History
The Damaged Text Became Readable Latin. It Did Not Become the Russian Original: RFC 1489
When the eighth bit disappeared from a KOI8-R message, Russian letters could fall into a strange, case-reversed Latin shadow. A reader might still guess the words. That humane failure mode did not restore the erased bits, certify the charset or turn recognition into proof of the…
CASE FILE
The Route Reflector Distributed the Link. It Never Witnessed It: RFC 9815's Sparse-Peering Evidence Boundary
A route reflector can hold the newest authenticated account of a data-centre link and still know nothing directly about whether that link carries a packet. RFC 9815 makes this separation operationally useful: BGP can distribute a link-state graph over far fewer sessions than the…
CASE FILE
The Packet Had No SRH. It Could Still Target an SRv6 SID
An edge filter inspects an IPv6 packet, finds no Segment Routing Header and lets it pass. The packet still carries a locally instantiated SRv6 SID as its destination. The visible header test succeeded; the admission decision examined the wrong fact.
History
The MX Record Found a Gateway. It Did Not Prove the Fax Machine Existed: RFC 1486
A wildcard in the Domain Name System could announce that a mail gateway was willing to serve thousands of telephone numbers. It could not say whether any one of those numbers existed, answered, belonged to a fax machine or put a page into the intended person's hands. RFC 1486…
CASE FILE
The HSM Signed a Small Attribute Set. The Large CMS Content Was Bound Through One Digest: RFC 9814
An operator can truthfully say that a hardware security module produced an SLH-DSA signature while still leaving the most important question unanswered: which bytes did the module actually sign? RFC 9814 makes that question decisive for CMS. A multi-gigabyte archive may never…
History
The String Carried the Distinguished Name. It Did Not Become the Directory Entry: RFC 1485
The String Carried the Distinguished Name. It Did Not Become the Directory Entry: RFC 1485 intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…
CASE FILE
The IP Address Stopped Naming the RADIUS Client. The Cleartext PSK Identity Took Over: RFC 9813
Two network access servers can stand behind one public address, while one mobile appliance can appear from several addresses in a week. RFC 9813 lets RADIUS/TLS distinguish those relationships with a PSK Identity. The useful part is not the new name. It is the sequence of checks…
History
The String Could Be Parsed Without Ambiguity. It Still Was Not the Directory Entry: RFC 1485
The String Could Be Parsed Without Ambiguity. It Still Was Not the Directory Entry: RFC 1485 intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…
CASE FILE
The Indicator Was Defanged. Its Next Consumer Could Still Arm It
A security analyst pastes a bracketed address into a ticket. It looks inert, and in that surface it may be. Minutes later, a preview worker extracts the same string, restores its URI form and fetches it for inspection. The analyst never clicked. The ticketing chain still crossed…
CASE FILE
The HTTP Request Returned 200. The Certificate Decision Was Still Inside: RFC 9811
A green transport result is tempting because it is immediate, familiar and easy to graph. RFC 9811 makes that result useful without letting it impersonate the certificate-management decision carried inside it. The distinction is small enough to fit in one response and important…
History
The Name Was Easy to Type. Its Identity Still Depended on the Directory Around It: RFC 1484
A person could say a short, natural name and let the directory fill in types, hierarchy and spelling. The convenience was real because the omitted context still existed: inside the local environment, current entries, matching rules and the user’s final choice.
History
The PDU Arrived. Its Protocol May Still Have Been Agreed Elsewhere: RFC 1483
RFC 1483 offered two ways to tell an ATM receiver what it had received. One put a protocol label in every AAL5 PDU. The other removed that label and made the virtual circuit carry its meaning. The bytes grew leaner, but the missing fact did not vanish; it moved into provisioning…
CASE FILE
The Device Can Last for Years. Its Trust Anchor Cannot Be Treated as a Lifetime Constant
A field sensor can remain bolted to a bridge long after its manufacturer changes owners, its issuing CA rolls over and its original algorithm becomes uncomfortable. The device still has power. The network still reaches it. Yet whether it can trust the next service chain depends…
CASE FILE
The Space Was Reserved. One Executive Approval Was Still Too Weak: RFC 9812
Nearly seven-eighths of IPv6 address space was being held for a future that had not arrived. The registry called it reserved, but the rule for releasing a major piece could still be satisfied by an executive approval with no RFC. RFC 9812 repaired that mismatch without pretending…
History
The IAB Endorsed CIDR. Four Different Actors Still Had to Make It Real: RFC 1481
In July 1993, the Internet Architecture Board used a sentence that sounds like a finish line: it “endorses the CIDR architecture and its implementation.” The sentence mattered. It still did not allocate an address block, add classless code to a router, install that code in a…
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