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,657 articles
History
One Router Drew the Path. No Router Needed the Whole Map: RFC 1992
Nimrod’s sharpest scaling decision was to abandon the comforting fiction of a single, complete map: knowledge could be partial, private and stale, provided that a chosen path did not depend on every router improvising from a different picture.
IETF
The Transform Was Agreed. The Replay Was Not Yet Rejected: RFC 9827
RFC 9827 gives IKEv2 a broader and more honest contract for packet sequence numbers. The selected Transform ID describes what should be true when an SA's packets enter the network; it does not certify sender coordination, receiver anti-replay policy, the packet stream that…
Story
LACNIC’s ASPA Explainer Cites a Moving Percentage Without a Snapshot
LACNIC’s ASPA Explainer Cites a Moving Percentage Without a Snapshot 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
RFC 10011 Brings the TLS Terminator Inside the Security Boundary
RFC 10011 allows a RESTCONF service to sit behind an external TLS terminator. That is not a relaxation of the security model. It is a relocation of the place where encrypted transport and authenticated identity become an administrative claim—and a warning that the terminator, the…
History
The Byte That Sent PPP Back to the Beginning: RFC 1973
RFC 1973 did not make Frame Relay trustworthy. It made a point-to-point conversation legible enough for two peers to notice when the conversation had changed shape—and to begin again before silence became a black hole.
IETF
Joyce Reynolds and the Assigned-Numbers RFC That Stopped Being the Registry
In 2002, Joyce Reynolds gave an old standards document a more honest job. RFC 1700 would remain a durable record of what the Assigned Numbers tables looked like in 1994, but it would no longer impersonate the changing registry that engineers actually needed.
Story
AFRINIC's IPv4 Summary Rose by Two. One Reserved Block Split into Three
AFRINIC's daily file gained two IPv4 records on 9 September. The tempting story is two new allocations. The rows tell a more useful one: a conserved block changed shape.
IETF
A Diagnostic Plan Is Not a Root Cause: Eight Receipts for Scheduled OAM
`draft-ietf-opsawg-scheduling-oam-tests-07` makes network diagnosis programmable as timed, ordered test sequences. The discipline begins when operators refuse to let a stored plan, a green status or a returned metric stand in for the execution, causality, authority and outcome…
IETF
An IETF Draft Names a Conflict-of-Interest Gap. Authority Should Trigger the Safeguard
Revision 07 of an individual IETF process draft adds only one short paragraph on conflicts of interest. The paragraph is enough to expose a larger design problem: the IETF has several concrete conflict policies, but each belongs to a defined body or corporate role. A general…
IETF
The color matched. The proof did not: RFC 9832’s transport-class evidence chain
Three BGP fields can carry the same 32-bit value and still answer different questions. RFC 9832 supplies an ordered mechanism for classful transport; operators still need a chain of receipts proving which namespace, attribute, database, fallback and forwarding state actually…
IETF
RFC 9983’s Anycast Flag Marks Intent, Not Service Health
A single bit can remove ambiguity from routing data without proving that a single request will succeed. RFC 9983 gives OSPFv2 an explicit way to mark a prefix as anycast, but it also draws an unusually useful governance line: the mark states how the prefix is intended to be…
Afrinic SAGA
AFRINIC’s continuity controls remain harder to prove than its public machinery
AFRINIC can keep a registry visible while the evidence needed to establish lawful authority, privileged access, detection and recovery remains incomplete. The practical test is not whether the machinery appears to run, but whether high-impact changes can be authorised, observed…
History
The Grant Was Automatic. The Boundary Was Not: RFC 1988
RFC 1988 removed the need to ask Hewlett-Packard for the same narrow permission implementation by implementation. It did not remove the perimeter around that permission—or the switch that could end it.
Story
ARIN’s Board Slate Has One Candidate Beyond Three Seats
Three seats. Four candidates. ARIN’s 2026 Board slate satisfies the rule that there must be more names than vacancies, but it does so at the narrowest possible margin. That fourth name is not decorative competition. It is the point at which an elected choice remains a contest and…
IETF
Paul Mockapetris and the Authoritative Bit That Did Not Cover the Whole Reply
One DNS response can carry an authoritative alias, a cached destination and helpful address records under a single AA flag. The bit has done its job; the database that stamped the whole packet “authoritative” has not.
CASE FILE
AS210328 After Registration: The Missing Link Between Network Identity and Cloud Service
AS210328 After Registration: The Missing Link Between Network Identity and Cloud Service intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences…
History
The Packet That Could Not Be Decrypted: RFC 1969’s Cross-Packet Chain
A lost encrypted packet in RFC 1969 did more than remove its own contents. It also took away the input needed to decrypt the next packet—yet the ciphertext of that unreadable successor carried enough state to let the receiver continue after it. This peculiar two-packet shadow…
Story
RIPE Atlas Can Show the Edge. It Cannot Show Who Chose It
A path measurement can show where one request landed. It cannot, on its own, reveal the platform rule that sent it there, the traffic that was eligible, the share served locally or what happens when the appliance disappears.
IETF
The watts fell. The proof did not: RFC 9845 and the green-network control loop
A power graph can move down while the network’s carbon cost, workload allocation and service risk remain unknown. RFC 9845 makes visibility useful; it does not let one meter speak for the whole system.
IETF
A Workload Credential Is Not the Workload: Eight Proofs Between Bootstrap and Outcome
The WIMSE practices draft shows how platforms can replace embedded secrets with short-lived workload credentials. Its harder lesson is that every safer credential still sits inside a longer chain of facts that must not be compressed into one green authentication event.
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