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.
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…
Story
ARIN Put 17,000 Legacy Networks in a Blog Post. The Status Table Is Missing
ARIN has published an unusually concrete warning about the contact records attached to legacy IPv4 space: roughly 17,000 networks, an `about half` risk description, 11% currently validated, another 20% incomplete, and a 76% comparison for resources under agreement. The figures…
Story
APNIC Signed a 2026 SANOG MoU. Its Public Link Still Shows “xxx” in the 2003 Text
APNIC says its Director General and the SANOG Chair formalized a Memorandum of Understanding at SANOG 44 in 2026. Yet APNIC's current partnership table still links readers to a three-page document whose operative date says `xxx day of August, 2003` and whose APNIC signature…
CASE FILE
The Probe Took the Same Path. It Still Did Not Share the Queue: RFC 10014 and the OAM Evidence Boundary
An operations team can truthfully report that its probe crossed the same nodes and links as customer traffic while missing the congestion that harmed that traffic. RFC 10014 explains why: packet participation, topological path and forwarding treatment are different properties.…
Story
ARIN Links ROAs to IRR Objects. Only the ROA Side Has a Visible Action Log
ARIN has made it possible for one routing-security action to leave two related records. That convenience is real. The evidentiary problem begins when the records later separate: the documented public history can explain the ROA, but not yet the whole operation that created…
ICANN
ICANN Gives SSE Applicants 21 Days to Challenge. What Should They Preserve on Day One?
An applicant cannot recover a short challenge window by reconstructing the decision record after the deadline has begun. ICANN's 2026 rules make the first governance task preservation: capture the transmitted determination, the notice actually received, the applicable rule…
Story
All Five AFRINIC Appeal Seats Expire on 31 December
AFRINIC filled its Policy Development Appeal Committee on 28 August and gave every appointment the same end date: 31 December 2026. That is 126 calendar dates when both endpoints are counted. The short first term is not evidence of a defective committee. It does, however, put…
ICANN
ICANN Confirms an SSE Error, Then Re-Evaluates. What Connects the Two Decisions?
An applicant can win an ICANN String Similarity Evaluation challenge without yet winning a new evaluation outcome. The missing link is the re-evaluation record: what the challenge found, what the evaluator reconsidered, and how the later determination relates to the first.
CASE FILE
The Server Returned Four Batches. It Had Not Frozen the Mailbox: RFC 10022 and the UIDBATCHES Closeout Boundary
An IMAP server can answer `UIDBATCHES 2000` with four orderly ranges and a final `OK`. That answer is useful precisely because it is less than a snapshot: the endpoints may name no stored message, deletions may thin a range, new mail may rise above it, and no later FETCH, COPY or…