Content Type
Long Form Analysis
Within the Content Type facet, Long Form 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.
IETF
David Meyer and the Address That Had to Ask Where It Lived
LISP lets an endpoint keep one identifier while its network attachment is described separately. That does not make location disappear. It moves forwarding into a chain of registered, resolved, cached, selected and reachable EID-to-RLOC state—and turns each link in that chain into…
IETF
Alan DeKok and the RADIUS Variant That Moved Trust into TLS
RFC 9765 is unusual not because it promises a clean break, but because it records a protocol author revisiting a choice he helped make: Alan DeKok's RADIUS/1.1 removes old packet-security machinery only where two peers explicitly negotiate a protected transport profile. The…
IETF
Clarence Filsfils and the Segment List That Learned to Share an Address
An SRv6 path can be perfectly explicit and still carry waste: the same locator block repeated across instruction after instruction, plus zero padding that moves through the network without adding a decision. RFC 9800 removes that repetition. Its deeper achievement is to specify…
Story
ARIN's Single-Site `/48` Lived in an Example Before It Reached the Rule
One site filled 100% of the `/48`s inside a `/48`. The sentence therefore pointed to `/44`; the example did not. ARIN-2025-7 repairs that small contradiction, and in doing so reveals a larger rule: examples must never become the hidden execution layer of number policy.
Story
RIPE's IPv6 PI Draft Has a Trigger but No Transition Receipt
Nine `/48` assignments can remain a valid deployed state while nothing changes. The next request for address space is different: it can activate a next-nibble decision, a contiguity test, a new prefix and a six-month return clock. Proposal 2024-01 names that trigger but does not…
Story
LACNIC's Anti-Fake-IXP Log Has No Event Column
LACNIC has made a scarce IPv4 reserve unusually visible. Its public file can show who holds an issued interval and how much of the pool remains reserved. What it cannot say in one row is what happened. A log commissioned to cover assignments, recoveries and returns still…
Story
ARIN's ISP/LIR Claim Needs a Predicate Ledger
One card asks what a company sells. Another asks whether it receives and redistributes Internet number resources. Draft Policy ARIN-2025-1 wants every holder of the first card to fit inside the second. Its proposed definitions do not yet make that containment rule true.
Story
APNIC Would Remove `/23`; Three Prefix Sizes Still Need Names
One bit separates a `/23` from a `/24`. It also separates 512 IPv4 addresses from 256. APNIC's current initial-LIR test can ask for immediate need for the smaller block and a one-year plan for the larger one. Prop-169 would repair that mismatch. Its replacement noun now needs an…
Story
AFRINIC Draft 2 Can Waive 90%; “Sufficiently Documented” Has No Fields
AFRINIC recorded the second-data-centre trap in 2018. An End User wanted another `/24` for redundancy, had used less than 90% of its existing space and was therefore ineligible. Draft 2 finally names that class of problem, then leaves the proof inside two words: sufficiently…
Story
Khipu's Local Archive Preference Creates an Evidence Expiry Boundary
A historical Khipu view can reach farther back than the archive shelf available on the workstation opening it. Once the number of local `ip2asn`, `ixp`, `ip2country` and `asn2country` snapshots is a preference, reproducibility has an expiry boundary that the measurement date…
North America Cloud Services Trends
AWS EBS in 2011: recovery capacity as accountability
A network change in one Availability Zone exposed a deeper continuity problem: redundancy can become a source of load when many replicas try to heal at once. The 2011 EBS disruption shows why recovery capacity, shared control paths, isolation, and verifiable closure belong inside…
North America Institutional Trends
Jim Mankowich and the Campus Wireless Choice That Preserved Voice Service
When Lawson State Community College planned a campus-wide wireless network in 2009, the hard question was not simply where to put access points. The college already carried voice calls over its network. Students and employees needed different traffic boundaries. Old buildings, a…
Europe and Middle East Regional ISP Trends
Florian Obser and the Incremental Rebuild of OpenBSD Network Configuration
When a broad plan for one network-configuration service proved too ambitious, Florian Obser helped turn the unfinished idea into smaller working parts. The result was not a clean victory over complexity. It was a sequence of bounded changes, explicit trade-offs, and…
Leaders
Pim van Pelt and the Decision to Sunset SixXS
Many infrastructure stories celebrate the moment a system starts. Pim van Pelt's more instructive story turns on the moment he and fellow operator Jeroen Massar decided that SixXS should stop. The service had helped people reach IPv6 when their providers did not offer it…
Asia-Pacific Cloud Services Trends
Daniel Pearson and the Operating Choices Behind PingCo
Daniel Pearson’s contribution to PingCo is best understood as a set of operating choices, not a single growth claim. Public records identify him as the company’s founder and chief executive. Partner and company accounts describe two connected moves: placing managed infrastructure…
North America Cloud Services Trends
Brad Walser and the Local Operating Choices Behind Walser Technology Group
Brad Walser’s public record is useful precisely because it is modest. Walser Technology Group describes a locally focused managed-services company built around flexible contracts and technical capacity kept near its customers. An N-able interview presents Walser’s account of…
Global Regional ISP Trends
Timur Bakeyev and the Maintenance Work Behind Network Identity Continuity
The visible milestones of Internet infrastructure are launches, standards and major security incidents. Timur Bakeyev's documented record points instead to the quieter work between those moments: adapting identity-related software to different systems, keeping packages buildable…
Leaders
Renato Barbiero’s Documented Path from Radio Licensing to ASN Responsibility
Renato Barbiero’s Documented Path from Radio Licensing to ASN Responsibility 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…
Leaders
How Bill Woodcock’s APNIC Proposal Changed IXP Addressing Rules
Internet exchange points let independent networks exchange traffic at a shared facility instead of sending every packet through a distant transit provider. That practical arrangement still depends on number-resource policy: exchange equipment needs addresses, entities need…
Leaders
Giovanni Di Clemente on the Fibre Cut That Tested Local Operator Continuity
A regional internet outage is rarely explained by one company, one cable, or one engineer. In June 2018, an Abruzzo publication identified Giovanni Di Clemente as a Telweb engineer and quoted his estimate that a severed backbone fibre had affected 40,000 to 50,000 users. It also…