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 Label Named the Encoding. It Did Not Name the Schema: RFC 9996 and Authority Behind a Protobuf Payload
A gateway accepts `application/protobuf`, the decoder returns a message value, and the request enters the business system. None of those successes establishes that the receiver used the producer's intended message definition. RFC 9996 gives Protocol Buffers a proper outer label.…
Story
RIPE Atlas Warns of Bad NTP Offsets. Thousands of Connected Probes Still Report Firmware 5120
RIPE NCC has named the faulty field and the replacement release. Its public API also shows that the affected version remains connected at scale. What is still missing is a correction record that joins those two facts to the result rows downstream users actually analyse.
Story
AFRINIC's New-Member Portal Names Three Preflight Guides. All Three Links Return the Same 404
AFRINIC's application portal is online and unusually clear about what a prospective member should read before applying. The problem is in the handoff: process, eligibility and supporting documents are presented as three separate guides, but each link depends on the same page that…
Europe and Middle East Regional ISP Trends
Satellite Ltd's power-backed business tiers need a failure map
Satellite Ltd sells reserve power as a visible feature of selected business tariffs. That turns continuity from a broad promise into a priced distinction—and makes the exact boundary of what stays powered the most important part of the offer.
IETF
Benoît Claise and the Augment the Base Module Could Not Name
A YANG module can list the modules it imports. It cannot, by reading itself, identify every external module that later inserts nodes into its schema tree. RFC 10035 makes that hidden direction reportable—one direct edge at a time.
IETF
Kazuho Oku and the Header That Makes Refusal Legible but Cannot Promise Streaming
An HTTP field can require a proxy that understands it to reject instead of quietly buffering. It cannot command a proxy that has never learned the field. RFC 10036 improves the evidence around incremental delivery precisely by preserving that distinction.
CASE FILE
The Envelope Signed the Digest. It Did Not Deliver the Preimage: RFC 9995 and the Authority Behind a COSE Hash Envelope
A release gate receives a valid signature over the digest of an SBOM. The envelope is small, the cryptography checks out, and the signed location points to a repository. Yet the SBOM itself is absent. Nothing has been downloaded, compared, parsed or judged. RFC 9995 makes the…
AUSNOG
AusNOG Turns Conference Attendance Into Voting Power
AusNOG does more than reward people who keep showing up. Its published rules convert event attendance into membership classes, then convert those classes into different numbers of votes at general meetings.
Story
RIPE NCC Began Verifying Roughly 1,600 No-Contract Legacy Holders. Its Q3 Plan Still Describes Two-Place Updates
RIPE NCC has a sensible plan to give old resource records a clearer organisational anchor. Its own quarterly plan also reveals the awkward middle of that migration: one change may still have to be performed manually in two places. The test is not whether the campaign looks…
Story
LACNIC Calls Postman Its Current API. The Website Still Says ROAs Change by Serial Number
LACNIC gives an API operator two public descriptions of the same control surface. Its Registration API page says Postman holds the most current v3 documentation, while the route table beside that instruction describes modifying or removing one ROA by `serialNumber`. Follow the…
CASE FILE
The Number Named the Enterprise. It Did Not Authenticate the Model: RFC 9997 and Authority Inside a Private SID Block
A network controller receives the integer key it expected, from the numerical territory associated with the vendor it expected. That is enough to avoid a collision. It is not enough to know who made the mapping, which model the integer denotes, or whether the device in front of…
CASE FILE
Yesterday’s Path Lent the New Flow Its Window. It Did Not Lend Its Capacity: RFC 9959 and the Authority to Reuse Congestion State
A service remembers that yesterday’s connection filled a long, fast path, so today’s connection starts with more confidence than an ordinary new flow. The gain can be real. So can the queue it creates when the same address now reaches another server, route or bottleneck. RFC 9959…
Story
APNIC Called RPKI Mirroring Marginal. Its NNIX Pilot Tests a Different Benefit
In October 2025, APNIC assessed a repository mirror as a short-lived aid during a long outage and called the benefit very marginal. Seven months later, its agreement with NNIX proposed a Hangzhou mirror pilot around latency, validation speed and data availability. The…
Story
ARIN's NET Permissions Change With the Lookup Path
One child NET, three ways to identify it, and three different questions about authority. An ARIN community suggestion reported that a direct registrant could reclaim a Detailed Reassignment and retrieve it through an exact address range, but could not use the same API key to GET…
Story
AFRINIC's Current RPKI CPS Says It Manages Asia-Pacific
The Certification Practice Statement linked from AFRINIC's current resource-certification page is version 3.0 from May 2020. In its CA-termination clause, the registry assigns itself the Asia-Pacific region. AFRINIC and IANA assign that region to APNIC and place AFRINIC in Africa…
IETF
The Old Segment Killed the New Connection: TCP's TIME-WAIT Assassination
A TCP connection can close before every copy of its packets has disappeared. TIME-WAIT is the protocol's quarantine between incarnations of the same conversation; RFC 1337 showed how an old segment could provoke the reset that ended that quarantine early.
CASE FILE
The Collection Held Every Evidence Item. It Had Not Bound Them to One Machine: RFC 9999 and the Composite Attestation Boundary
A verifier can receive a neat package labelled CPU, SmartNIC and GPU, decode every member and validate several signatures. None of those facts alone proves that the three reports describe the machine requesting access now. RFC 9999 makes remote-attestation messages portable; it…
Story
RIPE NCC Reports a 467-Day IPv4 Wait. The Queue Needs a Flow Ledger
RIPE NCC’s August member update says 757 LIRs were waiting for IPv4 space and the first LIR had been in line for 467 days. Its public chart records the queue’s size and its oldest wait, but those two stocks cannot show whether movement came from allocations, new requests…
Story
LACNIC Published a 98% Outreach Score. The Response Count Is Missing
LACNIC says more than 330 organizations attended its 2025 member gatherings and that 98% of the feedback it received fell in the highest satisfaction levels. Both statements may be accurate. The public post does not disclose the number of responses, so the percentage cannot be…
CASE FILE
The Address Was Unique. The Wire Still Saw a Collision: RFC 10019 and the Authority to Reconcile Zeroconf Multicast
Two isolated network segments can each make a locally correct multicast allocation. Join them, and both histories may remain truthful while the merged wire can no longer honour both claims. RFC 10019 turns that edge case into an operating principle: an address is not unique until…