Content Type
Case File
Within the Content Type facet, Case File 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.
IETF
WebAuthn’s 2026 Rejoin Handoff: The Governance Receipt Behind a New Participation Cycle
The Web Authentication Working Group’s 11 September 2026 recharter begins a new institutional phase for WebAuthn. The central challenge is not simply continuing technical discussion; it is preserving a reliable record of how an approved charter becomes active participation and…
CASE FILE
Sixty Names Were Defendants; the Statute Still Defined the Claim: Harrods v Sixty Internet Domain Names
The caption did something unusual: it named sixty domain names as defendants. That procedural choice made a dispute over the Harrods name look, for a moment, like a dispute over things rather than people. The Fourth Circuit’s answer was narrower. The names could be before the…
CASE FILE
The Registration Began with a Surname; Later Use Still Had a Separate Record: Nissan Motor v Nissan Computer
The label stayed the same while the page behind it changed. That difference—between the provenance of `nissan.com` and the later uses made of it—became the organising fact of a dispute that lasted through preliminary relief, a sweeping injunction, appeal and remand.
ICANN
The Domain Name Became the Defendant: Porsche.net and the ACPA's In Rem Route
A lawsuit that began by naming 128 domain names exposed a precise legal control problem: when a registrant cannot be reached through an ordinary personal action, what lets a federal court take authority over the registration itself—and when is it too late to challenge that route?
North America Cloud Services
The Sheriff Could Not Auction the Registrar's Service: Network Solutions v. Umbro
A portfolio of domain names looked like an asset a sheriff could sell. The Supreme Court of Virginia focused on the missing link: the winning bidder still needed Network Solutions to accept a new registration relationship and keep the names operational.
ICANN
The Takedown Notice Did Not Become a Verdict: Petroliam Nasional v. GoDaddy
The Ninth Circuit did not call every registrar passive or every takedown request futile. It drew a narrower, more useful line: a service provider's ability to maintain and forward a domain name does not create an unwritten ACPA claim that turns notice into adjudicatory authority.
ICANN
The Writ Reached ICANN; the Registry Data Stayed Abroad
The creditors proposed to sell or license operation of `.ir`. A court could reach ICANN in the United States, but an order changing the root-zone pointer would not deliver the foreign registry’s database, secure a competent successor or oblige the world’s networks to follow the…
CASE FILE
The 30 Percent Congress Legalised After It Was Collected
For two and a half years, every covered domain registration carried a public-purpose assessment that Congress had not specifically authorised. One month after a judge exposed the defect, Congress made the past lawful “as if” it had acted first.
Story
The Nine Applicants and the Missing Settlement in ARIN Arbitration
Nine companies asked a federal judge to stop ARIN from revoking their IPv4 records. Five months later, an arbitrator rejected every claim and incorporated a settlement that the public file says is attached—but is not.