Primary Domain
Infrastructure
Within the Primary Domain facet, 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.
IETF
QNAME Minimisation Makes Each DNS Delegation See Only What It Needs
A root server does not need an entire host name to point a resolver toward the next delegation. QNAME minimisation turns that observation into a disclosure rule: reveal the name one boundary at a time, measure fallback, and never confuse less upstream exposure with privacy from…
Europe and Middle East Regional ISP Trends
A digital landline is resilient only for as long as its backup path
The power fails at eight in the evening. The Digital Voice account is active, the number has migrated and a battery unit sits beside the router. An hour later the battery is empty. Or the router remains lit while the fibre modem does not. Or the cordless base and the telecare…
CASE FILE
The Revision Was Newer. It Was Not a Descendant.
A resolver needs a capability introduced on one branch of a YANG module. It accepts a revision dated later than the recommended minimum, yet that revision belongs to the sibling branch and never inherited the capability. The calendar comparison worked. The ancestry test never…
IETF
The ACK Did Not Arrive: TCP's Retransmission Timer Discipline
A missing ACK does not tell a TCP sender whether data was lost, merely delayed, or acknowledged by a packet still in flight. RFC 6298 turns that ambiguous silence into a controlled decision: estimate, wait, retransmit once, then become progressively more cautious.
Story
A Court Order Is Not a Registry Runbook
A court can determine rights and impose duties. It does not thereby describe every safe registry, credential and routing step. LACNIC needs a disciplined bridge from legal command to operational execution.
CASE FILE
The Version Number Promised Compatibility. It Had Not Tested the Device.
A controller sees a YANG module version above its recommended minimum and admits a change. The target then lacks the node the workflow expected—not because the version comparison lied, but because it answered a question about artifact lineage rather than the exact schema and…
CASE FILE
The files matched. The authority did not
An RPKI Signed Checklist can bind exact file bytes to a declared set of Internet Number Resources. That is a useful and unusually precise proof. It is also much narrower than the green result can appear: the entity does not identify a company, certify a document's truth, prove a…
CASE FILE
The Counter Named the Discard. It Had Not Proven the Cause.
Two interfaces report the same standardized discard class during one service degradation. At the first, a deliberate access rule is doing precisely what its owner intended. At the second, an old rule is catching valid traffic after a routing change. The labels agree; the…
CASE FILE
The Extension Was in IANA’s Registry. The Server Still Had Not Promised to Accept It.
A registrar’s integration system finds an `Active` EPP extension in IANA’s public registry and enables the command path. The next registry server’s greeting does not advertise the extension namespace. The specification is real and the catalogue is correct; the automation has…
CASE FILE
Two validators agreed on the version. They did not agree on the routes
Two RPKI validators can report the same RRDP session and newest serial while retaining different repository histories. The disagreement becomes visible only if they remember what hash an already-seen delta carried before. RFC 9697 turns that memory into an operational control…
CASE FILE
The Packet Carried the Action. One Router Could Not Read Far Enough to Perform It.
A correctly formed MPLS packet enters a path with a hop-by-hop action in a post-stack header. The first router finds and performs it. A middle router sees the in-stack indication but cannot read the entire post-stack container, so it skips that processing and forwards the packet.…
CASE FILE
The Device Said “Adult.” It Did Not Prove Who Was Holding the Family Tablet.
A child resumes a browser session left open under an adult profile on a shared tablet. The site requests an over-18 signal; the device returns a valid affirmative answer. No identity dossier crosses the network, yet the answer describes the enrolled context rather than the person…
CASE FILE
The Header Asked the Proxy to Stream. It Did Not Prove the First Event Moved.
An origin opens a Server-Sent Events response, sets `Incremental: ?1` and emits its first event. One proxy understands the field and forwards every arrival. The next proxy has never heard of the field, so it waits for the complete response. The response is designed never to…
Europe and Middle East Regional ISP Trends
A broadband switch is complete only when both bills agree
The new router is online. Video calls work. The old provider’s next bill still treats the previous line as active after the switch date.
CASE FILE
The Library Named a Direct Modifier. It Did Not Calculate the Dependency Graph.
Module B inserts a container into Module A. Module C then inserts a leaf into B’s new container. RFC 10035 lets the server report B as a direct augmenter of A and C as a direct augmenter of B. It deliberately does not place C on A’s list. The new inventory exposes immediate…
IETF
Ten Segments Before the Network Answers: TCP's Initial Window Bet
A new TCP sender once waited for the path to reveal itself three or four segments at a time. RFC 6928 permitted a first flight of ten. That shortened many small transfers, but it also concentrated more traffic in the only moment when the sender had almost no evidence about the…
Story
The Estate Cannot Route Itself
A liquidator can inventory equipment, contracts and claims. That does not make an Internet number delegation an ordinary asset that moves merely because a sale schedule says so. Insolvency creates two records that must meet: the court-supervised estate and LACNIC's…
CASE FILE
The Charter Opened a Work Queue. It Did Not Migrate a Certificate.
The LAMPS charter now contemplates an unsigned X.509 certificate as a slimmer way to carry trust-anchor subject information. Removing a self-signature can save expensive bytes. It does not make the container trusted, choose a post-quantum algorithm or move one relying party.…
CASE FILE
The Policy Named a Partition. It Did Not Reserve the Resources.
Two candidate paths can point to the same endpoint while carrying different Network Resource Partition identifiers. One 32-bit value changes which underlay resources the headend is meant to invoke. The BGP field can state that association; it cannot create the resources, install…
CASE FILE
Fourteen ACKs Did Not Prove a Window of Twenty-Four
An application sends ten segments, pauses, then supplies four more. Every segment is acknowledged. A naive slow-start counter can call the resulting congestion window twenty-four, although the path has never carried more than ten in one round trip. The IESG has now approved a…