Topic
Registry Governance
Within the Topic facet, Registry Governance topic intelligence connects articles that share a specific subject, signal focus, or monitoring theme. The page gives readers a richer path through related reporting, source evidence, market actors, and infrastructure implications, with enough context to understand why the topic matters across company movements, governance decisions, regional exposure, and operational risk. Readers can compare recurring signals, affected organisations, public evidence, market context, service continuity, procurement, competition, compliance, and strategic planning questions behind the subject instead of stopping at a thin list of matching articles. It explains what the topic covers, which infrastructure actors or policies are involved, what evidence supports the coverage, and why the subject may matter for operators, customers, investors, and policy readers.

IETF
NRS Advocacy for Standards Without Standards-Body Sovereignty
Number Resource Society can advocate open IETF-based interfaces and use implementation evidence without pretending that either NRS or a standards body defines operator rights. Recognised registries and authorised providers must implement the specifications; explicit contracts…

IETF
What RIR Policymakers Misborrowed from the IETF
Regional Internet Registry policy processes borrowed rough consensus from an engineering culture in which claims could be tested by independent implementations and rejected by networks that did not deploy them. Applied to compulsory registry rules, the same words lost those…

IETF
BCP Status and the Myth of Universal Consent
Best Current Practice status records a serious IETF judgment: a document has passed the applicable review path and expresses the community's best current technical or procedural thinking. It does not mean every implementer participated, every network deployed the practice, every…

IETF
The RFC That Became Policy Outside the IETF
An RFC can become extraordinarily influential without becoming law. Interoperable implementations, operational dependence, procurement choices, registry practice, and reasoned adoption by public authorities can give technical advice practical force. The danger begins when an…

IETF
Expert Reviewers as Single Points of Policy
Designated Expert review gives IANA access to narrow technical judgment without forcing every protocol extension through a new RFC. The efficiency is real, but so is the concentration: one volunteer can become the practical gate through which a namespace evolves. Legitimacy…

IETF
Protocol Registries and the Quiet IANA Function
Every extensible Internet protocol depends on a ledger of agreed values. RFCs decide who may receive a code point and on what terms; IANA turns those rules into durable, public operational fact. The arrangement works because policy, execution, review and change authority are…

Leaders
Nick Buraglio and the long operational reality of IPv6
Nick Buraglio's public record sits where the IPv6 transition becomes less a slogan than an operating discipline: ESnet-scale architecture, IETF v6ops process, RFC authorship, and the practical language of operators who have to keep networks useful while the industry waits for old…

IETF
Running Code as an Anti-Rhetorical Check
Implementation and deployment can force an IETF proposal to answer questions that elegant prose evades: whether independent systems interoperate, whether operators can diagnose failure, and whether the claimed benefit survives contact with real networks. That discipline improves…

IETF
Rough Consensus Was Built for Protocols, Not Property
Rough consensus earned legitimacy by testing technical objections against architecture, interoperability, implementation, and deployment. That is a powerful method for deciding how networks should communicate. It is not, by itself, authority to cancel, transfer, encumber, or…

ICANN
An ICP-2 for Services, Not Territorial Franchises
A modern successor to ICP-2 should stop treating continental service regions as permanent institutional franchises. It should certify providers against the functions that make one global number system trustworthy: uniqueness, security, auditable stewardship, and the tested…

ICANN
NRS Advocacy for the Exit Option ICP-2 Forgot
ICP-2 imagined migration when a new regional registry replaced incumbent service, and today's reform draft imagines emergency operation when an entire RIR fails. Neither starts with the operator that needs continuity before institutional failure is formally declared. Number…

ICANN
ICP-2 Compliance Without Periodic Recertification
Recognition gave each Regional Internet Registry a durable place in the Internet's numbering system after a demanding launch review. It did not create a routine independent test of whether the capabilities proved at launch still exist. A narrow recertification of continuity…

Leaders
Gaurab Raj Upadhaya and the bounded authority of Nepal's internet institutions
Gaurab Raj Upadhaya's public record is not a simple current-title biography. It is a way to see how Nepal-facing internet exchange work, operator forums, research-network service, global anycast DNS operations, APNIC governance and root DNSSEC trust can turn individual technical…

ICANN
Mutual Aid or Mutual Immunity?
When one regional internet registry cannot reliably operate, its peers should help keep essential services alive. The legitimacy test is whether that help remains temporary, transparent and independently reviewable, rather than becoming a shield against accountability.

ICANN
The RIR Cartel Test
The five regional internet registries must coordinate to keep numbers unique and routing records coherent. That necessity does not answer the harder question: when do shared rules stop protecting interoperability and start protecting incumbents from entry, portability, transfer…

ICANN
Regional Consent After a Registry Fails
When a Regional Internet Registry can no longer govern or serve reliably, the most visible coalition is not necessarily the region. A permanent replacement should rest first on verified authorization from the organizations that operate networks and depend on registry services…

ICANN
The Appeal From ICP-2's Final Decision
An updated registry-governance rule cannot make ICANN's recognition or derecognition decision legitimate merely by calling it final. The affected registry and the networks that depend on its records need an independent, usable route to review, with explicit standing…

ICANN
Interim Service Before Derecognition
The registry system should be able to keep allocations, registration records, reverse DNS, and routing-security services available without first deciding which institution deserves to survive a governance crisis. Transferable continuity must exist before recognition is withdrawn…

ICANN
The Standard of Proof for Registry Failure
A Regional Internet Registry can fail in several fundamentally different ways, yet the emerging rules still risk collapsing service interruption, defective corporate governance, unlawful conduct, and political disagreement into one elastic finding. A credible standard must…

ICANN
Who May Trigger an RIR Derecognition Review?
A governance failure does not become actionable merely because it is visible. Someone must be entitled to place evidence before a competent reviewer and require a response. The evolving ICP-2 replacement gives that initiating power to ICANN, peer registries, and a large coalition…
