Profile
Research
Research 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.
IETF
An Expired Internet-Draft Is Not a Rejected Proposal
The standards register had only two columns: document and outcome. Beside an Internet-Draft, a reviewer had copied the Datatracker label `Expired` and entered “Rejected by the IETF.” No rejection notice was attached. There was no adoption call, consensus record, Last Call, IESG…
CASE FILE
The Certificate Had Not Been Verified. Its Memory Claim Already Had to Be Judged: TLS Compression and the Pre-Trust Boundary
A two-kilobyte handshake message says it will become twelve megabytes after decompression. Before the receiver can inspect a name, a signature or a chain, it must decide whether that unauthenticated claim deserves memory and CPU. RFC 8879 makes certificates smaller on the wire…
IETF
An RFC MUST Without a Subject Is Not an Audit Finding
The compliance sheet looked decisive: “RFC 8200 — MUST — failed.” It named no component, packet condition, conformance profile or test. It did not say whether the cited sentence governed a sender, receiver, router or operator. A capitalized word had become the entire finding. The…
CASE FILE
The Edge Received a Key. It Did Not Receive the Certificate: TLS Delegated Credentials and the Boundary of Short-Lived Authority
A front end can finish a TLS 1.3 handshake for the certificate owner without holding the certificate’s long-term private key. What crosses that boundary is powerful but deliberately small: a signed public key, a role, an algorithm and an expiry—not the certificate, the CA…
IETF
The Packet Arrived Last. That Does Not Mean the Event Happened Last
In a wraparound test, a CoAP server sends one notification just before its Observe value rolls over and another just after. The newer datagram reaches the client first. The older one has been sleeping in a queue inside the network and arrives second. A client that sorts the two…
ICANN
Records in Escrow, No Registrar in Operation
At 09:00, a data escrow agent accepts a registrar's deposit. Its hash matches, the file opens, every required field passes validation and ICANN receives a valid-deposit report. At 09:15, imagine that the registrar's site, telephone line and customer portal stop answering. The…
CASE FILE
The Peer Requested New Keys. It Did Not Own the Epoch: TLS 1.3 KeyUpdate and the Authority to Rotate a Live Connection
One encrypted record leaves under the old key. Every later record from that sender must use the next one. The peer can authenticate the transition and ask for a reciprocal change, but it cannot see whether yesterday’s secret left memory, choose the other endpoint’s work queue, or…
CASE FILE
The Speaker Was in the Session, Not the Path: IXP Route Servers and the Authority to Broker Reachability
The BGP session was established to one system. The route began with another network's AS number. Its next hop named a third address on the exchange fabric, and the packets never crossed the machine that had delivered the UPDATE. Nothing was malformed. The apparent contradiction…
CASE FILE
An RFC Number Does Not Mean the IETF Approved It
A compliance register that records only “RFC 8729” looks precise. It is not. The number identifies a durable document, but it conceals that this particular RFC is an IAB-stream informational statement rather than an Internet Standard. When a single column makes every RFC look…
CASE FILE
The Request Said Urgent. The Scheduler Still Decided: HTTP Priorities and the Authority to Allocate Scarce Delivery
A browser can call a hero image urgent, an origin can prefer the font, and a CDN can see both through a different connection map. RFC 9218 lets each express useful information. It does not let any of them annex the scheduler that finally allocates the next byte.
History
The Prefix That Tried to Make IPv6 Automatic: 6to4 and 2002::/16
6to4 offered a seductive bargain: turn an existing IPv4 address into an IPv6 network and let relays complete the journey. The address trick worked as specified. The operational responsibility did not assemble itself around it.
CASE FILE
The “Obsoletes” Line Is Not a Remote Kill Switch
When RFC 9113 replaced the earlier HTTP/2 specification, the catalogue moved and selected registry references moved with it. A live connection did not. It still negotiated `h2`; no standards editor reached into a server, removed old code or accepted the outage risk on an…
ICANN
The Four-Hour Transfer Contact That Cannot Reverse the Transfer
The Four-Hour Transfer Contact That Cannot Reverse the Transfer 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. The…
North America National Telecom Trends
The outage clock starts before the root cause exists
Canada’s major-outage rules do not wait for an incident team to finish explaining the failure. They create a sequence of reporting clocks that begins with threshold evidence, continues through material updates and ends in a post-outage record that can survive both regulatory and…
Asia-Pacific National Telecom Trends
User-level AI-RAN needs an error ledger, not one average
DOCOMO and Samsung report that simulated user-level optimisation cut throughput-degradation frequency from 13.1% to 7.2%. The result is promising; commercial control depends on who improved, who was incorrectly changed, what other users lost and how the network rolls back.
Global Datacenter Trends
The battery passport behind a data-centre UPS replacement
A replacement battery rack can fit the room, the voltage window and the maintenance plan yet still fail as an option. From 2027, a qualifying industrial battery also needs an evidence chain that can travel with the hardware.
Asia-Pacific National Telecom Trends
DOCOMO's 2028 satellite roadmap needs a service envelope
DOCOMO has contracted for a satellite layer intended to add voice, faster browsing and IoT during fiscal 2028. The roadmap is strategically significant; its operating value will depend on published limits for capacity, latency, priority, device certification and fallback.
CASE FILE
The Resolver Named the Failure. It Did Not Prove the Cause: Extended DNS Errors and the Authority of Diagnosis
Extended DNS Errors can turn an opaque DNS failure into a useful account of what one resolver observed. The gain is operational clarity. The danger begins when a dashboard promotes that account into proven cause, assigned blame or permission to weaken the control that produced…
Global Datacenter Trends
The refrigerant deadline hiding inside data-centre cooling capacity
A cooling plant can be mechanically sound and still cease to be a safe basis for growth. The hidden boundary sits in the refrigerant, the rule date and the service chain that keeps the machine lawful and repairable.
Asia-Pacific National Telecom Trends
Marunouchi makes real estate the control plane for mmWave
DOCOMO and Mitsubishi Estate want to build a dense 5G cluster across one of Tokyo's busiest business districts. The partnership addresses mmWave's hardest constraint: radios only work where property access, sightlines, fiber, power and streetscape approval meet.