Skip to main content

Lead Report / History

Editorial illustration for RFC 2991 showing three physically unequal equal-cost paths and a bounded subset of flows remapping after one path is withdrawn.
Two routes can tie in the routing table and still disagree about packet size, delay and what a probe can see. In 2000, RFC 2991 made the router’s choice among those paths a question of how much disruption a network was willing to accept.

Equal Cost Did Not Make the Paths Interchangeable: RFC 2991 and the Price of Stable Multipath

Two routes can tie in the routing table and still disagree about packet size, delay and what a probe can see. In 2000, RFC 2991 made the router’s choice among those paths a question of how much disruption a network was willing to accept.

  1. ترسل شبكة داخلية زرقاء الطلب عبر مبدّل سياسة إلى مخزون عناوين خارجي كهرماني، بينما يعيد مسار أبيض منفصل رمزاً من أربع خلايا.

    The Packet Came from One Subnet. The Address Was for Another: RFC 3011

    DHCP once treated a packet’s arrival path as a practical clue to the address pool it needed. RFC 3011 made that clue overridable—and forced operators to decide who was allowed to point beyond the local pool.

  2. Two unmarked blue data capsules travel on different timing paths while one amber acknowledgment ring returns to a sender surrounded by widening timer rings

    The ACK That Could Not Name the Copy: How Karn Stopped TCP Learning the Wrong RTT

    A TCP acknowledgment can be completely true and still answer the wrong question. After a timeout, the same bytes may have crossed the network twice. The returning ACK proves that the receiver advanced, but not which copy made it advance. Karn's algorithm made that missing label operational: do not teach the timer with evidence whose cause cannot be identified.

  3. ترتبط نهايتان مختلفتان للوسائط داخل إطار سماوي للبوابة، بينما تبقى إيصالات التحكم وعدسة التدقيق منفصلة عن المسار غير المؤكد نحو مكبر صوت بعيد.

    The Context Was Connected. The Call Was Not Proven: RFC 3015

    Megaco gave a decomposed media gateway a precise local model of who could hear or see whom. RFC 3015 also showed why a successful command, a visible Context and a returned statistic were not yet receipts for an end-to-end conversation.

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

You Clicked Revoke. Why Does Access Still Work?

NVIDIA Agreed to Buy Hugging Face. Will It Stay Open?

The Cost Beyond Cognex’s $500M Deal

A Satellite Route Is Not a Delivery Receipt

Why a Reset Printer Can Lose Its Name

Your Ebook Note Moved to the Wrong Paragraph

Same Pixels, Missing Proof

What Did “Human Approved” Mean?

One Secure Part. Is the Network Safe?

Can Quantum Randomness Make a Secure Key?

What’s Inside AI’s $2.67T Forecast?

$11.9B for Hugging Face. Will It Stay Open?

Why Revoke Can Leave You Logged In

When a Website Lock Escapes

Three Links Claimed. Two Visible.

A completed bank of blank capability tiles stands left of a glass boundary while one live message crosses separate security, proxy, receipt, decision and outcome chambers on the right.

Governance

The Checklist Graded Capabilities, Not Packets: RFC 2989

In November 2000, RFC 2989 assembled a formidable checklist for network-access AAA protocols. It asked whether a candidate could scale, fail over, protect objects, carry EAP, authorize, reconcile state and deliver accounting records. Then it inserted the sentence that kept the table honest: requiring a protocol to support confidentiality was not the same as requiring every protocol message to be encrypted. The checklist graded what a design could express and require of implementations. It did not certify what any packet, proxy, server or subscriber actually experienced.

Abstract enterprise scene of minimalist office desks with blank glowing screens connected by network lines over a globe centred on Europe and South Asia, alluding to Allianz Technology SE's global AI operations.

Market / Companies

The 2027 Question: What Allianz's AI Numbers Actually Measure

Allianz's public AI story is usually told as a deadline. The group's Capital Markets Day set 2024–2027 targets, and coverage since has often folded its internal AI platforms into that countdown. The documents Allianz publishes tell a more precise story: 2027 is a productivity ambition stated in financial terms, while the evidence of what AI capacity is actually being built sits in adoption counts, delivery-footprint entities and 2026 platform milestones. Reading those numbers against each other shows where the group's AI execution is real, and where the framing outruns the record.

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 Atlas Says “Dissimilar” Probe Selection Is Complete. Its Public API Does Not Name the Selector
  2. APNIC Whois mnt-lower Marks Maintainer Hierarchy, Not Routing Hierarchy
  3. A Signed Transaction Token Does Not Attest Every Claim
  4. A CoAP Group Address Is Not a Security Membership Roster
  5. A Cleared Incident Does Not Prove Which Command Cleared It
  6. A Capability Menu Is Not a Subscription Decision
  7. An Enrollment Voucher Arrives After Identity Leaves the Device
  8. Henning Schulzrinne and the Ringing Response That Arrived Before Anyone Answered
  9. ICANN’s .TEXAS Consent Gate Is Exact. Texas’s Letter Adds “Any Derivative”
  10. The Proposed WebAuthn Charter Opens Raw Signing. Scope Is Not Approval
View Governance

Market

  1. Vint Cerf and the Deadline Behind the TCP/IP Cutover
  2. Jason Speers and the Hidden Handoffs Inside a Digital-First ISP
  3. ARTEMIS and the minute between a BGP alert and a safe response
  4. Backblaze's customer-held keys change who operates the second copy
  5. Nurani Nimpuno and the Accountability Layer Behind Number Governance
  6. Axtel's Second Bidder Has Preliminary Approval, Not a Higher Offer
  7. CleanSpark Has a 175 MW Lease, Not an 885 MW Delivered AI Campus
  8. Seyed Pouria Mousavizadeh Tehrani and the State Hidden Before IPv6’s First Reply
  9. Daniel Fett and the Issuer Field That Named the Server, Not the Token
  10. Cloudflare R2’s zero-egress price is not a zero-cost exit
View Market

Membership

  1. The Route Policy Can Change While Its SR-Algorithm Number Stays the Same
  2. A DNS Filtering Notice Is a Chain of Three Decisions, Not One Explanation
  3. A Registry-Lock Quorum Counts Approvals, Not Independent Authority
  4. The Address Was Borrowed. The Route Was Never Included: RFC 2008
  5. The State Table Was Also a Kill Switch: RFC 2012
  6. Remco van Mook and the IPv4 Gateway That Has No IPv4 Neighbour
  7. The Grant Was Automatic. The Boundary Was Not: RFC 1988
  8. A Join Priority Is Not an Enrollment Decision Record
  9. A Holder-Designated RDAP Referral Extends Discovery, Not Registry Authority
  10. Allison Mankin and the Name-Collision Sample That Could Not Prove Its Cause
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 Server Forgot the Lock. Recovery Began by Refusing New Ones: RFC 3010

NFS version 4 turned a crash into an argument over remembered rights. RFC 3010 answered with a bounded order: identify the returning client, let old state be reclaimed, and keep new conflicts outside until that opportunity had passed.

تعود إيصالات حالة العملاء عبر ممر تعافٍ كهرماني إلى خادم أعيد تشغيله وسجله فارغ، بينما تنتظر الطلبات الجديدة المتعارضة خلف بوابة منفصلة.

The Server Forgot the Lock. Recovery Began by Refusing New Ones: RFC 3010

NFS version 4 turned a crash into an argument over remembered rights. RFC 3010 answered with a bounded order: identify the returning client, let old state be reclaimed, and keep new conflicts outside until that opportunity had passed.

  1. The Signature Verified. The Resolver Still Asked Who Was Allowed to Sign: RFC 3008
  2. The Gate Issued a Challenge. Trust Still Had to Arrive: RFC 3012
  3. The DNS Reply Carried the Request’s MAC Forward: RFC 2845
Open History Session

Leadership Alliance

The Tags Looked the Same. One Was a Limit, the Other a Preference: RFC 2987

In November 2000, RFC 2987 placed `charset` and `language` inside the same media-feature grammar. Both used registered tokens, equality comparison and optional quality weights. Yet the document refused the most convenient inference: identical syntax did not make the two claims equivalent. A charset was usually a machine limit. A language was usually a human preference. The history matters because systems still fail when they let the shape of a declaration decide what the declaration is allowed to prove.

يدخل قرصان نحاسيان متطابقان في مقارن مساواة واحد؛ تختبر بوابة فك صلبة مسارًا، بينما ترتب شرائط صوتية متعددة الخيارات حول مستمع في المسار الآخر.

The Tags Looked the Same. One Was a Limit, the Other a Preference: RFC 2987

In November 2000, RFC 2987 placed `charset` and `language` inside the same media-feature grammar. Both used registered tokens, equality comparison and optional quality weights. Yet the document refused the most convenient inference: identical syntax did not make the two claims equivalent. A charset was usually a machine limit. A language was usually a human preference. The history matters because systems still fail when they let the shape of a declaration decide what the declaration is allowed to prove.

  1. The Namespace Was Global. Resolution Was Not: RFC 3001, RFC 3061, and the Authority Hidden in `urn:oid`
  2. The codec agreed. The nibble did not: RFC 2422
  3. The Access Concentrator Waited for the Cookie to Return: RFC 2516
Open Alliance Session