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,999 articles
IETF
Default Reject Turns Missing EBGP Policy from Silent Authority into an Explicit Failure
An external BGP session can be established while its authority to receive or advertise routes remains undefined. RFC 8212 changes the default at that boundary: without import policy, accept no routes; without export policy, announce none. The leadership question is not whether a…
ICANN
What Evidence Record Should a Community Priority Evaluation Applicant Build?
A criterion-linked record is more useful than a pile of endorsements.
CASE FILE
Sixty Names Were Defendants; the Statute Still Defined the Claim: Harrods v Sixty Internet Domain Names
The caption did something unusual: it named sixty domain names as defendants. That procedural choice made a dispute over the Harrods name look, for a moment, like a dispute over things rather than people. The Fourth Circuit’s answer was narrower. The names could be before the…
History
The Chain That Made a Public Key Believable: PEM Certificate Management
A public key does not identify its owner by itself. RFC 1422 addressed that gap for Privacy Enhanced Mail by specifying certificates, certification authorities, validation paths, and revocation information—the institutional machinery needed before a relying party could treat a…
NPNOG
After the RPKI Panel: Did npNOG’s 2020 Routing-Security Moment Survive the Screen?
The official page does not, by itself, prove that entities created ROAs, deployed validation or changed production routing policy afterwards.
Story
ARIN’s RDAP Notices Describe the Lookup Service, Not the Network’s Operating Policy
The warning labels attached to a registry lookup travel with the answer, but they do not belong to the network named inside it. ARIN’s top-level RDAP notices tell a reader how the lookup service may be used, where suspected inaccuracies can be reported and who claims copyright in…
Story
The RIR Governance Draft Is Public. Its Approval Path Is Still Unfinished
The 1 September release changes the evidence state around the proposed RIR governance framework: readers can now inspect version three, compare it with version two and read the stated rationale. Publication is a verifiable milestone, but it is not approval, adoption or legal…
IETF
Enhanced uRPF Lets an Operator Admit Feasible Source Paths Without Trusting Every Route
A valid packet from a multihomed customer can arrive on a link that the receiving router would not choose for the return journey. Strict reverse-path forwarding may discard it; loose checking may accept any routed source. RFC 8704 defines a narrower middle ground: build an…
IETF
The Prefix Arrived Before the Query: How RFC 9872 Changes NAT64 Discovery
An IPv6-only host that must reach IPv4 services needs to know which IPv6 prefix its network uses for address synthesis. RFC 9872 turns that knowledge into an access-network signal: learn PREF64 from Router Advertisements first, and use DNS discovery only when that signal is…
Story
APNIC prop-174 Turns an Abuse Mailbox into a Policy Control Surface
APNIC’s prop-174 would move abuse-mailbox operations from implementation practice into explicit policy. That can make contact duties measurable, but it also makes delivery, filtering, triage and response records part of a chain that may eventually reach membership consequences.
Story
LACNIC’s RDAP Conformance List Identifies Response Specifications, Not Network Authority
An RDAP response can look like a compact certificate of power: it carries a registry name, a range, a handle, a hierarchy link and a row of terse technical tokens. But the tokens in `rdapConformance` answer a narrower question. They describe the specifications used to build the…
History
The Pointer That Was Never Out of Band: TCP Urgent Data
TCP urgent data is a small control surface with a long history. The URG flag makes a 16-bit urgent pointer meaningful, but RFC 793 described the boundary it marks in two contradictory ways. That ambiguity crossed from the specification into implementations and application APIs.
IETF
ZONEMD Lets a Secondary Verify the Zone After the Transfer Ends
A completed zone transfer proves that a delivery procedure finished. It does not, by itself, prove that the receiver assembled the exact zone the publisher intended. ZONEMD adds a digest over the zone as a whole, creating a verification boundary after transport and before a…
IETF
The Bitmap Says a UDP Option Appeared—not What It Did: RFC 9870
RFC 9870 gives IPFIX exporters a compact way to report which UDP Option kinds appeared in a Flow. Its bitmaps are useful precisely because their claim is narrow: they preserve observed presence, not a packet history, a receiver’s processing decision or an application outcome.
IETF
DNS TCP Fallback Is a Capacity Path, Not an Exception
A resolver can pass every small UDP health check and still fail the first answer that matters. When a response is truncated, correctness moves onto TCP; listener capacity, connection state and middlebox policy then become part of DNS availability.
Story
AFRINIC Constituted Its Appeal Committee. The Appointment Record Now Has a Fixed Term
AFRINIC’s 28 August announcement names five Appeal Committee members and gives their appointments an immediate effective date and a 31 December 2026 endpoint. That creates a defined public mandate, while leaving future case handling to the committee and the applicable PDP rules.
CASE FILE
CIRA’s 20-Endorsement Threshold Has a Separate Conflict Test
CIRA’s September endorsement window gives members a route onto the election ballot. The twenty-supporter threshold works alongside conflict-of-interest rules that treat the two nomination routes differently.
Story
A Failed RIPE Database Update Can Still Change Records
RIPE NCC's documentation describes an update message whose entities can finish differently. The useful response is therefore not just a verdict on the message: it is an account of the changes already made, those rejected and those the caller still cannot confirm.
Story
LACNIC’s IPv4 transfer market and the price of scarcity
IPv4 exhaustion does not end allocation politics. It changes the place where they happen: from the distribution of a free pool to the rules governing transfers of resources that are already held.
IETF
Maciek Konstantynowicz and the Benchmark Result That Was Not a Service Guarantee
A network benchmark earns its value by saying exactly what it measured. RFC 9971 makes that discipline explicit: its MLRsearch result is a bounded result from stated trials and goals, not a transferable promise about every customer path, application or production hour.
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