The Task-Driven Agent Internet: Re-framing the Network Role and the Critical Path

Reconstructing the Network's Role and the Critical Path — As the Internet's service object shifts from "human clicks" to "task execution," the network is undergoing a role reconstruction from "bit pipe" to "task nervous system." Based on the latest wide-area network traffic measurement data and combined with global standards and industry progress, this report answers a core question: what role should the network play in the agent Internet, and what is most urgently needed right now.

Executive Summary

Core Conclusions

I. Origins: The Internet's Third Leap

To judge a research direction, one must first see whether it is riding the rhythm of a paradigm shift. Regarding the agent Internet, industry has formed a rare consensus judgment — the Internet is undergoing its third leap.

CAICT summarizes the core of the third-generation Internet as "leaping from connecting people and connecting information to connecting intelligence, connecting decisions, and connecting tasks"F. This means the basic unit of network interaction has already changed from "bytes" to "tasks."

At the terminology level, "Task-oriented Communication" is already a recognized hot term in 6G research, so "task-driven" has an international terminological basis and carries no risk of being a coined phrase.

II. The Question That Must Be Answered: What Agent Traffic Has Changed

To judge what the network should do, one must first look at what agent traffic actually "looks like." A recent wide-area network report based on real network measurements explains this change more thoroughly than traffic growth itself. Its value can be summarized in three progressive layers.

Layer One · Traffic Has Not Just Increased, Its "Character" Has Changed

In a public information-gathering test, an autonomous agent, to complete a single task, autonomously communicated repeatedly with web tools and models, reaching 44 web sources in total. The result — for the same task, network traffic triggered by the agent was about 450% higher than manual operationF. The measuring party called the connection between the agent and the model the "Spinal Cord": this is the new critical path, and once it jitters, the task chain fails directly, rather than merely pages slowing down.

Layer Two · It Is Like a "Thin Water Pipe," Not a "Large Water Pipe"

Large models generate one token at a time, so inference flows exhibit the counterintuitive characteristics of lasting longer and running at lower rates. This means the pressure is not mainly on peak bandwidth, but on state management — firewalls, intrusion detection, deep packet inspection, and other devices that need to maintain flow state must all re-plan table capacity for "long connections × massive flows."

Layer Three · Uplink Traffic Has Been Reversed

In inference flows, about 9% have uplink exceeding downlink, whereas in ordinary HTTP transactions this proportion is only about 0.5%F. The reason is that prompts have evolved into "context packages": historical conversations, file summaries, web content, tool-call results, task state — all must be pushed upstream. Uplink capacity, wireless-side planning, enterprise egress, and security policies all need to be re-examined accordingly.

On Latency: The Network Is Not the Main Bottleneck Now, But It Is Approaching the Main Battlefield

Current end-to-end inference latency is mainly determined by model processing time, with network latency accounting for only a smaller portion. But as inference hardware continues to accelerate and model processing time declines, the share of network latency in the overall experience will rise — the network "is not yet the main bottleneck, but will get closer and closer to the main battlefield." The report's long-term forecasts (such as the share of inference traffic in 2035 and the multiple growth of consumer and enterprise traffic) should be treated as planning signals rather than established factsI.

The Real Question: Should the Network "Understand" Agents

But it must be pointed out: this kind of discussion only raises the question and has not yet given a network-layer answer. It explains what the network will encounter, but does not answer "how to identify, how to assure, and at what granularity to schedule." This vacuum is precisely the value zone of network-layer research — and also the part this report will fill in later.

III. Global Research Landscape: Who Is Doing What

By organizing global progress into a map by "participant — progress," the division of labor between competition and cooperation becomes clear.

Most Worth Watching: Six Recognized Gaps

In IETF's latest survey of agent discovery mechanisms, the authors explicitly list six problems for which no standard solution yet existsF:

1. No standard for capability discovery — agents cannot be retrieved by "capability" alone; their addresses must be known in advance.
2. No interoperable federation — directories of different implementations cannot exchange registration information, and trust models are incompatible with one another.
3. The network layer and application layer are not connected — agents discovered at the network layer cannot be mutually recognized with A2A agent cards or MCP tool schemas.
4. Metadata schemas are fragmented — each party defines its own format, requiring customized translation between them.
5. Trust bootstrapping is difficult — "found" does not equal "trusted," and root trust remains unsolved.
6. No lifecycle management — capability changes cannot be notified to clients that have already discovered it.

IV. The Anchor of Demand: What Users Need Most

To judge the network's value, the anchor cannot be technology itself, but must be the kind of tasks users most urgently need. Signals on the demand side are already very clear.

These figures together illustrate one thing: what users pay for is not "being smarter," but "being able to reliably get things done." The metric of measurement has already shifted from MAU to DAA (daily active agents) — "what users want is not whether AI can, but whether AI can finish the job."I

Layering of Essential Scenarios

Each type of scenario has different network requirements, but all converge on the same set of foundational capabilities: whether a task can be found, connected, assured, traced, and settled.

V. Reconstructing the Network's Role: From Bit Pipe to Task Nervous System

Projecting the above decomposition of essential scenarios back onto the network yields six key roles the network should assume in the agent Internet. Each role corresponds precisely to one essential link.

VI. Critical Path and Priorities

Translating the above roles into "what should be done first right now," they can be ranked into three tiers by urgency × feasibility.

VII. Strategic Recommendations: Where Different Roles Should Focus

The common foundation of the agent Internet cannot be built by a single entity. Following the logic of "who should do it, and what should be done first," recommendations are given for different roles.

VIII. Conclusion

The Internet's service object is shifting from "human clicks" to "task execution." This is not an amplification of traffic scale, but a replacement of what is being carried — what the network served in the past was human attention; what it must carry in the future is action at software speed.

What follows is a fundamental reconstruction of the network's role: from a transmission pipeline for information to an execution foundation for tasks. The criteria for judging who holds the right to value distribution in the next-generation network change accordingly — no longer who has greater bandwidth and lower latency, but who can stably carry tasks and credibly deliver results.

For now, the industry's most urgent task is not capacity expansion, but filling in the three foundational capabilities of "identity — discovery — assurance." Whoever first builds the common foundation that lets agents "be found, be recognized, connect stably, and be traceable" will hold the most critical ticket to entry in the era of the agent Internet.