Content Type
Briefing
Within the Content Type facet, Briefing 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.
History
The Browser Remembered the Session. It Did Not Prove the Person: RFC 2109
In RFC 2109’s model shop, a server called a browser-held value `Customer="WILE_E_COYOTE"`. Later requests returned that value while separate cookies accumulated for a rocket launcher and a shipping method. The exchange made stateless HTTP remember a sequence. It did not make the…
North America Cloud Services Trends
Softcat’s $1.05bn GDT deal buys a service platform, not data-centre capacity
Softcat is paying for a route into large US technology accounts and the people, vendor relationships and delivery machinery that serve them. Whether that platform merits new dilution and leverage will depend on retention and cash conversion after completion, not on the…
Asia-Pacific Datacenter Trends
Bitdeer secured A202’s 65.1MW facility before it secured the customer
Bitdeer’s ten-year Johor data-centre agreement converts a large block of future electrical capacity into a dated operating commitment. It does not yet convert that capacity into cloud revenue—a distinction that matters far more than the headline value of the company’s sales…
Story
RIPE NCC Closed the Test API Incident. The Recovery Join Is Missing
Four status updates show a pilot service moving from investigation to resolution in 37 minutes. They do not show the small set of facts that would let a user connect that green status to a particular test operation, a checked isolation boundary and a completed reconciliation.
North America Datacenter Trends
Digital Realty’s $7.8bn Figure Is Not the $3.5bn Blackstone Cheque
The Northern Virginia acquisition joins a 100%-share asset value, a 64% seller interest, cash, stock and unfinished capacity in one headline. Investors need four ledgers, not one number.
North America Datacenter Trends
Oracle’s 1.7GW wind headline includes 433MW from existing farms
Oracle has presented more than 1.7GW across ten Texas wind projects as part of its electricity strategy for AI infrastructure. RWE’s disclosed 433MW component shows what that headline can—and cannot—mean: a virtual power purchase agreement tied to three operating, repowered wind…
CASE FILE
W3C’s Browser Portability Group Starts With a Report, Not a Standard
An iPhone user can now move selected Safari data into another browser through a documented export-and-import path. That is a real product capability. The W3C Browser Data Portability Community Group, launched on 15 September, is something else: a place to discuss principles and…
IETF
An Open Meeting Is Not an Antitrust Alibi: RFC 9680
RFC 9680 is most useful when read as a map of separated responsibilities. IETF procedure can make technical coordination open, contestable and reviewable. It cannot turn a published RFC, a declaration of rough consensus or a crowded meeting into proof that competitors never…
History
The Cell Skipped the Router’s Work. It Did Not Inherit the Route: RFC 2098
At a Cell Switch Router, one tiny lookup decided whether an arriving ATM cell stayed a cell or became an IP datagram again. A matching VPI/VCI entry sent it straight through the switch; a miss returned it to reassembly and IP forwarding. RFC 2098 built a fast path from that…
IETF
The Default Route Survived. The Leaf Did Not: RFC 9692’s Fallen-Leaf Test
A fat-tree can retain a perfectly valid default route while one plane has lost the path to a particular leaf. RFC 9692 repairs that mismatch with disaggregation, but the receipt of a control-plane exception is only the beginning of the evidence chain.
CASE FILE
The Score Starts Before the Stopwatch: RFC 9693 and Stateful NAT Evidence
A stateful NAT benchmark can report zero loss and still be incomparable with the run beside it. The missing variable may not be the offered rate. It may be the population of connections that existed before the measured traffic began—and whether the tester could send a valid…
IETF
The New Name Left of the Slash Was Registered. Nothing Else Was Proven
RFC 9694 turns a rare naming decision into an operating commitment. A new top-level media type can change how software groups unknown formats, chooses handlers and presents content to users. The registry entry is real, but it is only the first receipt in a much longer chain from…
ICANN
ICANN Mapped AFRALO’s Requests Without Adopting Them
The most important phrase in the AFRALO-AfrICANN submission is not in the Board Chair’s reply. It is in the cover note: the statement was sent to the ICANN Board “for information purposes.” Six pages of recommendations then met a two-page response that acknowledged the problem…
Story
APNIC’s Twin 28-Minute Incidents Need a Correlation Receipt
Two MyAPNIC incidents ended after exactly 28 minutes within roughly 49 hours. APNIC gave each a bounded explanation; it has not publicly said whether their dependency paths were compared.
Global Datacenter Trends
Generac’s US$8bn Warrant Meter Sits Above a Redacted Order Floor
Generac disclosed exactly how far Amazon-linked payments can move a 1,693,745-share warrant, yet withheld the minimum value of the Firm Orders beneath the supply relationship. That leaves investors with a visible equity ceiling and an invisible commercial floor—and makes the…
IETF
The Average Was Fast. The Frame Arrived Too Late for the Head That Moved
RFC 9699 describes why XR edge delivery is not a shorter-cloud problem. Offloading can spare a mobile device heat and battery drain, but it places tracking, world state, rendering and frame return inside one moving deadline. A good average hides the frame that returns after the…
IETF
XR's edge problem is the demand that averages conceal
RFC 9699 describes why extended reality might need nearby computing. The harder commercial question is who can prove that the late, crowded and thermally constrained moments remain usable.
History
The PostScript Bytes Stayed Still. The Carrier Identity Changed: RFC 2160
RFC 2160 gave a gateway two X.400 containers for one PostScript octet stream: an older Extended Body Part and a recommended FTAM Body Part. Both could cross into MIME without content conversion. That narrow success preserved the payload, but it did not prove which container a…
North America Datacenter Trends
NERC’s Computational-Load Standards Passed an Initial Ballot. Compliance Has Not Started
The preliminary vote matters because it narrows the chance that large computational loads will stay outside the reliability regime. It does not settle the text, approve a rule or start a compliance clock. Developers should distinguish those milestones before turning a standards…
ICANN
ICANN's 15-Day Verification Dialogue Became a Briefing. The Binding Route Is Still Unchosen
The most revealing part of ICANN's latest exchange about domain-registration accuracy is not whether contact checks should happen before a name resolves. It is what happened to the meeting meant to discuss that question: a proposed webinar and trilateral dialogue became an…