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.

IETF
A G-ACh Advertisement Shares Peer State Without Delegating Local Configuration Authority
A peer can truthfully advertise a capability and still have no authority to decide what the receiving node should do with it. RFC 7212 makes that distinction operational: advertisements cross the link, but authorization, interpretation, freshness and the consequences of a local…

Europe and Middle East National Telecom Trends
Kontron wins Romanian rail communications contracts
Kontron Transportation has won several railway communications contracts in Romania and will deliver the work with Hitachi Rail Romania over 48 months

North America Datacenter Trends
US data-centre land purchases reach $6bn
US spending on land for future data centres rose sharply in the first half of 2026 as developers competed for sites with access to power and water.

Asia-Pacific Datacenter Trends
KIDZ AI secures first refusal on 1MW in Cambodia
KIDZ AI can take capacity in stages at an operational Phnom Penh data centre while pursuing a minority investment in HUADING Cambodia.

Asia-Pacific National Telecom Trends
BSNL 4G network carries 6PB of data daily
BSNL's indigenous 4G network is serving 22–23 million users across 100,000 sites, shifting attention from rollout to live network performance.

History
The Address That Meant Everyone: How IPv4 Broadcasts Chose Ones Over Zeroes
IPv4 did not gain broadcasting through a new flag. It gained it by teaching hosts and gateways that some destination values did not name one machine at all. A field of ones came to mean everyone within a scope, while receivers carried an awkward obligation to understand the…

IETF
A Dynamic MPLS-TP Control Plane Does Not Own Every LSP
A green signaling adjacency can coexist with a broken data path, while a working static LSP can exist without any control plane at all. RFC 6373 therefore treats automation as a governed operating choice, not as automatic ownership of the transport network.

Europe and Middle East National Telecom Trends
4iG plans Starlink Mobile launch in Hungary and Albania
4iG will start with Hungary and Albania, then extend a later 2GHz 5G NTN service to Montenegro and North Macedonia.

IETF
Radia Perlman and the Appointed Forwarder That Had to Stop Forwarding
A TRILL switch may still hold the appointment for a VLAN while its safest legal action is to drop the native frames it would normally handle. That is not a contradiction in the standard. It is the moment when recorded authority and permission to act must be read as separate…

North America Datacenter Trends
MN8 pairs solar and storage for Google in West Virginia
MN8 is developing 86MW of solar and two battery systems for Google's West Virginia energy needs, with the three projects due between 2028 and 2030.

IETF
An MPLS Echo Response Is Not Bidirectional Proof Until the Requester Validates the Return Path
A valid echo response may come from an intermediate point reached when the probe’s TTL expires. Its arrival proves that a responder answered from that position; it does not prove that the intended reverse LSP exists or carried the response.

History
The Bit That Made Routers Report Their Limits: IPv4 DF and Path MTU Discovery
One IPv4 flag began as a prohibition: do not split this datagram. Path MTU Discovery turned that refusal into a measurement loop. An oversized packet would be discarded, a router would report the narrow link, and the source would learn what the path could carry—provided the error…

North America Datacenter Trends
FuelCell Energy signs 75MW Texas data-centre reservation
An unnamed data-centre operator has paid to reserve manufacturing capacity for a planned 75MW FuelCell Energy project in Texas.

Global Cloud Services
Oracle expands HPE Juniper networking for AI infrastructure
Oracle plans a multi-year global deployment of HPE Juniper routing and switching across its AI clusters, regional data centres and edge networks.

Global Datacenter Trends
Equinix unveils Fabric One for managed multicloud networking
Fabric One will let customers specify connectivity requirements while Equinix manages routing, cloud links, encryption and failover.

History
The Index Could Refuse the Question Before Retrieval: RFC 1862
A search box appears to sit outside the document it finds. The entity keeps its permissions; the index merely points. In 1994, an IAB workshop saw why that division was incomplete. A directory could expose the existence of a record before the entity server ever had a chance to…

CASE FILE
A Yanked PyPI Release Is Not a Package Withdrawal Verdict
A PyPI yank changes how a repository presents a release to selection tools. It can be an important signal for maintainers and consumers, particularly when a release is broken or violates a compatibility promise. It is not, by itself, a record that a package has been deleted, that…

History
The Channel Number Was Not the Circuit: RFC 1613 and X.25 over TCP
Two calls could arrive with the same twelve-bit channel number and still be different calls. RFC 1613 solved that 1994 X.25-over-TCP problem by refusing to make the enclosed number carry more identity than its local interface allowed. The TCP stream, the logical XOT interface and…

History
The Quarter-Hour Had Ended. Its Counters Had Not: RFC 1595
A performance window can be over without being final. RFC 1595 made that awkward truth visible in 1994: if ten severely errored seconds straddled a SONET/SDH quarter-hour boundary, the agent could later move seconds in the completed interval from error counters into unavailable…

CASE FILE
Removing a PyPI Collaborator Is Not Trusted-Publisher Revocation
Taking a name off a project’s collaborator list is a real access decision. It should not be described as a complete release-channel revocation when the publishing identity is governed on a separate surface.
