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,844 articles
Story
AFRINIC promises a validation meeting before the bylaws vote; the method is the test
The BRC must hold a stakeholder-validation meeting before constitutional amendments reach an AGMM or SGMM. Unless the method is public, “validated” will describe an event without proving what it tested.
CASE FILE
The Speaker Was in the Session, Not the Path: IXP Route Servers and the Authority to Broker Reachability
The BGP session was established to one system. The route began with another network's AS number. Its next hop named a third address on the exchange fabric, and the packets never crossed the machine that had delivered the UPDATE. Nothing was malformed. The apparent contradiction…
Story
LACNIC’s Election Commission Can Assign a Candidate to a Country They Are Not a Citizen Of
In 2025, LACNIC published an Electoral Commission candidate as a citizen of Uruguay and a resident of Brazil, then ruled that his long residence and economic activity meant he would occupy Brazil’s country slot. The official result and current roster continue to list him as…
History
The Second Connection Asked Who Owned the First: How IDENT Bounded a Username's Authority
A server has already accepted one TCP connection when it opens another in the opposite direction. On that second connection it sends two port numbers to the first host and asks a narrow question: which local user owns the first connection? IDENT made that answer useful for logs.…
CASE FILE
An RFC Number Does Not Mean the IETF Approved It
A compliance register that records only “RFC 8729” looks precise. It is not. The number identifies a durable document, but it conceals that this particular RFC is an IAB-stream informational statement rather than an Internet Standard. When a single column makes every RFC look…
Story
AFRINIC’s bylaws committee can recommend; the Board controls the gate to members
The consultation has ended, but consultation is not authority. AFRINIC’s own rules place the decisive pre-member gate with the institution that appointed the review committee.
History
The Time Packet That Was Not Time: How NTP Kiss-o'-Death Made Refusal Actionable
The reply fits the familiar NTP shape and even belongs to a request the client just sent. Yet its timestamps must not adjust a clock. Stratum 0 and the four letters `RATE` turn the packet into something else: a server's bounded request for less traffic, delivered inside the…
CASE FILE
The Request Said Urgent. The Scheduler Still Decided: HTTP Priorities and the Authority to Allocate Scarce Delivery
A browser can call a hero image urgent, an origin can prefer the font, and a CDN can see both through a different connection map. RFC 9218 lets each express useful information. It does not let any of them annex the scheduler that finally allocates the next byte.
Story
AFRINIC consultation closes; the response ledger is the next test
The endpoint has expired. AFRINIC’s committee rules now point to one accountability test: show what came in and how each item was handled.
Story
AFRINIC's “all legal costs” resolution still lacks closure
A 2022 Board record explains the urgent defence. It does not show how the unlimited-looking undertaking was classified, spent or closed.
History
The Prefix That Tried to Make IPv6 Automatic: 6to4 and 2002::/16
6to4 offered a seductive bargain: turn an existing IPv4 address into an IPv6 network and let relays complete the journey. The address trick worked as specified. The operational responsibility did not assemble itself around it.
CASE FILE
The “Obsoletes” Line Is Not a Remote Kill Switch
When RFC 9113 replaced the earlier HTTP/2 specification, the catalogue moved and selected registry references moved with it. A live connection did not. It still negotiated `h2`; no standards editor reached into a server, removed old code or accepted the outage risk on an…
ICANN
The Four-Hour Transfer Contact That Cannot Reverse the Transfer
The Four-Hour Transfer Contact That Cannot Reverse the Transfer 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…
History
The File Did Not Come From Port 69: How TFTP Bound a Transfer to Chosen Endpoints
A packet trace of a correct TFTP read begins with a small surprise. The request goes to UDP port 69, but the first block of the file comes back from another port. That change is neither drift nor a second service. It is the moment the protocol replaces a public door with a…
JPNOG
Green, Up, and Running at a Fraction of Normal: JANOG58's Rack-Scale Acceptance Gap
The LED was green. Link Status was UP. Optical power sat inside the normal range. An NCCL check across all links nevertheless found one connection delivering only an unspecified fraction of normal throughput. SoftBank's JANOG58 account is a compact lesson in the difference…
CASE FILE
The Resolver Named the Failure. It Did Not Prove the Cause: Extended DNS Errors and the Authority of Diagnosis
Extended DNS Errors can turn an opaque DNS failure into a useful account of what one resolver observed. The gain is operational clarity. The danger begins when a dashboard promotes that account into proven cause, assigned blame or permission to weaken the control that produced…
Story
AFRINIC Took Identity Proofing to Kigali. The Registry Handoff Needs a Receipt
A government ID can cross a conference desk in seconds. A registry change must remain explainable long after the badge, booth and meeting room have disappeared. AFRINIC's AfPIF service offer joined those two moments; the missing public entity is the receipt that keeps them…
History
The Question SMTP Learned Not to Answer: How VRFY Separated Address Acceptance from Directory Disclosure
In 1982, a remote machine could ask an SMTP server to `VRFY Smith` and receive Fred Smith’s full name and mailbox. The command was useful because it made a mail problem inspectable. It was dangerous for the same reason: a transport service had become a public directory, one…
Story
AFRINIC promises representation before publishing the method
An open, anonymous consultation may find useful priorities. It cannot become evidence of member consent merely because the response count grows.
APRICOT
One Forwarder, 64,000 Subscribers: The Failure Domain Inside APRICOT 2026's x86 BNG
One 144-core processor, one packet forwarder and 64,000 subscriber states: the most revealing number in 5x9 Networks' APRICOT 2026 presentation is not 1.6 Tbps. It is the number of access sessions brought into one execution domain while repeated cache state was removed.
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