BPM Working Group R. Gandhi, Ed.
Internet-Draft Cisco Systems, Inc.
Intended status: Standards Track T. Zhou
Expires: 3 May 2027 Huawei
Z. Li
China Mobile
F. Ihle
University of Tuebingen
B. Wen
Comcast
30 October 2026
Simple Two-Way Active Measurement Protocol (STAMP) Extensions for
Reflecting STAMP Packet MPLS Network Action Headers
draft-ietf-bpm-stamp-mpls-hdr-00
Abstract
The Simple Two-Way Active Measurement Protocol (STAMP) and its
optional extensions can be used for Edge-to-Edge (E2E) active
measurements. In Situ Operations, Administration, and Maintenance
(IOAM) data fields can be used for recording and collecting Hop-by-
Hop (HBH) and E2E operational and telemetry information. This
document extends STAMP to reflect MPLS Network Action Sub-Stacks and
Post-Stack MPLS Headers for HBH and E2E active measurements, for
example, using the IOAM data fields.
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 3 May 2027.
Gandhi, et al. Expires 3 May 2027 [Page 1]
Internet-Draft STAMP Reflecting MPLS MNA Headers October 2026
Copyright Notice
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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions Used in This Document . . . . . . . . . . . . . . 3
2.1. Requirements Language . . . . . . . . . . . . . . . . . . 4
2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
2.3. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 4
2.4. STAMP Reference Topology . . . . . . . . . . . . . . . . 5
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4. Reflecting MPLS Header MNA Data . . . . . . . . . . . . . . . 6
4.1. Reflected MPLS Header MNA Data TLV . . . . . . . . . . . 6
4.2. Procedure for Reflecting MPLS MNA Data . . . . . . . . . 8
4.3. Receiving MPLS Headers from the Data Plane . . . . . . . 12
4.4. MTU Considerations . . . . . . . . . . . . . . . . . . . 12
5. Unidirectional and Bidirectional Measurements . . . . . . . . 13
5.1. MNA Header Control Sub-TLV . . . . . . . . . . . . . . . 13
5.2. Procedure for MNA Header Control . . . . . . . . . . . . 15
6. Use Case of Reflecting IOAM Data Fields . . . . . . . . . . . 16
7. Operational Considerations . . . . . . . . . . . . . . . . . 17
7.1. Verifying Received MPLS Headers . . . . . . . . . . . . . 18
8. Security Considerations . . . . . . . . . . . . . . . . . . . 18
9. Implementation Status . . . . . . . . . . . . . . . . . . . . 19
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 20
11.1. Normative References . . . . . . . . . . . . . . . . . . 20
11.2. Informative References . . . . . . . . . . . . . . . . . 21
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22
Gandhi, et al. Expires 3 May 2027 [Page 2]
Internet-Draft STAMP Reflecting MPLS MNA Headers October 2026
1. Introduction
The Simple Two-Way Active Measurement Protocol (STAMP) [RFC8762]
provides capabilities for the measurement of 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 TLVs for STAMP. STAMP-Test packets are transmitted along
a path between a Session-Sender and a Session-Reflector to measure
Edge-to-Edge (E2E) performance metrics, such as delay, delay
variation, and packet loss along that path.
In Situ Operations, Administration, and Maintenance (IOAM) is used
for recording and collecting operational and telemetry information
while a packet traverses a path between two points in the network.
The information from the collected IOAM data fields [RFC9197] can be
used to support Hop-by-Hop (HBH) and E2E measurement use cases.
MPLS packets may carry MPLS Network Action (MNA) Sub-Stacks (NASes),
as specified in [RFC9994], and Post-Stack MPLS Headers (PSMHs) for
the MNA type, as specified in [I-D.ietf-mpls-mna-ps-hdr].
[I-D.ietf-mpls-mna-ioam] specifies MNA Sub-Stacks and PSMHs to carry
the IOAM option types specified in [RFC9197] and [RFC9326] for an
MPLS data plane.
It may be desirable in some contexts (e.g., diagnostics) to record
and collect HBH and E2E operational and telemetry information using
active measurement packets between two nodes in a network. This is
achieved by using optional STAMP extensions to reflect MPLS NASes and
PSMHs as specified in this document. The procedure specified in this
document leverages existing implementations at midpoint nodes with an
MPLS data plane that supports the NASes and PSMHs, without any
additional requirements for processing STAMP-Test packets.
This document does not cover use cases in which NAS or PSMH lengths
change along the path, or in which NASes or PSMHs are added to or
removed from the MPLS header of a Session-Sender test packet along
the path. A PSMH can be defined for types other than MNA. This
document concerns only PSMHs for the MNA type
[I-D.ietf-mpls-mna-ps-hdr].
2. Conventions Used in This Document
Gandhi, et al. Expires 3 May 2027 [Page 3]
Internet-Draft STAMP Reflecting MPLS MNA Headers October 2026
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 terms defined in [RFC8762], specifically Session-
Sender, Session-Reflector, STAMP-Test packet, symmetric, and
symmetrical.
This document uses terms defined in [RFC8972], specifically STAMP TLV
Flags and Sub-TLVs.
The Conformant Reflected Packet STAMP TLV flag defined in [RFC10052]
is re-used for communicating the error conditions for the STAMP TLVs
defined in this document. The error conditions specified for the
STAMP TLVs defined in [RFC10052] are not applicable to the extensions
defined in this document.
2.3. Abbreviations
+==============+=====================+============================+
| Abbreviation | Meaning | Reference |
+==============+=====================+============================+
| E2E | Edge-to-Edge | [RFC9197] |
+--------------+---------------------+----------------------------+
| HBH | Hop-by-Hop | [RFC9994] |
+--------------+---------------------+----------------------------+
| IOAM | In Situ Operations, | [RFC9197] |
| | Administration, and | |
| | Maintenance | |
+--------------+---------------------+----------------------------+
| MPLS | Multiprotocol Label | [RFC9994] |
| | Switching | |
+--------------+---------------------+----------------------------+
| MNA | MPLS Network Action | [RFC9994] |
+--------------+---------------------+----------------------------+
| MTU | Maximum | [RFC9994] |
| | Transmission Unit | |
+--------------+---------------------+----------------------------+
| NAS | Network Action Sub- | [RFC9994] |
| | Stack | |
+--------------+---------------------+----------------------------+
| PSMH | Post-Stack MPLS | [I-D.ietf-mpls-mna-ps-hdr] |
Gandhi, et al. Expires 3 May 2027 [Page 4]
Internet-Draft STAMP Reflecting MPLS MNA Headers October 2026
| | Header | |
+--------------+---------------------+----------------------------+
| STAMP | Simple Two-Way | [RFC8762] |
| | Active Measurement | |
| | Protocol | |
+--------------+---------------------+----------------------------+
| TLV | Type-Length-Value | [RFC8972] |
+--------------+---------------------+----------------------------+
Table 1: Abbreviations
2.4. STAMP Reference Topology
In the "STAMP Reference Topology" shown in Figure 1, the STAMP
Session-Sender S1 initiates a Session-Sender test packet, and the
STAMP Session-Reflector R1 transmits a reply Session-Reflector test
packet. The Session-Reflector test packets are transmitted to the
Session-Sender S1 on the same path (i.e., the same set of links and
nodes as shown in Figure 1) or on a different path in the reverse
direction from the path taken towards the Session-Reflector R1. Node
M1 is a midpoint node along the path that does not perform any STAMP
processing. A STAMP-Test packet is not required to transit through
the same midpoint node M1 in both directions.
T1 T2
/ \
+-------+ Test Packet +-------+ +-------+
| | - - - - - - - - | | - - - - - - - - ->| |
| S1 |=================| M1 |===================| R1 |
| |<- - - - - - - - | | - - - - - - - - - | |
+-------+ +-------+ Reply Test Packet +-------+
\ /
T4 T3
STAMP Session-Sender STAMP Session-Reflector
Figure 1: STAMP Reference Topology
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 as ((T4 - T1) - (T3 - T2)). 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.
Gandhi, et al. Expires 3 May 2027 [Page 5]
Internet-Draft STAMP Reflecting MPLS MNA Headers October 2026
Timestamps T1 and T2 are used by the Session-Sender to measure the
one-way delay metric as (T2 - T1), also referred to as the near-end
(forward direction) delay metric. Note that the delay value (T4 -
T3), measured by the Session-Sender, is referred to as the far-end
(backward direction) one-way delay metric. The computation of the
one-way delay metric requires the clocks on the Session-Sender and
Session-Reflector to be synchronized, e.g., using PTPv2 [IEEE1588] or
NTPv4 [RFC5905].
3. Overview
As specified in [RFC8972], the Session-Sender test packets and the
Session-Reflector test packets are symmetric in size when including
all optional TLVs (but excluding transport and network headers). A
Session-Reflector reflects all received STAMP TLVs from the Session-
Sender test packet.
As specified in [RFC8762], STAMP-Test packets are transmitted with
IP/UDP headers. Since midpoint nodes do not process the UDP headers
in the packets, they are agnostic to the STAMP-Test packets in the
payload.
STAMP-Test packets may carry MPLS headers containing NASes and PSMHs.
This document defines procedures and STAMP extensions for a Session-
Reflector to reflect the received MPLS NASes and PSMHs back to the
Session-Sender for both unidirectional and bidirectional measurement
types (see Section 5).
The IPv4/IPv6 and UDP headers for STAMP-Test packets follow the
procedures specified in Section 3.1 of [I-D.ietf-ippm-stamp-ext-hdr].
4. Reflecting MPLS Header MNA Data
4.1. Reflected MPLS Header MNA Data TLV
This document defines the "Reflected MPLS Header MNA Data" TLV for
STAMP (Type TBA1). A Session-Sender uses this TLV to request
reflection of a Network Action Sub-Stack (NAS) or Post-Stack MPLS
Header (PSMH) received in its test packet. The TLV is carried in
Session-Sender and Session-Reflector test packets, and a STAMP-Test
packet MAY carry one or more TLVs of this type. The same TLV type is
used for NASes and PSMHs. The format of the TLV is shown in
Figure 2.
Gandhi, et al. Expires 3 May 2027 [Page 6]
Internet-Draft STAMP Reflecting MPLS MNA Headers October 2026
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Requested MPLS Header MNA Data (8 octets) |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Received MPLS Header MNA Data |
~ (Length - 8 octets) ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: Reflected MPLS Header MNA Data TLV
The "Reflected MPLS Header MNA Data" TLV fields are defined as
follows:
* STAMP TLV Flags: The STAMP TLV Flags follow the procedures
specified in Section 4 of [RFC8972].
* Type: MUST be set to TBA1.
* Length: A two-octet field containing the total length, in octets,
of the NAS or PSMH to be reflected.
* Requested MPLS Header MNA Data: A fixed 8-octet field containing
the first 8 octets of the target NAS or PSMH to be reflected.
This field identifies which NAS or PSMH in the received Session-
Sender test packet is copied into the "Reflected MPLS Header MNA
Data" TLV when multiple NASes or PSMHs of the same length are
present; the selection rules are in Section 4.2.
* Received MPLS Header MNA Data: A variable-length field containing
the remaining (Length - 8) octets of the NAS or PSMH after its
first 8 octets, copied from the received Session-Sender test
packet by the Session-Reflector.
In Session-Sender test packets, the data in this field MUST be
initialized to all zeros.
When a Session-Reflector recognizes the received "Reflected MPLS
Header MNA Data" TLV but cannot use it to reflect a received NAS or
PSMH, it MUST return the "Reflected MPLS Header MNA Data" TLV with
the Conformant Reflected Packet STAMP TLV flag set to 1, following
the procedure specified in [RFC10052]. This can occur, for example,
if:
Gandhi, et al. Expires 3 May 2027 [Page 7]
Internet-Draft STAMP Reflecting MPLS MNA Headers October 2026
* The requested length does not match the length of the received NAS
or PSMH.
* The Session-Reflector cannot access the received NASes or PSMHs
from the data plane, or the data plane does not support the
received NASes or PSMHs.
* No NAS or PSMH matches the requested data and length, or the NAS
or PSMH is invalid.
* More than one NAS or PSMH of the requested length matches a non-
zero Requested MPLS Header MNA Data field.
4.2. Procedure for Reflecting MPLS MNA Data
For each NAS [RFC9994] or PSMH [I-D.ietf-mpls-mna-ps-hdr] in a
Session-Sender test packet that the Session-Sender requires the
Session-Reflector to reflect, the Session-Sender MUST add a
corresponding "Reflected MPLS Header MNA Data" TLV (see Section 4.1)
to the test packet. The Session-Sender requests a copy of that NAS
or PSMH in the corresponding TLV in the Session-Reflector test
packet.
An example of a STAMP-Test packet carrying NASes, a PSMH, and their
corresponding "Reflected MPLS Header MNA Data" TLVs is shown in
Figure 3.
Gandhi, et al. Expires 3 May 2027 [Page 8]
Internet-Draft STAMP Reflecting MPLS MNA Headers October 2026
+---------------------------------------------------------------+
| MPLS Header |
~ ~
+---------------------------------------------------------------+
| MNA Sub-Stack-1 [RFC9994] |
~ ~
+---------------------------------------------------------------+
~ ... ~
+---------------------------------------------------------------+
| MNA Sub-Stack-N [RFC9994] |
~ ~
+---------------------------------------------------------------+
~ ... ~
+---------------------------------------------------------------+
| Post-Stack MPLS Header-1 [I-D.ietf-mpls-mna-ps-hdr] |
~ ~
+---------------------------------------------------------------+
| IP Header |
+---------------------------------------------------------------+
| UDP Header |
+---------------------------------------------------------------+
| STAMP Packet [RFC8972] |
~ ~
+---------------------------------------------------------------+
| Reflected MPLS Header MNA Data-1 TLV (TBA1) |
| MNA Sub-Stack |
~ ~
+---------------------------------------------------------------+
~ ... ~
+---------------------------------------------------------------+
| Reflected MPLS Header MNA Data-M TLV (TBA1) |
| MNA Sub-Stack |
~ ~
+---------------------------------------------------------------+
| Reflected MPLS Header MNA Data-1 TLV (TBA1) |
| Post-Stack MPLS Header |
~ ~
+---------------------------------------------------------------+
Note: M <= N for the NASes shown.
Figure 3: Example Session-Sender and Session-Reflector Test
Packet with Reflected MPLS Header MNA Data TLVs
When a Session-Sender test packet contains multiple NASes or PSMHs
that the Session-Sender requires the Session-Reflector to reflect,
the corresponding "Reflected MPLS Header MNA Data" TLVs MUST appear
in the same order as those headers in the test packet. When the
Gandhi, et al. Expires 3 May 2027 [Page 9]
Internet-Draft STAMP Reflecting MPLS MNA Headers October 2026
Session-Sender does not require the Session-Reflector to reflect a
NAS or PSMH in the Session-Reflector test packet, the Session-Sender
MUST NOT add a corresponding "Reflected MPLS Header MNA Data" TLV to
its test packet. In this case, the total number of "Reflected MPLS
Header MNA Data" TLVs is less than the total number of NASes and
PSMHs in the Session-Sender test packet.
The number of "Reflected MPLS Header MNA Data" TLVs MUST NOT exceed
the total number of NASes and PSMHs in the Session-Sender test
packet.
If multiple NASes or PSMHs of the same length are present and the
Session-Sender requires the Session-Reflector to reflect only some of
them, the Session-Sender MUST populate the Requested MPLS Header MNA
Data field (see Figure 2) with the first 8 octets of the NAS or PSMH
to be reflected.
When multiple NASes or PSMHs have the same requested length and the
same first 8 octets, the Session-Sender can request reflection of all
of them by including one TLV for each header, in packet order. The
Session-Sender MUST NOT use these octets to selectively request only
some of those headers.
- The Session-Sender MUST set to zero each octet in the Requested
MPLS Header MNA Data field containing any part of a field that can
change in transit (a mutable field), for example, the 13-bit
Ancillary Data field in a NAS or the 16-bit Post-Stack Data field in
a PSMH. Because zero is a wildcard, the Session-Sender MUST NOT rely
on matching a zero-valued octet. For a non-zero value in the
Requested MPLS Header MNA Data field, the Session-Sender MUST request
selective reflection only if exactly one NAS or PSMH matches.
- The Session-Reflector compares only the non-zero octets of the
field. The Session-Reflector processes the "Reflected MPLS Header
MNA Data" TLVs in order and matches each TLV to the first NAS or
PSMH, not already matched by an earlier TLV, that has the requested
length and whose octets equal the non-zero octets of the field. This
allows successive TLVs to request reflection of multiple headers that
match the same Requested MPLS Header MNA Data field and requested
length.
Gandhi, et al. Expires 3 May 2027 [Page 10]
Internet-Draft STAMP Reflecting MPLS MNA Headers October 2026
Before requesting reflection of MPLS header MNA data, the Session-
Sender MUST be configured to request the applicable data from the
Session-Reflector. The Session-Reflector MUST apply the local
reflection policy specified in Section 7 before copying header data.
When reflection is not permitted by policy, the Session-Reflector
MUST NOT copy the requested NAS or PSMH data and MUST return the
corresponding TLV with the Conformant Reflected Packet STAMP TLV flag
set to 1, following the procedure specified in [RFC10052].
When a Session-Reflector supports the "Reflected MPLS Header MNA
Data" TLV and receives a Session-Sender test packet containing a
valid NAS or PSMH and a corresponding TLV, the following rules apply
to requests permitted by the local reflection policy:
1. If the Requested MPLS Header MNA Data field is not all zeros, the
Session-Reflector MUST compare it with the first 8 octets of each
NAS or PSMH of the requested length that has not already been
selected for an earlier TLV. A zero octet in the requested field
MUST match any value; each non-zero octet MUST match the
corresponding header octet exactly. The Session-Reflector MUST
select the header if exactly one header matches.
If no header or more than one header matches, the Session-
Reflector MUST return the TLV with the Conformant Reflected
Packet STAMP TLV flag set to 1, following the procedure specified
in [RFC10052], and MUST NOT copy header data.
If the Requested MPLS Header MNA Data field is all zeros, the
Session-Reflector MUST select the first NAS or PSMH of the
requested length that has not already been selected for an
earlier TLV and copy its first 8 octets into that field.
2. The Session-Reflector MUST copy the portion of the NAS or PSMH
after its first 8 octets into the Received MPLS Header MNA Data
field in the Session-Reflector test packet.
3. When the received Session-Sender test packet contains multiple
NASes or PSMHs, the Session-Reflector MUST process them in order,
starting with the top of the label stack, and copy each header
into its corresponding "Reflected MPLS Header MNA Data" TLV in
the Session-Reflector test packet, if such a TLV is present.
4. When a Session-Reflector receives a Session-Sender test packet
containing a NAS or PSMH without a corresponding "Reflected MPLS
Header MNA Data" TLV, it cannot copy that header into the
Session-Reflector test packet.
Gandhi, et al. Expires 3 May 2027 [Page 11]
Internet-Draft STAMP Reflecting MPLS MNA Headers October 2026
Because this procedure leverages existing implementations at midpoint
nodes, no additional requirements are imposed related to STAMP when
NASes and PSMHs are carried in STAMP-Test packets. Midpoint nodes
process these headers using the procedures specified in their
defining documents.
4.3. Receiving MPLS Headers from the Data Plane
For the HBH and Ingress-to-Egress (I2E) scopes, the penultimate node
MUST NOT remove the last copy of the NASes and PSMHs. As a result,
the egress node receives them, as specified in Section 9.3 of
[RFC9994] ("Penultimate Node Responsibilities") and Section 6.3 of
[I-D.ietf-mpls-mna-ps-hdr] ("Penultimate Node Responsibilities").
For the "Select" scope, the NAS and its corresponding PSMH are
removed from a packet at the transit node that processes the NAS.
Therefore, they are not received by the egress node.
The data plane MUST provide the received MPLS headers containing the
NASes and PSMHs from the Session-Sender test packets to the Session-
Reflector for both unidirectional and bidirectional measurement types
(see Section 5).
Similarly, for the reverse direction, the data plane MUST provide the
received MPLS headers containing the NASes and PSMHs from the
Session-Reflector test packets to the Session-Sender for the
bidirectional measurement type (see Section 5).
4.4. MTU Considerations
Each Session-Sender and Session-Reflector needs to know the
applicable path MTU for the direction in which it transmits STAMP-
Test packets. This information may be provisioned, collected through
management protocols, learned through a path-MTU-discovery mechanism
such as Path MTU Discovery for IPv6 [RFC8201] or through MTU
signaling for Label Distribution Protocol [RFC3988], or distributed
by a control protocol. The mechanisms for obtaining this information
are outside the scope of this document.
The transmitting node MUST ensure that the complete STAMP-Test
packet, including all applicable MPLS, IP, UDP, STAMP, and "Reflected
MPLS Header MNA Data" TLV fields, does not exceed the applicable path
MTU. If the packet exceeds this limit, the node MUST remove complete
"Reflected MPLS Header MNA Data" TLVs, skipping the HMAC TLV (Type 8)
[RFC8972] if present, one at a time, starting with the last TLV in
the packet, until the packet fits within the path MTU. If an HMAC
TLV was present and if any preceding TLV was removed, the HMAC digest
MUST be updated as specified in Section 4.8 of [RFC8972]. The
Gandhi, et al. Expires 3 May 2027 [Page 12]
Internet-Draft STAMP Reflecting MPLS MNA Headers October 2026
remaining TLVs MUST retain their relative order. If removing all
"Reflected MPLS Header MNA Data" TLVs does not bring the packet
within the path MTU, the node MUST NOT transmit it.
The Session-Reflector MUST return requested TLVs that it can process
in the order received. The Session-Sender can identify the MTU-
driven removal by comparing the ordered TLV sequence it sent with the
sequence returned by the Session-Reflector; an intentionally
unrequested header has no corresponding TLV in the Session-Sender
packet. The Conformant Reflected Packet STAMP TLV flag does not
indicate MTU-driven removal.
5. Unidirectional and Bidirectional Measurements
5.1. MNA Header Control Sub-TLV
This document defines the "MNA Header Control" Sub-TLV (Type TBA2)
for the "Reflected Test Packet Control" TLV (Type 12) [RFC10052].
This Sub-TLV is used to force the Session-Reflector to generate and
add matching NASes and PSMHs in the reply test packets. The format
of the "MNA Header Control" Sub-TLV is shown in Figure 4.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sub-TLV Flags | Type = TBA2 | Sub-TLV Length = 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4: MNA Header Control Sub-TLV
The MNA Header Control Sub-TLV fields are defined as follows:
* Sub-TLV Flags: An eight-bit field. The format, values, and
interpretation of flags are as defined for STAMP TLV Flags
[RFC8972]. Flag values are taken from the "STAMP TLV Flags"
registry [IANA-STAMP].
* Type: MUST be set to TBA2.
* Sub-TLV Length: A two-octet field equal to the length of the Data
field in octets. It MUST be set to 0. Otherwise, if the length
is non-zero, the Session-Reflector MUST return the Sub-TLV with
the Malformed flag set to 1 in the Sub-TLV Flags field as
specified in [RFC8972].
When the "Reflected Test Packet Control" TLV is included only to
carry the "MNA Header Control" Sub-TLV, the Session-Sender MUST set
the Number of the Reflected Packets field to 1, the Interval Between
Gandhi, et al. Expires 3 May 2027 [Page 13]
Internet-Draft STAMP Reflecting MPLS MNA Headers October 2026
the Reflected Packets field to 0, and the Length of the Reflected
Packet field to 0, so that a single Session-Reflector test packet is
returned with the length given by Section 3 of [RFC10052]. The
bidirectional measurement type requires that support for the
"Reflected Test Packet Control" TLV is enabled on the Session-
Reflector (Section 5 of [RFC10052]).
When a Session-Reflector receives a Session-Sender test packet with
the "MNA Header Control" Sub-TLV and the Session-Reflector supports
this Sub-TLV, the following rules apply:
1. The Session-Reflector MUST add locally generated matching NASes
and PSMHs (headers of the same type carrying the same option
types, for example, the same IOAM Option-Type and Namespace-ID)
in the Session-Reflector test packets, subject to the relevant
MPLS data-plane specifications, in the same order in which the
corresponding NASes and PSMHs appear in the received Session-
Sender test packet. The generated headers need not be byte-for-
byte copies of the received headers.
2. In the absence of the "MNA Header Control" Sub-TLV in the
received Session-Sender test packet, a Session-Reflector MUST
omit adding locally generated matching NASes and PSMHs in the
Session-Reflector test packet corresponding to the received NASes
and PSMHs. This does not preclude the Session-Reflector from
adding MPLS headers independently of the received MPLS headers.
3. The NASes and PSMHs received in the Session-Sender test packets
MUST be copied and reflected in the corresponding "Reflected MPLS
Header MNA Data" TLVs to the Session-Sender according to the
procedure in Section 4.2, regardless of whether the "MNA Header
Control" Sub-TLV is present.
4. If the Session-Reflector cannot add a new matching NAS or PSMH in
the Session-Reflector test packet, the Session-Reflector MUST
return the "Reflected Test Packet Control" TLV (Type 12)
[RFC10052] with the Conformant Reflected Packet STAMP TLV flag
set to 1 in the Sub-TLV Flags of the "MNA Header Control" Sub-TLV
using the procedure specified in [RFC10052]. This can occur, for
example, when the Session-Reflector does not support the received
NAS or PSMH or when the Session-Reflector cannot access the
received NASes or PSMHs from the data plane.
STAMP-Test packets MUST NOT carry more than one "MNA Header Control"
Sub-TLV in a "Reflected Test Packet Control" TLV (Type 12)
[RFC10052]. If the "Reflected Test Packet Control" TLV (Type 12) in
the Session-Sender test packet contains more than one "MNA Header
Control" Sub-TLV, the Session-Reflector MUST return the "Reflected
Gandhi, et al. Expires 3 May 2027 [Page 14]
Internet-Draft STAMP Reflecting MPLS MNA Headers October 2026
Test Packet Control" TLV (Type 12) with the Conformant Reflected
Packet STAMP TLV flag set to 1 in the Sub-TLV Flags of each "MNA
Header Control" Sub-TLV, using the procedure specified in [RFC10052].
5.2. Procedure for MNA Header Control
This document defines two measurement types for the NASes and PSMHs
carried in a two-way STAMP session: unidirectional (forward direction
only) and bidirectional (forward and reverse directions). These
types relate only to whether the Session-Reflector adds locally
generated new matching NASes and PSMHs in the Session-Reflector test
packets for the reverse path. The Session-Reflector still copies the
received NASes and PSMHs into the corresponding "Reflected MPLS
Header MNA Data" TLVs (see Section 4.1) in both measurement types.
The measurement type for a STAMP session is locally provisioned on
the STAMP Session-Sender.
In the bidirectional measurement type:
A Session-Reflector adds locally generated matching NASes and PSMHs
to the Session-Reflector test packets, subject to the relevant MPLS
data-plane specifications, in the same order as the NASes and PSMHs
received in the Session-Sender test packets for the reverse-direction
measurement. These headers need not be byte-for-byte copies of the
received headers; their length and content are local decisions at the
Session-Reflector.
The STAMP Session-Sender enables this type by adding the "MNA Header
Control" Sub-TLV (see Section 5.1) for the "Reflected Test Packet
Control" TLV (Type 12) [RFC10052] to the Session-Sender test packets.
In the unidirectional measurement type:
A Session-Reflector MUST omit adding new matching NASes and PSMHs to
the Session-Reflector test packets in response to the NASes and PSMHs
received in the Session-Sender test packets. This does not preclude
the Session-Reflector from adding MPLS headers independently.
This type is the default if the "MNA Header Control" Sub-TLV is
absent from the Session-Sender test packet.
Gandhi, et al. Expires 3 May 2027 [Page 15]
Internet-Draft STAMP Reflecting MPLS MNA Headers October 2026
6. Use Case of Reflecting IOAM Data Fields
IOAM is used for recording and collecting operational and telemetry
information while a packet traverses a path between two points in the
network. The IOAM data fields are specified in [RFC9197]. Examples
of data recorded by IOAM Trace Options include per-hop information,
such as node ID, timestamp, queue depth, interface identifier, and
interface load. The information collected can be used for monitoring
paths, proof-of-transit, and troubleshooting failures in the network.
IOAM can be used with STAMP-Test packets for active measurements.
The procedure and STAMP extensions specified in this document can be
used to reflect the collected IOAM data fields back to the Session-
Sender, where the Session-Sender can use this information to support
HBH and E2E measurement use cases.
[I-D.ietf-mpls-mna-ioam] defines MNA extensions for NASes and PSMHs
to carry the IOAM option types specified in [RFC9197] for the MPLS
data plane. The STAMP Session-Sender and Session-Reflector test
packets carry NASes and PSMHs with IOAM option types for recording
and collecting HBH and E2E operational and telemetry information for
active measurements, as shown in Figure 5.
+---------------------------------------------------------------+
| MPLS Header |
+---------------------------------------------------------------+
| IOAM MNA Sub-Stack [I-D.ietf-mpls-mna-ioam] |
~ ~
+---------------------------------------------------------------+
| IOAM Post-Stack MPLS Header [I-D.ietf-mpls-mna-ioam] |
~ ~
+---------------------------------------------------------------+
| IP Header |
+---------------------------------------------------------------+
| UDP Header |
+---------------------------------------------------------------+
| STAMP Packet [RFC8972] |
+---------------------------------------------------------------+
| Reflected MPLS Header MNA Data TLV (TBA1) |
| IOAM MNA Sub-Stack |
~ ~
+---------------------------------------------------------------+
| Reflected MPLS Header MNA Data TLV (TBA1) |
| IOAM Post-Stack MPLS Header |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 5: Example Session-Sender and Session-Reflector Test
Packet for IOAM with Reflected MPLS Header MNA Data TLVs
Gandhi, et al. Expires 3 May 2027 [Page 16]
Internet-Draft STAMP Reflecting MPLS MNA Headers October 2026
The Session-Sender node, midpoint nodes, and the Session-Reflector
node process the IOAM data fields, as specified in [RFC9197]. Note
that using the IOAM option type "Incremental Trace Option-Type" is
not supported by [I-D.ietf-mpls-mna-ioam].
IOAM Direct Exporting [RFC9326] is applicable to STAMP-Test packets
for on-path telemetry use cases. In this case, the Session-Reflector
is not required to reflect the IOAM option type, since no IOAM data
fields would be recorded in the STAMP-Test packets. Hence, the
Session-Sender MUST omit a corresponding "Reflected MPLS Header MNA
Data" TLV in Session-Sender test packets for the IOAM Direct
Exporting option type.
7. Operational Considerations
The operational considerations specified in [RFC8762], [RFC10052],
[RFC9994], and [I-D.ietf-mpls-mna-ps-hdr] apply to the procedures and
extensions specified in this document.
The management and deployment considerations in [RFC9197] also apply
when using the IOAM data fields specified in that document.
The configuration and state introduced in this document are expected
to be covered by the STAMP YANG module [I-D.ietf-ippm-stamp-yang].
Implementations MUST support the ability to provision the measurement
type as unidirectional or bidirectional, as specified in Section 5.
When reflecting a STAMP-Test packet with the Conformant Reflected
Packet STAMP TLV flag set to 1, an implementation SHOULD log the
specific error condition locally as well as increment a count for the
error condition on the Session-Reflector.
Before transmitting STAMP-Test packets, the operator must establish,
through explicit configuration or a control-plane mechanism, that the
intended receiving endpoint is enabled to receive the configured
STAMP traffic and supports the features used by the session. The
configuration or control-plane mechanism must cover the endpoint
addresses, UDP ports, and traffic profile, including the rate and
burst limits specified in Section 9.3 of
[I-D.ietf-ippm-stamp-ext-hdr], and must account for reflected traffic
in the reverse direction. Operators must restrict STAMP traffic to
configured endpoints using session configuration and appropriate
forwarding and access-control policies.
Configuring an endpoint to receive STAMP-Test traffic does not, by
itself, enable reflection of received MPLS NASes or PSMHs.
Implementations MUST provide a configurable local reflection policy
Gandhi, et al. Expires 3 May 2027 [Page 17]
Internet-Draft STAMP Reflecting MPLS MNA Headers October 2026
on the Session-Reflector. An operator must configure this policy to
identify the Session-Senders and header data configured for
reflection to avoid exposing the collected network information to
Session-Senders.
The STAMP session state notifications specified in Section 9.2 of
[I-D.ietf-ippm-stamp-ext-hdr] and rate limiting considerations
specified in Section 9.3 of [I-D.ietf-ippm-stamp-ext-hdr] also apply
to the STAMP-Test sessions using the procedures specified in this
document.
7.1. Verifying Received MPLS Headers
The procedure in Section 4.2 requires the first 8 octets of each NAS
or PSMH to remain unchanged in transit excluding the mutable fields
as identified by value 0 when multiple headers of the same length are
present and only some are to be copied into STAMP TLVs.
Additionally, the procedure specified requires the data plane to
provide the received MPLS headers to Session-Senders and Session-
Reflectors hosted in the control plane as specified in Section 4.3.
For the reasons mentioned above, an operator should verify that the
NASes and PSMHs are received correctly at both the Session-Reflector
and the Session-Sender.
8. Security Considerations
The security considerations specified in [RFC8762], [RFC8972],
[RFC9994], [RFC10052], and [I-D.ietf-mpls-mna-ps-hdr] apply to the
procedure and extensions specified in this document. In addition,
the security considerations specified in [RFC9197] and
[I-D.ietf-mpls-mna-ioam] also apply when using NASes and PSMHs for
IOAM data fields.
The security considerations specified in
[I-D.ietf-ippm-stamp-ext-hdr] to mitigate attacks also apply to the
STAMP-Test packets using the procedure and extensions specified in
this document.
The procedures specified in this document are intended for deployment
in a single network administrative domain. To mitigate any threats,
operators should filter STAMP-Test packets at the edges of the
network administrative domain. It is assumed that the operator has
verified the integrity of the paths in the forward and reverse
directions used to transmit STAMP-Test packets so that collected
network information is not exposed to an undesired node.
Gandhi, et al. Expires 3 May 2027 [Page 18]
Internet-Draft STAMP Reflecting MPLS MNA Headers October 2026
9. Implementation Status
Editorial note: Please remove this section prior to publication.
An open-source implementation of STAMP with optional TLVs specified
in [RFC8972], MPLS Network Action (with In-Stack and Post-Stack
Data), and the IOAM preallocated trace option [RFC9197] is available
for the Tofino2 platform. It supports unidirectional and
bidirectional measurement types for HBH delay measurements across
four transit nodes using the extensions specified in this document.
- https://github.com/uni-tue-kn/stamp-mpls-mna-poc
Contact:
Fabian Ihle
University of Tuebingen
Germany
Email: fabian.ihle@uni-tuebingen.de
10. IANA Considerations
IANA is requested to allocate the following TLV 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:
+=======+================================+===============+
| Value | Description | Reference |
+=======+================================+===============+
| TBA1 | Reflected MPLS Header MNA Data | This document |
+-------+--------------------------------+---------------+
Table 2: STAMP TLV Types
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:
Gandhi, et al. Expires 3 May 2027 [Page 19]
Internet-Draft STAMP Reflecting MPLS MNA Headers October 2026
+=======+====================+================+===========+
| Value | Description | TLV Used | Reference |
+=======+====================+================+===========+
| TBA2 | MNA Header Control | Reflected Test | This |
| | | Packet Control | document |
+-------+--------------------+----------------+-----------+
Table 3: Sub-TLV Type for Reflected Test Packet Control TLV
Note to the RFC Editor: Please replace all occurrences of TBA1 and
TBA2 with the values assigned by IANA.
11. References
11.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<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,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8762] Mirsky, G., Jun, G., Nydell, H., and R. Foote, "Simple
Two-Way Active Measurement Protocol", RFC 8762,
DOI 10.17487/RFC8762, March 2020,
<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, January 2021,
<https://www.rfc-editor.org/info/rfc8972>.
[RFC9197] Brockners, F., Ed., Bhandari, S., Ed., and T. Mizrahi,
Ed., "Data Fields for In Situ Operations, Administration,
and Maintenance (IOAM)", RFC 9197, DOI 10.17487/RFC9197,
May 2022, <https://www.rfc-editor.org/info/rfc9197>.
[RFC9326] Song, H., Gafni, B., Brockners, F., Bhandari, S., and T.
Mizrahi, "In Situ Operations, Administration, and
Maintenance (IOAM) Direct Exporting", RFC 9326,
DOI 10.17487/RFC9326, November 2022,
<https://www.rfc-editor.org/info/rfc9326>.
Gandhi, et al. Expires 3 May 2027 [Page 20]
Internet-Draft STAMP Reflecting MPLS MNA Headers October 2026
[RFC9994] Rajamanickam, J., Ed., Gandhi, R., Ed., Zigler, R., Song,
H., and K. Kompella, "MPLS Network Action (MNA) Sub-Stack
Specification Including In-Stack Network Actions and
Data", RFC 9994, DOI 10.17487/RFC9994, June 2026,
<https://www.rfc-editor.org/info/rfc9994>.
[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,
September 2026,
<https://www.rfc-editor.org/info/rfc10052>.
[I-D.ietf-ippm-stamp-ext-hdr]
Gandhi, R., Zhou, T., Li, Z., and W. Hawkins, "Simple Two-
Way Active Measurement Protocol (STAMP) Extensions for
Reflecting STAMP Packet IP Headers", Work in Progress,
Internet-Draft, draft-ietf-ippm-stamp-ext-hdr-25, 22
October 2026, <https://datatracker.ietf.org/doc/html/
draft-ietf-ippm-stamp-ext-hdr-25>.
[I-D.ietf-mpls-mna-ps-hdr]
Rajamanickam, J., Gandhi, R., Zigler, R., Dong, J., and J.
Bhattacharya, "MPLS Network Action (MNA) Post-Stack Header
Specification", Work in Progress, Internet-Draft, draft-
ietf-mpls-mna-ps-hdr-19, 6 August 2026,
<https://datatracker.ietf.org/doc/html/draft-ietf-mpls-
mna-ps-hdr-19>.
[I-D.ietf-mpls-mna-ioam]
Gandhi, R., Mirsky, G., Song, H., Wen, B., and V. Kozak,
"MPLS Network Actions for In Situ Operations,
Administration, and Maintenance", Work in Progress,
Internet-Draft, draft-ietf-mpls-mna-ioam-14, 11 September
2026, <https://datatracker.ietf.org/doc/html/draft-ietf-
mpls-mna-ioam-14>.
[IANA-STAMP]
IANA, "Simple Two-way Active Measurement Protocol (STAMP)
TLV Types",
<https://www.iana.org/assignments/stamp-tlv-types>.
11.2. Informative References
[RFC3988] Black, B. and K. Kompella, "Maximum Transmission Unit
Signalling Extensions for the Label Distribution
Protocol", RFC 3988, DOI 10.17487/RFC3988, February 2005,
<https://www.rfc-editor.org/info/rfc3988>.
Gandhi, et al. Expires 3 May 2027 [Page 21]
Internet-Draft STAMP Reflecting MPLS MNA Headers October 2026
[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, June 2010,
<https://www.rfc-editor.org/info/rfc5905>.
[RFC8201] McCann, J., Deering, S., Mogul, J., and R. Hinden, Ed.,
"Path MTU Discovery for IP version 6", STD 87, RFC 8201,
DOI 10.17487/RFC8201, July 2017,
<https://www.rfc-editor.org/info/rfc8201>.
[I-D.ietf-ippm-stamp-yang]
Mirsky, G., Min, X., Luo, W. S., and R. Gandhi, "Simple
Two-way Active Measurement Protocol (STAMP) Data Model",
Work in Progress, Internet-Draft, draft-ietf-ippm-stamp-
yang-12, 5 November 2023,
<https://datatracker.ietf.org/doc/html/draft-ietf-ippm-
stamp-yang-12>.
[IEEE1588] IEEE, "IEEE Standard for a Precision Clock Synchronization
Protocol for Networked Measurement and Control Systems",
IEEE Std 1588-2008, 2008.
Acknowledgments
The authors of this document would like to thank Greg Mirsky for
reviewing this document and providing review comments. The authors
would also like to thank Fabian Ihle for implementing the solution
defined in this document in Tofino2. The authors thank the reviewers
of [I-D.ietf-ippm-stamp-ext-hdr], this document leverages it.
Authors' Addresses
Rakesh Gandhi (editor)
Cisco Systems, Inc.
Canada
Email: rgandhi@cisco.com
Tianran Zhou
Huawei
China
Email: zhoutianran@huawei.com
Zhenqiang Li
China Mobile
China
Email: lizhenqiang@chinamobile.com
Gandhi, et al. Expires 3 May 2027 [Page 22]
Internet-Draft STAMP Reflecting MPLS MNA Headers October 2026
Fabian Ihle
University of Tuebingen
Tuebingen
Germany
Email: fabian.ihle@uni-tuebingen.de
Bin Wen
Comcast
United States of America
Email: Bin_Wen@cable.comcast.com
Gandhi, et al. Expires 3 May 2027 [Page 23]