Profile
Briefing
Briefing profile intelligence connects person, company, institution, and other entity coverage for readers comparing the subjects behind BTW.MEDIA reporting. The page helps compare public profiles, related events, evidence packs, role changes, operating footprints, governance exposure, organisational links, and market relevance while keeping organisation and people records distinct from ordinary news chronology. Readers can understand the subject behind the headline, the evidence supporting that profile, and the infrastructure or market relationships that make the profile relevant. They can see who or what the profile represents, which public sources support it, how it connects to companies, markets, governance bodies, or events, and what changes may deserve continued attention as the subject evolves.
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…
IETF
The Router Answered for the Exit. The Link Was Still Unproven
RFC 9703 lets MPLS Ping and Traceroute ask whether an EPE-SID reaches the peer association named by its Target FEC Stack. The reply can validate an egress role, and sometimes the observed incoming interface. It cannot make a skipped interface check, an unreconciled controller…
IETF
The Same Mail, Through Another Door: What JMAPACCESS Actually Promises
A mail client can discover a JMAP route without asking its user to start again. The difficult decision comes afterward: which parts of the old connection's knowledge remain usable through the new one?
History
The Bytes Looked the Same. The Page Boundary Did Not Come for Free: RFC 2159
RFC 2159 called the passage between X.400 fax bodies and MIME `image/g3fax` “nearly Byte copy”. The qualifier did the real work. The page image could remain recognizably the same while the gateway reversed every byte’s bit order, carried options into header parameters, padded the…
IETF
The Registry Changed. The Old Flow Did Not: RFC 9710
A one-line type correction can travel from IANA into generated collector code, dashboards and incident evidence. RFC 9710 shows why that journey needs a chain of custody: the registry may be normative, but a current row cannot silently upgrade yesterday's parser or rewrite…
North America Datacenter Trends
DMG spends before its 50MW tenant deal is definitive
DMG has bought connectivity and advanced conversion work at Christina Lake while the proposed 50MW AI-colocation agreement remains a letter of intent. The value of that head start depends on which commitments can serve a signed tenant rather than become stranded capital.