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,519 articles
Story
APNIC's RDAP Use Is 20%. That Is Not an Adoption Rate.
APNIC's new survey puts RDAP at 20% among respondents asked about core registry services. The number is useful evidence about reported use; it is not a census of deployed systems, a traffic share or a verdict on whether RDAP can replace WHOIS.
History
Jerry Saltzer and the Link That Carried a Name but No Permission
A path can tell a computer where a file is without answering whether the person following it may read the file. Jerry Saltzer’s account of protection in Multics turned that separation into an operating rule—and exposed how much revocation, audit and institutional power can be…
IETF
Accept-Patch Advertises Patch Formats, Not Permission to Modify
A server can tell clients which patch-document languages it understands without deciding who may change a resource. RFC 5789 gives that discovery statement a name, Accept-Patch, and keeps capability, format semantics, current state and write authority as separate questions.
CASE FILE
The Stream Was Created. The Broadcast Was Not: RFC 9725
A WHIP endpoint can return `201 Created` while the programme remains black. RFC 9725 makes low-latency contribution easier to start; it also makes it essential to distinguish the HTTP resource from the media path, the production chain and the audience result.
IETF
Web4 Policy Draft Makes Publication Evidence, Not Proof of Conduct
A federation can publish a current, correctly signed policy that lists its appeals, retention and revocation rules—and still fail to follow any of them. A new individual IETF draft makes that limitation explicit, turning policy publication into a verifiable disclosure surface…
Story
Rapport’s Forbidden-AKI Test Starts at Barry, Not at the Validator
A conformance test cannot prove that a validator rejected a forbidden certificate field until it proves that the field reached the certificate. A September correction to one LACNIC Rapport fixture makes that dependency unusually visible. The change replaces a scalar value that…
Story
AFRINIC's RRDP Lists 32 Deltas. That Is Not a Recovery Window.
AFRINIC's live RPKI notification showed a neat chain of 32 incremental updates. The number is useful, but it does not tell a network operator how long a validator may be offline before recovery changes from a small replay to a full snapshot.
History
Eve Schooler and the Invitation That Did Not Carry the Conversation
The most consequential line in an Internet call is not the one carrying a voice. It is the one that finds the other person, proposes a session and then gets out of the way. Eve Schooler’s path from experimental conference control to the early Session Initiation Protocol helps…
IETF
SAV Benchmark Draft Makes “Legitimate” a Reported Fact, Not an Assumption
A revised IETF benchmarking draft puts an easily overlooked governance burden inside a technical test report: anyone measuring source address validation must say which packets were legitimate, which were spoofed, and why. That requirement matters because an error rate is only as…
IETF
Content-Location Describes a Representation, Not Where the Client Must Go
An HTTP response can identify the resource corresponding to the document it carries without changing the address that was requested. RFC 9110 calls that field `Content-Location` and makes the boundary explicit: it is representation metadata, not a replacement target or an…
CASE FILE
RFC 9727 Put the APIs in a Catalog. It Did Not Put the Catalog in Charge
The most dangerous API inventory can be perfectly formatted. Its links validate, its cache is warm, and its obsolete interface is gone from the list. None of those facts says what is still listening on the network.
IETF
103 Early Hints Can Start a Fetch, Not Settle the Response
A web server can reveal part of its likely answer before it has decided the answer itself. RFC 8297 makes that useful without making it authoritative: a 103 response can fund preparation, while the final response alone settles what the request produced.
IETF
Agentproto Charter Revision Separates External Input From IETF Decisions
One sentence added to the Agentproto proposed charter does more than promise cooperation. Revision 00-01 says the prospective working group would coordinate with outside standards and open-source efforts to learn from deployed practice and avoid divergence. The sentence before it…
History
Lixia Zhang and the Data Packet That Did Not Need Its Original Server
The revealing moment in Named Data Networking is not when a packet reaches a machine. It is when an Interest is answered by a copy found somewhere else—and the receiver can still ask who signed the data, whether that key was entitled to sign this name, and whether a fresher…
Story
RIPE NCC Has 110 Sanctions Investigations. Its Table Has No Clock.
RIPE NCC’s latest sanctions report makes the size of its screening work visible: the cumulative register reached 2,172 alerts, with 110 still under investigation on 2 July 2026. What the table cannot show is equally consequential. A reader can see where cases sit, but not how…
IETF
A Problem Type URI Is an Identifier, Not a Remote Command
An API error can name a stable kind of failure without giving the name control over the client. RFC 9457 draws that boundary precisely: the problem type URI identifies semantics; the response, the client’s policy and separately defined evidence determine what may happen next.
Story
APNIC Says prop-170 Reached Consensus. APNIC-127 Still Does Not Say “Nibble”
On 14 September, two official APNIC pages described prop-170 as having reached consensus at APNIC 62. A third official page still labelled it “For Discussion at APNIC 62 OPM”. The operative policy supplied a more important answer: APNIC-127 still contained the old IPv6 allocation…
Story
The RIR Draft Counts 1,000 Members, Not 1,000 Votes
The proposed compliance-review threshold uses legal entities, not voting weight. LACNIC’s own election figures show why an auditable denominator must come first.
IETF
CMS Draft Makes Future Publication the Line Between New and Existing Use
A security rule can be precise and still leave its future population hard to see. A new LAMPS draft revision says new CMS SignedData uses must not use `id-data`, yet defines “new” by the date of a future publication while discussing nonretroactivity in terms of deployed…
IETF
UUIDv7 Is Time-Ordered, Not a Causal Receipt
UUIDv7 places time at the front of an identifier so new values tend to sort near one another. That is valuable for indexes and rough chronology. It does not mean the identifier can testify that event A caused event B, that two machines agreed on time, or that the holder has any…
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