Content Type
Research
Within the Content Type facet, Research 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
Stephen Wolff and the Boundary Between a Public Backbone and a Market
A packet could not explain whether it served scholarship or commerce. NSFNET nevertheless had to draw that distinction while it was becoming the principal American research backbone. Stephen Wolff’s most revealing contribution was to treat commercialization and privatization as…
IETF
An OAuth Remediation Challenge Is an Authority Proposal, Not a Retry Hint
A payment request fails, and the client receives an unusually helpful answer. The resource server does not merely say no. It supplies the structured authorization it says would make the operation acceptable. The client can carry that entity into a new OAuth flow and try again.…
History
Hans-Werner Braun and the Numbers That Made a Backbone Governable
Hans-Werner Braun helped operate NSFNET at the moment when a research network was becoming national infrastructure. His most durable lesson is not a router model or a speed record. It is that a backbone becomes governable when its operators can show, in public and with honest…
IETF
A ULD Server Handoff Needs Proof That Local Services Survived
The network can stay up while the printer, display and local controller quietly disappear. That is the awkward possibility inside a seemingly clean Unicast Local Discovery transition. A client may correctly choose a better server, close its old path and report success. Yet the…
History
RFC 2061: When a Mail Preview Needed a Cleanup Write
In December 1996, [RFC 2061](https://www.rfc-editor.org/rfc/rfc2061.html) offered IMAP4 clients ways to keep working with older servers. One fallback could retrieve a preview and then require a flag change: preserving access did not preserve every promise attached to it.
History
Pål Spilling and the Cable That Made Norway Both Reachable and Vulnerable
Norway’s first Internet connection was a door to a global research community—and, for a time, a single physical point at which that door could be shut. Pål Spilling’s career shows why a network’s topology is also a map of authority: it decides who can connect, who absorbs…
IETF
Deep-Space QUIC Moves Congestion Control into Mission Control
On Earth, a transport usually infers what the network can bear from acknowledgements, delay and loss. Between planets, that feedback can arrive after the useful moment has passed. A new IETF working-group draft responds by letting mission schedules govern QUIC’s rate, window and…
History
Louis Pouzin and the Network That Refused to Remember the Conversation
CYCLADES asked what a packet network should be trusted to know. Louis Pouzin's answer was deliberately austere: let the switching system move independent datagrams, and make the computers at the edges responsible for turning them into a reliable conversation. That division of…
IETF
The Rate in a DHCP Reply Is Not a Speed-Test Result
A new IETF draft would let broadband networks send upstream and downstream rates through DHCP. The number may shape a queue, populate a router screen or influence an access node, but it still describes a provisioning decision. Treating it as measured performance would erase who…
IETF
PIM Light’s Missing Hello Leaves Two Redundancy Decisions Outside the Interface
RFC 9739 lets multicast state cross a boundary without first establishing a PIM neighbour. The useful simplification leaves the network responsible for choosing who forwards a Join, preventing duplicate streams and turning a detected failure into an actual withdrawal.
History
George Sadowsky and the Workshops Designed to Outgrow Their Teachers
The Internet Society's network-training workshops were built around a demanding test of technical assistance: would the people in the classroom still need the visitors when the next router failed? George Sadowsky's contribution was to make the answer less dependent on equipment…
IETF
A Successful NFS Lookup Does Not Make a Filename Portable
A storage team can open a file by name every day for years and still discover, during a migration, that it never knew what made that name work. The bytes may have matched exactly. A server may instead have recognised two canonically equivalent Unicode sequences, ignored case…
History
Peter Kirstein and the Transatlantic Node That Was More Than a Terminal
When ARPANET reached London in 1973, the scarce asset was not simply a line across the Atlantic. Peter Kirstein's achievement was to turn UCL from a distant customer of American machines into a place where British researchers could attach computers, implement protocols, operate…
IETF
A Cable Record Is Not Proof the Cable Is There
A repair crew arrives at a roadside cabinet with a clean inventory view: one optical cable, the expected number of fibres, two named endpoints and a location reference. The screen is internally consistent. The trench is real. Yet the label on the closure belongs to an earlier…
IETF
The Parser Stopped. The Header Did Not Disappear: RFC 9740
A traffic report can register no use of a header because the header was absent, because an old field could not represent it, or because the exporter stopped looking. RFC 9740 gives those differences a more precise vocabulary. The consequential decision is whether a collector…
History
Dai Davies and the Buyer Europe Did Not Yet Have
In 1993, Europe’s national research networks did not mainly lack ambition. They lacked a counterparty. Someone had to turn many countries’ requirements into one specification, take that specification to a guarded telecommunications market, award contracts, reject deficient…
IETF
A Correct Registry Cannot Repair a Wrong ASN.1 Module
Two implementers can read official material, write conscientious code and still produce systems that refuse to speak to each other. That is what the authors of a new IETF draft say happened with RFC 6211: one implementation followed the entity identifier printed in the RFC…
IETF
The old connection is the test
An accepted QUIC configuration and a healthy service can coexist without proving that the connection already carrying work adopted the change. Revision 08 of the QUIC YANG draft puts that missing proof inside the implementation: the operational question is what changed in the…
IETF
Who Owns the Extra Spellings? RFC 9741 and the Cost of Text Aliases
A permissive decoder can spare a client a repair while giving another team a reconciliation problem. RFC 9741 makes a small but consequential distinction visible: accepting two texts as one value does not decide whether they are one resource, one approval or two billable…
History
Klaas Wierenga and the Credential That Stayed Home
A student from Delft opens a laptop in Cape Town. The local university can offer a network, but it cannot vouch for the visitor’s account. Delft can vouch for the account, but it does not control the Cape Town network. Klaas Wierenga’s decisive contribution to eduroam was to make…