Skip to main content

Lead Report / Leaders

Adrian Farrel before an abstract network where a luminous computed route fades before a darker device layer.
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.

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.

  1. 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.

  2. Aerial view of a tropical South Asian coastline where a submarine fibre-optic cable comes ashore at a low concrete landing station with a fenced compound and equipment shelter, palm trees and a wide sandy beach, the black cable visible in the shallows and a cable-laying ship offshore.

    Two Landing Stations, One Operator: What Bangladesh's Submarine Capacity Figures Actually Establish

    Bangladesh's international bandwidth comes ashore at two beaches and, on the public record, through one company. In October 2026 that company put a number on its own position, and the number closes arithmetically in one rendering of the statement and not in the other. This is a reading of what the record establishes, layer by layer, and of what it leaves standing unverified.

  3. Conceptual illustration of a submarine-cable repair vessel and cable-handling equipment at sea.

    APNIC’s US$3bn cable-repair forecast leaves the funding model open

    An APNIC-hosted essay cites a 2040 estimate of US$3 billion to replace 15 submarine-cable repair vessels and add five more. The ITU’s evidence points to the financing question behind that total: who will commit the long-term revenue needed to build and maintain the ships?

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

Before Quantum Breaks Encryption, Can You Find It All?

The Right Price. The Right Tech. But Can You Qualify?

The Alarm Lights Up. Did the Call Arrive?

Free Learning Data—But Is the Next Link Covered?

he 5G Core Is Ready. Is Your Phone?

11 Megawatts—but at What Hours?

You Have a Backup. Can You Actually Reach It?

17 Sites. How Many Working Exits?

The Clock That Tripped a Mobile Network

Reserved Cloud Capacity. Wrong Recovery Location?

Fast AI. So Why Is Your Next Request Waiting?

AI Found a Better Broadband Deal. Who Said Yes?

AI Says “Spam.” Where’s the Evidence?

Canada Passed the Cyber Law. Has Every Part Started?

One Rural Tower Fails. How Many People Lose Signal?

Five network-element stations compose one path on separate rails: a persistent break, growing hop beads, narrowing teal bandwidth, accumulating amber latency, constrained packet-size plates and a black unknown that survives every later station.

Governance

One Path, Four Algebras, and One Contagious Unknown: RFC 2215

A network path can be described by many numbers, but those numbers do not obey one law. RFC 2215 made that distinction operational: a break propagates by logical OR, aware hops are counted, bandwidth and packet size are narrowed by minima, and latency accumulates. More importantly, an unknown contribution remains unknown downstream. A composed value is therefore a qualified path characterization—not a reservation, a measurement of delivered performance, or a receipt for an application result.

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?

Terry Manderson

Market

Terry Manderson and the Reverse DNS Split That Needed Operators

A reverse lookup can lose its path before it reaches the PTR record. A resolver must first find the servers for the reverse zone itself. In 2010, Terry Manderson and Joe Abley proposed dedicated server names for IPv4 and IPv6 reverse DNS. Their RFC made separate operation possible, then left the choice of operators to IANA. The distinction is the story: a namespace can create room for resilience, but it cannot prove that the deployed networks occupy different failure domains.

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. The Key Was Generated in Two Rooms: DNSSEC’s First Root KSK Ceremony, 2010
  2. NULL Was a Negotiated Choice. The Packet Did Not Advertise That Choice
  3. The Switch Could Not Decrement TTL. The Ingress Paid the Hop Count Up Front: RFC 3034
  4. Two Duplicate ACKs Could Send New Data, but Not Enlarge the Window: RFC 3042
  5. The Best Route Was Not a Stable Answer: RFC 3345
  6. The Sender Estimated the Pipe. It Did Not Count the Packets Still in the Network: RFC 3517
  7. The Labels Kept Forwarding on Borrowed Time: RFC 3478
  8. The Answer Was Signed. DHCP Had Chosen the Name That Was Asked: RFC 3397
  9. The RFC Was Missing. The DHCP Option Was Not.
  10. The Priority Label Named a Policy. It Did Not Choose the Treatment: RFC 3487
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. Arctic Way Adds a Cable. Space Norway Still Has to Prove the Switch
  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. GTPL Hathway's revenue grew 19%, but Q2 EBITDA barely moved
  8. INWIT’s reported buyout would purchase equity, not settle the tower contracts
  9. The 2.1-gigawatt promise sits outside Black Hills’ wires
  10. William B. Norton and the Metric That Could Not Price a Peer
View Market

Membership

  1. Why .YU Stayed in the DNS Root Until 2010
  2. The Network Agreed the Root Was Down. It Did Not Prove a Crash: RFC 9866
  3. The First Ping Was Only One Route: Mauritius’s Internet, 1993–96
  4. The IPv6 Prefix Changed. The Identifier Stayed: RFC 3041
  5. The Route Stopped Flapping. Its Penalty Had Not: RFC 2439
  6. RFC 9707: Being Connected Is Not Access—and a Workshop Report Is Not a Mandate
  7. The Recognition Gate: What a Draft RIR Governance Document Actually Hands Out
  8. Craig Partridge and the Gigabit That Did Not Need a New Internet
  9. WebAuthn’s Remote Client Can Validate the RP ID. The Local Permission Cannot Prove It Did
  10. RFC 9797: A Randomized MAC Address Can Reduce Linkability Without Becoming Device Identity
View Membership

Number Resource Society

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

View Number Resource Society
  1. IPv4 transfer logs jumped 39%; recipient breadth barely moved
  2. The Address Council Describes Its Own Job, and Every Duty Points Upward
  3. A Trust Anchor Rollover Needs an Acceptance Ledger
  4. A Member Logo Is Not a Live Power of Attorney
  5. A Country Field Is Not an RIR Mandate
  6. An ASN Transfer Needs a Routing-Identity Handover Ledger
  7. A ROA Change Needs an Authorization-and-Withdrawal Ledger
  8. An Unanswered Profile Needs a Reply-State Ledger
  9. The FAQ Answer Needs a Version Date
  10. A RIR Representation Mandate Needs a Scope-and-Revocation Ledger

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

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.

One source packet reaches three filters that test different views of the return route

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. BCP Marked the Control Frame. It Had Not Proved the Spanning Tree Safe: RFC 3518
  2. Equal Cost Did Not Make the Paths Interchangeable: RFC 2991 and the Price of Stable Multipath
  3. The First NAPTR in the Packet Was Not the First Rule: RFC 3403
Open History Session

Leadership Alliance

RFC 9019: A Signed Firmware Manifest Is Not Installation Authority

The release pipeline turns green when a firmware manifest verifies. The payload digest matches, the signer is known, and the sequence number is acceptable. Only then does the neglected question become visible: what was this signer actually allowed to change on this device, at this time? RFC 9019 makes authentication evidence indispensable, but it refuses to turn that evidence into unlimited installation authority.

AI editorial illustration of a firmware package passing through separate authenticity and role-permission gates before distinct installation, activation, observation and recovery stations.

RFC 9019: A Signed Firmware Manifest Is Not Installation Authority

The release pipeline turns green when a firmware manifest verifies. The payload digest matches, the signer is known, and the sequence number is acceptable. Only then does the neglected question become visible: what was this signer actually allowed to change on this device, at this time? RFC 9019 makes authentication evidence indispensable, but it refuses to turn that evidence into unlimited installation authority.

  1. RFC 9810: The Certificate Was Granted, but Not as Requested
  2. The Coalition Clause: What the Empowered Community's June–July 2026 Instruments Certified — and Refused
  3. The New Reverse Tree Existed Before the Old One Disappeared: RFC 3152
Open Alliance Session