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
All Three Attestations Were True. They Still Did Not Belong to the CSR Key
A certification request can arrive with one valid statement about an HSM, another about corporate ownership and a third about platform health. The dangerous moment comes when a certificate authority treats three successful checks as one joined fact. Revision 29 of an IETF draft…
CASE FILE
One Timer Drove Three IPv6 Decisions. The Counters Could Not Explain Which One
A network team changes one millisecond value on an IPv6 interface. Address resolution, reachability probing and duplicate-address detection all inherit it. The edit receipt is precise; the operational meaning is not, until the team joins the change to an interface, an epoch and…
CASE FILE
The Route Reflector Distributed the Link. It Never Witnessed It: RFC 9815's Sparse-Peering Evidence Boundary
A route reflector can hold the newest authenticated account of a data-centre link and still know nothing directly about whether that link carries a packet. RFC 9815 makes this separation operationally useful: BGP can distribute a link-state graph over far fewer sessions than the…
CASE FILE
The Packet Had No SRH. It Could Still Target an SRv6 SID
An edge filter inspects an IPv6 packet, finds no Segment Routing Header and lets it pass. The packet still carries a locally instantiated SRv6 SID as its destination. The visible header test succeeded; the admission decision examined the wrong fact.
CASE FILE
The HSM Signed a Small Attribute Set. The Large CMS Content Was Bound Through One Digest: RFC 9814
An operator can truthfully say that a hardware security module produced an SLH-DSA signature while still leaving the most important question unanswered: which bytes did the module actually sign? RFC 9814 makes that question decisive for CMS. A multi-gigabyte archive may never…
CASE FILE
The IP Address Stopped Naming the RADIUS Client. The Cleartext PSK Identity Took Over: RFC 9813
Two network access servers can stand behind one public address, while one mobile appliance can appear from several addresses in a week. RFC 9813 lets RADIUS/TLS distinguish those relationships with a PSK Identity. The useful part is not the new name. It is the sequence of checks…
CASE FILE
The HTTP Request Returned 200. The Certificate Decision Was Still Inside: RFC 9811
A green transport result is tempting because it is immediate, familiar and easy to graph. RFC 9811 makes that result useful without letting it impersonate the certificate-management decision carried inside it. The distinction is small enough to fit in one response and important…
IETF
A Signature Is Not Proof of the Other Key: RFC 9883 and Private-Key Possession Statements
A second certificate request can be validly signed by an already certified signature key, yet that signature is only an assertion—not technical proof—that the requester controls the different private key behind the requested key-establishment certificate. RFC 9883 defines how a…
History
The Packet That Had to Answer Back: TCP's Challenge ACK Repair
TCP once treated a reset that landed anywhere inside the receive window as sufficiently believable to tear down a connection. RFC 5961 replaced that destructive shortcut with a narrower rule: exact sequence alignment could act immediately; merely plausible input had to survive a…
History
The ACK That Could Not Say Which Packet Arrived: Karn's Retransmission Ambiguity Rule
The same sequence range crossed the network twice. The acknowledgment that returned proved the bytes had arrived, but not which transmission had earned the reply. Karn's rule turned that uncertainty into a discipline: delivery evidence could advance while the round-trip estimator…
IETF
The Signature Algorithm Is Not the Signed Byte Sequence: RFC 9882 and ML-DSA in CMS
Two CMS systems choose ML-DSA-65 for identical content, yet verification fails when one signs a final implicit-tag representation and the other verifies the complete DER SignedAttrs value with its explicit SET OF tag. The algorithm is the same; the signed byte domain is not.
History
The Packet That Waited for Its Predecessor: Nagle's Small-Segment Rule
A one-byte write did not need a universal delay timer. It needed a rule about whether the connection already had data in flight. Nagle's answer made acknowledgment state—not the wall clock—the gate for another short TCP segment.
IETF
The Algorithm Name Is Not the Certificate Profile: RFC 9881 and ML-DSA in PKIX
The Algorithm Name Is Not the Certificate Profile: RFC 9881 and ML-DSA in PKIX intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may…
AFNOG
AfNOG Publishes Mailing-List Rules, Not the Moderation Procedure Behind Them
AfNOG’s mailing-list page sets clear expectations for a technical community: keep discussion operational, avoid disrespect, and do not use the list for blatant product marketing. The published page establishes the rules. It does not explain the procedure used when a post is…
IETF
A Registry TTL Is Policy State, Not a Live DNS Observation
RFC 10037 lets a registry publish configured DNS time-to-live values through RDAP. That sounds like a small JSON extension. Its more important effect is to expose a piece of registry policy without pretending that a registration-data service is watching the live DNS. The…
IETF
A Data Model Is Not a Wire Contract: RFC 9880 and SDF Protocol-Binding Boundaries
Two implementations can claim the same Thing model yet disagree on the wire: one chooses a URL and JSON payload convention, while the other expects a numeric identifier and different invocation rules. The gap appears when a protocol binding was implicit rather than versioned and…
History
The Probe That Could Not Declare an Idle Peer Dead: TCP Keep-Alives
An idle TCP connection can be quiet without being broken. Keep-alive probing was designed to ask whether the peer's transport state could still answer, while denying any single unanswered probe the authority to declare that state dead.
IETF
A Hybrid SSH Key Exchange Turns Algorithm Negotiation into a Migration Boundary
Installing post-quantum code does not mean an SSH session used it. RFC 10042 defines three hybrid methods that combine ML-KEM with an established elliptic-curve exchange. The protection becomes real only when both peers offer the same method, negotiation selects it, both…
Leaders
Prasad Vadke and the Escalation Clock Behind Enterprise Email
An enterprise email incident starts two clocks at once. One measures the technical work of diagnosis and recovery. The other measures missed decisions, interrupted meetings and the widening cost of uncertainty. Prasad Vadke's public writing on service-level agreements is most…
IETF
The Integrity Check Has Its Own Parameters: RFC 9879 and PBMAC1 in PKCS #12
A PKCS #12 exchange can fail at the integrity boundary when one implementation reads compatibility-shaped legacy fields while another follows PBMAC1’s nested parameters. The two sides can then disagree about the password-derived key, the MAC scheme, or the authenticated bytes.