]> Huawei

zhangruyi8@huawei.com

Huawei

maojianwei@huawei.com

Huawei

leo.liubing@huawei.com

Huawei

gengnan@huawei.com

Huawei

shangxiaotong@huawei.com

Huawei

gaoqiangzhou@huawei.com

Huawei

robinli314@163.com

AREA rtgwg Agents Measurement Communication Protocol This document focuses on the use cases and requirements of communication protocols for measurement agents on network devices. About This Document The latest revision of this draft can be found at . Status information for this document may be found at . Discussion of this document takes place on the rtgwg Working Group mailing list (), which is archived at . Source for this draft and an issue tracker can be found at .

Introduction This document outlines use cases and requirements for network device agents engaged in network measurement tasks. As networks evolve toward increased automation and intelligence, efficient and standardized interactions between agents (located in routers, switches, or other network elements) become critical. Network measurement supports scientific discovery and network operations through tasks like characterizing traffic, understanding protocol performance, billing customers and detecting problems. This draft focuses on defining use cases that illustrate practical communication flows between agents, utilizing protocols like HTTP, gRPC, and others, and establishes key requirements to ensure interoperability, scalability, and reliability. The methods of measurement is out of scope in this draft. But the measurement agents on network devices should have the ability of choosing and invoking suitable network measurement tool.

Conventions and Definitions 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 when, and only when, they appear in all capitals, as shown here.

Use Cases This section describes three use cases for communication between network device agents for network measurement. Each case follows the follow:

1. Intent analysis
2. Measurement configuration generation
3. Configuration deployment

Use Case 1: Latency Measurement +-------+ | | | Agent | | 2. response | | Agent | | | +-------+ <---------------+ +-------+ | | Network Device | | Network Device | +----------------+ +----------------+ ]]> Figure: Latency Measurement In this scenario, an agent analyzes network performance intent and generates a latency measurement configuration. The intent may generate by other agent or human. The configuration specifies ICMP-based measurement with a 5-second duration. The agent sends an HTTP GET request to related agent's endpoint with the configuration parameters. The agent which receives this request applies the configuration, executes the measurement, and returns results in JSON format containing average latency, jitter, and timestamps. Overall, this approach promotes interoperability and ease of integration in heterogeneous networks.

Use Case 2: Active Measurement This use case involves an agent perceived or received a risk of link congestion initiates an active probing measurement. The agent should analyzes the level of risk to determine probe type and frequency. After analyzing the agent generates a configuration specifying active probing. There may be multiple related agent to cooperate to handle this issue. When probe arriving destinations, related agents should send reports to the agent on the source node.

Requirements To enable effective network measurement between network device agents, several key requirements must be addressed to ensure robust, scalable, and interoperable communications. These requirements stem from the use cases described and broader industry needs, focusing on protocol capabilities, data handling, and system integration.

Transmission Support for stream-oriented transmission is essential. As demonstrated in above use cases, measurements often involve continuous data flows, such as real-time metrics or large datasets. Protocols must facilitate bidirectional streaming to allow agents to send and receive data concurrently without interruption, minimizing latency and enabling dynamic adjustments during measurements. This requirement aligns with protocols like gRPC and WebSocket, which natively support streaming, and should be extended to other implementations through standards like HTTP/2 for broader adoption.

Data Formats Structured and extensible data formats are critical for interoperability. Agents must exchange measurement results in a consistent manner, using formats such as JSON, XML, or Protocol Buffers. These formats enable easy parsing, validation, and integration with analytics tools. Additionally, the data schema should be extensible to accommodate new measurement types and parameters, allowing for future enhancements without breaking backward compatibility. For instance, defining common fields for timestamps, error codes, and metadata in responses can standardize interactions across diverse agent implementations.

Security Security mechanisms must be integrated to protect measurement data and prevent unauthorized access. This includes mandatory use of transport-layer security (e.g., TLS for HTTP and gRPC, WSS for WebSocket) to encrypt data in transit, as well as authentication and authorization frameworks such as OAuth or client certificates. Given the sensitive nature of network metrics, agents should also implement rate limiting and audit logging to detect and mitigate potential threats, ensuring compliance with organizational policies.

Reliability Reliability and error handling are paramount for maintaining measurement accuracy. Protocols should incorporate features like retransmission policies, timeouts, and graceful degradation to handle network failures or agent unavailability. For example, in the latency measurement use case, HTTP retries can be employed for transient errors, while gRPC's built-in error codes provide detailed diagnostics. Agents must also support idempotent operations to avoid duplicate measurements and ensure data consistency.

Scalability Scalability and performance optimizations are necessary to support large-scale deployments. This involves efficient resource management, such as connection pooling and load balancing, to handle high volumes of concurrent measurements. Protocols should minimize overhead through compression techniques and efficient serialization, as seen with Protocol Buffers in gRPC. Moreover, agents ought to support asynchronous operations to non-blockingly process multiple requests, enhancing overall system throughput.

Interoperability Interoperability and standardization across vendor implementations are crucial. This requires adherence to common APIs, protocol specifications, and data models, possibly defined in IETF RFCs. By promoting a unified approach, agents from different manufacturers can seamlessly communicate, reducing integration costs and fostering innovation in network automation. Additional considerations include support for multicast or publish-subscribe models for group measurements and mechanisms for data aggregation to reduce network load.

Security Considerations TBD

IANA Considerations This document has no IANA actions.

Conclusion This draft presents use cases and requirements for the measurement agents on the network device. The defined requirements for transmission, data formats, security, reliability, scalability, and interoperability form a foundation for standardized agent interactions. These improvements will enable more automated and intelligent network management, enhancing performance and resilience in modern networks.

Normative References In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.

Acknowledgments TODO acknowledge.