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.
History
RFC 2067: The Standard Deleted Three Legal Packet Shapes
In 1997, Internet engineers advanced IP over HIPPI by making the specification smaller. Three packet forms allowed by RFC 1374 disappeared: a short burst could no longer come first, the D1 area could no longer contain fill, and the D2 offset could no longer be nonzero. RFC 2067…
IETF
A DTLS Return-Routability Probe Is Not a Migration Receipt
A protected datagram arrives with the right Connection ID and a new source address. The cryptography can locate an existing DTLS security context, yet the receiver still has a separate decision to make: whether to move that context, release application output to the new address…
History
Ward Christensen and the 128-Byte Agreement That Left the Ends Free
XMODEM became useful by declining to become a platform. Ward Christensen put a small, deterministic agreement on the line, then left almost every other decision—dialling, storage, filenames, interface and improvement—to the computers and people at either end.
IETF
The Orbit Said the Link Was Ready. The Network Had Not Agreed
RFC 9717 turns orbital predictability into a routing advantage without confusing a forecast with an observation. Its proposed satellite architecture can prepare for scheduled change, but a schedule, a computed SID list and even a successful install receipt remain different claims…
History
RFC 2066: The Character Set Was Already Right. The Reply Still Had to Arrive
Telnet had a rule for avoiding endless politeness: do not acknowledge a request for a mode already in effect. RFC 2066 made a narrow but consequential exception. A receiver already using one of the proposed character sets still had to send `ACCEPTED`, because silence would force…
North America Cloud Services Trends
Payoneer won the vote. Its shares still have not become $7.40 cash
The 224.99 million affirmative votes removed one branch of the Payoneer–Nuvei merger’s decision tree. They did not trigger the legal event that converts eligible shares into cash, settle the disclosure litigation or make the remaining regulatory perimeter disappear.
History
RFC 2065: The DNS Reply Crossed an Ordinary Server. Its Signature Carried the Trust
In January 1997, RFC 2065 proposed a security upgrade that did not require every machine carrying a DNS answer to become its judge. A security-aware resolver could retrieve signed records through a server that knew little about the new machinery and verify the evidence itself.…
IETF
A TLS CertificateRequest Context Correlates a Response, Not an Authorization Scope
An opaque value can tell a TLS server which certificate request a client answered. It cannot tell an application what the authenticated key may do. When a correlation handle is promoted into a tenant, role or access boundary, precise cryptographic sequencing becomes an accidental…
History
Dina Katabi and the Feedback Field That Was Not a Bandwidth Grant
A packet leaves its sender asking to increase the flow by a certain amount. The first router accepts the request; the second writes a smaller number; the receiver sends that surviving value back. XCP turned congestion control into an explicit negotiation, but the number in its…
North America Cloud Services Trends
Ooma's US$65m loan almost matches the cash-adjusted acquisition price
Ooma announced two cloud-communications acquisitions at headline prices that add to US$68.2 million. The final purchase-price allocations tell a different and more useful story: US$73.186 million of consideration, including US$8.563 million of cash acquired, leaves US$64.623…
Global Cloud Services Trends
Zscaler’s acquisition-adjusted growth uses three different perimeters
Zscaler reported 25% growth in both revenue and annual recurring revenue for fiscal 2026, then offered a 20% comparison that removed Red Canary. Elsewhere, its accounts valued four acquisitions and its year-end controls report excluded all four from testing. The figures are not…
Global Cloud Services Trends
SentinelOne’s Flex milestone needs a consumption bridge
SentinelOne says its Flex commercial model now accounts for more than 10% of annualised recurring revenue. That is a meaningful threshold inside a business with US$1.218 billion of ARR and US$1.7 billion of remaining performance obligations. Yet the filing also says revenue from…
Global Cloud Services Trends
Workiva’s large-contract growth has an acquisition clock inside it
Workiva’s largest customer tiers are expanding much faster than its total customer count. That looks like a clean enterprise-upmarket story until one sentence in the filing changes the perimeter: customers acquired with Sustain.Life enter the customer count and…
CASE FILE
One Color Crossed Three ASes. It Never Became an SLA: RFC 9723
A low-latency color can survive every BGP hop and still fail to buy low latency. RFC 9723 gives SRv6 operators a compact way to propagate intent through colored locator prefixes; it does not merge the intent dictionary, route installation, packet path and customer outcome into…
Global Cloud Services Trends
Expensify’s card growth fails the two-rebate test
Expensify’s headline card number looks uncomplicated: interchange revenue rose 12% in the second quarter of 2026. The income statement tells a more demanding story. Customer cashback grew faster and reduced revenue, while a Visa volume incentive that reduces cost of revenue fell…
History
Stephen Casner and the Timestamp That Was Not a Clock
Two packets leave in sequence and carry the same timestamp. That looks like a broken clock only if the number is asked to describe transmission. In RTP, the two packets may simply be fragments of one video frame. Stephen Casner and his coauthors made that distinction part of the…
IETF
TLS close_notify Ends a Sending Stream, Not an Application Transaction
An orderly TLS ending can arrive after the last encrypted bytes and still say nothing about whether an invoice was booked, an order was accepted or a database committed. `close_notify` closes a cryptographic sending direction. Treating it as a business receipt makes a transport…
Global Cloud Services Trends
Klaviyo’s Shopify toll sits below gross margin
Klaviyo reported a 72.6% gross margin in the second quarter of 2026. That number describes what remained after the costs classified as delivering its service. It does not include a separately disclosed toll attached to one of the most important routes into that service. Shopify…
History
Sharon Goldberg and the Packet That Told a Clock to Stop Asking
The dangerous packet was not large, fast or obviously hostile. It looked like a time server asking a client to back away. In the `ntpd` versions studied by Sharon Goldberg and three collaborators, that courtesy message could be forged—and its requested silence could last far…
Global Cloud Services Trends
SailPoint’s AI ARR needs a renewal-status column
SailPoint has put a number on its new AI business: more than US$70 million of annual recurring revenue. The number is useful precisely because it is not yet a revenue line. Its definition can keep a contract in the count after expiry while a renewal or replacement deal is still…