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,698 articles
Story
One Upstream, Frozen Paperwork: What AS51035's Stable Shape Says About ER-Telecom's Ufa Branch
The network that carries the name "Network Operation Center JSC ER-Telecom Holding Ufa branch" has not changed its declared routing policy since September 2018, its registry role entity since October 2019, or its announcement set since December 2019. Its entire external…
History
The Counter Said the Call Succeeded. It Could Not Say Whether a Person Heard It: RFC 3055
In 2001, the PINT working group gave operators a disciplined way to count Internet-triggered telephone services. RFC 3055 could distinguish received, successful and disconnected calls across users, clients and gateways. Its greater lesson lies in the distance it preserved: a…
IETF
The CDN Accepted the Cancel. The Purge Could Still Finish.
A September 2026 CDNI draft gives interconnected content networks a richer language for prepositioning, invalidating and purging content. Its most important operational lesson is narrower: asking a distributed system to stop is not evidence that the work did not happen.
History
The 14 kHz Upgrade Kept a 16 kHz Door Open: RFC 5577
RFC 5577 widened the G.722.1 audio profile and added a faster sampling clock. Its most revealing migration rule was quieter: keep offering the 16 kHz configuration when older terminals still matter.
IETF
The Tunnel Negotiated Over TCP. Its Protected Traffic Still Had No Road
A large post-quantum IKE exchange can finish cleanly over TCP while the ESP path that must carry the protected service remains blocked. Revision 07 of the IETF’s separate-transport draft turns that awkward fact into an operating discipline: control-plane success is not data-plane…
History
The Phone Named Its Parts. The Controller Still Had to Ask What Was There: RFC 3054
RFC 3054 gave an Internet telephone a shared vocabulary for its display, keys, handset, speaker and media stream. The IPPhone profile let a remote controller begin with a known model instead of guessing a device from an arbitrary inventory. That shortcut reduced inference. It did…
History
The Root DSE Could Name Its Vendor. RFC 3045 Drew the Line at Capability Discovery.
An LDAP server could tell a client who made its software and which release string it reported. That was useful context for a human—or a narrowly targeted workaround—but it was not a feature list. RFC 3045 made the distinction explicit: a vendor label might help explain an…
IETF
Silence Is Not Availability: The Multicast Address That Survives Until the Partition Heals
Two senders can each complete a clean probe, retain the same multicast group ID and continue without an alarm. The contradiction appears only when the switch comes back and the network becomes whole again. An IETF draft now makes that delayed failure unusually legible: its…
CASE FILE
Filing the Complaint: The Public Remedy Path Behind the Svea Abuse Contact
Svea's abuse contact in the RIPE registry passes every automated check the registry runs, and no public source shows it has ever answered a report. This briefing sets out the filing test: the channels a reporter can actually use today, and the observable responses that would…
Number Resource Society
RIPE NCC's Excess-Contribution Redistribution: A Codified Remedy, Not a Gesture
When the RIPE NCC returned EUR 8,365,249 to its members in 2020, the money moved under a written procedure that predates the decision — and the October 2019 General Meeting vote that authorised it was split hard enough to reveal how contested the choice between reserve and…
History
The ISSN Stayed. The URLs Moved. RFC 3044 Built a Watcher Between Them
In 2001, the ISSN International Centre showed how a familiar serial number could travel inside a URN. The harder part was never printing the number. It was keeping the route from that number to a journal’s changing web address honest. RFC 3044 said the identifier could persist…
IETF
The Compensation Ran Forward. It Did Not Prove the Past Was Restored
An AI-assisted network workflow can carry a carefully structured recovery plan and still fail to put the world back. In the first NAIM Operation IR draft, compensation is another authorized, validated and logged operation—an attempt to reverse or mitigate a prior change, not a…
History
The Broker Ordered the Tunnel. Another Machine Had to Carry It: RFC 3053
RFC 3053 made an awkward early-IPv6 task look like a service: register, supply an IPv4 endpoint, receive configuration and connect. Its architecture also exposed a boundary that service language can hide. The Tunnel Broker made allocation and configuration decisions; a Tunnel…
Story
AS210328 Today: What the Live Record Shows — and Fails to Show — About AO ALMAZ's Cloud Network
AS210328 Today: What the Live Record Shows — and Fails to Show — About AO ALMAZ's Cloud Network 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 Mailbox Is Not the Complaint: A Four-Layer Test for Whether RIPE's Abuse-Contact System Actually Works
Every network abuse complaint in the RIPE service region ends, at some point, in an email address recorded in the RIPE Database. The registry proves each year that tens of thousands of those mailboxes can receive mail. What nobody can prove — because nothing published measures it…
History
A Global Name, One Authoritative Resolver: The Promise and Limit of RFC 3043
In January 2001, Network Solutions proposed a durable Internet name for people and organizations. RFC 3043 made the reference portable across applications, but its own registration template placed authoritative interpretation inside the company’s resolver. The distinction still…
IETF
The Draft Promised 0-RTT. Its Normative Rule Turns It Off.
The router returned after a failure with an old RPKI cache view and a valid QUIC session ticket. The draft's introduction offered a tempting picture: put the session request in the first packet and almost instantly close the blank interval. Five pages later, the protocol did…
IETF
The Incident Named a Cause. The Confidence Stayed Upstream
An incident record can be exact about the node, resource and class of a probable cause while remaining silent about how strongly the diagnosis is believed. Revision 17 of the IETF NMOP incident model makes that silence deliberate: confidence belongs outside the common incident…
History
The Standard Recommended LDP. It Did Not Prove the Protocol Was Running: RFC 3037
RFC 3037 recommended LDP for devices that carried MPLS traffic along normally routed paths. That sentence selected an appropriate protocol function; it did not certify a device, enable a feature, establish a TCP session, install a label or move a packet. The applicability…
History
Two Duplicate ACKs Could Send New Data, but Not Enlarge the Window: RFC 3042
A TCP sender with a three-segment congestion window loses one segment. The receiver can return only two duplicate acknowledgments for the later data, one short of the threshold that would trigger Fast Retransmit. In 2001, RFC 3042 proposed a narrow way to keep the feedback clock…
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