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,058 articles
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…
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…
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.
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…
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…
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.
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…
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.
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…
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…
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…
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…
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…
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.
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…
AFNOG
AfNOG Publishes Host Preferences but Makes the Convenors’ Choice Final
AfNOG’s public hosting page gives a prospective Africa Internet Summit host an unusually detailed list of obligations. It also publishes three selection preferences. What it does not publish is how those preferences are compared before AfNOG Convenors and AFRINIC Management make…
CASE FILE
The Header Was Allowed in the ACK. It Did Not Validate the Bill: RFC 9878
RFC 9878 fixes where several 3GPP SIP P-Headers may appear, including a narrow exception for ACK after a successful response. That permission solves an interoperability problem; it does not turn a signalling field into proof of location, route, entitlement or charge.
CASE FILE
W3C's ARIA Implementation Report Says March. Its File Changed in May.
W3C's updated *ARIA in HTML* Recommendation points readers to an implementation report whose visible date is 22 March 2026. The public file history shows a large revision on 20 May and another change on 27 May. Both can be true: March may be the evidence cutoff and May the…
History
The Fallback Was Written Down. Running Servers Still Broke the Session: RFC 1425
The old server was supposed to say that it did not understand `EHLO`, remain connected and let the client try `HELO`. That was the elegant transition drawn in RFC 1425. Seventeen months later, its successor had to record what running systems actually did: some dropped the…
History
The Shortcut Was for Display. The Stored Address Had to Outlive It: RFC 1278
The sharpest sentence in RFC 1278 comes after the convenient machinery. Macros could shorten a long presentation address, nest inside one another and choose the longest available substitution for display. Then the memo drew the line: no macro should ever be relied on. In 1991…
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