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,732 articles
History
The Counter Said GET. The Probe Had Remembered a Reply and Chosen One Verb: RFC 3395
The number looked like a direct observation. RFC 3395 revealed the machinery behind it: memory of an earlier packet, reconstruction of a conversation, and a compulsory choice when the traffic admitted more than one label.
History
A Legitimate Packet Can Still Fail the Filter: RFC 3704
A packet can carry a valid source address and still be dropped at a provider boundary. The reason may not be the address at all: it may be the route the receiving router believes should have brought it there.
History
The Ciphertext Grew by One Register. That Register Decided Whether the Key Existed: RFC 3394
RFC 3394 did not merely encrypt a row of key bytes and add padding. It sent one 64-bit register through every turn of the transform, placed that register at the front of the result, and required it to return in the expected form before an implementation could release any…
IETF
The OAM Probe Failed. BGP Withdrew a Path That Was Still Forwarding.
A liveness check meant to prevent a blackhole can create one when its negative result is wrong. The current BGP best-path draft addresses a real mismatch between IP reachability and the data plane that carries traffic. Its harder consequence is institutional: once a probe can…
IETF
The Label Table Survived. It Still Needed a Witness.
An LDP restart can keep an MPLS data plane from beginning again at zero. The harder question begins after that success: which retained label still belongs to which forwarding equivalence class, for how long, and who can prove that packets followed the surviving claim?
History
The Test Numbers Were Shared. The Experiments Were Not: RFC 3692
A protocol experiment needs a number before it can cross a wire. RFC 3692 made two values available for that moment—but warned that the same number could name different experiments in different places. Permission to test was not a promise of compatibility.
IETF
The Receiver Sent More Detail. It Still Had Not Sent Ground Truth.
RTCP XR let a receiver return far more than a loss fraction. It also made a harder discipline unavoidable: every number belongs to a witness, a stream, a measurement window and an algorithm, and none of those labels can be discarded merely because the dashboard looks complete.
IETF
The Trace Parsed Cleanly. The Missing Events Had No Tombstones.
A structured log can be valid, orderly and useful while failing to contain the moment that matters. The qlog draft makes network-protocol evidence portable; it also states, in unusually direct language, why a clean trace is not a completeness certificate. Leadership must preserve…
History
The Image Arrived Beside Its Reference. The Producer Still Could Not See the Reader: RFC 3391
RFC 3391 could rearrange the journey of a compound document so that each image travelled near the sentence that called for it. What it could not rearrange away was uncertainty about the machine at the other end.
IETF
The Path Looked Complete. The Tunnel Had Not Testified.
A neat row of responding routers can look like a complete journey. RFC 3609 asked operators to treat that row more carefully: an IP hop may be a container for an unseen forwarding system, and revealing what lies inside is a permissioned measurement problem rather than an…
History
Silence Stopped the Packets. The Room Did Not Go Silent: RFC 3389
The quiet heard at one end of an Internet call was not necessarily carried across the network; often, the receiving machine made it for itself.
IETF
Both Paths Were Valid. No Standard Chose Which One Should Carry the Next Byte.
Two network paths can pass every transport check and still leave the consequential decision unresolved. Multipath QUIC revision 21 gives endpoints a disciplined way to name, validate, acknowledge and retire several paths inside one connection. It does not decide which path should…
History
The Network Changed; the Subscriber’s Home Did Not: RFC 3141
In the early mobile Internet, a handset could borrow another operator’s radio network without moving its customer relationship. RFC 3141 made that split an AAA requirement: the visited network supplied access, while the subscriber’s home provider remained the formal service…
IETF
The Registrar Returned a Route. It Did Not Record the Journey.
RFC 3608 lets a SIP registrar tell a user agent which service proxies it may use after registration. That ordered Service-Route vector is useful configuration. It is not a transcript of the next request, proof that each proxy was reached, or evidence that the promised service…
History
One Missing Label Canceled Every Group: RFC 3388
The media descriptions remained individually valid, yet one unnamed line was enough to stop the application from believing any declared relationship among them.
History
3GPP2’s Meetings Were Open. Its Mailing Lists Were Not: RFC 3131
In June 2001, RFC 3131 described an unusual participation map: an interested person could attend a 3GPP2 meeting, yet the group's technical mailing lists were not open to the general public. The memo's proposed bridge was not to pretend the boundary did not exist. It was to put…
IETF
The Clock Put One Notification First. It Did Not Prove Why.
Publisher B’s notification sorted before publisher A’s. Neither publisher had received a message from the other. The order was useful, reproducible and entirely limited public evidence to show that one event caused the other.
IETF
The Candidate Was Valid. The Compute History Was Still Missing.
A public result can satisfy a cryptographic test while leaving the work that produced it almost entirely unattributed. RFC 3607, an Informational document from 2003, imagined Internet-scale “Chinese lottery” cryptanalysis. Its arithmetic was deliberately conditional. A valid…
History
The Queue Could Differentiate Packets. The Operator Still Had Not Defined a Service: RFC 3387
A priority mark could move one packet ahead of another, but it could not identify the buyer, prove the promise, settle the bill or decide which provider owned the failure.
History
The Lower Layer Recovered First. The Upper Layer Had to Wait: RFC 3386
One broken fibre could awaken several recovery systems at once; the hard problem was deciding which layer had the first right to move traffic, and how long every other layer should wait.
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