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
8,016 articles
History
The Database Said One Address. The Reply Followed the Packet Back: RFC 1445
The address book and the live packet disagreed. For a new request, the 1993 SNMPv2 administrative model used the address recorded for the destination. For the reply, it ordered something else: use the transport domain and address from which this request actually arrived, even if…
ICANN
ICANN Picks One Provider for Two Name Panels With Different Fee Rules
Analysys Mason will handle geographic and reserved-name reviews in the 2026 gTLD round. For applicants, however, those two desks do not produce the same bill.
CASE FILE
At Apache, a Release Vote Is Neither a Code Veto Nor a Board Technical Decision
At the Apache Software Foundation, a person can commit code, a qualified voter can stop a code change, a PMC can issue a formal release, and the Board can oversee the Foundation. Those acts sit in one institution, but they do not carry the same authority. Treating them as one…
CASE FILE
At OASIS, a Public Review Is Neither the Final Vote Nor a Suggestion
An OASIS standards document can collect comments, pass a Technical Committee ballot and still not be an OASIS Standard. Those are not redundant ceremonies. They are separate decisions with different records, constituencies and thresholds.
Story
RIPE's Flip Chart Experiment and the Work After the Introduction
A paper board helped researchers and network operators find one another. RIPE NCC's new account points to a useful next test: whether a promising introduction becomes a question both sides can afford to pursue, without silently committing either to data access or production…
IETF
IETF’s CSR Attestation Draft Leaves Verifier Selection to Format Designers
A last call on carrying device evidence in certificate requests puts a practical compatibility question in view: two services may understand the same format without being interchangeable destinations.
History
The Clock Went Back. The Key Had to Change: RFC 1446
After a power failure, an SNMP agent wakes with yesterday’s shared secret and a clock that thinks yesterday has not happened yet. A captured request, previously too old to accept, can become “recent” again. Its digest never changed. The receiver’s boundary of acceptable time did.…
History
The Key Changed Before the Reply Arrived. The Manager Had to Remember Both: RFC 1446
The agent had already installed the new secret. Its reply was built with that new value. The manager, still waiting for the reply before changing its own database, continued to trust the old one. RFC 1446 made this awkward interval explicit: a secure command could succeed at its…
Story
One Prefix, Two Countries in LACNIC’s Geofeed
A public location feed repeats 23 prefixes, four with conflicting country codes. The useful repair is narrower than deciding where the networks are: stop a loading rule from masquerading as geographic evidence.
CASE FILE
The Name Stayed the Same. The Module Did Not: RFC 9890
RFC 9890 makes a small registry correction with a large evidentiary consequence: a YANG module keeps its name and XML namespace across revisions, so identity alone can never tell an operator which definitions a system actually uses.
CASE FILE
OpenSSF Member Seats Stop at the Project Boundary
OpenSSF publishes a membership table with real fees, real representation routes and real Foundation-level benefits. It also publishes an unusually direct limit: a membership or sponsorship level does not decide a project matter, because project maintainers define that project's…
IETF
A Negative Trust Anchor Lets the Resolver Suspend DNSSEC Without Changing the Zone
When a signed domain breaks, a validating recursive resolver can either preserve the failure or create a narrow local exception. A negative trust anchor restores reachability without repairing the zone, but it transfers temporary authority over DNS authentication to the resolver…
IETF
IETF’s Broadband List Faces a Test of Reviewer Supply
A new discussion venue aims to give scattered access-network proposals a home. Its more demanding task is to assemble the people who can carry them through technical review.
IETF
Mukul Srivastava and the BMP Gauge That Counted a RIB but Did Not See a Route
A number can be both useful and radically incomplete. RFC 9972 gives BMP operators a more precise way to report how many routes occupy a named RIB view at a particular moment. It does not turn that count into a route record, a policy explanation or a delivery observation. Mukul…
Story
LACNIC’s Voice Primer and the Bandwidth Beyond the Codec
An 8 kbit/s voice encoder can send a 24 kbit/s stream before Ethernet, security and control traffic enter the calculation. LACNIC’s latest telephone explainer points to a distinction that matters when operators turn compression into a capacity budget.
CASE FILE
OpenJS CPC's New Community Vote Needs a Transition Receipt
This autumn, OpenJS Foundation’s Cross Project Council will replace two separate non-Impact voting paths with one Community Voting Member class. The Charter is unusually clear about the planned change: it names the effective election cycle, caps the new class at five seats and…
ICANN
ccNSO Draws a Boundary for ICANN’s IDN Follow-Up
The Council’s July answer permits enquiries prompted by a reasonable basis, while rejecting active compliance policing. A September Board discussion will consider the next steps for the still-pending recommendations.
IETF
BGP Roles Turn a Peering Relationship into a Route-Leak Boundary
Before two networks exchange a single route, each can state what kind of neighbour it believes it has. RFC 9234 turns that bilateral statement into a control: incompatible roles can stop the session, while the Only-to-Customer attribute can stop a marked route from crossing the…
IETF
Rich Salz and the TLS 1.3 Requirement That Was Not a Deployment Receipt
A standard can make a demanding rule without manufacturing the evidence that the rule has become true in every running system. That distinction is not a loophole; it is how an operator can tell a sound protocol decision from an unsupported deployment claim. Rich Salz’s…
History
The Module Kept Its Name. The Device Did Not Prove Its Version: RFC 1442
A monitoring console can display a MIB module's latest revision date with complete confidence and still know almost nothing about the code answering from a particular device. RFC 1442 gave SNMP information modules a stable identity and a disciplined memory of change. It also drew…
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