Content Type
Research
Within the Content Type facet, Research intelligence gathers BTW.MEDIA articles that share the same editorial format, helping readers compare briefings, profiles, risk notes, market analysis, and event coverage without mixing different kinds of evidence. The page explains how this content type frames internet infrastructure events, company movements, governance decisions, operational signals, and public evidence across the site. Readers can compare which actors or infrastructure systems appear most often, how source quality changes interpretation, and whether the material is a durable profile, a time-sensitive event, a strategic market signal, or a governance development. The result is a useful search page for operators, investors, customers, analysts, and policy stakeholders who need to understand the consequence, timing, and evidence behind similar article formats.
CASE FILE
DATAMATIX AS210973: what the live record proves about real operation
DATAMATIX AS210973: what the live record proves about real operation intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may follow.…
Asia-Pacific Institutional
The Challenger Who Never Held the Delegation: Cloud Registry Pty Ltd and the Contracted Enclosure of .au Authority
Cloud Registry Pty Ltd has spent more than a decade arguing that Australia's .au registry should be awarded by open tender, and it has never once held the contract. That record makes the small Sydney company a useful instrument for reading how delegated authority over a national…
CASE FILE
Sanctioned but Not Ordered: Svea's Two Accountability Channels
When a Swedish financial regulator fined Svea Bank AB 170 million kronor in December 2025, the fine made headlines. What the decision itself ordered — and, more precisely, what it did not — tells a sharper story about where accountability for the bank and for its internet-facing…
Global Datacenter
Registered, authorised, and still unproven: what DATAMATIX's live posture says about operating a network
Registered, authorised, and still unproven: what DATAMATIX's live posture says about operating a network intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the…
Story
AS210860 without a first-party witness: what the registry's unreadable endpoint means for DFINFRA
AS210860 without a first-party witness: what the registry's unreadable endpoint means for DFINFRA intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…
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 entity: 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…
Number Resource Society
From Draft to Adoption: What the Status Reports Reveal About the ICP-2 Succession
Two years after the Number Resource Organization's Executive Council asked its Number Council to review and update Internet Coordination Policy 2, the successor instrument has been drafted, consulted, revised and handed over — but it has not been adopted. The official process…
History
The Hash Chose Which DHCP Server Could Answer. It Could Not Promise Service
RFC 3074 turned a configured share into 256 buckets and a repeatable answer to one narrow question: which server was eligible to respond? The map did not measure work or prove a lease arrived.
ICANN
The Remedy That Has Never Been Used: Whether the Draft RIR Governance Document's Derecognition Machinery Is Actually Operable
Every accountability system is judged not by the rules it writes but by whether anyone has ever made those rules work. The *Governance Document for the Recognition, Operation, and Derecognition of Regional Internet Registries* — Version 3, dated 1 September 2026 and labeled FINAL…
History
The Hash Assigned the Server. It Did Not Prove the Server Was Ready: RFC 3074
RFC 3074 let cooperating DHCP servers compute who should answer without negotiating each request. The same calculation could not say whether the chosen server was reachable, had an address to offer or completed the client's configuration.
Asia-Pacific Institutional
TrueMoney's Scale Claims, Audited Against Its Own Paperwork
The TrueMoney wallet is the consumer face of Ascend Money, the fintech owned by Thailand's CP Group, and the directory entity Truemoney Company PLC is the card that tracks it. Previous reporting, including BTW's own account of the virtual-bank approval path published 30 September…
CASE FILE
The Mailbox Was Never the Remedy: Where Accountability Actually Fired in the Svea Abuse-Contact Chain
Every abuse report has to land somewhere. For Svea's legacy routed network block 193.105.138.0/24, the landing place shown by independent mirrors of the RIPE Database is a shared mailbox on the Verizon Business domain — a carrier-era contact inherited from a lineage Svea never…
History
The MIME Name Was Public. The Font Specification Still Lived at the Vendor: RFC 3073
RFC 3073 gave Portable Font Resource files a public MIME name. It did not make that name a substitute for the complete specification, a compatible decoder or evidence that a recipient rendered the intended glyphs.
Story
The Svea Abuse-Role Record: Validated Contactability, No Documented Processing
The abuse contact recorded and mirrored for Svea's legacy netblock 193.105.138.0/24 is a carrier-era inherited mailbox on the Verizon Business/UUNET lineage — registry-validated for technical deliverability but never documented to have received, answered, escalated or remediated…
History
The Parser Could Skip the Chunk. It Could Not Know What It Meant: RFC 3072
RFC 3072 made an unfamiliar SDXF chunk traversable by giving it a boundary a reader could locate. But reaching the next chunk is not the same as understanding what was skipped—or knowing whether an application can safely ignore it.
Asia-Pacific Institutional
The Small Autonomous System: FPT Software and What AS131402 Actually Does
The Small Autonomous System: FPT Software and What AS131402 Actually Does intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may…
History
The Label Was a Country Code. The Registry Could Still Be Generic: RFC 3071
In 2001, John Klensin argued that two characters could identify a country-code namespace without telling readers how its registry actually behaved. RFC 3071’s proposed categories followed operating practice—not the shape of the label—and stopped short of asking DNS administrators…
ICANN
If JPRS Fails, Who Keeps .jp Running? Reading the Successor Machinery in the .jp Record
Japan Registry Services Co., Ltd. (JPRS) has operated .jp since 1 April 2002 under an unusually public set of governing instruments. But the question of what happens if JPRS itself fails — bankruptcy, insolvency, or a decided re-transfer — has not previously been the subject of…
History
The Mask Promised a Neighbor. The VLAN Required a Router: RFC 3069
RFC 3069 saved IPv4 addresses by giving separated customer networks one shared prefix. But a host’s idea of “on-link” did not create a shared link: an upstream router had to answer, bind and forward.
History
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…