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
AFRINIC’s Two-Day Service Clock Opens on Three Different Maps
AFRINIC promises an effective response within two working days. Yet a correspondent choosing where to send a request meets twelve queue labels, sixteen specialist addresses, or three broad contacts and a general form. The commitment needs a public map between the front door and…
History
The Switch Offered a Shortcut. The Router Could Refuse: RFC 1953
In RFC 1953, the faster path began as a neighbor's request, not a command. A downstream node chose a label from its own local space and asked the upstream node to attach it to a defined IP flow. The upstream node could ignore the request. Even acceptance lasted only for a stated…
History
The File Ended, Then Continued: RFC 1952 and Gzip's Member Boundary
A `.gz` filename suggests one entity. RFC 1952 describes something more interesting: a procession of self-closing members. Finish one, place another immediately after it, and a decompressor can continue as though the file had acquired a new chapter. The old compressed bytes need…
Story
LACNIC’s Abuse-Contact Lockout Sits Outside the Policy Manual
LACNIC’s policy manual says when an abuse contact becomes noncompliant. A separate help page says the consequence is blocked access to MiLACNIC. The missing entity is not another reminder email. It is the public record that joins a rule to the administrative control it activates.
History
The Key Centre Disappeared into the Tree. Its Authority Did Not: RFC 1949
Scaling usually sounds like subtraction: remove the bottleneck, spread the work, let the network carry the rest. RFC 1949 did spread multicast key distribution, but it could not subtract trust. By letting authenticated tree nodes pass group secrets and authorise later joins, the…
History
The Password Was Correct Once. Acceptance Changed What Correct Meant: RFC 1938
Passwords usually sound like facts: either the claimant knows the right string or does not. RFC 1938 made that description incomplete. In its one-time-password system, a correct answer was consumed by success. The server replaced the value against which the next answer would be…
Story
ARIN’s RPKI Failover Test Left the Dependency Question Open
ARIN blocked access to its RPKI repositories for an hour, restored it, confirmed redundancy five minutes later and reported a return to baseline after another fifteen. That is unusually concrete resilience evidence. It is also narrower than the dependency question ARIN had…
History
The Server Pool Was Redundant. The Address Authority Was Singular: RFC 1931
A workstation with no configured address asks a question that looks deceptively small: which IP address may I use? RFC 1931 answered with several servers, but not several truths. Dynamic RARP separated the machines that could hear and answer a request from the authority allowed…
Story
APNIC’s WHOIS Archive Reports Two Totals for the Same Hour
The latest completed hour says APNIC received 3,192,583 WHOIS queries. Add the seven query types printed beside that total and the answer is 3,183,463. The missing bridge is not a rounding error; it is the meaning of the measurement.
History
The Gold Paper Clip Looked Decorative. It Was a Workflow Command: RFC 1927
A paper clip is legible before anyone explains it. That was the charm of RFC 1927—and the trap hidden inside its joke. The memo asked one office-supply icon to express whether documents belonged together, how they should look, which workflow should run, where an annotation…
History
The Packet Had an Alphabet and a Pitch, but No End Marker: RFC 1926
RFC 1926 could turn every nibble of an IP datagram into a Morse letter and place it on a chosen audio frequency. The difficult part begins after a receiver hears the start signal: when, exactly, has the packet ended? That small silence exposes the distance between a reversible…
Story
AFRINIC’s RPKI Guide Names a Validator Retired in 2021. The Link Now Runs Routinator
The hyperlink works. That is precisely why the documentation error is easy to miss: AFRINIC’s main RPKI guide preserves the name of one product while sending the reader to a different implementation.
History
The RFC Called Them Truths. The Errata Kept Them Opinions: RFC 1925
A missing period can be verified. A universal truth cannot. That unexpectedly precise distinction appears in the errata record of RFC 1925, the April Fools’ document that gave networking twelve durable aphorisms. The archive can repair its punctuation and preserve its jokes; it…
Story
RIPE Atlas Says “Dissimilar” Probe Selection Is Complete. Its Public API Does Not Name the Selector
RIPE Atlas Says “Dissimilar” Probe Selection Is Complete. Its Public API Does Not Name the Selector intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…
History
Twenty Characters Made the Address Shorter and the Evidence Harder to Read: RFC 1924
The log search returned nothing. The address was present, the 128 bits were unchanged, and the parser could reconstruct them exactly. Only the spelling had moved—from familiar colon-separated hexadecimal to twenty symbols dense with punctuation. RFC 1924 made IPv6 shorter. Its…
Story
LACNIC Deferred Its $2,100 IPv6-Only Fee to 2029. The 2020 Notice Still Ends the Waiver in 2026
The lower 2026 price is not an accounting mistake. It is the result of a unanimous Board decision that shifted the final step of LACNIC’s IPv6-only discount from 2026 to 2029. The documentary problem is quieter: the original notice remains public with the old endpoint, while the…
History
Every Line Returned to ASCII So the Middle Could Be Read: RFC 1922
Open a long Chinese message at line twenty. If that visible line depends on an escape sequence hidden nineteen lines above, scrolling has become a decoding hazard. RFC 1922 answered with deliberate repetition: a Chinese line declared the character set it needed and returned to…
History
The Second Request Was Deleted. Its Error Had to Wait: RFC 1921
A second printer request arrived before the first had finished. TNVIP did not queue it, number it or let it overtake. The receiver deleted it—and postponed the protocol-violation response until the first request had received its own answer. RFC 1921 used three small, separate…
Story
AFRINIC’s 2025 Receivables Were Almost All Past 60 Days. June’s Zero Bad-Debt Line Does Not Close Them
A dash can look like an ending. AFRINIC’s first-half 2026 report shows no actual bad-debt expense, yet its last audited balance sheet carried USD 561,761 of gross trade receivables more than 60 days old. Those are different accounting states. A privacy-safe cohort rollforward…
History
Both Networks Were Correct Until They Met: RFC 1918 and the Price of Local Uniqueness
At 09:00, two enterprise networks can each be orderly. Each has one machine at the same private address, one route toward it and one name that resolves correctly. At 09:01, an interconnection comes up. Nothing inside either machine has changed, yet the address can no longer…