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 URI Chose the Voicemail Menu. It Did Not Authenticate the Caller: RFC 3087
In 2001, SIP could carry a call to voicemail without carrying every trustworthy clue that an old telephone system used to choose the first greeting or menu. RFC 3087 turned the request target itself into a service instruction. That solved a routing problem, but it deliberately…
Story
Two-Thirds, Not Unanimity: How the RIR Governance Document's Version 3 Rewrites Who Decides
The draft that would replace ICP-2 does not merely modernise twenty-five-year-old criteria for recognising Regional Internet Registries. Its Version 3 quietly redraws the voting arithmetic of recognition, derecognition and amendment — and those thresholds, not the prose around…
Europe and Middle East Cloud Services
NovaCloud-Hosting after FFM2: the registry footprint that refuses to move
Six weeks after the operator declared its 19-day Frankfurt outage resolved, a dated re-read of the registry and routing record shows a footprint that has neither corrected nor collapsed — it has simply stayed contradictory.
IETF
The RADIUS Server Parsed the Wi-Fi Metric. It Still Did Not Know What Happened
An Access-Request can arrive with a perfectly valid Connect-Info string: a transmit rate, an RSSI and enough syntax for a policy engine to read both. That is useful progress. It is not yet evidence that the radio measured the right frames, that another vendor would report the…
History
The Policy Server Pushed the Rules. A Reconnect Had to Reconcile What the Device Kept: RFC 3084
RFC 3084 tried to make policy provisioning a disciplined conversation between a server and a network device. Its most revealing work began after delivery: a transaction needed a receipt, a failure needed rollback, and a broken connection left two machines that could remember…
History
A Revision Number Could Order a NewsItem. It Could Not Fetch One: RFC 3085
NewsML could let one logical news item live at several addresses, so RFC 3085 gave it one URN and a per-item revision number. The design was precise about which edition came later and what kind of update it represented; it left resolution and validation to a provider that might…
History
The Cable Link Encrypted Traffic. Its Management Plane Could Still Disable Privacy: RFC 3083
RFC 3083 turned DOCSIS Baseline Privacy into something operators could inspect, tune and reset through SNMP. That visibility helped diagnosis and incident response, but it created a second security boundary: the interface that observed encryption state could also change…
IETF
The Network Was SRv6. The Multicast Tree Was Not Segment-Routed
An operator can migrate the underlay to SRv6, advertise a source through Flex-Algo 128 and still forward every multicast packet through native IPv6 `(S,G)` state. The architecture label is true. The tempting inference—that a SID now describes, installs or proves the multicast…
Global Institutional
G42's Capacity Ledger: What the Abu Dhabi AI Group Actually Operates Versus What It Announced
Abu Dhabi's G42 sits at the intersection of Gulf sovereign capital, US export-control policy and one of the fastest AI infrastructure buildouts anywhere outside the United States. The public record around the company is dense with large numbers — 500,000 chips a year in draft…
History
TCP Was Reliable. One Channel Could Still Starve the Others: RFC 3081
RFC 3081 placed one BEEP session on one TCP connection, then confronted a consequence TCP could not solve for it. Reliable delivery for the connection did not guarantee progress for every application channel inside it. The mapping therefore added local credit, priority control…
History
The Notices Continued After the Directory Agent. New Services Could Still Be Missed: RFC 3082
RFC 3082 tried to replace wasteful polling with event-driven service discovery. Its recovery rules expose a more precise trade-off: a Directory Agent can lose subscription state while service agents already informed of that subscription keep announcing. A new service may enter…
CASE FILE
The SID Selected the Lane. It Did Not Prove the Capacity Was There
A new Segment Routing identifier can tell every router which resource partition a packet is meant to use. The difficult part begins after that lookup succeeds: proving that the promised bandwidth, buffers and queues were actually committed at every hop, remained bound to the same…
History
One Connection Was Not One Conversation: RFC 3080
A BEEP connection could be healthy while no application conversation had yet been agreed. RFC 3080 began with channel zero, a deliberately thin management plane that advertised profiles and negotiated new channels. Only an accepted profile gave an application channel meaning.…
CASE FILE
Completed According to Whose Plan? Svea Bank's Self-Reported AML Remediation Meets the Regulator's Record
When Sweden's financial supervisor Finansinspektionen (FI) announced a sanction against Svea Bank AB on 17 December 2025, the operational part of the decision contained exactly two points: a formal remark (anmärkning) and an administrative fine of SEK 170 million. There was no…
Asia-Pacific Regional ISP
Two APNIC Lineages, Contradictory Route Data, and a Corporate Record That Names No Telecom License: What XEONFIBER TECHNOLOGY Actually Proves
A same-named Indian company appears in two separate APNIC registration lineages, routing aggregators disagree outright about whether either network currently routes traffic, and the corporate registry entry that matches the name carries an activity code that is not a telecom…
History
The Master Key Never Encrypted a Packet: RFC 3079
RFC 3079 called one value a master key, then forbade it from touching traffic. Its job was to feed two role-aware branches, which in turn produced transient send and receive keys for separate cipher contexts. That hierarchy made a quiet point about interoperability: deriving…
CASE FILE
The Report Was Signed Before the Code Ran
An authenticated status report can be perfectly honest and still stop one step before the fact a governor wants. SUIT revision 22 names that boundary `invoke-pending`: the processor is about to hand control to code, but no one yet knows what the code will do.
CASE FILE
Three Names on One Netblock: How Custody of Svea's Legacy Abuse Contact Split Across a Merger
When a Swedish bank merges, its internet number resources do not disappear — they inherit. The RIPE Database record for 193.105.138.0/24 is a rare case where you can read the aftermath directly in a public registry entity: three distinct legal parties, one dissolved predecessor…
History
The Counter Detected the Lost Packet. It Could Not Decrypt the Next One: RFC 3078
RFC 3078 placed a twelve-bit counter beside encrypted PPP traffic so a receiver could notice when the stream had jumped. In stateful mode, that knowledge arrived with an uncomfortable consequence: the packet that exposed the gap still had to be thrown away. Recovery needed a…
Story
The 2019 Excess-Contribution Redistribution: How the RIPE NCC's Own Instruments Authorised and Applied a Contested Remedy
When the RIPE NCC returned EUR 8,365,249 to its members in 2020, the money did not move by improvisation. It moved under Standard Service Agreement Article 7, a Clearing House Procedure that predates the decision, and a General Meeting vote that split hard enough to show how…