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,975 articles
Story
RIPE’s Status Field Is a Registry Class, Not a Network Health Check
A single line in an address record can look like an operational verdict. In the RIPE Database, it is nothing of the kind: `status` locates an IPv4 record inside a policy hierarchy, while routing and reachability must be observed elsewhere.
CASE FILE
The Certificates Did Not Expire: Chrome's Entrust Cutoff Turned Trust Into an Operating Licence
The decisive field was not the expiry date printed inside a TLS certificate. It was the timestamp proving when that certificate entered the public record—and whether Chrome still accepted the authority behind it at that moment.
History
Eight Bytes the Endpoints Could Not Negotiate Away
A PPPoE session could open successfully without carrying the packet size that justified opening it. The extension that addressed this problem separated permission, negotiation and a size-sensitive fallback. Its historical importance lay in a broadband migration: when the session…
Story
At LACNIC, a New ISP Must Prove Need Before It Can Pay $8,000 for IPv4
LACNIC’s rules ask a first-time operator to show that customers and equipment already justify an address block. Exhaustion then sends that approved need into a private market. The rule is neutral on paper; the sequence is not neutral between a network starting from zero and one…
Story
AFRINIC's compliance-dashboard draft logs six states while leaving critical-infrastructure exceptions and enforcement receipts to later procedure
AFRINIC’s proposal could turn compliance data into an early-warning service for members. Its difficulty begins where the dashboard stops: the draft names signals and states, but leaves the human finding, enforcement rule, exception, appeal and rollback to procedures that do not…
NPNOG
Who opens the room? What npNOG-10's welcome order can—and cannot—prove
The first twenty minutes of a conference can reveal institutional relationships. They cannot, without supporting records, tell us who held the decisive authority.
Story
AFRINIC’s petition proposal needs a receipt for every step from Board silence to implementation
AFRINIC’s Draft01 responds to a real institutional failure: a registry cannot leave policy work frozen whenever its Board cannot act. But its alternative route—from fifteen supporters to a new staff analysis and then deemed ratification—still lacks the evidence controls that…
Number Resource Society
The Support Inbox Needs a Case Clock
An email can leave a member's system and still reveal nothing about whether the receiving institution accepted the matter, assigned it or decided when to respond. For a membership organisation that operates in the number-resource governance field, that gap is not solved by…
History
The Hint That Had to Be Replaced by an Answer: DNS Root Priming
A recursive resolver begins with an awkward form of knowledge: enough addresses to reach the DNS root, but no current root data in its cache. Priming is the small exchange that turns that inherited hint into an authoritative, expiring answer.
History
The Forwarding Evidence an IP Error Left Out
The router removed the labels before it prepared the error. What remained could identify the original IP conversation while omitting the state that had governed its passage through the network. Adding that state to ICMP made a report more useful. It did not make the report a…
IETF
The secret server name still needs a public front door: ECH’s new privacy boundary
Encrypted ClientHello gives a TLS connection two introductions: one the network may see, and one only the service can open. That is a real privacy gain, but it is not disappearance. The destination’s protection now depends on DNS configuration, a shared front door, key rotation…
Story
ARIN’s RDAP Bottom Search Is a Coverage Answer, Not a Leaf List
One query for a `/21` returns a direct `/22` allocation and an administrative `/8`. The result looks upside down only if `rdap-bottom` is mistaken for a list of descendants; its real job is to account for registry coverage.
ICANN
One Portal, No Clock: Who Actually Grants Zone-File Access?
CZDS lets a researcher ask many generic top-level-domain registries for zone files from one place. The common doorway is easy to mistake for a common decision. It is neither automatic access nor a single permission desk.
ICANN
The Forged Letter That Moved Sex.com: Kremen v. Cohen and Network Solutions
A forged instruction did not move a physical entity. It changed the authoritative registration record for a domain name—and forced a federal appellate court to ask what, exactly, the registrant controlled.
Story
LACNIC’s Last Waitlist Applicant Faces 12 Years for at Most 1,024 Addresses
LACNIC’s IPv4 queue does not preserve a block for every approved applicant. It preserves an identity-bound place in a sequence whose supply, order, final approval and address quality remain unsettled until recovered space is actually released.
History
The Number That Came Back Unchanged: PPP’s Magic-Number
A PPP endpoint could receive the exact number it had just sent and be entirely satisfied. It could receive the same number in another kind of packet and suspect a loop. The distinction was not in the four bytes. It was in the action those bytes belonged to—and in the small…
ICANN
A Proxy Clause Without a Private Enforcer: Balsam v Tucows
Daniel Balsam had a seven-figure judgment and a contract clause that seemed to point straight at the missing identity. What he did not have was the legal position from which to enforce that clause against the registrar.
Story
AFRINIC Has Rebuilt GovCom. Its Advice Still Needs a Public Return Path
AFRINIC’s 17 August announcement names a complete Governance Committee with elected, Board-appointed and non-voting entities. The next accountability test is not who occupies each chair, but whether every formal request, opinion, dissent and institutional response leaves a trace…
Story
ARIN’s NET Route List Stops at the Direct Allocation
An empty collection can look decisive until the query boundary is drawn. In ARIN’s routing-registry API, the ordinary NET route list ends at the direct registration; the downstream tree belongs to a different request.
ICANN
A Domain Name in a Receiver’s Hands: Office Depot v Zuccarini
The judgment was entered in Florida, the debtor lived elsewhere, the registrars were scattered across three countries, and the `.com` registry sat in Northern California. To collect the debt, the Ninth Circuit had to decide where an intangible domain name could be found.
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