BTW.Media
Daily editionStrategic Internet Intelligence
Sign InRegister

Live Wire

View all briefings
A Client Can Keep Its Name While Its Refresh Token Loses Its Key|The Maintainer Behind Kazakhstan's NovaCloud: Where Registry Control Actually Sits|The Third Message Was Encrypted. Neither Side Was Authenticated Yet|A Signed Wallet-State Boolean May Not Name the Wallet|ASH Repair Must Acknowledge Before It Asks Again|A Default IPv4 Exit Needs Authority After a Mapping Rule Is Withdrawn|IDMEFv2 Makes 204 a Receipt—and Leaves the Retry Ledger to the Alliance|Removing an OAuth Attester Is Not a Kill Switch for Issued Access|DTPC Lets an Application Delete Yesterday Before the Network Sends Today|ALPSiX’s first three listed prospects already appear on AAIX’s roster|A Proof of “We Cannot Tell” Still Has an Evidence Boundary|BGP Found a Reachable Address. It Had Not Yet Measured the Path That Would Carry the Packet

Lead Report / History

Two endpoint cabinets expose unchanged payload layers beside separate integrity mechanisms, while twin optical lenses cannot distinguish identical packet shells and an optional wrapper collar.
RFC 2410 gave IPsec an encryption algorithm that changed no bit at all. That apparent joke solved a serious interoperability problem: two endpoints could agree explicitly to use ESP for integrity without confidentiality. Yet the same ordinary ESP packet did not give an intermediate observer a deterministic way to know that the payload was unencrypted—and visibility still did not confer permission to inspect it.

NULL Was a Negotiated Choice. The Packet Did Not Advertise That Choice

RFC 2410 gave IPsec an encryption algorithm that changed no bit at all. That apparent joke solved a serious interoperability problem: two endpoints could agree explicitly to use ESP for integrity without confidentiality. Yet the same ordinary ESP packet did not give an intermediate observer a deterministic way to know that the payload was unencrypted—and visibility still did not confer permission to inspect it.

Read Full AnalysisHistory Intelligence
  1. A brass translation gate locks one luminous session onto a single server path while three other servers remain available.

    History

    The Pool Had Spare Servers. The Session Could Not Move: RFC 2391

    A service address can look like a place while concealing a choice. In RFC 2391, that address stood in front of a pool. A Load Sharing Network Address Translator chose one server when a new session arrived, rewrote the packets and kept both directions passing through itself. The pool might still contain healthy machines after the chosen server failed. That did not make the existing session portable. Selection happened once; the resulting binding governed every later packet until the session ended.

  2. Michuki Mwangi in an AI-generated portrait with Internet exchange infrastructure in the background.

    History

    Michuki Mwangi and the Missing Denominator in Africa’s 80 Percent Goal

    The phrase “80 percent” travelled through Africa’s peering debate as a continental aspiration, a content provider’s local-serving ratio and even a shorthand for the human work of building an exchange. Michuki Mwangi helped make the vision legible and practical; the record becomes less clear when those unlike numbers are treated as one score.

  3. A structured packet ribbon splits into fragments, reassembles, and becomes a matching calculation view whose mutable field positions are blank before two views align at an abstract comparison aperture.

    History

    The Authenticated View Was Not the Wire Image

    RFC 2402 did not ask sender and receiver to authenticate every IP-header bit exactly as it appeared in transit. They first prepared the same calculable view: protect what could remain stable, predict what would arrive deterministically, and replace unpredictable mutable contents with zero without erasing their place in the packet.

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

The Cost Beyond Cognex’s $500M Deal

A Satellite Route Is Not a Delivery Receipt

Why a Reset Printer Can Lose Its Name

Your Ebook Note Moved to the Wrong Paragraph

Same Pixels, Missing Proof

What Did “Human Approved” Mean?

One Secure Part. Is the Network Safe?

Can Quantum Randomness Make a Secure Key?

What’s Inside AI’s $2.67T Forecast?

$11.9B for Hugging Face. Will It Stay Open?

Why Revoke Can Leave You Logged In

When a Website Lock Escapes

Three Links Claimed. Two Visible.

Valid Signature, Wrong Person?

Published Doesn’t Mean Certified

Niels ten Oever in an AI editorial portrait against a softly abstract communications-network background.

Governance

Niels ten Oever and the review that followed a protocol off the page

RFC 9620's update to a human-rights review guide is notable for the evidence gap it admits: questions about design can surface risks, but understanding consequences also means listening to people, examining implementations and keeping the method open to revision.

Minimal square editorial illustration of one abstract registry-document seal connected by a single network line to a glowing circular root-server node carrying a stylized letter F, over a subtle world map in navy, slate and amber.

Market / Trends

AS210764: who can change the ISC-AGP1 record, and what the maintainer chain says about ISC stewardship

On 13 September 2021 the RIPE Database registered an autonomous system with the name ISC-AGP1, pointing straight at Internet Systems Consortium Inc. — the Delaware non-profit that has operated one of the Internet's thirteen root name servers since 1994. Four and a half years later, that registration has never been modified, the organisation behind it has been, and the routing world can see nothing at all. This report reads the record chain itself — maintainers, status, timestamps and neighbours — to answer a narrow question: who can modify the ISC-AGP1 record today, and does the public evidence show active stewardship or a dormant assignment?

One split scene: an orderly grid of blank registry index cards on the left, a dense panel of glowing route-monitor tiles on the right, separated only by empty space.

Market / Companies

Registered, Routed, and Named by a Description Line: What the Public Record Actually Proves About the Operator of AS17494

Every routing tracker on the internet can tell you what autonomous system 17494 is doing today. Almost none of them can tell you, with confidence, who is doing it. The public record for AS17494 is a live, continuously observed network sitting on top of a registration layer whose naming is a mess: a whois description line — 'Telecom Operator & Internet Service Provider as well' — that aggregators and BTW's own directory have adopted as an operator name, a registry organisation field that names the Bangladesh Telegraph & Telephone Board (BTTB), and a PeeringDB record, customer as-set and website attributions that point to Bangladesh Telecommunications Company Limited (BTCL). This article separates what the registration ledger says from what the operational ledger demonstrates, follows the interconnection mechanism that keeps the network reachable, and identifies the exact evidence that would resolve the identity collision and the discrepancies still embedded in the record.

Adrian Farrel before an abstract network where a luminous computed route fades before a darker device layer.

Market

Adrian Farrel and the Path That Exists Only on the Controller

A positive PCEP reply can put a clean route on an operator's screen before any router has accepted it. Adrian Farrel's PCE architecture matters because it lets us say exactly what has happened—and what has not.

Email message cards pass through a transparent moderation gate into a shared technical forum, with Nepal's Himalayan landscape behind.

Governance / NOGS

npNOG Calls Its Mailing List Open but Leaves Moderation Authority Unnamed

npNOG describes its mailing list as open, available to anyone and “sometimes moderated”. It also publishes seven content rules. What the reviewed pages do not publish is who moderates, what activates moderation, how a participant is notified or where a disputed decision goes.

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. John Day and the Seven-Layer Model That Could Not Order Deployment
  2. The Route Policy Can Change While Its SR-Algorithm Number Stays the Same
  3. A DNS Filtering Notice Is a Chain of Three Decisions, Not One Explanation
  4. A Registry-Lock Quorum Counts Approvals, Not Independent Authority
  5. The Address Was Borrowed. The Route Was Never Included: RFC 2008
  6. RIPEstat Wants Better AS Names—and a Map of Which ASNs Are One Entity
  7. RIPE Database mnt-ref Authorises an Organisation Reference, Not Corporate Control
  8. RIPE assignment-size Describes Aggregated IPv6 Assignments, Not Active Subscribers
  9. The State Table Was Also a Kill Switch: RFC 2012
  10. The Grant Was Automatic. The Boundary Was Not: RFC 1988
View Governance

Market

  1. Wasabi's Storage Bill Remembers More Than the Latest File
  2. Remco van Mook and the IPv4 Gateway That Has No IPv4 Neighbour
  3. Vint Cerf and the Deadline Behind the TCP/IP Cutover
  4. Jason Speers and the Hidden Handoffs Inside a Digital-First ISP
  5. ARTEMIS and the minute between a BGP alert and a safe response
  6. Backblaze's customer-held keys change who operates the second copy
  7. Nurani Nimpuno and the Accountability Layer Behind Number Governance
  8. Axtel's Second Bidder Has Preliminary Approval, Not a Higher Offer
  9. CleanSpark Has a 175 MW Lease, Not an 885 MW Delivered AI Campus
  10. Green Dot's US$42.3bn B2B Gross Dollar Volume Rose 22% as Purchase Volume Rose 1%
View Market

Membership

  1. The Roadmap Put Every Rule in Its Place. It Did Not Put Any Rule into Service
  2. Eric Brewer’s FirstGov: A Search Box, Not a Government Record
  3. Jon Crowcroft and the Internet That Became One Context Among Many
  4. The Server Listed Its Features. The Command Still Had to Succeed: RFC 2389
  5. The Third Hash Closed Quick Mode. It Did Not Confirm Both Kernels
  6. The Address Inside the Packet Was Invalid. The Frame Header Supplied the Source: RFC 2390
  7. The Payload Was Protected. The Envelope Was Still Visible
  8. Larry Peterson and the Global Slice That Never Owned a Node
  9. OpenAI holds its own routing identity. It has not yet bought its way out of the clouds
  10. The Graph Was Not the Test
View Membership

Number Resource Society

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

View Number Resource Society
  1. A Trust Anchor Rollover Needs an Acceptance Ledger
  2. An ASN Transfer Needs a Routing-Identity Handover Ledger
  3. A ROA Change Needs an Authorization-and-Withdrawal Ledger
  4. A RIR Representation Mandate Needs a Scope-and-Revocation Ledger
  5. A Member Logo Is Not a Live Power of Attorney
  6. A Country Field Is Not an RIR Mandate
  7. An Unanswered Profile Needs a Reply-State Ledger
  8. The FAQ Answer Needs a Version Date
  9. Bayan Telecommunications, AS6648 and the Boundary Between Network Records and Control
  10. When One Corporate Group Casts Twenty Registry Votes

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

Sylvia Ratnasamy and the Map That Was Never Geography

CAN drew a map in order to avoid keeping one central index. Its coordinates did not mark countries, cables or even nearby machines. They marked a temporary division of work: hash a key to a point, then ask whichever node currently holds the enclosing zone. Sylvia Ratnasamy and her co-authors made that abstraction beautifully spare. Its discipline lies in refusing to read more into the answer than the mechanism can know.

AI editorial portrait of Sylvia Ratnasamy beside a non-geographic CAN coordinate space divided into changing zones, with a highlighted key point and local handoff.

Sylvia Ratnasamy and the Map That Was Never Geography

CAN drew a map in order to avoid keeping one central index. Its coordinates did not mark countries, cables or even nearby machines. They marked a temporary division of work: hash a key to a point, then ask whichever node currently holds the enclosing zone. Sylvia Ratnasamy and her co-authors made that abstraction beautifully spare. Its discipline lies in refusing to read more into the answer than the mechanism can know.

  1. The Compressor Forgot on Purpose: RFC 2395 and the Datagram Boundary
  2. The Exchange Was Authenticated. The Shared Secret Was Still “Uncomputed”
  3. The DOI Named the Vocabulary. The Host Still Made the Decision
Open History Session

Leadership Alliance

The URL That Carried Its Own Cargo

RFC 2397 made a small but consequential move: it put the representation inside the address. The result was not merely a convenient encoding trick. It changed where retrieval ended, where interpretation began, and which component actually controlled the outcome.

A folded brass address ribbon becomes a glass capsule carrying a small payload into a local parsing and decoding instrument.

The URL That Carried Its Own Cargo

RFC 2397 made a small but consequential move: it put the representation inside the address. The result was not merely a convenient encoding trick. It changed where retrieval ended, where interpretation began, and which component actually controlled the outcome.

  1. Jitendra Padhye and the Throughput Equation That Was Never Capacity
  2. Frank Kelly and the Fairness That No Single Flow Could Prove
  3. The Policy Was Not the Packet
Open Alliance Session