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,154 articles
IETF
Mike McBride and the Multicast Registry That Prevented One Kind of Collision
Two IPv6 multicast allocation methods had been told to draw identifiers from the same box. RFC 10028 divided the box before a future host protocol and an old server protocol could make the same choice—and left operators with the harder job of proving that their networks had…
History
The Cutover Was Not One Cutover: How RFC 897 Separated Renaming from DNS Resolution
On 14 March 1984 a host could acquire an official name ending in `.ARPA` while the program using that name still consulted a local copy of a centrally maintained table. The new namespace could arrive through the old lookup machinery. RFC 897 made that apparent contradiction a…
ICANN
ICANN's Early IGO Arbitration Window Has No Answer Clock
ICANN's draft rules give a domain registrant a new choice before an IGO complaint is decided: request binding arbitration early. They say where the request goes and who receives notice. They also let the IGO accept or decline. What they do not say is when that answer is due, what…
Story
APNIC Reissued Four Expired ASPAs. Its Repair Needs a State Receipt.
APNIC has reported a bounded correction: automatic renewal did not run, four ASPA entities expired, and the entities were reissued and published at 11:03. That is useful operational disclosure. It is not yet a measurement of what every repository, validator, router or customer…
CASE FILE
One Trustee Roster, Two Boards: Internet Society Decisions Need a Capacity Receipt
Internet Society and its Foundation use the same trustees, yet their governing documents create two Boards—and a third capacity when Internet Society acts as the Foundation's sole Member. Back-to-back 2026 agendas show why aligned oversight still needs a record of which legal hat…
CASE FILE
A Ciphertext Reached the Key. It Did Not Name Its Sender: RFC 9180 and the Authority Missing from HPKE Base Mode
A team can receive an HPKE ciphertext, open it with the intended private key and still be unable to say who sent it, what outer request it belonged to, whether it is fresh, or whether anyone was entitled to act on its plaintext. RFC 9180 makes the cryptographic transition…
CASE FILE
An MPLS Action Is Not an Admission Decision: RFC 9994
A packet can arrive with a perfectly formed MPLS Network Action Sub-Stack, an opcode that an engineer can name and ancillary data that a parser can read. That packet has not yet proved that the next node supports the action, that the action belongs on this path, that its data…
History
The Dash That Grew With Every Forwarding: RFC 934 and the Cost of Recursive Quoting
In 1985, a message digest faced an apparently small problem: a line of ordinary mail text could look exactly like the line chosen to separate enclosed messages. RFC 934 answered by adding characters on the way in and removing them on the way out. That made the boundary…
Story
ARIN Kept Five Services Running Without Updates. Its Service-Level Report Has No Freshness Column
A registry can answer a question and still have nothing new to say. ARIN's planned July maintenance made that distinction visible: five reader-facing services remained operational while updates were not being published. The public service-level report measures availability well…
CASE FILE
The Packet Declared a Haptic Effect. The Device Still Had to Decide Whether to Render It: RFC 9993
A remote session marks one haptic unit as high priority. The packet is valid, the stream is negotiated and the receiver can decode it. None of that tells an actuator where on a body it may act, whether the requested amplitude is within the device’s envelope, whether a temperature…
History
The LANs the Host Was Not Meant to See: RFC 925 and the Cost of Hiding a Topology
An early Internet site could either expose every cable to the wider network or arrange its cables so that a host believed it lived on one large local network. RFC 925 chose the second illusion. It kept the host's ARP unchanged and made an intermediary discover, remember and…
CASE FILE
A Key Could Cross the Fabric. It Could Not Decide the Route: RFC 9992 and RIFT Authority
Two Top-of-Fabric nodes lose contact, each advertises the same RIFT key with a different value, and a leaf sees both. It must select one. A deterministic result is useful; it is not a declaration that the winning value is the current truth, that any receiver may act on it, or…
History
The Carrier Was Not the Connection: How RFC 892 Separated Transport State from the Network Path
One network connection could carry several transport conversations. One transport conversation could, in the most capable class, ride several network connections. RFC 892 treated those as inverse mappings rather than a contradiction: the carrier moved protocol units, while peer…
CASE FILE
The Private Key Never Left. Its Authority Did: RFC 9987 and the Transitive Trust of SSH Agent Forwarding
An engineer forwards a workstation’s SSH agent to a bastion. A process on that bastion cannot copy the private key, yet it may still ask the distant agent to sign a new authentication request. “No key exfiltration” is therefore an incomplete incident verdict: material custody and…
CASE FILE
The Domain Requested the Failure Report. The Receiver Still Had to Authorize Disclosure: RFC 9991 and DMARC Forensics
A mail receiver detects a genuine authentication failure in a forwarded calendar invitation. The author's domain has requested a forensic report at an external address. Sending the report could expose the invitation, its recipients and the forwarding path to a party that never…
IETF
Gavin Brown and the Successful Create That Did Not Yet Register a Domain
The server said the command had completed successfully. In the same breath, it said the action was still pending. RFC 8334 makes that apparent contradiction useful: an accepted application is evidence, but it is not yet a registered domain.
Story
AFRINIC’s News Page Canonicalizes to Its Privacy Policy
The page is reachable and visibly full of news. The contradiction sits in the same HTML response: the title, heading and structured data call it News & Announcements, while the canonical URL and social identity call it AFRINIC’s Privacy Policy.
CASE FILE
SC100’s Draft Draws DNSSEC’s Boundary at the Primary Perspective. The Receipt Must Name It
SC100 passed its vote by unanimity among the members who participated, but on 31 August 2026 it was still an accepted draft under intellectual-property review. Its most useful clarification is not that “DNSSEC is required.” That duty already exists. It is that the duty belongs to…
Story
APNIC's EC Adopted Topic Shepherds. No Public Charter Says What a Shepherd Can Do
APNIC's Executive Council has chosen a sensible answer to a familiar board problem: give individual members continuing responsibility for important subjects. Its May minutes call them topic “Shepherds” and say they will lead discussions on allocated areas. The missing part is not…
IETF
RADEXT’s Recharter Is Still Under Review. Seven Milestones Are Dated May or August
The proposed RADEXT charter has two clocks. Its approval clock still reads External Review. Its delivery table carries two milestones dated May 2026 and five dated August. That does not prove seven failures: some work is active, some awaits adoption, and the proposal itself is…
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