Primary Domain
Internet Infrastructure
Within the Primary Domain facet, Internet Infrastructure intelligence groups reporting by primary domain so readers can follow a focused area of internet infrastructure, governance, connectivity markets, or digital capital. The page brings together related articles, public evidence, institutions, companies, people, regional exposure, operating dependencies, and market context that may otherwise sit across separate category pages. It explains the domain, the likely actor class, the market or governance context, and the source material readers should use when comparing signals. Operators, analysts, and governance readers can see how the same domain appears across events, profiles, market shifts, public-source evidence, regional dependencies, and longer-cycle infrastructure decisions over time.
Latin America and Caribbean Institutional Trends
RRC24 Timed Out at Startup. Recovery Needs Its Own Load Test
RIPE NCC has traced a routing-data publication interruption to unusually heavy starting work. The useful management question is now what load a recovered service has actually proved it can finish.
Story
A LACNIC Telecom Essay Moves Voice to IP. It Leaves Backup Power Unassigned.
A new LACNIC Blog essay catches the most consequential detail in the retirement of traditional telephony: the call may look unchanged, but its power supply has moved. That observation deserves a more exact public answer about who keeps an IP call alive when the lights go out.
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…
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…
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…
Creators
Roy Arends and the hard work of changing DNS safely
Roy Arends helped write the 2005 specifications that made modern DNSSEC interoperable across implementations. Two decades later, his work at ICANN focuses on a harder operational problem: changing keys, error signals and delegation in a global system that no organisation can…
CASE FILE
A DNS Failure Drew 51 Queries. The Cause Was Still Unresolved
APNIC Labs sent several kinds of “no” from an experimental authoritative DNS service. Definitive negatives drew roughly four queries per test. `SERVFAIL` drew 51.73 and silence 83.46. Those are measurements of received traffic—not a verdict on which resolver layer multiplied it.
History
Before Renumbering Had a Procedure, It Had a Field Diary: RFC 1916
Most RFCs are remembered for an answer. RFC 1916 deserves attention because it published a question. In February 1996, the IETF's PIER working group needed practical guidance for changing enterprise IP addresses, but it did not pretend that a standards room already possessed the…
CASE FILE
The Purge Was Accepted. The Downstream CDN Still Said No
Revision 20 of an IETF working-group draft follows a cache-control request past the reassuring `201 Created` response. In a CDN cascade, a later rejection has to return as data inside another provider’s status resource—and the provider that refused may remain unnamed.
Creators
Roy Arends and the hard work of changing the DNS safely
Roy Arends helped write the 2005 specifications that made modern DNSSEC interoperable. Two decades later, his work at ICANN centres on a harder operational problem: changing keys, error signals and delegations across a global system that no institution can update by command.
History
The Assurance Was Public. The License Form Was Not: RFC 1915
A standard can be open to inspection while a decisive commercial term remains behind the next conversation. In 1996, the IETF published Motorola’s assurance that licences for claimed patents affecting two PPP control protocols would be available on reasonable and…
CASE FILE
The ICMP Error Named a Node. It Did Not Prove Which One
Revision 05 of an IETF draft makes node context harder to omit when an ICMP source address cannot do the diagnostic job alone. It also exposes a less comfortable truth: a more informative error can carry less of the packet that triggered it, and neither piece is authenticated.
Leaders
Mohamed Awang Lah and the Problem of Making Internet Capability Survive Institutional Change
The most revealing question about Mohamed Awang Lah is not whether he was important to Malaysia’s early internet development. The public record makes his importance difficult to dispute. The harder question is what, precisely, survived his successive roles: a person’s authority…
IETF
One CA Name, Several Ways to Issue
A buyer reviewing certificate operations asks a simple question: if DNS authorizes one certification-authority name with an account and a validation method, does that restriction govern every issuing system behind the name? RFC 8657 makes the answer consequential. A shared CA…