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.
CASE FILE
The UDP Payload Was Protected. The Option Was Not: RFC 9868
RFC 9868 gives UDP a place for transport options. It does not place that option area inside the UDP user data that DTLS protects, turn an option checksum into a security decision, or prove that an endpoint, path or application acted on an option.
CASE FILE
The Cursor Continued the List. It Did Not Continue the Right: RFC 9865
RFC 9865 gives SCIM a cleaner way to traverse a long result set. It does not convert a continuation value into a portable permission, a complete inventory, or a decision already made.
SANOG
SANOG’s Six-NOG Committee Does Not Cover Its Eight-Country Map
SANOG describes a region of eight countries. Its published future governance strategy, however, routes local-NOG representation through six named forums. That leaves Afghanistan and Maldives without the same visible institutional path into the Core Committee.
History
A Local Service Was Not Control of the Network: RFC 1291’s Mid-Level Boundary
In 1991, a mid-level network could make the Internet more usable without becoming the Internet's owner. RFC 1291 proposed local DNS capacity, software-discovery pointers, time servers, news feeds, mailing-list relays, testbeds, information services and NOC contacts. Its design…
Story
AFRINIC Says It Added JSContact. Its RDAP Guide Does Not Say Which One.
AFRINIC’s public record contains a useful sentence and an unfinished question. The current release entry for WHOIS 2.10.7 says that an RDAP feature called JSContact was added. The current RDAP guide tells a reader where the service is, which resources may be queried, which…
CASE FILE
The Color Reached PCEP. It Did Not Reach the Service: RFC 9863
RFC 9863 lets PCEP carry a color for a TE path. That is useful coordination data. It is not a guarantee that a service was mapped, a latency objective was met, or a customer received a result.
History
A Pointer Was Not the Information: RFC 1290 Had Not Made the Route Invisible
In 1991, the problem was not a lack of material on the network. RFC 1290 described the opposite: information and file repositories so abundant that browsing could consume a lifetime. The problem was how a person crossed from abundance to something usable. The document separated…
CASE FILE
The Router Repaired the Path. It Did Not Restore the Service: RFC 9855 and TI-LFA’s Local Boundary
A router can react to a directly attached failure in milliseconds and still know nothing about whether a customer service has recovered. RFC 9855 gives Segment Routing deployments a disciplined way to precompute and activate a loop-free repair path at the Point of Local Repair.…
History
The Architecture Retreat Named Five Problems. It Did Not Pick the Next Internet: RFC 1287
In 1991, a group of Internet architects looked at growth, address exhaustion, multiple protocol suites, security, real-time traffic and the next generation of applications. RFC 1287 is the record they left behind. It is tempting to read such a record backwards: it discusses…
History
A Bridge Port Was Not Necessarily an Interface. Its Counters Did Not Describe the Whole Line: RFC 1286
A network operator can be handed three reassuringly familiar facts: a port number, an interface index and a counter. RFC 1286, the 1991 Bridge MIB, is valuable because it refused to let those facts collapse into one picture. A bridge port could correspond to an interface without…
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.
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.
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…
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…
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…
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.
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…
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.
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.
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.…