Intelligence
Latest Articles
Latest intelligence on infrastructure operators, policy decisions, market moves, and digital power shifts.
Story
LACNIC's Legacy Deadline Is Running Ahead of Its Policy
Prior BTW reporting describes legacy IPv4 holders answering an administrative request while the community rule that would govern the same evidence is still being debated. That sequence does not make the outreach illegitimate. It makes the label on every decision unusually…
History
The Acknowledgment That Learned to Point: How TCP SACK Made Loss Visible
TCP's original acknowledgment could certify an unbroken prefix of a byte stream, but it could not describe the islands waiting beyond the first gap. Selective acknowledgment added a small map of those islands while leaving the sender—not the receiver—in charge of repair.
History
The Router That Pointed Sideways: How ICMP Redirect Stayed Local
ICMP Redirect let a gateway reveal a better local next hop without becoming a routing authority. Its power ended at the host that had just used it.
History
The Number That Became Newer After Zero: How DNS Ordered Versions Without a Clock
At the edge of a 32-bit counter, DNS asks operators to accept an apparent impossibility: zero may be newer than 4,294,967,295. That rule let independent name servers agree on version order without sharing a clock, but only inside a deliberately bounded window.
Story
The Evidence ARIN Should Require Before Retiring Legacy Whois
ARIN's new directory-services consultation looks like a consolidation project. Its migration inventory tells the more important story: an API can announce its own retirement, a local reassignment server needs a conversion tool, and Port 43 can hide inside scripts that the…
History
The Zone That Knocked: How DNS NOTIFY and IXFR Cut Staleness
DNS once made every secondary wait before learning its authority was stale. In 1996, NOTIFY delivered the knock and IXFR carried only the edit.
History
The Address You Needed DNS to Find: How Glue Broke the Delegation Loop
A DNS referral can name the server that knows the answer and still leave a resolver unable to reach it. Glue was the small, deliberately non-authoritative exception that let the resolver cross that gap without giving the parent zone control over the child's facts.
History
The Address That Asked the Wire: How ARP Made Local Reachability Revisable
Routing can choose the next IP address without knowing how to put a frame on the local cable. ARP filled that last gap with a public question, a private answer, and a memory designed to be corrected.
Story
APNIC's /12 Reserve Turns a /22 Offer Into a Queue
The newest impact assessment for prop-168 starts with a subtraction. APNIC counted 11,729 `/24` units in hand; protecting a `/12` for future transition use would remove 4,096 of them, leaving 7,633 for a wider group of applicants whose combined maximum demand would be larger.
History
The Connection That Had to Prove It Was New: Why TCP Needed a Three-Way Handshake
A packet can arrive at the right address, carry a plausible number and still belong to a conversation that has already died. TCP's familiar opening exchange was designed around that ambiguity: before accepting a new connection, both endpoints must show that they have seen each…
Global National Telecom Trends
An IRU Buys the Strand, Not the Road Around It
A dark-fibre contract can name a strand, reserve it for twenty years and make it feel like an owned asset. The harder question begins one layer out: who controls the ducts, access, power, maintenance, relocation and remedies that keep that strand useful when the route changes or…
History
The Packet That Had to Learn Its Size: How Path MTU Discovery Moved Fragmentation to the Edge
A packet may cross a path whose narrowest link is invisible to its sender. The Internet spent four decades changing who should discover that limit, who should report it and who should decide what size to send next.
Story
AFRINIC's New Committee Has Five Votes and Three Expiry Dates
AFRINIC has filled a governance body with five voting members chosen through two different routes. The more important design feature may be the calendar: its seats do not all expire together, and its advice cannot bind the people who receive it.
History
Two Kinds of Nothing: How DNS Learned to Separate NXDOMAIN from NODATA
An empty DNS answer can conceal two opposite realities: the requested name may be absent altogether, or it may be alive and carrying every record except the one requested. The Internet had to make that difference portable, cacheable and temporary before saving queries could stop…
History
The Error That Learned to Expire: How DNS Cached What Did Not Exist
The expensive DNS question is not always the one with a large answer. It may be the miss that thousands of resolvers repeat because nothing can be stored. Negative caching gave absence a scope, evidence and an expiry time—then forced operators to accept that a newly created name…
History
The Core That Had to Stop Being the Core: EGP and the Invention of Autonomous Systems
The early Internet did not decentralize by pretending that every network agreed. It learned to survive disagreement. The Exterior Gateway Protocol drew a boundary around what one routing administration could keep private and what it had to tell its neighbours. That boundary made…
History
The Mail Address That Outlived Its Server: How MX Records Separated Identity from Delivery
An email address looks like a destination. In the early Internet, it often was: a mailer could take the domain after `@`, open SMTP to the machine with that name and hope the mailbox lived there. In January 1986, RFC 974 described why that assumption had stopped scaling—and how…
CASE FILE
A Verified RFC Erratum Corrects the Record Without Rewriting It
An RFC erratum can identify a real defect, supply corrected wording and be verified by the responsible parties. It still does not silently replace the published specification. That separation lets implementers learn from mistakes while preserving the text the community actually…
History
The Clock Built from Disagreement: How NTP Made Internet Time Without Trusting One Server
In 1989, an Internet-wide experiment found clocks wrong by minutes, hours and, in a few cases, weeks. The problem was not a shortage of machines willing to state the time. It was deciding which statements deserved to move a local clock when packets, oscillators and operators…
History
The Web CERN Chose Not to Own: How a Laboratory Designed Its Own Exit
The World Wide Web did not become universal merely because it was invented at a famous laboratory. It became portable across institutions because its common machinery was kept small, its specifications were public, its clients escaped one workstation, and CERN eventually removed…