Intelligence
Latest Articles
Latest intelligence on infrastructure operators, policy decisions, market moves, and digital power shifts.
History
The Relay Changed the Message. It Had to Call Itself a Gateway: RFC 1344
A carrier can claim neutrality while the entity in its custody remains untouched. The claim becomes harder after it changes an image, replaces a reference with a copy or divides one message into several. RFC 1344 gave that moment a name in 1992: the intermediary was no longer…
History
The Test Bed Could Demonstrate a Future. It Could Not Decide the Public Network: RFC 1259
RFC 1259 imagined the NREN as a new subdivision built before the surrounding city. Its mistakes could teach later builders, but its streets, prices and residents could not decide the whole metropolis. The crucial Internet-history lesson was not prediction. It was the design of a…
IETF
MLS Can Reopen a Call for Adoption After an IPR Disclosure. It Cannot Turn Disclosure into a Verdict.
An IPR notice is a change to the information set, not an oracle. The MLS chairs have extended a Call for Adoption for the two-party MLS profile after a third-party disclosure arrived. That extension is useful precisely because it gives entities a new opportunity to state a…
IETF
Eric Rescorla and the Encrypted Hello That Could Not Name the Server
An encrypted ClientHello can make a familiar public clue disappear from the first TLS flight. That does not turn the remaining handshake into an identity ledger. RFC 9849, co-authored by Eric Rescorla, specifies a carefully bounded privacy envelope: it can hide the private…
IETF
DNSOP Can Signal a Zone Cut to Nowhere. It Cannot Publish a Private Namespace.
DNSOP is considering a modest DNS mechanism for a difficult operational fact: a child zone can exist for one network while being deliberately unavailable through the public namespace. The proposed parent-side signal could help a resolver avoid confusing that fact with public…
Global Datacenter Trends
Vertiv’s UIG earnout has two 50% EBITDA cliffs
Vertiv has put approximately US$1.45 billion of cash on the closing table for UtilityInnovation Group. Another US$1.15 billion sits behind two performance tests whose dollar targets are not public. The filed agreement nevertheless reveals the machine: fall just short of half a…
IETF
Wesley George and the Old ASN Key That Could Not Announce a Merger
Wesley George and the Old ASN Key That Could Not Announce a Merger 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…
History
The Network Did Not Have to Keep the Beat. The Receiver Rebuilt It: RFC 1257
In 1991, a voice sample could arrive early, the next one late, and the listener could still hear a regular cadence—if the receiver knew the deadline, kept enough memory and woke at the right time. RFC 1257 used that construction to move a costly promise out of every subnetwork…
IETF
HTTPbis Can Consider Signature Keys. The Call Does Not Choose an Application Trust Model
HTTPbis is asking whether it should adopt work on a draft for distributing verification keys with HTTP Message Signatures. That is a real and consequential technical question. It does not decide which party a bank, marketplace, device fleet, agent platform or internal service…
History
The Packet Got a New Lifetime at Every Border: RFC 1326
A tunnel is often described as a clean bargain: put one protocol inside another, cross a network that understands the outer wrapper, then recover the original packet at the exit. RFC 1326 asked what happens when two such bargains face each other and routing sends the packet back…
IETF
Martin Duke and the QUIC Version That Could Not Declare Its Deployment
QUIC version 2 has an official RFC, an IANA entry and a memorable wire value. None of those things puts it on an endpoint. Martin Duke’s RFC 9369 makes the distinction unusually visible: “version 2” is merely the published document’s informal name, while the protocol uses a…
History
The Analysis Could Not Stand In for the Test Network: RFC 1245 and RFC 1246
In July 1991, OSPF arrived with more than a protocol specification. Its supporting case was deliberately divided into an analysis and an experience report. That division preserved a distinction Internet engineering still needs: a model can bound expected behaviour, but only…
IETF
BBF Needs the BGP Model. IDR’s WGLC Is Still Not a Publication Date
The Broadband Forum has a practical dependency: its WT-477i2 work refers to the IETF BGP YANG model. That dependency is neither trivial nor improper. The public error would begin only if a dependency notice were retold as a delivery promise. The IETF IDR Working Group’s August…
IETF
Joseph Touch and the UDP Options That Leave the Application in Charge
An extra field at the end of a UDP packet can make a protocol more useful without becoming a permission slip. RFC 9868, co-authored by Joseph D. Touch, draws that line unusually clearly: transport options can be carried after the user’s declared datagram, while the application…
North America Institutional Trends
Select Medical’s vote came before 53 holders rolled another 3.84m shares
Select Medical stockholders approved a transaction built around a fixed US$16.50 cash price. Four days later, a newly filed schedule showed 53 additional holders moving 3,844,152 unrestricted shares into private-parent equity instead. Closing then put a US$1 billion incremental…
History
The NIC Owned the Question. It Did Not Own the Network: RFC 1302
A help desk can keep faith with a user without pretending to control every system behind the problem. RFC 1302 made that distinction unusually clear in 1992. A Network Information Center was expected to take responsibility for an inquiry until it was resolved in some way. Yet…
IETF
Loa Andersson and the MPLS Decision That Stopped at the Charter
An institutional decision can narrow a future work programme without configuring the network that later uses its protocols. RFC 3468 records an MPLS Working Group consensus, documented by Loa Andersson and George Swallow, to focus traffic-engineering signalling work on RSVP-TE…
Global Institutional
ARTEMIS and the minute between a BGP alert and a safe response
ARTEMIS compares public BGP observations with an operator’s own model of permitted routing to classify suspicious announcements and respond faster. Its history exposes the harder problem: when visibility is incomplete and a counter-announcement can itself cause harm, speed helps…
IETF
Deborah Brungard and the Transport Profile That Did Not Choose a Network
A standards requirement can make a capability available without dictating the network that will use it. RFC 5654, edited by Deborah Brungard and four colleagues, describes requirements for an MPLS Transport Profile. Its most important restraint is plain: the requirements concern…
Creators
Jakub Kicinski: How Linux Turns Networking Features into Sustainable Infrastructure
A new network card may arrive with an impressive capability and a pressing commercial deadline. Linux must ask a slower question: can that capability be expressed in a form other devices can understand, operators can observe, tests can reproduce and maintainers can support years…