Primary Domain
Infrastructure
Within the Primary Domain facet, 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 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…
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…
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…
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…
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…
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…
CASE FILE
The Neighbor Suggested a Door; We Chose Whether to Enter: BGP MED and Advisory Authority
The Neighbor Suggested a Door; We Chose Whether to Enter: BGP MED and Advisory Authority intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences…
CASE FILE
The Route Chose Three Times, the Neighbor Heard Once: BGP MRAI and Temporal Authority
A BGP router can change its mind several times while saying nothing new to one neighbor. The silence is not indecision. MRAI deliberately separates local route selection from external disclosure, trading the peer's freshest possible view for bounded UPDATE traffic and processing…
IETF
Ketan Talaulikar and the Prefix That Kept Its First Router's Name
An OSPF prefix can cross an area boundary without losing reachability and still lose part of its history. The new LSA names the Area Border Router that relayed it, not necessarily the router that first originated it. RFC 9084, edited by Ketan Talaulikar with four co-authors, adds…
Story
AFRINIC's Survey Can Count Replies. It Cannot Count Representation Yet
A response box can fill quickly and still leave the room outside it invisible. AFRINIC's new member and stakeholder survey may produce useful service evidence, but its eventual weight will depend on a record the launch has not yet supplied: who could answer, who was reached, what…
Latin America and Caribbean Cloud Services Trends
F5 leaves Mexico edge unconfirmed after scheduled go-live
More than 25 hours after F5's stated activation time for its `qro1-mx` Distributed Cloud Regional Edge, the public notice still says `Monitoring` and offers no completion update. The same change also depends on customers allowing a new `159.60.179.0/24` source range into their…
Story
RIPE's IPv6 PI Draft Has a Trigger but No Transition Receipt
Nine `/48` assignments can remain a valid deployed state while nothing changes. The next request for address space is different: it can activate a next-nibble decision, a contiguity test, a new prefix and a six-month return clock. Proposal 2024-01 names that trigger but does not…
Story
LACNIC's Anti-Fake-IXP Log Has No Event Column
LACNIC has made a scarce IPv4 reserve unusually visible. Its public file can show who holds an issued interval and how much of the pool remains reserved. What it cannot say in one row is what happened. A log commissioned to cover assignments, recoveries and returns still…
Story
ARIN's ISP/LIR Claim Needs a Predicate Ledger
One card asks what a company sells. Another asks whether it receives and redistributes Internet number resources. Draft Policy ARIN-2025-1 wants every holder of the first card to fit inside the second. Its proposed definitions do not yet make that containment rule true.
IETF
Tony Li and the Four-Byte Envelope That Refused to Rule the Payload
A GRE tunnel gives a packet a second address without taking away the first. The outer header decides how the envelope crosses an underlay; the inner header still decides what happens after the envelope is opened. Between them, the smallest GRE header can occupy only four octets.…
Story
APNIC Would Remove `/23`; Three Prefix Sizes Still Need Names
One bit separates a `/23` from a `/24`. It also separates 512 IPv4 addresses from 256. APNIC's current initial-LIR test can ask for immediate need for the smaller block and a one-year plan for the larger one. Prop-169 would repair that mismatch. Its replacement noun now needs an…
Story
AFRINIC Draft 2 Can Waive 90%; “Sufficiently Documented” Has No Fields
AFRINIC recorded the second-data-centre trap in 2018. An End User wanted another `/24` for redundancy, had used less than 90% of its existing space and was therefore ineligible. Draft 2 finally names that class of problem, then leaves the proof inside two words: sufficiently…
IETF
Acee Lindem and the Router That Had to Remember Rebooting
A valid signature can authenticate an old packet perfectly. That is the danger. If an OSPF router restarts and forgets which authenticated packets it has already accepted, a recording from yesterday can arrive wearing a correct digest and present itself as new. RFC 7474 makes…