BTW.Media
Daily editionStrategic Internet Intelligence
Sign InRegister

Live Wire

View all briefings
Cloudflare’s 2022 outage: rollback did not prove independent failover|Rogers’ 8 July Outage: What the Public Record Can—and Cannot—Prove|GlobalFoundries expands chip capacity for Marvell|China proposes BRICS open-source AI community|MTN partners UAE investor on African data centres|VodafoneThree puts Ericsson 5G core live|Theseus names Raval to lead Anthropic build-out|Tencent Cloud, U Mobile partner on 5G and AI|Community Fibre launches 8.5Gbps in London|Openreach finds London behind on PSTN migration|Meta raises Utah data centre spend to $3bn|Nokia links network data to Microsoft Fabric

Lead Report / History

Three brass routing stations send ivory message capsules to a glowing terminal only, a mailbox fallback, or a terminal and mailbox together.
Early SMTP could ask for more than mail. One command demanded that the text appear on a user's live terminal, another treated the terminal and mailbox as alternatives, and a third attempted both. Those verbs made a fleeting human state—logged in and willing to be interrupted—part of the transport contract. Their disappearance shows why the Internet learned to separate durable custody from immediate attention.

The Message That Tried to Arrive Before the Mailbox: How SMTP Abandoned Terminal Delivery

Early SMTP could ask for more than mail. One command demanded that the text appear on a user's live terminal, another treated the terminal and mailbox as alternatives, and a third attempted both. Those verbs made a fleeting human state—logged in and willing to be interrupted—part of the transport contract. Their disappearance shows why the Internet learned to separate durable custody from immediate attention.

Read Full AnalysisHistory Intelligence
  1. Two 1980s computer systems exchange a continuous amber block stream while a separate control line pairs two distinct checkpoint tokens above a stable storage vault

    History

    The Checkpoint That Was Not a Byte Number: How FTP Learned to Resume a File

    Midway through an FTP transfer, a reply could appear on the control connection: `110 MARK ssss = rrrr`. It did not say that a certain number of bytes had arrived. It joined one position understood by the sending system to another position understood by the receiving system—and the data was not supposed to stop while the reply travelled. Long before “resume download” became a button, FTP treated recovery as a problem of preserving two local meanings at one committed boundary.

  2. An ivory cable returns to two sockets on the same navy test block beside matching blue markers while a separate terracotta block remains unconnected

    History

    The Number That Came Back Unchanged: PPP’s Magic-Number

    A PPP endpoint could receive the exact number it had just sent and be entirely satisfied. It could receive the same number in another kind of packet and suspect a loop. The distinction was not in the four bytes. It was in the action those bytes belonged to—and in the small history each endpoint kept for itself.

  3. A blank ivory manuscript rests in a reversible brass carrier between a circular collective review table and a separate neutral archive tray.

    IETF

    IETF’s 2418bis Draft Adds an Exit State for Adoption

    The dependency register showed a green `WG Document` badge beside a draft that no longer attracted editors or review. When the working group removed the draft from its active work set, the register replaced green with grey and wrote “proposal rejected.” That last phrase was not in the decision. On 17 August 2026, the latest draft revision of the IETF’s working-group guidelines added a way to name this missing transition: a working group can return an Internet-Draft to a non-adopted state.

Member Access

Your daily intelligence edge starts here

Strategic Circle turns infrastructure moves, policy shifts and market signals into a concise briefing in your chosen language—plus the research library and member forum—for USD 20/month.

  • 01Daily intelligence brief
  • 02Governance + market + RIR
  • 03Preference control anytime
Explore Strategic CircleSign In

BTW Media on Air

Selected briefings, interviews, and live sessions from the BTW intelligence team, focused on internet infrastructure, governance, and market signals.

View All

5G Is Live in 7 Cities—So Why Does Your Phone Still Show 4G?

A 5G Network Counted the Crowd Without Identifying People

This AI Data Centre Wants 900MW. The Grid Won’t Supply It.

This Cell Tower Crossed the Pacific in the Stratosphere

AI Logged 13.88 Million Hours. What Does That Actually Mean?

VPN Restriction” Can Mean 4 Very Different Things

Cape Town Data Centres: Approved, but Still Contested

More Investment, Longer Wait: The VTS Cable Moves to 2030

Satellites in Orbit—So Why Isn’t the Network Ready?

This Airport Built Its Own 5G—Not for Faster Phones

Traffic Dropped. Your MongoDB Atlas Bill Might Not.

37 Million T-Mobile Accounts Exposed—What Could Attackers Actually Do?

3× Free Egress Isn’t Three Free Downloads

One More Slack Channel Can Change the Guest Role

Not Sold. Still Unavailable. Here’s Why.

An amber value query searches one bounded server while separate cyan DNS name trees remain outside its reach

Governance

The Answer That Could Only Name What One Server Knew: Why DNS Retired IQUERY

A DNS request once arrived with no question at all. Instead, it placed a resource record in the Answer section and asked the server to supply every name that matched it. The reversal looked elegant on paper: if an ordinary query mapped a name to a value, an inverse query would map the value back to names. But DNS had distributed its authority by names, not by every possible value stored beneath them. IQUERY could search one server’s memory; it could never establish that the server was the right place to ask or that its list was complete.

Two IPv6 packet variants encounter different parser depths along the same network path.

Market / Trends

IPv6 Extension Headers Are Becoming a Path-Compatibility Tax

The address answers. Ping works. Then the transport header moves 64 bytes deeper into an otherwise valid IPv6 packet, and the path goes quiet. Basic reachability survived; optional capability met the smallest parser on the route. It is a compact demonstration of how a protocol feature becomes somebody else’s hardware budget.

A vast scrubbing manifold removes red attack traffic while clean blue traffic narrows through two tunnels, a measurement prism and one customer handoff.

Market / Companies

A DDoS Scrubbing Contract Must Say Who Delivers the Clean Gigabit

A mitigation cloud can absorb an attack measured in terabits and still leave one customer's legitimate traffic dependent on a much smaller circuit, tunnel and router. The purchase decision is therefore not only how much hostile traffic the provider can discard. It is what clean traffic the contract obliges the whole delivery chain to carry, where that obligation is measured, and what happens when the platform is healthy but the protected service is not.

Over-the-shoulder view of an anonymous engineer studying abstract finite stack-depth and control-plane constraint graphics on text-free screens.

Market

Jeff Tantsura and the Operational Limits Made Visible by Maximum SID Depth Signaling

Jeff Tantsura's co-authored standards work on Maximum SID Depth shows why path computation needs an accurate record of what a running node can actually impose, carried with enough type and scope to remain useful from the IGP to BGP-LS and PCEP.

Six matching board chairs and one distinct executive chair face blank delegation folders connected to five chairless specialist worktables.

Governance / NOGS

After the Ballot: How Power Travels Through NANOG's Appointed Committees

NANOG's members elect most of the Board, not the specialist bodies that shape programmes, elections, audits and community work. The case for appointment is strong; the harder question is whether the public record lets a reader follow each grant of authority from selection to decision, review and eventual renewal or end.

Editorial position

Why BTW Media exists

  • Reality over advocacy
  • Evidence over sentiment
  • Systems over noise

Internet governance is too often described as theory, consensus, or institutional comfort while operators live with the consequences of structure, scarcity, jurisdiction, and incentives.

BTW shows how the system works when assumptions are tested: clear, uncomfortable, evidence-led reporting that keeps attention on structure rather than drama. Public reporting is published to travel: it may be indexed, quoted, translated, used in search and AI answers, and used to train models so the evidence can shape how infrastructure questions are understood.

Core Architecture

Governance, market, and membership branches operating in one integrated intelligence model.

Governance

  1. A Proposed Charter Is Not a Working Group Mandate
  2. The Command That Gave Away the Connection: Why SMTP Replaced TURN with ETRN
  3. A DNS Filtering Notice Is a Chain of Three Decisions, Not One Explanation
  4. The Timeout That Could Speak Only After Fragment Zero
  5. The Proposed RFC SLA Can Pass While Authors Still Wait
  6. The Bit That Could Not Keep a Service Running: Why DNS WKS Never Became a Live Directory
  7. An Expired Internet-Draft Is Not a Rejected Proposal
  8. The Number That Became Newer After Zero: How DNS Ordered Versions Without a Clock
  9. The Router That Pointed Sideways: How ICMP Redirect Stayed Local
  10. The Record the Receiver Could Not Hold: How TLS Made Size a Local Claim
View Governance

Market

  1. From 200 Days to 47, TLS Renewal Becomes Runtime State
  2. The Zero-Egress Invoice Is Not the Cost of Leaving Scaleway
  3. The Denominator Behind the Uptime Promise
  4. The Default Slice Can Make a 5G SLA Look Healthy
  5. GitHub's Attestation Proves a Build Path, Not a Safe Binary
  6. Monitoring’s FTTH menu exposes where passive access ends and power responsibility begins
  7. DMTF: The Standards That Control Servers Below the Operating System
  8. Cloud Portability Has a Postcode
  9. Boldyn's £1bn Tube network must earn its 20-year lock-in
  10. Green Dot's US$42.3bn B2B Gross Dollar Volume Rose 22% as Purchase Volume Rose 1%
View Market

Membership

  1. The Message That Chose Failure Over Cleartext
  2. ICANN Wrote a 24-Hour Disclosure Clock. Authentication Decides When It Starts
  3. The Relay That Added Context by Cutting Off the Message
  4. Two Registrations, One Phone
  5. The New Key That Inherited Its Past: What TLS KeyUpdate Could Rotate
  6. The 90-Day Emergency Policy That Kept Domain Registration Data Moving
  7. The Knock That Brought the Client Back
  8. The Link the Origin Asked to Remove: Why HTTP 410 Was Not 404
  9. The Row That Existed Before It Was Ready
  10. Sally Floyd and the Test That Throughput Alone Could Not Pass
View Membership

Number Resource Society

Reporting on address stewardship, representation, and the institutions shaping number-resource governance.

View Number Resource Society
  1. A Member Logo Is Not a Live Power of Attorney
  2. A Country Field Is Not an RIR Mandate
  3. A ROA Change Needs an Authorization-and-Withdrawal Ledger
  4. An Unanswered Profile Needs a Reply-State Ledger
  5. The FAQ Answer Needs a Version Date
  6. Bayan Telecommunications, AS6648 and the Boundary Between Network Records and Control
  7. When One Corporate Group Casts Twenty Registry Votes
  8. Digital Identity Requirements at the Registry Gate
  9. A Global South Label Cannot Substitute for a Mandate

RIR Watchdog

Five regional sessions: ARIN, RIPE NCC, APNIC, AFRINIC, and LACNIC.

Network Operator Group (NOGs)

Operational intelligence from the communities where routing, peering, resilience, and deployment practice are tested.

View Network Operator Groups

History of the Internet

The internet's hidden roots in military strategy

Structural context for current governance behavior and infrastructure control models.

An amber request capsule is stopped at a barrier marked 425 before an incomplete handshake ring, while the same capsule passes after the ring closes

The Request That Had to Wait for Proof: Why HTTP Needed 425

TLS 1.3 let returning clients send requests before a new handshake finished. HTTP 425 made replayable early data wait without changing the request itself.

  1. The Receiver That Chose What Came First
  2. The Save That Left the Page Intact: HTTP 204
  3. The Address That Grew Old Before It Died
Open History Session

Leadership Alliance

Global AI summit launches as world enters implementation decade

Capital, policy, and institutional leadership alignment in cross-border digital systems.

One IPv4 datagram enters a splitter; three fragments emerge, but only the zero-offset fragment retains both option modules.

The Instruction That Had to Survive the Split

One IPv4 datagram entered a router with two options. Loose Source and Record Route, type 131, had its high bit set. Record Route, type 7, did not. When the router cut the datagram into three fragments, the zero-offset fragment kept both options; the other two kept only the source-route instruction. Their headers were deliberately unequal. One bit had separated state every fragment needed from state whose authority remained with the beginning.

  1. The Address That Needed a Local Footnote
  2. The Host That Learned a Small Routing Table: How IPv6 Ranked First Hops
  3. The Session Ticket Could Not Remember the Protocol
Open Alliance Session