Topic
Network-resource Evidence
Within the Topic facet, Network-resource Evidence topic intelligence connects articles that share a specific subject, signal focus, or monitoring theme. The page gives readers a richer path through related reporting, source evidence, market actors, and infrastructure implications, with enough context to understand why the topic matters across company movements, governance decisions, regional exposure, and operational risk. Readers can compare recurring signals, affected organisations, public evidence, market context, service continuity, procurement, competition, compliance, and strategic planning questions behind the subject instead of stopping at a thin list of matching articles. It explains what the topic covers, which infrastructure actors or policies are involved, what evidence supports the coverage, and why the subject may matter for operators, customers, investors, and policy readers.
History
Free to Copy, No Warranty: CERN’s 1993 Web Software Release
CERN’s April 1993 declaration did not invent the Web or certify that it worked everywhere. It changed who could reuse three pieces of the software without asking CERN first—and who carried the risk if they did. The document paired a broad grant to copy and modify with an equally…
History
BARRNet's OSPF Routes Took an Extra Hop Before the Protocol Changed
A 1991 field report traced two OSPFv2 features to one regional network’s practical limits: its imported routes needed a better next hop, while some routers lacked room for every external route.
Story
WorldLink’s APNIC /32 Scaled; DHCPv6 Still Held the Session
WorldLink’s account of more than one million IPv6-enabled IPoE subscribers includes an outage loop in which DHCPv6 lease recovery and a broadband gateway’s binding behavior could affect the shared session. The figures describe different things; none is an independent…
Europe and Middle East National Telecom Trends
Ireland’s 87% fibre reach still needs a clear adoption denominator
ComReg’s latest quarterly figures show a fibre network reaching most premises, but the headline “take-up” rate cannot be read as the missing share of that coverage. The workbook’s own glossary leaves a denominator question that matters for investment, competition and…
History
Two Links to Stockholm, One Missing at Home: Estonia’s 1992 Internet
A 64 kbps satellite link brought TCP/IP from Tallinn to Stockholm in 1992. A second link served Tartu. The striking part of the story is what did not yet connect the two Estonian cities.
Story
APNIC makes no consensus call on an IP-abuse definition
Prop-172 would define technical abuse tied to Internet number resources, but APNIC 62 left it on the Policy SIG mailing list. The remaining question is who can assess a response when the resource holder and complainant disagree.
History
From KAIST to the NCA: KRNIC’s Move and Independence
Korea’s early Internet registry changed institutional homes before it became an independent foundation. A September 1994 meeting record captures the handoff in one line—and in a changed nameserver address.
History
RARP Found the Address, Not the Configuration: RFC 903
A diskless workstation could wake knowing the number stamped on its network interface but not the Internet address needed to use IP. In 1984, RFC 903 gave it a narrow question for the local link: which protocol address had a server mapped to this hardware address?
History
MILNET Was Split Logically Before Its Circuits Were Physically Separated
The Defense Department’s separation of research traffic from unclassified military operations was a staged operating change. MILNET service began first, software controls divided the communities in 1983, and the physical network partition followed in 1984. Controlled gateways…
History
Brazil’s Academic Backbone Was National. Its Exits Were Not.
A countrywide network map can conceal a much narrower set of routes to the outside world. In Brazil’s research Internet, domestic reach expanded before international egress was distributed across the national backbone.
Story
LACNIC’s Legacy Policy Page Leaves Its No-Consensus Timeline Unclear
LACNIC’s index dates a no-consensus state for LAC-2023-4 version 4 to 29 August, lists an assessment window through 8 September and says the version was not discussed. A separate legacy-recovery proposal appeared on 16 September.
Story
A new individual draft points to IPv6. ARIN’s space policy still includes IPv4
ARIN’s current space-address proposal still names both IPv4 and IPv6. September records point toward an IPv6-only direction and a separate IANA/NRO allocation model, but neither record is an adopted change.
History
Same Client, Same Server Set: RFC 1542’s BOOTP Relay Rule
When one small bootstrap request has to cross a subnet boundary, the relay becomes part of the client’s conversation with a server. RFC 1542 made a quiet but consequential choice: distribute clients across servers if useful, but keep each client’s sequence of requests attached to…
Story
A Prefix Can Locate an IRR Set. It Cannot Validate It
A Prefix Can Locate an IRR Set. It Cannot Validate It 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 Story…
History
IPv6 Won After SIPP Changed: The Revision Behind the IPng Choice
The candidate that became the basis for IPv6 did not reach the finish line in its first form. Reviewers questioned both its transition plan and the space it reserved for addresses. The eventual choice followed a redesign: eight-byte addresses became fixed sixteen-byte addresses…
History
A Test Day Was Not a Switch: How World IPv6 Launch Changed the Goal
World IPv6 Day asked a narrow but consequential question: could popular websites add IPv6 for a day without breaking the IPv4 service people already used? A year later, World IPv6 Launch widened the assignment to access providers, home-router makers and content networks, with a…
Story
LACNIC’s Routing Lab Needs an Operational Receipt
Two event surveys record who said they attended LACNIC’s secure-routing lab. A new session moves from manual BGP checks to RPKI automation; neither record shows whether that workflow left the virtual lab and entered operating networks.
History
The Portland Home Behind South Africa’s First Internet Link
Before a leased line joined Rhodes University to the wider Internet, email between South Africa and Portland moved through a store-and-forward relay. In 1991, a low-speed circuit ending at Randy Bush’s home office became the far end of Rhodes’s first full IP connection. The…
Story
A Loop Is a Path Claim. An ASN Is an Inference.
A RIPE Atlas trace to 45.186.15.13 shows two public addresses alternating at every hop from TTL 9 through TTL 30. That is a striking path pattern. It is not yet an incident report, and the address sequence does not by itself identify who is accountable. LACNIC’s new Dominican…
History
13,159 Messages on a Narrow Link: RELCOM During the August 1991 Coup
A contemporary report counted 6,000 messages on an ordinary day between RELCOM and Finland, then 13,159 at the height of the August coup attempt. The number is striking because it records a working network under pressure; it does not count people reached or prove that email…