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 Page Looked Final. The File Was Not: RFC 5385
An executive opens a document, checks that every heading, page break and reference looks right, and approves what appears on screen. RFC 5385 shows why that moment is useful but incomplete: the visible page was an authoring view, while compliant output still depended on styles, a…
IETF
No Complaints Is Not a Multicast Delivery Receipt
A software publisher sent one release to thousands of receivers. The transfer curve flattened, the repair channel went quiet, and the control room marked the campaign complete. That last step turned a useful transport observation into a claim the protocol had never made: in a…
History
The Identifier Became Readable. Its Original Form Still Had to Survive: RFC 3987
A reader could finally see an Internet address in familiar script. The operational problem began when a cache, clipboard, resolver and audit log each decided that “the same” address meant a different transformation.
History
The Schedule Had a Call Sign. The RFC Did Not Prove It Went on Air: KRFC 1313
An April 1992 RFC stages a Bay Area talk-radio station for the Internet crowd, complete with a schedule, sponsors, guests and ways to listen. Its best historical evidence may be the memo itself—not the broadcast it describes.
IETF
The Lowest Address Won. That Did Not Make It Right: RFC 5384
Two downstream routers ask for incompatible treatment of the same multicast tree. The upstream router cannot preserve both requests, so RFC 5384 gives it a deterministic answer: use the attribute supplied by the adjacency with the numerically smallest IP address. The network can…
History
The Network Carried the Wire’s Essentials, Not the Wire Itself: RFC 3985
A buyer can sign for an “Ethernet circuit” and still leave the decisive term undefined: which attributes must survive for the packet-network emulation to count as the service that was ordered?
IETF
The Example ASN Passed Syntax Checks. It Still Was Not a Network Identity
The Example ASN Passed Syntax Checks. It Still Was Not a Network Identity intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may…
History
The Management Bridge Was Not a Compatibility Promise: RFC 1285
In January 1992, RFC 1285 tried to make FDDI station management legible to SNMP without changing what its entities meant. Twenty months later, RFC 1512 warned that a revised ANSI model had moved the entities to a different MIB branch and that compatibility with RFC 1285 must not…
Creators
Susan Kare and the File Behind the Icon
MoMA’s collection includes Susan Kare’s 1982 Macintosh icon sketchbook; a later account of the archive she brought to museums describes more than 300 floppy disks of born-digital work. The paper page and the disk are not two copies of one thing. Together, they show why a digital…
History
The Picture Packets Arrived. The Decoder Rules Had Their Own Timeline: RFC 3984
An immaculate RTP trace can account for every picture packet and still fail to explain a black decoder, because the missing evidence may be the state that told the decoder what those packets meant.
IETF
The Message Reached a Server. It Was Not the Server the User Chose: RFC 5383
A traveller presses Send from a hotel room. The mail client reports a clean TCP connection, the server speaks SMTP, and nothing on the screen says that the hotel has replaced the destination. RFC 5383 preserved this uncomfortable case: network reachability can succeed precisely…
IETF
The Server Found Your Principal. It Still Had Not Authorized the Work
The login succeeded. A WebDAV request returned a URL that represented the current user. The client followed it, painted the account green and attempted a write. The write was denied. Nothing in that sequence contradicted RFC 5397. The standard solved a narrower problem: how a…
History
The Standards List Had an Expiry Date: RFC 1280
In March 1992, the Internet Activities Board published a map of protocol status with an instruction rarely associated with a standards document: do not use this edition after 31 July. RFC 1280 was authoritative enough to coordinate decisions, but temporary enough to require a…
Asia-Pacific Cloud Services Trends
One Mailbox, Two Companies, One Address: What Reproduced APNIC Whois Text Shows About NEXGENET COMPANY LIMITED's Accountability Surface
NEXGENET COMPANY LIMITED looks, from a distance, like an ordinary small internet provider in Yangon. Look directly at the registry records that define who answers for its networks, and the picture becomes more complicated: one generic role entity named "NEXGENET COMPANY LIMITED…
IETF
The Port Was Saved. The Session Identity Was Spent: RFC 5382
A translator can make an excellent capacity graph by lending the same public address and port to more than one internal endpoint. The graph turns red only when two of those endpoints call the same server. Then the hidden distinction disappears, and an apparent efficiency becomes…
History
An Empty Field Was Not One Thing. RFC 3982 Made Absence Part of the Protocol
When a registry export turns every unavailable value into an empty cell, it destroys the most consequential fact about that cell: whether the datum never existed, could never be published, was withheld from this requester, or had been disclosed under conditions the export…
History
An OSI Address Had to Carry More Than a Route: RFC 1277
In 1991, OSI applications were already being tried over TCP/IP and X.25 networks that did not offer the OSI Network Service. RFC 1277 put the missing lower-layer clues inside an address the directory could already return. That made a connection attempt possible without making the…
IETF
The Empty Registry Row Was Not Permission to Use It
An engineer opens the DNS parameter table and finds a number marked unassigned. The field accepts it. A laboratory server answers it. A packet trace shows the value crossing the network. None of those facts says the Internet has granted that number a stable public meaning. RFC…
History
The Channel Was Ready. Identity Was Still a Separate Question: RFC 3983
RFC 3983 gave IRIS a precise moment when a negotiated BEEP channel became “ready.” That word described message capability, not a completed trust decision. Server identity, user authentication, encryption, query authorization and the registry result still had separate owners and…
History
A Packet's Endpoints Could Not Name the Network in Between: RFC 1272
In 1991, an Internet provider could see a packet’s source and destination without learning which neighboring administration had carried it across a boundary. RFC 1272 made that gap the central problem for network accounting: to reconcile use between providers, the meter had to…