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.
CASE FILE
The Session Grouped Four Streams. It Did Not Reconstruct the Scene: RFC 10034 and Authority over a V3C Representation
Volumetric video does not travel as one self-sufficient picture. It can arrive as an atlas plus occupancy, geometry and attribute streams, each with its own packets and failure state. RFC 10034 gives those parts a shared transport grammar. It does not appoint any one green…
CASE FILE
The Header Asked for a Stream. The Proxy Still Owned the Flush: RFC 10036 and the Authority to Release an HTTP Message
A sender can place `Incremental: ?1` at the front of an HTTP message and begin producing useful content immediately. That does not make the path a pipe. Every intermediary still controls a parser, a security decision, a capacity limit and a buffer. RFC 10036 turns the sender's…
Story
LACNIC's Delegation File Declares 49,894 Records. It Contains 48,214
A daily file built for machines fails the counting rule printed in its own specification, while its automatic alias and its dated signature offer two different paths to trust. The discrepancy is not evidence of missing Internet resources. It is a test of whether a registry…
CASE FILE
The Server Issued a Locator. The Network Had Not Yet Accepted the Route: RFC 10038 and the Authority to Allocate SRv6 Reachability
A DHCPv6 Reply can make an SRv6 locator administratively real in a few fields: who received it, how it is divided and when it expires. The packet path is harder. A route still has to be installed, advertised, selected, programmed, filtered and joined to a local SID behavior. RFC…
CASE FILE
The Token Matched. Permission Still Had to Be Checked: WebDAV Lock Tokens and Write Authority
A WebDAV client can present the exact token for a live lock and still be correctly refused. That is not a contradiction in the protocol. It is the point at which a coordination marker stops and authority begins.
CASE FILE
The Registry Published the TTL. The Resolver Kept Its Own Clock: RFC 10037 and the Authority to Describe a DNS Change Window
A registry can now place a delegation TTL in an RDAP response, where an operator can read it without querying the DNS. The number is useful precisely because its authority is narrow. It describes what the registry database has provisioned; it does not reveal how many seconds…
CASE FILE
The Cache Told You It Was a Hit: Cache-Status and the Authority to Explain a Response
Cache-Status gives every cache in an HTTP path a common way to describe its part in delivering a response. That makes incidents easier to investigate, but it also creates a tempting mistake: treating the system's own explanation as if it were independent proof.
CASE FILE
The Message Was Accepted Before It Was Released: IETF's Mail Transition and the Authority to Hold, Rewrite and Relay
On 11 September, a first-time sender may hand a message to the IETF's mail system and receive an apparently ordinary SMTP outcome while the operational copy waits elsewhere for a challenge response. That gap between acceptance and release is the real story in the IETF's new email…
Story
ARIN’s ROA Alerts Follow Deletion, Not the Change in Routing Authority
ARIN can commit several routing authorizations in one transaction, yet its documented alert boundary still follows a single verb: delete. Two public suggestions expose the resulting choice between inbox noise and silence. A safer design would report the net change once.
Story
APNIC Sold 6 Cordelia. Its RPKI CPS Still Says APNIC Owns the Building
Five days after APNIC announced that it had sold its South Brisbane office, two prominent registry contacts acquired fresh modification times and the unchanged post-office-box address. Yet the RPKI practice statement served from APNIC’s long-lived URL still says the registry owns…
CASE FILE
The Method Was Safe. The Body Still Defined the Request: HTTP QUERY and the Authority to Name an Equivalent Resource
HTTP has long forced complex read operations into an awkward choice: expose the query in a GET URI, or carry it in POST content and surrender the assumptions attached to a safe, idempotent method. RFC 10008 introduces QUERY as a third path. Its promise is precise, but so is its…
CASE FILE
The Network Changed Before the Decision Became Final: NETCONF Confirmed Commit and Rollback Authority
NETCONF can place a candidate configuration into active use while a timer still gives the server authority to restore the previous state. That provisional success is useful precisely because a protocol acknowledgement, a final datastore and a functioning network are different…
CASE FILE
The Query Changed. The Cache Answered Anyway: No-Vary-Search and the Authority to Declare URL Equivalence
Two addresses can look different while an application treats them as the same page. No-Vary-Search lets an origin expose that knowledge to caches. The tempting story is fewer misses. The operational story is harder: one party declares which distinctions do not matter, another…
CASE FILE
The Answer Was Not Ready. The Browser Could Still Move: HTTP 103 Early Hints and the Authority to Speculate
A server can reveal a likely stylesheet before it knows whether the request will end in a page, an error or a redirect. HTTP 103 gives that provisional clue a place on the wire. The clue can save time, but it cannot become the answer: the client still decides whether to spend…
Story
RIPE NCC's New CTO Inherits a €12.2m Estimate, Not a Mandate
Sjoerd Wolthers becomes RIPE NCC's permanent chief technology officer on 1 September. The appointment settles who will lead the technology function. It does not settle a separate question left open in the latest public Board minutes: whether, how and on what evidence RIPE NCC…
Story
LACNIC's Four-Vendor BGP Claim Needs the Configuration Column
One malformed Prefix-SID attribute reportedly met three different actions as it crossed the Internet: discard, propagation and session reset. LACNIC's new routing-security article makes the divergence visible. To make it reproducible, the comparison now needs to name the release…
CASE FILE
The Error Returned as a New Question: DNS Report-Channel and the Authority of Feedback
An authoritative server can announce where it wants to hear about failures it cannot see. It cannot make a resolver diagnose, report or believe anything. DNS Error Reporting turns one local validation failure into a second DNS query, then leaves transport, caching and human…
Story
At ARIN, Resource-Level Tech Authority Stops Before the ROA
ARIN's records can give a Technical Point of Contact authority over one network resource while routing-security actions remain organized around the containing organization. A newly confirmed suggestion asks ARIN to bridge that gap. The hard part is not adding another permission…
CASE FILE
The Packet Hid Its Exact Length. The Pattern Still Spoke: EDNS Padding and the Limits of DNS Privacy
An encrypted DNS message can conceal its names and answers while leaving a surprisingly useful silhouette. EDNS Padding changes that silhouette by adding bytes. The difficult question is not whether the packet became larger, but whether client, server, transport and path made…
Story
One Source IP Accounted for 38.76% of APNIC's WHOIS Queries in an Hour
One Source IP Accounted for 38.76% of APNIC's WHOIS Queries in an Hour 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.…