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 CSV Said the Poll Succeeded. The Trap Could No Longer Be Reconstructed.
One row looked complete: timestamp, source, destination, SNMP version, operation, request ID, zero error status and a list of variable bindings. It was compact enough to scan, join and graph. But when the question changed from “how many responses succeeded?” to “what did this…
History
The Name Crossed Protocols. Its Parameters Did Not Move by Themselves: RFC 3555
RFC 3555 did not merely give RTP codecs names that could be printed in another protocol. It specified a custody chain: each piece of a media-type expression had a different destination in SDP, and the payload specification—not the registry—kept authority over what the pieces…
IETF
The Parameter Had an IANA Row. The Call Still Had No Route.
RFC 5341 gives `tel` URI extensions a controlled namespace and a durable reference. That is vital coordination. It is not a runtime receipt for the URI, the number, the network or the call.
History
The Name Was Permanent Because It Refused to Name the Current Value: RFC 3553
A registry can move without forcing every protocol document and implementation to rename what it means. RFC 3553 achieved that continuity by giving the name less authority than people are tempted to read into it.
Leaders
Grace Hopper Turned Portability into a Test—and Credited the Team
A language standard can describe what a compiler should do without showing whether different vendors’ compilers actually do it. When Grace Hopper returned to Navy service in 1967, the problem was no longer only how to write a common language. It was how to test the…
IETF
The Relay Lost One Capability. The Recipient Changed.
An internationalized address entered a mail transaction with an ASCII alternative attached. When a later relay could not carry the original, the experimental downgrade design selected the alternative. The message did not merely change encoding. It could arrive at another…
IETF
The Address Worked Here. On the Next Host, It Named Someone Else.
A legacy program saw an IPv4-shaped value and did what programs have done for decades: cached it, logged it, and handed it to a peer. The value was a HIP Local Scope Identifier. Its meaning ended at the machine that created it.
IETF
A Phone Number Found Two Calendar Doors. It Scheduled Nothing.
One ENUM lookup can return an HTTPS calendar resource and a mail address for scheduling. Both are useful discoveries. Neither says that the caller may enter the calendar, that an invitation reached the intended person, or that a meeting now exists. RFC 5333 is valuable precisely…
IETF
The Multicast EtherType Stopped Meaning “Multicast”
A trace decoder sees Ethernet type `0x8848` and prints “MPLS multicast.” That label looks harmless because it repeats the old registry name. Under RFC 5332, however, the decisive fact is different: on the specified multicast Ethernet path, the top MPLS label was…
IETF
The Header Said Audio. The Container Still Held More Than Sound.
A correct label can still be an incomplete inventory. RFC 5334 designed `audio/ogg`, `video/ogg`, and `application/ogg` around the container’s predominant use, while leaving every logical stream to be identified and processed separately.
IETF
The Count Fell. The LSPs Did Not.
Consider a migration in which one link's advertised unconstrained-TE-LSP count drops from 84 to 51 while every expected tunnel remains in service. Nothing has to be removed for that change to occur. A new originator can stop counting LSPs provisioned through the management…
IETF
The Outer Label Was Removed One Hop Early. The Inner Label Lost Its Table.
Penultimate-hop-popping is normally an efficiency: remove an MPLS tunnel label before the egress so the last router has less work. RFC 5331 identifies the case where that optimization destroys evidence. An upstream-assigned inner label has meaning only inside the label space…
IETF
Every Router Carried the Advertisement. Not Every Router Understood It.
RFC 5329 deliberately lets an OSPFv3 Traffic Engineering LSA cross an area through routers that do not recognize its type. That is a compatibility achievement, not a semantic receipt. The same packet trail can prove excellent flooding and still leave the TE database empty…
History
RMON Could Name MPLS, Not Its Children: RFC 3919
An RMON probe could distinguish two MPLS entry types, yet RFC 3919 stopped short of giving the label stack a universal protocol family tree. The contrast with IPv6 shows where an identifier can travel—and where its meaning must stop.
IETF
The Name Survived. One Resolver Path Did Not.
RFC 5328 gave DVB metadata a persistent, location-independent name. It did not make that name a live route, an authenticated entity or proof that a receiver used the resource. A `urn:dvb` string can remain valid while one discovery path fails, another returns a new locator and a…
IETF
The Retransmission Was Byte-Perfect. Its Cookie Was Already Obsolete.
RFC 5327 gives an LTP session a security state that can change while a signal is still crossing the link. A cookie may grow after the original segment leaves, and a retransmission must carry the value current now, not the value that was correct then. Authentication can protect…
History
One Tagged Frame, Many Multicast Clocks
In a multicast test, one packet leaves one ingress and arrives at many exits. RFC 3918’s key measurement choice was to keep those arrivals separate: a headline latency number could not tell an operator which branch had paid the delay.
IETF
The Sender Finished the Session. The Green Bytes Were Never Confirmed.
RFC 5326 designed a transport for links where a reply might take minutes, interruptions are scheduled and retransmission capacity is expensive. Its completion notice is exact: every byte was transmitted, and the receiver reported the reliable red prefix. It does not say the…
IETF
The Policy Row Existed. The Fabric Had Not Activated It.
RFC 5324 gives an operator a large management surface for Fibre Channel security: editable policy entities, activation controls, negotiated Security Association pairs, traffic selectors, counters and bounded event history. Those records describe different stages. A configured row…
History
DHCP Gave Vendors Separate Option Spaces, Not IANA-Defined Meanings
In 2004, DHCPv4 gained a way to place several vendors’ configuration data in one exchange without pretending that a shared packet made their private option vocabularies the same. RFC 3925 widened the envelope; it did not standardize everything inside it.