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 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
4,325 articles
Story
LACNIC Whois routing-c Can Register Routing Policy, Not Prove Who Operates BGP
LACNIC Whois routing-c Can Register Routing Policy, Not Prove Who Operates BGP intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may…
History
The Test Address Came With Its Eviction Notice: RFC 1897 and the 6bone
In 1996, an IPv6 address could be useful, globally coordinated and routable across an experimental backbone while still carrying no promise of permanence. RFC 1897 made that distinction explicit: its addresses were for prototype testing, would be reclaimed and required their…
Story
AFRINIC's PDP Reform Needs a Decision Ledger
AFRINIC's proposed operating rules for its Policy Development Working Group try to replace contested custom with written procedure. The harder task is making every transfer of authority—from discussion to consensus, appointment, ratification and appeal—visible enough to audit.
CASE FILE
A Celestial Name Is Not a Network Address: The Authority Split TIPTOP Has to Preserve
One entity can be discovered under a temporary tag, receive several provisional designations, gain a permanent number and acquire a name years later. A route cannot afford to mistake any one of those labels for proof of where a packet should go.
History
The Route the Sender Tried to Choose: How IPv4 Source Routing Lost Its Default Trust
IPv4 once carried a small, mutable itinerary inside the packet itself. The history of source routing is the history of how that sender-supplied path changed from a protocol feature into an explicitly configured exception.
IETF
A G-ACh Advertisement Shares Peer State Without Delegating Local Configuration Authority
A peer can truthfully advertise a capability and still have no authority to decide what the receiving node should do with it. RFC 7212 makes that distinction operational: advertisements cross the link, but authorization, interpretation, freshness and the consequences of a local…
History
The Peer Returned a DNS Address. It Had Not Proved Names Would Resolve: RFC 1877
The useful answer in a 1995 dial-up exchange could begin with a deliberately useless address. A PPP client placed zero in an IPCP name-server option precisely so the remote peer would reject the value and suggest another. That suggestion could become negotiated configuration only…
Story
ARIN Closed Its Mailing-List Suggestion With a Prompt, Not a Reach Result
ARIN preserved voluntary choice when it declined to enroll every General Member in a governance mailing list. Its August closure record proves that a prompt reached the membership-request form. It does not yet show how far the list reaches across member organizations.
IETF
JOSE Sends Two Algorithms Toward Deprecation Without a Clock for Local Exceptions
The JOSE Working Group has asked the IESG to publish a draft that would deprecate `none` and `RSA1_5`. The document draws a sensible line between a safer common default and narrowly retained local choice. The unresolved operating question is how a permitted exception stops…
CASE FILE
A Deprecation Date Is Not a Client Migration Plan
The response is still `200 OK`, but it now carries a date after which the resource will be deprecated. That date can warn a client. It cannot identify who owns the client, whether a replacement preserves its assumptions, or what must be true before the old endpoint can be…
History
The Address That Meant Everyone: How IPv4 Broadcasts Chose Ones Over Zeroes
IPv4 did not gain broadcasting through a new flag. It gained it by teaching hosts and gateways that some destination values did not name one machine at all. A field of ones came to mean everyone within a scope, while receivers carried an awkward obligation to understand the…
IETF
A Dynamic MPLS-TP Control Plane Does Not Own Every LSP
A green signaling adjacency can coexist with a broken data path, while a working static LSP can exist without any control plane at all. RFC 6373 therefore treats automation as a governed operating choice, not as automatic ownership of the transport network.
IETF
Radia Perlman and the Appointed Forwarder That Had to Stop Forwarding
A TRILL switch may still hold the appointment for a VLAN while its safest legal action is to drop the native frames it would normally handle. That is not a contradiction in the standard. It is the moment when recorded authority and permission to act must be read as separate…
Story
AFRINIC Whois mnt-domains Authorizes Reverse-Domain Records, Not DNS Service Operation
A database key can authorize the creation of a reverse-domain record while every DNS query to the supposed service still times out. In the AFRINIC Database, `mnt-domains` identifies a maintainer with authority over child domain-entity creation. It is evidence about registry…
NANOG
The Mailing List Is an Operations Room, Not a Legislature
NANOG's mailing list is valuable because operators can expose a fault, compare evidence and correct a diagnosis in public. That practical authority should not be confused with permission to speak for networks whose operators did not join the thread.
CASE FILE
The IAB Gave Post-Quantum Authentication Evidence Another Week. It Still Needs a Chain of Custody
The extended deadline invites one more week of operational evidence. The harder task begins after a paper arrives: keeping measurements, disclosure choices, workshop synthesis and eventual standards work from collapsing into one unsupported claim.
IETF
An MPLS Echo Response Is Not Bidirectional Proof Until the Requester Validates the Return Path
A valid echo response may come from an intermediate point reached when the probe’s TTL expires. Its arrival proves that a responder answered from that position; it does not prove that the intended reverse LSP exists or carried the response.
History
The Bit That Made Routers Report Their Limits: IPv4 DF and Path MTU Discovery
One IPv4 flag began as a prohibition: do not split this datagram. Path MTU Discovery turned that refusal into a measurement loop. An oversized packet would be discarded, a router would report the narrow link, and the source would learn what the path could carry—provided the error…
History
Readable Without a Parser Did Not Mean Safe to Parse: RFC 1874
In 1995, one MIME label tried to preserve two truths about the same structured document. A person without SGML software might still read its general meaning; a machine with SGML software might interpret far more than the visible lines. RFC 1874 called the first case `text/sgml`…
Story
RIPE assignment-size Describes Aggregated IPv6 Assignments, Not Active Subscribers
A `/46` contains 1,024 possible `/56` prefixes. When a RIPE Database entity pairs that aggregate with `assignment-size: 56`, the arithmetic is exact—but the tempting subscriber count is not. The field records the size used for End User assignments inside an aggregate…
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