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,707 articles
IETF
A Healthy RadSec Proxy Could Not Prove the Home Realm
The access controller had a protected RadSec connection, a valid peer certificate and a prompt `Status-Server` reply. One customer realm still timed out. Nothing in those observations is contradictory: each belongs to a different hop, and revision 18 of the RadSec draft makes the…
History
The Hash Chose Which DHCP Server Could Answer. It Could Not Promise Service
RFC 3074 turned a configured share into 256 buckets and a repeatable answer to one narrow question: which server was eligible to respond? The map did not measure work or prove a lease arrived.
ICANN
The Remedy That Has Never Been Used: Whether the Draft RIR Governance Document's Derecognition Machinery Is Actually Operable
Every accountability system is judged not by the rules it writes but by whether anyone has ever made those rules work. The *Governance Document for the Recognition, Operation, and Derecognition of Regional Internet Registries* — Version 3, dated 1 September 2026 and labeled FINAL…
IETF
The Dashboard Still Showed 10,000 Valid Routes. They Were Not the Same 10,000.
The number survived the maintenance window without moving. That looked reassuring—until the operators compared the routes behind it. A new IETF YANG draft makes several RPKI validation totals observable across the BGP pipeline. It also makes clear why a total, detached from its…
History
The Hash Assigned the Server. It Did Not Prove the Server Was Ready: RFC 3074
RFC 3074 let cooperating DHCP servers compute who should answer without negotiating each request. The same calculation could not say whether the chosen server was reachable, had an address to offer or completed the client's configuration.
Story
Call for Nominations to the RIPE NCC Executive Board: What the 2026 Record Actually Publishes
The RIPE NCC has run a complete Executive Board nomination cycle for its May 2026 General Meeting. Reading the registry's own instruments — the call for nominations, the candidate and nomination procedure pages, and the document submission guidelines — shows a process that is…
CASE FILE
The Mailbox Was Never the Remedy: Where Accountability Actually Fired in the Svea Abuse-Contact Chain
Every abuse report has to land somewhere. For Svea's legacy routed network block 193.105.138.0/24, the landing place shown by independent mirrors of the RIPE Database is a shared mailbox on the Verizon Business domain — a carrier-era contact inherited from a lineage Svea never…
History
The MIME Name Was Public. The Font Specification Still Lived at the Vendor: RFC 3073
RFC 3073 gave Portable Font Resource files a public MIME name. It did not make that name a substitute for the complete specification, a compatible decoder or evidence that a recipient rendered the intended glyphs.
IETF
The Collector Counted CE. It Could Not Tell Which Service Was Marked
A dashboard reports 12,000 Congestion Experienced packets and divides them by the ECT(1) total. The percentage looks exact enough to justify a change to the low-latency service. Yet the packets now carrying CE no longer say whether they arrived at the marker as ECT(1) or ECT(0).…
IETF
The Voucher Promised Another Voucher. Renewal Had Not Happened.
ANIMA's current onboarding draft gives a MASA room to project how long it expects to renew a device Voucher. Revision 36 also makes the later gates clearer. The projected date is still not a replacement artifact, a service-availability receipt or proof that the device completed…
Story
The Svea Abuse-Role Record: Validated Contactability, No Documented Processing
The abuse contact recorded and mirrored for Svea's legacy netblock 193.105.138.0/24 is a carrier-era inherited mailbox on the Verizon Business/UUNET lineage — registry-validated for technical deliverability but never documented to have received, answered, escalated or remediated…
History
The Parser Could Skip the Chunk. It Could Not Know What It Meant: RFC 3072
RFC 3072 made an unfamiliar SDXF chunk traversable by giving it a boundary a reader could locate. But reaching the next chunk is not the same as understanding what was skipped—or knowing whether an application can safely ignore it.
Number Resource Society
The nomination funnel behind RIPE NCC's Executive Board election: what the May 2025 record actually shows
Every three years, the RIPE NCC membership nominates, supports and elects the people who sit on the body that governs the world's largest regional internet registry by membership count. The May 2025 election left a complete public record: a call for nominations under Article 9.1…
CASE FILE
The Mailbox That Exists Only in the Registry: Svea's Abuse Contact and the Limits of "Valid"
When Svea Ekonomi AB merged into Svea Bank AB on 3 January 2022, the group's abuse-contact surface in the RIPE registry did not follow the merger. Nearly four years later, the routed legacy netblock 193.105.138.0/24 still presents a mailbox on a third party's domain…
History
The Label Was a Country Code. The Registry Could Still Be Generic: RFC 3071
In 2001, John Klensin argued that two characters could identify a country-code namespace without telling readers how its registry actually behaved. RFC 3071’s proposed categories followed operating practice—not the shape of the label—and stopped short of asking DNS administrators…
IETF
The Draft Removed Two HPKE Modes. Running Code Did Not Disappear.
The proposed HPKE replacement reserves the two mode values that RFC 9180 used for Auth and AuthPSK. That is a clear standards decision; it is not an inventory of libraries, profiles, stored entities or counterparties that may still depend on the older compatibility set.
IETF
The Proxy Authenticated the User. It Did Not Authenticate the Source MAC
A green tunnel indicator can be perfectly accurate and still conceal the most important unresolved question: which Layer 2 identities may the authenticated user introduce into the remote broadcast domain? CONNECT-ETHERNET draws that boundary sharply. HTTP can establish the…
ICANN
If JPRS Fails, Who Keeps .jp Running? Reading the Successor Machinery in the .jp Record
Japan Registry Services Co., Ltd. (JPRS) has operated .jp since 1 April 2002 under an unusually public set of governing instruments. But the question of what happens if JPRS itself fails — bankruptcy, insolvency, or a decided re-transfer — has not previously been the subject of…
History
The Mask Promised a Neighbor. The VLAN Required a Router: RFC 3069
RFC 3069 saved IPv4 addresses by giving separated customer networks one shared prefix. But a host’s idea of “on-link” did not create a shared link: an upstream router had to answer, bind and forward.
History
The Tunnel Was Media-Independent. Its Circuit Was Not: RFC 3070
RFC 3070 made L2TP portable across a Frame Relay network, but portability did not make the bearer disappear. The tunnel still depended on a virtual circuit with its own endpoints, framing identifier, setup rules, packet-size limit and unresolved questions of service quality and…
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