]> Huawei

China zhangli344@huawei.com

Huawei

China zhoutianran@huawei.com

OPS Area IPPM Working Group IOAM Bit Error Rate measurement Networks may experience transmission bit errors due to various factors, such as poor fiber quality, thereby corrupting packets. Merely measuring the end-to-end bit error rate makes it difficult to locate the exact link wich poor quality. Therefore, a measurement method is needed to collect bit error rate information along the entire path to locate the specific linke with poor quality. This document extends IOAM with a new Trace-Type and "Interface Bit Error Rate" field to collect the interface error rate along the path. This new Trace-Type is applicable to Pre-allocated Trace, Incremental Trace, and Direct Exporting Option-Type.

Introduction In situ Operations, Administration, and Maintenance (IOAM) collects OAM information within the packet while the packet traverses a particular network domain. IOAM is used to complement mechanisms, such as Ping or Traceroute. Networks may experience transmission bit errors due to various factors, such as poor fiber quality, thereby corrupting packets. Although,the bit errors in the received packets can be detected using Cyclic Redundancy Check (CRC) and may be dropped or corrected using Forward Error Correction(FEC). But even with efficient CRC and FEC mechanisms, some bit errors may escape detection and correction (called residual bit error rate), and result in upper-layer checksum failures and packet drops. arguments the STAMP extensions in to enable the measurement of end-to-end residual bit error rate within the "Extra Padding" TLV of STAMP packets. However, merely measuring the end-to-end bit error rate makes it difficult to locate the exact link with poor quality. Therefore, a measurement method is needed to collect bit error rate information along the entire path to locate the specific linke with poor quality. This document extends IOAM with a new Trace-Type and "Interface Bit Error Rate" field to collect the interface error rate along the path. This new Trace-Type is applicable to Pre-allocated Trace, Incremental Trace, and Direct Exporting Option-Type.

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

Terminology The abbreviations used in this document are: IOAM: In situ Operations, Administration, and Maintenance

IOAM extension

Extension to Pre-allocated and Incremental Trace-Option

Extension to Pre-allocated and Incremental Trace-Option Header The format of IOAM Pre-allocated and Incremental Trace-Option header defined in is shown as follows:

IOAM Pre-allocated and Incremental Trace-Option Header

The IOAM Trace-Type filed is a 24-bit identifier that specifies which data types are used in this node data list. Currently, bit 0 to bit 11 are already occupied, and bit 12 to 21 are not allocated. This document requires to allocate a new bit X in the IOAM Trace-Type field: Bit X: When set, indicates the presence of bit error rate of the ingress interface in the node data.

Extension to IOAM Node Data Fields This document defines a new IOAM node data field, which is called "Interface Bit Error Rate". The format of this field is shown as follows:

Interface bit error rate field

where: A bit: This field represents the Anomalous (A) bit. The A bit is set when the measured value of this parameter exceeds its configured maximum threshold. The A bit is cleared when the measured value falls below its configured reuse threshold. If the A bit is cleared, the sub-TLV represents steady-state link performance. RESERVED: This field is reserved for future use. It MUST be set to 0 when sent and MUST be ignored when received. Link Bit Error Ratio: This 24-bit field carries Link Bit Error Ratio as a percentage of the total traffic sent over a configurable interval. The basic unit is 0.000003%, where (2^24 - 2) is 50.331642%. This value is the highest link bit error percentage that can be expressed. Therefore, measured values that are larger than the field maximum SHOULD be encoded as the maximum value.

Extension for Direct Exporting Option As described in , the format of this IOAM-Trace-Type of Direct Exporting Option is the same as defined in . Therefore, the new bit defined in is also valid in Direct Exporting Option.

IANA Considerations This document requests IANA to allocate a bit from the "IOAM Trace-Type" registry:

Value	Description	Reference
Bit X	Bit error rate of ingress interface	This document

Security Considerations TBD

References Normative References In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. Informative References In situ Operations, Administration, and Maintenance (IOAM) collects operational and telemetry information in the packet while the packet traverses a path between two points in the network. This document discusses the data fields and associated data types for IOAM. IOAM-Data-Fields can be encapsulated into a variety of protocols, such as Network Service Header (NSH), Segment Routing, Generic Network Virtualization Encapsulation (Geneve), or IPv6. IOAM can be used to complement OAM mechanisms based on, e.g., ICMP or other types of probe packets. Cisco Systems, Inc. Meta Platforms, Inc. Nokia The Simple Two-Way Active Measurement Protocol (STAMP), as defined in RFC 8762, along with its optional extensions specified in RFC 8972, can be utilized for active measurement. Networks may experience transmission bit errors due to various factors, including poor fiber quality. Even with efficient CRC and FEC mechanisms, some bit errors may escape detection and correction, referred to as residual bit errors. This document further augments the STAMP extensions specified in RFC 8972 to enable the measurement of residual bit error rate within the "Extra Padding" TLV of STAMP packets. This document describes optional extensions to Simple Two-way Active Measurement Protocol (STAMP) that enable measurement of performance metrics. The document also defines a STAMP Test Session Identifier and thus updates RFC 8762. In situ Operations, Administration, and Maintenance (IOAM) is used for recording and collecting operational and telemetry information. Specifically, IOAM allows telemetry data to be pushed into data packets while they traverse the network. This document introduces a new IOAM option type (denoted IOAM-Option-Type) called the "IOAM Direct Export (DEX) Option-Type". This Option-Type is used as a trigger for IOAM data to be directly exported or locally aggregated without being pushed into in-flight data packets. The exporting method and format are outside the scope of this document.

Acknowledgements TBD