Skip to main content

Lead Report / History

One source packet reaches three filters that test different views of the return route
A packet can carry a valid source address and still be dropped at a provider boundary. The reason may not be the address at all: it may be the route the receiving router believes should have brought it there.

A Legitimate Packet Can Still Fail the Filter: RFC 3704

A packet can carry a valid source address and still be dropped at a provider boundary. The reason may not be the address at all: it may be the route the receiving router believes should have brought it there.

  1. Unordered record capsules enter a sorter that builds authority tiers, selects one lane and blocks movement into lower tiers.

    The First NAPTR in the Packet Was Not the First Rule: RFC 3403

    DNS could carry a rule program without carrying its execution order in the order of arrival. RFC 3403 made the client reconstruct authority from the records themselves: `ORDER` came first, and only then could preference or service capability choose a path.

  2. Один идентификатор IPv6-интерфейса повторяется при смене префиксов, а временные адреса источника для исходящих соединений меняются.

    The IPv6 Prefix Changed. The Identifier Stayed: RFC 3041

    In 2001, IPv6 offered a way for a device to build an address without asking a DHCP server. But changing networks did not necessarily change the part of the address that could follow the same interface. RFC 3041 proposed temporary addresses to make that link harder to draw.

  3. A short unlabeled name enters a DHCP suffix selector, becomes one of several complete name paths, and reaches a valid wax-sealed DNS answer on the wrong branch.

    The Answer Was Signed. DHCP Had Chosen the Name That Was Asked: RFC 3397

    A resolver can verify every cryptographic fact in a DNS answer and still connect to the wrong administrative domain. RFC 3397 exposed the earlier decision that made this possible: before DNS could answer, DHCP could help decide which name would be asked.

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

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 Network Was Fine. The App Still Failed.

More Investment, Later Delivery

Approved—but Not Under Construction

In Orbit, But Not Live Yet

“Ringing” Doesn’t Mean Their Phone Rang

885 MW Planned—Only 175 MW Leased

$42.253B Loaded—Purchases Grew 1.3%

One ISP Brand, Several Operators

Your Key Can Block Native Replication

One File, Multiple Storage Charges

Zero Egress Isn’t a Free Exit

150ms Faster—But No Backup

Signed Update, Incompatible Device

A Valid Number Doesn’t Prove the Caller

Two Safe Budgets, One Overspend

Three separated packet chambers feed differently sized fragments with one shared symbol into a logical rail that reassembles one continuous option.

Governance

The Packet’s Fields Were Out of Order. The Option Still Had to Become One Object: RFC 3396

A DHCP option could be cut anywhere, placed in three separate fields and encountered in an order unlike the packet’s physical layout. RFC 3396 made one rule decisive: the pieces had no meaning until a decoder put them back into one object.

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.

An unbranded data-centre construction hall and substation are separate from an open tract and inactive modular mining containers at blue hour.

Market / Trends

CleanSpark Has a 175 MW Lease, Not an 885 MW Delivered AI Campus

CleanSpark’s June 2026 quarterly filing contains three adjacent but materially different facts. On 10 July it signed a 20-year triple-net infrastructure lease for 175 MW of critical IT load at Sandersville, Georgia. The same counterparty also signed an LOI and exclusivity arrangement over a Texas portfolio of 718 acres with up to 885 MW of secured and planned power capacity. And CleanSpark intends to move the Sandersville site from bitcoin mining to an AI campus, with full mining decommissioning expected during fiscal 2028. The first is a definitive lease. The second is not described as one. The third is a future operating transition. Combining them would replace an execution ledger with a headline number.

Conceptual diagram of Cloudflare R2 object storage, an outward file-transfer route and a separate workspace for inspecting replacement application components.

Market / Companies

Cloudflare R2’s zero-egress price is not a zero-cost exit

Cloudflare lists no charge for outbound transfer from R2 and documents a way to copy objects out. The remaining economic question is what customers must spend—and successfully operate—to turn that export into a working replacement.

Two evidence paths, prior participation and equivalent operational proof, converge on the same event-host readiness standard.

Governance / NOGS

AfNOG’s Host Call Strongly Prefers Prior Workshop Familiarity Without Publishing an Equivalent Path

AfNOG’s dated host call strongly prefers hosts familiar with its workshop requirements through prior participation. The reviewed page does not publish an equivalent proof route for a first-time host.

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. The Replicas Converged. The Losing Value Still Had to Be Preserved: RFC 3384
  2. A Link Could Name a Record Without Naming It: RFC 3368
  3. The Route Policy Can Change While Its SR-Algorithm Number Stays the Same
  4. A DNS Filtering Notice Is a Chain of Three Decisions, Not One Explanation
  5. A Registry-Lock Quorum Counts Approvals, Not Independent Authority
  6. The Address Was Borrowed. The Route Was Never Included: RFC 2008
  7. The State Table Was Also a Kill Switch: RFC 2012
  8. The Grant Was Automatic. The Boundary Was Not: RFC 1988
  9. A Join Priority Is Not an Enrollment Decision Record
  10. A Holder-Designated RDAP Referral Extends Discovery, Not Registry Authority
View Governance

Market

  1. Remco van Mook and the IPv4 Gateway That Has No IPv4 Neighbour
  2. Vint Cerf and the Deadline Behind the TCP/IP Cutover
  3. Jason Speers and the Hidden Handoffs Inside a Digital-First ISP
  4. Nurani Nimpuno and the Accountability Layer Behind Number Governance
  5. Seyed Pouria Mousavizadeh Tehrani and the State Hidden Before IPv6’s First Reply
  6. Daniel Fett and the Issuer Field That Named the Server, Not the Token
  7. Nick McKeown and the Barrier Reply That Never Saw a Packet
  8. Lattice’s US$925m AMI draw is not its US$1bn cash purchase price
  9. William B. Norton and the Metric That Could Not Price a Peer
  10. Kodiak’s 76 MW deal names the load, not its credit
View Market

Membership

  1. The Best Service Was Only Best Under the Sort Keys: RFC 3421
  2. The Counter Said GET. The Probe Had Remembered a Reply and Chosen One Verb: RFC 3395
  3. The Collection Kept the Members Together. It Did Not Preserve Their Order: RFC 3382
  4. The Image Arrived Beside Its Reference. The Producer Still Could Not See the Reader: RFC 3391
  5. A Persistent Name Needed a Succession Plan: RFC 3406
  6. The Ciphertext Grew by One Register. That Register Decided Whether the Key Existed: RFC 3394
  7. The Checksum Was 32 Bits. The Error Model Decided What That Meant: RFC 3385
  8. 3GPP2’s Meetings Were Open. Its Mailing Lists Were Not: RFC 3131
  9. The Endpoint Said It Could. It Did Not Say the Session Would: RFC 3407
  10. The Same URI Could Resolve to a Location, a Resource, or a Description: RFC 3404
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 Member Logo Is Not a Live Power of Attorney
  4. A Country Field Is Not an RIR Mandate
  5. A ROA Change Needs an Authorization-and-Withdrawal Ledger
  6. An Unanswered Profile Needs a Reply-State Ledger
  7. The FAQ Answer Needs a Version Date
  8. Bayan Telecommunications, AS6648 and the Boundary Between Network Records and Control
  9. A RIR Representation Mandate Needs a Scope-and-Revocation Ledger
  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

Every Rule Rewrote the Key. None Could Rewrite the Original String: RFC 3402

A discovery system can travel through several authorities without letting any of them replace the thing being discovered. RFC 3402 made that distinction executable: rules changed the next lookup key, while the original application string remained beyond their reach.

One immutable central string passes beneath several rule stations while only a chain of lookup keys changes above it, ending at a separate terminal result.

Every Rule Rewrote the Key. None Could Rewrite the Original String: RFC 3402

A discovery system can travel through several authorities without letting any of them replace the thing being discovered. RFC 3402 made that distinction executable: rules changed the next lookup key, while the original application string remained beyond their reach.

  1. The Lease Carried a Route, Not Just an Address: RFC 3442
  2. The Lower Layer Recovered First. The Upper Layer Had to Wait: RFC 3386
  3. The Queue Could Differentiate Packets. The Operator Still Had Not Defined a Service: RFC 3387
Open History Session

Leadership Alliance

The Missing Byte Became a Link-Layer Promise: RFC 3408

The smallest header in a radio voice stream was only one octet. Removing it saved more than one octet—and demanded that another layer swear it could recover what was no longer present.

A tiny absent header slot is bridged by separate cyan rails for packet identity, loss indication and sequence evidence before an amber gate permits header-free radio packets.

The Missing Byte Became a Link-Layer Promise: RFC 3408

The smallest header in a radio voice stream was only one octet. Removing it saved more than one octet—and demanded that another layer swear it could recover what was no longer present.

  1. The Test Numbers Were Shared. The Experiments Were Not: RFC 3692
  2. One Missing Label Canceled Every Group: RFC 3388
  3. The Address Was Only Bytes Until Its Transport Domain Arrived: RFC 3419
Open Alliance Session