Skip to main content

Lead Report / ICANN

A copper Texas silhouette engraved .TEXAS fits an exact transparent gate while four separate review routes branch beside a blank scope receipt.
Six words enlarge a clear objection into an undefined perimeter. Texas told ICANN that it opposed `.texas` “and any derivative thereof.” The 2026 Applicant Guidebook gives the state a consequential voice over the exact ISO 3166-2 match, but it also says strings that include without exactly matching a geographic name fall outside that consent gate. Preserving both rules requires a record that assigns every real applied string to its actual review route instead of letting correspondence become a shadow list of names.

ICANN’s .TEXAS Consent Gate Is Exact. Texas’s Letter Adds “Any Derivative”

Six words enlarge a clear objection into an undefined perimeter. Texas told ICANN that it opposed `.texas` “and any derivative thereof.” The 2026 Applicant Guidebook gives the state a consequential voice over the exact ISO 3166-2 match, but it also says strings that include without exactly matching a geographic name fall outside that consent gate. Preserving both rules requires a record that assigns every real applied string to its actual review route instead of letting correspondence become a shadow list of names.

  1. Editorial illustration of four separate standards-admission gates with distinct sealed authentication and signing-key branches in the foreground.

    The Proposed WebAuthn Charter Opens Raw Signing. Scope Is Not Approval

    W3C is considering a larger mandate for Web Authentication. The proposed charter would let the group work on signatures over arbitrary data, including uses associated with agentic AI and verifiable digital credentials. That sentence opens a standards room; it does not certify the design inside it. The public record still describes a draft extension with no user research, no browser-implementor signals and no guarantee that a person understood the bytes being signed. The governance task is to preserve those states instead of letting “in scope” become a premature badge of approval.

  2. Editorial still life of seven matching APNIC council seats feeding one fixed selector, a distinct connected ex-officio executive chair, and two blank brass language plates exchanged above the unchanged mechanism.

    APNIC Renamed an Election as an Appointment. The Selector Did Not Change.

    APNIC's 2026 By-law amendment replaced one verb: the Executive Council would no longer “elect” the Director General but “appoint” that officer. Read alone, the change sounds like a transfer of power. APNIC's own supporting paper says the opposite. The selector was already the Executive Council, acting by majority vote. What changed was the legal description of that act and the boundary between seven membership-elected Council seats and one ex-officio seat held by the chief executive.

  3. A certificate tile passes through a dark internal timing chamber, expands into a field of related certificates, and reaches two transparent public revocation endpoints.

    The CA/B Forum Draft Makes Revocation’s End Public. Its Clock Starts Inside the CA

    A proposed rewrite of the TLS Baseline Requirements would finally say what a relying party must be able to see before a certificate counts as revoked. Yet the deadline would begin at a less visible event: the moment the certificate authority classifies an incoming problem report as actionable. The stronger endpoint makes the missing start receipt harder to ignore.

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

37 Million T-Mobile Accounts Exposed—What Could Attackers Actually Do?

AI Answered Your Call. Did It Solve Anything?

Your Account Was Hacked. Why Didn’t Reporting It Fix Anything?

Can Your AI Search Give Away Your Plans?

How a Cyberattack Became a Gas Shortage | Colonial Pipeline Explained

16 Kbps on Paper. Just 80 bps in Practice.

Factory Reset: 100% Complete. Still Offline?

One Dot Sent Cookies to the Wrong Website | curl Bug Explained

Why Waymo Stopped During San Francisco’s Blackout

Waymo’s Blackout Test: Safe Stops, System Limits

The Fiber Recovered in 12 Minutes. T-Mobile Took 12 Hours.

IP Lock-In Is Not Loyalty: How ISPs Can Monetize Portability

Four Green Streams. No 3D Person. What Failed?

Why This Repair Route Had to Stay Secret | RFC 831

HTTPS at the Edge—Without Copying the Master Key

An unnumbered clock mechanism pauses at a luminous verification gate before the path divides into several independent decision chambers.

Governance

ICANN Wrote a 24-Hour Disclosure Clock. Authentication Decides When It Starts

The most consequential sentence in ICANN's new urgent-disclosure rules is not the one containing “24 hours.” It sits lower on the same policy page, in an implementation note: the obligations become effective when ICANN fully implements a Consensus Policy that establishes requester authentication. Both statements are true. Section 10.7 contains a precise clock for registrars and registry operators, and that clock is not yet an enforceable Section 10.7 clock. The distinction is more than drafting hygiene. It determines when compliance begins, who can start the timer, which request channel counts and what an authentication credential is allowed to prove. ICANN needs an activation receipt that makes the transition visible without turning identity verification into a decision to disclose.

A network engineer checks an isolated router rack linked through a controlled fibre feed-through to production equipment behind glass.

Market / Companies

OVHcloud made anti-DDoS maintenance a BGP-to-OSPF change-control failure

OVHcloud's October 2021 outage began with planned work intended to strengthen anti-DDoS protection, but the public record describes a routing-control failure rather than a successful attack. A command affecting redistribution from BGP into OSPF caused the full Internet routing table to enter the internal routing system, exhausted control-plane resources, broke IPv4 reachability, defeated the attempted rollback, and forced engineers to isolate and power off a router before the network could converge. The incident is a test of whether production change controls govern the routes that actually run, not merely the procedure that was approved.

Two IPv6 packet variants encounter different parser depths along the same network path.

Market / Trends

IPv6 Extension Headers Are Becoming a Path-Compatibility Tax

The address answers. Ping works. Then the transport header moves 64 bytes deeper into an otherwise valid IPv6 packet, and the path goes quiet. Basic reachability survived; optional capability met the smallest parser on the route. It is a compact demonstration of how a protocol feature becomes somebody else’s hardware budget.

AI-generated editorial illustration showing a bespectacled man in a data centre beside Ceph distributed-storage nodes and block, object and file storage symbols.

Market

Sage Weil: The Architect Who Made Distributed Storage Calculable

Sage Weil’s most durable contribution to internet infrastructure was not a storage appliance but an architecture. Ceph used CRUSH to calculate where data belongs and RADOS to spread storage, repair and movement across a cluster. The design helped commodity machines behave like one storage system—and created an operational project that ultimately had to outgrow its founder.

AI-generated editorial illustration of an empty conference stage leading through layered methodological review, operator challenge, response and archival correction; no real person, venue, slide, document or data is depicted.

Governance / NOGS

The Talk Was Accepted. The Evidence Wasn't Settled: NANOG's Vendor Test After the Stage

A number can travel farther than the qualification printed beside it. The dispute that followed NANOG 96's presentation on IP geofeeds shows why vendor research should be judged neither by the employer on the title slide nor by the applause in the room. Its proper test is whether operators can follow a consequential claim through method, denominator, objection, response and correction after the microphone has been switched off.

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. An IETF-Appointed ISOC Trustee Is Not an IETF Delegate
  2. The Writ Reached ICANN; the Registry Data Stayed Abroad
  3. The Nine Applicants and the Missing Settlement in ARIN Arbitration
  4. ICANN Can Group Two Strings Without Finding Them Similar. What Does the Middle String Control?
  5. After the Silence: What AFRINIC’s 2017 Written Cure Needed to Prove
  6. LACNIC’s RDAP Last Changed Event Dates the Registry Record, Not the Network Handover
  7. The Takedown Notice Did Not Become a Verdict: Petroliam Nasional v. GoDaddy
  8. The Forged Letter That Moved Sex.com: Kremen v. Cohen and Network Solutions
  9. ARIN’s 28 “Legitimate” Fraud Reports Were Not 28 Findings of Fraud
  10. The Public Query Became a Private Lead Machine: Register.com v. Verio
View Governance

Market

  1. Inet Tehno SRL and the cash-flow test behind local network reliability
  2. LymeFiber’s 57-Mile Build Meets Its Real Test at the Pole
  3. EAST STARK-TV LLC and the cash-flow test behind local network reliability
  4. Hostinger Operations UAB as Registrar: Can a Business Recover Its Domain When the Administrator Disappears?
  5. Mauritania's 2018 ACE Cable Cut Made International Path Diversity an Accountability Test
  6. China Telecom's 2010 Route Leak Made Prefix-Volume Claims an Accountability Test
  7. Linode and AS63949: Cloud Convenience Still Needs Operator Discipline
  8. The Denominator Behind the Uptime Promise
  9. TPG's 2024 voice outage turned emergency-call notification into a change-control test
  10. Amaliy Aloqalar Biznesi Ltd. and the cash-flow test behind local network reliability
View Market

Membership

  1. DENIC's 2026 .de DNSSEC Failure Made Signing-System Parity an Accountability Test
  2. The 90-Day Emergency Policy That Kept Domain Registration Data Moving
  3. A DNS Filtering Notice Is a Chain of Three Decisions, Not One Explanation
  4. A DDoS Scrubbing Contract Must Say Who Delivers the Clean Gigabit
  5. From 200 Days to 47, TLS Renewal Becomes Runtime State
  6. Telekom Malaysia's 2015 Route Leak Made Upstream Filtering a Transit Accountability Test
  7. The Zero-Egress Invoice Is Not the Cost of Leaving Scaleway
  8. UA Day Built 17 Demonstrations. Production Readiness Needs a Return Visit
  9. When a DNS-Abuse Report Becomes Actionable—and What the Contract Still Does Not Order
  10. C-Root's 2024 Stale Zone Made Publication Freshness a Root-Server Accountability Test
View Membership

Number Resource Society

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

View Number Resource Society
  1. When One Corporate Group Casts Twenty Registry Votes
  2. Digital Identity Requirements at the Registry Gate
  3. A Global South Label Cannot Substitute for a Mandate
  4. A Trust Anchor Rollover Needs an Acceptance Ledger
  5. A Member Logo Is Not a Live Power of Attorney
  6. A Country Field Is Not an RIR Mandate
  7. An ASN Transfer Needs a Routing-Identity Handover Ledger
  8. A ROA Change Needs an Authorization-and-Withdrawal Ledger
  9. An Unanswered Profile Needs a Reply-State Ledger
  10. The FAQ Answer Needs a Version Date

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

Andrew S. Tanenbaum and the Amoeba Capability That Authorized an Object, Not a Person

Amoeba compressed a service address, an object name, an operations mask and an anti-forgery check into 128 bits. The resulting capability could travel with user code and carry authority without a central list of holders—but a valid token still said nothing by itself about the holder's human identity, purpose, mandate or the durable result of an operation.

AI editorial portrait of Andrew S. Tanenbaum beside an abstract segmented Amoeba capability

Andrew S. Tanenbaum and the Amoeba Capability That Authorized an Object, Not a Person

Amoeba compressed a service address, an object name, an operations mask and an anti-forgery check into 128 bits. The resulting capability could travel with user code and carry authority without a central list of holders—but a valid token still said nothing by itself about the holder's human identity, purpose, mandate or the durable result of an operation.

  1. The Receiver That Chose What Came First
  2. The Save That Left the Page Intact: HTTP 204
  3. The Address That Grew Old Before It Died
Open History Session

Leadership Alliance

Zayo Group, LLC and AS6461: What Can a Fiber Backbone Prove About Route Continuity?

A large fiber network can move traffic across long distances, but size alone cannot tell a buyer whether one application, office, data centre or customer circuit will stay online during a failure. Public records around Zayo and AS6461 show why that distinction matters. Registries identify names and number resources. Routing observers show what their collectors could see at particular times. Security records can show whether one route origin was authorised. Company materials describe products, options and operating policies. Each layer is useful, yet none is a substitute for testing the exact service a customer plans to rely on.

Zayo Group, LLC and AS6461: What Can a Fiber Backbone Prove About Route Continuity?

A large fiber network can move traffic across long distances, but size alone cannot tell a buyer whether one application, office, data centre or customer circuit will stay online during a failure. Public records around Zayo and AS6461 show why that distinction matters. Registries identify names and number resources. Routing observers show what their collectors could see at particular times. Security records can show whether one route origin was authorised. Company materials describe products, options and operating policies. Each layer is useful, yet none is a substitute for testing the exact service a customer plans to rely on.

  1. CenturyLink's 2018 outage showed how an unused management channel became a national failure path
  2. The Route Policy Can Change While Its SR-Algorithm Number Stays the Same
  3. Sandhills Publishing's AS20005 Control Surface: Routing Records, Dual Data Centers, and Continuity Costs
Open Alliance Session