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,720 articles
IETF
The DNS Server Arrived. The Resolution Path Did Not: RFC 3646
A DHCPv6 Reply can carry a preferred list of recursive servers and a domain search list in a few bytes. That is useful configuration evidence, but it is not a receipt for what the host installed, which resolver handled a query, what name was ultimately asked, whether DNSSEC…
History
One DNS Record Carried Keys That Did Not Share Trust: RFC 3445
The early DNS `KEY` record looked economical: place many kinds of public key in one familiar directory. Its economy disappeared when every query, signature and cache operation had to carry keys governed by different people, rules and failure consequences. RFC 3445 turned that…
IETF
The Group Cipher Opened. It Did Not Name the Sender: RFC 9750
A green decryption result can be entirely correct and still answer the wrong management question. RFC 9750 gives operators a sharper vocabulary for separating group-secret possession, client attribution, identity binding, application authority and delivery—five layers that…
IETF
The Signature Was Valid. Permission Was Still a Separate Question: RFC 3645
A green cryptographic check is seductive. It can make an operations console look as though the whole decision has already been made: the peer is trusted, the requested DNS change is allowed, the zone was updated and users can now see the result. RFC 3645 supports only part of…
History
The Physical Link Knew What the Tunnel Terminator Could Not See: RFC 3437
An L2TP tunnel put PPP control far from the wire whose limits it had to negotiate. RFC 3437 answered that information asymmetry with four messages: the access edge could state what it wanted and allowed, and the remote session owner could return the configuration packets that…
IETF
The Certificate Was Allowed to Sign for Messaging. It Did Not Name the Account: RFC 9734
RFC 9734 gives an instant-messaging certificate a narrower purpose. That is valuable precisely because it does less than many trust screens will be tempted to claim: the new OID can constrain a key’s use without deciding which account is current, which device is authorized, or…
IETF
The Port Was Visible. The Service Was Only a Guess: RFC 3639
A firewall can read a destination port with perfect accuracy and still be wrong about the service. RFC 3639 drew that boundary in 2003: transport labels coordinate endpoints, while a device on the path usually sees only a convention. The more aggressively an intermediary turns…
History
One Secure Stream Cost One TLS Connection: RFC 3436
SCTP promised many independent message streams inside one resilient association. RFC 3436 preserved that independence by giving every protected bidirectional stream its own TLS connection—but the price was a separate handshake, strict ordering, unlimited lifetime and a security…
History
The Notified Entity Received the Commands. It Did Not Resolve the Handover: RFC 3435
A media gateway could be redirected toward a backup Call Agent and still leave the hardest question unanswered: which controller possessed the complete, legitimate state of the call? RFC 3435 made the routing pointer explicit while admitting that controller-to-controller conflict…
IETF
The Counter Went Quiet When the Link Got Worse: RFC 3637
A monitoring curve can flatten for two opposite reasons: the faults stopped, or the counting rule stopped admitting them. RFC 3637 documented the second possibility with unusual candour. Its Ethernet WIS MIB reused deployed SONET management entities even where their interval and…
IETF
The Measurement Label Moved the Flow It Was Supposed to Observe: RFC 9714
A measurement can be internally precise and externally wrong about its subject. RFC 9714 gives MPLS packets a Flow-ID Label for Alternate Marking, yet warns that inserting that label may change ECMP selection—so the instrumented twin can leave the path of the production flow it…
History
The Zero After a Failed Poll Was Not a Reading: RFC 3434
A monitoring system can display zero with perfect numerical confidence while knowing nothing about the quantity it was meant to retrieve. RFC 3434 made that contradiction explicit: after a failed poll, zero occupied the magnitude field, but a separate status said the value was…
History
The Number Needed Scale, Precision, and Time: RFC 3433
An integer from a chassis sensor looked precise long before it became meaningful. RFC 3433 made the surrounding type, scale, precision, status and update history part of the reading—and left alarms and physical truth outside that narrow receipt.
IETF
The Snapshot Restored a Key That Had Already Been Spent: RFC 9708
A hash-based signature can survive future cryptanalytic pressure and still fail because yesterday’s machine state came back to life. RFC 9708 makes HSS/LMS usable in certificates and CMS, but its deepest operational fact is not an algorithm identifier: signing authority includes…
CASE FILE
NovaCloud-Hosting's real transit story: three small upstreams behind a Tier-1 marketing front
NovaCloud-Hosting sells itself as a globally connected European host, but the registry and the routing table tell a narrower story. This investigation reconstructs who actually carries the operator's traffic, why its own pages contradict each other, and what a customer is really…
IETF
The First KDC Address Had Priority. It Did Not Have a Health Check.
The maintenance dashboard called the first address “primary” and the second “backup.” That sounded like a live conclusion. RFC 3634 had promised something narrower: a DHCP field containing one or more IPv4 KDC addresses, placed in decreasing order of administrative priority. It…
History
The Start Time Was Random. The Stream Was Still Periodic: RFC 3432
RFC 3432 randomized when a measurement train began, then sent its probes on a regular beat. The method reduced predictability without pretending that its application-shaped sample represented every moment of the network.
IETF
The Caller Card Said Verified. The Trust Still Ended at the Inserter: RFC 9796
A green caller card can be accurate without being self-authenticating. RFC 9796 lets a trusted network actor expose verified Rich Call Data to a device that cannot validate the original PASSporT, but the word “verified” remains attached to one field, one verifier and one trust…
History
The Packet Was Delivered. The Accounting Record Was Not Yet Safe: RFC 3423
One acknowledgement ended at the transport stack; another waited for the receiving application to process an accounting record and place it in persistent storage. RFC 3423 made the space between those two signals visible.
IETF
The Same “No” Rejected a Transfer—or Cancelled It.
The forensic export looked complete: a domain name, a `TRANSFER` command, `-Approve:No`, and a `200 Command completed successfully` response. Yet the decisive column was missing. If the command came from the current sponsoring registrar, “No” rejected another registrar’s request.…
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