Topic
Institutional Legitimacy
Within the Topic facet, Institutional Legitimacy 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.
ICANN
ICANN’s Alternative-Name Test Stops at Technical Feasibility
ICANN has opened public comment on a model for linking a gTLD to the same string in alternative naming systems. The initial report says the arrangement can be technically safe if one controller and one coherent source of truth govern every copy of the name. That is a demanding…
IETF
The IETF Moved Its Secretariat Inside, Not Its Standards Authority
From 1 August, the IETF Secretariat is organised as two teams inside the IETF Administration LLC, after an April transition from a conventional outsourced service to an employer-of-record arrangement. The change shortens the administrative chain, but the constitutional line…
Story
AFRINIC's New Committee Has Five Votes and Three Expiry Dates
AFRINIC has filled a governance body with five voting members chosen through two different routes. The more important design feature may be the calendar: its seats do not all expire together, and its advice cannot bind the people who receive it.
ICANN
ICANN Has an Application Count, Not Yet a String Count
ICANN closed its 2026 new-gTLD window with more than 1,600 primary applications and more than 1,100 replacement-string options. Those figures describe the queue at submission, not the final set of names that will proceed through evaluation.
History
The Core That Had to Stop Being the Core: EGP and the Invention of Autonomous Systems
The early Internet did not decentralize by pretending that every network agreed. It learned to survive disagreement. The Exterior Gateway Protocol drew a boundary around what one routing administration could keep private and what it had to tell its neighbours. That boundary made…
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…
History
The Web CERN Chose Not to Own: How a Laboratory Designed Its Own Exit
The World Wide Web did not become universal merely because it was invented at a famous laboratory. It became portable across institutions because its common machinery was kept small, its specifications were public, its clients escaped one workstation, and CERN eventually removed…
CASE FILE
DNSSEC Can Prove Absence Without Deciding Entitlement
A signed negative DNS answer can establish that a name or record type was absent from a particular signed zone during a bounded validity period. It cannot establish why the entry is absent, who deserves the label, whether a registrar should create it, or whether an Opt-Out…
History
The Day the Old Protocol Lost Its Network: The 1983 TCP/IP Cutover and the Limits of Technical Authority
On 1 January 1983, an ARPANET host that still depended on NCP faced a new fact: the network beneath it could stop servicing the old protocol. The famous cutover mattered not because a memo became universal law, but because a disclosed rule reached an execution boundary whose…
History
Where the Network Stopped: The IMP, the Host, and the First Price of Shared Correctness
ARPANET’s Interface Message Processor made packet switching operational by putting substantial machinery into a dedicated subnet. It also made a harder problem visible: infrastructure can carry, check, meter and protect communication without possessing the knowledge required to…
History
When One Router Announced Everyone’s Network: AS7007 and the Failure of Unchecked Trust
When One Router Announced Everyone’s Network: AS7007 and the Failure of Unchecked Trust intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences…
History
When the First Network Became Replaceable: ARPANET’s Retirement and the Internet That Continued
ARPANET did not take the Internet with it when it was retired in 1990. That was not because the pioneering network had become unimportant. It was because its most important function—making unlike networks communicate—had already escaped the machinery and institution that first…
History
The Window That Learned Restraint: How TCP Stopped Congestion Collapse Without a Traffic Authority
The Internet's answer to its first congestion crisis was not a controller above the network. It was a new discipline inside every sender: learn the path from acknowledgements and loss, increase carefully, and retreat before retransmissions turn shared capacity into useless…
History
The Worm That Needed a Switchboard: How the 1988 Internet Built CERT Without Giving It Command
When the Internet’s first great emergency arrived, its most effective institutional answer was neither a central operator nor a security sovereign. It was a small, trusted point of contact built to make independent operators faster and better informed while leaving their…
ICANN
ICANN’s 1,600-plus gTLD applications still face the payment gate
ICANN closed its 2026 application window with more than 1,600 primary gTLD applications, but that headline is not yet the final field. Full evaluation fees must be received under a rule whose baseline falls on 19 August and whose later-invoice exception can extend individual…
Global Institutional
The UCIe promise for chiplets depends on what lies beyond the link
UCIe has defined a die-to-die interface that reaches 64 GT/s and now spans 3D packaging, raw traffic and whole-package management. The decisive test will be whether these rules sustain multi-vendor products when power, thermals, manufacturing yield, software, security and…
Global Institutional
UCIe's chiplet promise depends on engineering and accountability beyond the link
UCIe has pushed the die-to-die interface to 64 GT/s and added 3D packaging, raw data transport and whole-package management. The real test is whether these rules can support multi-vendor products when power delivery, thermals, yield, software, security and accountability still…
Global Institutional
UCIe’s chiplet promise will be decided beyond the link
UCIe now defines a die-to-die interface reaching 64 GT/s and covering 3D packaging, raw traffic and package-wide management. Its market value depends on whether these rules can support multi-vendor products while power, thermal design, yield, software, security and liability…
Global Institutional
UCIe’s chiplet vision will be decided beyond the link
UCIe defines die-to-die links reaching 64 GT/s and now covers 3D packaging, raw traffic and package-wide management. Its real test is whether multi-vendor products can succeed while power, heat, yield, software, security and responsibility remain outside the standard.
Global Institutional
UCIe’s chiplet promise extends beyond the link
UCIe has defined a die-to-die interface capable of 64 GT/s, 3D stacking, raw traffic and package-wide management. The decisive test is whether those rules enable multi-vendor products while power, thermal design, manufacturing yield, software, security and contractual…