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.
Europe and Middle East Cloud Services
AlmazCloud's AS210328: What the Routing Record Now Shows — and What It Still Doesn't
AlmazCloud's AS210328: What the Routing Record Now Shows — and What It Still Doesn't intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences…
Story
AS210764: a root-server ASN that no global router can see
AS210764: a root-server ASN that no global router can see 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 follow. The Story…
Europe and Middle East Regional ISP
DATAMATIX and AS210973: Closing the Evidence Chain From Registry Record to Operating Business
DATAMATIX and AS210973: Closing the Evidence Chain From Registry Record to Operating Business intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…
Global Institutional
BIND 9 repair ends where ISC's support boundary begins
Internet Systems Consortium draws three lines that decide whether a BIND 9 defect becomes a repair: which release branches stay in support, which severity earns a public advisory, and which single monthly release carries the patch. Dated records from ISC, from Debian's packaging…
CASE FILE
The SID Was Compact. The Path Authority Was Not: RFC 9631
RFC 9631 can express an IPv6 path with 16- or 32-bit segment identifiers. The saving is real, but the meaning of each short number lives in a local forwarding table whose version, owner and execution are not carried in the packet.
IETF
The flags were all there. The connection history was not
A flow record can report SYN, ACK and FIN in one tidy bitmap. RFC 9565 makes that report more interoperable and future-proof, but it does not turn the bitmap into a transcript of the connection that produced it.
CASE FILE
The Reference Graph Arrived. The Picture Did Not: RFC 9628
VP9 over RTP can disclose how one picture depends on another, packet by packet or through a recurring structure. That map is valuable, but it is not a receipt for complete delivery, successful decoding or the image a viewer actually saw.
IETF
The packets arrived in order. The network still had not proved the whole history
RFC 9566 gives DetNet IP a practical way to replicate packets, remove duplicates and restore order through MPLS over UDP/IP. Its machinery can improve service protection, but the clean sequence leaving an ordering function is a local result, not a complete receipt for path…
IETF
The router became Active. The path still had not proved it could carry traffic
RFC 9568 can move a virtual first hop from one router to another in seconds. Its state machine decides who should speak for the address; operators still need separate receipts showing that the new speaker can move the packets.
CASE FILE
The Sequence Number Did Not Decode the Picture: RFC 9627
A Layer Refresh Request can name the exact upgrade a receiver wants and repeat that command reliably. It still cannot certify the encoder's action, the packet path or the layer that finally reached the screen.
IETF
The update graph was complete. The network verdict was not
RFC 9569 gives ALTO clients a disciplined way to retrieve changing network information. It preserves a server’s version history; it does not certify the observation, the client decision or the traffic result.
CASE FILE
The Video Was Encrypted. Its Frame Decisions Were Not: RFC 9626
An RTP switch can make useful forwarding decisions without seeing a conference's video. RFC 9626 gives it a small map of frame boundaries and dependencies. That map is authenticated metadata, not an independent witness to what the encrypted picture actually contains or what a…
IETF
The token was valid. The reason for opening the gate was still missing
RFC 9578 lets an issuer mint a token without learning the token itself. The cryptography proves a narrow past act; authorization and delivery remain decisions of other systems.
CASE FILE
The Connection Was Ready. The Policy Decision Was Still Hidden: RFCs 9621–9623
A transport abstraction can choose among addresses, interfaces and protocols without forcing the application to know every mechanism. That is a genuine engineering gain. It also means that a green `Ready` event can arrive after a consequential choice whose inputs, rejected…
IETF
The timestamp carried a guarantee. The clock never showed its work
RFC 9581 can encode a precise instant, its timescale and a claimed error bound in one compact CBOR entity. That makes the claim portable; it does not make the clock trustworthy.
CASE FILE
The Verdict Stayed the Same. The Validator Ran Out of Memory: RFC 9618
A certificate regression suite can return every expected verdict and still miss the failure that matters in production. RFC 9618 shows why semantic correctness and bounded execution are separate obligations: the old X.509 policy tree and the new policy graph can accept the same…
IETF
The photons survived the suburbs. The application case still needs proof
NIST’s 62-kilometre entanglement test is valuable running evidence. RFC 9583 shows why it is only the first receipt in a much longer chain from quantum link to useful service.
CASE FILE
The Route Cost Fell. The Service Did Not Improve: RFC 9616
The routing dashboard marked the new path as cheaper after its RTT samples settled. The application trace still showed slower transactions and deeper queues. Nothing was necessarily broken: RFC 9616 standardises a disciplined way to turn neighbour delay into a Babel cost, not a…
IETF
Every packet arrived. The picture still did not exist
RFC 9584 gives EVC video a rigorous RTP transport grammar, but a clean packet trace ends before decoding, rendering and the viewer’s screen.
CASE FILE
The Data Was Split. The Operator Could Still Reassemble the Person: RFC 9614
The relay could identify the client but could not read the request. The gateway could read the request but could not see the client's address. Then one operator aligned the two logs by time and size. Every box kept its local promise; the system did not keep the privacy promise.…