Intelligence
Latest Articles
Latest intelligence on infrastructure operators, policy decisions, market moves, and digital power shifts.
History
The Address That Could Not Be Downgraded: How SMTPUTF8 Made the Route Part of the Name
An accented display name could cross old email systems because it was decoration around an ASCII address. A non-ASCII mailbox name was different: it was the destination itself. SMTPUTF8 made every relay prove that it could carry that identity without inventing another one.
Academics
Katerina Argyraki and the search for proof in packet forwarding
Katerina Argyraki’s research follows a problem that becomes harder as networks become more programmable: a packet-processing system may be fast and flexible, yet operators and users often have little evidence that it behaved correctly. Her work at EPFL connects software-router…
Global Institutional
FreeRADIUS and the trust decisions behind network access
A network login may be decided in a few packets, but the trust behind it can span certificates, directories, access devices, roaming partners and accounting systems. FreeRADIUS makes that policy inspectable and programmable, while leaving operators responsible for the legacy…
Creators
Dave Maltz and the operating stack behind Azure networking
Dave Maltz’s role at Microsoft is best understood through the breadth of the organisation he leads. Azure Networking spans customer-facing services, DNS, security, distributed control, host offload, switch software, data-centre fabrics, wide-area links and optical systems. That…
History
The Receipt That Could Not Promise Delivery
SMTP DSN turned the bounce into structured evidence while preserving a crucial limit: a sender could request a report, but no receipt could promise more than the reporting system had observed.
CASE FILE
The Tag Fit. The Authority Did Not: BGP Large Communities and the Namespace That Executes Policy
The route carried exactly the value the interconnection handbook prescribed. One provider acted on it, another erased it, and a third would have accepted the same instruction from a party that had never been authorized to give it. Twelve octets solved the numbering problem. They…
Story
The second consultation placed Board review before a future SGMM vote
AFRINIC’s 4 August announcement described a careful sequence for moving constitutional text from public comments to committee revision, independent legal scrutiny, Board review and, only if the Board allowed the proposal to advance, later consideration by members. The important…
IETF
Jana Iyengar and the Connection That Outlived Its Address
A QUIC connection can continue when a device changes networks, but the old session cannot lend every old assurance to the new path. RFC 9000 preserves connection state narrowly, then demands fresh evidence for reachability, sending limits, congestion, ECN and privacy.
Global Institutional
BIRD and the routing policy engine behind internet exchanges
The BIRD Internet Routing Daemon grew from a Czech university project into a control-plane system used in demanding routing environments, including internet exchanges where policy is concentrated and operational mistakes can spread quickly. Its history shows how open routing…
CASE FILE
The Route That Knew Nothing and Reached Everything: BGP Default Origination and the Authority of Last Resort
A customer still had an Established BGP session, a selected `0.0.0.0/0` and several successful probes. Most of the Internet had nevertheless become unreachable. The route with the widest scope had survived the loss of the service it was supposed to summarize.
History
The Eighth Bit Needed Permission at Every Hop: How 8BITMIME Changed SMTP
Email could describe an accented character long before every relay could carry its bytes unchanged. 8BITMIME made that mismatch visible: a server had to promise capability on this hop, and acceptance created a duty to keep every bit.
CASE FILE
The Path Was Shorter Because the Evidence Was Gone: BGP ATOMIC_AGGREGATE and the Authority to Compress
The `/22` remained visible, its origin stayed valid and every external session was green. One of the four `/24`s beneath it had nevertheless disappeared. The public path looked cleaner at precisely the moment when the network knew less about the destinations it claimed to reach.
IETF
Sally Floyd and the Test That Throughput Alone Could Not Pass
A faster flow can be a worse network result. Sally Floyd’s work on congestion-control evaluation shows why a headline rate must be tested against delay, loss, fairness, instability, difficult paths and the traffic it displaces before an algorithm earns a wider deployment.
Global National Telecom
Boldyn's £1bn Tube network must earn its 20-year lock-in
Four mobile operators can share one radio and fibre layer beneath London instead of attempting four separate builds. That is sensible engineering. It is also a twenty-year concentration of operating power, financed before the network produces mature cash. Boldyn has to prove that…
History
The Commands Sent Before Their Answers Arrived: How SMTP PIPELINING Changed the Wait
Early SMTP made a sender pause after nearly every command. On a distant link, the message could spend more time waiting for permission to continue than moving. PIPELINING shortened that silence, but only by making order—not wording—the ledger of unfinished work.
CASE FILE
The coalition that spoke for operators: who authorized TCCM at WSIS+20?
TCCM placed registry and infrastructure operators inside the WSIS+20 consultation record with unusual persistence. The record shows who spoke, which organizations endorsed two important submissions and where the final United Nations text matched the coalition’s requests. It does…
CASE FILE
The Internet Saw One AS. Operations Had Twelve: BGP Confederations and the Authority of a Hidden Topology
The public route never changed. External peers still saw AS 64500, the sessions remained Established and the prefix stayed visible in collectors. Inside the network, however, one router had crossed from Member-AS 65021 to 65031 while its neighbor still believed the old boundary.…
History
The Method That Refused to Be Misunderstood: Why HTTP 510 Existed
RFC 2774 tried to stop servers returning success after ignoring mandatory HTTP extensions. The fate of 510 shows the cost of verifiable semantics.
CASE FILE
The Router Could Not Read the Attribute, So It Forwarded It: BGP's Partial Bit and the Authority of Ignorance
This technical explainer opens with a constructed operating scenario, not a reported incident. The transit router does exactly what the protocol asks: it receives a route carrying an optional transitive attribute it does not understand, preserves the opaque bytes, sets Partial…
History
The Message Measured Before It Moved: How SMTP SIZE Made Refusal Early
Early SMTP could carry a large message all the way to a server before learning that the server would never keep it. The SIZE extension did something narrower than guaranteeing delivery: it let two relays compare a declared load with local capacity before paying the full transfer…