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
Reusable Blocks Could Still Fail Together: RFC 3269
Reliable multicast needed more than reusable pieces. RFC 3269 required each RMT building block to state its boundaries and dependencies, then made a complete protocol explain how those pieces fit.
History
The Address Plan Was 87% Full While Most Addresses Were Still Empty: RFC 3194
RFC 3194 put a percentage on the pain of hierarchical addressing. The result looked familiar and meant something unusual: an IPv4-sized plan at 87% Host Density held about 240 million entities, not 87% of 4.3 billion addresses. The metric compared scaling pressure across…
IETF
The App Kept the User Out of the Browser. It Also Entered the Trust Boundary.
OAuth’s proposed Authorization Challenge Endpoint can keep a native first-party journey inside the app. The saved context switch is real. So is the transfer of credential prompts, session continuity and risk routing into a client whose provenance, presentation and installed…
IETF
The Delegation Counter Reached Zero. The Sensing Policy Could Still Have Been Lost.
A depth counter can stop the next handoff while saying nothing about what happened to the rules carried through the earlier ones. In agentic sensing, a finite graph is not yet a compliant chain of authority.
History
The Telephone Number Was Not an Email Address Until the Gateway Owned the Right-Hand Side: RFC 3191
The string to the left of the at-sign looked like a telephone instruction. That did not give every mail server the right to dial it. RFC 3191 made the domain on the right choose the gateway that could interpret the number, the service and the qualifiers—and left delivery beyond…
IETF
The Origin Published a Knowledge Map. It Did Not Authorise the Agent to Obey It.
An agent can discover a file, verify its bytes and still have no permission to act on a sentence inside it. The proposed `knowledge-linkset` well-known URI makes that distinction operationally urgent rather than philosophical.
History
The Minimum Sample Was Audio on the Network and an Error on the Tape: RFC 3190
The number at the bottom of the waveform had two incompatible jobs. RTP treated it as an ordinary sample. A DV deck treated it as notice that no sample had survived. RFC 3190 made the bridge choose which meaning would cross.
IETF
The Capsule Recorded a Disagreement. It Had No Right to Block Anything.
A new SCITT profile proposes an immutable third-party comparison between what a subject declared and what an observer found. Its most important design choice is not the hash or the Merkle tree, but the refusal to let measurement quietly become authority.
IETF
The Tool Knew the SID. It Still Did Not Own the Actuator.
CORECONF-M2M proposes a compact route from YANG models and SID identifiers to MCP tools that an AI agent can call. The route can remove bespoke serialization without removing the harder boundary: who may act, what the device accepted and whether the physical world actually…
History
The Country Prefix Found the Resolver. It Did Not Prove the Archive Kept the Object: RFC 3188
The prefix `fi` could tell a client where Finland's branch of the NBN world began. It could not make a harvested Web page survive, authenticate the service answering today, or prove that the returned file was the original. RFC 3188 made a federation of local library numbers…
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…