Profile
Research
Research profile intelligence connects person, company, institution, and other entity coverage for readers comparing the subjects behind BTW.MEDIA reporting. The page helps compare public profiles, related events, evidence packs, role changes, operating footprints, governance exposure, organisational links, and market relevance while keeping organisation and people records distinct from ordinary news chronology. Readers can understand the subject behind the headline, the evidence supporting that profile, and the infrastructure or market relationships that make the profile relevant. They can see who or what the profile represents, which public sources support it, how it connects to companies, markets, governance bodies, or events, and what changes may deserve continued attention as the subject evolves.
History
The Root Was a Coordination Shortcut, Not a World Directory: RFC 2120
X.500 drew a clean Directory Information Tree, but its root carried an awkward human obligation. Every administrator of a first-level Directory System Agent was expected to coordinate with every other one through bilateral agreements or private arrangements outside the standard.…
History
Adele Goldberg and the Contract That Let Smalltalk-80 Travel
The Blue Book turned a live system into a portable agreement: preserve the image, implement the entity memory, bytecodes, contexts and primitives, and let unlike machines run the same Smalltalk-80. The agreement made reimplementation possible; it never promised equal speed…
History
The Join Had No Receipt. The Tree Survived by Refresh: RFC 2117
RFC 2117 did not build a sparse multicast tree as one transaction. A local membership indication created one record; a Join/Prune refreshed records hop by hop; a source initially reached a rendezvous point inside Register messages; a branch could later move to source-specific…
IETF
RFC 9787 and the Moment a Draft Becomes a Message: Encryption, Commitment and Cross-Device Custody
A protected email draft is not merely an early copy of a sent message. RFC 9787 treats it as a different authority state: unfinished text may need confidentiality from the mailbox service while remaining unreadable to intended recipients and unendorsed by the user's ordinary…
CASE FILE
Internet Society Approved Its 2026–2027 Election Clock. Now It Needs an Activation Record
On 14 September, Internet Society’s Board completed two acts in one written resolution: it added four people to the committees supervising the next trustee-selection cycle, and it approved that cycle’s timetable “as attached”. The corporate decision is visible. The exact public…
History
The MIB Located the Address. The Repeater Still Had No MAC
A management station could ask which hub port had carried a source address, rank the busiest ports and reconstruct a shared-Ethernet topology. RFC 2108 made those answers comparable without pretending that the repeater itself understood a packet.
History
Kathleen Booth and the Line Between a Symbol and a Machine Order
In 1947, Kathleen Britten and Andrew Booth described a way to move from a mathematical plan to the exact fields their calculator would obey. The abbreviated notation made that crossing legible. It did not make the machine understand what the calculation meant.
CASE FILE
W3C’s LLM Note Assigns Personal Responsibility—but Not an Accountability Process
The W3C Advisory Board’s new note contains a strong sentence: each person remains responsible for work they share, whether or not a large language model helped produce it. The status paragraph contains an equally important limit. The document is an Advisory Board Group Note…
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…