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
A Call-Home Datagram Is Not Device Authority
A managed router may need to reach an operator from behind an address translator or firewall. The newest NETCONF working-group draft adapts Call Home to QUIC by having the device send an empty UDP datagram and the management system connect back to its source. The mechanism is…
CASE FILE
The Log Filter Made Tomorrow’s Evidence Decision
RFC 9742 gives network operators a common language for configuring syslog. The harder question is whether that language preserves the particular evidence an incident will make valuable.
History
Jan Gruntorád and the Link That Had to Become Two Networks
At the start of 1992, an international circuit from Prague to Linz was strengthened and divided. One channel continued to carry EARN traffic; the other was assigned to the Internet. In that physical line becoming two operational networks lies a more useful history of Jan…
IETF
A Fast-Path Timestamp Is Not an Authenticated Measurement
A network can make a measurement faster by keeping a probe in silicon. That is an engineering gain, not a cryptographic transformation. The proposed Timestamp and Forward mode for segment-routing STAMP lets a reflector write a receive time in the data plane and send the packet…
IETF
An Unset FRR Flag Cannot Name the Local Policy That Won
A traffic-engineering head end asks every repair point to keep a backup path below a delay bound. The reservation comes back with one repair point’s new flag unset. Traffic may still have a backup there, computed under local policy, but the ingress cannot tell from that bit which…
History
Ben Segal and the TCP/IP Pilot That Could Not Leave CERN
By March 1988, TCP/IP served 355 machines at CERN, from an IBM mainframe and a Cray to VAX systems, workstations, PCs and Macintoshes. Yet none of those machines could use TCP/IP to cross the laboratory’s external boundary. Ben Segal’s pilot had solved heterogeneous connectivity…
CASE FILE
RFC 9744: the circuit identities a shared tunnel must retain
Fewer service labels can make a carrier network cheaper to operate. The saving becomes less convincing when the remote edge can no longer tell which customer circuit needs a different path.
IETF
A Verified RDAP Contact Needs an Audience Boundary, Not a Universal Badge
A registrar can verify an email address once and face two different disclosure questions the next morning: what may an anonymous reader learn, and what may an authenticated investigator learn for a justified purpose? The verification event is the same. The authority to disclose…
History
RFC 2057: the 1996 argument over who controlled the audience
In 1996, sending an email to a mailing list could hand its onward distribution to another operator's program. Scott Bradner's RFC examined the distance between controlling that first transmission and establishing the identity and age of everyone it eventually reached.
History
Rob Blokzijl and the Chair That Could Coordinate but Not Command
The most revealing sentence in RIPE’s first terms of reference is not the one that declares a European ambition. It is the sentence that withholds power. RIPE was not a network provider, and the networks cooperating through it remained under the executive authority of their own…
CASE FILE
RFC 9746: the compatibility cost of choosing EVPN split horizon
A default-method entity can send an upgraded Ethernet segment back to its encapsulation baseline. The operational question is whether the network has kept the resources and evidence needed to make that return safely.
IETF
An Authenticated BGP Update Is Not an SD-WAN Tunnel Admission Record
When a protected control-plane session delivers a syntactically valid route, it is tempting to treat the event as one completed act of trust. In an SD-WAN, however, the update has only crossed the first of several institutional boundaries. The harder question is not whether BGP…
History
Qiheng Hu and the 64K Link That Needed Authority at Both Ends
By the end of 1993, the network was technically ready. Its domestic backbone joined three academic systems, its team had chosen TCP/IP, and the international circuit had been provisioned. Yet packets still did not cross. Qiheng Hu’s part in China’s full-function Internet…
IETF
A BMP Percentile Is Local Until Its Sampling Method Travels With It
A router can report a P95 that is correctly encoded, correctly attributed and still unsafe to compare with the P95 from the next router. The missing link is not another decimal place. It is the method that selected the observations from which the percentile was made.
CASE FILE
RFC 9747: the neighbour returns a packet, not a health declaration
Unaffiliated BFD Echo removes the need for the far end to speak BFD. That useful simplification leaves the local operator owning both the test and the decision made from its result.
History
Jun Murai and the Address Space That Became a Trust
The number is oddly exact: 14,680,064 IPv4 addresses. They were neither a fresh registry allocation nor abandoned space waiting to be reclaimed. They were seven-eighths of an old Class A block, held through three decades of changing Internet institutions, and in 2020 Jun Murai…
IETF
IPv6-Only Is a Scoped Forwarding Claim, Not an IPv4 Decommission Certificate
The phrase “IPv6-only” sounds like a clean finish line. In an operating network it can describe something much narrower: one link natively forwards IPv6 while IPv4 still reaches users through translation, another plane remains dual-stack, and a management path still depends on…
History
Kilnam Chon and the Router Asia Could Not Buy
On 15 May 1982, two computers in South Korea began speaking across a 1,200 bps leased line. The connection was modest; the missing box beside it was more consequential. With no obtainable IP router, Kilnam Chon’s group treated published protocol documents as equipment they could…
IETF
A Valid CoSERV Result Is Not a Completeness Proof
A relying party asks for the reference material needed to judge attestation evidence. The query is deterministic, the response is signed, the contents are still valid and every cryptographic check succeeds. That is a strong result—but a bounded one. The exchange proves what was…
History
Kees Neggers and the Backbone Europe Built in Parallel
On 26 September 1992, one link between London and Montpellier completed Ebone’s initially defined backbone. The more revealing number was not its line rate but its age: 390 days since a small group had first met outside Amsterdam to ask whether Europe could operate a shared IP…