University of Surrey

sb@stewartbryant.com

Independent

swallow.ietf@gmail.com

Huawei

mach.chen@huawei.com

Huawei Technologies

giuseppe.fioccola@huawei.com

ZTE Corp.

gregimirsky@gmail.com

MPLS Performance Measurement OAM RFC 6374 describes methods of making loss and delay measurements on Label Switched Paths (LSPs) primarily as they are used in MPLS Transport Profile (MPLS-TP) networks. This document describes a method of extending the performance measurements (specified in RFC 6374) from flows carried over MPLS-TP to flows carried over generic MPLS LSPs. In particular, it extends the technique to allow loss and delay measurements to be made on multipoint-to-point LSPs and introduces some additional techniques to allow more sophisticated measurements to be made in both MPLS-TP and generic MPLS networks.

Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at .

Copyright Notice Copyright (c) 2024 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 () 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

• .  Introduction
• .  Requirements Language
• .  Packet Loss Measurement Using SFL
• .  Single Packet Delay Measurement Using SFL
• .  Data Service Packet Delay Measurement
• .  Some Simplifying Rules
• .  Multiple Packet Delay Characteristics
  • .  Method 1: Time Buckets
  • .  Method 2: Classic Standard Deviation
    • .  Multi-packet Delay Measurement Message Format
  • .  Per-Packet Delay Measurement
  • .  Average Delay
• .  Sampled Measurement
• .  Carrying Packets over an LSP Using an SFL
  • .  Extending RFC 6374 with SFL TLV
• . Combined Loss/Delay Measurement Using SFL
• . Privacy Considerations
• . Security Considerations
• . IANA Considerations
  • .  Allocation of MPLS Generalized Associated Channel (G-ACh) Types
  • .  Allocation of MPLS Loss/Delay TLV Object
• . References
  • .  Normative References
  • .  Informative References
• Acknowledgments
• Contributors
• Authors' Addresses

Introduction was originally designed for use as an Operations, Administration, and Maintenance (OAM) protocol for use with MPLS Transport Profile (MPLS-TP) LSPs. MPLS-TP only supports point-to-point and point-to-multipoint LSPs. This document describes how to use in the generic MPLS case and also introduces a number of more sophisticated measurements of applicability to both cases. describes the requirement for introducing flow identities when using packet loss measurements described in . In summary, describes use of the loss measurement (LM) message as the packet accounting demarcation point. Unfortunately, this gives rise to a number of problems that may lead to significant packet accounting errors in certain situations. For example:

1. Where a flow is subjected to Equal-Cost Multipath (ECMP) treatment, packets can arrive out of order with respect to the LM packet.
2. Where a flow is subjected to ECMP treatment, packets can arrive at different hardware interfaces, thus requiring reception of an LM packet on one interface to trigger a packet accounting action on a different interface that may not be co-located with it. This is a difficult technical problem to address with the required degree of accuracy.
3. Even where there is no ECMP (for example, on RSVP-TE, MPLS-TP LSPs, and pseudowires (PWs)), local processing may be distributed over a number of processor cores, leading to synchronization problems.
4. Link aggregation techniques may also lead to synchronization issues.
5. Some forwarder implementations have a long pipeline between processing a packet and incrementing the associated counter, again leading to synchronization difficulties.

An approach to mitigating these synchronization issues is described in -- the packets are batched by the sender, and each batch is marked in some way such that adjacent batches can be easily recognized by the receiver. An additional problem arises where the LSP is a multipoint-to-point LSP since MPLS does not include a source address in the packet. Network management operations require the measurement of packet loss between a source and destination. It is thus necessary to introduce some source-specific information into the packet to identify packet batches from a specific source. describes a method of encoding per-flow instructions in an MPLS label stack using a technique called Synonymous Flow Labels (SFLs), in which labels that mimic the behavior of other labels provide the packet batch identifiers and enable the per-batch packet accounting. This memo specifies how SFLs are used to perform packet loss and delay measurements as described in . When the terms "performance measurement method," "Query," "packet," or "message" are used in this document, they refer to a performance measurement method, Query, packet, or message as specified in .

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.

Packet Loss Measurement Using SFL The data service packets of the flow being instrumented are grouped into batches, and all the packets within a batch are marked with the SFL corresponding to that batch. The sender counts the number of packets in the batch. When the batch has completed and the sender is confident that all of the packets in that batch will have been received, the sender issues a Query message to determine the number actually received and hence the number of packets lost. The Query message is sent using the same SFL as the corresponding batch of data service packets. The format of the Query and Response packets is described in .

Single Packet Delay Measurement Using SFL describes how to measure the packet delay by measuring the transit time of a packet over an LSP. Such a packet may not need to be carried over an SFL since the delay over a particular LSP should be a function of the Traffic Class (TC) bits. However, where SFLs are being used to monitor packet loss or where label-inferred scheduling is used , then the SFL would be REQUIRED to ensure that the packet that was being used as a proxy for a data service packet experienced a representative delay. The format of a packet carried over the LSP using an SFL is shown in .

Data Service Packet Delay Measurement Where it is desired to more thoroughly instrument a packet flow and to determine the delay of a number of packets, it is undesirable to send a large number of packets acting as proxy data service packets (see ). A method of directly measuring the delay characteristics of a batch of packets is therefore needed. Given the long intervals over which it is necessary to measure packet loss, it is not necessarily the case that the batch times for the two measurement types would be identical. Thus, we use a technique that permits the two measurements to be made concurrently and yet relatively independently from each other. The notion that they are relatively independent arises from the potential for the two batches to overlap in time, in which case either the delay batch time will need to be cut short or the loss time will need to be extended to allow correct reconciliation of the various counters. The problem is illustrated in .

Query Packet with SFL (Case 1) AAAAAAAAAABBBBBBBBBBAAAAAAAAAABBBBBBBBBB SFL marking of a packet batch for loss measurement (Case 2) AADDDDAAAABBBBBBBBBBAAAAAAAAAABBBBBBBBBB SFL marking of a subset of the packets for delay (Case 3) AAAAAAAADDDDBBBBBBBBAAAAAAAAAABBBBBBBBBB SFL marking of a subset of the packets across a packet loss measurement boundary (Case 4) AACDCDCDAABBBBBBBBBBAAAAAAAAAABBBBBBBBBB A case of multiple delay measurements within a packet loss measurement where A and B are packets where loss is being measured. C and D are packets where loss and delay are being measured.

In Case 1, we show where loss measurement alone is being carried out on the flow under analysis. For illustrative purposes, consider that 10 packets are used in each flow in the time interval being analyzed. Now consider Case 2, where a small batch of packets need to be analyzed for delay. These are marked with a different SFL type, indicating that they are to be monitored for both loss and delay. The SFL=A indicates loss batch A, and SFL=D indicates a batch of packets that are to be instrumented for delay, but SFL D is synonymous with SFL A, which in turn is synonymous with the underlying Forwarding Equivalence Class (FEC). Thus, a packet marked "D" will be accumulated into the A loss batch, into the delay statistics, and will be forwarded as normal. Whether the packet is actually counted twice (for loss and delay) or whether the two counters are reconciled during reporting is a local matter. Now consider Case 3, where a small batch of packets is marked for delay across a loss batch boundary. These packets need to be considered as a part of batch A or a part of batch B, and any Query needs to take place after all packets A or D (whichever option is chosen) have arrived at the receiving Label Switching Router (LSR). Now consider Case 4. Here, we have a case where it is required to take a number of delay measurements within a batch of packets that we are measuring for loss. To do this, we need two SFLs for delay (C and D) and alternate between them (on a delay-batch-by-delay-batch basis) for the purposes of measuring the delay characteristics of the different batches of packets.

Some Simplifying Rules It is possible to construct a large set of overlapping measurement types in terms of loss, delay, loss and delay, and batch overlap. If we allow all combinations of cases, this leads to configuration, testing, and implementation complexity and, hence, increased costs. The following simplifying rules represent the default case:

1. Any system that needs to measure delay MUST be able to measure loss.
2. Any system that is to measure delay MUST be configured to measure loss. Whether the loss statistics are collected or not is a local matter.
3. A delay measurement MAY start at any point during a loss measurement batch, subject to rule 4.
4. A delay measurement interval MUST be short enough that it will complete before the enclosing loss batch completes.
5. The duration of a second delay batch (D in ) must be such that all packets from the packets belonging to a first delay batch (C in ) will have been received before the second delay batch completes. This condition is satisfied when the time to send a batch is long compared to the network propagation time and is a parameter that can be established by the network operator.

Given that the sender controls both the start and duration of a loss and a delay packet batch, these rules are readily implemented in the control plane.

Multiple Packet Delay Characteristics A number of methods are described that add to the set of measurements originally specified in . Each of these methods has different characteristics and different processing demands on the packet forwarder. The choice of method will depend on the type of diagnostic that the operator seeks. Three methods are discussed:

1. Time Buckets
2. Classic Standard Deviation
3. Average Delay

Method 1: Time Buckets In this method, the receiving LSR measures the inter-packet gap, classifies the delay into a number of delay buckets, and records the number of packets in each bucket. As an example, if the operator were concerned about packets with a delay of up to 1 μs, 2 μs, 4 μs, 8 μs, and over 8 μs, then there would be five buckets, and packets that arrived up to 1 μs would cause the "up to 1 μs" bucket counter to increase. Likewise, for those that arrived between 1 μs and 2 μs, the "2 μs" bucket counter would increase, etc. In practice, it might be better in terms of processing and potential parallelism if both the "up to 1 μs" and "2 μs" counters were incremented when a packet had a delay relative to its predecessor of 2 μs, and any more detailed information was calculated in the analytics system. This method allows the operator to see more structure in the jitter characteristics than simply measuring the average jitter and avoids the complication of needing to perform a per-packet multiply but will probably need the time intervals between buckets to be programmable by the operator. The packet format of a Time Bucket Jitter Measurement message is shown below:

Time Bucket Jitter Measurement Message Format 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Version| Flags | Control Code | Message Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | QTF | RTF | RPTF | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Session Identifier | DS | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Number of | Reserved 1 | | Buckets | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Interval (in 10 ns units) | | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Number of Pkts in Bucket 1 | | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ~ ~ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Number of Pkts in Bucket N | | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ~ ~ ~ TLV Block ~ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

The Version, Flags, Control Code, Message Length, Querier Timestamp Format (QTF), Responder Timestamp Format (RTF), Responder's Preferred Timestamp Format (RPTF), Session Identifier, Reserved, and Differentiated Services (DS) fields are as defined in . The remaining fields, which are unsigned integers, are as follows:

• Number of Buckets in the measurement.
• Reserved 1 must be sent as zero and ignored on receipt.
• Interval (in 10 ns units) is the inter-packet interval for this bucket.
• Number of Pkts in Bucket 1 is the number of packets found in the first bucket.
• Number of Pkts in Bucket N is the number of packets found in the Nth bucket, where N is the value in the Number of Buckets field.

There will be a number of Interval/Number pairs depending on the number of buckets being specified by the Querier. If a message is being used to configure the buckets (i.e., the responder is creating or modifying the buckets according to the intervals in the Query message), then the responder MUST respond with 0 packets in each bucket until it has been configured for a full measurement period. This indicates that it was configured at the time of the last response message, and thus, the response is valid for the whole interval. As per the convention in , the Number of Pkts in Bucket fields are included in the Query message and set to zero. Out-of-band configuration is permitted by this mode of operation. Note this is a departure from the normal fixed format used in . The Time Bucket Jitter Measurement message is carried over an LSP in the way described in and over an LSP with an SFL as described in .

Method 2: Classic Standard Deviation In this method, provision is made for reporting the following delay characteristics:

1. Number of packets in the batch (n)
2. Sum of delays in a batch (S)
3. Maximum delay
4. Minimum delay
5. Sum of squares of inter-packet delay (SumS)

Characteristics 1 and 2 give the mean delay. Measuring the delay of each pair in the batch is discussed in . Characteristics 3 and 4 give the outliers. Characteristics 1, 2, and 5 can be used to calculate the variance of the inter-packet gap, hence the standard deviation giving a view of the distribution of packet delays and hence the jitter. The equation for the variance (var) is given by: var = (SumS - S*S/n)/(n-1) There is some concern over the use of this algorithm for measuring variance because SumS and S*S/n can be similar numbers, particularly where variance is low. However, the method is acceptable because it does not require a division in the hardware.

Multi-packet Delay Measurement Message Format The packet format of a Multi-packet Delay Measurement message is shown below:

Multi-packet Delay Measurement Message Format 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Version| Flags | Control Code | Message Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | QTF | RTF | RPTF | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Session Identifier | DS | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Number of Packets | | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Sum of Delays for Batch | | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Minimum Delay | | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Maximum Delay | | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Sum of squares of Inter-packet delay | | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ~ ~ ~ TLV Block ~ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

The Version, Flags, Control Code, Message Length, QTF, RTF, RPTF, Session Identifier, Reserved, and DS fields are as defined in . The remaining fields are as follows:

• Number of Packets is the number of packets in this batch.
• Sum of Delays for Batch is the duration of the batch in the time measurement format specified in the RTF field.
• Minimum Delay is the minimum inter-packet gap observed during the batch in the time format specified in the RTF field.
• Maximum Delay is the maximum inter-packet gap observed during the batch in the time format specified in the RTF field.

The Multi-packet Delay Measurement message is carried over an LSP in the way described in and over an LSP with an SFL as described in .

Per-Packet Delay Measurement If detailed packet delay measurement is required, then it might be possible to record the inter-packet gap for each packet pair. In cases other than the exceptions of slow flows or small batch sizes, this would create a large (per-packet) demand on storage in the instrumentation system, a large bandwidth for such a storage system and large bandwidth for the analytics system. Such a measurement technique is outside the scope of this document.

Average Delay Introduced in is the concept of a one-way delay measurement in which the average time of arrival of a set of packets is measured. In this approach, the packet is timestamped at arrival, and the responder returns the sum of the timestamps and the number of timestamps. From this, the analytics engine can determine the mean delay. An alternative model is that the responder returns the timestamp of the first and last packet and the number of packets. This latter method has the advantage of allowing the average delay to be determined at a number of points along the packet path and allowing the components of the delay to be characterized. Unless specifically configured otherwise, the responder may return either or both types of response, and the analytics engine should process the response appropriately. The packet format of an Average Delay Measurement message is shown below:

Average Delay Measurement Message Format 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Version| Flags | Control Code | Message Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | QTF | RTF | RPTF | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Session Identifier | DS | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Number of Packets | | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Time of First Packet | | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Time of Last Packet | | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Sum of Timestamps of Batch | | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ~ ~ ~ TLV Block ~ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

The Version, Flags, Control Code, Message Length, QTF, RTF, RPTF, Session Identifier, and DS fields are as defined in . The remaining fields are as follows:

• Number of Packets is the number of packets in this batch.
• Time of First Packet is the time of arrival of the first packet in the batch.
• Time of Last Packet is the time of arrival of the last packet in the batch.
• Sum of Timestamps of Batch.

The Average Delay Measurement message is carried over an LSP in the way described in and over an LSP with an SFL as described in . As is the convention with , the Query message contains placeholders for the Response message. The placeholders are sent as zero.

Sampled Measurement In the discussion so far, it has been assumed that we would measure the delay characteristics of every packet in a delay measurement interval defined by an SFL of constant color. In , the concept of a sampled measurement is considered. That is, the responder only measures a packet at the start of a group of packets being marked for delay measurement by a particular color, rather than every packet in the marked batch. A measurement interval is not defined by the duration of a marked batch of packets but the interval between a pair of packets taking a readout of the delay characteristic. This approach has the advantage that the measurement is not impacted by ECMP effects. This sampled approach may be used if supported by the responder and configured by the operator.

Carrying Packets over an LSP Using an SFL We illustrate the packet format of a Query message using SFLs for the case of an MPLS Direct Loss Measurement in .

Query Packet with SFL +-------------------------------+ | | | LSP | | Label | +-------------------------------+ | | | Synonymous Flow | | Label | +-------------------------------+ | | | GAL | | | +-------------------------------+ | | | ACH Type = 0xA | | | +-------------------------------+ | | | Measurement Message | | | | +-------------------------+ | | | | | | | Fixed-format | | | | portion of msg | | | | | | | +-------------------------+ | | | | | | | Optional SFL TLV | | | | | | | +-------------------------+ | | | | | | | Optional Return | | | | Information | | | | | | | +-------------------------+ | | | +-------------------------------+

The MPLS label stack is exactly the same as that used for the user data service packets being instrumented except for the inclusion of the Generic Associated Channel Label (GAL) to allow the receiver to distinguish between normal data packets and OAM packets. Since the packet loss measurements are being made on the data service packets, an MPLS Direct Loss Measurement is being made, which is indicated by the type field in the Associated Channel Header (ACH) (Type = 0x000A). The measurement message consists of up to three components as follows.

• The fixed-format portion of the message is carried over the ACH channel. The ACH channel type specifies the type of measurement being made (currently: loss, delay, or loss and delay).
• (Optional) The SFL TLV specified in MAY be carried if needed. It is used to provide the implementation with a reminder of the SFL that was used to carry the message. This is needed because a number of MPLS implementations do not provide the MPLS label stack to the MPLS OAM handler. This TLV is required if messages are sent over UDP . This TLV MUST be included unless, by some method outside the scope of this document, it is known that this information is not needed by the responder.
• (Optional) The Return Information MAY be carried if needed. It allows the responder send the response to the Querier. This is not needed if the response is requested in band and the MPLS construct being measured is a point-to-point LSP, but it otherwise MUST be carried. The Return Address TLV is defined in , and the optional UDP Return Object is defined in .

Where a measurement other than an MPLS Direct Loss Measurement is to be made, the appropriate measurement message is used (for example, one of the new types defined in this document), and this is indicated to the receiver by the use of the corresponding ACH type.

Extending RFC 6374 with SFL TLV The SFL TLV is shown in . This contains the SFL that was carried in the label stack, the FEC that was used to allocate the SFL, and the index (into the batch of SFLs that were allocated for the FEC) that corresponds to this SFL.

SFL TLV 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length |MBZ| SFL Batch | SFL Index | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | SFL | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | FEC | . . +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Where:

Type

Set to Synonymous Flow Label (SFL-TLV).

Length

The length of the TLV is as specified in .

MBZ

MUST be sent as zero and ignored on receive.

SFL Batch

An identifier for a collection of SFLs grouped together for management and control purposes.

SFL Index

The index of this SFL within the list of SFLs that were assigned for the FEC. Multiple SFLs can be assigned to a FEC, each with different actions. This index is an optional convenience for use in mapping between the TLV and the associated data structures in the LSRs. The use of this feature is agreed upon between the two parties during configuration. It is not required but is a convenience for the receiver if both parties support the facility.

SFL

The SFL used to deliver this packet. This is an MPLS label that is a component of a label stack entry as defined in .

Reserved

MUST be sent as zero and ignored on receive.

FEC

The Forwarding Equivalence Class that was used to request this SFL. This is encoded as per .

This information is needed to allow for operation with hardware that discards the MPLS label stack before passing the remainder of the stack to the OAM handler. By providing both the SFL and the FEC plus index into the array of allocated SFLs, a number of implementation types are supported.

Combined Loss/Delay Measurement Using SFL This mode of operation is not currently supported by this specification.

Privacy Considerations The inclusion of originating and/or flow information in a packet provides more identity information and hence potentially degrades the privacy of the communication. While the inclusion of the additional granularity does allow greater insight into the flow characteristics, it does not specifically identify which node originated the packet other than by inspection of the network at the point of ingress or inspection of the control protocol packets. This privacy threat may be mitigated by encrypting the control protocol packets, regularly changing the synonymous labels, and by concurrently using a number of such labels.

Security Considerations The security considerations documented in and (which in turn calls up and ) are applicable to this protocol. The issue noted in is a security consideration. There are no other new security issues associated with the MPLS data plane. Any control protocol used to request SFLs will need to ensure the legitimacy of the request. An attacker that manages to corrupt the SFL TLV in could disrupt the measurements in a way that the responder is unable to detect. However, the network operator is likely to notice the anomalous network performance measurements, and in any case, normal MPLS network security procedures make this type of attack extremely unlikely.

IANA Considerations

Allocation of MPLS Generalized Associated Channel (G-ACh) Types As per the IANA considerations in updated by and , IANA has allocated the following values in the "MPLS Generalized Associated Channel (G-ACh) Types" registry, in the "Generic Associated Channel (G-ACh) Parameters" registry group:

Value	Description	Reference
0x0010	Time Bucket Jitter Measurement	RFC 9571
0x0011	Multi-packet Delay Measurement	RFC 9571
0x0012	Average Delay Measurement	RFC 9571

Allocation of MPLS Loss/Delay TLV Object IANA has allocated the following TLV from the 0-127 range of the "MPLS Loss/Delay Measurement TLV Object" registry in the "Generic Associated Channel (G-ACh) Parameters" registry group:

Type	Description	Reference
4	Synonymous Flow Label	RFC 9571

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. This document specifies the encoding to be used by an LSR in order to transmit labeled packets on Point-to-Point Protocol (PPP) data links, on LAN data links, and possibly on other data links as well. This document also specifies rules and procedures for processing the various fields of the label stack encoding. [STANDARDS-TRACK] The architecture for Multiprotocol Label Switching (MPLS) is described in RFC 3031. A fundamental concept in MPLS is that two Label Switching Routers (LSRs) must agree on the meaning of the labels used to forward traffic between and through them. This common understanding is achieved by using a set of procedures, called a label distribution protocol, by which one LSR informs another of label bindings it has made. This document defines a set of such procedures called LDP (for Label Distribution Protocol) by which LSRs distribute labels to support MPLS forwarding along normally routed paths. [STANDARDS-TRACK] This document generalizes the applicability of the pseudowire (PW) Associated Channel Header (ACH), enabling the realization of a control channel associated to MPLS Label Switched Paths (LSPs) and MPLS Sections in addition to MPLS pseudowires. In order to identify the presence of this Associated Channel Header in the label stack, this document also assigns one of the reserved MPLS label values to the Generic Associated Channel Label (GAL), to be used as a label based exception mechanism. Many service provider service level agreements (SLAs) depend on the ability to measure and monitor performance metrics for packet loss and one-way and two-way delay, as well as related metrics such as delay variation and channel throughput. This measurement capability also provides operators with greater visibility into the performance characteristics of their networks, thereby facilitating planning, troubleshooting, and network performance evaluation. This document specifies protocol mechanisms to enable the efficient and accurate measurement of these performance metrics in MPLS networks. [STANDARDS-TRACK] The MPLS Generic Associated Channel (G-ACh) is a generalization of the applicability of the pseudowire (PW) Associated Channel Header (ACH). RFC 5586 defines the concept of TLV constructs that can be carried in messages on the G-ACh by placing them in the ACH between the fixed header fields and the G-ACh message. These TLVs are called ACH TLVs No Associated Channel Type yet defined uses an ACH TLV. Furthermore, it is believed that handling TLVs in hardware introduces significant problems to the fast path, and since G-ACh messages are intended to be processed substantially in hardware, the use of ACH TLVs is undesirable. This document updates RFC 5586 by retiring ACH TLVs and removing the associated registry. RFC 5586 generalized the applicability of the pseudowire Associated Channel Header (PW-ACH) into the Generic Associated Channel G-ACh. However, registries and allocations of G-ACh parameters had been distributed throughout different, sometimes unrelated, registries. This document coalesces these into a new "Generic Associated Channel (G-ACh) Parameters" registry under the "Multiprotocol Label Switching Architecture (MPLS)" heading. This document updates RFC 5586. This document also updates RFCs 6374, 6378, 6427, and 6428. RFC 6374 defines a protocol for Packet Loss and Delay Measurement for MPLS networks (MPLS-PLDM). This document specifies the procedures to be used when sending and processing out-of-band MPLS performance management Responses over an UDP/IP return path. 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. RFC 8372 ("MPLS Flow Identification Considerations") describes the requirement for introducing flow identities within the MPLS architecture. This document describes a method of accomplishing this by using a technique called "Synonymous Flow Labels" in which labels that mimic the behavior of other labels provide the identification service. These identifiers can be used to trigger per-flow operations on the packet at the receiving label switching router. Informative References This document defines a flexible solution for support of Differentiated Services (Diff-Serv) over Multi-Protocol Label Switching (MPLS) networks. [STANDARDS-TRACK] This document provides a security framework for Multiprotocol Label Switching (MPLS) and Generalized Multiprotocol Label Switching (GMPLS) Networks. This document addresses the security aspects that are relevant in the context of MPLS and GMPLS. It describes the security threats, the related defensive techniques, and the mechanisms for detection and reporting. This document emphasizes RSVP-TE and LDP security considerations, as well as inter-AS and inter-provider security considerations for building and maintaining MPLS and GMPLS networks across different domains or different Service Providers. This document is not an Internet Standards Track specification; it is published for informational purposes. This document specifies an architectural framework for the application of Multiprotocol Label Switching (MPLS) to the construction of packet-switched transport networks. It describes a common set of protocol functions -- the MPLS Transport Profile (MPLS-TP) -- that supports the operational models and capabilities typical of such networks, including signaled or explicitly provisioned bidirectional connection-oriented paths, protection and restoration mechanisms, comprehensive Operations, Administration, and Maintenance (OAM) functions, and network operation in the absence of a dynamic control plane or IP forwarding support. Some of these functions are defined in existing MPLS specifications, while others require extensions to existing specifications to meet the requirements of the MPLS-TP. This document defines the subset of the MPLS-TP applicable in general and to point-to-point transport paths. The remaining subset, applicable specifically to point-to-multipoint transport paths, is outside the scope of this document. This document is a product of a joint Internet Engineering Task Force (IETF) / International Telecommunication Union Telecommunication Standardization Sector (ITU-T) effort to include an MPLS Transport Profile within the IETF MPLS and Pseudowire Emulation Edge-to-Edge (PWE3) architectures to support the capabilities and functionalities of a packet transport network as defined by the ITU-T. This document is not an Internet Standards Track specification; it is published for informational purposes. Many MPLS implementations have supported multipath techniques, and many MPLS deployments have used multipath techniques, particularly in very high-bandwidth applications, such as provider IP/MPLS core networks. MPLS Transport Profile (MPLS-TP) has strongly discouraged the use of multipath techniques. Some degradation of MPLS-TP Operations, Administration, and Maintenance (OAM) performance cannot be avoided when operating over many types of multipath implementations. Using MPLS Entropy Labels (RFC 6790), MPLS Label Switched Paths (LSPs) can be carried over multipath links while also providing a fully MPLS-TP-compliant server layer for MPLS-TP LSPs. This document describes the means of supporting MPLS as a server layer for MPLS-TP. The use of MPLS-TP LSPs as a server layer for MPLS LSPs is also discussed. Pervasive monitoring is a technical attack that should be mitigated in the design of IETF protocols, where possible. This document discusses aspects to consider when developing a solution for MPLS flow identification. The key application that needs this solution is in-band performance monitoring of MPLS flows when MPLS is used to encapsulate user data packets. This document describes the Alternate-Marking technique to perform packet loss, delay, and jitter measurements on live traffic. This technology can be applied in various situations and for different protocols. According to the classification defined in RFC 7799, it could be considered Passive or Hybrid depending on the application. This document obsoletes RFC 8321.

Acknowledgments The authors thank and for their thorough and thoughtful review of this document.

Contributors Huawei

lizhenbin@huawei.com

Ciena Corporation

ssivabal@ciena.com

Authors' Addresses University of Surrey

sb@stewartbryant.com

Independent

swallow.ietf@gmail.com

Huawei

mach.chen@huawei.com

Huawei Technologies

giuseppe.fioccola@huawei.com

ZTE Corp.

gregimirsky@gmail.com