Profile
Research
Research profile intelligence connects person, company, institution, and other entity coverage for readers comparing the subjects behind BTW.MEDIA reporting. The page helps compare public profiles, related events, evidence packs, role changes, operating footprints, governance exposure, organisational links, and market relevance while keeping organisation and people records distinct from ordinary news chronology. Readers can understand the subject behind the headline, the evidence supporting that profile, and the infrastructure or market relationships that make the profile relevant. They can see who or what the profile represents, which public sources support it, how it connects to companies, markets, governance bodies, or events, and what changes may deserve continued attention as the subject evolves.
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…
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…