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
When 255 Octets Stop Being Enough: RFC 9885 and Multi-Part IS-IS TLVs
A syntactically valid IS-IS LSP can leave a receiver with an incomplete entity when information crosses the 255-octet limit and the receiver processes only one TLV occurrence. RFC 9885 defines how to recognize and process those related occurrences without changing the underlying…
IETF
Happy Eyeballs Is a Racing Budget, Not Proof of Dual-Stack Health
A page can load normally while one address family is unusable. Happy Eyeballs protects the user by letting another candidate win, but that success becomes misleading when operators treat it as evidence that the whole dual-stack service is healthy.
AFNOG
AfNOG Publishes Fellowship Criteria, Not the Procedure That Applies Them
AfNOG’s published Abha Ahuja Bursary application page tells candidates what the fellowship is looking for. It identifies a selecting committee, lists eligibility criteria and says incomplete applications will not be considered. The reviewed page does not set out how those…
History
The Router Saw a New Network. It Was a Shadow of Its Own Mapping: RFC 1504
The route looked newly learned and the number was locally valid. The awkward fact was that no second network had appeared. A number invented at one translation boundary had travelled around a redundant path, lost its lineage and returned as if it belonged to a stranger.
History
The Key That Could Change Mid-Connection: TCP-AO's Rollover Signal
Long-lived routing sessions made a simple operational question unusually dangerous: how can two endpoints replace an authentication key without dropping the TCP connection or guessing the same switching instant? TCP-AO answered with visible key identifiers and directional…
IETF
A Local Root Makes DNS Resilience an Operator-Controlled Failover Decision
RFC 8806 lets a recursive resolver answer root-zone questions from a complete local copy. The design can reduce dependence on a reachable remote root server and keep root queries off intervening networks. It also moves a consequential decision inside the operator’s own system…
IETF
The Label Arrived, but Did It Reach the Right Path? RFC 9884 and PSID Validation
A label can arrive at the intended egress and be popped there, yet still be associated with the wrong SR Policy, candidate path, or segment list. RFC 9884 makes that control-plane correlation testable with LSP Ping instead of treating reachability as proof of path identity.
Story
ARIN’s IRR Objects Keep the Channel That Created Them
An IRR object migrated from ARIN’s email service can be deleted in ARIN Online but not edited there. The asymmetry is defensible as a record of provenance. The trouble begins when the web remedy—delete and recreate—changes that provenance without a visible continuity receipt.
Asia-Pacific Institutional Trends
PLN prepares 150kV Gorontalo transmission links
PLN is preparing new 150kV lines and a Marisa–Moutong interconnection, while the 30MVA Marisa substation extension is reported complete.
Asia-Pacific Datacenter Trends
Baya Systems taps AdoreSys for APAC ASIC design
AdoreSys will combine Baya's interconnect IP with ASIC design and implementation services for semiconductor customers across China and the wider Asia-Pacific market.
Asia-Pacific National Telecom Trends
Kemkomdigi agrees Palapa Ring reroute for Sitaro
Sitaro and Kemkomdigi agreed to reroute Palapa Ring Tengah through Tagulandang, with construction and commissioning still pending.
Asia-Pacific Institutional Trends
PLN adds 5MW to Selayar power system
Six rental generators are now operating in Selayar, lifting the island system's total generation capacity to 16MW.
Asia-Pacific National Telecom Trends
Firmus signs 25-year APX East capacity deal
Firmus will spend about US$300m for up to 150Tbps over 25 years on SUBCO's planned Australia-US cable, due in 2028.
North America National Telecom Trends
Clearfield adds WAV distribution channel
Clearfield will use WAV to distribute its fibre, cabinet and power products to wireless and broadband providers across the US and Canada.
Asia-Pacific Datacenter Trends
India targets data-centre delivery bottlenecks
India is focusing on reliable power, ready land and faster approvals as it seeks to turn about $200bn of expected data-centre investment into projects.
Europe and Middle East National Telecom Trends
MasOrange tests 6GHz radio technology with Ericsson
MasOrange has tested 6GHz spectrum with 256TR active antennas and beamforming as it evaluates radio technology for future 6G deployment.
North America Regional ISP Trends
Ritter, Great Plains complete merger to form Rightfiber
Rightfiber starts with a 28,000-mile fibre network, more than 300,000 FTTH passings and a $1.6 billion facility for growth and acquisitions.
Europe and Middle East National Telecom Trends
Tottenham Hotspur upgrades stadium network with Wi-Fi 7
HPE will add outdoor Wi-Fi 7 and bring data-centre, campus and edge network management into Aruba Central at Tottenham Hotspur Stadium.
North America Datacenter Trends
Texas Batch Zero load is twice ERCOT peak
ERCOT is auditing about 200GW of large-load projects after Texas data-centre demand overwhelmed a grid whose July peak reached 91.3GW.
Story
APNIC’s Resource Quality Check Is Not an Address Attribute
APNIC made a careful change in 2019: “assurance” became “check”. The distinction matters because a registry can observe routes, filters and reputation signals, but it cannot make thousands of other networks carry the result forward.