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
Two Duplicate ACKs Could Send New Data, but Not Enlarge the Window: RFC 3042
A TCP sender with a three-segment congestion window loses one segment. The receiver can return only two duplicate acknowledgments for the later data, one short of the threshold that would trigger Fast Retransmit. In 2001, RFC 3042 proposed a narrow way to keep the feedback clock…
Latin America and Caribbean National Telecom
Millicom Finishes the Telefónica Roll-Up: What Closed, What It Cost, and Where the Leverage Now Sits
Millicom International Cellular S.A. has converted an eighteen-month pipeline of announced Telefónica divestments into completed ownership: Uruguay closed on October 7, 2025 at a $440 million enterprise value, Ecuador on October 30, 2025 at $380 million, Telefónica's controlling…
History
The ATM Label Changed at Every Switch. LDP Needed One Both Ends Could Share
An ATM circuit could keep carrying cells while the number printed in its VPI/VCI field changed at the next switch. LDP peers therefore needed more than the local label: they needed a shared identity for the virtual connection before they could bind it into MPLS.
History
The Switch Could Not Decrement TTL. The Ingress Paid the Hop Count Up Front: RFC 3034
A Frame Relay switch could replace a DLCI at line rate yet lack the operation that routers performed on every packet: subtract one from time to live. RFC 3034 preserved MPLS loop and scope accounting by charging a propagated segment length at the boundary. The control plane…
Europe and Middle East National Telecom
stc Leverages the Balance Sheet Itself: Inside Saudi Telecom's Funded Pivot to Capital Intensity
For six years Saudi Telecom Company (stc) ran one of the cleanest balance sheets in global telecom: net debt to EBITDA of 0.02x at mid-2025, effectively cash on the sidelines. In the first half of 2026 that state ended. Group capital expenditure rose 31.0% year on year to SAR…
History
LDP Kept the Full-Length Prefix and Dropped the Host FEC
In 2001, LDP gave routers two distinct ways to describe a destination address, even when both could point at the same host. Six years later, its revised specification removed one of those forms for a precise reason: no implementation used it. The full-length prefix remained.
History
The Identifier Named the Session. It Did Not Move It: RFC 3033
A call-control message could carry the exact IPv4 or IPv6 tuple that named an Internet session, yet the packets could still be travelling over the old virtual circuit. RFC 3033 gave ATM signalling a vocabulary for the intended subject. It deliberately stopped short of claiming…
History
The Server Advertised a Capability. Authentication Changed the Answer: RFC 2449
A POP3 client asks what a server can do before it knows who is asking. The reply may be deliberately cautious. The same server can give a more precise answer once a user is authenticated—and a different answer again after the session gains an integrity-protection layer. RFC 2449…
History
The Server Signed the Verdict. The Object Was Still Invalid: RFC 3029
A signed certificate arrives from a trusted validation server. Its conclusion is not “valid” but “invalid”. There is no contradiction. The signature authenticates who issued the verdict, the request it answers, the time and the policy used. It does not repair the document or…
History
The Network Treated Every Packet Equally. The Codec Did Not: RFC 2448
When a compressed picture loses a few bytes, the size of the loss can be a poor guide to its consequence. A missing fragment of ordinary image data may blemish one region; losing a compact description of how to decode what follows can damage much more. In 1998, RFC 2448 proposed…
History
The Rule Chose an Action, Not an Outcome: RFC 3028
A mail filter reaches the end of its script without choosing a destination. That absence could have meant loss. Sieve instead turned it into a protective decision: keep the message by default. The small rule exposes the larger architecture of RFC 3028—language evaluation could…
History
The Envelope Was Not the Calendar: RFC 2447 Put iTIP Inside MIME
RFC 2447 made familiar Internet email a carrier for structured scheduling without asking the mail envelope to become a calendar protocol. Its binding placed a `text/calendar` entity inside MIME, paired the entity's `METHOD` with the MIME `method` parameter, and allowed a readable…
History
The Suffix Knew the Grammar, Not the Meaning: RFC 3023
A MIME dispatcher could read the final four characters of `application/foo+xml` and learn something useful: an XML processor might open the representation. It still could not know what `foo` meant, which operations were safe, or whether the document was allowed to cause an…
History
A Complete COUNTER Is Still a Proposal: Authority and State in RFC 2446
*The original iTIP model separated a fully specified alternative event from the authority to change the organizer’s master calendar entry.*
History
The Broadcast Address Became a Router: RFC 3021
On an ordinary IPv4 subnet, an address whose host bits are all ones had long carried broadcast meaning. RFC 3021 made that same bit pattern identify one router—provided the link really had only two ends and both ends understood the exception.
History
The Bundle Turned Green When One Link Survived: RFC 3020
RFC 3020 made several Frame Relay circuits look like one logical interface. It also made “up” a configurable predicate: sometimes one surviving link was enough. The green state was useful, but it was a receipt for a policy threshold—not for full capacity, intact ordering or…
History
The Cache Row Said a Group Had Members. Management Could Have Created It: RFC 3019
RFC 3019 gave operators a table of IPv6 multicast membership. The same table let management create or delete rows and declare the local machine a member. Its most useful historical lesson is therefore not that a row was false, but that its origin and evidentiary limit had to…
History
A Password Could Be Used Once. The Session Still Needed Its Own Protection: RFC 2444
RFC 2444 made a one-time password a named way for network protocols to authenticate a user. It did not make the conversation that followed private, prove who answered the server, or turn a successful login into a general security guarantee.
History
The Transaction Was Atomic. The Remote Call Was Not Reversible: RFC 3018
RFC 3018 imagined a network in which software could read memory, allocate storage and transfer control across machines as if the distance had disappeared. Its transaction could release a bundle all at once. Once a remote call ran, however, the protocol offered no universal road…
History
The Replicas Agreed. The Clients Still Had to Return: RFC 2443
In the late 1990s, ATM networks could carry IP multicast, but a multicast client still needed a service that knew which groups existed and which endpoints belonged to them. RFC 2443 copied that knowledge among MARS servers. Its more revealing rule was what happened when the…