--- title: "Echoes" canonical: "https://current.tinyfish.ai/issue/17/echoes" publication: "TinyFish" publisher: "TinyFish" language: "en-US" guide: "https://current.tinyfish.ai/llms.txt" permalink: "https://current.tinyfish.ai/issue/17/echoes" issue: 17 section: "echoes" description: "Past infrastructure decisions echoing in today's production realities" authors: ["Nora Kaplan","Rina Takahashi"] published: 2026-02-23 updated: 2026-02-16 articles: 11 --- # TinyFish > CURRENT is a journal about AI agents in production, for the engineering and product leaders who have to make them work. Drawing on experience building enterprise web agents, it explains why the demo succeeded and the deployment didn't, and what that means for choosing vendors, briefing the board, and avoiding mistakes others have already made. [Read on the website]() ## Issue 17 — Echoes Past infrastructure decisions echoing in today's production realities ### Address Space Archaeology - [The Workaround That Became the Foundation]() — By [Nora Kaplan]() · Published 2026-02-16 · Format: Address Space Archaeology IPv4 addresses trade at $35-52 each in 2026. Actual commodity instruments with brokers, escrow services, standardized contracts. Organizations lease them monthly. Over 40 million transferred last year. ### Protocol Fossils - [Protocol Decisions from 1987 Still Run Your Infrastructure]() — Published 2026-02-16 DNS packets were capped at 512 bytes in 1987 when lookups were simple. Now 75% of major websites exceed 738 bytes, forcing TCP fallback that fragments DNSSEC responses. The limit persists because changing it breaks middleboxes everywhere. ### The RFC Reader - [An Interview with the Protocol Archaeologist Who Reads 50-Year-Old Internet Standards]() — Published 2026-02-16 Bell Retrograde doesn't keep an office in any conventional sense. When I arrive at the converted warehouse space in Oakland, I find them surrounded by three monitors displaying RFC documents, a whiteboard covered in protocol diagrams, and what appears to be a hand-drawn timeline spanning 1969 to present. A cat named Parser sleeps on a stack of printed IETF standards. ### Protocol Timelines - [The 25-Year Overnight Success]() — By [Rina Takahashi]() · Published 2026-02-16 · Format: Protocol Timelines HTTPS worked perfectly in 1995. Banks used it, e-commerce used it, everyone else ignored it for twenty years. This October, Chrome defaults three billion users to encrypted connections. The technology stayed the same. Economics and social pressure shifted. Twenty-five years from optional to mandatory. The protocol was ready from day one. The baseline took a generation to shift. - [The Workaround Trap]() — By [Rina Takahashi]() · Published 2026-02-16 · Format: Protocol Timelines IPv6 launched in 1994 to solve address exhaustion. Thirty years later, adoption hovers around 45%. HTTP/2 launched in 2015 to speed up page loads. Five years later, half the web had adopted it. Same internet, same organizations, wildly different timelines. The gap shows what makes protocols stick or die quickly. Successful workarounds can trap infrastructure for decades. Backward compatibility determines whether transitions take years or generations. ### Further Reading - **When DNS Assumptions Break But the System Survives** — [Source]() — Published 2026-02-16 Design assumptions violated at scale, yet DNS adapted. National Research Council traces the gap between intention and reality. - **The End of End-to-End: When Network Intelligence Backfires** — [Source]() — Published 2026-02-16 Adding intelligence to networks was supposed to help. MIT Technology Review on why it created the failures instead. - **IAB's Warning: How NAT Undermined Internet Architecture** — [Source]() — Published 2026-02-16 Address translation solved an immediate problem. IETF document on the architectural compromise we're still living with decades later. - **The 1983 TCP/IP Migration and Its Address Space Legacy** — [Source]() — Published 2026-02-16 Transition decisions made under pressure created address constraints that outlasted the crisis. Internet Society traces the inheritance. - **Rough Consensus: How IETF Standards Actually Get Made** — [Source]() — Published 2026-02-16 No voting, just talking until something emerges. CDT guide to the surprisingly informal process that builds internet infrastructure. - **DNS Domain Wars: When Namespace Control Became Political** — [Source]() — Published 2026-02-16 Charging for domain names turned technical infrastructure into contested territory. Harvard traces the moment naming became governance. ## Other sections in Issue 17 - [Daily Brief]() - [Market Pulse]() - [Foundations]() - [Practitioner's Corner]() - [Vision]() ## More - [Publication guide]() - [Issue archive]()