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
The Username Looked Like a Person. The Namespace Only Promised a Slot: RFC 1439
In 1993, a tidy rule for turning names into email accounts met a problem that no directory card could hide: two people could produce the same string, and a successful delivery could still reach the wrong human. RFC 1439 treated the collision not as clerical untidiness but as a…
Global Institutional
OIF and the work of making 1.6-terabit links agree
The Optical Internetworking Forum sits between formal standards and commercial products, turning optical, electrical and management choices into implementation agreements that vendors can build and operators can test. Its influence is clearest when several layers have to work…
History
The File Arrived. The Recipient Had Not Accepted It: RFC 1440
In 1993, an experimental Internet protocol tried to deliver a file the way a network might deliver a parcel: the sender pushed it without logging into the destination, the receiving host put it aside, and the named recipient decided what to do later. That convenience depended on…
History
The WAN Session Was Up. The End Stations Still Had Two Links: RFC 1434
In an early-1990s network, a terminal could believe it was talking to a distant peer while every acknowledgement it saw came from a router in the same room. RFC 1434 made that split deliberate: keep fragile local link timing local, build another circuit between switches, and…
Global Institutional
Batfish and the promise of testing a network before it changes
Batfish turns multi-vendor configurations into a model of routing and forwarding so operators can ask whether reachability, policy and failure behaviour survive a proposed change before touching production. Its answers can be exhaustive inside the model, but their operational…
History
The Codes Aligned. The Circuit Still Needed Permission: RFC 1394
A two-letter domain, a telex answerback and a telephone prefix could all point toward the same country and still leave a message nowhere to go. RFC 1394 made those correspondences useful by placing them in one table. It also marked the table's limits: values could be wrong…
History
The Route Named a Next Hop. The Link Still Had to Agree: RFC 1433
Two machines could occupy the same data-network service and still be unable to exchange a frame. RFC 1433 began from that uncomfortable fact: routing could identify a shorter next hop, while address resolution and link filters retained the power to make the route usable—or turn…
Creators
Albert Greenberg and the network as a distributed computer
Across AT&T, Microsoft Azure and Uber, Albert Greenberg has worked on a recurring problem: how to make a large network behave like one coherent system when topology, traffic, control software, hardware and failure all change at different speeds. His influence is best understood…
Story
Inside AFRINIC’s Reverse-DNS Cleanup
The registry’s public data distinguish delegation records, domain entities and resource holders. They also distinguish an error inventory from removal events. Those differences explain why a falling count can reflect worthwhile maintenance without measuring the restoration of…
History
The Interim Fix Bought Time. It Could Spend the Future: RFC 1380
The Internet of 1992 had more than one deadline. Router tables and Class B allocations were under immediate pressure; a larger address space and a richer Internet layer demanded slower architectural work. RFC 1380 refused to hide that mismatch inside one programme. It recommended…
History
The Network Found the Book. It Could Not Keep the Shelf Current: RFC 1432
In March 1993, a bibliography about the Internet carried an unusually revealing provenance: much of its detail had arrived through the Internet itself. The network could help a reader discover a book, yet RFC 1432 also preserved the reasons discovery could never certify the…
History
The Transport Opened a Connection. SNMP Still Owned the Retry: RFC 1283
A connection is an enticing piece of evidence. It has a beginning, a lifetime and an end. In 1991, RFC 1283 placed SNMP on an OSI connection-oriented transport and then warned implementers not to read too much into that new structure. The connection could carry one or more…
History
The Client Found the Person. The Score Still Belonged to One Directory: RFC 1431
A successful search can be the beginning of an evaluation rather than its conclusion. In February 1993, RFC 1431 asked what an X.500 directory client had actually accomplished when a person's entry appeared—and what the answer had cost inside one particular directory.
History
The Rule Was Voluntary. The Sanction Still Needed a Local Mandate: RFC 1281
A network can share a rule without sharing a government. RFC 1281 began from that awkward fact. The Internet of 1991 depended on voluntary cooperation, yet security failures crossed institutional borders and demanded action. The memo's durable insight was not that goodwill could…
History
The Gateway Rewrote the Message. It Could Not Invent the Charset: RFC 1428
The old message arrived as eight-bit octets and a social fact. Somewhere, sender and reader knew what those bytes meant. The message itself did not say. In 1993, a gateway standing between that installed mail world and MIME could add structure, recode headers and leave a trace of…
History
The Domain Entry Pointed to the Organisation. It Was Not the Organisation: RFC 1279
The most disciplined line in RFC 1279 was not about search speed or a grand replacement for DNS. It was about identity. A domain and an organisation were different entities; a mailbox and a person were different entities. The proposed directory could connect them, but it was not…
History
The Fallback Was Written Down. Running Servers Still Broke the Session: RFC 1425
The old server was supposed to say that it did not understand `EHLO`, remain connected and let the client try `HELO`. That was the elegant transition drawn in RFC 1425. Seventeen months later, its successor had to record what running systems actually did: some dropped the…
History
The Shortcut Was for Display. The Stored Address Had to Outlive It: RFC 1278
The sharpest sentence in RFC 1278 comes after the convenient machinery. Macros could shorten a long presentation address, nest inside one another and choose the longest available substitution for display. Then the memo drew the line: no macro should ever be relied on. In 1991…
History
The Mail Stayed Readable. Every Rewrite Became the Verifier's Problem: RFC 1421
The words were already on the screen. A recipient could read the paragraphs, understand the request and even act on them. Yet the machine still had a different question: were these the same canonical lines that the sender had signed? In RFC 1421's `MIC-CLEAR` format, human access…
History
The Plan Was Published Before the Result. The Announcement Could Change the Sample: RFC 1273
The awkward number in RFC 1273 was not 73,760 connection attempts. It was the cost of explaining them. In the study’s initial tests, messages intended to notify remote administrators generated more network and administrative load than the measurement itself, while roughly half…