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
Four Radios, One Control Problem: What RFC 9913 Reveals About RAW's Capability Plane
Four radio technologies can each advertise scheduling or redundancy while exposing different clocks, resource units, diversity primitives and failure correlations; their feature names are therefore not interchangeable assurance promises. This briefing by Theo March examines how…
AFNOG
AfNOG’s Affiliation Field Names an Institution Without Defining the Relationship
AfNOG’s 2007 call requested a contributor’s affiliation without defining what relationship that label represented.
History
Why IPv4 Checksums Only Its Header
A packet can carry an undamaged payload and still be dangerous to forward if a bit error changes its destination, length or remaining lifetime. IPv4 therefore checks the control surface routers must trust: its header, and only its header.
Story
Barry’s README Uses the IPv6 Prefix Its Lexer Rejects
`::/0` and `0::/0` name the same IPv6 address space. In LACNIC’s experimental Barry generator, the first spelling is documented as a default yet an open issue says it stops at the descriptor lexer; adding one zero lets the token proceed. That is not an RPKI validation failure. It…
CASE FILE
The Reference Was Well-Formed. It Was Not Yet Evidence
A digest can look precise enough to end an argument. Revision 03 of the Canonical Payload Binding draft instead turns that apparent certainty into a sequence of accountable tests: the reference must be admissible, one authorized digest context must be selected, the artifact must…
IETF
The Fast Path Is a Recovery Graph: RFC 9912 Moves Wireless Reliability Into the Network Plane
Wireless conditions can change faster than a controller can install a new route, so RAW preinstalls a finite recovery graph and lets a Point of Local Repair select protection paths locally. That is the architectural move: reliability becomes a network-plane control problem, not a…
CASE FILE
The Maximum Metric Kept the Link. Missing Data Could Keep It or Remove It
A routing value can look catastrophic without withdrawing a link, while an empty field can either remove that link or leave it eligible. RFC 9843 makes those outcomes deliberate. Operations fail when telemetry turns three different protocol states into one red icon.
CASE FILE
A RISC-V Profile Is a Compatibility Vocabulary, Not a Hardware Mandate
A RISC-V profile makes a useful promise of language, not a universal promise of hardware. It tells hardware and software communities which bounded instruction-set surface they can discuss together. It does not, by itself, tell a buyer what is on a particular chip, tell a…
Leaders
Vint Cerf and the Deadline Behind the TCP/IP Cutover
The decisive test was not whether TCP/IP worked in a document. In Vint Cerf's recollection, rehearsed NCP shutdowns in 1982 exposed mail disruption and showed how much operational work remained before the ARPANET could change protocols. The transition became credible through…
IETF
The Namespace Stayed Put: RFC 9911 Makes Common YANG Types a Migration Surface
A server can import the same `ietf-yang-types` namespace yet validate a timestamp differently when the common module revision changes. RFC 9911 keeps the familiar module identity while revising accepted values, canonical forms, and descriptions—turning a shared typedef library…
History
When IPv4 TTL Stopped Being a Clock
IPv4 gives every datagram a field called Time to Live, measured in seconds. Yet the forwarding rule subtracts at least one even when less than a second has passed. That mismatch turned a nominal lifetime timer into the Internet's practical hop budget.
History
The Formatting Could Disappear. The Message Still Had to Be Readable: RFC 1523
A reader that understood no boldface, centring or indentation could still recover the prose. RFC 1523 made that outcome a property of the format itself: presentation commands were disposable, while their limits, nesting and whitespace rules made the remaining text predictable…
AFNOG
AfNOG’s Direct-Contact Field Lists Reachability Without Stating Its Handling Boundary
AfNOG’s 2007 call requested four published contact points without publishing an adjacent purpose, access or retention notice.
IETF
The Link Is a Snapshot: RFC 9910 Makes RIR Hierarchies Searchable
A single-result RDAP search link may become a lookup URL, but registry state can change before a client follows it. The link is therefore a time-bound snapshot of a registry view, not a timeless statement about a resource.
Leaders
Warren Kumari and the Design of DNS Failure You Can Survive
Warren Kumari’s standards work shows that resilient DNS is not the absence of failure. It is the disciplined design of limited continuity, explicit freshness, fallback and legible error signals.
History
Why IPv4 Options Carry a Copy Bit
Two fragments of the same IPv4 datagram can legitimately carry different option sets. That is not an accident of implementation. A single bit inside every option type tells a fragmenter whether the option must follow all fragments or remain only with the first.
History
The Link Was Open. Configuration Still Belonged to a Second Negotiator: RFC 1552
In one 1993 PPP design, reaching `Opened` could mean the network protocol was ready. In another, the very same state was only permission for a second negotiator to begin. RFC 1552 made that difference explicit—and showed why a state name is never a complete receipt.
AFNOG
AfNOG’s Requested-Time Field Leaves Its Relation to Programme Planning Unexplained
AfNOG’s 2007 call asked contributors how much time they wanted without explaining how that request would relate to programme planning.
IETF
The Server Writes the Blank Form: RFC 9908 Makes EST CSR Attributes Operational
An EST server can now send a partially filled CSR form: it fixes the values it requires while leaving explicit blanks for the client to complete.
IETF
The Review Is the Interface: RFC 9907 Turns YANG Documents into Operational Controls
A YANG module may parse cleanly yet still create incompatible operations when its specification leaves lifecycle, datastore, or registry authority ambiguous. RFC 9907 makes authoring and review discipline part of the control surface for management specifications.