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
One Korean Email Needed Two Passports
In 1993, a Korean email could arrive with a perfectly readable subject and a body full of wreckage—or the other way around. The two parts had crossed the same network but carried different encoding papers. RFC 1557 gave the body a seven-bit switching scheme and sent Korean words…
History
The Directory Had Servers. Who Would Fill It?
An Internet-wide directory sounded like a machine problem in 1993. RFC 1430 put the expensive work elsewhere: mapping messy institutional records into one shared structure, keeping them accurate and paying for the services that connected them.
History
The IPv4 Pool Was Free. The Future Title Office Was Up for Grabs.
In December 1994, Geoff Huston looked at an address allocation system that charged nothing for the scarce thing it handed out. His RFC imagined what would happen when the free pool could no longer meet every request: holders might sell blocks, large providers might dominate the…
History
Millions of Messages, One Copy on Busy Links. The Map Had Two Months to Live.
In 1993, BITNET's LISTSERV distribution service claimed 2–6 million messages a day and tried to cross busy links with one copy before fanning out near recipients. Its speed rested on an unglamorous condition: the operator's master-node map had to be less than two months old.
Story
RIPE Atlas Wants Your Spare Raspberry Pi. It Still Has to Find the Missing Networks.
RIPE NCC is exploring a flashable image that would turn a volunteer's own device into an Atlas hardware probe. The box is easier to find than the network vantage point that makes it useful.
ICANN
ICANN Expects a $40 Million Refund. Applicants Had to Opt In.
About 1,600 applications produced roughly $110 million in implementation-cost recovery against a $70 million target. ICANN expects the excess back as a volume refund, but the Applicant Guidebook put the choice in each application: elect the refund, or forfeit a later request.
History
CoVis Gave Students Full Internet Accounts. It Banned Anonymity.
At two Chicago-area high schools, a 1990s science project let students hold their own Internet accounts. They could write directly to scientists and be contacted by strangers online without a teacher relaying every message. The same project told them to use their real names, keep…
History
The Standards List Had an Expiry Date. The IAB Could Send a Protocol Back.
In March 1993, the official Internet protocol standards list told readers to stop using that edition after 31 July. It also showed why a proposal did not become a standard merely by surviving an IETF meeting: the IESG had to recommend advancement, the IAB had to ratify it, and…
IETF
RFC 10066 Gives One PCEP Path Many Routes. The Headend Can Still Say No.
A path controller can now describe several routes inside one Segment Routing candidate path. The device that must install them gets the last word on how many it can carry. That small negotiation determines whether multipath is a useful operating choice or an expensive surprise.
History
Cook Gave the Public Network Fifteen Governors. Congress Gave It None.
In 1993, Gordon Cook drew a board for a national research and education network that Congress had never commissioned. Its fifteen seats would put schoolchildren's advocates, librarians, disabled users, carriers, manufacturers and federal agencies in the same room. The seating…
History
The Directory Put “Internet” at the Top. Only Countries Had a Registrar.
The 1993 X.500 directory pilot gave “Internet” a place near the root of its naming tree and placed the DNS subtree beneath it. Its own guidelines called that entry an informal adoption. The only top-level entries with a recognised registration authority were countries.
Story
ARIN’s Survey Gap Shrunk. Its Performance Score Fell Eight Points.
ARIN’s 2026 customer survey offers a tidy headline and a less tidy ledger: the gap between performance and expectations narrowed, while both scores fell. The distinction matters to members deciding what the registry should fix—and what its next fee should buy.
History
The Header Stayed. The Old Host Still Dropped the Packet.
In 1992, one address-extension proposal tried to spare the Internet a new IP header by putting extra address bits in the old header's options. The packet kept its familiar outline. A host that had not learned the new address class would still discard it.
Story
ARIN Has $12.5 Million Above Its Reserve Target. Its 2027 Fees Still Rise.
ARIN's treasurer called the registry's finances healthy at its October meeting. He had the numbers to make that case. The Board had also already voted to raise next year's registration-plan fees by 5%. The question for members is how quickly the registry should spend its cushion…
History
No Voter Roll. Seven Nominators Chosen by Lot.
The IETF had a power problem in 1992. A dispute over the Internet's future addressing system turned into a harder question: who could decide which standards advanced, and who chose those decision-makers? A ballot sounded democratic until someone asked for the voter list. The IETF…
History
A Video Call Wanted 100 Milliseconds. The Map Had Other Ideas.
In 1992, a proposed Internet flow specification refused to turn a caller's preferred delay into a universal deadline. One hundred milliseconds across the Pacific and one hundred milliseconds across town had different meanings. The network needed to know what traffic a call would…
Story
ARIN's /44 Draft Says Will. Its Staff Says May.
An eight-site network can qualify for a /44 under ARIN's IPv6 draft. At ARIN 58, someone asked the question the draft leaves on the desk: can that network take less? The written examples say it **will receive** the larger block. The registry's senior staff said there is a choice.…
History
The Report Number Was Required. The Title Was Optional.
In 1992, a computer-science department could put news of a new technical report into email instead of stuffing envelopes. RFC 1357 gave the announcement a strict identity: a version, the publisher's report number, a record date and a closing identifier. The title could be left…
History
The Email Said “Withdrawn.” The Catalog Still Had to Decide.
In 1992, a technical report could acquire a portable bibliography record by email. RFC 1357 even described how its publisher could send a later withdrawal. The message carried a complete replacement record; each receiving library still controlled what entered its own catalog.
Story
ARIN Put a Border on Its IPv6 Bridge. The Border Is on the Wrong Noun.
ARIN staff already turn down requests to use a special IPv4 transition pool outside the region. A policy now in Last Call would put that practice in the manual. Its one added phrase limits where IPv6 is deployed, while staff say the rule is meant to limit where the IPv4 addresses…