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,561 articles
IETF
LWAPP Is a Historic Record, Not a Deployment Baseline
RFC 5412 documents the Lightweight Access Point Protocol as it was submitted during the CAPWAP work. It is valuable archival evidence about an access controller and wireless termination point model, but the RFC Editor explicitly labels it Historic and says it should not be used…
CASE FILE
PP-26’s Podium Has a Queue. Its Formal Record Needs a Second Track
Before the conference opens, ITU has defined a scarce public-speaking channel: one high-ranking delegate per Member State, a first-come queue tempered by official rank and physical presence, and two or three minutes at the microphone. The resulting speeches can shape strategic…
IETF
CATS Chose the Service Contact. The Backend Stayed Hidden: RFC 10053
CATS can steer a request toward a promising service contact using network and compute conditions. That choice still may not reveal which service instance handles the request behind the contact, or whether the reported metrics describe that instance alone.
History
The Controller Needed a Network Before It Could Control One: RFC 7149
In March 2014, an IETF memo asked service providers to look past the seductive diagram of a central controller and ask a more operational question: how does that controller find, reach and safely influence the network beneath it? RFC 7149 treated startup, customer negotiation and…
IETF
A SIP Guide Is a Map, Not a Deployment Certificate.
RFC 5411 is useful precisely because SIP is too large to hold in one mental model. It groups the RFC series by topics, labels their status and points readers toward related work. But the document is an Informational snapshot, not a live inventory of what a carrier runs. A listed…
History
DHCP Carried a Stable Subscriber ID. The Standard Did Not Define Its Meaning: RFC 3993
A customer could move between access paths while a provider still wanted the same configuration decision. RFC 3993 gave the DHCP relay a place to carry a stable subscriber label, but left the label’s assignment and meaning with the provider.
IETF
The Broadcast Extension Carried a Key Message. It Did Not Prove the Key Was Installed.
OMA BCAST needed MIKEY to carry more than one kind of control message: short-term keys, long-term keys, reporting data and parental-control information. RFC 5410 adds a General Extension payload for that transport. The payload proves that a particular message was encoded for a…
IETF
CMS Wrapped the Key. The Recipient Identity Still Had to Match.
RFC 5409 is not a general promise that “IBE works with email.” It defines the CMS conventions for encrypting a content-encryption key with Boneh-Franklin or Boneh-Boyen IBE, including recipient-identity encoding and algorithm identifiers. The envelope can be structurally valid…
IETF
The Identity Could Be a Public Key. It Still Was Not Permission.
An identity-based encryption design promises a neat operational shortcut: calculate a public key from the recipient's identity, encrypt immediately, and ask a trusted private-key generator for the matching secret only when the recipient needs it. RFC 5408 makes the shortcut…
IETF
A Better Edge Is Not Permission to Move the Session: RFC 10054
A client can leave the metro edge while its service remains stateful. RFC 10054 says a routing system may account for both network and compute conditions, but a mid-session move needs an explicit application indication that CATS is allowed. The faster destination and the…
CASE FILE
CNCF’s 2.07× Finding Needs a Clear Cohort Record
The CNCF reports that projects with maintainers from several organizations at Sandbox entry graduate more often. Its current review template separately requires maintainers from at least two organizations at graduation. Those statements point in a similar direction, but they…
IETF
The Channel Was Bound. The Operation Was Still a Separate Decision.
An SIP gateway showed a verified security context and a clean message check. The dashboard promoted that evidence into “authorised and complete.” RFC 5407 draws a harder line: SIP Version 2 can bind a SIP message to lower-channel information, but the binding does not become local…
History
Level 2 Belonged to the Session, Not the Device: RFC 7147
An iSCSI target could meet different initiators through separate sessions. RFC 7147 put the negotiated protocol level where that agreement lived: in each session’s management record, not on a device-wide capability badge.
IETF
The Channel Was Bound. The Operation Was Still a Separate Decision.
An IPsec gateway showed a verified security context and a clean message check. The dashboard promoted that evidence into “authorised and complete.” RFC 5406 draws a harder line: IPsec Version 2 can bind a IPsec message to lower-channel information, but the binding does not become…
IETF
The Channel Was Bound. The Operation Was Still a Separate Decision.
An RTP gateway showed a verified security context and a clean message check. The dashboard promoted that evidence into “authorised and complete.” RFC 5404 draws a harder line: G.719 RTP Version 2 can bind a G.719 frame block to lower-channel information, but the binding does not…
IETF
The Channel Was Bound. The Operation Was Still a Separate Decision.
An RPC gateway showed a verified security context and a clean message check. The dashboard promoted that evidence into “authorised and complete.” RFC 5403 draws a harder line: RPCSEC_GSS Version 2 can bind a GSS context to lower-channel information, but the binding does not…
IETF
Only One Side Authenticated. Both Ends Still Had to Bind the Channel: RFC 5387
Two control panels can each show a green lock while an unauthorized proxy sits between them. RFC 5387 explains the missing evidence: authentication may intentionally run in one direction, but the claim that both parties share one protected channel has to be checked at both ends.…
History
A Global Address Could Be a Loan, Not a Host's Identity: RFC 1335
In May 1992, one proposed answer to IPv4's allocation pressure began with a quiet distinction: a machine could keep its address at home while borrowing a globally unique one only when it needed to cross the Internet.
APRICOT
APNOG Put Its Board on a March Clock. The Handover Is the Test.
APNOG says its Board terms will run from March to March, rather than exactly with the annual general meeting. The stated purpose is practical: give outgoing and incoming directors time to hand over work and let new directors apply for an Australian director ID before appointment.
IETF
The Receipt Matched. The Order Was Not Yet Accepted.
The trading gateway returned a signed receipt with the expected Message Integrity Check. A dashboard promoted that narrow success into “order accepted.” RFC 5402 shows why the promotion is unsafe: compression changes which bytes sit inside the signature and MIC boundary, while…
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