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
7,970 articles
CASE FILE
The Registrant Was Abroad; the Dot-Com Registry Was in Virginia: CNN v CNNews.com
The Registrant Was Abroad; the Dot-Com Registry Was in Virginia: CNN v CNNews.com intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that…
Story
RIPE NCC’s RDAP Country Code Does Not Geolocate the Network
A two-letter country code looks ready for a map. In a RIPE NCC RDAP network entity, however, it is a registration field—not a set of coordinates and not live evidence of where routers, users, traffic or services are located.
IETF
The Link Is Not the Location: RFC 9877 and RDAP Geofeed Control
A geofeed link tells a client where to look; it does not turn every location claim in that file into verified truth. RFC 9877 makes RDAP a scoped discovery and authority signal, with controls that keep lookup scope, freshness, authenticity and privacy separate.
Story
APNIC’s RDAP objectClassName Defines a Schema Class, Not a Network Role
The label `ip network` appears near the top of an APNIC RDAP response. It is easy to read it as a description of what an organisation does. Its real purpose is narrower and more useful: it tells software which RDAP entity schema it is processing.
Number Resource Society
An IPv4 Transfer Pre-Approval Needs a Registration-and-Expiry Ledger
An IPv4 transfer pre-approval answers a narrow question: how much address space a recipient may qualify to receive during a defined period. It does not identify a source, complete a transfer or prove that the registry has changed.
Story
APNIC prop-170 Must Price the Space Between IPv6 Need and Nibble Alignment
A technically valid IPv6 prefix is not always an easy unit to operate. APNIC prop-170 would let an LIR request the smallest nibble-aligned allocation that satisfies an already validated need. The proposal promises cleaner plans without abandoning needs-based allocation; its…
History
The Window That Refused to Open One Byte at a Time: TCP Silly Window Syndrome Avoidance
A TCP receiver can have room for more data without advertising that room immediately. That deliberate silence prevents a small permission from becoming a self-repeating stream of small packets.
NANOG
Membership Is a Mandate With Edges
NANOG membership creates real authority inside the association. It does not turn a corporate electorate into every network operator in North America.
IETF
A Two-Byte Number Can Lie About the Payload: RFC 9876 and CoAP Registry Control
CoAP defines Content-Format as a small integer that identifies a payload's media type and any content coding. RFC 9876 makes the registration procedure behind that integer stricter, because the code point is meaningful only when its media type, parameters, coding and semantics…
Number Resource Society
A Number-Resource Policy Decision Needs an Adoption-and-Implementation Ledger
A consensus announcement is useful evidence, but it is not by itself a complete answer to what text applies or when an operational change took effect.
Story
ARIN’s RDAP Remarks Qualify This Object, Not Every Registry Record
Human-readable text inside an RDAP response can look like a general registry instruction. Its location matters. In ARIN’s live entity response, Registration Comments sit inside a particular entity entity, while service terms and reporting notices occupy the response’s top level.
BDNOG
bdNOG Publishes Who Oversees Its Executive Committee, Not How
bdNOG’s public governance pages draw a clean line: the Board is the highest authority, while the Executive Committee (EC) manages the community’s work. The Board page says it approves yearly activities and holds the EC accountable. The EC page names the operating committee and…
IETF
A Resolver Can Choose Encryption Before DNS Operators Coordinate
Encryption between a user and a recursive DNS resolver does not protect the next hop. The resolver may still send the resulting query in cleartext to an authoritative server, exposing another part of the path to passive observation. RFC 9539 proposes an experimental compromise…
History
The Window That Closed Without Ending the Connection: TCP Persist
When a TCP receiver says it has no room left, the sender stops sending ordinary data. The harder question is how either side escapes that pause if the one message announcing new room never arrives.
IETF
One Header Can Invalidate a Whole Site Section: RFC 9875 and HTTP Cache Groups
A response can label related stored responses inside one cache and one URI origin, while a later unsafe request can name those labels for possible invalidation. The useful boundary is local coordination, not a promise of synchronization across caches, CDNs, or origins.
CASE FILE
The Certificate Challenge Crossed the Delay. Authority Did Not: RFC 9891
RFC 9891 carries an ACME proof through a delay-tolerant network, but it carefully stops the proof at control of a Node ID during one policy-bound exchange. Everything beyond that boundary still needs its own evidence.
Story
LACNIC’s RDAP Self Link Locates the Record, Not the Network’s Serving Infrastructure
A URL inside a registry response can look like an infrastructure clue. In LACNIC’s RDAP output, however, `rel: self` tells a client where to retrieve the registration entity; it does not say where the registered network’s traffic, applications or authoritative services run.
Story
AFRINIC Named Five Fellowship Recipients from a Pool Above 1,700. The Selection Record Is Not Public
AFRINIC’s announcement identifies five people and describes a highly competitive programme. It does not publish the exact applicant total, the scoring method, the assessors or the decision record, so the notice proves an outcome without making the selection reproducible.
IETF
Catalog Zones Turn a DNS Member List into Fleet-Wide Provisioning Authority
An empty file is usually absence. An empty DNS catalog can be an instruction. If a generator accidentally publishes a catalog without its members, every consumer that originally provisioned those zones from that catalog may begin removing them and their associated state. RFC 9432…
History
The Number Made Harder for an Off-Path Attacker to Predict: TCP Initial Sequence Numbers
A TCP connection begins by exchanging numbers. The security change was not to hide that exchange, but to stop one visible number from revealing the next connection's starting point.
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