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
Raj Jain and the One Bit That Needed Two Time Filters
DECbit is remembered as a one-bit congestion signal. The more consequential idea was the timing around it: routers and endpoints each had to decide what a stream of momentary observations meant before anyone changed the traffic load.
IETF
Requesting an HTTP Digest Does Not Create an Integrity Contract
An HTTP client can state exactly which digest algorithms it would prefer and still receive a response with another algorithm—or no digest at all. RFC9530 makes that latitude deliberate. Operational integrity begins only after the recipient inspects what actually arrived…
IETF
A TLS Certificate Can Fit the Handshake and Overfill the HTTP Request
A reverse proxy can accept a client's certificate, then produce a request its backend cannot accommodate. RFC9440 makes that otherwise obscure transition visible: certificate data becomes HTTP fields, and the receiving capacity belongs to a different budget. Neither a successful…
History
Larry Masinter and the form that arrived in pieces
The history of multipart/form-data reveals a quiet source of software risk: a request can reach its destination intact while the application loses the distinctions it carried.
History
Scott Shenker and the decision before a flow begins
Ethane and NOX made enterprise networking answer a question that routing alone cannot settle: who may start this connection, and which path makes that permission real?
IETF
A New OAuth Token Does Not Prove Recent Authentication
Issuing a credential and authenticating its user are different events. RFC9470 makes the distinction operational: a resource can ask for stronger or more recent authentication, but neither a fresh token nor a successfully relayed challenge proves that the condition has been met.
IETF
Equivalent URNs Are Not Interchangeable Service Requests
A comparison can correctly say that two URN names identify the same resource without saying that every service request carrying those names is interchangeable. RFC8141 draws that boundary through optional components—and leaves an important existing-query case to the resolver's…
IETF
Changing a SIP Push Reference Must Not Abandon the Dialog
A private reference can become less useful for tracking without becoming less useful to an existing conversation. SIP push notification makes that distinction explicit: a proxy must issue fresh references, yet keep the old ones that ongoing dialogs still depend on.
IETF
A CDN Customer May Choose the Route—Not Erase Its Loop Guard
The small CDN-Loop request field draws an unusually sharp boundary: customers retain routing choices, but not the ability to erase a common safety mechanism. That boundary protects cooperation without making the field a trustworthy account of where a request has been.
IETF
The CDNI Map That Grew—and Lost Every Client
A CDNI advertisement can name more address ranges and leave fewer requests eligible. The explanation lies in how restrictions are combined—and in the decision rights that a clean-looking coverage map can quietly absorb.
IETF
CDNI’s Complete Collection Is Not an All-Success Receipt
A publisher preparing replacement content needs to know that an earlier purge has finished. A tidy reporting collection can answer a different question: whether another status update will arrive. CDNI keeps those meanings separate, and the next release decision must do the same.
IETF
CDNI Redirection Must Not Restart the Token’s Expiry Clock
A delivery network may change the next recipient, sign a new route and record a new issuance time. Under the CDNI URI Signing profile, none of those changes gives ordinary redirection permission to reset an existing expiry. Segment-token renewal is a different, explicitly enabled…
History
RFC 2063: The missing minutes inside a recovered total
When a reader stops while its meter keeps running, accumulated traffic may remain recoverable. The missing collections still leave a hole in the history of when that traffic passed.
History
Urs Hölzle and the Fabric That Learned to Change in Pieces
An awkward failure in an early Google network helps explain a less visible infrastructure achievement: making a vast switching system serviceable without treating it as one indivisible machine.
IETF
No-Vary-Search Needs an Activation Boundary for Client-Side Decisions
Two URLs can justify reusing the same server response while still representing different choices by a reader. When a prerendered page is activated under a different query, the application must bind its decisions to that final choice—not to the address it happened to inspect…
History
Ermanno Pietrosemoli and the Sea Link Whose Peak Was Not a Promise
In a picture used to teach long-distance wireless planning, the equipment has been running for days but the link counter has been running for minutes. Both numbers can be true. Ermanno Pietrosemoli's work on a remarkable radio crossing between Sardinia and Tuscany makes that…
North America Cloud Services Trends
C3 AI’s Supplier Savings Need an Obligation Bridge
C3 AI has reduced the cost incurred under its supplier arrangements. Its future purchase commitments have also fallen, by a different amount. Reading both movements as the same saving would miss the contractual question at the heart of the turnaround: what was consumed, what was…
IETF
An Expired Idempotency Key Is Not Permission to Repeat an Effect
A retry cache can forget a request while the request’s consequences remain. The expiry of that memory is an operational boundary, not fresh authority to create the same resource, issue the same instruction or commit the same business effect again.
History
Budi Rahardjo and the Incident Desk That Could Ask, but Not Order
An incident email can reach the right person without giving that person the right to change a server. Budi Rahardjo's contribution to Indonesia's Internet security was to build a place where that distinction could be made useful: a trusted coordination desk that routes evidence…
North America Institutional Trends
Corning’s Equity-Sale Stop Button Does Not Erase the Settlement Queue
A phone call can suspend new sales under Corning’s US$2 billion equity programme. It does not give the company a general right to recall trades already made. That distinction turns a flexible financing headline into a more demanding operating question: which shares remain merely…