Content Type
Analysis
Within the Content Type facet, Analysis intelligence gathers BTW.MEDIA articles that share the same editorial format, helping readers compare briefings, profiles, risk notes, market analysis, and event coverage without mixing different kinds of evidence. The page explains how this content type frames internet infrastructure events, company movements, governance decisions, operational signals, and public evidence across the site. Readers can compare which actors or infrastructure systems appear most often, how source quality changes interpretation, and whether the material is a durable profile, a time-sensitive event, a strategic market signal, or a governance development. The result is a useful search page for operators, investors, customers, analysts, and policy stakeholders who need to understand the consequence, timing, and evidence behind similar article formats.
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…
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…
Global Regional ISP Trends
Hyperoptic coverage is not serviceable until the building says yes
A broadband map can colour an address as covered before anyone has secured the right to open the riser, use the shared duct or enter the corridor that leads to the flat. Hyperoptic’s own installation documents show why the useful unit of coverage is not the postcode but the…
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…
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…
ICANN
One Portal, No Clock: Who Actually Grants Zone-File Access?
CZDS lets a researcher ask many generic top-level-domain registries for zone files from one place. The common doorway is easy to mistake for a common decision. It is neither automatic access nor a single permission desk.
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…
ICANN
When ICANN Ends a Registrar, Who Receives the Domains?
ICANN’s public bulk-transfer table shows a terminated registrar, a gaining registrar and a date. The missing middle is the consequential part: who was eligible to receive the registrations, which operating promises mattered, and what the decision did—and did not—give the…
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…
History
Two Queries, Two Servers: Why DNS Needed NSID
A service address can stay the same while the machine answering changes. DNS needed a way to identify the instance behind a particular reply, not merely whichever instance answered the next question. The resulting standard made the association precise while leaving the identity…
History
The Random Bit That Congestion Erased: The ECN Nonce Experiment
An experiment can work and still lose its claim on shared protocol space. ECN Nonce made a receiver's congestion report testable by exploiting information a router had destroyed. Its withdrawal illuminates both the limits of that test and the cost of keeping an experiment alive…
History
The Name That Entered Through Port One: TCPMUX and the Scope of Coordination
A two-page proposal from 1988 let a new service borrow a common entrance instead of acquiring its own official TCP port. The interesting question was not whether numbers disappeared, but which decisions could now remain inside the host.
History
The Bit That Could Not Keep a Service Running: Why DNS WKS Never Became a Live Directory
Before opening a connection, an early Internet mailer could inspect one bit in DNS and decide whether a server existed. The bit was exact. The world behind it was not.
History
The Answer That Could Only Name What One Server Knew: Why DNS Retired IQUERY
A DNS request once arrived with no question at all. Instead, it placed a resource record in the Answer section and asked the server to supply every name that matched it. The reversal looked elegant on paper: if an ordinary query mapped a name to a value, an inverse query would…
History
The Reply That Could Not Say Which Packet Arrived: How Karn’s Algorithm Taught TCP to Refuse a Measurement
A sender transmits one TCP segment, waits, and sends the same sequence space again after its timer expires. An acknowledgment then advances. Delivery has become visible, but causation has not: the ACK carries no label saying whether the first transmission was merely slow or the…
History
The Mask That Silence Guessed Wrong: How ICMP Bootstrapped a Subnet
A host wakes with an IPv4 address but no rule for deciding which destinations are on its own wire. It broadcasts a question: what mask divides this address into network, subnet and host? Nothing answers. The old specification permits a conservative guess—the unsubnetted mask…