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,105 articles
LKNOG
LKNOG's 2019 Call for Papers Used Two Queues for One Agenda
LKNOG3 told authors that papers would be selected first-come, first-served, while also allowing its committee to retain a limited number of slots for exceptionally timely, important or operationally critical presentations. The two clauses made submission time the ordinary rule…
History
The Paper-Out Signal Changed. Nothing Had Yet Been Printed: RFC 1318
In the early 1990s, a printer cable could offer a manager a small, sharp vocabulary: power, online, busy, paper out, fault. Such words feel close to an outcome. A paper-out signal seems to belong to paper; online seems to belong to readiness; busy seems to belong to work. RFC…
CASE FILE
WHATWG Found No Objection. W3C Found No Consensus.
At 12:24 UTC on 28 August, Intel told the W3C Devices and Sensors Working Group that it had concerns about removing five peripheral APIs from a proposed charter. The message arrived through the channel and by the date named in the call for consensus. The same public archive then…
History
The Memo Said Standard. The Record Said Informational: RFC 1216
RFC 1216 called its Ultra Low Speed idea a new standard paradigm. The official record calls the document Informational, places it in the Independent Stream and says it has no formal standing in the IETF standards process. The contradiction is not a clerical nuisance. It is the…
NPNOG
Safety by Organiser Discretion: Testing npNOG’s Code of Conduct
npNOG’s published conduct policy sets a clear behavioural floor and gives organisers power to act quickly. The harder question is whether the public record makes the reporting, conflict and correction process legible without exposing the people it is meant to protect.
IETF
Murray Kucherawy and the DKIM Signature That Left the Tail Unsigned
The verifier returned `dkim=pass`. The message was therefore signed — but not necessarily all of it. One optional number can make both statements true: `l=` tells DKIM to stop hashing after a specified number of canonicalized body octets, while the reader may still see everything…
History
The Port Had a State. The Session Had Another: RFC 1316
An early network-management screen could make a character port look like a single thing: one connector, one status, one counter, perhaps one conspicuous command called reset. RFC 1316, published in 1992, refused that convenience. Its Character MIB placed a port, the sessions…
CASE FILE
The Echo Reached the Path. The Service Was Still Unproven.
An active SFC probe can establish something useful and narrow: that a deliberately formed test was processed along a specified part of a service-function path. It cannot, on its own, turn that observation into evidence that production traffic received the promised treatment.
History
The Interface Was Down. The Circuits Had Not All Failed: RFC 1315
A network manager needs to know what a measurement actually names before using it to explain an outage. RFC 1315, the 1992 Frame Relay DTE MIB, offers an unusually clear historical example. It places many virtual connections under one physical Frame Relay interface, then defines…
History
The Trap Was Defined. No Event Had Been Observed: RFC 1215
A network trap can look like an event before anything has happened. Its enterprise, variables, description and number may already sit neatly in a management module. RFC 1215 made that definition concise in 1991. It also left a crucial boundary in plain sight: the macro expanded…
CASE FILE
The OID Named the Key Package. It Did Not Authorize Its Use: RFC 9939
The package parsed cleanly and its CMS content-type OID was correct. That establishes a useful syntactic fact. It does not establish who controls the private key, whether it was recovered safely, or whether any later use is permitted.
IETF
John Klensin and the SMTP Reply That Accepted Responsibility, Not Delivery
The sending server sees `250 OK`, removes a message from its queue and calls the transaction complete. That can be correct. Calling the message delivered is not. In SMTP, the final positive reply moves custody to a new operator; the destination still has to be reached, and…
CASE FILE
SC-106 Names Non-Web Relying Parties. The SCWG Charter Names Browsers
Draft pull request 679 puts SDKs, embedded systems, enterprise middleware and operating-system trust stores inside its case for ML-DSA certificates. The Server Certificate Working Group’s voting rules put browsers at the centre. That mismatch does not invalidate the proposal. It…
History
The File Was Not a Fax Call: RFC 1314
In April 1992, the Internet Engineering Task Force made a modest but consequential distinction for black-and-white documents. A scanned page could be a file before it became a transmission, a printout, a fax, or something that a person had seen. RFC 1314 gave that file a common…
NPNOG
Seats Available: How npNOG Allocates Limited Workshop Capacity
npNOG's workshop pages reveal a simple access rule built around timing and finite seats. What that rule shows—and what the public record still cannot prove.
CASE FILE
The ACK Allowed Another Send. The Path Had Not Recovered: RFC 9937
An ACK arrived, the sender released another segment, and the recovery graph improved. RFC 9937 makes that local arithmetic more disciplined. It does not turn the graph into a path-capacity certificate or a service-recovery declaration.
IETF
RATS Has a Two-Clock Fix in Source. Version 09 Still Faces Last Call
One public comment changed the RATS Endorsements editor's source in four days. The change separates the period for which an endorsement's content applies from the period in which its signer remains acceptable. That is a real result of IETF review. It is not yet a result of the…
History
The Address Bounced. The Main List Might Not Contain It: RFC 1211
A failed address sounds like a simple list-maintenance fact: find the subscriber and remove the line. RFC 1211 documented the harder 1991 reality. The failing mailbox might not appear in the main list at all. One exploder entry could conceal another organisation’s membership…
CASE FILE
The Content Type Was YAML. The Decision Still Had to Be Local.
`application/yaml` tells a receiver what kind of serialization has arrived. It does not tell that receiver what it may safely believe, retain or do next.
History
The Server Sent Plus. The Message Had Not Been Seen: RFC 1312
A short message service can return a positive acknowledgement and still leave the last important question unanswered: what, exactly, was positive? RFC 1312's Message Send Protocol 2 answered with unusual clarity. A server might have successfully invoked a local message-delivery…
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