Intelligence
Latest Articles
Latest intelligence on infrastructure operators, policy decisions, market moves, and digital power shifts.
History
The Request That Had to Wait for Proof: Why HTTP Needed 425
TLS 1.3 let returning clients send requests before a new handshake finished. HTTP 425 made replayable early data wait without changing the request itself.
CASE FILE
The Monitor Saw the Route, Not the Packet: BGP BMP and the Authority of a Control-Plane Witness
A monitoring feed can be accurate and still support a false conclusion. BGP Monitoring Protocol gives operators structured views of routes before policy, after policy, at export and after selection. Those views are not interchangeable. The first duty of a BMP system is therefore…
CASE FILE
The Metric Crossed the AS Boundary: BGP AIGP and the Authority to Define One Interior Cost
Two autonomous systems can belong to one operator and still speak different mathematical languages. If one calls a 10-millisecond link “10” and the other calls a high-capacity link “10,” adding their metrics produces a precise number with no coherent meaning. BGP AIGP can carry a…
History
The Alias That Could Not Move Authority: DNS DNAME
DNAME redirects descendant lookups by replacing one suffix. The owner, zone apex and NS delegation stay put even when many queries follow the new subtree.
CASE FILE
The Backup Was Chosen Before the Failure: BGP PIC and the Authority of Precomputed Forwarding
When a backbone link fails, the first packets do not wait for a committee of routing processes to reconsider millions of destinations. On a router using BGP Prefix Independent Convergence, they may follow a backup that was selected and installed hours earlier. The speed comes…
Story
ARIN's New “Sole Use” Definition Has No Observation Window
Imagine one address prefix serving three anycast sites: one inside ARIN's service region and two outside it. The inside site is withdrawn for maintenance, then restored an hour later. The holder, service design and prefix have not changed. Under the wording of a new ARIN…
History
The Save That Left the Page Intact: HTTP 204
HTTP 204 says an action finished without replacing its active view. Status marks completion, while headers carry post-action identity without response content.
History
The Connection That Was Not Authority: Why HTTP Needed 421
HTTP learned to save time by letting several named origins share one authenticated connection. Status 421 preserved the limit of that bargain: a channel can be reachable, secured and reusable in principle without being the connection context through which a particular origin is…
History
The Copy That Arrived as a Difference: HTTP 226
HTTP 226 lets a changed representation travel as instructions for a cached base. Base, delta message and reconstructed result retain separate identities.
CASE FILE
The Reflector Chose from the Wrong City: BGP ORR and the Authority to Compute Another Router’s Best Exit
A centralized route reflector can make a path decision from a place where no customer traffic ever flows. BGP Optimal Route Reflection lets it calculate from a client’s logical position instead. The mechanism restores a missing perspective, but it also creates a new delegated…
History
The Alias That Did Not Need a Second Walk: HTTP 208
WebDAV could expose one collection through two paths. HTTP 208 keeps the second path visible while omitting descendants already reported through the first.
CASE FILE
The Route Reflector Hid the Choice: BGP ADD-PATH and the Authority to Expose Alternatives
A route reflector can make a large network easier to operate by showing each client only the route it selected. That economy also removes choices. ADD-PATH creates a way to carry several paths for one prefix, but the protocol does not decide which alternatives deserve exposure…
IETF
John Scudder and the BGP Session That Had to Declare Its Capabilities
Two routers may complete a TCP connection and still be unfit for the BGP job expected of them. One may understand an optional extension that the other has never implemented; both may understand it while only one admits support in the OPEN message; or an older peer may reject the…
CASE FILE
The Route Was Valid. The Reflector Called It a Loop: BGP Cluster IDs and the Authority to Discard Reachability
Every BGP session was Established. The customer prefix was valid at its source. Yet a regional reflector refused the route because a four-octet value in `CLUSTER_LIST` matched its own. The protocol had done exactly what it was told: an identity meant to stop loops had been reused…
History
The Preference Allowed to Lose: How Happy Eyeballs Races Paths
A valid IPv6 answer can still lead nowhere. Happy Eyeballs lets IPv6 start first, then allows observed reachability to win before the user pays a long timeout.
CASE FILE
The Policy Changed; the Routes Did Not: BGP Route Refresh and Re-evaluation Authority
Editing an inbound BGP policy changes a rule, not the routes already judged under the old one. To apply the new rule, a router needs the inputs again. Route Refresh lets it ask a capable neighbor to re-advertise the neighbor's current export set without destroying the session—but…
History
The Connection Beyond Its Address: Why QUIC Uses Connection IDs
Addresses and UDP ports can change while work remains. A QUIC Connection ID preserves continuity, but path validation and fresh identifiers bound trust.
CASE FILE
The Route Carried a Request, Not a Restraint: BGP NO_EXPORT and the Authority to Propagate
A route can arrive carrying `NO_EXPORT`, a name that sounds like a lock. It is nothing of the kind. The community tells a receiving network where the route is meant to stop, but the receiver's running policy still decides whether the value survives and whether the route leaves…
Story
APNIC's SIG Review Lists Twelve Changes Before It Has Decision Text
Twelve headings can make a governance review look nearly finished. They can also hide the one thing a consensus call must actually decide: the precise rules that will replace the current ones. APNIC's July SIG Guidelines draft has diagnosed a connected set of problems; its next…
History
The Name Created by a Question: How DNS Wildcards Stay Bounded
A DNS wildcard can synthesize a name never stored in the zone. Exact nodes, empty non-terminals and delegation still decide when that default may answer.