Skip to main content

Primary Domain

Infrastructure

Within the Primary Domain facet, Infrastructure intelligence groups reporting by primary domain so readers can follow a focused area of internet infrastructure, governance, connectivity markets, or digital capital. The page brings together related articles, public evidence, institutions, companies, people, regional exposure, operating dependencies, and market context that may otherwise sit across separate category pages. It explains the domain, the likely actor class, the market or governance context, and the source material readers should use when comparing signals. Operators, analysts, and governance readers can see how the same domain appears across events, profiles, market shifts, public-source evidence, regional dependencies, and longer-cycle infrastructure decisions over time.

A resilient field controller rebuilds a protected Group OSCORE context through a cyan recovery ring while a separate amber application-control path remains deliberately gated.

CASE FILE

After a Reboot, “Secure” Must Not Mean “Resume”: RFC 10021 and Group OSCORE Recovery

A controller can regain a safe cryptographic footing after a power loss without regaining permission to continue the process it interrupted. RFC 10021 makes that distinction operational: restore the security context first; decide separately whether anything should resume.

Sep 1, 2026
Home buyer checking property listings while broadband connectivity is shown across a UK residential neighbourhood

Europe and Middle East National Telecom Trends

Slow broadband deters UK home movers, survey finds

Hyperoptic’s survey suggests broadband is being checked before a move, raising the value of clear availability and fast activation.

Sep 1, 2026
RFC 1274 editorial illustration: an optional attribute tile rests within an existing schema card, while a mandatory-change tile begins a separate class behind a glass boundary.

History

An Optional Attribute Could Extend a Class. A Mandatory One Had to Start Another: RFC 1274

An early directory needed a common vocabulary without turning every local requirement into a universal decree. RFC 1274’s answer for COSINE and Internet X.500 pilots was neither a frozen list nor permission for every site to reuse the same name privately. It made a more careful…

Sep 1, 2026
Three abstract blue service modules joined by a line that passes through an amber correction node, a distinct verification ring and a bright secured final module.

Story

RIPE NCC Fixed a Cross-Service Vulnerability. The Remediation Needs a Chain Receipt.

“Fixed” is a useful word only when a reader can tell what changed its meaning. RIPE NCC’s June account of a multi-service vulnerability disclosure makes that distinction unusually visible. It describes several issue categories across more than one service, and it also says that…

Sep 1, 2026
Two unbranded signature seals pass through separate cyan and amber inspection channels before a closed amber policy gate and vault.

CASE FILE

The Hybrid Signature Arrived. The Verification Rule Still Had to Be Chosen: RFC 9955

Two signature components can travel together without forcing every receiver to treat them as one indivisible verification event. RFC 9955 makes the distinction useful: a hybrid artifact records a design choice; the receiver's verification rule still decides what was actually…

Sep 1, 2026
AI editorial portrait of Qin Wu beside three YANG revision paths converging on one stable module identity.

IETF

Qin Wu and the Registry Rule That Had to Catch Up With Practice

The same YANG module name appears three times in IANA’s register, attached to three dates and one XML namespace. That is not a uniqueness failure. It is the evidence needed to distinguish a stable identity from the revisions that change inside it.

Sep 1, 2026
RFC 1262 editorial illustration: an early-1990s research workstation sends cyan observation paths toward a copper operational boundary before abstract remote network clusters.

History

The Measurement Needed Permission Before It Became a Result: RFC 1262

In 1991, the Internet Activities Board gave researchers a deliberately unromantic answer to a worthy ambition. Measuring the network was critical to its development, evolution and deployment planning; it could also disturb the very operation it hoped to understand. RFC 1262 kept…

Sep 1, 2026
Data centre beside cooling infrastructure showing Rystad forecasts for water use in 2025 and 2030

Global Datacenter Trends

Data centre water use could hit 644bn litres

Rystad says cooling choices could cut 2030 water demand sharply, but some lower-water systems require more electricity.

Sep 1, 2026
Meta data centre in Alberta beside power infrastructure with projected household electricity cost increases

North America Datacenter Trends

Meta data centre could raise Alberta power bills

Pembina says Meta’s new load could raise wholesale power prices even if the company pays the direct cost of connecting its data centre.

Sep 1, 2026
RFC 1258 editorial illustration: early-1990s workstations use amber inherited-trust paths through a local admission gate while a violet verification path stops before it.

History

The Trusted Host Filled the Password Gap. It Did Not Prove the Host: RFC 1258 and BSD rlogin

In 1991, BSD rlogin made a familiar promise of convenience. A person sitting at one Unix machine could arrive at another without typing a password again, if the receiving system treated the originating host as trusted. RFC 1258 did not disguise the exchange as a proof ceremony.…

Sep 1, 2026
Infographic showing Anthropic, Lambda, Nvidia and Hut 8 in the reported US$35bn AI compute delivery chain

North America Datacenter Trends

Anthropic reportedly agrees US$35bn Lambda compute deal

The reported deal depends on Hut 8 delivering Texas capacity before Lambda can turn Anthropic’s commitment into usable compute.

Sep 1, 2026
Illustration of SMA grid, battery storage and power-conversion systems supporting an AI data centre

North America Datacenter Trends

SMA launches AI data centre power portfolio

The systems are designed to smooth volatile AI loads before they reach grids or generators, with an 800VDC option planned for 2027.

Sep 1, 2026
Editorial illustration of municipal water being added to a direct-to-chip cooling loop alongside a data centre commissioning checklist

Global Datacenter Trends

Ecolab links cooling-loop fill to week-long data centre outage

A week-long outage linked to the wrong cooling-loop fill shows why coolant verification matters before direct-to-chip systems enter operation.

Sep 1, 2026
Early-1990s workstations and servers use separate amber unicast discovery paths across a shared blue network cloud; one remote peer cluster has no completed arrival.

History

The Tunnel Made One Network. Discovery Still Had to Reach Everyone: RFC 1234

In June 1991, RFC 1234 offered a compact way to carry IPX across an IP internet: place the IPX datagram inside UDP and let an implementation regard the IP internet as one IPX network. It is tempting to read that sentence as a story of effortless unification. The rest of the RFC…

Sep 1, 2026
Vodafone Idea telecom tower with infographic showing ₹49,000 crore in spectrum payments through FY29 alongside a ₹45,000 crore network investment plan

Asia-Pacific National Telecom Trends

Vodafone Idea reaffirms ₹49,000 crore spectrum plan

The payments rise sharply through FY29 while Vi is also trying to fund a ₹45,000 crore network expansion programme.

Sep 1, 2026
A device token leaves an archive slot while a separate amber policy capsule, closed access gate and observation lens remain distinct.

CASE FILE

The Device Left SCIM. Its Network Access Still Needed a Decision: RFC 9944

A deleted Device record can settle what a SCIM service will show. It cannot, on its own, settle what a network will enforce. RFC 9944 makes that distinction unusually plain: removal is an application's signal of intent, while a SCIM server and its back-end policy decide whether…

Sep 1, 2026
Daniel Eggert in an AI editorial portrait between a layered mailbox, gapped UID intervals, an overlapping boundary and unequal downstream work lanes.

IETF

Daniel Eggert and the Message Batch That Was Not a Stable Page

A UID range can divide a mailbox into manageable work without freezing that mailbox, enumerating its messages or making each unit equally expensive. RFC 10022 gives clients a partition. It does not give them pagination certainty.

Sep 1, 2026
Illustration of a factory-built data-centre module being manufactured off-site and lifted into place at a construction site

North America Datacenter

Compu Dynamics moves AI data-centre construction off-site

Compu Dynamics is expanding factory-built delivery for AI projects, shifting more power, cooling and white-space work away from the construction site.

Sep 1, 2026
Editorial illustration of a deepwater HVDC cable system on an offshore vessel representing Nexans' 525kV cable and repair-joint qualification

Europe and Middle East Institutional

Nexans qualifies 525kV HVDC repair system for 3,000m

Nexans has qualified a 525kV HVDC cable and repair joint for 3,000-metre depths on the planned Crete-Cyprus interconnector.

Sep 1, 2026
Four separate physical zones show a measured cyan bead, an amber state ring, a suspended uncertain fracture and a closed ivory decision gate.

CASE FILE

The Alarm Changed State. The Cause Still Had to Be Found: RFC 9940 and the Evidence Boundary

An alert can be prompt, honest and operationally useful without being a verdict. RFC 9940 gives network teams a vocabulary for that restraint: a measurement, an event, a fault, a problem, a suspected cause and a decision are related, but they are not interchangeable.

Sep 1, 2026