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
The Address Arrived. The Resolver Didn't: IPv6 Learns to Advertise DNS
SLAAC could configure an IPv6 address and a default router while leaving a laptop with nowhere to ask for a domain name. The fix moved DNS into Router Advertisements, then had to account for packet loss, competing configuration sources and who was allowed to announce a resolver.
History
Almost 5,000 Usenet Groups—and a $250,000 Threat to the Provider
On 12 April 1994, Internet Direct’s system administrator said a Green Card Lottery advertisement had reached almost 5,000 Usenet groups, the provider had disabled the users, and the law firm threatened a $250,000 suit. The telling question was who controlled the account that sent…
CASE FILE
The exchange in the name, the hub in the brochure
A Hong Kong company registered with APNIC as ASIX Asia Satellite Internet eXchange Ltd sells, by its own account, teleport capacity: dedicated satellite carriers, shared carriers scheduled from a hub, video uplink, ground support, co-location. That is a star with a ground station…
History
Korea Had .kr in 1986. The Dedicated Hawaii Line Came in 1990.
A country can acquire an Internet name before it has a direct international circuit. Korea’s timeline puts the introduction of .kr in 1986 and the dedicated KAIST–University of Hawaii line in 1990. In between, researchers were already exchanging mail and reaching foreign networks…
Story
RIPE NCC Named Six Arbiters. Its Published Vote Report Leaves Out the Count
The October result report names each winner and seat, then stops before the numbers that would show how an instant-runoff election reached those six outcomes. The arbiters’ announced terms run through the Autumn General Meeting in 2031.
History
Napster’s Search Was Central. The Song Wasn’t.
The MP3 stayed on a user’s computer, but its name entered a live server directory. That small architectural split gave Napster a search-and-exclusion control point—and put the court’s attention on what the service could actually see and do.
Story
RIPE’s database failed for eight hours. No reverse-DNS delegation changed.
RIPE NCC’s first alert said database failures were affecting reverse DNS. Two days later, its investigation drew a sharper line: every failed request either asked for no change or failed a validation check. The outage interrupted the write path; the published delegation stayed…
Academics
Four French Networks Share 17,435 Antennas. The Backup SIM Needs a Map.
Alexandre Vogel and Cristel Pelsser counted where France’s four historical mobile operators share radio equipment. Their January 2026 inventory found 17,435 antenna records linked to all four networks—a reminder that a second operator name is not automatically a second physical…
Story
Ties de Kock Wants a Two-Week Audition Before RIPE Keeps a BGP Feed Forever
RIPE NCC runs the collectors; network operators supply the feeds. At RIPE 93, Ties de Kock proposed a two-week trial before RIPE decides which new sessions belong in its permanent BGP archive.
Leaders
Jen Linkova Took a Seven-Second Wi-Fi Delay to the IETF. It Became RFC 9131
In 2019, a phone on Jen Linkova’s office guest Wi-Fi took seven seconds to connect after the network went IPv6-only. She traced the wait to Neighbor Discovery, took the fix through IETF review and later saw it published as RFC 9131.
Leaders
MANRS Wants a Valid ROA for Every Route. Legacy Networks Will Test the Rule.
At RIPE 93, Andrei Robachevsky described a proposed RPKI floor for network operators. The hard part sits beyond the router: who can publish the authorization for a legacy or customer-held prefix?
Leaders
A Single LAN Cannot Contain an IXP. Stefan Wahl Wants the Directory to Catch Up.
At RIPE 92, Stefan Wahl argued that exchange directories still draw one flat peering LAN while operators sell and run a stack of distinct services. That gap now reaches into route filters, trust settings and automation.
Story
RIPE Found 37% of ROA Definitions Off BGP. Who’s Cleaning Up?
RIPE NCC says about 37% of AS-prefix definitions in ROAs were not seen in BGP. Some are deliberate backups. Others may be old permissions that outlived the route, and the incentive to create them is stronger than the incentive to retire them.
History
One uidNumber Edit Could Give an Account Superuser Power. RFC 2307 Put the Risk in LDAP
A Unix lookup could return more than a login name. By 1998, RFC 2307 was sketching how LDAP could carry the numeric identity that local programs consumed—and warning what happened if the wrong person could edit it.
History
A Hosting Provider’s CAA Rule Could Reach Its Customers. RFC 8659 Changed the Search.
A DNS alias can point a customer’s name into a provider’s name tree. CAA’s first lookup rule could carry the provider’s parent-zone policy into that search; six years later, RFC 8659 changed where the climb stops.
IETF
The ACL Got a Calendar. The Group Map Still Has to Work
RFC 10065 gives network access rules a common way to match endpoint groups and time windows. The difficult part remains the hand-off from an identity returned at login to the packets a device actually filters.
History
PPPoE Lost Eight Bytes. RFC 4638 Made Them a Two-End Negotiation
The 1999 limit left a PPP packet 1,492 octets inside a standard 1,500-octet Ethernet payload. The 2006 extension reopened the final eight only when client, concentrator and path could carry them.
History
The Empty Till: HTTP 402 Was Reserved in 1997. The Standard Still Has No Checkout.
HTTP gave payment a status number, then left the transaction outside the protocol. Across four generations of HTTP semantics, 402 kept its sign and never acquired a shared checkout.
Academics
Vaishnavi Raghavajosyula measured 76,700 paths. The edge still trims the packet
A RIPE Atlas study found 1,500-byte path MTUs on 80.5% of its sample. The smaller limits clustered near network edges, where one fixed packet size is most likely to meet a hard ceiling.
Story
A Firewall Blinded RIPE’s DNS Monitors. The Route Guard Held.
A mistaken firewall change drove every DNS instance’s Atlas reachability reading to zero. RIPE NCC’s automation kept the service prefixes advertised because the simultaneous collapse looked like a broken measurement path, not a reason to pull every route.