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,434 articles
IETF
Mark Crispin and the \Seen Flag That Did Not Prove a Human Read the Message
An email turns from bold to ordinary type, and a shared mailbox quietly acquires a fact: `\Seen`. The interface calls the message read. The server can prove that a flag changed. Between those statements sits the question Mark Crispin’s IMAP makes unavoidable: what, exactly…
IETF
A NAT64 Mapping Is Not a Filtering Policy
A repeatable public tuple can prove how a stateful NAT64 translator allocates an address and port. It cannot prove which IPv4 sources are allowed to use that state on the way back. Treating those two facts as one control turns an interoperability test into a security verdict it…
ICANN
IAB Reappoints David Lawrence; Its ICANN Handoff Notices Disagree
Three public notices now describe one liaison transition. The first put ICANN87 in November. The second put it in October. The third named David Lawrence for another term but did not say when that term takes effect. ICANN’s own calendar and Bylaws resolve most of the puzzle, yet…
ICANN
At ccNSO, Nominating a Colleague Can Still Be Self-Nomination
Five Council seats are entering selection. The rules distinguish an institution putting someone forward from support that comes from outside it.
IETF
The disclosure rule that does not travel alone
An incident report can inherit its sharing conditions from the structure around it. Turning that report into a convenient extract is therefore a policy decision, even when none of its factual fields changes.
History
The Switch Offered a Shortcut. The Router Could Refuse: RFC 1953
In RFC 1953, the faster path began as a neighbor's request, not a command. A downstream node chose a label from its own local space and asked the upstream node to attach it to a defined IP flow. The upstream node could ignore the request. Even acceptance lasted only for a stated…
CASE FILE
IGF’s 80-Workshop Baseline Has Two Weighting Stages—and a Human Decision After Them
The September programme papers make selection more intelligible. They also show why a ranking, a recommended slate and an approved agenda need separate records.
Story
AFRINIC's 8 September Snapshot Returned Four Old Resources to “Allocated.” It Cannot Say Why
Three ASNs and one /19 crossed AFRINIC’s public boundary together between two signed daily files. Their 2006 dates came back with them. That is evidence of a current state change, not evidence of a new allocation—and the distinction deserves a small public receipt.
IETF
The cost of a stateless relay lives elsewhere
A PANA relay can avoid keeping a record for every client without making network admission cheap, ownerless or continuously available. The useful economy is a placement decision: which component remembers the path, which validates the exchange, and which team must restore it.
IETF
One Operator Does Not Make One SRv6 Trusted Domain
A merger puts two routing estates beneath one legal owner. The new diagram draws a single box around them, and an automation team proposes removing the filters at the seam. The diagram may be administratively correct. It proves nothing about whether the two SRv6 instances share…
IETF
Jonathan Rosenberg and the OPEN Status That Belonged to a Service, Not a Person
A green dot glows beside a name. A message goes unanswered. The apparent contradiction disappears once the dot is read at the level the presence standards actually describe: a communications service may be open to receiving a message while the human remains absent, occupied…
IETF
IPv6 Neighbor Discovery Puts Three Actions Behind One Boolean
A boolean is the smallest possible management choice. In the IPv6 Neighbor Discovery YANG model now in IETF Last Call, one such switch can authorize a much larger sequence: record a duplicate-address event, discard the triggering message and block the host that sent it. The draft…
History
The File Ended, Then Continued: RFC 1952 and Gzip's Member Boundary
A `.gz` filename suggests one entity. RFC 1952 describes something more interesting: a procession of self-closing members. Finish one, place another immediately after it, and a decompressor can continue as though the file had acquired a new chapter. The old compressed bytes need…
Story
LACNIC’s Abuse-Contact Lockout Sits Outside the Policy Manual
LACNIC’s policy manual says when an abuse contact becomes noncompliant. A separate help page says the consequence is blocked access to MiLACNIC. The missing entity is not another reminder email. It is the public record that joins a rule to the administrative control it activates.
IETF
A migration measured in readable objects
Moving an old MIB into YANG can make a device easier to observe without moving the obligations attached to changing it. RFC 6643 makes that limited bargain explicit. The risk begins when a migration programme buys the first capability and declares the second complete.
Story
DATAMATIX and AS210973: What Public Routing Evidence Can—and Cannot—Prove
DATAMATIX and AS210973: What Public Routing Evidence Can—and Cannot—Prove intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may…
ICANN
ICANN's NomCom Invites Process Advice, Not Candidate Testimonials
The 2027 consultation puts contributors' views on the public record. It does not turn the selection process into an endorsement campaign.
IETF
Factory defaults can remove the way back
A factory reset can do precisely what its specification requires and still leave an operator unable to manage the device. RFC 8808 separates a return to preset configuration from two outcomes that the phrase “back to factory” tends to imply: a usable route back in, and data that…
IETF
A Cleared Incident Does Not Prove Which Command Cleared It
An incident client sends one `incident-resolve` request containing several incident numbers. Later, separate notifications arrive. Two records now say `cleared`; another remains `updated`. The network view is useful, but the decisive question has vanished between the command and…
History
The Key Centre Disappeared into the Tree. Its Authority Did Not: RFC 1949
Scaling usually sounds like subtraction: remove the bottleneck, spread the work, let the network carry the rest. RFC 1949 did spread multicast key distribution, but it could not subtract trust. By letting authenticated tree nodes pass group secrets and authorise later joins, the…
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