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
The Address Said Home. The Dial-Up Line Said Away: RFC 2107
RFC 2107 let a remote dial-in client borrow the routing appearance of home. The illusion depended on a Foreign Agent, a Home Agent, a shared secret, a Tunnel ID and state that had to be created and destroyed in the right order.
History
The Router Gave the Workstation an Address. It Did Not Give It an Identity: RFC 2106
RFC 2106 solved a real scaling problem by placing many remote SNA and NetBIOS workstations behind one DRAP server. The bargain was precise: fewer backbone peers, more state and judgment concentrated at the boundary.
History
The Tag Moved the Packet. It Did Not Prove the Path: RFC 2105
A packet entered a switch carrying a short tag. The machine used that value as an exact index, selected an interface, replaced the tag and sent the packet onward. That was the elegant part of Cisco’s 1997 Tag Switching proposal. The harder truth sat elsewhere: routing protocols…
IETF
When Fast Reroute Must Stop: RFC 9791 and the Responsibility Boundary Behind NFFRR
RFC 9791 gives a deceptively simple answer to a hard failure problem: once fast reroute has already redirected a packet, a downstream node may need to refuse another local repair. The difficult part is not the idea of a marker. It is the authority embedded in that marker—the…
CASE FILE
The Grammar Changed. Your Acceptance Boundary Might Not.
RFC 9682 repairs CDDL’s collected grammar and adds a cleaner hexadecimal escape form, but the important compatibility boundary is not the publication date of the RFC. It is the point at which a particular source model meets a particular parser, becomes a particular validator…
History
Two Hash Passes Made a Reusable MAC. The Tag Did Not Make a Trust Decision: RFC 2104
RFC 2104 gave protocol designers a compact way to turn existing iterative hash functions into a message authentication code: one keyed inner pass, one differently keyed outer pass, and an interface that could survive replacement of the hash beneath it. What endured was the…
IETF
When “Lease” Stops Meaning “Address Assigned”
An operator upgrades a DHCPv6 inventory schema and discovers that one familiar dashboard label—“lease”—now conceals two different origins of authority. In one record, the server selected or delegated the resource. In another, the device selected a SLAAC or static address and…
History
The Link Was Open. Each Name Still Needed Admission: RFC 2097
PPP could bring a remote machine to the edge of a NetBIOS Frames network, but RFC 2097 did not treat link-up as reachability. Before NBF traffic flowed, NBFCP let the remote side ask a peer to project particular sixteen-octet names, return a result for every name, identify its…
History
The Counter Passed One Receiver’s Window. It Did Not Name the Sender: RFC 2085
RFC 2085 placed a 64-bit replay counter inside one HMAC-MD5 Authentication Header transform, but only when the Security Association selected it. A receiver could admit unseen packets within its own reordering window and reject a repeated value. That was useful freshness evidence…
History
The Fourth Letter Decided What the Editor Could Keep: RFC 2083
An editor can change every pixel in a PNG and still face a question that no preview answers: what should happen to a chunk it does not understand? RFC 2083 put part of that decision into the capitalization of four bytes. The last letter governed copying after edits, while the…
History
The Directory Stored Two Links. It Could Not Tell You What Either Meant: RFC 2079
A directory entry could carry two impeccable-looking links: one labelled “official record,” another “current service.” RFC 2079 made both values easy to store and split into URI and label. It did not tell a client whether the links described two resources, two locations for one…
History
The Header Existed. Its Jurisdiction Did Not Follow: RFC 2076
A mail parser could prove that a line named `Apparently-To` was present. It could not prove that the field was a standard Internet-mail instruction, that it was safe to expose, or that any receiver should act on it. RFC 2076 made that gap visible by cataloguing familiar message…
ICANN
The autistici.org Hold Has a Timestamp but No Public Decision Receipt
PIR’s RDAP service records exactly when `autistici.org` changed and which registry controls remain applied. It cannot tell the public who connected a US sanctions designation to that domain-wide action, which rule governed the choice, why it happened before a wind-down licence…
IETF
RFC 9806 Corrects the Label, Not the Deployment
The standards record now has a clear name for SIPREC recording metadata: `application/rs-metadata+xml`. That clarity joins an original metadata RFC, a contradictory protocol RFC, an erratum, a later update and an IANA entry. It still leaves operators to prove whether the…
IETF
The Card Passed Two Profiles. The Protocol Still Had a Question: RFC 10050
A profile can prove that a JSContact card belongs to a named, versioned subset. It cannot prove that a protocol should accept the card, or even tell a receiver which profile the sender intended. RFC 10050 makes that boundary explicit and turns profile identity, recursive property…
IETF
The Backup Was Valid. The Signature State Was Not: RFC 10033
A stateful hash-based signing key is not merely secret material in storage. It is also a changing account of one-time keys already exposed to the world. RFC 10033 makes that operational distinction unavoidable: restoring an authentic but older copy can recover the right key while…
History
Barbara Liskov and the Argus Commit That Stopped at the Guardian Boundary
Argus made failure a language-level concern: guardians owned recoverable entities, handlers crossed machine boundaries, and actions could commit or abort a distributed change. Its strongest lesson is also its limit. A committed action settled the participating Argus state; it did…
IETF
An AEGIS Codepoint Is Not a Negotiation Receipt
RFC 10032 gives six AEGIS variants stable AEAD identifiers. It does not show that two peers offered the same suite, chose the same tag length, executed the intended implementation path or protected a single live packet with it. The missing record sits between specification…
History
Anita Borg and the Systers List: Admission to a Governed Room, Not Proof of Equality
A message could enter Systers because a member, an address and the list's routing rules admitted it to a private professional room. That delivery made scattered women in computing less isolated; it did not verify every identity claim, guarantee a career opportunity, erase…
IETF
A DHCP Lease Is Not a Relay-Topology Receipt
RFC 9928 lets an intermediate relay speak DHCPv4-over-DHCPv6 for a legacy IPv4 client that knows nothing about the conversion. The lease can be valid while the evidence connecting the request to its physical access port is incomplete. The missing entity is not another success…