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,374 articles
IETF
Carsten Bormann and the Token That Matched a Reply, Not a Person
A field small enough to fit inside a constrained message can still be asked to carry too much institutional meaning. CoAP’s design offers a better discipline: give each compact identifier one narrow job, preserve the surrounding evidence, and refuse to turn correlation into…
Story
LACNIC's Delegation File Declares 49,894 Records. It Contains 48,214
A daily file built for machines fails the counting rule printed in its own specification, while its automatic alias and its dated signature offer two different paths to trust. The discrepancy is not evidence of missing Internet resources. It is a test of whether a registry…
Story
LACNIC’s Revocation List Shows a /23 in 2023 and a Nested /24 in 2026
The same first address appears twice in LACNIC’s public revoked-resources table, first as a 512-address block and three years later as its lower 256-address half. That visual repetition invites the wrong question: was the same resource revoked twice? Six official daily snapshots…
History
The Number That Said Goodbye So the Stream Could Continue: How RTP Resolved SSRC Collisions
Two live sources could enter one RTP session carrying the same 32-bit number. The protocol did not ask a central registry to decide who owned it. The source that found its own number in conflict sent goodbye for that label, selected an unused replacement and kept the media…
CASE FILE
The Server Issued a Locator. The Network Had Not Yet Accepted the Route: RFC 10038 and the Authority to Allocate SRv6 Reachability
A DHCPv6 Reply can make an SRv6 locator administratively real in a few fields: who received it, how it is divided and when it expires. The packet path is harder. A route still has to be installed, advertised, selected, programmed, filtered and joined to a local SID behavior. RFC…
CASE FILE
Internet Society Does Not Track Attendance Where Much Board Work Happens
Internet Society expects trustees to attend every formal Board meeting and records who was present, excused or absent. Its current policy draws a different line around informal monthly meetings: attendance is not tracked even though, in the organisation's own words, a significant…
IETF
A Temporary IANA Registry Needs More Than an Expiry Date
The IETF is considering a way to publish an IANA registry before the RFC that creates it has been approved. A visible two-year clock is a useful warning, but the harder governance question is what happens to the authority behind every entry when the registry is renewed, closed…
History
One XID, Two Executions: Why RPC Needed Memory Beyond the Reply Number
A remote call can be repeated with exactly the same number and still perform its work twice. ONC RPC made replies attributable; the harder task was preserving enough server-side history to say whether a retry was new.
CASE FILE
The Token Matched. Permission Still Had to Be Checked: WebDAV Lock Tokens and Write Authority
A WebDAV client can present the exact token for a live lock and still be correctly refused. That is not a contradiction in the protocol. It is the point at which a coordination marker stops and authority begins.
IETF
Fernando Gont and the First Fragment That Had to Name What Came Next
An IPv6 fragment can arrive first without explaining what the completed packet is for. The source address is visible, the destination is visible and the fragment offset says zero, yet the transport header a firewall needs may be hiding in a later piece. RFC 7112, co-authored by…
CASE FILE
The Registry Published the TTL. The Resolver Kept Its Own Clock: RFC 10037 and the Authority to Describe a DNS Change Window
A registry can now place a delegation TTL in an RDAP response, where an operator can read it without querying the DNS. The number is useful precisely because its authority is narrow. It describes what the registry database has provisioned; it does not reveal how many seconds…
History
The Answer That Supplied the Next Question: How SNMP Walked the MIB
An early network manager could know the name of a routing-table column without knowing a single row index. SNMP solved that ignorance with an unusual answer: return not the requested name, but the next accessible one. The reply became the next question, and an unknown inventory…
Story
ARIN Accepts Non-Human Service Accounts. Its Guide Still Says to Use an Individual Email
ARIN closed a four-year request on 29 July after removing the account-creation restriction on non-human service accounts. The implementation gives network operators a proper principal for automation. The public instructions have not yet made the same transition: the account guide…
CASE FILE
Internet Society Copied Five Succession Duties—and Changed Who Sits at the Table
Internet Society's Board abolished its Leadership Continuity Committee only after placing its five recurring duties inside the Compensation Committee's charter. The text survived. The chair, the CEO's status and the confidentiality perimeter did not remain the same, making plan…
CASE FILE
The Cache Told You It Was a Hit: Cache-Status and the Authority to Explain a Response
Cache-Status gives every cache in an HTTP path a common way to describe its part in delivering a response. That makes incidents easier to investigate, but it also creates a tempting mistake: treating the system's own explanation as if it were independent proof.
CASE FILE
The Message Was Accepted Before It Was Released: IETF's Mail Transition and the Authority to Hold, Rewrite and Relay
On 11 September, a first-time sender may hand a message to the IETF's mail system and receive an apparently ordinary SMTP outcome while the operational copy waits elsewhere for a challenge response. That gap between acceptance and release is the real story in the IETF's new email…
IETF
SECDISPATCH Has Closed. Its Outcomes Need a Transfer Record
The IETF has merged its separate Security Dispatch venue into a broader DISPATCH working group and will close the old mailing list. The new door is clear. The harder governance task is keeping every old proposal’s last recorded disposition attached to the right archive, authority…
Story
ARIN’s ROA Alerts Follow Deletion, Not the Change in Routing Authority
ARIN can commit several routing authorizations in one transaction, yet its documented alert boundary still follows a single verb: delete. Two public suggestions expose the resulting choice between inbox noise and silence. A safer design would report the net change once.
History
The Option Nobody Understood Still Said What to Do: How IPv6 Bounded Unknown Options
IPv6 gave future options a way to meet old software without leaving the consequence to guesswork. Three leading bits did not explain the new feature; they told an unknowing processor how far ignorance was allowed to travel.
IETF
Jen Linkova and the Five-Minute Clock That Kept IPv4 on Call
The most revealing part of RFC 8925 is not that a device can decline an IPv4 address. It is that the refusal expires. A client asks for DHCPv4 option 108, a configured server returns a waiting time, and the client pauses DHCPv4 only until that clock runs out or the network…
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