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
4,666 articles
Story
RIPE’s IPv6 PI Draft Reserves Growth Space. Partial Transfers Can Make It Unusable.
RIPE’s current IPv6 PI proposal tries to make future growth easier by reserving a larger nibble-boundary envelope around a new assignment. Its own impact analysis identifies the catch: if the assigned block can be transferred in pieces, the untouched reservation may no longer be…
Number Resource Society
Datatokni ForoyaTele: What AS210417 Shows—and What It Does Not
Datatokni ForoyaTele: What AS210417 Shows—and What It Does Not 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 follow. The…
History
A Non-Zero Priority Let One Neighbour Use 4,352 Bytes: RFC 2019
RFC 2019 did not discover an end-to-end path. It extracted one useful fact from a bridge’s rewrite of an FDDI frame, then spent that fact on a tightly bounded permission: larger unicast to one neighbour while the shared network stayed conservative.
History
Danny Cohen and the Byte-Order War the Network Could Not Win
Four bytes can describe one number and still tell two incompatible stories. Danny Cohen saw that the useful question was not which machine deserved to prevail, but what every machine had to promise at the boundary.
History
The Tunnel Rebuilt the Header from What It Chose to Remember: RFC 2004
RFC 2004 did not put an IPv4 packet inside a second complete IPv4 envelope. It edited the packet’s own header for the tunnel journey, tucked the displaced fields into an eight- or twelve-octet forwarding slip, and made the exit responsible for putting selected facts back. The…
IETF
The Port Won the Election. Its Services Still Owed Receipts: RFC 9786
A single access interface can carry bridging, routed VPNs, IRB state and customer expectations at once. RFC 9786 deliberately elects that interface as one Port-Active unit. The gain is deterministic active/standby control; the liability is equally concentrated. A common…
ICANN
ICANN’s Authority Is Layered, Contractual and Procedurally Bounded
ICANN coordinates critical Internet identifiers through a stack of instruments rather than through a single sovereign mandate. Its corporate documents define a limited mission; contracts give it leverage over many registries and registrars; affiliates perform delegated…
IETF
RFC 9945’s Moderator Team Is Not Its Activation Receipt
The RFC is published. The team exists. A public repository contains procedures. None of those facts, taken alone, answers the question RFC 9945 itself makes decisive: which exact procedures did the IESG approve, and when did the new moderation regime take effect?
IETF
The Interface Still Said Up While the Carrier Was Down
A quiet status light can be the most dangerous signal in a recovery room. Revision 19 of the IETF's common interface-extension draft deliberately permits an interface to remain reported as up while a short down timer is running beneath it. That is useful engineering, not…
Story
LACNIC’s IPv6 Clock Subtracts 210 `/32`s Without Showing Which Fragments Count
IANA’s allocation clock for LACNIC reaches a reassuringly precise answer: 978,428 units of `/32` space remain available. The public rows beneath it supply exactly the 210-unit subtraction that produces that number. Yet most of those fragments are not labelled `available` in…
Story
ARIN Says Sponsors Need 60 Days. Its ARIN 58 Page Is Still Open at 42.
ARIN’s sponsorship page presents an opportunity and a cutoff as if both were current: it is seeking sponsors for ARIN 58, yet says sponsorships must be finalized 60 days before the event. The page served after that boundary needs one more field—a dated status that says what, if…
History
Protocol 4 Is an Envelope Label, Not a Delivery Receipt: RFC 2003
A monitor sees an IPv4 packet from one router to another and reads `4` in the outer Protocol field. That observation is precise but small: it says another IPv4 datagram should follow. It does not name the original sender, validate the inner route or show that the letter inside…
IETF
The Preference Won the Election. It Did Not Prove the Forwarder Was Ready: RFC 9785
An operator can make one EVPN Provider Edge router the obvious administrative favourite. RFC 9785 gives that intention a precise place in the DF election. What it does not give is a shortcut from “preferred” to “safe to carry traffic”. The standard opens a control surface…
IETF
The XML Matched. The Network Did Not
Two configuration documents can be well formed, stable under XML canonicalization and accepted by a validator, yet still fail to describe the same effective YANG data—or any change that a device actually applied. The first NETMOD draft dedicated to YANG’s XML encoding makes the…
History
Dave Täht and the Result That Had to Be Reproducible
A failed run can be more valuable than a beautiful graph. Dave Täht’s work on network latency made that unsettling proposition practical: if the apparatus cannot expose why a result is invalid, the result is not yet evidence.
IETF
DetNet’s ‘Optimal Path’ Is a Governance Decision Before It Is a Calculation
A DetNet controller may be able to calculate several feasible routes and install one of them precisely. The difficult question arrives earlier: who was entitled to decide that latency mattered more than spare capacity, that protection justified duplicated resources, and that…
History
The Message Had an Address, Not the Object: RFC 2017
In October 1996, RFC 2017 gave MIME mail a way to point at an external entity with a URL. Its economy was the point—and the trap. A locator could arrive intact while the content stayed elsewhere, retrieval still needed permission, and neither a declared type nor a matching digest…
ICANN
ICANN’s ITP Contract Has a Release Gate, Not a Date
ICANN’s Board has approved the authority to contract for the next generation of the organization’s publishing platform while concealing several negotiating particulars. That is not unusual procurement hygiene. The more interesting governance fact is that ICANN has also named who…
Number Resource Society
Florian Bauer and AS210833: What the Public Record Can Test About Network Stewardship
Florian Bauer and AS210833: What the Public Record Can Test About Network Stewardship intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences…
IETF
The Message Had One Security Badge. Its Layers Did Not Share One Status: RFC 9787
The comforting part of an encrypted-mail interface is the badge. The difficult part is deciding exactly which bytes are entitled to it. RFC 9787 makes that boundary explicit: one received message gets one cryptographic summary, calculated only from the contiguous protection…
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