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
Who Could Apply for a Top-Level Domain? RFC 920’s First Eligibility List
In October 1984, the first top-level domain list was also a set of admission rules: some names were temporary, others stood for broad categories, and none could enter the tree without an administrator and a route to authorization.
Europe and Middle East National Telecom Trends
EG-IX’s 1.22 Exabytes: Growth Is Clear; Local Value Still Needs Proof
EG-IX reported 1.22 exabytes of traffic in nine months, but the total cannot tell a buyer which routes stayed in Egypt, which users benefited or whether service costs fell. The investment case turns on that missing denominator—and on the service terms that shape participation.
History
Three Networks, One Transmission: The 1977 Internetting Demonstration
The famous van was only one endpoint. The real test was whether a message could cross packet radio, the ARPANET and a satellite packet network without turning them into one enlarged network. The surviving record supports a successful route—and a much narrower claim than “the…
History
The Glossary Left Interoperability Undefined: RFC 1208’s Moving Target
Adapted from a pocket guide for Interop ’90, RFC 1208 helped readers navigate a fast-moving field without pretending that one short definition could prove two vendors’ systems actually worked together.
Story
LACNIC Adds ASPA Publishing to MiLACNIC; Uptake Is Still Uncounted
LACNIC Adds ASPA Publishing to MiLACNIC; Uptake Is Still Uncounted intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may follow. The…
Africa National Telecom Trends
Nigeria’s Next Fibre Kilometre Depends on Who Clears the Roadworks
Nigeria’s fibre-cut figures point to a control gap that a bigger network cannot solve by itself. Before a road crew excavates, a project needs a verifiable record of the route check, the official who can release or stop the work, who pays for protection or relocation, and how the…
Academics
Paul Vixie and DNS RRL: A Response Limit, Not an Identity Test
DNS Response Rate Limiting was built to make an authoritative server a less useful amplifier in a forged-source flood. The mechanism can cap repeated answers; it cannot tell an operator who sent a spoofed query, why it was sent, or whether every client grouped with it is hostile.
History
The Cache Changed the Destination, Not the Root: AlterNIC’s 1997 InterNIC Redirect
A resolver in one operator’s network returned an AlterNIC address for `www.internic.net`. Its cache record exposed the route the redirect took: additional DNS data had become a local answer. That was evidence of a changed destination at one resolver, not of a new authority taking…
History
A Customer Link Became a Security Boundary: RFC 2267 and BCP 38
In 1998, an informational memo moved one check from the machine under attack to the provider edge nearest the traffic’s declared source. RFC 2267 asked whether a packet arriving from a customer network used a source prefix that network could legitimately send. The rule narrowed…
CASE FILE
PeeringDB’s API v3 Draft Expands Reads Without Rewriting Data-Use Rules
PeeringDB is proposing a read-only interface served from multiple locations. Its draft would make queries easier to cache, but the existing rules still govern bulk storage, redistribution and commercial reuse.
Story
LACNIC’s Loop Study Moves 59 Cases into Intra-AS Under a Private-Hop Rule
LACNIC’s Dominican Republic measurements leave 41 possible-loop cases unclassified after a second rule shifts 59 from the unknown column into intra-AS. The difference is a choice about how to read a hidden hop, not a count of newly confirmed faults.
Academics
Eric Allman, Sendmail 8 and the Gap Between Mail Standards and Public Code
When Eric Allman returned to active Sendmail work in 1991, the problem was not simply that the mail program needed another release. His account describes a widening distance between changing SMTP requirements and the versions that operators could inspect, adapt and compile for…
History
The Pigeon Returned an IP Packet. A Human Still Had to Finish Delivery: RFC 1149 in Bergen
In Bergen in 2001, a Linux user group tested a ten-year-old specification for carrying IP datagrams by pigeon. Four replies reached the log, but only after a person removed the paper, scanned it and corrected the OCR. The surviving record shows what this one route tested—and what…
Story
APNIC Sets a One-Hour RPKI Patch Window; rsync May Pause for Up to Two Minutes
APNIC plans security patching on 13 October from 08:00 to 09:00 UTC+10. Its notice forecasts up to two minutes of unavailability on one self-hosted RPKI rsync endpoint, while saying other RPKI services are not expected to be interrupted.
Academics
Toerless Eckert’s AI4AN draft moves the trust question into the router
AI4AN offers a different place to put an AI system in network operations: let a model help write and test automation software, then let that software run on network devices. In Toerless Eckert and Alexander Clemm’s current IETF draft, the difficult question is no longer only…
History
The Frame Held 512 Bytes. The Datagram Could Span 120 of Them: RFC 1201
The 1991 ARCNET specification made a small fixed frame carry a much larger IP datagram by moving fragmentation down to the data link. Its 60,480-octet ceiling was only a format limit: every network still had to choose and share a practical maximum.
Europe and Middle East Institutional Trends
The EU’s government network must prove it can change providers
Orange Business has been selected to provide the TESTA-EIRIS backbone. The European Commission’s own design assigns DG DIGIT control of the wider system and calls for alternatives at critical functions. The test of sovereignty will come when administrations migrate, handle…
Leaders
Lynn St. Amour’s .ORG legacy was a funding channel, not a blank cheque
ISOC’s 2013 retrospective called the .ORG award a turning point. The board record shows what that meant in practice: a new source of programme funding, a separate registry operator and rules that kept project money apart from the Society’s general operating cash.
History
Before Joining the Internet, You Needed Its Oral Tradition: RFC 1118
In September 1989, RFC 1118 set out to help a small, isolated IP network cross into the Internet. Its most useful contribution was a map of people, operating centers and unwritten practice; its own disclaimer showed how quickly that map could age.
Asia-Pacific National Telecom Trends
NTT’s 2 Tb/s radio turns installation time into network capacity
A 100-metre outdoor link at a reported 2.04 Tbit/s is a serious engineering result. Its commercial value will depend on the work it can remove, the service it can sustain and the time needed to integrate and maintain it.