Skip to main content

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.

AI editorial portrait of Nicolás Antoniello beside an imagined ring of registry desks and an empty drawer.

Leaders

Nicolás Antoniello Wanted a Sixth Registry. IANA's IPv4 Drawer Was Empty.

Global networks crossed five registry regions with one address plan. Antoniello proposed a virtual desk to serve them. LACNIC's own impact analysis found that the desk needed five operators, a new system and an IPv4 pool IANA no longer had.

Nov 3, 2026
AI editorial portrait of Malcolm Hutty in an imagined Internet registry policy setting.

Leaders

Malcolm Hutty Put Fairness Back Into RIPE’s “No Need” IPv4 Fight

The form asking how many IPv4 addresses an applicant needed had outlived the free pool. Malcolm Hutty feared that tearing up the form under the banner “No Need” would also sound like tearing up the registry’s promise to distribute addresses fairly.

Nov 3, 2026
AI editorial head-and-shoulders portrait of Gaurab Raj Upadhaya against an imagined BGP route-path backdrop.

Leaders

Gaurab Raj Upadhaya Put “Tier 1” on a BGP Path. A Third Network Walked In.

A carrier can call itself transit-free. Its customers still have to route through the network that exists. At APNIC in 2006, Gaurab Raj Upadhaya and two colleagues laid the industry's status claim against observed AS paths and found a guest the neat hierarchy had no seat for.

Nov 3, 2026
서로 다른 네 브라우저 장치가 같은 빛나는 모듈을 실행하는 동안 뒤편의 정식 규격 문서는 도장을 기다린다.

History

Four Browsers Ran WebAssembly Before W3C Published Its First Draft

By November 2017, Chrome, Edge, Firefox and Safari could run WebAssembly. W3C's first public Working Draft of the Core specification came three months later; its Recommendation took until December 2019. The browsers did not wait for the stamp. Their implementers had already…

Nov 3, 2026
AI editorial portrait of Erik Bais in an imagined registry archive.

Leaders

Erik Bais Put a 24-Month Clock on Acquired IPv4. The Merger Door Stayed Open.

RIPE's transfer rules once lived in four documents. Bais pulled them into one and made a newly acquired scarce resource wait before a policy transfer. A company could still be acquired again while the clock ran.

Nov 3, 2026
열린 캐비닛 문 너머로 밝은 공공 정원이 보이고, 안에는 B-tree 장치 하나만 작동하며 옆에는 꺼낸 저장 서랍들이 놓여 있다.

History

SQLite Gave Away the Code and Took Away the Backend Menu

On 20 September 2001, SQLite made its code public domain and removed the abstraction that let its database engine use different storage drivers. The same release opened one door to everyone and shut several doors inside the machine. The record is a useful antidote to the idea…

Nov 3, 2026
기술 설명서가 두 책상 사이로 옮겨지는 동안 여러 발행자와 독자는 피드 파일을 계속 주고받는다.

History

UserLand Handed Harvard the RSS 2.0 Rulebook. The Feeds Kept Running.

In July 2003, a software company gave a university center the document that described RSS 2.0. The handover opened the rulebook for reuse and put an independent board beside it. It did not hand anyone the streams already moving between publishers and readers. That small…

Nov 3, 2026
AI editorial portrait of Scott Bradner in an imagined Roman-numeral standards chamber.

Leaders

Scott Bradner Gave the Standards Process Roman Numerals. The Appeals Stayed.

On 1 April 1999, Bradner published a Roman version of the Internet standards rulebook. The joke changed the names and numbers. It left the machinery that decides who can appeal, and when, remarkably intact.

Nov 3, 2026
AI editorial head-and-shoulders portrait of Katsuyasu Toyama against an imagined registry operations backdrop.

Leaders

APNIC Voted for Katsuyasu Toyama’s IPv6 IRR. April Came and Went.

The room endorsed an IPv6 routing registry in September 2004. It left the hard questions to a quiet mailing list. APNIC then aimed for April 2005, ran into software work, invited operators to a test service, and recorded implementation in May 2006. Toyama got the vote; a usable…

Nov 3, 2026
AI editorial head-and-shoulders portrait of Masasi Eto against an imagined network research backdrop.

Leaders

Masasi Eto Found a Registry That Could Spell the Route but Could Not Agree on It

Two networks could file perfectly legible routing policies and still describe opposite versions of their exchange. Masasi Eto tested that gap in 2003. His finding put a number on the registry's awkward question: if its records disagree with each other, who will trust them enough…

Nov 3, 2026
A mechanical tool lifts small road fragments from a working map, leaving a broken route; an older map roll is sealed nearby while a licence stamp waits above a fresh sheet.

History

OpenStreetMap Cut the Map in July. The New Licence Arrived in September.

In July 2012, a bot removed incompatible contributions from the map people were already using. The Open Database Licence was still weeks away. OpenStreetMap had to turn a legal decision into a working dataset before its foundation could stamp the new terms on the file.

Nov 3, 2026
이용자가 관리하는 URL이 두 인증 제공자 중 하나를 가리키고, 방문 사이트는 그 연결을 확인한 뒤 같은 계정을 연다.

History

OpenID Let You Change the Login Company. Your URL Had to Stay Put.

In 2007, OpenID promised a person could keep an online identifier while changing the company that checked the password. The trick was to make the identifier a URL the person controlled, then put directions to the current authentication provider at that URL. The bargain shifted…

Nov 3, 2026
Two upstream racks feed one address ledger marked /24.

Story

Two Providers Can Announce the Route. ARIN's Easy /24 Comes From One.

ARIN says a downstream customer's need to use more than one upstream can, by itself, justify a /24 IPv4 block from an ISP. The customer must identify every upstream and run a border routing protocol with the provider supplying the block. Yet the policy gives that shortcut for a…

Nov 3, 2026
An upstream network rack branches to a simple customer card and a detailed address record passing a verification gate.

Story

ARIN Accepts a Customer as Free Text. Give It Control and the Contact Gate Closes.

An upstream provider can put a customer's name into a simple ARIN reassignment without linking it to a vetted organization or contact record. The provider keeps control. If the customer needs a detailed reassignment or reallocation with its own management capability, ARIN…

Nov 3, 2026
Abstract address-block tiles on an operator desk beneath a 24-segment review clock, beside a separate return path.

Story

ARIN Can Review Your Addresses Without Cause. The 24-Month Brake Has Other Entrances.

ARIN's current policy lets it examine how an organization uses any number resources in its database and ask for reasonable supporting documents. One route needs no stated cause, unless a full review has finished in the preceding twenty-four months. Three other routes remain: a…

Nov 3, 2026
Three number-resource tiles in a glass registry case between a sealed holder gate and a narrow legal exception passage.

Story

You Cannot Cancel RIPE NCC's Transfer Lock. A Merger Can Still Open It.

RIPE NCC offers holders of registered IPv4, IPv6 and ASNs a voluntary transfer lock for six, twelve or twenty-four months. Once approved, the holder cannot cancel it. Transfer requests during the lock are blocked. Yet RIPE NCC's current procedure reserves the right not to enforce…

Nov 3, 2026
Two server towers share one service-address emblem while each sends an answer card with a different geometric seal.

History

One DNS Address, Many Machines. A Bad Answer Could Name Its Server.

A DNS reply can arrive from an address shared by dozens of servers. When one reply is wrong, asking again may reach another machine and produce a clean answer. RFC 5001 gave the troublesome reply a way to carry an identifier for the server that sent it. The marker travels with…

Nov 2, 2026
ICANN Approved Another ERP Contract. The Public Got Three Black Bars.

ICANN

ICANN Approved Another ERP Contract. The Public Got Three Black Bars.

The Board signed off on the system that runs its internal books. Its published decision hides the supplier, the ceiling and the deal itself.

Nov 2, 2026
A mail sorting robot stands beside cabinet drawers marked with wax seals that indicate their roles.

History

The Mail Client Guessed at “Sent.” RFC 6154 Made the Server Answer.

A mail client opening a new account needs to know where to save drafts, sent copies and discarded messages. For years it often had to guess from folder names or ask the user. A folder named “Sent” might be called something else; a server could file sent copies itself or wait for…

Nov 2, 2026
Intact cable lines reach neighborhood homes above a dark shared network room while new operator equipment lights up beside it.

History

Excite@Home Went Bankrupt. The Cable Stayed; Operators Rebuilt the Service.

The neighborhood cable line could still reach the house. The company supplying much of the Internet service behind it was failing. In 2001–02, AT&T, Cox and Comcast faced different deadlines to take back the work Excite@Home had done for them, and the transition appeared on their…

Nov 2, 2026