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,567 articles
CASE FILE
The Message Continued. The Constraint Went Missing: RFC 9753
RFC 9753 lets stateful PCEP peers keep working when selected entities are optional. That is a useful availability mechanism. It is not evidence that the ignored meaning survived, that the replacement LSP is equivalent, or that forwarding remained safe.
IETF
The Template List Was Present. The Intended Configuration Was Not Yet Proven
Revision 03 of the YANG configuration-templates draft turns list order and ancestor depth into configuration semantics. Reconstructing the intended tree is therefore possible only from a complete, same-version evidence bundle—and even a perfect reconstruction stops before…
Story
AFRINIC’s ccTLD Map Counts 27. Three Require an Address Join.
AFRINIC’s new DNS surface gets the total right, but it does not show the work behind the number. Twenty-four of its 27 ccTLD rows name the registry in a delegated hostname. Somalia, Nigeria and Mali become legible only when their nameserver addresses are joined to AFRINIC’s…
IETF
Immutable to the Client Is Not Immutable in Time
A proposed YANG metadata annotation lets a network-management server identify system configuration that clients cannot change. Its name—`immutable`—is accurate only across a particular control boundary. The server can still create, update or delete the underlying system…
History
Ginny Strazisar and the Gateway Code That Traveled Before the Packets Did
The celebrated packet path began with a less cinematic journey: an engineer arriving at a site where the machine for her software was not yet ready. Virginia “Ginny” Strazisar Travers helped turn internetworking from a protocol idea into installed boundary equipment at BBN…
History
The Clock at the Edge: RFC 2030 and the Evidence Lost When One Reply Becomes Time
RFC 2030 made Internet time small enough for simple devices by preserving the NTP packet while discarding most of the machinery around it. Its warning was architectural: an SNTP client belonged at a leaf, not in the middle of a dependency chain, because one usable reply could set…
History
The Server Was Up. The Website Was Not: RFC 2039’s Missing Layer
In 1996, one short RFC identified a management error that survives every change of tooling: a machine can be measurable, orderly and alive while the service it is meant to provide is failing somewhere else.
IETF
An Uncacheable Attribute Does Not Prove the Client Cache Is Empty
NFSv4.2 is gaining a way for a server to mark a file's data as unsuitable for ordinary client caching. That is useful policy vocabulary. It is not an observation of what any particular client has already seen, retained, revalidated or committed. Operators need both records before…
IETF
A Green YANG Validator Cannot Recover the Requirement NAIM Never Received
NAIM proposes a disciplined relay from natural language to canonical JSON, human review, model context and generated YANG. Its strongest contribution may be showing exactly where confidence must stop: a successful conversion is evidence about one representation chain, not proof…
Story
LACNIC’s BGP Case Counts 368 Route Peers. The Vendor Could Not Produce a Definitive Installation List.
LACNIC’s latest routing-security case is unusually rich in network evidence and unusually poor in application evidence. The route, certificate and attack window can be reconstructed in detail; the vendor still cannot say which installations accepted the malicious update. That gap…
IETF
RTCP Can Carry a Resolution Request, Not an Energy-Savings Claim
A new RTCP feedback format gives a video receiver a precise way to ask for fewer frames or fewer pixels. That is useful running code. It is not an energy meter. The governance problem begins when a standards-compliant request, or the sender’s acknowledgement of it, is promoted…
CASE FILE
The Server Accepted the Message. The User Still Could Not Find It.
RFC 9755 gives IMAP a precise UTF-8 handshake, but a capability banner and a successful APPEND are only the first receipts in a much longer chain from stored octets to usable mail.
Story
AFRINIC's Prefix Checker Can Supply the ASN From BGP. The Verdict Keeps Only the RPKI Time.
AFRINIC's Prefix Checker Can Supply the ASN From BGP. The Verdict Keeps Only the RPKI Time. intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…
History
Karen Sollins and the Delayed ACK That Made Every Packet Appear Twice
TFTP could deliver a file correctly and still damage the network carrying it. In the failure later called the Sorcerer’s Apprentice syndrome, one delayed acknowledgement could start a feedback loop in which every remaining data block and acknowledgement travelled twice. Karen…
IETF
A Planned Boundary Change Needs Two Validation Times
A civic boundary can change at midnight while every address stays physically where it was. The database problem begins earlier: operators need to prepare records for the new administrative reality without pretending that a forecast is already the truth. An active ECRIT…
CASE FILE
The Controller Said Done. The Packets Had Not Testified: RFC 9757
RFC 9757 gives a PCE an experimental vocabulary for coordinating Native IP paths, but its acknowledgements end inside the controller–client conversation. Leadership still needs independent proof that BGP, routing policy, forwarding hardware and live traffic enacted the same…
History
Eight Bytes Drew a Recovery Boundary: RFC 2029 and CellB After Packet Loss
RFC 2029 gave every CellB packet its own spatial address: the first 4×4 cell’s coordinates and the image dimensions. That small repeated header let a receiver resume at a known place after loss, but it did not replace the missing cells or prove that the resulting frame was…
IETF
One MAC Address, Four Spellings: A YANG Draft Redraws the Duplicate Boundary
The proposed rule is easy to miss because nothing on screen has to change. A value can keep the colon, hyphen and letter case that arrived over the wire, while a second, invisible form decides whether another configuration entry is a duplicate.
History
One Agent, Many Machines: RFC 2037 Put the Scope Back into the Name
RFC 2037 treated an index as a local coordinate, not a universal identity: the agent, naming scope and mapping path had to travel with the number.
Story
APNIC Prop-173 Would Make Every Directory Query an Agreement. The Response Would Carry No Version.
An acceptable-use policy can change while the response governed by it remains in a cache for years. APNIC's prop-173 would make ordinary WHOIS, RDAP and web queries subject to a clear, versioned policy and would tell users that querying or using the service means agreeing to…
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