Content Type
Long Form
Within the Content Type facet, Long Form 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.
IETF
Jari Arkko and the Registry Field That the Protocol Did Not Need
A protocol registry is often read as a durable record, which makes every old column look like a permanent requirement. RFC 8602 takes the opposite discipline: an inherited postal-address field in two TRIP registration procedures had no identified use, so IANA stopped collecting…
North America Institutional Trends
Public Storage’s Canada Deal Has Two Unit Prices and a $500m Debt Draw
Public Storage closed its PS Canada acquisition with an upfront value of about $1.2 billion. The filed mechanics are more revealing than the rounded headline: 2,762,108 operating-partnership units valued at $321.98 each, about $310 million in cash, a possible second unit issue…
IETF
Lars Eggert and the UDP Datagram That Did Not Escape Shared Costs
UDP gives an application a small transport contract. It does not give it a private network. Lars Eggert's work on RFC 8085 makes that distinction operational: the freedom to choose datagrams leaves congestion responsibility with the traffic that actually shares a path.
North America Institutional Trends
Keurig Dr Pepper’s $925m Chobani Exit Starts with $400m Cash
Keurig Dr Pepper describes its Chobani transactions as producing $925 million of pre-tax proceeds. The filing divides that total into instruments with different clocks: $400 million of cash at closing, a $400 million note due on 26 December and $125 million of asset consideration…
North America Datacenter Trends
Fervo’s 396 MW Google PPA Has a 600 MW Offer Gate
Fervo Energy and Google have signed for 396 MW of enhanced geothermal power from Cape Station. The same contract also requires Fervo to offer roughly 600 MW more—but Google still has to accept, and both sides still have to sign another agreement. That distinction turns a…
IETF
Nandita Dukkipati and the TCP Recovery That Stopped Lurching
A sender can finish loss recovery at exactly the intended congestion window and still have taken the wrong journey there. A long pause followed by a burst and a sequence of small, ACK-clocked releases may move the same number of bytes. They do not place the same strain on a…
North America Datacenter Trends
Applied Optoelectronics’ Two New Factory Leases Sit Behind a US$102.25m Purchase Gate
Applied Optoelectronics has leased two Houston buildings that do not yet exist. The landlord is expected to construct 1.09 million square feet, while the tenant accepts ten years of escalating base rent, most property operating costs and a US$11.3 million deposit. Yet the new…
IETF
Ashesh Mishra and the BFD Check That Had to Be Reversible
The receiver had not accepted the packet. It was merely calculating whether it should. Yet that calculation could erase the only state from which a rejection remained possible.
North America Cloud Services Trends
Personalis Shareholders Vote Before Tempus Chooses the Cash Mix
Personalis shareholders are being asked to authorize a merger whose consideration form may still be unresolved when they vote. Tempus can wait until three business days before closing to replace stock with cash for up to half of the target’s outstanding shares. The exchange ratio…
IETF
Wes Hardaker and the DNS Server That Had to Outlive Two TTLs
The new nameserver was answering perfectly. The old one was quiet. An operator shut it down after the child zone's TTL elapsed—and a minority of users vanished, because their resolvers were still keeping time from the parent.
IETF
Mirja Kühlewind and the QUIC Spin Bit That Measured the Application Period, Not Network RTT
A passive observer saw a clean pulse every 200 milliseconds and labelled the path RTT 200 ms. The packets were real and the arithmetic was correct. The conclusion was not: a sparse application was sending every 200 ms across a much faster path.
IETF
Murray Kucherawy and the DKIM Signature That Left the Tail Unsigned
The verifier returned `dkim=pass`. The message was therefore signed — but not necessarily all of it. One optional number can make both statements true: `l=` tells DKIM to stop hashing after a specified number of canonicalized body octets, while the reader may still see everything…
IETF
John Klensin and the SMTP Reply That Accepted Responsibility, Not Delivery
The sending server sees `250 OK`, removes a message from its queue and calls the transaction complete. That can be correct. Calling the message delivered is not. In SMTP, the final positive reply moves custody to a new operator; the destination still has to be reached, and…
IETF
Tomek Mrugalski and the DHCPv6 Success That Did Not Renew the Lease
A laptop changes networks and asks whether its existing IPv6 addresses still belong on the new link. A server answers `Success`. The tempting conclusion is that the leases are safe. RFC 9915 says something narrower: the addresses fit the link, while every old lifetime keeps…
IETF
Bob Briscoe and the L4S Mark That Did Not Prove Low Latency
An IP packet can carry the L4S identifier all the way across a network even when one operator deliberately sends it through the Classic queue. That is not a contradiction. It is the clue that a packet's declared treatment, its actual queue and its measured delay are three…
IETF
Kent Watsen and the UDP Model That Did Not Record the Running Socket
A management system can hold a perfectly valid UDP endpoint configuration while the machine is listening somewhere else—or nowhere at all. RFC 9984 makes the common vocabulary portable, but it deliberately leaves the runtime testimony to the system that executes it.
IETF
David Schinazi and the UDP Tunnel That Opened Before the Destination Answered
A green CONNECT-UDP response can arrive before the destination has sent a single packet. RFC 9298 makes that apparent paradox precise: the proxy is reporting its own readiness, not certifying a remote application's existence.
IETF
Christopher A. Wood and the Privacy Boundary No One Operator Should Hold
Oblivious HTTP does not ask an operator to forget what it can see. It rearranges the transaction so that one operator can see where a request came from and another can see what the request says—then makes the absence of a single complete view the privacy control.
IETF
Martin Thomson and the Key Log That Could Decrypt a Session but Not Prove It
The incident package looked decisive: a packet capture, a small text file and a screenshot of readable TLS traffic. The decryption had worked. Yet the file did not say who enabled logging, which endpoint produced the secret, when it was collected or whether the alleged session…
IETF
Todd Herr and the DMARC Pass That Did Not Make the Message Safe
The green word `pass` can be perfectly correct and dangerously misunderstood. In DMARC it certifies a narrow relationship between domains. It does not certify the person in the display name, the proposition in the message, the attachment behind the button or the wisdom of putting…