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 Large BFD Packet Stayed Up. The Whole Path Was Not Proven: RFC 9764
A green BFD session can now say something useful about packet size, but only if the claim stays as narrow as the packets that earned it. RFC 9764 turns padded control traffic into a recurring lower-bound test. It does not turn one forwarding treatment into a certificate for every…
CASE FILE
The Packet Carried a Resource ID. The Path Did Not Promise to Obey
An IPv6 packet may name the resource partition it wants at every hop and still emerge without proof that every router recognized the request, used the intended queue or preserved the promised isolation.
CASE FILE
The Certificates Were Related. The Verifier Still Owned the Decision: RFC 9763
A certificate authority can attest that two credentials belong to the same end entity. It cannot make two private keys act in a live exchange, choose a peer’s trust anchors or decide whether one successful authentication is enough. RFC 9763 is valuable because it draws that line…
CASE FILE
The Cache Could Stay. The Old Answer Could Not
An NFS client may re-read a busy directory, see the same names and still tell an application that a growing file has its old size. Revision 11 of a working-group draft answers that failure without pretending to abolish caching: it limits which answer the client may expose after…
CASE FILE
The Authorization Server Said Active. The Resource Server Still Had to Decide
One green boolean can look like permission. RFC 9767 is more disciplined: `active: true` is an authorization server’s answer to a resource server’s specific question about a token, a proof method and, sometimes, minimum access. The resource server still owns the application…
CASE FILE
One Subscription, Many Publishers: The Parent Owns the Split
A collector can ask one network node for one stream of updates and receive data from several publishing processes hidden behind the same address and subscription identifier. Revision 21 of the NETCONF distributed-notification draft corrects the authority that makes this possible…
CASE FILE
QUIC's Partial Reset Gained a Permission Gate. Its Delivery Promise Can Still Shrink
Revision 11 of QUIC Stream Resets with Partial Delivery closes an important permission gap: an endpoint may not send `RESET_STREAM_AT` unless its peer advertised support. That rule says the receiver can parse the extension. It does not make the sender's first Reliable Size…
CASE FILE
The Receiver Counted the Marks. It Did Not Choose the Sender’s Response
An acknowledgment disappears. The next one arrives with a three-bit counter advanced, but perhaps not by as little as it seems: the counter may have wrapped while the evidence was missing. RFC 9768 gives TCP a better congestion receipt, not an oracle. The receiver reflects marks…
Leaders
Hans Petter Holen and the Chair That Needed a Selection Process
A trusted personal handover placed Hans Petter Holen in the RIPE Chair role in 2014. By 2020, the more consequential achievement was a community process designed to make the next transition less dependent on any one person.
Leaders
Mirjam Kühne and the Forum That Had to Become a Journal
A post-Christmas spam problem revealed the editorial work required to keep an open technical publication useful: selection, moderation, format and a named hand-off.
CASE FILE
The Beacon Anchor Became Verifiable. Its Quantum Timeline Still Needed Another Archive
Revision 01 of Wathīqa repairs an important weakness in its evidence record: the first beacon value is no longer merely a time-shaped field but a signed pulse tied to a pinned certificate, with an optional successor that can prove immediate chain continuity. The repair is real.…
CASE FILE
The Receiver Lowered the Window. The Sender Never Changed Its Algorithm
A small advertised TCP window is often read as proof that the receiving application cannot keep up. RFC 9840 makes that shortcut unsafe. It gives the receiver a second reason to limit the window—deliberate low-priority transport—while leaving the sender’s congestion-control…
Leaders
Cristiano Amon and Qualcomm's Two-Engine Bargain
Cristiano Amon's defining leadership test before becoming CEO was not simply to accelerate Qualcomm's chip roadmap. It was to keep product execution credible while a legally distinct licensing business faced customer conflict, litigation and regulatory pressure.
CASE FILE
The Reference Was Well-Formed. It Was Not Yet Evidence
A digest can look precise enough to end an argument. Revision 03 of the Canonical Payload Binding draft instead turns that apparent certainty into a sequence of accountable tests: the reference must be admissible, one authorized digest context must be selected, the artifact must…
CASE FILE
The Maximum Metric Kept the Link. Missing Data Could Keep It or Remove It
A routing value can look catastrophic without withdrawing a link, while an empty field can either remove that link or leave it eligible. RFC 9843 makes those outcomes deliberate. Operations fail when telemetry turns three different protocol states into one red icon.
Leaders
Vint Cerf and the Deadline Behind the TCP/IP Cutover
The decisive test was not whether TCP/IP worked in a document. In Vint Cerf's recollection, rehearsed NCP shutdowns in 1982 exposed mail disruption and showed how much operational work remained before the ARPANET could change protocols. The transition became credible through…
Leaders
Warren Kumari and the Design of DNS Failure You Can Survive
Warren Kumari’s standards work shows that resilient DNS is not the absence of failure. It is the disciplined design of limited continuity, explicit freshness, fallback and legible error signals.
CASE FILE
The Cipher Was Approved. Its Key Budget Still Had to Be Counted
An AEAD name in a configuration proves which construction was selected, not how much cryptographic authority remains under the live keys. Revision 13 of CFRG’s usage-limits draft makes the missing control plane visible: applications choose the risk target, deployments count the…
CASE FILE
The Interface Name Was Required Locally. It Had to Vanish Before Transmission
An IPv6 link-local address can be perfectly valid and still fail to identify a usable path. RFC 9844 supplies the missing local selector—a zone identifier—while imposing an equally important limit: the label has meaning only inside one node and must not become identity on the…
Leaders
Seyed Pouria Mousavizadeh Tehrani and the State Hidden Before IPv6’s First Reply
A first IPv6 exchange can expose network state that steady-state reachability leaves invisible.