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,427 articles
CASE FILE
The route outlived the speaker
BGP Long-Lived Graceful Restart can keep a failed peer’s routes for hours or days after ordinary restart protection ends. That buys time, but it also turns stale state into a temporary operating promise whose timer, forwarding basis and exit must be proved.
History
The Packet That Had to Go Home Before Going On
A mobile computer could carry its address to another network, but not necessarily the right to emit that address from there. Mobile IPv4's reverse tunnel sent an outgoing packet home before letting it continue to its correspondent. The detour was less an admission that the…
History
The New Key That Inherited Its Past: What TLS KeyUpdate Could Rotate
A protected connection may last far longer than the key that first carried its traffic. TLS 1.3 gave that connection a way to move forward without renegotiating who its peers were—but the new secret remained a descendant of the old one, with a sharply bounded security promise.
History
The Alert EOF Could Not Replace: How TLS Made One Direction's End Explicit
A receiver can authenticate every byte it saw and still not know whether more bytes were meant to arrive. TLS solved that narrower problem by putting the ending inside the protected conversation, then learned that the two directions should not be forced to end together.
History
The Report That Had to Wait for the Crowd
An RTCP report timer reaches its appointment, and the source still does not send. The report is ready. The correct next action may still be to send nothing. In the control protocol accompanying real-time media, an appointment made with an incomplete picture of the group is not an…
CASE FILE
The User Matched Twice. The Packet Was Valid: RADIUS CoA and the Authority to Change a Live Session
A correctly protected control request reaches an access router and asks for a new traffic filter. The subscriber name matches two live sessions. Cryptography has answered who sent the packet on this hop. It has not answered which connection may be changed.
IETF
IETF LLC Bars AI Note-Takers from Board Meetings
The April 2025 attendance list placed a human observer and an `AI Noota Assistant` on the same line. A separate human scribe still owned the minutes. The current IETF Administration LLC Board page now draws a harder boundary: AI note-taking and transcription tools may not enter…
Story
The Commitment Must Keep Its Name: RIPE NCC’s Missing Annual Ledger
RIPE-862 offers a precise starting chain: **Internet Resilience, Scalability and Routing Security**; the service-level objective **Security**; and the key metric **Internet Number Resources covered by ROAs and ASPA**. The next links—a costed 2027 Activity Plan and Budget…
History
The Record the Receiver Could Not Hold: How TLS Made Size a Local Claim
A small endpoint may be able to stream encrypted output while lacking the memory to authenticate an equally large record arriving from its peer. TLS eventually learned that the two directions do not have to pretend they are the same machine.
CASE FILE
The session stayed green. The routes disappeared
A malformed BGP UPDATE no longer has to take an entire peering session down. That is a major containment gain, but it changes what operators must prove: an Established session can now coexist with a precise set of destinations that the receiver has removed for safety.
History
The Checksum That Had to Ask in the Old Language
A TCP endpoint could propose a different checksum without making an old peer fail. The old peer would ignore the unfamiliar option, answer normally, and thereby withhold the matching signal the experiment required. The fallback that made RFC 1146 safe to deploy also made…
Story
Between Listening and the Map: LACNIC’s Missing Input Trace
LACNIC’s public account names a collective planning process and a route from listening to SWOT and a final strategic map. What the checked documents do not expose is the privacy-safe join that would let a reviewer follow one issue from source class and channel through synthesis…
History
The Flight TLS Sent Before the Server Finished: How False Start Borrowed One Round Trip
TLS False Start let a client release freshly encrypted application data after sending its own Finished but before verifying the server's. It saved a wait by moving data across an unfinished proof boundary—not by removing the proof, resuming an old session or sending plaintext.
IETF
IETF’s 2418bis Draft Adds an Exit State for Adoption
The dependency register showed a green `WG Document` badge beside a draft that no longer attracted editors or review. When the working group removed the draft from its active work set, the register replaced green with grey and wrote “proposal rejected.” That last phrase was not…
IETF
Ross Callon and the UDP Port That Was Entropy, Not a Session
A familiar UDP header can make an MPLS tunnel look more conversational than it is. Ross Callon’s shared work on RFC 7510 shows why the source port is a path-distribution signal, while identity, admission, label meaning and congestion responsibility remain elsewhere.
CASE FILE
The Packet Was Authentic. The Clock Was Still Wrong: NTS and the Authority of a Time Measurement
Two time servers answer the same machine. Both replies pass Network Time Security checks. Their offsets are 800 milliseconds apart. The cryptography has done its job, yet the operator's hardest question remains unanswered: which measurement, if either, may steer the clock?
CASE FILE
The route that came home wearing its own ASN
The route that came home wearing its own ASN 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 CASE FILE intelligence…
History
The Address That Needed a Local Footnote
Copy `fe80::1%eth0` from one host to another and every character survives. The intended path may not. `eth0` belongs to the first host’s local map, so the apparently complete address carries a footnote whose authority ends at the machine that wrote it.
CASE FILE
The DNS ID Changed. The Old Rule Still Blocked Mail: MTA-STS and the Authority of a Cached Policy
At 09:00 a recipient added a backup MX to its HTTPS policy and changed the `_mta-sts` TXT `id`. One sender fetched the update. Another could not refresh and still held yesterday's unexpired `enforce` policy. Both resolved the same backup host; only one was permitted to use it.…
History
The Name TLS Had to Hear Before It Could Hide It: How SNI Made Shared HTTPS Possible
At a shared address, a TLS server had to choose a certificate before it could decrypt the HTTP request that named the intended site. Server Name Indication resolved that ordering problem by putting the name in the ClientHello—making virtual HTTPS practical while leaving the…
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