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.
CASE FILE
The Underlay Group Was Requested. The Receivers Were Not Proved: RFC 9798
One multicast-valued Receiver RLOC reaches a root ITR. It looks like a destination and may cause real forwarding state, but it answers neither “which ETRs asked?” nor “who received data?” RFC 9798 makes the division of labour precise enough to build a better receipt: preserve the…
Europe and Middle East Regional ISP Trends
Poyraz Hosting’s AS210574: What the Public Record Still Cannot Establish
Poyraz Hosting’s AS210574: What the Public Record Still Cannot Establish 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…
Global Institutional
Kea’s control surface is documented; its operational outcomes are not
ISC’s Kea DHCP exposes high-availability coordination, HTTP/JSON management, runtime configuration and DHCP-DDNS. Netgate and OPNsense show that the software has entered downstream network platforms. The public record still does not establish how widely those controls are…
IETF
The Diff Was Classified. The Upgrade Was Not Proven
Revision 09 of the YANG schema-comparison draft can produce a disciplined account of what changed between two schema revisions. Its editorial, backwards-compatible and non-backwards-compatible labels are valuable precisely because they are narrow: they describe the comparison…
Global Institutional
DFINFRA and AS210860: The Control Chain Is Still Unproven
DFINFRA and AS210860: The Control Chain Is Still Unproven 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 Global…
History
The UDP Table Knew the Port, Not the Conversation: RFC 2013
RFC 2013 gave a network manager two kinds of sight: four odometers for an entire UDP engine and a list of local doors where applications were listening. It could say that a door existed and that traffic totals moved. It could not say who stood outside, which process answered, or…
History
A CHAP Success Proved One Comparison, Not the Connection: RFC 1994
The decisive packet in CHAP was called Success. Its name sounded broader than its evidence: one authenticator had compared one response with one locally calculated value for one challenge. RFC 1994 made that comparison useful by binding it to time and direction—and left every…
Europe and Middle East Regional ISP
Vorboss’s network control is visible in routing, not yet proven across the physical chain
A systems-led investigation of what Vorboss demonstrably controls in London connectivity—and where public evidence still ends before fibre, facilities and recovery mechanisms.
IETF
Tim Bruijnzeels and the RPKI Overclaim That No Longer Invalidated the Whole Subtree
A certificate can be wrong in one place without being worthless everywhere. That proposition sounds modest, yet it changed the failure geometry of the Resource Public Key Infrastructure. In RFC 8360, Tim Bruijnzeels and five co-authors replaced one all-or-nothing consequence with…
IETF
The Hidden Service Answered. The Onion Key Had Not Yet Spoken: RFC 9799
The hidden service answered over Tor, the ACME account was valid, and the final CSR was ready. None of those facts yet proved that the applicant controlled the `.onion` identity. RFC 9799 makes that missing proof explicit—and shows why issuance authority, descriptor visibility…
Leaders
Noor Helmi’s Control Surface—and the Missing Transfer Record
A closer look at what can be attributed to IX Telecom’s co-founder and CEO, and what the public record still cannot show about capability surviving beyond the individual.
IETF
The Cursor Knew the Position. It Did Not Know the Moment
YANG list pagination can preserve the exact filter, sort field, locale, direction and continuation token used to reach the next page. That makes the traversal auditable. It does not make nine requests one observation, or an ordered page a frozen dataset.
History
One Packet Became Several Frames, and Several Packets Became One: RFC 1993
RFC 1993 recorded a compression design in which the most intuitive boundary on a serial link—the frame edge—stopped being the boundary that mattered. Its Gandalf FZA stream could gather several original PPP packets into one compressed frame or carry a single original packet…
History
The State Table Was Also a Kill Switch: RFC 2012
In RFC 2012, a manager could inspect a TCP connection in one moment and erase its host-side existence in the next. The same row that reported state also accepted `deleteTCB(12)`, turning a table of observations into a remote intervention surface whose consequences extended well…
IETF
Michael Tüxen and the Zero SCTP Checksum That Still Needed Error Detection
Zero usually looks like absence. In RFC 9653, a zero in SCTP's checksum field means something narrower: one endpoint may omit the correct CRC32c only after its peer has named an acceptable alternative error-detection method for that association. Michael Tüxen's work on the…
Story
A Direct Route Fixed a 150ms Detour. It Has No Backup.
A route from Britain toward Denmark appeared to turn the Atlantic into a roundabout. The first explanation blamed the wrong control point. Operators then found a short European path, traced the detour to export and peering choices, and installed a direct route whose lack of…
IETF
Mark Handley and the SDP Version You Cannot Compare Across Origins
A controller receives two session descriptions. One places version 391 in its `o=` line, the other 402. A dashboard sorts the larger number to the top and calls it latest. The arithmetic is flawless and the conclusion can still be wrong: the two descriptions carry different…
Story
AFRINIC Crossed an ASN Block Boundary With 52 Earlier Numbers Absent From the Ledger
AFRINIC Crossed an ASN Block Boundary With 52 Earlier Numbers Absent From the Ledger intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences…
IETF
The Stream Was Ordered. The Network Was Not Yet Proven
At the instant a controller receives `<rpc-reply><ok/></rpc-reply>`, the change can feel complete. The bytes arrived in order, the peer was authenticated, and the server returned success. Yet each of those facts belongs to a different evidentiary layer from the question operators…
History
The IP MIB Passed Compliance. IPv6 Was Still Outside the Frame: RFC 2011
A green conformance result can be perfectly accurate and still answer the wrong operational question. RFC 2011 made the surviving MIB-II IP and ICMP entities orderly under SMIv2. Its own IESG Note also warned that the order stopped at a four-octet address. The document is a…