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 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
8,111 articles

IETF
A Call-Home Datagram Is Not Device Authority
A managed router may need to reach an operator from behind an address translator or firewall. The newest NETCONF working-group draft adapts Call Home to QUIC by having the device send an empty UDP datagram and the management system connect back to its source. The mechanism is…

CASE FILE
The Log Filter Made Tomorrow’s Evidence Decision
RFC 9742 gives network operators a common language for configuring syslog. The harder question is whether that language preserves the particular evidence an incident will make valuable.

IETF
PQC Readiness Draft Lists One Implementation but Closes None of Five Gaps
Running code deserves attention. It does not deserve a larger claim than its evidence can carry. A new revision of an individual Internet-Draft on post-quantum readiness now lists one certification-authority implementation, one estate and one set of classical-certificate…

History
Jan Gruntorád and the Link That Had to Become Two Networks
At the start of 1992, an international circuit from Prague to Linz was strengthened and divided. One channel continued to carry EARN traffic; the other was assigned to the Internet. In that physical line becoming two operational networks lies a more useful history of Jan…

IETF
A Fast-Path Timestamp Is Not an Authenticated Measurement
A network can make a measurement faster by keeping a probe in silicon. That is an engineering gain, not a cryptographic transformation. The proposed Timestamp and Forward mode for segment-routing STAMP lets a reflector write a receive time in the data plane and send the packet…

Story
RIPE NCC Lets Operators Sign ASPAs Without Showing the Providers It Sees
RIPE NCC has made ASPA signing possible and tells operators to list every real upstream. Its public guide also says the Dashboard offers no BGP-derived hint about who those upstreams might be. The missing interface is not an automatic answer but an evidence receipt that helps a…

Story
RIPE’s NRTMv4 Source Gate Reads a Replica. Its Fallback Does Not Cover the Gate
A three-file code change gives RIPE NCC’s NRTMv4 service a sensible read path and leaves one unusually precise question behind: when a source is new, what proves the catalogue reached that path before the service begins treating it as authoritative?

IETF
VXLAN's Registry Opens 39 Bits While Its Wire Text Still Reserves 24
A protocol registry is a promise about future change. A packet diagram is a promise about what implementations do now. The latest VXLAN bis draft makes both promises about the same header, but they do not yet line up: its proposed IANA registry marks 39 unused bits as Unassigned…

IETF
An Unset FRR Flag Cannot Name the Local Policy That Won
A traffic-engineering head end asks every repair point to keep a backup path below a delay bound. The reservation comes back with one repair point’s new flag unset. Traffic may still have a backup there, computed under local policy, but the ingress cannot tell from that bit which…

History
Ben Segal and the TCP/IP Pilot That Could Not Leave CERN
By March 1988, TCP/IP served 355 machines at CERN, from an IBM mainframe and a Cray to VAX systems, workstations, PCs and Macintoshes. Yet none of those machines could use TCP/IP to cross the laboratory’s external boundary. Ben Segal’s pilot had solved heterogeneous connectivity…

CASE FILE
RFC 9744: the circuit identities a shared tunnel must retain
Fewer service labels can make a carrier network cheaper to operate. The saving becomes less convincing when the remote edge can no longer tell which customer circuit needs a different path.

Story
AFRINIC's 2026 Closure Data Spells Voluntary Two Ways
AFRINIC has done the useful thing by publishing reproducible statistics on closed memberships and returned number resources. But its current 2026 data place `VOLUNTARY` beside `VOLUNTART`, and the dashboard treats the two strings as different categories. That one-character split…

IETF
A Verified RDAP Contact Needs an Audience Boundary, Not a Universal Badge
A registrar can verify an email address once and face two different disclosure questions the next morning: what may an anonymous reader learn, and what may an authenticated investigator learn for a justified purpose? The verification event is the same. The authority to disclose…

IETF
COSE HPKE's Default Mode Does Not Authenticate the Sender
A protected COSE entity arrives, the selected recipient key opens it and every cryptographic check in the HPKE operation succeeds. That result is valuable, but it does not always answer the question an operator is most likely to ask next: who sent this, and were they allowed to?…

History
RFC 2057: the 1996 argument over who controlled the audience
In 1996, sending an email to a mailing list could hand its onward distribution to another operator's program. Scott Bradner's RFC examined the distance between controlling that first transmission and establishing the identity and age of everyone it eventually reached.

History
Rob Blokzijl and the Chair That Could Coordinate but Not Command
The most revealing sentence in RIPE’s first terms of reference is not the one that declares a European ambition. It is the sentence that withholds power. RIPE was not a network provider, and the networks cooperating through it remained under the executive authority of their own…

Story
LACNIC’s AI Client Resolves a Model, Then Chats Without a Resolution ID
LACNIC has published a cleaner way for Java applications to reach its PAI AI gateway. The new client says which model answered. What it cannot say, in its public typed contract, is whether that answer came from the exact model-resolution state the application inspected a moment…

CASE FILE
RFC 9746: the compatibility cost of choosing EVPN split horizon
A default-method entity can send an upgraded Ethernet segment back to its encapsulation baseline. The operational question is whether the network has kept the resources and evidence needed to make that return safely.

IETF
An Authenticated BGP Update Is Not an SD-WAN Tunnel Admission Record
When a protected control-plane session delivers a syntactically valid route, it is tempting to treat the event as one completed act of trust. In an SD-WAN, however, the update has only crossed the first of several institutional boundaries. The harder question is not whether BGP…

IETF
A Writable Port Map Needs an Override Receipt
The service orchestrator has found a promising attachment point. One reference tells it which physical port lies beneath the logical choice, and the next capacity query may decide whether the order proceeds. In the IETF’s new Last Call, that small reference is normally…
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