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.
Academics
David J. Farber’s Interesting People List Made Debate Visible, Not Representative
A 1993 note from the mailing list’s moderator records both an open invitation and a retained editorial gate. The archive makes selected arguments inspectable; it does not measure what Internet users thought.
History
Archie’s Search Was Only as Fresh as Its Last FTP Listing
Archie made a scattered set of anonymous FTP archives searchable by collecting their directory listings. That small distinction shaped the service: its answer could point to a filename and a place, but the file still lived on someone else’s machine—and the index could only…
History
The License Covered the Code, Not the Protocol: Gopher’s 1993 Line
On 11 March 1993, the Minnesota Gopher Team opened a newsgroup post by saying it had heard enough “hysteria” and rumor to set out an official position. The phrase that later stuck was simple: commercial users would need a licence. The policy that followed was not. It divided…
IETF
RFC 10065 makes the group ID a control input, not proof of enforcement
RFC 10065 gives operators a way to carry group identity into network access rules. The harder question begins after the identifier arrives: who owns its mapping, where is the rule installed, and what evidence shows that the right traffic was actually controlled?
Leaders
Alan Greenberg and the Request That Opened a GNSO Policy File
A May 2007 email from Alan Greenberg carried an ALAC decision into the GNSO’s formal process: ask ICANN staff to examine domain tasting. The request opened a route to deliberation; it did not decide the policy or speak for every Internet user.
History
The Plug Had Four Pins: NORDUnet and Europe’s Protocol Choice
In May 1988, a Nordic research network asked the United States for a route into NSFNET while promising to carry several rival network services at home. Its four-pin plug became a practical answer to a harder question: could researchers share a backbone before they agreed on one…
Leaders
Tina Dam and the Root-Zone Test That Couldn’t Approve a Name
Before an internationalized top-level domain could enter the root, ICANN asked a deliberately narrow question: would encoded labels disturb the servers and resolvers that move DNS queries onward? The laboratory test answered that question within its setup. It could not decide…
IETF
Syslog Could Report Clock Quality. Operators Still Had to Set Its Bounds: RFC 5424
A timestamp can travel farther than the conditions that made it credible. RFC 5424 gave a syslog originator a compact way to describe those conditions, but the description was only as sound as the clock configuration and monitoring behind it.
IETF
Inside EAP-FAST, Type 6 Meant Something Else: RFC 5421
RFC 5421 placed a familiar EAP method code inside a new frame: Type 6 still looked like Generic Token Card, but inside an EAP-FAST tunnel it selected a differently formatted inner exchange. The specification drew a strict boundary between those meanings; its IESG note warned that…
Academics
Lorrie Cranor’s Privacy Labels Need a Trail From Code to Store
The work around Google Play’s Data safety section points to a practical question: can a developer trace each store declaration back to code and SDK behavior? Lorrie Cranor’s research on usable privacy puts that translation problem inside the software workflow.
IETF
Provisioning Success Still Needed an Access Decision: RFC 5422
RFC 5422 separates completed credential provisioning from permission to use network resources; its server-unauthenticated mode is explicitly provisioning-only.
History
Publishing the Flaw Was Not Publishing the Worm: RFC 1135’s Disclosure Debate
The 1988 Internet worm left a question that was easy to flatten into “publish or conceal.” Contemporary records show a narrower choice: explain the defects and the program’s methods, distribute fixes, or release a working decompilation that lowered the effort needed to make…
Leaders
Rebecca MacKinnon’s Return Puts Two Accountability Methods in View
When Rebecca MacKinnon returned to the Global Network Initiative in August 2026, she brought a useful history into view: she helped found both GNI and Ranking Digital Rights, but the organizations examine accountability through different evidence. A 2020 RDR scoring rule treated…
IETF
AAA Knew the Subscriber. The Home Agent Still Needed a Key: RFC 5419
RFC 5419 explains why some Mobile IPv6 operators wanted subscriber authentication to ride on an existing AAA relationship. Its more revealing question is what happens after that decision: the home AAA server may recognize the subscriber, yet the selected Home Agent still needs a…
History
Routine Did Not Mean Unreviewed: RFC 6709’s Test for Protocol Extensions
In protocol design, “routine” can sound like a verdict that a change is too small to matter. RFC 6709 used it more narrowly. An extension was routine only when the base protocol and deployed implementations could treat it as opaque without harm. That says something about…
IETF
A CAPWAP Credential Did Not Enroll a Device in the Network: RFC 5418
RFC 5418’s 802.11 threat model separates WTP–AC authentication from deployment membership, device role and the path client traffic takes. A valid session settles only part of the operating question.
History
One Internet, Many Operators: RFC 1462’s Telephone Analogy
The 1993 FYI used a familiar phone call to explain an unfamiliar topology: users experienced one Internet service, while separate networks operated and repaired their own sections.
History
NAT Was a Function, Not an Interface: Why RFC 4008’s MIB Had to Change
In 2005, a management station configuring NAT through RFC 4008 had to begin with an interface index. Ten years later, the successor MIB described NAT as a logical function that could span interfaces, address realms, subscribers, and multiple instances. The change was a correction…
Leaders
Anriette Esterhuysen’s IGF Framework Defined Capacity by What Institutions Could Sustain
The Internet Governance Forum’s 2021 report can count grants, supported entities and workshops. Anriette Esterhuysen’s earlier framework asked a longer question: could people and their institutions keep setting and pursuing their own Internet-policy goals after the event was…
History
The Frame Crossed the Pseudowire. Its Service Role Did Not: RFC 7152
In 2014, an IETF requirements memo exposed a small but consequential gap in Layer 2 VPNs: a provider-edge router could receive an Ethernet frame across a pseudowire without knowing whether the frame had entered the remote network through a root or a leaf attachment. RFC 7152…