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
The Reflector Returned an Address. It Did Not Return an Exit Plan.
RFC 3424 treated self-address discovery across NAT as a temporary heuristic, not a new identity system. The harder question was never whether a reflector could report a mapping. It was who would retire the dependency after applications learned to need it.
IETF
The Grease Range Passed. Every Other Unknown Value Still Failed
A middlebox can learn to permit the values reserved for anti-ossification tests while continuing to reject every genuinely unfamiliar DNS extension, turning the test itself into a new fossil.
History
The Stronger Lock Was Offered. The Attacker Removed It Before Selection: RFC 3329
The first security offer traveled before there was any agreed security to protect it. That circular problem made a one-line deletion powerful: erase the stronger mechanism, and two capable SIP peers might settle for less. RFC 3329 answered with a receipt delivered later, after…
History
A REGISTER Was Temporary. Its Route Was for Later: RFC 3327
A registrar could know which contact to call without knowing every proxy that a future call had to cross. RFC 3327 attached an ordered Path to a contact binding so the home proxy could reuse those route references after REGISTER had finished. That Path prescribed later routing…
History
The Registrar Knew the Contact. It Still Did Not Know How to Reach It: RFC 3327
A successful registration can answer the wrong question perfectly. SIP could tell a registrar which Contact belonged to a public address, yet still leave the home network unable to reproduce the route required to reach that Contact. RFC 3327 turned that missing route into state…
IETF
The Answer Arrived. The Resolver Never Accepted the Limit
A proposed DNS option lets a client cap how much address information a recursive resolver may disclose, but a normal answer can conceal the most important fact: an older resolver may have ignored the request completely.
IETF
The Server Never Rejected the Connection. The Firewall Rejected Two New Bits.
A TCP reset looked like the remote endpoint had refused the connection. RFC 3360 showed why that conclusion could be false: an on-path box might have generated RST merely because an ECN setup SYN used two formerly reserved flags.
Story
RIPE’s RRC12 Output Stalled After a High-Volume DE-CIX Peer
RIPE NCC says an unusually large stream of BGP messages from one DE-CIX peer repeatedly timed out the process that turns RRC12 updates into public files. Its archive still ended at 01:00 UTC on 2 October when checked 18 hours later.
History
The Phone Stopped Ringing. The Protocol Had to Preserve Why: RFC 3326
Two phones can stop ringing at the same instant for opposite reasons. One was abandoned; the other lost a race because the call was answered elsewhere. RFC 3326 gave SIP a place to preserve that difference after the visible action had become identical.
Leaders
John Curran and ARIN’s 2019 Resilience Test
ARIN’s December 2019 outage exposed a gap between a high-availability design and a recovery path that could survive a shared-storage failure. The public record shows how the registry restored its website and customer application on separate clocks, then made remediation and…
IETF
The Bit Came Back. The Delegation Evidence Did Not
The resolver set a new capability bit and saw that bit echoed in the answer. Between those two packets, an attacker had removed the delegation records that mattered. The exchange still looked negotiated. It was not yet authenticated.
History
A CANCEL Carried the Cause. SIP Still Did the Canceling: RFC 3326
When one branch of a forked call answers, a proxy can stop the other branches and attach a short explanation. RFC 3326 made that explanation portable without letting it take over the protocol action.
History
The User Chose a Preferred Identity. The Proxy Had to Remove the Choice: RFC 3325
RFC 3325 gave the user a way to name the identity they preferred. Then it ordered the proxy to delete that preference before forwarding the message. The deletion was not cleanup; it was the line between a user-selected hint and a network assertion.
IETF
The Console Prompt Appeared. The Recovery Path Still Had Five Dependencies.
An operator can reach a router's console while remaining unable to recover the network. RFC 3871 made the emergency interface a security requirement in 2004; its more durable lesson is that transport, device identity, authentication, privilege, command effect and restored service…
History
They Shared a Trust Domain. They Still Did Not Trust Each Other: RFC 3324
RFC 3324 drew one of its most important security boundaries with an apparently paradoxical example: two SIP nodes could belong to the same trust domain while one did not trust the other. Membership described a common rule set. Trust described a verified edge known to the…
Story
LACNIC’s 47-University Security Metric Leaves Its Denominator Unclear
LACNIC’s September account repeats a striking improvement in the share of Ecuadorian universities rated critically for security. The public record gives the percentages and a cohort description, but not the endpoint counts needed to reproduce the change.
IETF
The Selector Found Nothing. The System Cleared the Field
The JSON Path worked exactly as specified. It found no matching node, so the server resolved the reference to `null`. The later method accepted the value and cleared a property that nobody had intended to touch. Nothing in the protocol malfunctioned. The mistake was believing…
History
The Caller Was Anonymous to the Recipient, Not to the Privacy Service: RFC 3323
RFC 3323 did not define anonymity as disappearance. It defined a route through which one party could stop seeing an identity only because another party was trusted to see, remove and route around it.
History
Anonymous to the Other Party, Reachable Inside the Dialog: RFC 3323
RFC 3323 did not make a SIP caller disappear. It asked a narrower question: which identity-bearing details should a recipient see, and what state must a service retain so the conversation can still work?
IETF
The Adjacency Was New. The Router’s LSP Was From Its Previous Life.
The Adjacency Was New. The Router’s LSP Was From Its Previous Life. 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 follow. The…