Simple Two-Way Active Measurement Protocol Extensions for Performance Measurement on LAG

Link Aggregation Group (LAG), as defined in , provides mechanisms to combine multiple physical links into a single logical link. This logical link offers higher bandwidth and better resiliency, because if one of the physical member links fails, the aggregate logical link can continue to forward traffic over the remaining operational physical member links. Usually, when forwarding traffic over LAG, the hash-based mechanism is used to load balance the traffic across the LAG member links. Link delay of each member link varies because of different transport paths. To provide low latency service for time sensitive traffic, we need to explicitly steer the traffic across the LAG member links based on the link delay, loss and so on. That requires a solution to measure the performance metrics of each member link of a LAG. Hence the measured performance metrics can work together with layer 2 bundle member link attributes advertisement for traffic steering. Simple Two-Way Active Measurement Protocol (STAMP) is an active measurement method according to the classification given in , which can complement passive and hybrid methods. It provides a mechanism to measure both one-way and round-trip performance metrics, like delay, delay variation, and packet loss. Running a single STAMP test session over the aggregation without the knowledge of each member link would make it impossible to measure the performance of a given physical member link. The measured metrics can only reflect the performance of one member link or an average of some/all member links of the LAG. This document extends STAMP to implement performance measurement on every member link of a LAG. It can provide the same metrics as OWAMP and TWAMP can measure, such as delay, jitter, and packet loss. The proposed method could also potentially apply to layer 3 ECMP (Equal Cost Multi-Path), e.g., with Segment Routing Policy. The details are for future work, and not in the scope of this document

This document intends to address the scenario (e.g., ) where a LAG (e.g., the LAG includes four member links) directly connects two nodes (A and B) . The goal is to measure the performance of each link of the LAG.

To measure the performance metrics of every member link of a LAG, multiple sessions (one session for each member link) need to be established between the two end points that are connected by the LAG. These sessions are called micro sessions in the remainder of this document. Although micro sessions, indicated by SSID, are in fact STAMP sessions estabilished on member links of a LAG, test packets of micro sessions are RECOMMENDED to carry member link information for validation, as stated below. All micro sessions of a LAG share the same Sender IP Address and Receiver IP Address of the LAG. As for the UDP Port, the micro sessions may share the same Sender Port and Receiver Port pair, or each micro session is configured with a different Sender Port and Receiver Port pair. But from the operational point of view, the former is simpler and is RECOMMENDED. At the Sender side, each micro STAMP session MUST be assigned with a unique SSID. Both the micro STAMP Session Sender and Reflector MUST use SSID to correlate the test packet to a micro session. If there is no such a session, or the SSID is not correct, the test packet MUST be discarded. Test packets MAY carry the member link information for validation check, which is RECOMMENDED. For example, when a micro STAMP Session-Sender receives a reflected test packet, it may need to check whether the test packet is from the expected member link. The member link information is encoded in the Micro-session ID TLV introduced in section 3 of this document and the detailed description about the member link validation is also in this section. A micro STAMP Session-Sender MAY include the Follow-Up Telemetry TLV to request information from the micro Session-Reflector. This timestamp might be important for the micro Session-Sender, as it improves the accuracy of network delay measurement by minimizing the impact of egress queuing delays on the measurement.

Test packets are RECOMMENDED to carry member link information in Micro-session ID TLV introdued in this section for validation check. The micro Session Sender can verify whether the test packet is reveived from the expected member link. It can also verify whether the packet is sent from the expected member link at the Reflector side. The micro Session Reflector can verify whether the test packet is received from the expected member link.

STAMP TLV mechanism extends STAMP test packets with one or more optional TLVs. This document defines the TLV Type (value TBA1) for the Micro-session ID TLV that carries the micro STAMP Session-Sender member link identifier and Session-Reflector member link identifier in Sender Micro-session ID field and Reflector Micro-session ID field respectively. The format of the Micro-session ID TLV is shown as follows:

Type (one-octet in length): It is defined to indicate this TLV is a Micro-session ID TLV. Value TBA1 is allocated by IANA (Section 5). Length (2-octets in length): It is defined to carry the length of the Value field in octets. The Length field value MUST be 4. Sender Micro-session ID (2-octets in length): It is now defined to carry the LAG member link identifier of the Sender side. In the future, it may be used generically to cover use-cases beyond LAG. The value of this field MUST be unique within a STAMP session indicated by SSID at the Session-Sender. Reflector Micro-session ID (2-octets in length): It is now defined to carry the LAG member link identifier of the Reflector side. In the future, it may be used generically to cover use-cases beyond LAG. The value of this field MUST be unique within a STAMP session indicated by SSID at the Session-Reflector.

The micro STAMP-Test reuses the procedures as defined in Section 4 of STAMP with the following additions. The micro STAMP Session-Sender MUST send the micro STAMP-Test packets over the member link with which the session is associated. The configuration and management of the mapping between a micro STAMP session and the Sender/Reflector member link identifiers are outside the scope of this document. When sending a test packet, the micro STAMP Session-Sender MUST set the Sender Micro-session ID field with the member link identifier associated with the micro STAMP session. If the Session-Sender knows the Reflector member link identifier, the Reflector Micro-session ID field MUST be set. Otherwise, the Reflector Micro-session ID field MUST be zero. The Reflector member link identifier can be obtained from pre-configuration or learned from data plane (e.g., the reflected test packet). How to obtain/learn the Reflector member link identifier is outside of this document's scope. When the micro STAMP Session-Reflector receives a test packet, if the Reflector Micro-session ID is not zero, the micro STAMP Session-Reflector MUST use the Reflector member link identifier to check whether it is associated with the micro STAMP session. If the validation fails, the test packet MUST be discarded. If the Reflector Micro-session ID is zero, it will not be verified. If all validations passed, the Session-Reflector sends a reflected test packet to the Session-Sender. The micro STAMP Session-Reflector MUST put the Sender and Reflector member link identifiers that are associated with the micro STAMP session in the Sender Micro-session ID and Reflector Micro-session ID fields respectively. The Sender member link identifier is copied from the received test packet. When receiving a reflected test packet, the micro Session-Sender MUST use the Sender Micro-session ID to validate whether the reflected test packet is correctly transmitted over the expected member link. If the validation fails, the test packet MUST be discarded. The micro Session-Sender MUST use the Reflector Micro-session ID to validate the Reflector's behavior. If the validation fails, the test packet MUST be discarded. Two modes of the STAMP Session-Reflector, stateless and stateful, characterize the expected behavior. The micro STAMP-Test supports both stateless and stateful modes. However, the micro STAMP-Test does not introduce any additional state to STAMP, i.e, any procedure with regard to the Micro-session ID is stateless.

The micro STAMP Session-Sender sends micro Session-Sender packets with the Micro-session ID TLV. The micro Session-Reflector checks whether a test packet is received from the member link associated with the correct micro STAMP session, if the Reflector Micro-session ID field is set. When reflecting, the micro STAMP Session-Reflector copies the Sender Micro-session ID from the received micro Session-Sender packet to the micro Session-Reflector packet, and sets the Reflector Micro-session ID field with the member link identifier that is associated with the micro STAMP session. When receiving the micro Session-Reflector packet, the micro Session-Sender uses the the Sender Micro-session ID to check whether the packet is received from the member link associated with the correct micro STAMP session. The micro Session-Sender also use the Reflector Micro-session ID to validate the Reflector's behavior.

In the "STAMP TLV Types" registry created for [RFC8972], a new STAMP TLV Type for Micro-session ID TLV is requested from IANA as follows:

The STAMP extension defined in this document is intended for deployment in LAG scenario where Session-Sender and Session-Reflector are directly connnected. As such, it's assumed that a node involved in STAMP protocol operation has previously verified the integrity of the LAG connection and the identity of its one-hop-away peer node. This document does not introduce any additional security issues and the security mechanisms defined in and apply in this document.

The authors would like to thank Mach Chen, Min Xiao, Fang Xin, Marcus Ihlar, Richard Foote for the valuable comments to this work.