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.
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…
History
George Varghese and the Deficit Counter That Made Round Robin Count Bytes
Round robin looks fair when a scheduler gives every queue one turn. On a packet link, however, turns are not equal units: one queue may send 1,500 bytes while another sends 500. M. Shreedhar and George Varghese changed the accounting unit. Deficit Round Robin lets each queue…
History
Jennifer Rexford and the Nearest BGP Exit That Was Never an End-to-End Optimum
An engineer changes one interior link weight. No external route is withdrawn, no new neighbour appears, and the destination prefix stays the same. Yet traffic leaves through another border router. Jennifer Rexford and her collaborators made this seam between IGP and BGP visible…
IETF
The Envelope Parsed. The Observation Is Not Yet Proven
`draft-ietf-netconf-notif-envelope-05` gives YANG-Push notifications a header that can travel with the message. That makes correlation easier. It does not collapse identity, continuity, time, provenance and operational truth into one successful parse.
History
The Root Server Became a Stack of Receipts: RFC 2010
RFC 2010 turned confidence in a capable root-server volunteer into inspectable duties—from checksums and clocks to capacity, contacts and outage notices—without deciding who deserved the role.
History
The Message Opened. That Did Not Mean the Evidence Was Complete: RFC 1991
An early PGP message could pass through six visibly successful operations—ASCII decoding, packet parsing, session-key recovery, decryption, decompression and signature verification—without any one of them proving who controlled the key, when the act occurred, whether it was…
CASE FILE
The Two Routes Arrived. Their Bits Still Did Not Belong Together: RFC 9819
An ingress PE can possess the two BGP advertisements required to construct an SRv6 Service SID and still lack permission to treat their bits as one executable instruction. RFC 9819 makes the missing proof visible: identity, argument size, insertion boundary, local acceptance…
History
The Packet Reached the Area. It Had Not Reached the Person: RFC 2009
RFC 2009 tried to fit a physical polygon inside a logical Internet address by routing approximately first and deciding precisely at the edge—a scaling bargain that made location, delivery and outcome separate facts.
Creators
Ivan Pepelnjak and the discipline of verifiable network automation
From Slovenia’s early internet infrastructure to netlab’s multi-vendor labs, Ivan Pepelnjak has consistently advanced an approach built on explicit models, reproducible tests and clearly stated limits. His central contribution is not a single protocol but a durable question: what…
CASE FILE
The Datastore Was Complete. The Control Plane Was Still Unproven: RFC 9826
A clean PCEP management tree can show an entity, its peers, live-looking sessions, notifications and counters in one coherent view. That coherence is a major operational gain. It is also where evidence from a management projection is most easily mistaken for proof of the network…
IETF
The Message Reassembled. The Telemetry May Still Be Incomplete
`draft-ietf-netconf-udp-notif-26` makes high-frequency YANG notifications cheaper to move across a controlled network. It also makes an important distinction unavoidable: transport evidence can show what a receiver assembled, but only a wider chain can show what the network…
History
The Address Was Borrowed. The Route Was Never Included: RFC 2008
The Address Was Borrowed. The Route Was Never Included: RFC 2008 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…
IETF
ALLDISPATCH Is a Routing Forum, Not a Standards Authority
The IETF-Wide Dispatch session can influence where emerging protocol proposals go next, but its leverage lies in routing and coordination—not in independently approving standards.
History
The Certificate Was Public. The Private Key Was Not: RFC 1984’s Trust Boundaries
In July 1996, two Internet standards bodies accepted that a government could operate a certification authority and still rejected the idea that a government, or any other third party, should hold a user’s private key. That is not a contradiction. It is the organising distinction…