Topic
Consensus Capture
Within the Topic facet, Consensus Capture 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.
History
Best Practice Forums and the Problem of Institutional Self-Citation
The Internet Governance Forum's Best Practice Forums were created to turn an annual conversation into useful, durable knowledge. Their collective authorship is a strength, but it is not a method of verification. A report can draw on open meetings, quote many stakeholders and pass…
History
IGF Dynamic Coalitions: Output Without Ratification
Dynamic Coalitions are among the Internet Governance Forum's most productive institutional experiments. They keep specialists working between annual meetings, assemble research, draft principles, build practical guides and advocate for neglected issues. Their openness and…
History
National IGFs and the Risk of Borrowed Branding
A national Internet Governance Forum can do work that a global meeting cannot. It can hear arguments in local languages, connect network failures to domestic institutions, expose regulators to affected communities, and give small organizations a place to meet companies and…
History
The Multistakeholder Advisory Group's Appointment Chain
The Internet Governance Forum's Multistakeholder Advisory Group is designed to contain different regions, sectors and forms of expertise. That diversity improves the annual programme, but it does not answer a more basic institutional question: who authorised each person to help…
History
Athens 2006 and the First IGF Agenda
The first Internet Governance Forum did not merely schedule conversations. It made an early judgment about which disputes could be placed together on a global stage without destroying the experiment. Openness, security, diversity and access became its principal vocabulary.…
History
Why the IGF Was Useful Because It Was Powerless
The Internet Governance Forum has no treaty-making chamber, no regulator, no police, no power to allocate Internet resources and no authority to order a platform, network or government to change course. This absence is often described as its central weakness. It was also a…
History
Working Group on Internet Governance: Forty Members, No Global Electorate
The Working Group on Internet Governance did something unusually difficult in 2004 and 2005. It gave a politically divided field a common vocabulary, widened Internet governance beyond names and addresses, catalogued neglected public-policy questions and proposed a forum in which…
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
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
Code Sprint Participation Is Not Protocol Mandate
Code can prove that a specification is implementable, expose ambiguity, demonstrate interoperability, and falsify confident claims made in a meeting. It cannot prove that absent operators can deploy the result economically, that affected users accept its consequences, or that the…
IETF
Remote-Only IETF and the Redistribution of Influence
Moving the IETF online in 2020 removed flights, visas, hotels, and a physical room from the price of joining a meeting. It did not remove scarcity. Influence was redistributed toward people who could secure synchronized time, quiet space, reliable connectivity, employer…
IETF
The IETF LLC and the Professionalisation of a Volunteer Institution
The 2018 creation of the IETF Administration LLC moved budgets, contracts, fundraising, staff, and legal risk into a dedicated corporate body governed by a small board and run by professional executives. It gave the IETF the capacity to execute at scale. It also made the…
IETF
ISOC’s Legal Shell Around IETF Autonomy
For more than a quarter-century, the Internet Society gave the Internet Engineering Task Force something a volunteer standards community could not easily create for itself: legal standing, insurance, bankable contracts, fiscal administration, and a place inside which liability…
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…