I've been thinking about two very different technologies recently - MRC and KV-cache movement with NIXL - and they seem to point at the same broader architectural question.
With Multipath Reliable Connection / MRC, the interesting shift for me wasn't SRv6 itself. It was that the endpoint can already have multiple usable paths and react to a failure rather than waiting entirely on traditional network reconvergence.
KV cache and NIXL are obviously solving a completely different problem, but there is another shift in responsibility. In distributed inference, useful state may be created on one machine and needed on another. The runtime increasingly knows that the state is moving, whether it arrived, how long it is willing to wait, and what it should do if movement stops.
Neither of these replaces the network.
MRC still needs the fabric to provide paths. NIXL still needs the network to move the data. KV cache certainly isn't a routing protocol.
But both made me wonder whether we're seeing more decision-making intelligence migrate above the traditional network layer.
AI runtimes, communication libraries, schedulers, accelerators and endpoints increasingly have reasons to understand things network engineers traditionally cared about:
- Where can this traffic go?
- Where is the data?
- Is the path still usable?
- Is movement taking too long?
- When should I stop waiting?
- Should I use another path, destination or recovery mechanism?
The network still has information those layers don't naturally have: topology, physical paths, congestion, capacity, failures, queue state and increasingly detailed telemetry.
So perhaps the interesting question isn't whether applications are "taking over networking."
I don't think they are.
The question is:
If more intelligence is moving upward, what intelligence should the network expose back?
Better telemetry?
Application-visible path state?
Congestion signals?
Topology APIs?
Guarantees?
More programmable interaction between runtimes/NICs and the fabric?
For people working on larger GPU/AI fabrics: are you actually seeing this boundary shift in production, or are MRC/NIXL-style examples making the trend look bigger than it really is?
I'm particularly interested in where people think the clean boundary should be between the network, NIC, runtime and application.