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
ARIN’s Board Slate Has One Candidate Beyond Three Seats
Three seats. Four candidates. ARIN’s 2026 Board slate satisfies the rule that there must be more names than vacancies, but it does so at the narrowest possible margin. That fourth name is not decorative competition. It is the point at which an elected choice remains a contest and…
Story
RIPE Atlas Can Show the Edge. It Cannot Show Who Chose It
A path measurement can show where one request landed. It cannot, on its own, reveal the platform rule that sent it there, the traffic that was eligible, the share served locally or what happens when the appliance disappears.
History
The Turnaround Was the Budget: RFC 1986 and ETFTP’s Selective Evidence
On a half-duplex radio path, the expensive event was not merely losing a packet. It was surrendering the channel, synchronizing the other direction, and paying again before useful data could resume. RFC 1986 designed ETFTP around that bill.
Story
APNIC’s Electoral-Committee Recusal Safeguard Lives in a Blog Comment
APNIC has a sensible answer to an awkward governance question: Executive Council members who may seek re-election do not help choose the committee that polices the election. The trouble is not the answer. It is where the answer lives—and how little of the annual record shows the…
Story
LACNIC 46's Attendee List Has Consent. It Still Needs a Retention Clock
LACNIC tells registrants that their names will appear on the event website. That clarity settles the easy argument; the harder one is how a public list shows the scope, duration and outcome of the permission it already has.
Story
AFRINIC Calls Its NS2 Dashboard ‘Real-time.’ All Twelve Linked Measurements Are Stopped One-Offs
A page can refresh on demand without measuring the present. AFRINIC’s public NS2 dashboard illustrates the distinction: it advertises “Real-time Anycast Node Monitoring”, yet every RIPE Atlas measurement wired into the interface is a stopped one-off. The result is useful evidence…
Story
A Backup DNS Plan Is Not a Second Resolver
A 9 September APNIC Blog account turns a household outage into a precise infrastructure lesson: resilience begins only when an alternative service is running, reaches the clients that depend on it, survives a controlled failure and can be rolled back.
Story
RIPE NCC’s K-root Refresh Needs Three Acceptance Records, Not One Batch Status
Amsterdam can be refreshed while the three-site programme remains in progress. That is not a contradiction; it is a warning about the unit of evidence. RIPE NCC has named three K-root core sites whose seven-year-old routers and servers were due for replacement. The useful public…
History
The Packet Stayed Native, but the Dictionary Moved: RFC 1977's Hidden PPP State
A packet capture can show an ordinary PPP datagram while both endpoints quietly rewrite the codebook that will determine the meaning of the next compressed packet. RFC 1977 made that invisible transition a condition of interoperability.
Story
AFRINIC Says It Belongs to All of Us. Its SGMM Notice Draws a Smaller Corporate Boundary
AFRINIC’s anniversary message speaks to members, stakeholders and the wider Internet community in one generous voice. Six days later, the meeting named in that message operated through a narrower set of corporate roles. Both can be legitimate. The governance test is whether a…
Story
LACNIC’s Autonomous-Network Ladder Needs a Scenario Ledger, Not a Company Badge
Two operators can both call themselves level three while describing entirely different machines. One may automate fault diagnosis in a radio network; the other may automate service fulfilment but leave every consequential configuration change to a person. The number sounds…
History
The Header Came Last: How RFC 1963 Reassembled Serial Frames over PPP
RFC 1963 made an unusual bargain with time: send the serial data first, postpone the adaptation header until the packet's end, and let the transmitter decide on segmentation only after compression had revealed the size. What reached the receiver was a grammar for reconstruction…
Story
ARIN’s RPKI Constraint Is Only as Current as the Package That Ships It
A trust boundary can be carefully designed, correctly signed and still arrive too late. ARIN’s planned RPKI constraint work makes that mundane distribution problem part of routing-security policy.
Story
APNIC and NIXI Cannot Close India’s ROV Plan With One Percentage
On 8 September, APNIC Labs could describe India’s observed ROV filtering as 1.14% or 6.03%. Both figures came from the same dated record. The difference was the window—and it is exactly why a national routing-security promise needs a receipt, not a headline number.
History
No Memo Could Command the Network: RFC 1958 and the Right to Change
The most durable sentence in a document about architectural principles may be its warning that the principles will not endure. RFC 1958 treated the Internet less as a monument to be defended than as a city whose streets had to remain open while each block was rebuilt.
History
The URL Carried a Query, Not Its Authority: RFC 1959
In 1996, a directory lookup could be folded into a string short enough to paste into a document or hand to a web client. That convenience was exact but narrow. RFC 1959 could name a server, a place in the directory, the attributes to request, a search scope and a filter. It could…
Story
RIPE NCC Finished the RIS Bare-Metal Move. That Does Not Close the Pipeline
RIPE NCC’s newest RIS plan uses “finished” and “in progress” in the same paragraph, without contradicting itself. The data moved; processing assurance, storage choices, Kafka renewal and a consumer’s latency response sit on different clocks. The useful public record is not one…
Creators
Cricket Liu and the long work of making DNS operable
Cricket Liu’s career follows the Domain Name System from a specialist service run by a small group of operators to an enterprise control plane and, increasingly, a security sensor. His importance lies less in inventing protocols than in explaining how names, addresses, leases and…
History
The Space the Standard Never Required: How POP3 Software Made Compatibility Law
A single blank character can look too small to deserve a history. RFC 1957 showed why it did: once a common server emitted that character on every response, clients learned to depend on it, and a conforming shorter reply became the dangerous case.
History
The Proposal Added a Header. It Refused to Rewrite the Address: RFC 1955
RFC 1955 described a way to make the Internet's routing problem look smaller without pretending that its addressing problem had disappeared. At an entrance border, the proposal would place the original IPv4 datagram inside a second IP header addressed to an autonomous domain. At…