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,467 articles
History
The Report That Could Not Declare the Link Bad: How PPP Kept Quality Policy Local
A PPP peer could say how many packets and octets it had sent, and return what it had seen from the other direction. It could not make the protocol pronounce the link acceptable. Link-Quality-Reports standardized a shared accounting mechanism while leaving the threshold, the…
CASE FILE
The Token Never Reached JavaScript. The Command Still Ran: RFC 10017 and Browser OAuth Authority
RFC 10017 gives sensitive browser applications a clear architectural preference: keep OAuth tokens in a confidential Backend for Frontend. That closes several theft paths. It does not stop hostile code already running in the approved origin from asking the BFF to act. The…
ICANN
ICANN Confirms an SSE Error, Then Re-Evaluates. What Connects the Two Decisions?
An applicant can win an ICANN String Similarity Evaluation challenge without yet winning a new evaluation outcome. The missing link is the re-evaluation record: what the challenge found, what the evaluator reconsidered, and how the later determination relates to the first.
History
The authority map behind JARING: What Mohamed Awang Lah led—and what he did not control
Mohamed Awang Lah occupies a prominent place in the history of Malaysia’s early internet infrastructure. Yet prominence is not the same as unlimited authority. The evidence supports a more useful account: he exercised substantial technical and operating leadership inside…
CASE FILE
The Server Returned Four Batches. It Had Not Frozen the Mailbox: RFC 10022 and the UIDBATCHES Closeout Boundary
An IMAP server can answer `UIDBATCHES 2000` with four orderly ranges and a final `OK`. That answer is useful precisely because it is less than a snapshot: the endpoints may name no stored message, deletions may thin a range, new mail may rise above it, and no later FETCH, COPY or…
History
One Link Was Actually Several: How PPP Multilink Kept a Bundle in Sequence
A second line could join a PPP connection without beginning a second network conversation. Multilink PPP treated the lines as members of one bundle, cut a packet into independently framed fragments, and gave the receiver just enough shared order to put the packet back together.…
CASE FILE
The Card Was Removed. Its Configuration Stayed: RFC 10016 and the Authority of System State
RFC 10016 gives device-supplied configuration a standard place to be seen. It also exposes a harder operational truth: the device can withdraw a system node while client intent remains, and a client can withdraw an override only to uncover the system value beneath it. The four…
MENOG
MENOG’s Local Host Can Sign Contracts, but the Secretariat Holds Approval
MENOG gives a local host substantial work and visible benefits. Its host requirements also draw a precise line: the host may sign service contracts on the Secretariat’s behalf, but only subject to the Secretariat’s approval.
History
The Success That Ended Its Own Stream: How XMPP Restarted After TLS and SASL
In XMPP, a successful security negotiation did not authorize the old XML stream to continue. It made that stream obsolete. The parties kept the same TCP connection, discarded context that no longer deserved trust, exchanged new stream headers and learned again which features were…
History
The Characters the Checksum Never Saw: How PPP Filtered the Serial Path Before Trusting the Frame
PPP did not ask its checksum to remember every character that crossed a serial path. It first defined which bytes belonged to the frame, which were temporary disguises, and which low control characters intervening equipment might have inserted. Only after the receiver reversed…
CASE FILE
The Tree Was Active. One Leaf Still Had No Packet: RFC 10018 and the P2MP Closeout Boundary
The Tree Was Active. One Leaf Still Had No Packet: RFC 10018 and the P2MP Closeout Boundary intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…
CASE FILE
The Endpoint Still Spoke TLS 1.2. Its Old Handshake Had to Go: RFC 10015 and the Retirement Boundary
RFC 10015 does not switch TLS 1.2 off. It makes a more exacting intervention: keep the protocol version where it is still needed, but remove the finite-field Diffie-Hellman and RSA key-exchange paths whose risk can no longer be justified. The hard part begins after that sentence…
History
The Header That Appeared Only When It Saved Bytes: How IPComp Made Compression Conditional
IPComp negotiated a common way to decompress traffic, then allowed each packet to decline the offer. If compression plus its four-byte header did not make that packet smaller, the correct wire format was the original packet with no IPComp header at all. Capability lived in the…
History
The Datagram Relay That Died with a Stream: How SOCKS5 Bound UDP to a TCP Association
A SOCKS5 relay could still be receiving perfectly formed UDP datagrams when its TCP control connection vanished. The specification nevertheless ended the association. UDP had no farewell to offer, so the protocol borrowed a lifetime from a different transport—and kept that…
History
The Key That Could Not Lock the Tunnel: How GRE Separated Flow Identity from Security
GRE called a four-byte field a Key before the specification could say what that key opened. Six years later, the standards-track repair gave it a smaller and more useful job: distinguish one logical flow inside a tunnel. The name survived. The claim of security did not.
CASE FILE
W3C Resolved to Change WCAG 3. It Did Not Freeze the Text
On 25 August, the Accessibility Guidelines Working Group adopted three resolutions that pointed editors to a conformance draft and told them to resolve the document's remaining comments before updating WCAG 3. That was a real group decision. It was not approval of every word that…
CASE FILE
The Handshake Combined Two Secrets. The Random Generator Was Still One
RFC 10024 gives TLS 1.3 a precise way to combine a traditional exchange with ML-KEM. The construction protects against the failure of one cryptographic assumption; it does not certify that the two components were executed inside independent operational failure domains.
Story
Four Counterparty Pairs Made 89% of RIPE NCC's July IPv4 Transfer Total
RIPE NCC's August member update says 5,935,616 IPv4 addresses were transferred in July, 4,159,744 more than in June. The public transfer tables reproduce both numbers exactly. They also change the meaning of the headline: four repeated from-to pairs account for 5,299,712…
CASE FILE
The Name Matched. The Key Had No Right to Revoke: RFC 10007 and the Missing `cRLSign` Proof
One certification authority gave the same named subject two different keys. Only one was meant to sign revocation lists. For years, the validation text could let the other key cross that boundary precisely because its certificate said nothing about permitted use.
ICANN
ICANN's IPIP Termination Notice Has Two Lists—and Only One Names the Breaches
ICANN has told registrar IPIP INC. that its accreditation will end on 13 September. The eight-page notice is more precise than the inevitable shorthand: it names four breaches that remained uncured, then separately records additional concerns, then sets out consequences and…
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