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 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,331 articles
Story
APNIC prop-164 Turns Smaller IPv6 Allocations into a Reservation Test
APNIC prop-164 would let account holders begin with IPv6 allocations smaller than `/32` while preserving room for growth. The proposal may improve Whois and RDAP accuracy, but its durable test is whether reserved address space becomes a visible, reviewable registry commitment…
Story
ARIN’s Alternate Whois Link Is a Substitute View, Not Independent Corroboration
One ARIN RDAP record points sideways to ARIN’s older Whois REST service. That link is useful, but it does not turn two views from the same registry into two independent witnesses.
IETF
The Algorithm Name Is Not the Certificate Profile: RFC 9881 and ML-DSA in PKIX
The Algorithm Name Is Not the Certificate Profile: RFC 9881 and ML-DSA in PKIX 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…
AFNOG
AfNOG Publishes Mailing-List Rules, Not the Moderation Procedure Behind Them
AfNOG’s mailing-list page sets clear expectations for a technical community: keep discussion operational, avoid disrespect, and do not use the list for blatant product marketing. The published page establishes the rules. It does not explain the procedure used when a post is…
Number Resource Society
An RPKI Publication Point Needs a Commit-to-Visibility Ledger
An RPKI publication server can accept an authenticated update atomically while relying parties still hold an earlier repository view. That is not necessarily a contradiction or a failure. It is a boundary between different authorities, protocols and observation times. A useful…
IETF
A Registry TTL Is Policy State, Not a Live DNS Observation
RFC 10037 lets a registry publish configured DNS time-to-live values through RDAP. That sounds like a small JSON extension. Its more important effect is to expose a piece of registry policy without pretending that a registration-data service is watching the live DNS. The…
IETF
A Data Model Is Not a Wire Contract: RFC 9880 and SDF Protocol-Binding Boundaries
Two implementations can claim the same Thing model yet disagree on the wire: one chooses a URL and JSON payload convention, while the other expects a numeric identifier and different invocation rules. The gap appears when a protocol binding was implicit rather than versioned and…
Story
LACNIC’s RDAP Name Is a Registration Label, Not a Legal or Routing Identity
A field called `name` invites more confidence than it deserves. In LACNIC’s live RDAP record for `200.0.0.0/21`, the value is simply the address interval written as a label. It identifies a registration record; it does not settle who legally owns the addresses or who operates the…
Story
APNIC's Larger IPv4 Delegations Need a Queue Rule Before a Bigger Ceiling
APNIC's prop-168 would let eligible account holders grow toward an aggregated /22 while proposing a separate /12 transition reserve. The proposal defines who may ask and how much they may receive; its own scarcity arithmetic shows why it must also define who goes first when…
History
The Probe That Could Not Declare an Idle Peer Dead: TCP Keep-Alives
An idle TCP connection can be quiet without being broken. Keep-alive probing was designed to ask whether the peer's transport state could still answer, while denying any single unanswered probe the authority to declare that state dead.
IETF
A Hybrid SSH Key Exchange Turns Algorithm Negotiation into a Migration Boundary
Installing post-quantum code does not mean an SSH session used it. RFC 10042 defines three hybrid methods that combine ML-KEM with an established elliptic-curve exchange. The protection becomes real only when both peers offer the same method, negotiation selects it, both…
IETF
The Integrity Check Has Its Own Parameters: RFC 9879 and PBMAC1 in PKCS #12
A PKCS #12 exchange can fail at the integrity boundary when one implementation reads compatibility-shaped legacy fields while another follows PBMAC1’s nested parameters. The two sides can then disagree about the password-derived key, the MAC scheme, or the authenticated bytes.
IDNOG
IDNOG Publishes Sponsorship Tiers and Talk Review, Not the Boundary Between Them
IDNOG’s public record shows two systems around the same conference. One groups commercial supporters into named sponsorship tiers. The other assigns presentation review to a volunteer Programme Committee. What the reviewed material does not show is the rule separating those…
Story
AFRINIC’s RDAP Handle Is a Registry Reference, Not a Global Network Identity
The string `196.216.2.0 - 196.216.3.255` looks like an address range because it is one. In AFRINIC’s current RDAP response, however, that same string also serves as the entity’s `handle`. Its meaning there is narrower than the network identity that downstream systems may be…
Number Resource Society
An ASN Transfer Needs a Routing-Identity Handover Ledger
An ASN Transfer Needs a Routing-Identity Handover Ledger 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 follow. The Number…
NANOG
What NANOG's Public Record Says—and Does Not Say—About Recusal
Technical peer review works because reviewers know the field. That is also why conflicts cannot be treated as an exotic exception. NANOG's Program Committee evaluates proposed talks. As a bounded governance premise, any specialised technical committee may bring reviewers and…
Story
ARIN's RDAP Transition Needs Evidence at Three Different Exit Gates
ARIN wants one standardized directory protocol in place of three older services. The destination is coherent; the operational test is whether Whois-RWS, RWhois and Port 43 can each leave on evidence suited to the users and dependencies they actually carry.
History
The Acknowledgment That Waited for a Second Segment: TCP Delayed ACKs
TCP does not always answer one received data segment with one immediate acknowledgment. The receiver may wait briefly, but that silence is governed by a second-segment threshold, a timer, and exceptions that preserve loss evidence.
IETF
QNAME Minimisation Is a Query-Sequence Contract, Not a Privacy Switch
A resolver may advertise QNAME minimisation while exposing very different names, costs and failure modes from one lookup to the next. The feature matters only when operators can reconstruct the bounded sequence produced by delegation knowledge, cache state and negative proofs.
IETF
An SRv6 Locator Lease Makes DHCPv6 Part of the Routing Control Plane
An SRv6 locator is the address-space foundation from which a segment endpoint creates SIDs. RFC 10038 allows that foundation to arrive as a DHCPv6 lease. The convenience is real, but so is the transfer of authority: pool selection, lease renewal, route installation and withdrawal…
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