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
8,859 articles
Story
ARIN Waited for a Geofeed Standard. Its RDAP Help Still Does Not Claim It.
Two years ago ARIN tied a community request to a visible trigger: once the common RDAP geofeed standard was accepted, three named product surfaces would change. The standard is now RFC 9877. The useful question is no longer whether the IETF will finish the vocabulary, but how an…
IETF
A Join Priority Is Not an Enrollment Decision Record
A proposed RPL option lets a low-power mesh distribute how much capacity it has for new devices. The number can rise as it moves away from the root, and its maximum value can switch Join Proxy service off. That is efficient coordination, but a Pledge seeing a high priority cannot…
History
Demi Getschko and the Country Code That Arrived Before Brazil Spoke TCP/IP
On 18 April 1989, `.br` entered the DNS root while Brazilian academic networks were still speaking BITNET, HEPnet and other protocols. Demi Getschko's part in that sequence reveals a neglected infrastructure skill: securing a durable name, accepting responsibility for it and…
IETF
A Green Check Without Its Schema Is Not Evidence
Revision 00 of an expired NETMOD draft proposed two ways to validate YANG `anydata`. The interesting divide is not pass versus fail, but whether the receipt preserves the schema context and whether constraint checks ran at all.
Story
BCAP’s Prize Entry Preceded Training. Its Outcome Receipt Has Not.
The WSIS Prize submission window closed two days before BCAP’s published professional-development start window opened. The project won in July and is still listed as ongoing through 2027. The award may be sound; the public record still needs to say which finished phase and which…
History
One PPP Link, Two SNA Permissions: What RFC 2043's Open State Could Not Prove
A line can be up while the thing an operator cares about is still down. RFC 2043 made that distinction unusually concrete: on one PPP link, SNA with LLC 802.2 and HPR SNA without LLC were admitted by different control protocols. Each could open without speaking for the other, and…
CASE FILE
The Private Number Was Valid. The Instruction Was Still Unowned: RFC 9752
A vendor payload can cross a stateful PCEP session with a real enterprise number and perfect framing while leaving the decisive questions unanswered: who published its meaning, what the PCC was allowed to do, what the device installed, and what the traffic experienced.
IETF
ACTN’s Abstract Topology Is a Policy View, Not a Physical Inventory
An optical controller may show a coordinator that two packet edges could be connected while withholding the fibres, wavelengths and vendor-specific constraints underneath. That abstraction is not a defective inventory. It is a deliberately governed view. The evidentiary mistake…
IETF
A Signed Epoch Marker Is Not a Universal Clock
Remote attestation needs a way to reject stale evidence even when an attester has no dependable real-time clock. The RATS Epoch Marker proposal supplies a signed coordinate from an Epoch Bell, but the signature proves only what that Bell emitted. It does not make the marker a…
History
The Next Macroblock Could Start Cleanly. The Picture Was Still Damaged: RFC 2032
RFC 2032 gave an H.261 receiver a deliberate place to resume after packet loss and a compact way to ask for corrective action. Neither mechanism certified that the missing picture returned, that prediction state was right, or that a viewer saw an uninterrupted frame.
History
255 Was a Workshop Tag, Not a Private BGP Namespace: RFC 2042
Two unfinished BGP attributes could both wear the number 255 and still mean entirely different things. That was the point. In RFC 2042, the value marked work under development; public identity began only when an attribute was documented and IANA assigned it a unique code.
Story
APNIC's ASPA Interface Checks Observed Paths. A Standby Provider Leaves No Path to Check.
APNIC has built a sensible safety rail into its new ASPA interface: suggest providers from visible routing data, then show how an edit would affect paths that BGP observers can see. The awkward provider is the one hired precisely not to be visible yet. A standby link turns the…
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…
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