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
An HTTP Library Was Not an Interoperability Plan: RFC 3205
In 2002, protocol designers were tempted to borrow HTTP for its installed base: browsers, server code, security machinery and access through existing network boundaries. RFC 3205 did not reject that bargain. It asked designers to account for the assumptions that came with…
History
The ISBN Named an Edition. It Could Resolve to Many Copies—or the Wrong Book: RFC 3187
A persistent name was supposed to survive changing locations. RFC 3187 made the bargain concrete and awkward: one ISBN URN might lead to many URLs, no digital entity at all, or two bibliographic records because a publisher had reused a number by mistake. Persistence belonged to…
IETF
The Agent Went Silent. The Trust Score Punished What the Verifier Could Not See.
The proposed Network Behavioral Trust Protocol turns missing heartbeats and co-silence into score decay, SUSPECT and QUARANTINED states. That may be useful operationally, but an absence first describes a verifier's observation surface—not an agent's character.
History
RFC 1180 Explained TCP/IP, Then Sent Readers Back to the Standards
In January 1991, T.J. Socolofsky and C.J. Kale offered network professionals a practical way to follow an IP datagram from one host, through a router, to another. They also drew a bright line: the memo explained TCP/IP; it did not define it.
History
The Customer Saw a Private Wire. The Operator Held the Hidden Address Pair: RFC 3186
At one edge, customer equipment emitted an ordinary PPP frame. At the other, customer equipment received one. Between them, switches replaced the frame’s first octets, forwarded it through a shared MAPOS fabric, restored the original values and withheld the machinery from view.…
History
The Recipient List Shrunk. The Old Key Still Opened the Message: RFC 3185
The second encrypted message named fewer recipients than the first. One omitted member could still open it. Nothing had malfunctioned: RFC 3185 warned that this was the expected consequence of deriving a later key-encryption key from content-key material already delivered to the…
IETF
The Key Changed. The Instance Stayed the Same Because Someone Kept the Ledger.
OAuth attestation can prove that a client instance holds a current key. A new profile tries to preserve that instance's identity when the key changes. The continuity does not live in the identifier string: it lives in an attester's enrollment records, lifecycle rules and custody…
History
The Domain Signed the Message. The Individual Was Still Unnamed: RFC 3183
A recipient could verify that a message had crossed an authenticated organizational boundary and still be unable to display the name of the person who sent it. RFC 3183 made that distinction unusually explicit. Its domain-security machinery did not offer one generic act called…
History
The Firewall Was Allowed to Say No. It Wasn't Supposed to Break the Conversation: RFC 2979
In October 2000, an Informational RFC drew a line that packet filters often blurred: a site could refuse traffic for security reasons, but a firewall should not accidentally make legitimate, standards-compliant communication fail. That distinction assigned the repair bill to the…
IETF
The ICV Was Valid. The Path Record Could Still Be False.
IOAM can carry a cumulative integrity chain across the network and let a Validator confirm that protected fields were not modified. That is valuable evidence. It is not the same as proving that every expected record arrived, every participating node told the truth, or the…
History
The Name Entered RSVP. Authority Still Had to Decide What It Meant: RFC 3182
In 2001, an RSVP request could carry a user name, an application name, a Kerberos ticket or a certificate toward the router deciding whether a flow deserved scarce resources. That sounds like identity becoming authority. RFC 3182 documented something more conditional. The name…
History
A Secure Peer Link Could Still Carry an Untrusted MASC Claim: RFC 2909
MASC divided multicast address space into temporary, nested claims. Its 2000 security section identified a harder boundary: protecting the next peer did not make every relayed update trustworthy.
IETF
The Controller Reported Both Directions Done. The Network Had Not Proved Hitless
Fine-grain optical transport can change a low-rate service’s bandwidth without a planned interruption. Yet the green completion event at the multi-domain coordinator is only one controller’s conclusion. It is not a receipt for every direction, domain, protection path, tributary…
North America Datacenter Trends
96 megawatts, two ledgers: what Georgia’s Google nuclear deal still has to prove
Georgia Power says Google’s subscription to a proposed nuclear-uprate tariff could produce about $900 million in customer benefits. The agreement separates an environmental claim from grid capacity—but the public record does not yet show the tariff’s price, risk allocation or…
History
The New Flow Won Admission. Its Defending Priority Still Had to Survive the Next Arrival: RFC 3181
A flow could arrive late and still displace an earlier reservation. RFC 3181 made that reversal deliberate, but it did not give one number permanent authority. The new flow competed with a preemption priority; after admission, another value became its defence against the next…
Story
APNIC Ties an Eight-Service Outage to a Misplaced Load-Balancer Drain
APNIC says a maintenance step intended for one load-balancer node was run against the other, causing an outage across eight listed services. The notice calls it 15 minutes, although its displayed start and end times are 17 minutes apart.
History
One AS, 256 Multicast Addresses—and a Four-Byte Limit
GLOP made a static multicast block calculable from an existing network number: useful when groups had to stay put, but only as flexible as the two-byte AS field it borrowed.
IETF
The Batch Proof Passed. How Many Privacy Pass Tokens Did You Actually Get?
Batched Privacy Pass issuance can cut proof overhead and round trips, but it also creates a new place for operational truth to disappear. One verified proof or one successful HTTP response is not yet a receipt for the number of tokens that survived finalization, entered durable…
History
The Runtime Replied 231. The Script Still Owed a Termination Receipt: RFC 3179
A control system can answer correctly before the work is done. RFC 3179 made that temporal gap explicit: one reply said a management script had reached a runtime state, other messages carried intermediate output or errors, and a later reply marked termination. None of them alone…
IETF
The ACME Order Named a Profile. The Certificate Still Had to Prove It.
ACME Profiles gives certificate authorities a cleaner way to expose policy choices and lets clients bind one choice to an Order. The new string is useful coordination, but leaders should resist turning it into a compliance badge: the issued certificate, its deployment and the…