BTW.Media
Daily editionStrategic Internet Intelligence
Sign InRegister

Live Wire

View all briefings
Two controllers used the same device ID. The combined inventory needed a new namespace|TLS Trust Labels Get Smaller; the Trust Decision Does Not Move|Inseego closes Nokia FWA deal; $10m support is no interoperability guarantee|RIPE NCC is changing the RPKI key. The harder question is what it can touch|A Lab Benchmark Is Not a Live-Network Verdict|ICANN Counted 1,616 Applications. It Had Not Added 1,616 TLDs.|Singtel’s token service sells a gateway; savings remain unpriced|Celestica’s 11.1m-share offering shifts the AI test to cash returns|DFINFRA's second tier: the live routing that a frozen registry cannot see|The Reflector Returned Eight Packets. It Still Had Not Measured the Application.|NovaCloud-Hosting's registry administration is split across three maintainers: who actually runs the operator's record?|Three carriers agree a satellite JV; existing deals stay separate

Lead Report / History

A packet reaches a metal boundary gate that removes five amber counter discs before five glass switching chambers exchange geometric link tokens without changing the remaining stack.
A Frame Relay switch could replace a DLCI at line rate yet lack the operation that routers performed on every packet: subtract one from time to live. RFC 3034 preserved MPLS loop and scope accounting by charging a propagated segment length at the boundary. The control plane supplied the number; the ingress performed the subtraction; neither fact alone proved the path a packet actually took.

The Switch Could Not Decrement TTL. The Ingress Paid the Hop Count Up Front: RFC 3034

A Frame Relay switch could replace a DLCI at line rate yet lack the operation that routers performed on every packet: subtract one from time to live. RFC 3034 preserved MPLS loop and scope accounting by charging a propagated segment length at the boundary. The control plane supplied the number; the ingress performed the subtraction; neither fact alone proved the path a packet actually took.

Read Full AnalysisHistory Intelligence
  1. A packet stream has a gap; two blue acknowledgment pulses return while the sender-side window stays fixed.

    History

    Two Duplicate ACKs Could Send New Data, but Not Enlarge the Window: RFC 3042

    A TCP sender with a three-segment congestion window loses one segment. The receiver can return only two duplicate acknowledgments for the later data, one short of the threshold that would trigger Fast Retransmit. In 2001, RFC 3042 proposed a narrow way to keep the feedback clock moving: send new data on those first two ACKs, while leaving the congestion window unchanged.

  2. A branching document tree passes through a transform aperture; only a compact cyan-gold fragment reaches the signing chamber while a fuller view remains outside.

    History

    The Signature Verified the Transform. It Did Not Verify the Document You Saw: RFC 3075

    In XML Signature, a green cryptographic result belonged to a deliberately constructed object: referenced data after its declared transforms, represented by digests inside canonicalized `SignedInfo`. RFC 3075 made that receipt precise. It also warned that the source document, the screen shown to a person, the key’s institutional meaning and the application’s decision could all be different things.

  3. Copper telephone trunk wiring feeds a rack-mounted media gateway in the foreground; a small amber signal pulse appears beside the gateway, with a distant controller workstation linked by a dotted blue packet path.

    History

    The Gateway Owned the Milliseconds. The Call Agent Still Owned the Call: RFC 3064

    When circuit telephony met packet control, distance became a design constraint. RFC 3064 put reactions measured in tens of milliseconds beside the wire, inside the media gateway. It did not surrender the larger decision: the Call Agent still decided what the call meant, and a released trunk was not yet a deleted network connection.

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

A shared policy schema branches through a decision point into two devices with distinct local interpretation paths.

Governance

The Model Could Describe the Rule. It Left the Result to Devices: RFC 3060

RFC 3060 gave policy systems a shared vocabulary of groups, rules, conditions and actions. It did not give every router one shared interpreter. The standard could describe when a rule applied and even mark an action order as mandatory or recommended, while leaving the algorithm that turned those attributes into a decision to an implementation. That gap was not hidden in the schema; the RFC called it out as a design boundary.

Simplified network topology of a small corporate autonomous system with two upstream transit connections and blank registry route-object cards

Market / Companies

The Small Autonomous System: FPT Software and What AS131402 Actually Does

A software-outsourcing company does not, on the face of it, need to run an autonomous system. Yet FPT Software Company limited holds AS131402 under Vietnam's VNNIC-administered APNIC block, announces nine IPv4 prefixes, and rides two national carriers for transit. Reading the routing and registry evidence side by side shows a small but genuinely operational network — and a useful case study in how number-resource footprints encode organisational relationships that company announcements never mention.

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.

Conceptual data cartridge with empty frames and blank paper traces of earlier generations; not actual Wasabi equipment.

Market / Trends

Wasabi's Storage Bill Remembers More Than the Latest File

Overwriting one object can leave several generations on the bill. A shorter minimum duration, a new invoice and a new price each change a different part of that history.

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. RIPE assignment-size Describes Aggregated IPv6 Assignments, Not Active Subscribers
  2. The State Table Was Also a Kill Switch: RFC 2012
  3. The Grant Was Automatic. The Boundary Was Not: RFC 1988
  4. A Join Priority Is Not an Enrollment Decision Record
  5. A Holder-Designated RDAP Referral Extends Discovery, Not Registry Authority
  6. Allison Mankin and the Name-Collision Sample That Could Not Prove Its Cause
  7. RIPE Atlas Says “Dissimilar” Probe Selection Is Complete. Its Public API Does Not Name the Selector
  8. Equal Cost Did Not Make the Paths Interchangeable: RFC 2991 and the Price of Stable Multipath
  9. APNIC Whois mnt-lower Marks Maintainer Hierarchy, Not Routing Hierarchy
  10. A Signed Transaction Token Does Not Attest Every Claim
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. ARTEMIS and the minute between a BGP alert and a safe response
  5. Backblaze's customer-held keys change who operates the second copy
  6. Nurani Nimpuno and the Accountability Layer Behind Number Governance
  7. Axtel's Second Bidder Has Preliminary Approval, Not a Higher Offer
  8. CleanSpark Has a 175 MW Lease, Not an 885 MW Delivered AI Campus
  9. Seyed Pouria Mousavizadeh Tehrani and the State Hidden Before IPv6’s First Reply
  10. Daniel Fett and the Issuer Field That Named the Server, Not the Token
View Market

Membership

  1. The Missing Extension Was Not an Empty Answer: RFC 3059
  2. The Root DSE Could Name Its Vendor. RFC 3045 Drew the Line at Capability Discovery.
  3. A Global Name, One Authoritative Resolver: The Promise and Limit of RFC 3043
  4. The Standard Recommended LDP. It Did Not Prove the Protocol Was Running: RFC 3037
  5. LDP Kept the Full-Length Prefix and Dropped the Host FEC
  6. The Identifier Named the Session. It Did Not Move It: RFC 3033
  7. The Route Policy Can Change While Its SR-Algorithm Number Stays the Same
  8. A DNS Filtering Notice Is a Chain of Three Decisions, Not One Explanation
  9. A Registry-Lock Quorum Counts Approvals, Not Independent Authority
  10. The Address Was Borrowed. The Route Was Never Included: RFC 2008
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

The Tunnel Was Media-Independent. Its Circuit Was Not: RFC 3070

RFC 3070 made L2TP portable across a Frame Relay network, but portability did not make the bearer disappear. The tunnel still depended on a virtual circuit with its own endpoints, framing identifier, setup rules, packet-size limit and unresolved questions of service quality and security. The history matters because abstraction can move a dependency without eliminating it.

A luminous packet tunnel spans two network sites while a separate provisioned circuit runs through the ground below and branches into alternate paths.

The Tunnel Was Media-Independent. Its Circuit Was Not: RFC 3070

RFC 3070 made L2TP portable across a Frame Relay network, but portability did not make the bearer disappear. The tunnel still depended on a virtual circuit with its own endpoints, framing identifier, setup rules, packet-size limit and unresolved questions of service quality and security. The history matters because abstraction can move a dependency without eliminating it.

  1. The Label Was a Country Code. The Registry Could Still Be Generic: RFC 3071
  2. The Tag Named the Content. It Could Not Certify Understanding: RFC 3066
  3. The Hash Assigned the Server. It Did Not Prove the Server Was Ready: RFC 3074
Open History Session

Leadership Alliance

The ATM Label Changed at Every Switch. LDP Needed One Both Ends Could Share

An ATM circuit could keep carrying cells while the number printed in its VPI/VCI field changed at the next switch. LDP peers therefore needed more than the local label: they needed a shared identity for the virtual connection before they could bind it into MPLS.

An amber virtual circuit passes between two ATM switches while distinct local label tiles change at each hop.

The ATM Label Changed at Every Switch. LDP Needed One Both Ends Could Share

An ATM circuit could keep carrying cells while the number printed in its VPI/VCI field changed at the next switch. LDP peers therefore needed more than the local label: they needed a shared identity for the virtual connection before they could bind it into MPLS.

  1. Labels Waited for the Thread to Rewind: RFC 3063
  2. The Broker Ordered the Tunnel. Another Machine Had to Carry It: RFC 3053
  3. The Counter Detected the Lost Packet. It Could Not Decrypt the Next One: RFC 3078
Open Alliance Session