Skip to main content

Lead Report / History

يظل مسار BGP المتعافي خلف حاجز التخميد بينما تتناقص عقوبته المحلية، مع بقاء مسار بديل ظاهراً.
A BGP route can become reachable again before a router has forgotten its instability. RFC 2439 turned recent route history into a temporary penalty: decay could restore a suppressed path, but only after its score crossed a separate reuse threshold.

The Route Stopped Flapping. Its Penalty Had Not: RFC 2439

A BGP route can become reachable again before a router has forgotten its instability. RFC 2439 turned recent route history into a temporary penalty: decay could restore a suppressed path, but only after its score crossed a separate reuse threshold.

  1. ترى مجموعتان من الموجّهات مسارات متداخلة جزئياً وتتناوب بينهما إشارات الاختيار.

    The Best Route Was Not a Stable Answer: RFC 3345

    A router can choose the best path in its own table, advertise it, and still help create a loop that makes the next “best” choice different. RFC 3345 showed how that can happen when BGP’s scaling shortcuts reduce which exit paths each router sees.

  2. An empty slot in an archival registry drawer sits beside a separate device module holding a glowing token, illustrating how a code can be absent from the record yet present in use.

    The RFC Was Missing. The DHCP Option Was Not.

    RFC 3679 returned DHCP option numbers that had no durable use, but it refused to treat an empty RFC shelf as proof that every code was free. PXE and Apple implementations were already using some undocumented numbers. Sixteen years later, a captive-portal experiment would show why that distinction mattered.

  3. Two equal network marks travel with packets of different sizes toward an endpoint that weighs their byte volume separately.

    Why Congestion Is Marked per Packet but Read per Byte: RFC 7141

    In 2014 the IETF drew a boundary between making a congestion signal and interpreting its weight. A router should not give a small packet a softer chance of being marked; a transport may still count a marked packet in proportion to the bytes it carried.

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

Celestica Revenue Jumped 62%. Why Sell 11.1M Shares?

Celestica Revenue Jumps 62%—What About Cash?

TLS Is Connected—Is the Device Still Trusted?

Inseego Bought Nokia’s FWA Business. Compatibility Too?

Salesforce + Bandwidth: Is Voice Live Everywhere?

Calendar Says “Owner”—Can You Actually Edit?

Celestica Revenue Jumps 62%—What About Cash?

You Paused the Stream. Did the Network Stop?

AML Check Completed—Is the Customer Cleared?

Payment Matched. Was the Product Delivered?

Zhone Completes Tellabs Deal—Are the Systems Integrated?

You Paused. Is the Network Still Fetching?

AML Check Complete. Did You Pass?

Payment Confirmed. Where’s the Product?

The Deal Closed—But the Products Aren’t Integrated Yet

Conceptual illustration of separate data-centre sites linked across a Japanese coastal landscape by network and power signals; no specific facility or demonstrated result is depicted.

Market / Trends

Japan’s virtual hyperscaler still has to become a service

A 12-organization Japanese trial is trying to place AI workloads against data-centre, network and power conditions. Its commercial test is whether those signals can become a customer promise, with measurable value and a clear party accountable when a job fails.

RFC 3596 · DNS query transport · IPv4 and IPv6 record families remain independent

Governance

The Query Crossed IPv4. Its Answer Could Still Name IPv6: RFC 3596

DNS did not need an IPv6 road in order to talk about an IPv6 address. RFC 3596 kept the packet carrying a question separate from the record the question asked for—a small design boundary that let one naming system span a mixed-version Internet.

AI editorial portrait of Grace Hopper, shown head and shoulders in a softly focused mid-1970s programming office.

Market

Grace Hopper Turned Portability into a Test—and Credited the Team

A language standard can describe what a compiler should do without showing whether different vendors’ compilers actually do it. When Grace Hopper returned to Navy service in 1967, the problem was no longer only how to write a common language. It was how to test the implementations—and make the test travel across machines too.

Conceptual diagram of Cloudflare R2 object storage, an outward file-transfer route and a separate workspace for inspecting replacement application components.

Market / Companies

Cloudflare R2’s zero-egress price is not a zero-cost exit

Cloudflare lists no charge for outbound transfer from R2 and documents a way to copy objects out. The remaining economic question is what customers must spend—and successfully operate—to turn that export into a working replacement.

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. One Datagram Changed Its Route. The Other Socket Defaults Should Have Survived: RFC 3542
  2. One IDN Registration Reserved a Package, Not Just a Label: RFC 3743
  3. The IETF Made a Lower-Level Reference Visible Before It Made It Easier: RFC 3967
  4. DHCP Gave Vendors Separate Option Spaces, Not IANA-Defined Meanings
  5. The Phone Said Ringing. The Caller Still Had to Listen for Packets: RFC 3960
  6. The Peer Could Invalidate the STag. The Local Layer Still Had to Check: RFC 7145
  7. The Directory Tree Grew Sixfold. The Client Still Needed a Map.
  8. A Gateway Could Change the Wrapper, Not the Message: RFC 3923
  9. The Tunnel Was Up. Its Primary Path Might Not Be: RFC 3970
  10. The Name Promised Persistence. Its Resolver Did Not Yet Exist: RFC 3937
View Governance

Market

  1. A Three-Year Transition Is in the Draft. ICANN Is Still Pricing the Work
  2. Progress’s Domo price is a bet on revenue after planned churn
  3. CoreWeave’s 240 MW India plan is a delivery clock, not compute yet
  4. HPE’s Gen13 servers broaden AI choices, not yet the economics
  5. Samsung’s $1bn Helix commitment is capital, not an order book
  6. Cloudflare gains a European sales channel, not yet a service guarantee
  7. Independence Is a Process, Not a Label: How the UN Chose Its AI Science Panel
  8. FreeU has a $55 price; the value of each ad remains undisclosed
  9. Vodacom has proved the refund loop; virtual wheeling still needs a price test
  10. Skyworks’ $500m synergy clock has started; product upside is still unpriced
View Market

Membership

  1. The Deadline Expired. The SCTP Stack Could Check Later.
  2. TCP Delivered the Trap. It Still Did Not Confirm the Operation: RFC 3430
  3. Thirty Minutes Was a Forgetting Timer, Not a Failover Promise
  4. A Search Result Was Not an Identity: RFC 3744’s Canonical Principal
  5. The Handle Envelope Sat Outside Its Message Credential: RFC 3652
  6. A Passport for Tax Data: Why Security Is Becoming a Continuing Condition of Exchange
  7. The Rule Had a Sunset Date. Its Evidence Report Was Optional: RFC 3933
  8. The Name Crossed Protocols. Its Parameters Did Not Move by Themselves: RFC 3555
  9. Compatibility Hid the Cost. RFC 1263 Wanted the Version Boundary Visible
  10. Reply-All Could Reuse the Fax Sender’s Permission: RFC 3965
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. 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 AD Bit Reported Validation Policy, Not a Signed Answer: RFC 3655

A DNS reply can contain a one-bit assurance from the resolver that checked it. In 2003, RFC 3655 narrowed what that bit meant—and made clear that trusting the bit depended on trusting the resolver and the path to it.

يفحص المحلّل التكراري مجموعات السجلات ويرسل إشارة حالة مستقلة عبر قناة محمية إلى العميل.

The AD Bit Reported Validation Policy, Not a Signed Answer: RFC 3655

A DNS reply can contain a one-bit assurance from the resolver that checked it. In 2003, RFC 3655 narrowed what that bit meant—and made clear that trusting the bit depended on trusting the resolver and the path to it.

  1. The Tunnel Accepted the Packet. Decapsulation Erased Its Nearest Trace: RFC 3964
  2. Zero Did Not Mean Default. It Meant 4,294,967,296 Iterations: RFC 3962
  3. One Binding Moved a Whole Network. It Did Not Prove Every Node Was Reachable: RFC 3963
Open History Session

Leadership Alliance

Forum’s AI revenue forecast is a commissioning calendar, not a run rate

Forum Markets’ planned 2027 AI revenue depends on turning three sites and a financing model into accepted, billable GPU hours. The company’s 11-megawatt-at-the-meter plan is a useful starting point, but it is not 11 megawatts of operating compute or proof of cash earnings.

Универсальный электросчётчик и силовые кабели ведут к серверам GPU без маркировки в дата-центре; это концепция, а не площадка Forum или Edge Node.

Forum’s AI revenue forecast is a commissioning calendar, not a run rate

Forum Markets’ planned 2027 AI revenue depends on turning three sites and a financing model into accepted, billable GPU hours. The company’s 11-megawatt-at-the-meter plan is a useful starting point, but it is not 11 megawatts of operating compute or proof of cash earnings.

  1. After the WTO Moratorium Lapsed, Three Tracks Claimed Different Mandates
  2. ReuNION’s 320 Tb/s is design capacity; the financing chain is the test
  3. Penguin’s AI factory boom is now a working-capital business
Open Alliance Session