Region
Global Internet Governance
Global Internet Governance regional intelligence explains how companies, people, policy moves, network operations, investment signals, data centre demand, telecom execution, and market constraints shape infrastructure delivery in the same geographic market or governance area. The page connects published coverage with evidence, regional actors, operating dependencies, market context, and customer or regulatory exposure that may otherwise sit across separate topic or company pages. Readers can compare who is active, which signals are backed by public evidence, how local execution risk connects to broader internet infrastructure strategy, and what changes may affect customers, partners, regulators, or capital planning. Readers can understand the geography, the relevant infrastructure sectors, the public evidence base, and the practical questions that make the regional page more useful than a short listing of articles.
History
The Tunis Agenda's Paragraph 72 and the Forum That Could Not Decide
The Internet Governance Forum was not born with a defective version of regulatory power. It was designed without that power. Paragraph 72 of the 2005 Tunis Agenda gave the new forum a wide agenda: discuss public policy, connect institutions, exchange evidence and practice, advise…
History
Geneva 2003: The Compromise That Deferred the Authority Question
The first phase of the World Summit on the Information Society did not decide who held final authority over the Internet. It made a different bargain. Governments received an express statement that policy authority over Internet-related public policy was a sovereign right of…
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
Standards Capture Is Measured in Implementations, Not Attendance
A crowded standards meeting can still produce an outcome whose authorship, patent position, code, and deployment are controlled by a narrow commercial interest. A sparsely attended meeting can produce a genuinely independent protocol if objections are answered, separate code…
IETF
Security Area Urgency and the Sunset Problem
Security standards often have to move before the evidence is complete. A newly practical attack, a compromised primitive, or a change in adversary capability can make delay more dangerous than an imperfect first response. That urgency is legitimate. It is not a reason to let the…
IETF
The IAB's Architectural Voice and Its Democratic Limits
The Internet Architecture Board is valuable because it can look across protocols, research, standards areas and institutional boundaries at risks that no single working group owns. That panoramic competence does not make it a legislature for the Internet. Its members are selected…
IETF
The Appeal That Takes Longer Than the Implementation
An IETF appeal can be procedurally available and practically late. RFC 2026 gives an objector routes through working-group leadership, Area Directors, the IESG and the IAB, yet it sets no general maximum for a decision and does not give a filing automatic suspensive effect.…
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…
IETF
The Patent Disclosure That Arrives After Consensus
A patent disclosure can be formally public and still arrive too late to make consensus informed. By the time a working group has selected an architecture, editors have stabilized the text, implementers have written code, and purchasers have planned products, a newly visible claim…
IETF
Humans, Not Companies—Until Employers Pay the Time
The IETF is right to ask entities for individual engineering judgment rather than corporate votes. Yet individual participation is a rule of conduct, not evidence that organizational power has disappeared. Employers finance working time, travel, laboratories, legal advice, patent…
IETF
RFC 2026 and the Rights of an Objector
The IETF gives a technical objector something more serious than a right to speak and something less powerful than a veto: a route from working group chairs to Area Directors, the IESG, and the IAB. The route can expose error, but its internal hierarchy, procedural discretion, and…
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…