Skip to main content

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
Governance signal visual
GovernanceGovernance
FocusInstitutional Governance

Policy continuity, legitimacy, and accountability signals across internet governance institutions.

CurrentSeven Governance Tracks

RIR Watchdog, Case File, NRS, ICANN, IETF, History of Internet, and NOG sessions.

SignalExecution over Statement

Coverage prioritizes implementation evidence and institutional behavior over declarative positions.

Latest Coverage

Latest from Governance

4,303 articles

Story

ARIN Publishes IPv6 Requests Beside Delegations. The Cohorts Are Not Joined.

An IPv6 request can enter ARIN’s system, pass automatically or move into staff review, prompt a request for more information, receive approval, wait for fees and a signed agreement, and only then become an issuance. ARIN publishes useful numbers at the entrance and the exit of…

Sep 3, 2026

IETF

IETF Separates Training Scripts From Slides. Now Test the Handover.

The IETF's latest training-procurement answers make captions, transcripts and narration scripts separate source assets. That is a useful move toward maintainable course material. Its value will become visible when someone other than the original producer has to correct a module.

Sep 3, 2026

History

The Transport Opened a Connection. SNMP Still Owned the Retry: RFC 1283

A connection is an enticing piece of evidence. It has a beginning, a lifetime and an end. In 1991, RFC 1283 placed SNMP on an OSI connection-oriented transport and then warned implementers not to read too much into that new structure. The connection could carry one or more…

Sep 3, 2026

CASE FILE

The Request Was Signed. The Other Private Key Was Still Only Asserted: RFC 9883

A certificate request can carry a valid signature and still offer no technical proof that the requester holds the private key named by its new public key. RFC 9883 does this deliberately. It turns the gap into an explicit policy choice—and a revocation dependency that operators…

Sep 3, 2026

IETF

Tommy Pauly and the QUIC ACK That Did Not Reach the Application

A QUIC acknowledgement can close one precise transport question while leaving the question an application actually cares about open. RFC 9221, co-authored by Tommy Pauly, makes that seam unusually visible for DATAGRAM frames: the receiver's transport processed a frame, but the…

Sep 3, 2026

Story

APNIC's Directory Terms Proposal Turns Query Access Into a Governance Question

Prop-173 would replace ambiguity around ordinary APNIC WHOIS and RDAP queries with a public, versioned acceptable-use policy. The consequential question is not whether terms should exist, but whether their rules distinguish legitimate operational reuse from a substitute data…

Sep 3, 2026

IETF

DNSOP Can Recommend a Domain-Control Check. It Cannot Govern an Application Identity’s Lifecycle.

The DNSOP working group is in Last Call on a useful document about applications that use global-DNS names as identifiers. Its central discipline is easy to miss. A service may need proof that a registrant or an authorized party controls a domain when an integration is…

Sep 3, 2026

History

The Client Found the Person. The Score Still Belonged to One Directory: RFC 1431

A successful search can be the beginning of an evaluation rather than its conclusion. In February 1993, RFC 1431 asked what an X.500 directory client had actually accomplished when a person's entry appeared—and what the answer had cost inside one particular directory.

Sep 3, 2026

Number Resource Society

When a Contributor Fee Opens a Governance Door, the Record Must Show Why

A contributor fee can support serious community work, and a fee-paying contributor can be qualified for leadership. The governance problem begins only when a public eligibility promise is not matched by a record showing how contributor status, nomination, interests, recusal and…

Sep 3, 2026

CASE FILE

RFC 9882 Put SHA-512 in the Field. It Did Not Always Use It

A CMS record can truthfully name SHA-512 while that algorithm contributes nothing to the signature being checked. RFC 9882 requires exactly that combination on one of its two ML-DSA paths. The apparent contradiction disappears only when an auditor follows the bytes rather than…

Sep 3, 2026

IETF

The Newer Packet Arrived First: How TCP RACK Used Time to Find Loss

RACK changes the evidence TCP can use when looking for loss: not only sequence-space gaps, but also the transmission times of data known to have arrived.

Sep 3, 2026

History

The Rule Was Voluntary. The Sanction Still Needed a Local Mandate: RFC 1281

A network can share a rule without sharing a government. RFC 1281 began from that awkward fact. The Internet of 1991 depended on voluntary cooperation, yet security failures crossed institutional borders and demanded action. The memo's durable insight was not that goodwill could…

Sep 3, 2026

Story

AFRINIC Reported Its Forms Site Offline. The Notice Did Not Close the Recovery Loop

AFRINIC’s 13 May notice established one narrow public fact: forms.afrinic.net was temporarily unavailable while urgent maintenance followed a technical issue. It did not establish when the problem began, which workflows were affected, or when a verified recovery occurred.

Sep 3, 2026

IETF

Gorry Fairhurst and the Circuit Breaker Trip That Did Not Name the Fault

A transport circuit breaker is useful precisely because it knows less than an incident report. RFC 8084, written by Gorry Fairhurst, defines a way to halt or sharply reduce traffic after a configured measurement has remained beyond its threshold. It does not turn that reaction…

Sep 3, 2026

CASE FILE

WebAuthn's Report Has Four Browser Columns. Independence Needs a Key.

W3C's new WebAuthn Level 3 Recommendation links a fixed test report with four browser columns. The transition record adds that part of Chrome's implementation differs from Edge's. That caveat is important—and incomplete. Product names show where tests ran; they do not tell a…

Sep 3, 2026

IETF

A Device-Assignment Token Can Carry Evidence. It Cannot Carry a Relying Party’s Decision.

RATS is asking whether it should adopt a draft that describes an EAT profile for assigning a device to a confidential virtual machine. The question is useful and bounded. It concerns a text, `draft-poirier-rats-eat-da-10`, and the possibility of working-group work. It does not…

Sep 2, 2026

CASE FILE

RFC 9879 Modernised the MAC. It Did Not Retire the Legacy Reader

Two applications can open the same PKCS #12 file and report success for different reasons. One may verify its new PBMAC1 envelope. Another may fail to understand that envelope, ignore the failed check and continue to the encrypted key material. RFC 9879 makes the first path…

Sep 2, 2026

History

The Gateway Rewrote the Message. It Could Not Invent the Charset: RFC 1428

The old message arrived as eight-bit octets and a social fact. Somewhere, sender and reader knew what those bytes meant. The message itself did not say. In 1993, a gateway standing between that installed mail world and MIME could add structure, recode headers and leave a trace of…

Sep 2, 2026

Story

APNIC Can Define Internet Abuse Without Becoming Its Judge

Prop-172 would give APNIC policy a common vocabulary for abuse involving IP addresses. Its usefulness depends on a harder boundary: naming conduct must not quietly become authority for the registry to decide allegations, monitor networks or impose remedies.

Sep 2, 2026

History

The Domain Entry Pointed to the Organisation. It Was Not the Organisation: RFC 1279

The most disciplined line in RFC 1279 was not about search speed or a grand replacement for DNS. It was about identity. A domain and an organisation were different entities; a mailbox and a person were different entities. The proposed directory could connect them, but it was not…

Sep 2, 2026

Session Map

Governance Branch

RIR Watchdog

Five regional sessions tracking allocation policy, board legitimacy, and institutional continuity.

Open RIR Watchdog

Case File

Long-cycle governance dossiers with legal, election, and institutional stress analysis.

Open Case File

Number Resource Society

Membership, charter, and resource-governance intelligence from the NRS ecosystem.

Open NRS Session

ICANN

DNS coordination, accountability frameworks, and global multi-stakeholder process dynamics.

Open ICANN Session

IETF

Protocol standardization trajectory and interoperability risk under fragmented policy conditions.

Open IETF Session

History of Internet

Long-cycle infrastructure history used for governance interpretation and structural forecasting.

Open History Session

NOGs

Operator-level implementation intelligence from APRICOT plus regional and national NOG ecosystems.

Open NOGs Session