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 Checksum That Had to Ask in the Old Language
A TCP endpoint could propose a different checksum without making an old peer fail. The old peer would ignore the unfamiliar option, answer normally, and thereby withhold the matching signal the experiment required. The fallback that made RFC 1146 safe to deploy also made…
History
The Flight TLS Sent Before the Server Finished: How False Start Borrowed One Round Trip
TLS False Start let a client release freshly encrypted application data after sending its own Finished but before verifying the server's. It saved a wait by moving data across an unfinished proof boundary—not by removing the proof, resuming an old session or sending plaintext.
IETF
Ross Callon and the UDP Port That Was Entropy, Not a Session
A familiar UDP header can make an MPLS tunnel look more conversational than it is. Ross Callon’s shared work on RFC 7510 shows why the source port is a path-distribution signal, while identity, admission, label meaning and congestion responsibility remain elsewhere.
History
The Address That Needed a Local Footnote
Copy `fe80::1%eth0` from one host to another and every character survives. The intended path may not. `eth0` belongs to the first host’s local map, so the apparently complete address carries a footnote whose authority ends at the machine that wrote it.
History
The Name TLS Had to Hear Before It Could Hide It: How SNI Made Shared HTTPS Possible
At a shared address, a TLS server had to choose a certificate before it could decrypt the HTTP request that named the intended site. Server Name Indication resolved that ordering problem by putting the name in the ClientHello—making virtual HTTPS practical while leaving the…
History
The Row That Existed Before It Was Ready
An SNMP manager can write `createAndWait`, yet it can never read `createAndWait` back. What returns may be `notReady`: the row now exists, but the device cannot yet attempt to use it. That asymmetry turned a request into an action and incompleteness into an observable fact.
History
The Memory the Server Sealed for Later: How TLS Session Tickets Made State Client-Carried
A TLS server learned to put its own resumable memory into a sealed entity and ask the client to bring it back. The arrangement saved per-client storage, but it did not abolish state: it concentrated acceptance in ticket keys, expiry rules and a fallback the server still…
History
Two Registrations, One Phone
The edge proxy had already crashed and restarted. The incoming call had already reached the service. The phone, however, had not yet learned that its old return path was gone. SIP Outbound was designed for precisely this interval—and for the harder question that followed: when…
IETF
Eric Vyncke and the Probe Label That Could Not Confer Trust
An unsolicited packet arrives before its explanation does. Eric Vyncke’s work on RFC 9511 asks whether a measurement sender can make that first encounter less opaque without demanding a new protocol, a central registry or automatic trust—and answers by drawing a hard line between…
History
The Server Carried the Proof: How OCSP Stapling Moved Evidence, Not Authority
A website could hand a visitor a signed answer about its own certificate without becoming entitled to write that answer. OCSP stapling made that separation useful—and left a less visible bargain over freshness, silence and who must keep the evidence available.
History
The Reply That Taught a Resolver to Stop Asking
A refusal can end a conversation, or send the question somewhere else. When DNS designers considered a new response code for servers unwilling to provide a conventional ANY answer, unfamiliarity could make resolvers try other authoritative servers. A small, nonempty answer…
History
The Header That Waited Behind Its Data
A variable-length header could stand between an arriving packet and a useful boundary in memory. In the early 1980s, BSD systems tried moving that obstacle: put the data first and its higher-level headers afterwards, then restore the ordinary arrangement at the receiver. Trailer…
History
A Map Pin Was Not a Measurement
DNS LOC could express a coordinate to a thousandth of an arcsecond while declaring a horizontal error circle ten kilometres across. That was not a contradiction. The format distinguished the fineness of an address on a map from the strength of the knowledge behind it. A consumer…
Story
RIPE RIS Generated the BGP Snapshot. Delivery Still Failed
The 25 August incident did not begin with a failed route collector. RIPE NCC says the 16:00 UTC bview files had been generated, yet they did not reach the public archive after a failover. That distinction turns a small status notice into a useful test of where a public…
Global Cloud Services Trends
Two Providers Receive 38.6% of Popular-Domain Mail. The Missing Metric Is Recoverability
Public DNS can show where a domain asks the Internet to deliver its mail. It cannot show how long that domain would take to leave.
History
Eight Bytes the Endpoints Could Not Negotiate Away
A PPPoE session could open successfully without carrying the packet size that justified opening it. The extension that addressed this problem separated permission, negotiation and a size-sensitive fallback. Its historical importance lay in a broadband migration: when the session…
History
The Forwarding Evidence an IP Error Left Out
The router removed the labels before it prepared the error. What remained could identify the original IP conversation while omitting the state that had governed its passage through the network. Adding that state to ICMP made a report more useful. It did not make the report a…
History
The Number That Came Back Unchanged: PPP’s Magic-Number
A PPP endpoint could receive the exact number it had just sent and be entirely satisfied. It could receive the same number in another kind of packet and suspect a loop. The distinction was not in the four bytes. It was in the action those bytes belonged to—and in the small…
History
The Message SMTP Could Forget Without Hanging Up: How RSET Defined Transaction Scope
One rejected recipient can leave a mail server holding an awkward remainder: a valid sender, one accepted destination and a message that should no longer be sent. SMTP’s quiet answer was `RSET`, an acknowledged way to forget that unfinished message while keeping the conversation…
History
Borrowed Bytes: How DHCP Reused Its Boot Fields
A thirteen-byte filename could be too large—not for a DHCP message, and not for an option, but for the space left in one field. Reusing old boot fields solved one shortage. Reassembling the pieces in an agreed order solved another. The distinction made a small extension into a…