Internet-Draft STAMP Extensions for Signaling November 2026
Gandhi Expires 19 May 2027 [Page]
Workgroup:
BPM Working Group
Internet-Draft:
draft-gandhi-bpm-stamp-signaling-00
Published:
Intended Status:
Standards Track
Expires:
Author:
R. Gandhi, Ed.
Cisco Systems, Inc.

Simple Two-Way Active Measurement Protocol (STAMP) Extensions for Signaling Parameters

Abstract

The Simple Two-Way Active Measurement Protocol (STAMP) specified in RFC 8762 supports active measurement of network performance without a control channel to pre-signal session parameters. RFC 8972 defines optional extensions in the form of Type-Length-Value (TLV) elements for STAMP. This document defines a STAMP Type-Length-Value (TLV) that allows a Session-Sender and a Session-Reflector to exchange measurement capabilities and configuration parameters in STAMP-Test packets. The Session-Sender uses the returned parameters to configure a STAMP session.

Status of This Memo

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 19 May 2027.

▲

Table of Contents

1. Introduction

The Simple Two-Way Active Measurement Protocol (STAMP), specified in [RFC8762], provides capabilities for measuring various performance metrics in IP networks without the use of a control channel to pre-signal session parameters. [RFC8972] defines optional extensions in the form of Type-Length-Value (TLV) elements for STAMP.

A Session-Sender may not know which measurement capabilities and configuration parameters are supported or required by a particular Session-Reflector. For example, the Session-Sender may not know whether the Session-Reflector supports stateful or stateless operation, a given timestamping method, or the requested packet transmission interval. The Session-Sender may also need to know whether the Session-Reflector's clock is synchronized for one-way delay metrics.

Without this information, a Session-Sender cannot reliably select a measurement mode or configure the rate and timestamping behavior of a STAMP session. This document defines a signaling procedure using a STAMP TLV carried in STAMP-Test packets. The Session-Sender includes its Profile ID and one or more requested measurement-mode sub-TLVs in a STAMP-Test packet. The Session-Reflector returns the selected Profile ID and parameters for each requested mode in the reflected packet. The Session-Sender uses the returned parameters to configure subsequent STAMP-Test packets. The signaling uses the STAMP measurement path and test packets in-band and does not require a separate control channel.

This mechanism does not provision the IP endpoints, authentication, or reachability required to exchange STAMP-Test packets. Those items must be configured by other means. The TLV signals capabilities and session parameters after the Session-Sender can transmit an initial STAMP-Test packet to the Session-Reflector.

2. Conventions Used in This Document

2.1. Requirements Language

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.

2.2. Terminology

This document uses the terms Session-Sender, Session-Reflector, and STAMP-Test packet as defined in [RFC8762] and [RFC8972].

This document uses the terms STAMP TLV and STAMP TLV Flags as defined in [RFC8972].

"Signaling request" refers to a STAMP-Test packet carrying the TLV from the Session-Sender. "Signaling response" refers to the corresponding reflected STAMP-Test packet.

2.3. Abbreviations

Table 1: Abbreviations
Abbreviation Meaning Reference
NTP Network Time Protocol [RFC5905]
PTP Precision Time Protocol [IEEE1588]
STAMP Simple Two-Way Active Measurement Protocol [RFC8762]
TLV Type-Length-Value [RFC8972]

3. Overview

The signaling exchange is carried in STAMP-Test packets as an optional TLV, following the general extension processing procedures in [RFC8972]. The Session-Sender sends an initial signaling request with its desired Profile ID and one or more mode-specific sub-TLVs, with no more than one sub-TLV for each measurement mode. Each sub-TLV identifies a mode and requests the parameters applicable to that mode. If the Session-Sender does not know which mode or modes are configured for a Profile ID, it MAY include one sub-TLV for each mode it wants to query; to query all modes defined in this document, it includes one sub-TLV for each defined mode. The two-way, one-way, and loopback measurement modes are described in Section 3.1, Section 3.2, and Section 3.3, respectively. Note that the two-way measurement mode is specified as part of the STAMP process in [RFC8762] and [RFC8972]. The other measurement modes are defined in this document. This document defines signaling parameters for those modes. The Session-Reflector returns the selected Profile ID and one corresponding sub-TLV for each requested mode. A response sub-TLV with its U flag clear indicates that the mode is configured and available for the selected Profile ID; a sub-TLV with its U flag set indicates that the mode is not configured for that profile, unsupported, or disallowed for the request's source node.

A response may provide parameters for multiple available modes as alternatives for one session. A STAMP-Test session MUST operate in exactly one measurement mode. After receiving and validating a response, the Session-Sender MUST select exactly one available mode that meets its requirements for the session and MUST NOT use more than one measurement mode in that session. If no returned mode meets its requirements, it MUST NOT start the session. For one-way and two-way modes, each corresponding sub-TLV carries the minimum receive interval and UDP port; capabilities are reported in the parent TLV. Loopback mode uses a separate sub-TLV because those parameters do not apply to it.

The exchange is initiated by the Session-Sender and requires no Session-Reflector-initiated discovery packet. A Session-Reflector can process the signaling request without retaining per-session state. The parent TLV Capability Flags report stateful operation support for one-way or two-way mode and stateless operation support for two-way mode. The initial request is sent using a locally configured interval. If the response is absent, malformed, or indicates that a Session-Sender requirement is not supported, the Session-Sender does not treat the requested configuration as negotiated.

The Profile ID is an opaque identifier for a profile known at both endpoints. A single Profile ID can be associated with more than one measurement mode. The identifier allows the endpoints to select corresponding local configuration.

3.1. Two-Way Measurement Mode

As shown in Figure 1, in two-way measurement mode, the STAMP Session-Sender S1 initiates a Session-Sender test packet, and the STAMP Session-Reflector R1 generates and transmits a Session-Reflector test packet. The Session-Reflector test packet is sent to the Session-Sender S1 on either the same path (i.e., the same set of links and nodes) or a different path in the reverse direction from the path taken toward the Session-Reflector R1.

                   T1                           T2
                  /                               \
         +-------+  Session-Sender Test Packet     +-------+
         |       | - - - - - - - - - - - - - - - ->|       |
         |   S1  |=================================|   R1  |
         |       |<- - - - - - - - - - - - - - - - |       |
         +-------+   Session-Reflector test packet +-------+
                  \                               /
                   T4                           T3

     STAMP Session-Sender                 STAMP Session-Reflector
Figure 1: Reference Topology for Two-Way Measurement Mode

T1 is a transmit timestamp, and T4 is a receive timestamp added by node S1. T2 is a receive timestamp, and T3 is a transmit timestamp added by node R1. All four timestamps are used by the Session-Sender to measure the two-way delay metric, defined as ((T4 - T1) - (T3 - T2)). Timestamps T1 and T2 are used by the Session-Sender to measure the forward one-way delay metric, defined as (T2 - T1). Note that the delay value (T4 - T3), measured by the Session-Sender, is the reverse one-way delay metric. The "two-way delay" is the sum of the one-way delays in each direction and reflects the delay of the bidirectional path, irrespective of processing delays within the Session-Reflector.

In two-way measurement mode, the round-trip delay interval (T4 - T1) includes the Session-Reflector processing time, including handling the UDP header in the exception path, generating the Session-Reflector test packet, and reflecting optional TLVs. The two-way delay metric subtracts the Session-Reflector interval (T3 - T2) from the round-trip delay interval.

The computation of the one-way delay metric requires the clocks on the Session-Sender and the Session-Reflector to be synchronized, e.g., using either PTPv2 [IEEE1588] or NTPv4 [RFC5905].

In two-way measurement mode, round-trip packet loss, near-end packet loss (forward direction), and far-end packet loss (backward direction) can be measured. Note that packet loss measurement does not require the clocks on the Session-Sender and the Session-Reflector to be synchronized using either PTPv2 or NTPv4.

3.2. One-Way Measurement Mode

As shown in Figure 2, in one-way measurement mode, the STAMP Session-Sender S1 initiates a Session-Sender test packet. Upon receiving a Session-Sender test packet, the STAMP Session-Reflector does not transmit a Session-Reflector test packet.

                   T1                           T2
                  /                               \
         +-------+  Session-Sender Test Packet     +-------+
         |       | - - - - - - - - - - - - - - - ->|       |
         |   S1  |=================================|   R1  |
         |       |                                 |       |
         +-------+                                 +-------+

     STAMP Session-Sender                 STAMP Session-Reflector
Figure 2: Reference Topology for One-Way Measurement Mode

T1 is a transmit timestamp added by node S1 and T2 is a receive timestamp added by node R1. Timestamps T1 and T2 are used by the Session-Reflector to measure the one-way delay metric, defined as (T2 - T1).

The computation of the one-way delay metric requires the clocks on the Session-Sender and the Session-Reflector to be synchronized using either PTPv2 or NTPv4.

In one-way measurement mode, forward-direction packet loss can be measured. The Session-Reflector compares the Session-Sender Sequence Number in each received Session-Sender test packet with the sequence number in the previously received packet. An increase of k indicates that k-1 test packets were not received, accounting for sequence-number wraparound. This measurement is available at the Session-Reflector. Note that packet loss measurement does not require the clocks on the Session-Sender and the Session-Reflector to be synchronized using either PTPv2 or NTPv4.

3.3. Loopback Measurement Mode

As shown in Figure 3, in loopback measurement mode, the STAMP Session-Sender S1 initiates a Session-Sender test packet to measure the round-trip delay using source routing. The node R1 at the end of the configured forward path forwards the received STAMP-Test packet along the configured return path using its MPLS and service forwarding state in the data plane. The node R1 does not need to support STAMP or maintain a STAMP session.

                   T1
                  /
         +-------+  Session-Sender Test Packet     +-------+
         |       | - - - - - - - - - - - - - - - - |       |
         |   S1  |================================||   R1  |
         |       |<- - - - - - - - - - - - - - - - |       |
         +-------+     Session-Sender test packet  +-------+
                  \    (Return)
                   T4

    STAMP Session-Sender                 STAMP Session-Reflector
                                         (Loopback, Forward)
Figure 3: Reference Topology for Loopback Measurement Mode

T1 is a transmit timestamp and T4 is a receive timestamp added by node S1. The Session-Sender uses them to measure the round-trip delay metric, defined as (T4 - T1). This delay includes test packet processing on the node R1 in the data plane. The processing delay includes only the time required to forward the test packet from the incoming interface to the outgoing interface in the data plane. The node R1 does not timestamp the test packets and therefore does not require a timestamping capability.

In loopback measurement mode, only round-trip packet loss can be measured.

4. STAMP Parameters TLV

This document defines the "STAMP Parameters" TLV (Type=TBD). Its Value contains, in order, a 16-bit Maximum Padding Size field, an 8-bit Reserved field, a one-octet Profile ID, a 16-bit Reserved field, eight one-bit R flags, a Capability Flags octet, and one or more measurement mode sub-TLVs associated with that Profile ID. Each request and response MUST contain at least one measurement mode sub-TLV and MUST NOT contain more than one sub-TLV for any one measurement mode. A STAMP-Test packet MUST NOT contain more than one STAMP Parameters TLV. The STAMP TLV Flags, Type, and Length fields use the format specified in [RFC8972].

 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |STAMP TLV Flags|  Type=TBD     |          Length               |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |Maximum Padding Size (16 bits) | Reserved      | Profile ID 8b |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |Reserved             (16 bits) |R|R|R|R|R|R|R|R|U|Y|S|H|N|P|L|F|
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |                                                               |
 ~                 Measurement Mode Sub-TLVs                     ~
 |                                                               |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4: STAMP Parameters TLV

The fields of the STAMP Parameters TLV are defined as follows:

4.1. Two-Way Measurement Mode Parameters Sub-TLV

The "Two-Way Measurement Mode Parameters" sub-TLV (Type=TBA1) identifies the two-way measurement mode described in Section 3.1 and carries the configuration parameters for that mode.

 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |STAMP TLV Flags|  Type=TBA1    |          Length=4             |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |  Session-Reflector UDP Port   |   Minimum Receive Interval    |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 5: Two-Way Measurement Mode Parameters Sub-TLV

The fields of the "Two-Way Measurement Mode Parameters" sub-TLV are defined as follows:

  • STAMP TLV Flags: The flags follow the procedures specified in [RFC8972].

  • Type: MUST be set to TBA1.

  • Length: A two-octet field set to 4, indicating that the Value field is four octets long.

  • Session-Reflector UDP Port: An unsigned 16-bit integer in network byte order that identifies the UDP port on the Session-Reflector for STAMP-Test packets in this mode. In a request, it MUST be set to 0. In a response, the value MUST be non-zero and indicates the Session-Reflector's configured port for this mode.

  • Minimum Receive Interval: An unsigned 16-bit integer in network byte order, expressed in milliseconds. In a request, it MUST be set to 0. In a response, the value MUST be non-zero and indicates the Session-Reflector's shortest configured receive interval for this mode.

4.2. One-Way Measurement Mode Parameters Sub-TLV

The "One-Way Measurement Mode Parameters" sub-TLV (Type=TBA2) identifies the one-way measurement mode described in Section 3.2 and carries the configuration parameters for that mode.

 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |STAMP TLV Flags|  Type=TBA2    |          Length=4             |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |  Session-Reflector UDP Port   |   Minimum Receive Interval    |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 6: One-Way Measurement Mode Parameters Sub-TLV

The fields of the "One-Way Measurement Mode Parameters" sub-TLV are defined as follows:

  • STAMP TLV Flags: The flags follow the procedures specified in [RFC8972].

  • Type: MUST be set to TBA2.

  • Length: A two-octet field set to 4, indicating that the Value field is four octets long.

  • Session-Reflector UDP Port: An unsigned 16-bit integer in network byte order that identifies the UDP port on the Session-Reflector for STAMP-Test packets in this mode. In a request, it MUST be set to 0. In a response, the value MUST be non-zero and indicates the Session-Reflector's configured port for this mode.

  • Minimum Receive Interval: An unsigned 16-bit integer in network byte order, expressed in milliseconds. In a request, it MUST be set to 0. In a response, it is the shortest interval at which the Session-Reflector is configured to receive and process STAMP-Test packets for this mode. A response value of zero is invalid.

4.3. Loopback Measurement Mode Parameters Sub-TLV

The "Loopback Measurement Mode Parameters" sub-TLV (Type=TBA3) identifies the loopback measurement mode described in Section 3.3. Presence of this sub-TLV in a request indicates that the Session-Sender requests loopback mode; its presence in a response indicates that the Session-Reflector supports loopback mode. Capability Flags are carried in the parent TLV and do not report capabilities for loopback mode.

 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |STAMP TLV Flags|  Type=TBA3    |          Length=0             |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 7: Loopback Measurement Mode Parameters Sub-TLV

The fields of the "Loopback Measurement Mode Parameters" sub-TLV are defined as follows:

  • STAMP TLV Flags: The flags follow the procedures specified in [RFC8972].

  • Type: MUST be set to TBA3.

  • Length: A two-octet field set to zero, indicating that the Value field is empty. The Session-Reflector MUST reject a loopback mode sub-TLV with a non-zero Length as malformed by setting the M (Malformed) flag to 1 as specified in [RFC8972].

  • Value: This sub-TLV has no Value field. It carries no capability flags or configuration parameters.

5. STAMP Signaling Procedures

5.1. Session-Sender Procedures

Before sending the first STAMP-Test packet with STAMP Parameters TLV, the Session-Sender MUST be configured with the Session-Reflector's IP address and STAMP UDP port number, and with an initial transmission interval that is acceptable under local policy. Each signaling request MUST include exactly one STAMP Parameters TLV. The Session-Sender MUST set all Capability Flags to 0, set the Profile ID to the desired profile or zero, set the Maximum Padding Size field to 0, and include one or more measurement mode sub-TLVs for the intended STAMP session, with no more than one sub-TLV for each mode. If the Session-Sender knows which mode or modes are configured for the Profile ID, it MAY include a sub-TLV for one or more of those modes. If it does not know which mode or modes are configured, it MAY include one sub-TLV for each mode whose parameters it wants for the session. In each one-way or two-way mode sub-TLV, it MUST set the Session-Reflector UDP Port and Minimum Receive Interval fields to 0. Other STAMP TLVs MAY be included subject to the procedures in [RFC8972].

The Session-Sender MUST wait for the corresponding reflected packet and validate its STAMP session identity and the returned TLV. If the Conformant Reflected Packet STAMP TLV flag is set to 1, the Session-Sender MUST treat the response as indicating that the requested Profile ID was not found. The Session-Sender MUST NOT start a measurement session using that Profile ID. If the STAMP Parameters TLV is returned with its parent U flag set, the Session-Sender MUST treat the TLV as unrecognized, MUST NOT use it to configure a session, and MUST continue with the existing STAMP procedure as specified in [RFC8762] and [RFC8972]. Otherwise, the returned parent TLV is valid only if its M flag is clear, its Length is at least 12 octets, its sub-TLV sequence is well-formed, it contains exactly one corresponding sub-TLV for each requested mode and no unrequested or duplicate mode sub-TLVs, and each sub-TLV has a valid length and value. The Session-Sender MUST treat a parent TLV with the M flag set or invalid fields as malformed. The U flag in a returned mode sub-TLV applies only to the corresponding measurement mode, as specified below.

When the parent TLV is recognized and valid, the Session-Sender MUST verify that the returned Profile ID matches its non-zero requested Profile ID. For each requested mode, it MUST inspect the U flag in the corresponding response sub-TLV. If that flag is set, the Session-Sender MUST treat the mode as unavailable for the selected Profile ID and MUST NOT use that sub-TLV to configure a session. If the flag is clear, it MUST verify that every capability bit required for that mode is set in the returned parent TLV's Capability Flags. For one-way and two-way modes, it MUST also verify that the returned Session-Reflector UDP Port and Minimum Receive Interval are non-zero. The Session-Sender MUST select a single available mode that meets its requirements for the STAMP session. If multiple returned modes meet its requirements, it MUST choose one according to local policy. If no returned mode meets its requirements, it MUST NOT start a measurement session and MAY terminate the signaling attempt.

After selecting a mode, the Session-Sender MAY create a STAMP-Test session using the parameters returned for that mode. For one-way or two-way mode, it MUST set the interval between consecutive STAMP-Test packets to no less than the returned Minimum Receive Interval. The Session-Sender MUST compute one-way metrics only if the returned Y bit is set and its own clock is synchronized; otherwise it MUST use two-way metrics or select another mode.

If the Session-Sender does not receive a valid signaling response within a locally configured timeout, it MUST NOT assume that the Session-Reflector supports the requested capabilities. It MAY retry the signaling request subject to the rate limits and retry policy configured for the session.

5.2. Session-Reflector Procedures

When a Session-Reflector receives a STAMP-Test packet containing the STAMP Parameters TLV, it MUST validate the TLV Length and all sub-TLVs. The Length MUST be at least 12 octets, and each sub-TLV MUST fit completely within the parent TLV Value. A request MUST contain one or more measurement mode sub-TLVs and MUST NOT contain more than one sub-TLV for any one mode. If the TLV or a sub-TLV is malformed, including a duplicate mode sub-TLV, the Session-Reflector MUST process the error using the malformed-TLV procedures in Section 4 of [RFC8972] by setting the M (Malformed) flag to 1.

If a valid request contains a non-zero Profile ID that the Session-Reflector does not find in its local configuration, the Session-Reflector MUST return the received STAMP Parameters TLV with the Conformant Reflected Packet STAMP TLV flag set to 1, following the procedure specified in [RFC10052].

For a valid request whose Profile ID is zero or is found in the Session-Reflector's local configuration, the Session-Reflector MUST return one STAMP Parameters TLV in the reflected STAMP-Test packet. It MUST set the Profile ID to the profile selected for the session (or zero if none is selected). It MUST set the Maximum Padding Size field to the maximum amount of additional padding it supports for the signaling session, or to 0 if it does not support extra padding. For each requested mode that is configured for the selected Profile ID, supported by the Session-Reflector, and permitted for the source node, it MUST return the corresponding measurement mode sub-TLV with U clear and the parameters it supports for that mode and, for one-way or two-way mode, its configured minimum receive interval in milliseconds. It MUST return exactly one corresponding sub-TLV for every requested mode, including modes that are unavailable as described below. It MUST report supported capabilities for the successfully returned modes in the parent TLV's Capability Flags. It MUST NOT advertise a capability or parameter that it cannot provide for the session. The Session-Reflector MUST return only capabilities and configuration parameters associated with the Profile ID selected for that request.

For each requested mode that is not configured for the selected Profile ID, not supported by the Session-Reflector, or prohibited by local policy for a session from the request's source node, the Session-Reflector MUST return the corresponding measurement mode sub-TLV with its U (Unrecognized) flag set to 1 and its M (Malformed) flag set to 0. It MUST preserve the sub-TLV's Type, Length, and Value and MUST NOT add negotiated STAMP parameters to that sub-TLV.

The Session-Reflector MUST enforce a receive-processing limit no more aggressive than the returned minimum interval for the selected one-way or two-way mode, subject to resource protection and local policy. This requirement does not apply to loopback mode. A Session-Reflector MAY change its capabilities or minimum interval as local configuration changes; a Session-Sender that observes a changed response SHOULD re-evaluate the session configuration.

For one-way and two-way modes, the Session-Reflector MAY support stateful operation and sets F in the parent TLV's Capability Flags to report that support. For two-way mode, the Session-Reflector MAY also support stateless operation and sets L in the parent TLV's Capability Flags to report that support.

A Session-Sender MUST use the TLV only with a Session-Reflector that follows [RFC8972] TLV reflection procedures.

After initial signaling, the Session-Sender MAY continue to include the TLV to detect changes in Session-Reflector capabilities or parameters. If it does so, it MUST revalidate the response and reconfigure or stop the session when the response no longer meets its requirements. A Session-Reflector MUST return the TLV whenever it receives a valid request TLV, including after the initial exchange.

6. Operational Considerations

The operational considerations specified in [RFC8762] and [RFC8972] apply. Operators configure the Session-Reflector endpoint and an initial Session-Sender rate before signaling can begin. This mechanism exchanges capabilities and session parameters; it does not discover endpoints or establish routing, security associations, or authorization policy.

For one-way and two-way modes, the Minimum Receive Interval is an operational limit for the Session-Reflector. Operators should provision intervals that protect Session-Reflector resources and avoid excessive traffic on the measured path.

A Session-Sender should choose a timestamp format and measurement metric that match both endpoints and the measurement objective.

7. Security Considerations

The security considerations specified in [RFC8762] and [RFC8972] apply. Since the TLV is carried in STAMP-Test packets, an on-path attacker able to modify or inject packets could alter advertised capabilities, profile identifiers, or rate parameters. Implementations SHOULD authenticate STAMP packets when the measurement environment requires protection against modification or injection.

The Session-Reflector's capability information can reveal implementation and operational details. Operators SHOULD restrict access to STAMP Session-Reflectors to authorized measurement endpoints and protect the information according to local policy. A Session-Reflector MUST continue to apply its configured resource limits regardless of values received in a signaling request; the request cannot raise the Session-Reflector's allowed receive rate or enable an unsupported capability.

8. IANA Considerations

IANA is requested to allocate the following TLVs from the IETF Review range of the "STAMP TLV Types" registry (see: https://www.iana.org/assignments/stamp-tlv-types) under the Simple Two-way Active Measurement Protocol (STAMP) TLV Types registry group:

Table 2: STAMP TLV Type
Value Description Reference
TBD STAMP Parameters This document

IANA is requested to allocate the following sub-TLV from the IETF Review range of the "STAMP Sub-TLV Types" registry (see: https://www.iana.org/assignments/stamp-tlv-types) under the Simple Two-way Active Measurement Protocol (STAMP) TLV Types registry group:

Table 3: STAMP Sub-TLV Types
Value Description Used In Reference
TBA1 Two-Way Measurement Mode Parameters STAMP Parameters TLV This document
TBA2 One-Way Measurement Mode Parameters STAMP Parameters TLV This document
TBA3 Loopback Measurement Mode Parameters STAMP Parameters TLV This document

9. References

9.1. Normative References

[RFC2119]
Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/info/rfc2119>.
[RFC8174]
Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, , <https://www.rfc-editor.org/info/rfc8174>.
[RFC3828]
Larzon, L., Degermark, M., Pink, S., Jonsson, L., Ed., and G. Fairhurst, Ed., "The Lightweight User Datagram Protocol (UDP-Lite)", RFC 3828, DOI 10.17487/RFC3828, , <https://www.rfc-editor.org/info/rfc3828>.
[RFC8762]
Mirsky, G., Jun, G., Nydell, H., and R. Foote, "Simple Two-Way Active Measurement Protocol", RFC 8762, DOI 10.17487/RFC8762, , <https://www.rfc-editor.org/info/rfc8762>.
[RFC8972]
Mirsky, G., Min, X., Nydell, H., Foote, R., Masputra, A., and E. Ruffini, "Simple Two-Way Active Measurement Protocol Optional Extensions", RFC 8972, DOI 10.17487/RFC8972, , <https://www.rfc-editor.org/info/rfc8972>.
[RFC10052]
Mirsky, G., Ruffini, E., Nydell, H., Foote, R., and W. Hawkins, "Performance Measurement with Asymmetrical Traffic Using the Simple Two-Way Active Measurement Protocol (STAMP)", RFC 10052, DOI 10.17487/RFC10052, , <https://www.rfc-editor.org/info/rfc10052>.

9.2. Informative References

[RFC5905]
Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch, "Network Time Protocol Version 4: Protocol and Algorithms Specification", RFC 5905, DOI 10.17487/RFC5905, , <https://www.rfc-editor.org/info/rfc5905>.
[IEEE1588]
IEEE, "IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems", IEEE Std 1588-2019, .

Author's Address

Rakesh Gandhi (editor)
Cisco Systems, Inc.
Canada