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
4,363 articles
IETF
QUIC Stream Limits Count Openings, Not Live Concurrency
A transport authorization is a lifetime ledger, not a dashboard of active work.
IETF
The MPLS Generic Associated Channel Carries Maintenance Without Turning Its Label into Forwarding Authority
MPLS label value 13 acts as the Generic Associated Channel Label, identifying a G-ACh packet and indicating that an Associated Channel Header follows the bottom of the label stack. The ACH Channel Type then selects a registered processing context. This is an in-band maintenance…
History
The Number That Made TCP Flow Control Move
TCP did not put a receiver's memory size into every segment. It put a moving allowance into the header: a count of how many data octets the sender of that segment was then willing to accept, beginning at the acknowledgment frontier. That pairing turned flow control into a…
CASE FILE
The Signature Still Verified. The Identifier Had Changed
A new measurement submitted to the IETF shows how 64 different CBOR encodings can preserve one valid COSE signature while producing 64 different hashes of the transmitted statement. The cryptography did not fail. The storage boundary did: a system that reads and re-encodes before…
AFNOG
AfNOG’s ‘Soon-to-Be-Deployed’ Tutorial Scope Leaves Readiness Undefined
AfNOG’s 2007 call described advanced training on technology soon to be deployed without defining readiness.
History
The Handle Was the Same. The Credential Could Be Different: RFC 1509
Two programs present the same pointer-sized value to a security service. One reaches Alice’s credential. The other may reach Bob’s—or nothing at all. No bit in the value has changed. The caller has. RFC 1509 made this possible on purpose, because its handle was never the…
CASE FILE
The SID Field Was Present. The SID Was Still Missing: RFC 9831
A controller sent a Segment Type I with its SID-present flag set. The receiving headend could count all 16 octets of the field. Every octet was zero. That was not malformed silence: RFC 9831 permits the controller to describe the behavior it wants while leaving the executable SID…
IETF
TR-4 Can Mean “Record Only.” One Conformance Number Is Not a Proof
The most revealing event in a new format for machine testimony is that the format had to correct its own testimony. Revision 01 withdrew a claim its cited survey did not support, made a supposedly verifiable digest reproducible, and admitted that its implementations all came from…
CASE FILE
At Mozilla, a Module Owner’s OK Is Neither Commit Access Nor a Firefox Release Promise
Mozilla’s public governance material makes a useful distinction that reporting often erases. A module owner or peer can approve a change for a module; a person can separately be granted repository access; a change can be checked in or landed; and Firefox can later move code…
IETF
An MPLS Extension Label Expands a Scarce Namespace Without Letting the Sender Assign Meaning
An MPLS LSR sees Base Special-Purpose Label 15 as the Extension Label (XL), then interprets the immediately following label under the Extended Special-Purpose Label (eSPL) registry. That two-entry mechanism expands a tightly constrained namespace without allowing a packet author…
Story
ARIN’s Harmonization Draft Needs a Semantic-Diff Ledger
ARIN-2026-4 presents itself as clarification, but two nearly parallel clauses differ in actor and modal force: the current text says registration “guarantees” uniqueness, while the proposal says a public registry is “necessary” to ensure uniqueness of allocated resources. Those…
IETF
The Model Behind the Label Stack: RFC 9902 and the Operational Contract for IS-IS Segment Routing
One enable leaf can start advertising IS-IS Segment Routing extensions, but safe activation depends on the protocol-independent SR label resources already configured beneath it. RFC 9902 makes that seam visible: the switch belongs to IS-IS, while the resources it invokes belong…
IETF
QUIC Final Size Fixes a Byte Boundary, Not an Application Outcome
A transport fact can close a stream direction without closing the question of what the application actually accomplished.
History
The Bits TCP Kept for the Future
Six quiet positions in TCP's 1981 header carried no immediate function. Their importance lay in the discipline around that emptiness: send them as zero, leave them available, and let a later standard define meaning without moving the boundary of the base header. Two decades…
IETF
An ICMP Label Stack Reveals MPLS Failure Context Without Authorizing a Repair
When an MPLS LSR generates a selected multi-part ICMP error, it can append the complete incoming MPLS label stack. A diagnostic consumer can therefore see encapsulation context that ordinary ICMP omits; the report enriches diagnosis, but it does not authorize anyone to repair the…
IETF
Reveal Less, Prove Enough: RFC 9901 and the Control Surface of Selective Disclosure
One issuer-signed credential can disclose an address to one verifier and a birthdate to another because its signed JSON carries salted digests while the holder presents only selected cleartext Disclosures. That mechanism is defined by RFC 9901, an IETF Standards Track…
AFNOG
AfNOG’s Non-Commercial Tutorial Principle Leaves Its Meaning Undefined
AfNOG’s 2007 call said tutorials should be non-commercial but did not define that boundary.
History
The Bit That Made TCP’s Acknowledgment Number Mean Something
Every TCP segment reserves 32 bits for an acknowledgment number, but the number is not automatically evidence. One control bit decides whether those bits describe the next sequence number the sender expects—or are simply not significant at all.
IETF
A QUIC Packet Number Is a Reconstruction, Not a Global Sequence
A protected QUIC header carries only part of a packet number. The rest is recovered from authenticated state, so a wire value cannot serve as a connection-wide counter.
Story
ARIN’s Property-Language Proposal Needs a Document-Control Ledger
Deleting one sentence from a policy manual does not settle a rights question. It relocates the reader’s evidence path. ARIN-2026-3 makes that relocation the central governance issue: if NRPM Section 6.4.1 is retired, readers need a reliable way to find the proposition that…
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