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.
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…
IETF
Before CAPWAP Discovery, DHCP Ordered the Controllers a WTP Could Try: RFC 5417
A DHCPv4 or DHCPv6 option can place one access controller ahead of another in a wireless termination point’s bootstrap search. RFC 5417 makes that sequence a configured preference; discovery and DTLS still determine which peer can become the control endpoint.
CASE FILE
The Root DNS Saw Twice the Traffic. A Resolver Update Was the Clue.
For about a week, queries reaching the DNS root rose from roughly 1.6 million to 3.2 million per second. The traffic was valid, came from recursive-resolver networks, and did not measurably impair root service. The episode shows how a software change far upstream can become a…
IETF
RFC 5416: The 802.11 Binding Has an Era Boundary
RFC 5416 is easy to misread as a promise about every feature a modern Wi-Fi deployment may advertise. It is more precise than that: the CAPWAP binding fixes how an access point and controller exchange IEEE 802.11 information for the 802.11-2007 era. The leadership question is…
IETF
CAPWAP State Is Not Service Proof: RFC 5415
RFC 5415 gives wireless operators a structured CAPWAP control plane: an Access Controller manages Wireless Termination Points, establishes protected sessions, changes configuration and carries client data through defined modes. The useful leadership boundary is inside that…
Leaders
As Root-Zone Requests Grew, Kim Davies Rebuilt RZMS
By 2022, larger top-level-domain portfolios and more frequent DNSSEC key changes had outgrown the assumptions of the Root Zone Management System. Kim Davies described how an ICANN team rebuilt RZMS around configurable approvals, concurrent requests and technical checks that could…
IETF
WiCoP Is a Historic Control Record, Not a Deployment Baseline: RFC 5414
RFC 5414 describes WiCoP, a Wireless LAN Control Protocol for centrally managing and provisioning large WLANs. The RFC Editor marks it Historic and identifies RFC 5415 as the replacement. That status changes the question for a leadership team: a controller diagram or provisioning…
IETF
SLAPP Security Is a Historical Boundary, Not Deployment Proof
RFC 5413 records the Secure Light Access Point Protocol as submitted during the CAPWAP work. Its discovery, authentication and secure transport ideas are useful historical evidence, but the RFC Editor says the document was published solely for the historical record, was not…
IETF
LWAPP Is a Historic Record, Not a Deployment Baseline
RFC 5412 documents the Lightweight Access Point Protocol as it was submitted during the CAPWAP work. It is valuable archival evidence about an access controller and wireless termination point model, but the RFC Editor explicitly labels it Historic and says it should not be used…
IETF
CATS Chose the Service Contact. The Backend Stayed Hidden: RFC 10053
CATS can steer a request toward a promising service contact using network and compute conditions. That choice still may not reveal which service instance handles the request behind the contact, or whether the reported metrics describe that instance alone.
History
The Controller Needed a Network Before It Could Control One: RFC 7149
In March 2014, an IETF memo asked service providers to look past the seductive diagram of a central controller and ask a more operational question: how does that controller find, reach and safely influence the network beneath it? RFC 7149 treated startup, customer negotiation and…
IETF
A SIP Guide Is a Map, Not a Deployment Certificate.
RFC 5411 is useful precisely because SIP is too large to hold in one mental model. It groups the RFC series by topics, labels their status and points readers toward related work. But the document is an Informational snapshot, not a live inventory of what a carrier runs. A listed…
IETF
The Broadcast Extension Carried a Key Message. It Did Not Prove the Key Was Installed.
OMA BCAST needed MIKEY to carry more than one kind of control message: short-term keys, long-term keys, reporting data and parental-control information. RFC 5410 adds a General Extension payload for that transport. The payload proves that a particular message was encoded for a…
IETF
CMS Wrapped the Key. The Recipient Identity Still Had to Match.
RFC 5409 is not a general promise that “IBE works with email.” It defines the CMS conventions for encrypting a content-encryption key with Boneh-Franklin or Boneh-Boyen IBE, including recipient-identity encoding and algorithm identifiers. The envelope can be structurally valid…
IETF
The Identity Could Be a Public Key. It Still Was Not Permission.
An identity-based encryption design promises a neat operational shortcut: calculate a public key from the recipient's identity, encrypt immediately, and ask a trusted private-key generator for the matching secret only when the recipient needs it. RFC 5408 makes the shortcut…
Creators
A Phrase Traveled Without Its Author: Cory Doctorow and Interoperability’s Policy Boundary
When a Canadian parliamentary witness invoked Cory Doctorow’s phrase “adversarial interoperability,” she was speaking about a bill on copyright locks and software-enabled devices. The exchange carried an idea into a formal record, but it did not make Doctorow the witness, the…
IETF
A Better Edge Is Not Permission to Move the Session: RFC 10054
A client can leave the metro edge while its service remains stateful. RFC 10054 says a routing system may account for both network and compute conditions, but a mid-session move needs an explicit application indication that CATS is allowed. The faster destination and the…
IETF
The Channel Was Bound. The Operation Was Still a Separate Decision.
An SIP gateway showed a verified security context and a clean message check. The dashboard promoted that evidence into “authorised and complete.” RFC 5407 draws a harder line: SIP Version 2 can bind a SIP message to lower-channel information, but the binding does not become local…
IETF
The Channel Was Bound. The Operation Was Still a Separate Decision.
An IPsec gateway showed a verified security context and a clean message check. The dashboard promoted that evidence into “authorised and complete.” RFC 5406 draws a harder line: IPsec Version 2 can bind a IPsec message to lower-channel information, but the binding does not become…