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,702 articles
History
A Common Incident Object Was Not a Common Verdict: RFC 3067
RFC 3067 imagined a security-incident report that could cross organisational and national boundaries without losing the distinctions needed to act. Its strongest insight was not that every response team should reach the same conclusion. It was that they needed a common entity…
History
The Tag Named the Content. It Could Not Certify Understanding: RFC 3066
In January 2001, RFC 3066 gave Internet protocols a compact way to say which human language an information entity used. It also drew a line that systems still cross too casually: a valid label can guide selection and processing, but it cannot testify that a person will understand…
Number Resource Society
The Recognition Side of the Draft RIR Governance Document: Six Criteria, One Pipeline, and a Two-Thirds Gate
Before anyone can join the club, the club must first define who counts as a member, what a candidate must prove, who examines the proof, and who holds the final veto. That is precisely what Article 3 of the *Governance Document for the Recognition, Operation, and Derecognition of…
IETF
The Exporter Produced 128 Bytes. It Did Not Bind the Token Holder to the Tunnel.
Revision 04 of EAP-PPT deletes an output that looked like inner-method keying material. The correction matters because a tunnel exporter can produce bytes without proving that the same party both terminated the tunnel and possessed the bearer token.
IETF
The Tag Froze the Module. It Did Not Freeze Consensus
A proposed IETF workflow would move YANG source out of RFC prose and point publication at an exact repository tag. That can settle which bytes were reviewed. It cannot, on its own, settle who agreed, what was shipped, what a device loaded or whether the network behaved as…
Story
The Ladder That Has Not Fired: What the Public Record Shows About Enforcement on the Svea Abuse-Contact Surface
When Svea Ekonomi AB merged into Svea Bank AB on 3 January 2022, the RIPE Database inherited a problem that no merger clause can settle by itself: the group's registered abuse-contact surface. Nearly four years later, that surface still carries the dissolved company's identity in…
Number Resource Society
Inside Article 6: How the Draft RIR Governance Document Would Make Derecognition Possible — and Unilateral Removal Impossible
The Governance Document for the Recognition, Operation, and Derecognition of Regional Internet Registries, delivered to the NRO Executive Council as a recommended draft on 28 July 2026, is best read not as a charter for expanding ICANN's power but as a procedure whose every step…
History
The Gateway Owned the Milliseconds. The Call Agent Still Owned the Call: RFC 3064
When circuit telephony met packet control, distance became a design constraint. RFC 3064 put reactions measured in tens of milliseconds beside the wire, inside the media gateway. It did not surrender the larger decision: the Call Agent still decided what the call meant, and a…
CASE FILE
GoCodeIT Support: a role label, a corporation, and where accountability actually sits
GoCodeIT Support is a name that looks like a person in the registry, but the public evidence shows it is an institutional contact role — and the accountability behind it sits with a company in two RIRs at once.
History
Labels Waited for the Thread to Rewind: RFC 3063
In a changing MPLS network, a route could point around a loop before a label-switched path was ready. RFC 3063 proposed a way to make the label wait: send a short-lived, colored control thread downstream, and do not advertise the mapping until that thread has returned through a…
IETF
The Sender Received a Standard CNP. It Could Not See What the Proxy Dropped.
A new congestion-notification proposal gives old RoCEv2 senders a compatible warning through a proxy. Compatibility solves the packet-format problem; it does not preserve the whole evidence chain from congestion point to sender.
Story
How AFRINIC's Board Was Rebuilt: The Bylaws Provisions That Actually Governed the 2025 Election
When AfriNIC Ltd — the regional internet registry for Africa, better known as AFRINIC — entered receivership, its governing crisis became a test of which written rules actually bind an institution when its board is empty. The answer, on the evidence of the 2025 election record…
History
The Missing Extension Was Not an Empty Answer: RFC 3059
RFC 3059 tried to save a round trip in service discovery: return each service URL with its attributes in the same reply. Its most durable lesson lies in the path where that optimization disappeared. No extension did not mean “no attributes.” It meant the client still owed the…
IETF
The Prompt Listed the Rules. The Device Change Needed a Different Receipt
An Internet-Draft on autonomous network management makes the essential distinction: telling an AI what it may do is not the same as enforcing those limits. For operators, the durable proof is the policy snapshot actually evaluated at execution, joined to the device change and its…
History
The Password Had No Directory Entry to Change: RFC 3062
In 2001, LDAP's ordinary edit operation could not reach every password. RFC 3062 introduced a separate password-change request that could target a session's user or a non-DN identity, even when the credential lived outside the directory. Its success rule was strict; its view of…
Number Resource Society
Recognition Without Unanimity: How the Second Draft of the RIR Governance Document Rewrites the RIR Lifecycle
When the Number Resource Organization's Number Council published the second draft of the RIR Governance Document on 28 August 2025, it did more than tidy the language of a consultation paper. The revision quietly rebuilt the machinery that decides which organisations are allowed…
CASE FILE
The Chain That Was Touched: Where Attention Fell in the Svea Abuse-Contact Record
The Chain That Was Touched: Where Attention Fell in the Svea Abuse-Contact Record intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that…
History
The OID Made IDEA Encodable. It Did Not Make the Cipher Available: RFC 3058
RFC 3058 gave IDEA two precise names inside CMS and a reproducible way to wrap a content key. It solved the problem of how conforming software should represent the cipher. It did not install IDEA at either end, grant permission to use it, select it for a message, or prove that…
IETF
Every Checkpoint Verified. The Producer Could Still Have Forked the Log.
A September 2026 Internet-Draft proposes a private append-only log whose compact checkpoints can be witnessed without publishing the records. Its hardest lesson is that a cryptographically consistent history can still be only one of two histories.
History
The Model Could Describe the Rule. It Left the Result to Devices: RFC 3060
RFC 3060 gave policy systems a shared vocabulary of groups, rules, conditions and actions. It did not give every router one shared interpreter. The standard could describe when a rule applied and even mark an action order as mandatory or recommended, while leaving the algorithm…
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