Primary Domain
Internet Infrastructure
Within the Primary Domain facet, Internet 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.
History
They Asked Internet Organizers for Three Paragraphs. They Sent Back 33 Pages.
In February 1991, Gary Malkin asked current members of the IAB, IESG and IRSG for three things: a biography, their education and interests, and their view of Internet growth. The 1992 successor to his first collection ran to 33 pages and carried 24 portraits, with the submitted…
Leaders
Fredrik Lindeberg’s blunt resilience test: unplug half the nodes
Netnod’s security chief wants operators to test the question a risk register cannot answer: does the service still work after its dependencies are cut?
Academics
The Proof Arrives Too Early: Muhammad Usama Sardar’s Attested TLS Fight
At RIPE 93, TU Dresden researcher Muhammad Usama Sardar explained how early attested TLS can deliver platform evidence without binding it tightly enough to the connection and hardware a client intends to trust. A question from the room exposed a second boundary: an IETF URL does…
Europe and Middle East Institutional Trends
Saudi Arabia Built a 6.6 Tbps Exchange and Filled a Quarter of It
On 30 October 2026 the Saudi Arabian Internet Exchange's own homepage reported 6.6 Tbps of provisioned capacity and an all-time peak of 1.65 Tb/s — arithmetic that closes to exactly one quarter, and a gap that tells a buyer more about the exchange than any membership total does.
Leaders
Bruno Banelli’s 256-Route Demo Passed. “Mainline Support” Needs a Feature List.
At RIPE 93, Novarq co-founder Bruno Banelli showed BIRD installing IPv4 and IPv6 routes through Linux into a switch ASIC. The 256-route change worked. The full routing table, real ECMP traffic split, BFD and cable-pull recovery did not enter the test.
Leaders
Alistair Woodman’s CVE Queue May Hit 500. Users Need to Help Pay
At RIPE 93, Alistair Woodman said the EEF’s CVE workload could rise from about 10 records last year to more than 500 this year. Five people hold the CNA’s principal roles, two handle most cases, and discovery still leaves the maintainer with the patch.
IETF
The Fastest Compute Site Still Misses the 20ms Budget
An IETF cloud-VR example sends the request with the shortest processing delay to the wrong edge. Only one choice adds compute and network delay together and clears the 20 ms service budget.
IETF
PCEP Can Pair the Paths. It Cannot Prove the Return Trip Works
The costly question sits outside the PCEP message: who calls the service down when the return LSP loses liveness? RFC 10067 gives two one-way Segment Routing paths a shared association; it leaves the service verdict to two directional checks and an explicit operating rule.
Leaders
Eric Băleanu’s Romanian IX Opens Two Doors: Membership for Small ISPs, Commercial Links for Larger Ones
InterLAN-IX grew from neighbourhood LANs and a Bucharest operators’ association into one Layer 2 platform stretched into regional cities. Small local providers can join the association that owns it; larger operators connect commercially. The geography that widened access also put…
Story
ARIN Chose RDAP. Port 43 Still Has No Retirement Date
ARIN’s new directory-services roadmap replaces one sunset calendar with four separate readiness tests. Port 43 WHOIS, still used across security and research, now has no fixed retirement date.
Story
RIPE’s Cross-Border Model Starts With an 88.1% Country Match
A RIPE 93 talk compared the country on an address-prefix record with the country of the AS announcing it. The slide deck says six mechanisms explain 99.6% of cross-border origination, then includes an 88.1% bucket where the two country codes already match.
History
The Pretty Copy Had to Match the Plain One: RFC 2223
In 1997, the RFC Editor allowed PostScript to carry diagrams and a polished page, but kept ASCII as the primary version. The second file could join the RFC archive only after the editor agreed that it matched the first.
Europe and Middle East Institutional
Netnod Runs a Nordic Exchange and I-root. Its Registry File Says It Is a Membership Row.
Netnod Runs a Nordic Exchange and I-root. Its Registry File Says It Is a Membership Row. intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences…
History
The First ARPANET Login Crashed at G. The Log Kept Six Words.
At 10:30 p.m. on 29 October 1969, UCLA’s handwritten record marked a host-to-host success with six words about a conversation between two hosts. Leonard Kleinrock later recalled the first remote-login attempt reaching the letter G before the SRI host crashed. A small software…
History
CA*net Reached the North on 56 Kbps. NTnet Was Still in Beta.
By late 1994, YukonNet and NTnet had joined CA*net over leased 56 Kbps lines. The national backbone had received a T-1 upgrade; NTnet’s first dedicated-line users were still testing service.
History
The Empty Kerberos Field That Still Crossed a Border
In September 1993, RFC 1510 gave Kerberos V5 a way to carry authentication across administrative realms. Its `transited` field records intermediate realms; separate ticket fields identify both ends of the exchange. A direct hop between two realms can leave that field empty. The…
History
The Ping Failed. The Error Was the First Good News: RFC 1574
An OSI network manager in 1994 could send a new echo request to a machine that did not understand it. If the machine returned an error, the answer still settled one urgent question: something at that hop had heard the probe. RFC 1574 turned that awkward reply into part of a…
History
The Email Read Receipt Had to Ask Nicely
A sender adds one header to an email and waits for the little thrill of knowing what happened at the other end. In March 1998, RFC 2298 gave that wish a machine-readable form. It also gave the recipient’s mail program the last word. The header could ask for a receipt. The program…
IETF
One Failed Reply Can Fail a Shared Task. Who Sets the Rule?
In one iCalendar mode, a single attendee’s failure reply can mark the entire task `FAILED`. RFC 10051 defines that trigger; in `SERVER` mode, each implementation writes its own rule.
History
The Internet’s Gigabit Dream Had a Waiting Room
In April 1990, a report from an Internet Research Steering Group workshop put the gigabit network on the table. The room had plenty of ideas for moving bits faster. Then came the awkward question: how long would a program still wait for another machine to answer? A brighter fiber…