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.
IETF
The Receiver Acknowledged the Frame Before It Had Finished Decoding It
A one-bit acknowledgement can make video recovery faster by telling the sender what the receiver is prepared to use. Its value comes from arriving early. That is also why it cannot serve as a receipt for completed decode, retained reference state, rendering or viewer outcome.
History
The Random Key Wasn't a Recovery Key. It Was a Way to Keep Failure Silent: RFC 3218
An encrypted message could fail before its content was even touched. That sounded like useful diagnostic precision until the difference became a service an attacker could query. RFC 3218 answered with an unsettling discipline: when RSA key transport failed, invent a fresh random…
History
The RFC That Tried to Unbox the URL: RFC 3305
The Web’s identifiers once seemed to belong in separate boxes: a URL told you where to go; a URN told you what something was. RFC 3305, a 2002 report from a joint W3C/IETF planning group, argued that this tidy split was getting in the way of the schemes themselves.
IETF
The Accounting Record Said the Group Was Enforced. The Packet Had Not Testified.
A NAS can report that it received a Group ID and is enforcing its policy. That is useful evidence. It is not the same as proving which mapping every enforcement point used, which rule was active, or what happened to the packet.
History
The Confirmation Said the NAK Was Heard. It Did Not Say the Repair Arrived: RFC 3208
PGM made reliable multicast scale by refusing to collect a success receipt from every receiver. A missing packet produced a negative acknowledgement; a router confirmed that request hop by hop; repair state selected the branches that should receive retransmission. But the…
History
A Billion Users Still Left Most People Out: RFC 3271
In 2002, Vint Cerf projected more than a billion Internet users by the end of 2005—and immediately noted that this would still mean only about 16% of the world's population. That contrast turns “the Internet is for everyone” from a victory slogan into a test with many separate…
IETF
They Both Said “Peer.” One Meant a Relationship; the Other Meant a Session.
A shared word let two teams finish the meeting quickly. It also let each leave with a different export policy in mind. In routing operations, vocabulary is coordination evidence, not a substitute for the predicates that make an action safe.
History
IPsec Authenticated Every Packet, but Not Necessarily the User Inside the Tunnel: RFC 3193
RFC 3193 secured L2TP by making two protocols share facts without pretending they were one protocol. L2TP knew which tunnel and socket it was building; IPsec knew which address, port and identity its Security Association covered. Their coordination protected every packet, yet the…
IETF
The Stream Sped Up. The Reason Could Not Be Replayed.
An adaptive YANG-Push subscription can move from a quiet reporting interval to a rapid one when an XPath condition becomes true. The connected receiver gets a mandatory state-change notice. A receiver that reconnects later cannot ask the replay buffer for that notice. The data…
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…