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.

IETF
A Proposed Charter Is Not a Working Group Mandate
A document browser usually rewards the highest revision number. A governance register cannot. On 27 August 2026, the IETF showed DAWN's first charter proposal and NETCONF's proposed recharter under review at the same time. The newer text would create authority in the first case…

ICANN
ICANN Broadened the Project Fund Before Fixing Its Qualification Rule
A capital request can look complete before it is governable. Give it a fund name, an owner and an estimated cost, and the card resembles an authorization. Yet the decisive field is still missing: which published rule made this work eligible for exceptional funding rather than the…

IETF
An IETF Process Variance Does Not Silently Rewrite the Rule
The most dangerous exception in a governance system is not the red waiver attached to one named case. It is the value copied from that waiver into the default column. The first record still invites questions: which specification, which requirement, whose recommendation, what…

Story
Between Listening and the Map: LACNIC’s Missing Input Trace
LACNIC’s public account names a collective planning process and a route from listening to SWOT and a final strategic map. What the checked documents do not expose is the privacy-safe join that would let a reviewer follow one issue from source class and channel through synthesis…

IETF
IETF’s 2418bis Draft Adds an Exit State for Adoption
The dependency register showed a green `WG Document` badge beside a draft that no longer attracted editors or review. When the working group removed the draft from its active work set, the register replaced green with grey and wrote “proposal rejected.” That last phrase was not…

ICANN
The Breach Notice Stayed Itself: Employ Media, ICANN and the .JOBS Settlement
The contract did not require Employ Media to win before the threatened termination stopped. It required the registry operator to file arbitration and request a stay at the same time. On 3 May 2011, that procedural act kept `.JOBS` in place while ICANN and its operator argued over…

Leaders
Aaron Wendel and What Two Failed ARIN Proposals Reveal About Operator Power
Fourteen years apart, two public tallies put Aaron Wendel on the losing side of consequential debates about Internet number resources. The defeats are more revealing than a conventional success story: they show how practical operating knowledge enters policy, how commercial…

NPNOG
Who opens the room? What npNOG-10's welcome order can—and cannot—prove
The first twenty minutes of a conference can reveal institutional relationships. They cannot, without supporting records, tell us who held the decisive authority.

CASE FILE
An RFC Number Does Not Mean the IETF Approved It
A compliance register that records only “RFC 8729” looks precise. It is not. The number identifies a durable document, but it conceals that this particular RFC is an IAB-stream informational statement rather than an Internet Standard. When a single column makes every RFC look…

CASE FILE
An IANA Code Point Is Not a Licence to Deploy
The Internet needs common numbers, strings and names so that independently built systems can understand one another. IANA protocol-parameter registries supply that shared vocabulary. Their authority is real, but deliberately narrow: a registry entry can settle which value carries…

CASE FILE
Empowered without a vote: what the IGF Leadership Panel can actually command
The IGF Leadership Panel was designed to carry messages, recruit senior attention and find resources. Appointment by the UN Secretary-General gives that work institutional access. The operative rules still leave the annual programme with the MAG, execution with the Secretariat…

ICANN
The drafting room behind root advice: who controls the RSSAC Caucus pipeline?
Most RSSAC reports are built in a body far larger than the committee that formally approves them. The current rules make that division visible: experts may propose, research and draft; root server operator representatives keep the gates for admission, scope, amendment and…

ICANN
The security advisers the Board appoints: where SSAC authority stops
Three dates describe the gate. On 25 November 2025, an internal membership committee recommended three candidates. On 10 December, SSAC approved them by consensus. On 25 January 2026, the ICANN Board appointed them. Expertise entered through a committee of incumbents and acquired…

Story
AFRINIC appeal panel remains unnamed after deadline
AFRINIC sought nominees for three seats on a five-member appeals panel. Ten days after the deadline, its live page still published no current members.

CASE FILE
The coalition that spoke for operators: who authorized TCCM at WSIS+20?
TCCM placed registry and infrastructure operators inside the WSIS+20 consultation record with unusual persistence. The record shows who spoke, which organizations endorsed two important submissions and where the final United Nations text matched the coalition’s requests. It does…

Story
APNIC's SIG Review Lists Twelve Changes Before It Has Decision Text
Twelve headings can make a governance review look nearly finished. They can also hide the one thing a consensus call must actually decide: the precise rules that will replace the current ones. APNIC's July SIG Guidelines draft has diagnosed a connected set of problems; its next…

Story
APNIC's Impact Assessments Leave the Both-Pass Outcome Undefined
The word `nibble` will appear twice on APNIC 62's policy agenda. One proposal would move the minimum IPv6 allocation from `/32` to `/40`. The other would leave `/32` untouched and align a larger, already-validated request. A shared hexadecimal convenience hides two different…

CASE FILE
A Verified RFC Erratum Corrects the Record Without Rewriting It
An RFC erratum can identify a real defect, supply corrected wording and be verified by the responsible parties. It still does not silently replace the published specification. That separation lets implementers learn from mistakes while preserving the text the community actually…

Story
AFRINIC draft keeps emergency Board policy alive even after rejection
Proposed Articles 11.4 and 11.5 would preserve a Board power to implement an urgent number-resource policy before the ordinary public process. The next policy meeting could reject it, but actions already taken would remain valid.

Story
AFRINIC draft keeps a Board veto over ten-member AGMM proposals
Article 7.2A would require support from ten Resource Members in Good Standing before a proposal reaches AFRINIC's annual meeting. Even then, two-thirds of all Directors could keep it off the agenda, provided they give written reasons.
