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,791 articles
CASE FILE
The Draft Was New. Its Dependency Had Expired Six Years Earlier
Revision 09 gave an L2VPN snooping draft a fresh date without changing its mechanism. The document can still be useful, but its own import graph shows why leaders must demand an executable dependency receipt before treating standards activity as implementation readiness.
IETF
IETF’s PROBE Revision Admits Its Ping Analogy Misled Both Code and Eyes
A new deployment appendix records an unusually candid standards lesson: a familiar analogy can become an undocumented instruction, first for implementers and then for operators reading the result.
History
The Old Address Fit Inside IPv6. Its Routing Model Did Not: RFC 1888
A twenty-octet address can be placed beside a sixteen-octet one, sliced, tagged and reconstructed. That arithmetic says nothing about whether the route hierarchy survives the move. RFC 1888 recorded this distinction in 1996: its encodings could preserve address bits, while the…
ICANN
Allison Mankin and the Name-Collision Sample That Could Not Prove Its Cause
A root server can record a query for a private-looking name with great precision. The record still cannot say which application produced it, who owns the broken dependency, how many users rely on it or what a future delegation would harm. Allison Mankin’s work on RFC 8023 helps…
CASE FILE
A Proxy-Status Chain Does Not Name the Incident Owner
RFC 9209 can make a failure path legible without making anyone accountable for repairing it. The missing entity is an intermediary fault-handoff matrix: a private governance record that connects each visible or redacted hop to an operator, an escalation clock, retained evidence…
Story
ARIN Adopted an Amended IPv6 Task Force Charter. The Public Index Does Not Show It
ARIN’s Board minutes record the creation of an IPv6 Task Force, an amendment that shortened its planned life, and three people who volunteered to do the work. What the public record does not yet supply is the operative text that joins those facts into a mandate. The missing…
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…
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