BPM Working Group R. Gandhi, Ed.
Internet-Draft Cisco Systems, Inc.
Intended status: Standards Track P. Schoenmaker
Expires: 6 May 2027 Meta Platforms, Inc.
R. Foote
Nokia
L. Zhang
Huawei Technologies
2 November 2026
Simple Two-Way Active Measurement Protocol (STAMP) Extensions for
Residual Bit Error Rate Measurement
draft-ietf-bpm-stamp-ber-01
Abstract
The Simple Two-Way Active Measurement Protocol (STAMP), specified in
RFC 8762, and its optional extensions, specified in RFC 8972, support
active measurement. Networks may experience transmission bit errors
due to various factors, including poor fiber quality. Even with
efficient FEC and CRC mechanisms, some bit errors may escape
detection and correction; these are referred to as residual bit
errors. This document further augments the STAMP extensions
specified in RFC 8972 to enable the measurement of the residual bit
error rate within the "Extra Padding" TLV of STAMP-Test packets.
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 6 May 2027.
Copyright Notice
Copyright (c) 2026 IETF Trust and the persons identified as the
document authors. All rights reserved.
Gandhi, et al. Expires 6 May 2027 [Page 1]
Internet-Draft STAMP for Residual Bit Error Rate November 2026
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 . . . . . . . . . . . . . . . . . . . . . . . . 2
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 . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Residual BER in Padding TLV Extension . . . . . . . . . . . . 7
4.1. Bit Pattern in Padding Sub-TLV . . . . . . . . . . . . . 8
5. STAMP Procedure for Residual BER Measurement . . . . . . . . 8
5.1. STAMP Session-Sender . . . . . . . . . . . . . . . . . . 9
5.1.1. MTU Considerations . . . . . . . . . . . . . . . . . 10
5.1.2. Bit Pattern Considerations . . . . . . . . . . . . . 10
5.2. STAMP Session-Reflector . . . . . . . . . . . . . . . . . 10
5.2.1. STAMP TLV Conformant Check . . . . . . . . . . . . . 11
5.3. Considerations for a Link Aggregation Group . . . . . . . 12
6. Operational Considerations . . . . . . . . . . . . . . . . . 12
6.1. Configuration Data Model Parameters . . . . . . . . . . . 12
6.2. Operational Data Model Parameters . . . . . . . . . . . . 13
7. Security Considerations . . . . . . . . . . . . . . . . . . . 14
8. Implementation Status . . . . . . . . . . . . . . . . . . . . 14
8.1. Open Source Implementation . . . . . . . . . . . . . . . 14
8.2. Cisco Implementation . . . . . . . . . . . . . . . . . . 15
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 15
10.1. Normative References . . . . . . . . . . . . . . . . . . 15
10.2. Informative References . . . . . . . . . . . . . . . . . 16
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17
1. Introduction
The Simple Two-Way Active Measurement Protocol (STAMP) is designed to
measure various performance metrics in IP networks without relying on
a control channel to pre-signal session parameters, as specified in
[RFC8762]. STAMP-Test packets are sent between a Session-Sender and
a Session-Reflector to measure delay and packet loss along the path.
Gandhi, et al. Expires 6 May 2027 [Page 2]
Internet-Draft STAMP for Residual Bit Error Rate November 2026
[RFC8972] introduces optional extensions for STAMP in the form of
Type-Length-Value (TLV) objects, including the capability to transmit
the "Extra Padding" (Type=1) TLV within STAMP-Test packets.
Networks may experience transmission bit errors due to various
factors, such as poor fiber quality. These errors can corrupt
packets. Bit errors can be single-bit errors or occur in bursts.
Bit errors in the received packets can be corrected using Forward
Error Correction (FEC) [RFC3819]. The remaining bit errors in the
received packets can be detected using a Cyclic Redundancy Check
(CRC) [RFC3819]. Packets that fail CRC validation may be discarded
[RFC3819]. Even with efficient FEC and CRC mechanisms, some bit
errors may escape detection and correction; these are referred to as
residual bit errors [RFC3819]. Residual bit errors can also result
from packet corruption during data marshalling between protocol
layers, such as padding or alignment issues, encoding conflicts, and
buffer overflows or underflows. These bit errors can cause checksum
failures in upper-layer protocols such as UDP and TCP, resulting in
packet drops. Measuring the residual bit error rate (BER), also
called the bit error ratio [RFC3385], using active measurement
packets between two nodes is beneficial for detecting service
degradation. For an accurate measurement of residual BER,
transmitting large active measurement packets is preferable,
especially on links with low bit error rates. Furthermore, there is
a need to transmit active measurement packets at a high rate to
measure residual BER on high-capacity links.
STAMP-Test packets are transported over UDP. The UDP checksum can be
used to check the integrity of the header and payload. However, the
checksum field does not provide an accurate measurement of bit
errors.
The authenticated mode provides data integrity protection for STAMP-
Test packets by adding a Hashed Message Authentication Code (HMAC),
such as HMAC-SHA-256 [RFC8762]. However, the authenticated mode does
not provide an accurate measurement of bit errors. In addition, the
"HMAC" TLV defined in [RFC8972] for authenticating STAMP TLVs does
not verify the integrity of the "Extra Padding" TLV.
This document further augments the STAMP extensions defined in
[RFC8972] to enable the measurement of the residual bit error rate
within the "Extra Padding" TLV of STAMP-Test packets.
2. Conventions Used in This Document
Gandhi, et al. Expires 6 May 2027 [Page 3]
Internet-Draft STAMP for Residual Bit Error Rate November 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 reused to communicate the error conditions for the STAMP TLV and
the Sub-TLV 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 |
+==============+===========================+===========+
| BER | Bit Error Rate | [RFC3385] |
+--------------+---------------------------+-----------+
| CRC | Cyclic Redundancy Check | [RFC3819] |
+--------------+---------------------------+-----------+
| FEC | Forward Error Correction | [RFC3819] |
+--------------+---------------------------+-----------+
| MTU | Maximum Transmission Unit | [RFC8200] |
+--------------+---------------------------+-----------+
| STAMP | Simple Two-Way Active | [RFC8762] |
| | Measurement Protocol | |
+--------------+---------------------------+-----------+
| TLV | Type-Length-Value | [RFC8972] |
+--------------+---------------------------+-----------+
Table 1: Abbreviations
Gandhi, et al. Expires 6 May 2027 [Page 4]
Internet-Draft STAMP for Residual Bit Error Rate November 2026
2.4. STAMP Reference Topology
In the STAMP reference topology shown in Figure 1, the STAMP Session-
Sender S1 initiates Session-Sender test packets, and the STAMP
Session-Reflector R1 transmits Session-Reflector test packets.
T1 T2
/ \
+-------+ Session-Sender Test Packet +-------+
| | - - - - - - - - - - - - - - - ->| |
| S1 |==================================| R1 |
| |<- - - - - - - - - - - - - - - - | |
+-------+ Session-Reflector 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
the node S1. T2 is a receive timestamp, and T3 is a transmit
timestamp added by the node R1.
3. Overview
The optional extensions for STAMP-Test packets [RFC8762] are defined
in [RFC8972] in the form of TLVs. The Session-Sender transmits
optional STAMP TLVs, and the Session-Reflector reflects all STAMP
TLVs received in Session-Sender test packets. [RFC8972] defines an
optional TLV extension specifically for transmitting the "Extra
Padding" (Type=1) TLV in STAMP-Test packets. The "Extra Padding" TLV
can be filled with either a predefined fixed pattern or a random
pattern of bits [RFC8972].
This document defines a procedure to measure the residual BER within
the "Extra Padding" TLV. The process involves the Session-Sender
transmitting padding data filled with a predefined bit pattern. The
Session-Reflector then checks for bit errors by comparing the
received padding data against the predefined bit pattern. This
allows the detection of a single bit error or a burst of bit errors
and the measurement of residual BER. The Session-Reflector does not
discard a Session-Sender test packet with bit errors but instead
corrects the bit errors and reflects the packet back to the Session-
Sender. The Session-Reflector also returns the bit error count in
the reflected Session-Reflector test packet.
Gandhi, et al. Expires 6 May 2027 [Page 5]
Internet-Draft STAMP for Residual Bit Error Rate November 2026
Residual BER is measured in both directions between the Session-
Sender and the Session-Reflector using the procedure and extensions
defined in this document. Residual BER is calculated from the number
of bit errors detected in the padding data and the number of bits
received in that data.
The following additional considerations apply to the residual BER
procedure defined in this document:
* The integrity of STAMP-Test packets used for BER measurement can
be protected with the authenticated mode and the HMAC mechanisms
defined in [RFC8762] and [RFC8972]. Because the HMAC does not
cover the "Extra Padding" TLV, residual BER measurement remains
possible when these mechanisms are used.
* The UDP checksum verifies the integrity of received STAMP-Test
packets. Bit errors in the "Extra Padding" TLV, which is used for
residual BER measurement, can cause UDP checksum verification to
fail and the packet to be dropped.
* For IPv4, a UDP checksum value of 0 indicates that no checksum is
provided, allowing residual BER measurement without packet drops
caused by checksum verification failures [RFC768].
* For IPv6, a UDP checksum value of 0 is not permitted by [RFC8200].
STAMP in the authenticated mode can be used to provide data
integrity protection.
* When the UDP checksum is zero, the UDP layer does not detect
corruption of the STAMP-Test payload. When using the
unauthenticated mode defined in [RFC8762] and [RFC8972],
implementations MUST perform the specified STAMP packet and
session validation, including checks of packet format, session
identification, sequence number field, timestamp fields, and TLV
structure and length, and MUST discard packets that fail those
checks. These checks detect some invalid packets but do not
provide general integrity protection: corruption that leaves a
packet valid, including changes to measurement fields or TLV
values, may go undetected and affect the measurement.
* STAMP fields other than the "Extra Padding" TLV are not used to
measure residual BER. Bit errors in those fields can cause packet
validation to fail. Such packets are generally reported using
another measurement metric, such as packet drops or authentication
failures.
Gandhi, et al. Expires 6 May 2027 [Page 6]
Internet-Draft STAMP for Residual Bit Error Rate November 2026
4. Residual BER in Padding TLV Extension
This document defines a "Residual BER in Padding" TLV (Type=TBA1) for
STAMP. Its Value consists of a four-octet bit error count, a four-
octet maximum bit error burst size, and a sequence of sub-TLVs. Each
sub-TLV has the STAMP TLV Flags, Type, Length, and Value fields
defined in [RFC8972]. The format of the "Residual BER in Padding"
TLV is shown in Figure 2.
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Bit error count (4 octets) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Maximum bit error burst size (4 octets) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Sub-TLVs ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: Residual BER in Padding TLV
The fields of the "Residual BER in Padding" TLV are defined as
follows:
* STAMP TLV Flags: The STAMP TLV Flags follow the procedures
specified in [RFC8972].
* Type: MUST be set to TBA1.
* Length: A two-octet field equal to the length of the Value field,
in octets, including the bit error count, the maximum bit error
burst size, and all sub-TLVs. Length MUST be 8 or more octets.
If Length is less than 8 octets, the Session-Reflector MUST return
the "Residual BER in Padding" TLV with the Malformed flag set to 1
in the STAMP TLV Flags field, as specified in [RFC8972].
* Bit error count: A four-octet field containing the number of bit
errors in the padding data within the "Extra Padding" TLV.
* Maximum bit error burst size: A four-octet field containing the
maximum number of consecutive bit errors in the padding data
within the "Extra Padding" TLV.
Gandhi, et al. Expires 6 May 2027 [Page 7]
Internet-Draft STAMP for Residual Bit Error Rate November 2026
* Sub-TLVs: A sequence of zero or more sub-TLVs defined in
Section 4.1.
The "Residual BER in Padding" TLV contains a bit error count and a
maximum bit error burst size, and MAY contain one "Bit Pattern in
Padding" sub-TLV (Type=TBA2).
4.1. Bit Pattern in Padding Sub-TLV
The "Bit Pattern in Padding" sub-TLV is optional and is carried
within the "Residual BER in Padding" TLV. Its format is shown in
Figure 3.
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 | Sub-TLV Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Bit pattern ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3: Bit Pattern in Padding Sub-TLV
The fields of the "Bit Pattern in Padding" sub-TLV are defined as
follows:
* STAMP TLV Flags: The STAMP TLV Flags follow the procedures
specified in [RFC8972].
* Type: MUST be set to TBA2.
* Sub-TLV Length: A two-octet field equal to the length of the Value
field, in octets. The length of the Value field MUST be at least
4 octets. If it is less than 4 octets, the Session-Reflector MUST
return the "Bit Pattern in Padding" sub-TLV with the Malformed
flag set to 1 in the STAMP TLV Flags field, as specified in
[RFC8972].
* Bit pattern: The repeated bit pattern that MUST be used in the
"Extra Padding" TLV.
5. STAMP Procedure for Residual BER Measurement
The "Residual BER in Padding" TLV is carried in STAMP-Test packets
sent by the Session-Sender and the Session-Reflector for residual BER
measurement.
Gandhi, et al. Expires 6 May 2027 [Page 8]
Internet-Draft STAMP for Residual Bit Error Rate November 2026
An example of a STAMP-Test packet using an "Extra Padding" TLV and a
"Residual BER in Padding" TLV for measuring residual BER 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| STAMP-Test Packet RFC 8972 |
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|STAMP TLV Flags| Type=1 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Extra Padding ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+--
|STAMP TLV Flags| Type=TBA1 | Length=16 | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ T
| Bit error count | L
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ V
| Maximum bit error burst size | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+--
|STAMP TLV Flags| Type=TBA2 | Sub-TLV Length=4 | S
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ u
| Bit pattern | b
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+--
Figure 4: Example STAMP-Test Packet to Measure Residual BER
5.1. STAMP Session-Sender
When a STAMP Session-Sender is configured to measure residual BER, it
adds an "Extra Padding" (Type=1) TLV and one "Residual BER in
Padding" (Type=TBA1) TLV to Session-Sender test packets. The
"Residual BER in Padding" TLV contains a bit error count and a
maximum bit error burst size, and MAY contain one "Bit Pattern in
Padding" sub-TLV (Type=TBA2). A Session-Sender test packet MUST NOT
contain more than one "Extra Padding" TLV or more than one "Residual
BER in Padding" TLV.
The Session-Sender MUST add an "Extra Padding" TLV [RFC8972] when it
adds a "Residual BER in Padding" TLV to a Session-Sender test packet.
If the "Bit Pattern in Padding" sub-TLV is present, the length of its
Value field MUST be at least 4 octets, and its data MUST contain the
bit pattern employed in the "Extra Padding" TLV. The length of the
padding data MUST be an integer multiple of the length of the bit
pattern to ease implementation.
Gandhi, et al. Expires 6 May 2027 [Page 9]
Internet-Draft STAMP for Residual Bit Error Rate November 2026
The bit error count MUST be set to 0 by the Session-Sender.
The maximum bit error burst size field MUST be set to 0 by the
Session-Sender.
The integrity of the "Residual BER in Padding" TLV, including its
sub-TLVs, can be protected using the HMAC mechanisms defined in
[RFC8972].
If the Session-Sender receives the "Residual BER in Padding" TLV or
any of its sub-TLVs with the U flag (Unrecognized) set to 1 in the
corresponding STAMP TLV Flags field, it assumes that the Session-
Reflector does not support residual BER measurement. The Session-
Sender therefore disables residual BER measurement but continues with
the other STAMP measurements such as delay and loss.
5.1.1. MTU Considerations
As specified in [RFC8972], the Session-Sender test packets and the
Session-Reflector test packets are symmetric in size. The Session-
Sender and the Session-Reflector MUST adjust the size of the padding
data after adding the STAMP TLVs to ensure that the resulting packets
do not exceed the path MTU. Information about the path MTU of the
nodes may be configured, collected through management protocols, or
distributed by control protocols, such as Path MTU Discovery for IPv6
[RFC8201]. The mechanisms for learning the path MTU of the nodes
along the path are out of scope for this document.
5.1.2. Bit Pattern Considerations
The bit pattern in the "Bit Pattern in Padding" sub-TLV may itself
contain bit errors. This can result in a measurement error due to a
mismatch between the bit pattern and the padding data. One way to
avoid this issue is for the Session-Sender and Session-Reflector to
use the locally configured bit pattern or the default bit pattern of
"0xFF00FF00", which is repeated in the padding data. In this case,
the "Bit Pattern in Padding" sub-TLV is not transmitted in STAMP-Test
packets.
5.2. STAMP Session-Reflector
When the Session-Reflector receives a Session-Sender test packet with
a "Residual BER in Padding" TLV, it MUST check the padding data in
the "Extra Padding" TLV against the expected bit pattern, counting
each mismatching bit as a bit error. If the "Bit Pattern in Padding"
sub-TLV is absent, the Session-Reflector uses the locally configured
bit pattern or the default bit pattern.
Gandhi, et al. Expires 6 May 2027 [Page 10]
Internet-Draft STAMP for Residual Bit Error Rate November 2026
The Session-Reflector MUST set the bit error count to the number of
detected bit errors and reflect the "Residual BER in Padding" TLV
back to the Session-Sender in a Session-Reflector test packet. If no
bit errors are detected, the value remains 0.
The Session-Reflector MUST set the maximum bit error burst size field
to the maximum number of consecutive bits that do not match the
expected bit pattern. If no bit errors are detected, or if the
Session-Reflector cannot compute the maximum bit error burst size, it
MUST return a value of 0 for the maximum bit error burst size field.
The Session-Reflector corrects the padding data in the "Extra
Padding" TLV to match the expected bit pattern and reflects the
corrected "Extra Padding" TLV and the updated "Residual BER in
Padding" TLV to the Session-Sender in a Session-Reflector test
packet. The corrected padding data is used to measure residual BER
in the reverse direction.
If the Session-Reflector does not recognize the "Residual BER in
Padding" TLV, it MUST return that TLV with the U flag (Unrecognized)
set to 1 in its STAMP TLV Flags field. If it recognizes the
"Residual BER in Padding" TLV but does not recognize one of its sub-
TLVs, it MUST return that sub-TLV with the U flag set to 1 in the
STAMP TLV Flags field of the sub-TLV, as specified in [RFC8972].
5.2.1. STAMP TLV Conformant Check
Following the procedure specified in [RFC10052], the Session-
Reflector MUST set the Conformant Reflected Packet STAMP TLV flag to
1 in the STAMP TLV Flags field of the reflected "Residual BER in
Padding" TLV in the following cases:
* If the Session-Reflector receives a Session-Sender test packet
with a "Residual BER in Padding" TLV but without an "Extra
Padding" TLV, with more than one "Extra Padding" TLV, with more
than one "Residual BER in Padding" TLV, or with a "Residual BER in
Padding" TLV whose Length field is less than 8 octets.
* If the "Residual BER in Padding" TLV contains more than one "Bit
Pattern in Padding" sub-TLV.
* If the length of the extra padding data is not an integer multiple
of the length of the bit pattern.
Gandhi, et al. Expires 6 May 2027 [Page 11]
Internet-Draft STAMP for Residual Bit Error Rate November 2026
5.3. Considerations for a Link Aggregation Group
Networks may experience transmission bit errors differently for
different link members of a Link Aggregation Group (LAG). The
procedure and extensions defined in this document are equally
applicable to measuring residual BER in both directions on each
individual member of the LAG.
To measure delay on LAG member links, a separate STAMP micro-session
is created for each member of the LAG. The STAMP extension for the
"Micro-Session ID" TLV, as defined in [RFC9534], is used to identify
each member link of the LAG associated with the STAMP micro-session
at the Session-Sender and the Session-Reflector. The Session-
Reflector replies on the same member of the LAG in the reverse
direction based on the information in the received STAMP-Test packet
and on either the local configuration for the micro-session or the
information from the data plane where the STAMP-Test packet was
received.
Note that in order to obtain a good approximation of the residual BER
measurement, it is RECOMMENDED to transmit STAMP-Test packets with
padding data so that the packet size matches, but does not exceed,
the link MTU.
6. Operational Considerations
The operational considerations specified in [RFC8762] apply to the
procedure and extensions defined in this document. Additional
operational considerations are specified in the following
subsections.
6.1. Configuration Data Model Parameters
The configuration data model for the residual BER measurement using
STAMP MUST allow the setting of the following parameters:
* Padding size (number of octets, which is an integer multiple of
the padding bit pattern size in octets)
* Padding bit pattern (of variable length, at least 4 octets)
* Transmit interval for STAMP-Test packets
* Computation interval as a multiple of the transmit interval for
reporting residual BER measurements
Gandhi, et al. Expires 6 May 2027 [Page 12]
Internet-Draft STAMP for Residual Bit Error Rate November 2026
6.2. Operational Data Model Parameters
The operational data model for the residual BER measurement using
STAMP MUST allow the reporting of the following parameters:
Forward direction (near-end) residual BER measurement:
* Total number of STAMP-Test packets received in the computation
interval.
* Total number of STAMP-Test packets received with a non-zero bit
error count in the "Residual BER in Padding" TLVs in the
computation interval.
* Sum of the number of bits in the padding data of all received
STAMP-Test packets in the computation interval.
* Sum of the bit error counts reported in the "Residual BER in
Padding" TLVs of all received STAMP-Test packets in the
computation interval.
* Maximum and average values of the Maximum Bit Error Burst Size
field in the "Residual BER in Padding" TLVs of all received STAMP-
Test packets in the computation interval.
Reverse direction (far-end) residual BER measurement:
* Total number of STAMP-Test packets received in the computation
interval.
* Total number of STAMP-Test packets received with bit errors in the
computation interval.
* Sum of the number of bits in the padding data of all received
STAMP-Test packets in the computation interval.
* Sum of the number of bit errors in all received STAMP-Test packets
in the computation interval.
* Maximum and average values of the maximum bit error burst size in
all received STAMP-Test packets in the computation interval.
Thresholds may be configured for the following residual BER metrics
for the forward and reverse directions, measured over the computation
interval:
* Number of bit errors per million bits received
Gandhi, et al. Expires 6 May 2027 [Page 13]
Internet-Draft STAMP for Residual Bit Error Rate November 2026
* Number of STAMP-Test packets with bit errors per million packets
received
When a computed metric crosses a user-configured threshold, an alarm
may be generated and event-driven telemetry may be triggered.
When reflecting a STAMP TLV or a Sub-TLV 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.
7. Security Considerations
The security considerations specified in [RFC8762] and [RFC8972]
apply to the procedure and extensions defined in this document.
8. Implementation Status
Editorial note: Please remove this section prior to publication.
8.1. Open Source Implementation
An open-source implementation of the Simple Two-Way Active
Measurement Protocol ([RFC8762]) is available in Teaparty.
* https://github.com/cerfcast/teaparty
An implementation of the solution specified in this document is
available at the following location:
* https://github.com/cerfcast/teaparty/
commit/592558a38dbcf9b273acb2a2fe8ab0d8f16d0709
Additionally, there is support for residual BER in the Wireshark
dissector:
* https://github.com/cerfcast/teaparty/
commit/608b9e89fce2f25ed88eaa367d0bacc693845da2
Contact:
William Hawkins
University of Cincinnati
Email: hawkinsw@obs.cr
Gandhi, et al. Expires 6 May 2027 [Page 14]
Internet-Draft STAMP for Residual Bit Error Rate November 2026
8.2. Cisco Implementation
An implementation of the solution defined in this document is
available in IOS XR Software Release 26.1.1 for the Cisco 8000
Series.
- https://www.cisco.com/c/en/us/td/docs/iosxr/cisco8000/segment-
routing/26xx/configuration/guide/b-segment-routing-cg-cisco8000-26xx/
configuring-performance-measurement.html#link-residual-bit-error-
rate-measurement-using-stamp
9. 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 | Residual BER in Padding | This document |
+-------+-------------------------+---------------+
Table 2: STAMP TLV Type
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:
+=======+========================+==============+===========+
| Value | Description | Used in | Reference |
+=======+========================+==============+===========+
| TBA2 | Bit Pattern in Padding | Residual BER | This |
| | | in Padding | document |
+-------+------------------------+--------------+-----------+
Table 3: STAMP Sub-TLV Types
10. References
10.1. Normative References
[RFC768] Postel, J., "User Datagram Protocol", STD 6, RFC 768,
DOI 10.17487/RFC768, August 1980,
<https://www.rfc-editor.org/info/rfc768>.
Gandhi, et al. Expires 6 May 2027 [Page 15]
Internet-Draft STAMP for Residual Bit Error Rate November 2026
[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>.
[RFC3819] Karn, P., Ed., Bormann, C., Fairhurst, G., Grossman, D.,
Ludwig, R., Mahdavi, J., Montenegro, G., Touch, J., and L.
Wood, "Advice for Internet Subnetwork Designers", BCP 89,
RFC 3819, DOI 10.17487/RFC3819, July 2004,
<https://www.rfc-editor.org/info/rfc3819>.
[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>.
[RFC8200] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", STD 86, RFC 8200,
DOI 10.17487/RFC8200, July 2017,
<https://www.rfc-editor.org/info/rfc8200>.
[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>.
[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>.
10.2. Informative References
[RFC3385] Sheinwald, D., Satran, J., Thaler, P., and V. Cavanna,
"Internet Protocol Small Computer System Interface (iSCSI)
Cyclic Redundancy Check (CRC)/Checksum Considerations",
RFC 3385, DOI 10.17487/RFC3385, September 2002,
<https://www.rfc-editor.org/info/rfc3385>.
Gandhi, et al. Expires 6 May 2027 [Page 16]
Internet-Draft STAMP for Residual Bit Error Rate November 2026
[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>.
[RFC9534] Li, Z., Zhou, T., Guo, J., Mirsky, G., and R. Gandhi,
"Simple Two-Way Active Measurement Protocol Extensions for
Performance Measurement on a Link Aggregation Group",
RFC 9534, DOI 10.17487/RFC9534, January 2024,
<https://www.rfc-editor.org/info/rfc9534>.
Acknowledgments
The authors would like to thank Ianik Semco and Miloslav Kopka for
discussions about bit error rate measurement. The authors would also
like to thank Ruediger Geib, Zhenqiang Li, Carsten Rossenhoevel,
Ernesto Ruffini, and Xiao Min for reviewing this document and
providing many useful comments and suggestions. The authors would
also like to thank William Hawkins for implementing the solution
defined in this document and providing many useful suggestions.
Authors' Addresses
Rakesh Gandhi (editor)
Cisco Systems, Inc.
Canada
Email: rgandhi@cisco.com
Peter Schoenmaker
Meta Platforms, Inc.
United Kingdom
Email: psch@meta.com
Richard Foote
Nokia
Email: footer.foote@nokia.com
Li Zhang
Huawei Technologies
China
Email: zhangli344@huawei.com
Gandhi, et al. Expires 6 May 2027 [Page 17]