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.

IETF
RFC 9818: A Delegated Prefix Is Not Usable Capacity Until the Lease, Route and Filter Agree
A provider may hand an IPv6 CE router more address space than one LAN needs. RFC 9818 shows why that allocation is only the first claim in a longer chain: a downstream lease, a next-hop route, a matching filter decision and a lifetime bounded by the parent delegation must remain…

Story
AFRINIC's Power to Revoke Number Resources Sits in a Contract, Not a Constitution
Every dispute about AFRINIC's internet number resources eventually resolves into a narrower question than the one the headlines ask. The registry's authority to suspend, revoke or refuse to renew African IP address space is not a constitutional attribute of a regional internet…

Afrinic SAGA
RIPE NCC to AFRINIC: the handover that moved the ledger but never escrowed it
Africa got its own internet registry in 2005. What it did not get, on the evidence available two decades later, was a registry that could outlive its keeper. The entities moved. The guarantee did not.

Global Cloud Services
Oracle Cloud's AI build-out: contracted backlog runs ahead of energised capacity
Oracle closed the first quarter of its 2027 fiscal year with $664 billion of remaining performance obligations on its books and a statement that it had delivered 850 megawatts of AI compute capacity to customers during the same three months. Read together, those two numbers…

IETF
RFC 9862: The Drop Flag Lives on a Candidate Path, but the Consequence Belongs to the Whole SR Policy
RFC 9862 carries a drop instruction on one Candidate Path even though the resulting decision belongs to the entire Segment Routing Policy. That mismatch between signaling scope and consequence scope is exactly where an operational status can be correct yet still fail to explain…

History
Hari Balakrishnan and the Detour That Could Only Promise What It Measured
The direct path is dropping packets, yet the routing system still considers it alive. A second machine can reach both ends, but only an application that measures those two legs knows the detour exists. Hari Balakrishnan and his coauthors made that gap operational in RON: not a…

IETF
RFC 9867: A Created Security Association Is Not Proof That the PPK Was Mixed
An IKEv2 exchange can finish and a new Security Association can appear even when the preshared key intended to strengthen it was never incorporated. RFC 9867 makes that outcome legitimate under optional policy. It also makes a creation-only security dashboard dangerously…

History
Christian Huitema and the DHCP Client That Had to Forget More Than Its Address
A laptop leaves one network, changes its wireless address and arrives at another. The visible label is new, yet its DHCP request repeats an old client identifier, asks for options in the same peculiar order and offers the address it used before. Christian Huitema and his…

IETF
RFC 9707: Being Connected Is Not Access—and a Workshop Report Is Not a Mandate
An Internet link can be live while the service a person needs remains unaffordable, unreadable, blocked, fragile or unsafe. RFC 9707 makes that failure visible. It also marks the limit of its own authority: the document records a workshop, not a consensus verdict. Governance…

History
Eddie Kohler and the Router Arrow That Did Not Say Who Called First
A packet-processing diagram contains an arrow from one component to the next. It looks like an instruction: the left side acts, the right side receives. In Eddie Kohler's Click modular router, that inference is unsafe. The packet still travels along the arrow, but control may…

Asia-Pacific National Telecom
Vodafone Idea's Binding Constraint Is a Creditor That Is Also Its Largest Shareholder
The Indian state owns 48.99% of Vodafone Idea and is, at the same time, the company's largest creditor. With bank borrowings down to Rs 211 crore, the network the operator can actually build now depends on whether operating cash flow can carry an announced Rs 45,000 crore…

History
Robert Metcalfe and the Collision That Gave Nobody the Next Turn
Two stations listen to the same cable, hear nothing and begin speaking. The contradiction is only apparent: a signal needs time to travel, so each station can be locally correct and globally in conflict. Early Ethernet made that conflict observable as a collision. It did not…

IETF
RFC 9812: A Stricter Review Gate Does Not Allocate IPv6 Space
Most of the IPv6 address space remains marked “Reserved by IETF.” RFC 9812 changed the rule for any major future release of that reserve from IESG Approval to IETF Review. That is a consequential transfer from an exceptional gate to a public, documented process. It is not an…

IETF
Nick Hilliard and the IPv6 Prefix That Works Only When It Goes Nowhere
`100::/64` is globally unique, forwardable inside a network and deliberately not globally reachable. That apparent contradiction is the point. The prefix gives IPv6 remote-triggered blackholing a clean internal next hop, but its success cannot be read from an IANA row or a green…

IETF
RFC 9998: A Failed Age Check Is Not Consent to a More Intrusive One
Age checks are often presented as a door: prove the required range and it opens; fail and it stays shut. The harder governance problem begins when the first check produces no reliable answer. A system may then ask for a document, a face scan, a phone number or a longer behavioral…

Leaders
Nick McKeown and the Barrier Reply That Never Saw a Packet
A controller can receive a perfectly valid OpenFlow Barrier Reply while the customer’s packet is still being discarded. That is not a contradiction. The reply certifies order on one control connection; delivery belongs to a longer chain of evidence that starts after the fence.

IETF
RFC 9876: A CoAP Registry Number Is Not an Interoperability Verdict
The smallest number in a protocol can carry the largest institutional misunderstanding. A CoAP Content-Format identifier lets a constrained device say, compactly, what representation it is sending. RFC 9876 makes the allocation of that number much harder to get wrong. It does not…

IETF
RFC 9874: A Successful EPP Delete Can Break Another Client’s DNS
The dangerous EPP deletion is not necessarily the one that fails. It is the one that succeeds for the requesting client while changing name-server state relied on by domains sponsored by somebody else. RFC 9874 turns that hidden dependency into an operational question. The…

Leaders
Remco van Mook and the IPv4 Gateway That Has No IPv4 Neighbour
An IPv4 default gateway normally looks like an address that a host can find with ARP. Remco van Mook's current IETF proposal turns that expectation inside out: `192.0.0.11` is not a neighbour to discover, but an instruction to reuse a neighbour that IPv6 has already discovered.…

IETF
The Network Agreed the Root Was Down. It Did Not Prove a Crash: RFC 9866
RFC 9866 lets a low-power network reach a coordinated decision that its current routing root is no longer usable. The decision can be operationally correct even when the root is still powered and the physical cause is unknown. Treating `GLOBALLY DOWN` as a forensic verdict would…
