Skip to main content

Lead Report / Story

An abstract directory tile points to a source-specific IRR database, followed by a separate validation stage.
PeeringDB’s source-qualified AS-SET names can remove ambiguity from discovery. The current record for AFRINIC’s ASN 33764 shows why a source label should still be read as provenance, not certification.

A Prefix Can Locate an IRR Set. It Cannot Validate It

PeeringDB’s source-qualified AS-SET names can remove ambiguity from discovery. The current record for AFRINIC’s ASN 33764 shows why a source label should still be read as provenance, not certification.

  1. Two BOOTP client paths pass through a relay to stable server groups on a period network plan; a crossed-out round-robin arrow marks the rule.

    Same Client, Same Server Set: RFC 1542’s BOOTP Relay Rule

    When one small bootstrap request has to cross a subnet boundary, the relay becomes part of the client’s conversation with a server. RFC 1542 made a quiet but consequential choice: distribute clients across servers if useful, but keep each client’s sequence of requests attached to the same destination or destination set.

  2. AI editorial portrait of Milton L. Mueller in a scholar's office with bookshelves and a subtle network diagram.

    Milton L. Mueller Helped Make the IPv4 Address Market Measurable

    A market can be real before anyone can count it well. Milton L. Mueller’s work on IPv4 transfers joined registry records, court filings and sampled routing data to make a disputed market visible. The method clarified what could be observed—and why a transfer count still could not prove a network’s need, price or continuity.

  3. Two desk calendars show different days circled beside a blank proxy form and envelope in an empty meeting room.

    RIPE NCC’s proxy deadline appears as 4 October and 14 October

    One RIPE NCC notice lists 4 October as the proxy-vote deadline; the General Meeting and proxy pages list 14 October. The Articles’ two-week rule points to 14 October for a meeting that begins on 28 October, but the published mismatch remains unexplained.

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

MGM’s Cyberattack Didn’t Stay Online

Four Green Lights. Why Is the 3D Person Missing?

Can a Secure Session Outlive Trust?

Who Actually Carries the Call?

The $120M Number That Isn’t Cash

The Calendar Says You’re the Owner—But Can You Edit It?

76% SaaS Doesn’t Mean 76% Growth

Spectrum Reached Orbit. Can Isar Keep Delivering?

BSNL Moves 6 PB a Day. Is That Good 4G?

Red Sea Utilities Are Operating—Now Measure 25 Years

Inside iFX EXPO Asia 2026: Trading and Fintech Converge in Hong Kong

Why This Backup Route Had to Stay Hidden

Tideo Closed. AS210972 Went Quiet. Why Is the Contact Record Still There?

Mistral’s 1GW AI Plan Has Backers—But Where Are the Orders?

AS142207’s Records Changed After Its Public Routes Disappeared

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.

AI editorial illustration of a cyan root signal branching through a low-power mesh, where successive admission points shift toward amber and red while a separate layered evidence trail preserves the hidden path.

Governance

A Join Priority Is Not an Enrollment Decision Record

A proposed RPL option lets a low-power mesh distribute how much capacity it has for new devices. The number can rise as it moves away from the root, and its maximum value can switch Join Proxy service off. That is efficient coordination, but a Pledge seeing a high priority cannot tell whether root policy, approximate network size, a firmware gap, a local resource shortage or a hostile control-plane message closed the door. Admission governance needs a separate causal receipt.

Conceptual illustration contrasting a suspended primary cloud operations room, a separated backup vault, and an alternate compute hall.

Market / Companies

IDCF’s outage put the recovery control plane in view

The ransomware incident at IDC Frontier did not prove that IDCF Cloud Backup failed. It did expose a more useful market question: when the ordinary cloud console is stopped, who can reach a copy, authorize its use and supply somewhere to run the restored service?

Conceptual illustration of the completed BT–TalkTalk operating transfer: connected UK homes continue beside a separate desk representing pending competition and public-interest review.

Market / Trends

BT bought continuity before clearance; the costs are still being counted

BT has taken TalkTalk’s consumer business and PlatformX out of administration to keep 2.5 million retail and wholesale connections operating. That closes one clock—the risk of an abrupt service break—while opening another: whether a completed rescue acquisition should remain in place after competition and public-interest review.

Three conference microphones stand apart from an organised production desk in a quiet Pokhara meeting room.

Governance / NOGS

Who opens the room? What npNOG-10's welcome order can—and cannot—prove

The first twenty minutes of a conference can reveal institutional relationships. They cannot, without supporting records, tell us who held the decisive authority.

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. WebAuthn’s Remote Client Can Validate the RP ID. The Local Permission Cannot Prove It Did
  2. A Completed Gateway Action Is Not a Physical Outcome
  3. RFC 9797: A Randomized MAC Address Can Reduce Linkability Without Becoming Device Identity
  4. A Signed Epoch Marker Is Not a Universal Clock
  5. A Token Status Bit Is Not a Revocation Timeline
  6. NULL Was a Negotiated Choice. The Packet Did Not Advertise That Choice
  7. The Switch Could Not Decrement TTL. The Ingress Paid the Hop Count Up Front: RFC 3034
  8. Two Duplicate ACKs Could Send New Data, but Not Enlarge the Window: RFC 3042
  9. The Best Route Was Not a Stable Answer: RFC 3345
  10. The Sender Estimated the Pipe. It Did Not Count the Packets Still in the Network: RFC 3517
View Governance

Market

  1. FiberCop’s fibre gains still need to earn their way into cash
  2. Paul Vixie and DNS RRL: A Response Limit, Not an Identity Test
  3. Cloudflare R2’s zero-egress price is not a zero-cost exit
  4. Japan’s virtual hyperscaler still has to become a service
  5. PowerCompute’s 11 MW contract firms only 300 kW at peak
  6. Nick McKeown and the Barrier Reply That Never Saw a Packet
  7. The 2.1-gigawatt promise sits outside Black Hills’ wires
  8. William B. Norton and the Metric That Could Not Price a Peer
  9. QuantumScape’s PowerBlock makes a data-centre pitch before it names a buyer
  10. Kodiak’s 76 MW deal names the load, not its credit
View Market

Membership

  1. RFC 9019: A Signed Firmware Manifest Is Not Installation Authority
  2. RFC 9810: The Certificate Was Granted, but Not as Requested
  3. The Coalition Clause: What the Empowered Community's June–July 2026 Instruments Certified — and Refused
  4. Immutable to the Client Is Not Immutable in Time
  5. The New Reverse Tree Existed Before the Old One Disappeared: RFC 3152
  6. The Network Agreed the Root Was Down. It Did Not Prove a Crash: RFC 9866
  7. The IPv6 Prefix Changed. The Identifier Stayed: RFC 3041
  8. The Route Stopped Flapping. Its Penalty Had Not: RFC 2439
  9. RFC 9707: Being Connected Is Not Access—and a Workshop Report Is Not a Mandate
  10. Craig Partridge and the Gigabit That Did Not Need a New Internet
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. A Member Logo Is Not a Live Power of Attorney
  3. A Country Field Is Not an RIR Mandate
  4. An ASN Transfer Needs a Routing-Identity Handover Ledger
  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. A RIR Representation Mandate Needs a Scope-and-Revocation Ledger
  9. When One Corporate Group Casts Twenty Registry Votes
  10. Digital Identity Requirements at the Registry Gate

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

RARP Found the Address, Not the Configuration: RFC 903

A diskless workstation could wake knowing the number stamped on its network interface but not the Internet address needed to use IP. In 1984, RFC 903 gave it a narrow question for the local link: which protocol address had a server mapped to this hardware address?

A diskless workstation asks a local server over a short Ethernet segment for its mapped protocol address; other boot settings sit outside the reply.

RARP Found the Address, Not the Configuration: RFC 903

A diskless workstation could wake knowing the number stamped on its network interface but not the Internet address needed to use IP. In 1984, RFC 903 gave it a narrow question for the local link: which protocol address had a server mapped to this hardware address?

  1. A Legitimate Packet Can Still Fail the Filter: RFC 3704
  2. BCP Marked the Control Frame. It Had Not Proved the Spanning Tree Safe: RFC 3518
  3. Equal Cost Did Not Make the Paths Interchangeable: RFC 2991 and the Price of Stable Multipath
Open History Session

Leadership Alliance

Remco van Mook and the IPv4 Gateway That Has No IPv4 Neighbour

An IPv4 default gateway normally looks like an address that a host can find with ARP. Remco van Mook's current IETF proposal turns that expectation inside out: `192.0.0.11` is not a neighbour to discover, but an instruction to reuse a neighbour that IPv6 has already discovered. The economy is real. So is the new dependency chain.

Remco van Mook before converging blue and amber light paths, an abstract editorial portrait of IPv4 forwarding that borrows an IPv6 next hop.

Remco van Mook and the IPv4 Gateway That Has No IPv4 Neighbour

An IPv4 default gateway normally looks like an address that a host can find with ARP. Remco van Mook's current IETF proposal turns that expectation inside out: `192.0.0.11` is not a neighbour to discover, but an instruction to reuse a neighbour that IPv6 has already discovered. The economy is real. So is the new dependency chain.

  1. A Signed Transaction Token Does Not Attest Every Claim
  2. The First NAPTR in the Packet Was Not the First Rule: RFC 3403
  3. One Path, Four Algebras, and One Contagious Unknown: RFC 2215
Open Alliance Session