| Internet-Draft | Capabilities and Future Requirements of | March 2026 |
| Ye & Cheng | Expires 3 September 2026 | [Page] |
In the coming years, the accelerating proliferation of agentic AI is anticipated to drive the number of intelligent agents to reach the scale of hundreds of billions. IPv6, with vast address space, native end-to-end connectivity and rich built-in functionalities, serves as the critical infrastructure underpinning the development of the Internet of Agents (IoA). This draft systematically analyzes the foundational capabilities that IPv6 can provide for the IoA at the current stage, and further explores the evolutionary requirements that the IoA imposes on the future IPv6 development.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 3 September 2026.¶
Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
As artificial intelligence (AI) technology undergoes a transition from Generative AI to Agentic AI, the global number of AI agents is projected to reach approximately 900 billion by the end of this decade. AI agents, integrating core capabilities such as large language models (LLM), memory systems, tool calling, and task planning, possess the ability to perceive their environment, make autonomous decisions, and execute tasks efficiently, thereby placing new demands on the network infrastructure. Constrained by limited address space, IPv4 struggles to support secure end-to-end connectivity among massive numbers of AI agents. Consequently, the evolution to IPv6-only is not merely a technological upgrade but also a foundational enabler for the large-scale development of agents. As the core protocol for the next-generation Internet, IPv6, with vast address space, native end-to-end connectivity and rich built-in functionalities, serves as the critical infrastructure underpinning the development of the Internet of Agents (IoA).¶
This draft systematically analyzes the foundational capabilities that IPv6 can provide for the IoA at the current stage, and further explores the evolutionary requirements that the IoA imposes on the future IPv6 development.¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶
IPv6 employs a 128-bit address architecture, offering approximately 3.4×10³⁸ unique IPv6 addresses, which fundamentally resolves the exhaustion of the IPv4 addresses. In the context of IoA, where a vast number of agents necessitate exact addresses for intercommunication, the expansive address space of IPv6 is of critical importance. It enables the assignment of globally unique addresses to every agent, sensor, or container instance, thereby simplifying service discovery, facilitating horizontal scaling, and allowing for fine-grained identity mapping. As the population of agents grows exponentially, this native capability, which eliminates the need for address reuse, will become the cornerstone supporting a trillion-agent network.¶
The adoption of IPv6 eliminates the dependency on Network Address Translation (NAT), thereby streamlining network design and enabling lower-latency communication. First, the removal of NAT facilitates genuine end-to-end direct communication by assigning a unique global address to each agent. This is essential for the IoA, as it empowers agents to perform point-to-point coordination, task scheduling, and direct orchestration without reliance on intermediate nodes for forwarding or address translation. Furthermore, this end-to-end reachability can reduce the overhead of connection establishment and session lookup introduced by NAT, thereby simplifying coordination protocols among agents and minimizing communication latency.¶
For certain types of agents, particularly those operating in dynamic environments such as mobile devices, drones and connected vehicles, mobility constitutes a critical characteristic, as these agents frequently need to switch between different network access points. IPv6 provides native support for this requirement through Stateless Address Autoconfiguration (SLAAC).¶
SLAAC enables devices to autonomously generate IPv6 addresses upon connecting to a network, thereby equipping agents with the capability for rapid network attachment and dynamic readdressing without manual intervention. This realizes "plug-and-play" operation. For systems tasked with managing large-scale deployments of mobile agents, such automated configuration substantially reduces administrative overhead. Moreover, IPv6's robust support in constrained networks further enhances the mobility of edge agents, allowing them to seamlessly roam across access points without communication disruption.¶
Segment Routing over IPv6 (SRv6) further enhances network intelligence and programmability. By embedding instructions in the IPv6 extension header, SRv6 enables fine-grained path control, allowing the network to dynamically adjust traffic flows based on application requirements. This provides a powerful foundation for the remote management and path optimization of agents. In the context of the IoA, the contributions of SRv6 can be observed across several aspects: First, through flexible path programming, SRv6 enables the establishment of deterministic forwarding paths for packets, thereby achieving ultra-low-latency transmission. This allows agents to rapidly upload locally computed preliminary results to the cloud, realizing the separation of storage and computation while ensuring that raw data remains local and securely isolated. Second, SRv6 supports network slicing, enabling the creation of dedicated virtual networks tailored to diverse agent applications, thereby guaranteeing the quality of service for critical tasks. Third, the integration with application identifiers endows the network with the awareness of upper-layer applications. By embedding application-layer semantic information (e.g., service type, Service Level Agreement (SLA) requirements such as low latency, high bandwidth, and high reliability) directly into IPv6 packets, the network can automatically trigger the corresponding forwarding paths or service function chains.¶
The disappearance of NAT, while a advantage of IPv6, also poses new security challenges. In the IPv4 era, NAT unintentionally provided a layer of "obscurity protection" that internal device addresses remained invisible to external network, thereby reducing the risk of direct attacks. With IPv6, however, agents are directly exposed to the public network and are globally addressable, which demands the implementation of more robust host-level security mechanisms. For the IoA, this implies the deployment of finer-grained firewall policies, access control lists (ACLs), and identity authentication. Therefore, it is imperative to establish an advanced security for the IPv6-based IoA to control access based on identity, continuously monitor behaviors, and detect anomalies.¶
The temporary addresses that randomly generated and constantly changed, help protect a topological location and identity from being exposed to eavesdroppers and other information collectors [RFC3041]. However, this pivacy extension also introduces challenges for the communications of agents that require long-lived sessions. In the IoA, persistent connections are often necessary to achieve state synchronization and task continuity, yet the frequent changes of addresses may disrupt the stability of such long-lived sessions.¶
Striking a balance between privacy protection and session persistence thus emerges as a critical issue for the IoA. On one hand, it is necessary to protect the location, identity, and activities of agents from malicious tracking; on the other hand, it is essential to ensure that the communications of agents performing critical tasks can maintain stability. Addressing this tension may require more sophisticated address management strategies, such as dynamically selecting address types based on task sensitivity and communication patterns, or setting fixed identifiers at the application layer that are independent of addresses.¶
The vast address space of IPv6 significantly raises the cost of large-scale attacks that based on address scanning. Attackers can no longer enumerate all possible addresses as easily as in IPv4 space, even the state-of-the-art academic scanning tools can only discover tens of millions of IPv6 hosts within the 2^128 address space. However, the the increasing proliferation of agents and IoT devices may becom new objects of attack and could be potentially exploited to amplify attack. The security architecture must therefore re-evaluate DDoS defense strategies.¶
Building an IPv6-based comprehensive network observability framework is essential to better support the efficient operation of the Internet of Agents (IoA). This requires the establishment of IPv6-native telemetry and monitoring capabilities, along with corresponding updates to threat detection rules. However, current monitoring systems provide insufficient support for IPv6, with many legacy tools exhibiting deficiencies in handling IPv6 formats, extension headers, and specific behaviors. For instance, the IPv6 Flow Label field, which can be used to mark traffic priority at the packet level, remains largely underutilized by existing monitoring tools. Meanwhile, the address changes introduced by privacy extensions render traditional address-based tracking and auditing methods ineffective, further undermining network visibility. Furthermore, inconsistencies in the processing of IPv6 extension headers introduce additional complexity to network monitoring: Different devices handle IPv6 packets with extension headers in varied ways. For example, some may forward them normally, others may silently ignore them, and some may even discard them outright.¶
Therefore, data sampling and monitoring tools must be fully adapted to IPv6, ranging from correct interpretation of extension header semantics to the effective utilization of various specialized fields， so as to ensure continuous observation and analysis of agents' operations and behaviors, as well as timely anomaly detection. Additionally, threat detection rules must be enhanced to address IPv6-specific attacks, such as Neighbor Discovery Protocol spoofing, routing header manipulation, fragment attacks, among others.¶
This document has no IANA actions.¶