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
CyIX Was on the 1999 IXP Map. The Entry Says Little About Its Network.
A 1999 Cisco inventory listed Cyprus’s exchange point among sites said to be operating. CYNET dates its founding to that same year, but neither source tells us who peered there, how the network was built or what local users gained.
IETF
Tomek Mrugalski and the DHCPv6 name that points an IPv4 tunnel upstream
A DHCPv6 Reply can carry one fully qualified domain name for a Dual-Stack Lite endpoint. That name tells a customer edge device where it may try to send IPv4 through an IPv6 network; it does not show that DNS resolved, a tunnel formed, translation state exists, or a service…
History
The IP Timestamp Option Kept a Route Diary, Not a Stopwatch, 1981
In 1981, IPv4 gained a small field for recording where a packet had been processed and when. Its design resembles a route diary, but it cannot be read as a synchronized stopwatch for network delay.
History
UDP’s Zero Was a Status Flag, Not a Checksum, 1980
A 16-bit field made room for two different zeros: one was a computed checksum, the other a signal that no checksum had been sent. The distinction began in UDP’s 1980 specification and later met stricter rules in IPv6.
Story
AFRINIC pairs Johannesburg IPv6 Deployathon with five travel awards
AFRINIC, ISPA and ZANOG have scheduled a three-day, in-person IPv6 Deployathon in Sandton for 20–22 October. The event listing says INX-ZA will cover travel and accommodation for five fellows, or ZAR 50,000 in total; applications closed on 12 October, and no award recipients or…
Number Resource Society
The Number Resource Organization: How Five Registries Coordinate the Internet's Address Space
The Number Resource Organization: How Five Registries Coordinate the Internet's Address Space intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…
History
Stanford Ran 18 IP Subnets Before the Standard, 1984
In October 1984, RFC 917 described subnetting as a proposal. Stanford had already used IP subnets since early 1982, adapting an older Pup network and routing system rather than waiting for a common Internet procedure.
Story
AS48019 and Terra-Telecom LLC: A Registry Record With an Unanswered Question
AS48019 and Terra-Telecom LLC: A Registry Record With an Unanswered Question 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…
History
The DNS Answer Had an Order. The Client Kept the Choice: RFC 1794
In 1995, engineers wanted DNS to steer requests toward a less-loaded machine without changing the protocol or breaking the installed base. The compromise could rank addresses before a reply went out. It could not make every resolver or application obey that ranking.
History
Six Sites, One 56 kbps Line: NSFNET Before the T1 Upgrade, 1986–1988
Before NSFNET became shorthand for a national high-speed backbone, it was a deliberately small bridge between six scientific computing sites. Its first 56 kbps links exposed a mismatch: access to supercomputers had been funded, but useful access depended on moving data between…
Europe and Middle East Institutional
RIPE 86: Rotterdam's May 2023 Meeting, Verified on the Record
RIPE 86 — a meeting number that keeps being attached to the wrong months — took place in Rotterdam, the Netherlands, from 22 to 26 May 2023. The dated record behind that number is concrete: a Routing Working Group session that logged 20,000 RPKI certificates under the RIPE NCC…
History
From Fuzzball PING to BSD ping: Mike Muuss’s 1983 Port
A brief exchange between two network researchers joined a laboratory instrument to a small Unix command. Their shared name can obscure how different the two tools were—and what a reply could actually establish.
History
RDAP Could Still Point to WHOIS: The port43 Field, 2021
A registration record could move into RDAP’s structured JSON and still carry the address of a WHOIS server where the same entity might be found. The small `port43` member preserved a service pointer across a protocol transition, while stopping short of a URI, a redirect, or a…
History
When Class C Was Too Large: RFC 1375’s Small-Network Address Proposal, 1992
In 1992, one proposal tried to make an Internet address say more about the size of the network using it. RFC 1375 offered new IPv4 classes for sites that could not use a full Class C block, then sketched regional and device-oriented meanings for some of the same bits. Its…
History
NUNet Routed Nigerian University Mail Through Abuja and Trieste
Nigeria’s university network was designed as a route to full Internet connectivity, but its early operating path was much narrower: campus mail servers called Abuja by modem, and Abuja relayed their messages to ICTP in Trieste.
Global Regional ISP Trends
A 1,500-Byte Majority Hid a Directional PMTU Gap
A study of 76,700 RIPE Atlas path measurements found 1,500 bytes on most observed paths. Its bidirectional subset and MSS comparisons show why that majority is a baseline for investigation, not a universal operating receipt.
Story
LACNIC links an operator’s ASN to the freedom to change providers
LACNIC links an operator’s ASN to the freedom to change providers 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…
History
BolNET Reached Every Academic Network University by 1999. Access Remained an Open Question
Bolivia’s early Internet story is often dated to 1989, yet the institutional record describes a project that changed form as it moved from campus research into a national data service. By 1999 the university links were in place; the history that records that milestone also says…
IETF
UDP ECN Depends on the Socket API
An ECN mark can survive every router on a path and still be invisible to the UDP application expected to report it. RFC 10055 documents the operating-system interface between an IP-layer congestion signal and user-space transports such as QUIC.
History
TANet’s No-Transit Boundary: ISP Interconnection Rules, 1996–2006
Taiwan’s education network allowed commercial providers to interconnect on conditions that kept its own backbone and international circuits outside their carriage plans. The surviving versions show how that boundary was reviewed, measured and revised.