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,451 articles
Story
RIPE's member-of Proves Authorized Set Membership, Not Live Route Propagation
RIPE's member-of Proves Authorized Set Membership, Not Live Route Propagation 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…
CASE FILE
The Verification That Will Not Come Again
A JMAP subscription can be accepted just as its authentication assumptions expire. RFC 9749 puts recovery on the client—and a reported error in its optional warning path makes that hand-off worth examining closely.
CASE FILE
The Failure Event Was Signed. Its Second Arrival Was Still a Replay.
A vendor outage alert enters an agent session, passes signature verification and triggers a fallback. The receiver loses its acknowledgement, so the same alert arrives again. Every cryptographic check can still be green while the second delivery repeats a real-world response.…
IETF
CFRG’s Curve Rewrite Leaves Three Acceptance Decisions to Calling Protocols
A byte string can pass every mathematical check and still be unacceptable to the protocol that received it. Revision 14 of CFRG’s pairing-friendly-curves draft makes that boundary unusually visible: the common document says how to recover valid points and scalars, while the…
CASE FILE
Cancel the Second Checklist
Closing a redundant register should end a redundant obligation. RFC 9751 offers a precise example of administrative subtraction—and a test for organisations whose paperwork can outlive the procedure it describes.
History
The Number That Changed Meaning at the Domain Boundary
One security domain could encode “Unclassified” as 5 while another encoded the same human label as 1. CIPSO did not solve that disagreement by choosing a universal number. It put a Domain of Interpretation identifier beside the number and made interoperability depend on the…
IETF
Suzanne Woolf and the Server Label That Is Not a Machine Identity
A DNS reply can carry a label for the server that produced it. That sounds like identity until anycast, operator-defined bytes and hop-by-hop scope are allowed back into the picture. Suzanne Woolf’s work on the requirements behind NSID offers a more useful interpretation: the…
Story
APNIC's ASPA Lists Authorized Providers, Not Observed Transit
APNIC's ASPA Lists Authorized Providers, Not Observed Transit 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. The Story…
Story
APNIC Adopted a Foundation Liaison. The Public Record Stops Before the Protocol
APNIC has done the difficult part that institutions often avoid: it identified an old role with no settled scope, named the governance risks around it, and formally adopted a replacement. The next part was deliberately separated. Observer attendance, confidentiality and…
CASE FILE
Who Keeps the Original Mail?
A legacy inbox can show a readable substitute while losing the address, context or verification that made the original useful. RFC 9755 turns compatibility into a question of custody.
CASE FILE
A Data Manifest Cannot Account for the Datapoints That Never Arrived
A network chart contains a clean sixty-second blank. The points before it have a platform, subscription and collection context; so do the points after it. The empty interval has none. A manifest can make received telemetry intelligible, but it cannot, from inside the same…
CASE FILE
The Agent Timed Out. That Does Not Mean Its Budget Came Back.
A procurement agent sends a bounded order to a supplier. The call disappears into a timeout. No confirmation returns, but the supplier may already have accepted the order. At that moment, refunding the agent’s authority is not customer service; it is permission to spend twice. A…
CASE FILE
Who Pays to Retire an Experimental Number?
A successful network trial leaves more than working software. It leaves a dictionary of errors, tools that read it and people who depend on it. RFC 9756 makes the route to a permanent assignment clearer; someone still has to pay for the move.
History
The Security Label That Needed Its Own Specification
One IPv4 option could appear more than once in the same datagram, yet no occurrence was self-explanatory. Its one-byte format code pointed outward to another specification that defined what the remaining bytes meant and whether a system should accept them.
Story
APNIC Put 23 September and 17 August in One Payment Notice
A service notice should let a Member decide when to act. APNIC’s current online-payment notice instead presents one four-hour window in its identity and timetable, then names a different day in the description. The responsible conclusion is not to choose between them. It is to…
History
The Parent Named the Server. The Server Still Had No Zone: RFC 1912 and Lame Delegation
The referral worked exactly as configured. A resolver asked the parent where to find a child domain, received two name-server names and sent a query to one of them. Only then did the system reveal its mistake: the selected machine had no child zone to serve. The directory entry…
Story
ARIN's Retired Origin AS Field Recorded a Possibility, Not a Live Route
Old registration exports can preserve an `Origin AS` value long after ARIN removed the field. The label looks authoritative, but ARIN defined it as an optional holder-supplied list of ASNs from which a block might originate. It was neither a cryptographic authorization nor a…
IETF
Deletion Is the Hard Test as DNSOP’s Integration Draft Reaches Its Last Call Deadline
A DNS name can be easy to attach to an application and surprisingly hard to detach. As DNSOP’s integration draft reaches its scheduled Working Group Last Call deadline, its most consequential test is not whether a user can prove control once. It is whether the application can…
IETF
Sara Dickinson and the Resolver Promise Encryption Cannot Prove
The padlock beside a DNS resolver name is reassuring because it proves something useful: the client has protected its conversation on the way to a particular service. It is also dangerously easy to ask that icon to prove the rest. Sara Dickinson’s co-authored RFC 8932 follows the…
CASE FILE
The Alarm Needs a Way Home
Multipoint BFD can detect a broken branch close to the receiver. Turning that local knowledge into a dependable decision at the source is a separate service—with its own paths, capacity and owner.
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