Skip to main content

Lead Report / Leaders

Roque Gagliano in a head-and-shoulders portrait against a softly blurred network-engineering background.
RFC 6916 treats a change in RPKI cryptography as a multi-year migration across certificate authorities, repositories and relying parties. Co-authored by Roque Gagliano, the 2013 Best Current Practice makes readiness dates part of the trust mechanism—and leaves emergency transition outside its scope.

Roque Gagliano’s RPKI Plan Put a Clock Inside the Trust Chain

RFC 6916 treats a change in RPKI cryptography as a multi-year migration across certificate authorities, repositories and relying parties. Co-authored by Roque Gagliano, the 2013 Best Current Practice makes readiness dates part of the trust mechanism—and leaves emergency transition outside its scope.

  1. Editorial illustration of an unbranded network router with an amber cable looping back toward the device against a restrained blue network-path backdrop.

    The Gateway That Points Back: A DHCP Draft Adds a Legacy-Client Escape Hatch

    Version 03 of an individual Internet-Draft adds a conditional DHCPv4 Router Option for clients that require one: the host's own address or 127.0.0.1. The author says this should keep non-local IPv4 traffic on the host, but no published test yet shows how operating systems handle the new values.

  2. Концептуальная иллюстрация общественного телецентра в Тимбукту конца 1990-х: компьютеры, телефон, факс и местное собрание.

    Who Could Set the Price, and Who Could Keep the Centre Running? Timbuktu’s Community Telecentre, 1997–2002

    Timbuktu’s multipurpose community telecentre made network access useful through a local institution: people could telephone, send a fax, learn computing, print documents and, sometimes, reach the Internet. Its history also shows why calling a facility “community-owned” did not settle who controlled its money, maintenance or daily decisions.

  3. Концептуальная иллюстрация университетского исследователя, который в Суве обменивается почтой через компьютер и модем начала 1990-х.

    Fiji's Mail Link Ran Before Its Internet Route, 1992–94

    At the University of the South Pacific, email already crossed the Pacific through a dial-up relay in 1992. A full Internet connection came later in the record, and even its date depends on which contemporary or retrospective account is used.

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

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?

Spain’s 400 Prefix: Does It Make a Call Trustworthy?

The Fibre Crew Is Ready. Can It Actually Dig?

Four Operators, One Shared Mast. Who’s Responsible?

Can Both Labs Read the Same Digital Evidence?

Who Keeps Your Old Linux Device Updated?

Why Your Internet’s Return Trip Can Have a Different Size Limit

A Cell Tower in the Sky? The AI Control Challenge

How Did People Search IMDb Before It Had a Website?

Before Emoji: Why We Started Typing :-)

Who Could Step In If an Internet Registry Stops Working?

One Scam Call. How Many Networks?

Aventa’s Irish deal puts cable execution to the test

Market / Trends

Aventa’s Irish deal puts cable execution to the test

The offshore engineering group says its acquisition of Irish Sea Contractors adds nearshore installation and repair work. The strategic case is plausible, but the public record contains no price, backlog or measured evidence that the combination will lower project cost or repair time.

A minimal diagram on deep navy in two separated bands. Below, four solid brushed-metal rectangular blocks stand on one baseline as an ascending staircase, each taller and wider than the one to its left, each with a small blue indicator bar near its top edge and the tallest block brightest. Above, after a wide empty strip of dark navy, a single thin white line rises and falls across a faintly ruled timeline. Nothing connects the curve to any block.

Market / Companies

SwissIX prices every port step and publishes no port's load

Between 22:41 and 22:42 UTC on 18 October 2026, four pages on the SwissIX website were captured and read: the homepage, the traffic statistics page, the participants page and the peering page. Together they hold a complete monthly price menu for port capacity and a set of four aggregate traffic graphs. They do not hold the number that connects the two — the load on any particular port — and that gap, rather than any traffic figure, is the subject of this report. Every figure below is attributed to the page it came from and dated to that retrieval window.

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.

A marked amber control capsule crosses a transparent point-to-point bridge while an unresolved loop glows in the larger spanning-tree lattice beyond it.

Governance

BCP Marked the Control Frame. It Had Not Proved the Spanning Tree Safe: RFC 3518

One bit could tell a PPP implementation to treat a frame as bridge-control traffic. That was valuable. It was not a certificate that the bridged network beyond the link had reached a safe state.

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 Route Stopped Flapping. Its Penalty Had Not: RFC 2439
  2. RFC 9707: Being Connected Is Not Access—and a Workshop Report Is Not a Mandate
  3. The Recognition Gate: What a Draft RIR Governance Document Actually Hands Out
  4. Craig Partridge and the Gigabit That Did Not Need a New Internet
  5. WebAuthn’s Remote Client Can Validate the RP ID. The Local Permission Cannot Prove It Did
  6. RFC 9797: A Randomized MAC Address Can Reduce Linkability Without Becoming Device Identity
  7. The Key Was Generated in Two Rooms: DNSSEC’s First Root KSK Ceremony, 2010
  8. APNIC budgets 7.5% more fee income as net membership growth slows
  9. NULL Was a Negotiated Choice. The Packet Did Not Advertise That Choice
  10. The Switch Could Not Decrement TTL. The Ingress Paid the Hop Count Up Front: RFC 3034
View Governance

Market

  1. Terry Manderson and the Reverse DNS Split That Needed Operators
  2. FiberCop’s fibre gains still need to earn their way into cash
  3. BT bought continuity before clearance; the costs are still being counted
  4. Paul Vixie and DNS RRL: A Response Limit, Not an Identity Test
  5. Arctic Way Adds a Cable. Space Norway Still Has to Prove the Switch
  6. Cloudflare R2’s zero-egress price is not a zero-cost exit
  7. Japan’s virtual hyperscaler still has to become a service
  8. PowerCompute’s 11 MW contract firms only 300 kW at peak
  9. Nick McKeown and the Barrier Reply That Never Saw a Packet
  10. GTPL Hathway's revenue grew 19%, but Q2 EBITDA barely moved
View Market

Membership

  1. One Path, Four Algebras, and One Contagious Unknown: RFC 2215
  2. RFC 9019: A Signed Firmware Manifest Is Not Installation Authority
  3. RFC 9810: The Certificate Was Granted, but Not as Requested
  4. The Coalition Clause: What the Empowered Community's June–July 2026 Instruments Certified — and Refused
  5. The New Reverse Tree Existed Before the Old One Disappeared: RFC 3152
  6. Why .YU Stayed in the DNS Root Until 2010
  7. The Network Agreed the Root Was Down. It Did Not Prove a Crash: RFC 9866
  8. The First Ping Was Only One Route: Mauritius’s Internet, 1993–96
  9. IDCF’s outage put the recovery control plane in view
  10. The IPv6 Prefix Changed. The Identifier Stayed: RFC 3041
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

Tunisia’s .tn Domain Went to a Research Institute Before ATI, 1991–96

The .tn namespace entered the global DNS through a research institute in 1991; five years later, its stewardship moved to a new national Internet agency as Tunisia’s backbone operations were being reorganized. These were linked institutional changes, but domain delegation, international connectivity and public access remained separate systems.

Tunisia’s .tn Domain Went to a Research Institute Before ATI, 1991–96

The .tn namespace entered the global DNS through a research institute in 1991; five years later, its stewardship moved to a new national Internet agency as Tunisia’s backbone operations were being reorganized. These were linked institutional changes, but domain delegation, international connectivity and public access remained separate systems.

  1. The Exchange Was Settlement-Free. The Connection Was Not: CIX, 1991
  2. Tajikistan’s Email Network Crossed Regions Before Direct Internet Access, 1995–97
  3. A Legitimate Packet Can Still Fail the Filter: RFC 3704
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. Two Landing Stations, One Operator: What Bangladesh's Submarine Capacity Figures Actually Establish
  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 Alliance Session