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.
Number Resource Society
The FAQ Answer Needs a Version Date
A frequently asked question looks like the lightest form of institutional writing. In practice, it can be the page a member reads before applying, changing details, relying on a benefit or choosing where to ask for help. When that answer has no visible date or predecessor…
North America Regional ISP Trends
BEAD awards do not become project cash until reimbursement clears
A fibre crew can finish a week's work while the contractor's payroll and the supplier's invoice fall due before the state has accepted the next BEAD payment trigger. The award may be valid, the construction eligible and the project economic, yet the subgrantee still has to…
Story
At LACNIC, the Most Valuable IPv4 Option Is Waiting
At LACNIC, the Most Valuable IPv4 Option Is Waiting 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 Story…
IETF
The quarter-second bargain behind Happy Eyeballs
Happy Eyeballs turned dual-stack connection setup into a managed race. Its success lies in making path failure less visible to users; its cost is that the same success can make broken paths less urgent to repair.
Global Regional ISP Trends
RPKI’s Recovery Path Is Becoming a Routing Control Surface
A ROA is not useful merely because it exists. The operational result also depends on how repositories and validators move from delta to snapshot to fallback—and how long they trust a previously valid view when those paths fail.
History
The Address That Expired to Protect Its User: IPv6 Temporary Addresses
IPv6 privacy extensions did not make an address secret. They changed which address a host would prefer for its next conversation, how long that preference lasted, and when the identifier finally had to leave the interface.
IETF
Joining the group is no longer enough: SSM makes the receiver name the sender
Source-Specific Multicast turns a multicast join into a choice: the receiver must identify both the group it wants and the source it is willing to hear.
ICANN
The Public Query Became a Private Lead Machine: Register.com v. Verio
A daily list of newly registered domains looked like public infrastructure until Verio connected it to automated WHOIS queries and rapid sales calls. The resulting case is less a monument to web-contract doctrine than a practical warning about layered permission: public data, a…
Global Regional ISP Trends
Put the recovery circuit outside the failure it must repair
A network site is not locally controllable merely because its equipment is nearby. Control exists only if the people expected to restore the site can still reach, authenticate to, understand and change it after the production path has failed.
ICANN
When a DNS-Abuse Report Becomes Actionable—and What the Contract Still Does Not Order
The decisive step in ICANN's DNS-abuse regime is not the arrival of an allegation. It is the moment when available evidence supports a reasonable finding, after which a registrar or registry must act promptly—but still choose a remedy that fits its role, the harm and the risk to…
CASE FILE
The Certificates Did Not Expire: Chrome's Entrust Cutoff Turned Trust Into an Operating Licence
The decisive field was not the expiry date printed inside a TLS certificate. It was the timestamp proving when that certificate entered the public record—and whether Chrome still accepted the authority behind it at that moment.
Story
At LACNIC, a New ISP Must Prove Need Before It Can Pay $8,000 for IPv4
LACNIC’s rules ask a first-time operator to show that customers and equipment already justify an address block. Exhaustion then sends that approved need into a private market. The rule is neutral on paper; the sequence is not neutral between a network starting from zero and one…
NPNOG
Who opens the room? What npNOG-10's welcome order can—and cannot—prove
The first twenty minutes of a conference can reveal institutional relationships. They cannot, without supporting records, tell us who held the decisive authority.
History
The Hint That Had to Be Replaced by an Answer: DNS Root Priming
A recursive resolver begins with an awkward form of knowledge: enough addresses to reach the DNS root, but no current root data in its cache. Priming is the small exchange that turns that inherited hint into an authoritative, expiring answer.
IETF
The secret server name still needs a public front door: ECH’s new privacy boundary
Encrypted ClientHello gives a TLS connection two introductions: one the network may see, and one only the service can open. That is a real privacy gain, but it is not disappearance. The destination’s protection now depends on DNS configuration, a shared front door, key rotation…
Story
ARIN’s RDAP Bottom Search Is a Coverage Answer, Not a Leaf List
One query for a `/21` returns a direct `/22` allocation and an administrative `/8`. The result looks upside down only if `rdap-bottom` is mistaken for a list of descendants; its real job is to account for registry coverage.
ICANN
The Forged Letter That Moved Sex.com: Kremen v. Cohen and Network Solutions
A forged instruction did not move a physical entity. It changed the authoritative registration record for a domain name—and forced a federal appellate court to ask what, exactly, the registrant controlled.
Story
LACNIC’s Last Waitlist Applicant Faces 12 Years for at Most 1,024 Addresses
LACNIC’s IPv4 queue does not preserve a block for every approved applicant. It preserves an identity-bound place in a sequence whose supply, order, final approval and address quality remain unsettled until recovered space is actually released.
Story
ARIN’s NET Route List Stops at the Direct Allocation
An empty collection can look decisive until the query boundary is drawn. In ARIN’s routing-registry API, the ordinary NET route list ends at the direct registration; the downstream tree belongs to a different request.
North America Cloud Services Trends
Rollback has not happened until every edge population proves the old decision is gone
A control plane can accept the previous Fastly service version in seconds. The business is not restored until requests across the edge stop encountering the withdrawn rule, artefact or cache decision—and the evidence covers the populations that matter.