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.
CASE FILE
The VPN Number Arrived. Admission Was Still Open
RFC 9837 puts a 32-bit VPN service selector inside an IPv6 packet. The field can tell an egress router which forwarding entry to use. It cannot tell that router whether the sender had the right to choose it. That second claim belongs to the tunnel and the domain boundary.
History
The Table Measured What an Application Could Use, Not the Disk: RFC 1514
A host can report a perfectly accurate disk capacity and a smaller, equally accurate amount of usable storage. The disagreement begins only when a manager strips away which layer each number describes. In 1993, RFC 1514 built that distinction into the Host Resources MIB: physical…
CASE FILE
The Circuit Was Ordered. The Network Had Not Built It
RFCs 9833–9836 give an attachment circuit several linked identities instead of pretending that an accepted customer order is already a working path. Their most useful operational lesson is the distance between the service request, the provider’s network realization and the…
CASE FILE
The Registry Said 200. The Domain Command Failed
The newest EPP-over-HTTPS draft makes a deceptively simple distinction operationally unavoidable: `200 (OK)` can mean the command reached the registry application, not that the registry accepted it. Once registration traffic passes through load balancers, retries and distributed…
History
The Address Stayed the Same. The Server Did Not Have To: RFC 1546
In 1993, one ordinary-looking destination field was asked to do an unusual job: name a service offered by several machines while declining to name any particular machine. RFC 1546 called that experimental service anycasting. Its enduring lesson is less about shortening a path…
North America Datacenter Trends
Target Hospitality’s Data-Centre Community Is an Asset-Reuse Test Before It Is an AI Capacity Story
Data-centre development requires more than power, land and servers. It also requires a workforce that can live close enough to build, operate and maintain the site. Target Hospitality’s 2025 filing offers a useful record of that supporting layer, but not in the form of a new…
North America Datacenter Trends
WhiteFiber’s US$72.6m Prepayment Is a Liability Before Its GPU Orders Become Revenue
WhiteFiber has received meaningful customer cash for future cloud and data-centre services. Its 30 June filing also describes new GPU service orders. Those are constructive facts, but they sit on different clocks: a prepayment is a liability until service is performed, while an…
History
The Probe Counted Shortages, Not Missing Frames: RFC 1513
The counter moved from 41 to 42. How many frames had vanished? RFC 1513 gave the only responsible answer: the number did not say. It recorded one more occasion on which a monitoring probe ran short of resources, not the size of the unseen traffic behind that shortage.
AFNOG
AfNOG’s Optional Hands-On Tutorial Format Leaves Resource Needs Unstated
AfNOG’s 2007 call allowed hands-on tutorial components but did not publish their resource needs.
History
Why TCP Sequence Numbers Return to Zero
In TCP, zero does not always come before a large number. After sequence position 4,294,967,295, the next position is zero. The protocol keeps acknowledgments, windows and retransmission decisions coherent by treating the 32-bit sequence space as a ring and comparing positions…
Story
The IANA Review Called Outreach Sufficient. AFRINIC Had No Voting Community Member
The 2025 IANA Numbering Services review reached a supportable technical result and met its global quorum. Its own records nevertheless show a narrower institutional fact: a committee designed for ten community voters listed only eight, because AFRINIC’s two community places were…
IETF
One Intent, Two Link-State Languages: RFC 9903 and the OSPF SR-MPLS Control Boundary
A single SR intent can be managed through a common YANG surface, while OSPFv2 exposes it through Opaque LSAs and OSPFv3 through Extended LSAs and distinct TLVs. That is a shared management contract, not identical wire encoding.
History
The Number That Made TCP Flow Control Move
TCP did not put a receiver's memory size into every segment. It put a moving allowance into the header: a count of how many data octets the sender of that segment was then willing to accept, beginning at the acknowledgment frontier. That pairing turned flow control into a…
CASE FILE
The Signature Still Verified. The Identifier Had Changed
A new measurement submitted to the IETF shows how 64 different CBOR encodings can preserve one valid COSE signature while producing 64 different hashes of the transmitted statement. The cryptography did not fail. The storage boundary did: a system that reads and re-encodes before…
AFNOG
AfNOG’s ‘Soon-to-Be-Deployed’ Tutorial Scope Leaves Readiness Undefined
AfNOG’s 2007 call described advanced training on technology soon to be deployed without defining readiness.
Leaders
Razvan C. Oprea and the Discipline of Naming Operational Limits
The most revealing moments in Razvan C. Oprea’s public work are not declarations of success. They are the moments when a measurement fails to show what it was expected to show, when a research project draws a line around what its data can establish, or when a technical strategy…
History
The Handle Was the Same. The Credential Could Be Different: RFC 1509
Two programs present the same pointer-sized value to a security service. One reaches Alice’s credential. The other may reach Bob’s—or nothing at all. No bit in the value has changed. The caller has. RFC 1509 made this possible on purpose, because its handle was never the…
CASE FILE
The SID Field Was Present. The SID Was Still Missing: RFC 9831
A controller sent a Segment Type I with its SID-present flag set. The receiving headend could count all 16 octets of the field. Every octet was zero. That was not malformed silence: RFC 9831 permits the controller to describe the behavior it wants while leaving the executable SID…
IETF
The Model Behind the Label Stack: RFC 9902 and the Operational Contract for IS-IS Segment Routing
One enable leaf can start advertising IS-IS Segment Routing extensions, but safe activation depends on the protocol-independent SR label resources already configured beneath it. RFC 9902 makes that seam visible: the switch belongs to IS-IS, while the resources it invokes belong…
History
The Bits TCP Kept for the Future
Six quiet positions in TCP's 1981 header carried no immediate function. Their importance lay in the discipline around that emptiness: send them as zero, leave them available, and let a later standard define meaning without moving the boundary of the base header. Two decades…