Content Type
Analysis
Within the Content Type facet, Analysis 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.
Story
RIPE NCC’s AuthDNS Ledger Counts 43 Nodes but Not the Eyeball Coverage They Deliver
RIPE NCC has made the objective unusually clear: put AuthDNS where poorly served networks can actually reach it. Its public inventory can show that 43 hosted instances are operational. What it cannot yet show is whether each new map pin changed the anycast catchment that matters.
Story
RIPE’s IPv6 PI Draft Reserves Growth Space. Partial Transfers Can Make It Unusable.
RIPE’s current IPv6 PI proposal tries to make future growth easier by reserving a larger nibble-boundary envelope around a new assignment. Its own impact analysis identifies the catch: if the assigned block can be transferred in pieces, the untouched reservation may no longer be…
Story
LACNIC’s IPv6 Clock Subtracts 210 `/32`s Without Showing Which Fragments Count
IANA’s allocation clock for LACNIC reaches a reassuringly precise answer: 978,428 units of `/32` space remain available. The public rows beneath it supply exactly the 210-unit subtraction that produces that number. Yet most of those fragments are not labelled `available` in…
Story
ARIN Says Sponsors Need 60 Days. Its ARIN 58 Page Is Still Open at 42.
ARIN’s sponsorship page presents an opportunity and a cutoff as if both were current: it is seeking sponsors for ARIN 58, yet says sponsorships must be finalized 60 days before the event. The page served after that boundary needs one more field—a dated status that says what, if…
History
The Binding Was Accepted; the Location Was Not Proven: RFC 2002
Mobile IP’s first standards-track design separated a durable network identity from a temporary delivery instruction. The home agent could authenticate and accept that instruction, yet neither act proved where the device physically was—or that a packet completed its journey.
Story
ARIN’s ASPA Change Is a Set Decision. It Needs a Diff Receipt
Changing one upstream in an ASPA is not the digital equivalent of adding a name to a contact list. The operator is replacing a signed statement about the whole provider set. ARIN can acknowledge the transaction, yet the operator still needs evidence of what changed, what was…
Story
LACNIC’s Highest Risks Have Two Clocks and No Public Start Point
LACNIC has put unusually sharp time limits around its most serious residual risks. Its public Board record says what must happen immediately, within 90 days and in less than 120 days. What it does not publish is the event from which either clock is counted—a small omission that…
Story
APNIC Reported 60 Atlas Probes Distributed and 23 Deployed. The Missing Unit Is the Cohort
A probe in a box is an opportunity to measure the Internet. A probe that has connected, remained available and filled a blind spot is measurement capacity. APNIC’s 2025 reporting places 60 distributed devices beside 23 deployed ones, but does not publish the join that would tell…
Story
APNIC's NIR Co-Chair Was Re-elected Without an Online Ballot—By Rule
APNIC 62's linked result sheet contains four polls but no NIR SIG contest. That blank is not a missing tally. It is the visible edge between two procedures: contested positions go to the online system; one confirmed candidate goes to acclamation in the SIG room.
Story
AFRINIC’s Green Status Page Leaves a Website Incident in “Recovering”
AFRINIC’s public status API says every system is go. The same API says a July website incident is still present, still recovering and has never ended. Both statements cannot serve as the final operational record without a rule that explains how they reconcile.
Story
AFRINIC's Arabic Policy Index Returns 404 While English Tracks Seven Live Proposals
A policy register can be authoritative in one language and still become unreliable evidence in another. On 11 September, AFRINIC's English current-proposals index answered normally; the official Arabic route did not answer with an older table, a move notice or an English…
Story
Rapport Tests Cache Survival. Its Missing-Manifest Warning Is Still Commented Out
LACNIC’s young RPKI test suite preserves the right routes when a manifest disappears; the quieter question is whether the person responsible for those routes is demonstrably told why they are now coming from cache.
Story
RIPE NCC's Archived May GM Page Is Showing October's Live Registration Table
The October 2026 General Meeting page carried a live country-by-country registration count. At the same instant, the archived page for May displayed precisely the same 37 rows and 231 votes, although May's final report records 3,421 registrations and 3,049 ballots cast. The…
History
The List Expired on 16 June: RFC 2000 and the Two Axes of Protocol Status
RFC 2000 was itself an Internet Standard, yet it carried a use-by date. That was not a paradox. The document was authoritative as a dated classification, not a permanent measurement of what the Internet had implemented.
Story
ARIN’s 2026 Candidate Forum Page Still Carries the 2025 Voting Window
ARIN opened registration for an October forum on its 2026 Board candidates. The event page gets the year, forum date and subject right, then tells readers that voting runs from 30 October through 7 November—the window ARIN published for 2025, not the 22–30 October window on its…
Story
RIPE NCC's Admin WebUI Fills Automation Gaps. Retirement Needs an Exception Ledger
The revealing phrase in RIPE NCC’s current registry plan is not “technical debt” but “admin-like capabilities”: the old interface carries operational exceptions that a cleaner replacement could otherwise erase from view.
History
The UDP Table Knew the Port, Not the Conversation: RFC 2013
RFC 2013 gave a network manager two kinds of sight: four odometers for an entire UDP engine and a list of local doors where applications were listening. It could say that a door existed and that traffic totals moved. It could not say who stood outside, which process answered, or…
History
A CHAP Success Proved One Comparison, Not the Connection: RFC 1994
The decisive packet in CHAP was called Success. Its name sounded broader than its evidence: one authenticator had compared one response with one locally calculated value for one challenge. RFC 1994 made that comparison useful by binding it to time and direction—and left every…
Story
LACNIC Listed 32 Resources for December Revocation. That Is Not 32 Cases.
A new LACNIC cohort places 32 number-resource records on one 90-day clock. The table is useful precisely because it is public. Its limit is just as important: a row identifies a resource, not the recovery case behind it.
Story
APNIC Closed Its CentOS Workstream. The Evidence Chain Still Has Four Open Joins
APNIC can point to a genuine finish line: in the second quarter of 2026 it completed a multi-year move away from end-of-life CentOS hosts. Its wider security record is less linear. Tests, findings, classifications and exercises appear in separate reports, but the public evidence…