Encapsulation For MPLS Performance Measurement with Alternate Marking Method

describes a performance measurement method, which can be used to measure packet loss, delay, and jitter on live traffic. Since this method is based on marking consecutive batches of packets, it's referred to as Alternate-Marking Method. describes the desired capabilities for MPLS flow identification, intended for in-band performance monitoring of MPLS flows. This document defines the encapsulation for MPLS performance measurement with alternate marking method, which performs flow-based packet loss, delay, and jitter measurements on MPLS live traffic. The encapsulation defined in this document supports performance monitoring at the intermediate nodes, as well as MPLS flow identification at both transport and service layers. This document employs an encapsulation method, other than Synonymous Flow Label (SFL), to achieve MPLS flow identification. The method described in this document is complementary to the SFL method , the former mainly aims at hop-by-hop processing and the latter mainly aims at edge-to-edge processing. Different sets of MPLS flows may use different methods. The method described in this document is also complementary to the In-situ OAM method , the former doesn't introduce any new header whereas the latter introduces a new In-situ OAM header. Furthermore, the former requires the network nodes to collect the data used for performance measurement, while the latter requires the network nodes to collect the data used for operational and telemetry information collection. An MPLS flow may apply both of the two methods concurrently.

ACL: Access Control List BoS: Bottom of Stack cSPL: Composite Special Purpose Label ECMP: Equal-Cost Multipath ELC: Entropy Label Capability ERLD: Entropy Readable Label Depth eSPL: Extended Special Purpose Label FL: Flow-ID Label FLC: Flow-ID Label Capability FLI: Flow-ID Label Indicator FRLD: Flow-ID Readable Label Depth LSP: Label Switched Path MPLS: Multi-Protocol Label Switching NMS: Network Management System PHP: Penultimate Hop Popping PM: Performance Measurement PW: PseudoWire SFL: Synonymous Flow Label SID: Segment ID SR: Segment Routing TC: Traffic Class TTL: Time to Live VC: Virtual Channel VPN: Virtual Private Network XL: Extension Label

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.

Flow-based MPLS performance measurement encapsulation with alternate marking method has the following format:

The Flow-ID Label Indicator (FLI) is an Extended Special Purpose Label (eSPL), which is combined with the Extension Label (XL, value 15) to form a Composite Special Purpose Label (cSPL), as defined in . The FLI is defined in this document as value TBA1. The Traffic Class (TC) and Time To Live (TTL) for the XL and FLI SHOULD follow the same field values of that label immediately preceding the XL. Otherwise, the TC and TTL for the XL and FLI MAY be different values if it is known that the XL will not be exposed as the top label at any point along the LSP. The Bottom of Stack (BoS) bit for the XL and FLI MUST be zero. The Flow-ID Label (FL) is used as an MPLS flow identification , its value MUST be unique within the administrative domain. Flow-ID values can be allocated by an external NMS/controller, based on measurement object instance such as LSP or PW. There is a one-to-one mapping between Flow-ID and flow. The specific method on how to allocate the Flow-ID values is described in Section 4. The FL can be placed at either the bottom or the middle of the MPLS label stack, and the FL MAY appear multiple times in a label stack. Section 2.1 of this document provides several examples to illustrate how to apply FL in a label stack. The TTL for the FL MUST be zero to ensure that it is not used inadvertently for forwarding. The BoS bit for the FL depends on whether the FL is placed at the bottom of the MPLS label stack. Besides the flow identification, a color-marking field is also necessary for alternate marking method. To achieve the purpose of coloring the MPLS traffic, as well as the distinction between hop-by-hop measurement and edge-to-edge measurement, the TC for the FL is defined as follows: L(oss) bit is used for coloring the MPLS packets for loss measurement. D(elay) bit is used for coloring the MPLS packets for delay/jitter measurement. T(ype) bit is used to indicate the measurement type. When T bit is set to 1, that means edge-to-edge performance measurement. When T bit is set to 0, that means hop-by-hop performance measurement.

Three examples on different layout of Flow-ID label (4 octets) are illustrated as follows. Note that more examples may exist. (1) Layout of Flow-ID label when applied to MPLS transport.

Note that here if the penultimate hop popping (PHP) is in use, the PHP LSR that recognizes the cSPL MAY choose not to pop the cSPL and the following Flow-ID label, otherwise the egress LSR would be excluded from the performance measurement. Also note that in other examples of applying Flow-ID to MPLS transport, one LSP label can be substituted by multiple SID labels in the case of using SR Policy, and the combination of cSPL and Flow-ID label can be placed between SID labels, as specified in Section 5. (2) Layout of Flow-ID label when applied to MPLS service.

Note that here the application label can be MPLS PW label, MPLS Ethernet VPN label or MPLS IP VPN label, and it's also called VC label as defined in . (3) Layout of Flow-ID label when applied to both MPLS transport and MPLS service.

Note that for this example the two Flow-ID values appearing in a label stack MUST be different, that is to say, the Flow-ID label applied to MPLS transport and the Flow-ID label applied to MPLS service share the same value space. Also note that the two Flow-ID label values are independent from each other, e.g., two packets can belong to the same VPN flow but two different LSP flows, or two packets can belong to two different VPN flows but the same LSP flow.

The procedures for Flow-ID label encapsulation, look-up and decapsulation are summarized as follows: The MPLS ingress node inserts the XL, FLI and FL into the MPLS label stack. At the same time, the ingress node sets the Flow-ID value, the two color-marking bits and the T bit, as defined in Section 2. If the edge-to-edge measurement is applied, i.e., the T bit is set to 1, then only the MPLS egress node is the processing node. The processing node looks up the FL with the help of the XL and FLI, and exports the collected data, such as the Flow-ID, block counters and timestamps, to an external NMS/controller, referring to the alternate marking method. Section 6 of describes protocols for collected data export, and the details on how to export the collected data are outside the scope of this document. Note that while looking up the Flow-ID label, the transit node needs to perform some deep packet inspection beyond the label (at the top of the label stack) used to take forwarding decisions. The processing node may also pop the XL, FLI and FL from the MPLS label stack. The egress node pops the whole MPLS label stack, and this document doesn't introduce any new process to the decapsulated packet.

There are at least two ways of allocating Flow-ID, one way is to allocate Flow-ID by manual trigger from the network operator, and the other way is to allocate Flow-ID by automatic trigger from the ingress node. Details are as follows: In the case of manual trigger, the network operator would manually input the characteristics (e.g. IP five tuples and IP DSCP) of the measured flow, then the NMS/controller would generate one or two Flow-IDs based on the input from the network operator, and provision the ingress node with the characteristics of the measured flow and the corresponding allocated Flow-ID(s). In the case of automatic trigger, the ingress node would identify the flow entering the measured path, export the characteristics of the identified flow to the NMS/controller by IPFIX , then the NMS/controller would generate one or two Flow-IDs based on the characteristics exported from the ingress node, and provision the ingress node with the characteristics of the identified flow and the corresponding allocated Flow-ID(s). The policy pre-configured at the NMS/controller decides whether one Flow-ID or two Flow-IDs would be generated. If the performance measurement on MPLS service is enabled, then one Flow-ID applied to MPLS service would be generated; If the performance measurement on MPLS transport is enabled, then one Flow-ID applied to MPLS transport would be generated; If both of them are enabled, then two Flow-IDs respectively applied to MPLS service and MPLS transport would be generated, in this case, the transit node needs to look up both of the two Flow-IDs by default, and that can be changed by configuration to, e.g., look up only the Flow-ID applied to MPLS transport. Whether using the above-mentioned two ways or other ways to allocate Flow-ID, the NMS/controller MUST guarantee every generated Flow-ID is unique within the administrative domain and MUST NOT have a value in the reserved label space (0-15) .

Analogous to the Entropy Label Capability (ELC) defined in Section 5 of and the Entropy Readable Label Depth (ERLD) defined in Section 4 of , the Flow-ID Label Capability (FLC) and the Flow-ID Readable Label Depth (FRLD) are defined in this document. Both FLC and FRLD have the similar semantics with the ELC and ERLD to a router, except that the Flow-ID is used in its flow identification function while the Entropy is used in its load-balancing function. The ingress node MUST insert each FL at an appropriate depth, which ensures the node to which the FL is exposed has the FLC. The ingress node SHOULD insert each FL within an appropriate FRLD, which is the minimum FRLD of all the on-path nodes that need to read and use the FL in question. How the ingress node knows the FLC and FRLD of all the on-path nodes is outside the scope of this document, whereas provides a method to achieve that. When the SR paths are used for transport, the label stack grows as the number of on-path segments increases, if the number of on-path segments is high, that may become a challenge for the FL to be placed within an appropriate FRLD. In order to overcome this potential challenge, an implementation MAY provide flexibility to the ingress node to place FL between SID labels, i.e., multiple identical FLs at different depths MAY be interleaved with SID labels, when that happens a sophisticated network planning may be needed and it's beyond the scope of this document.

Analogous to what's described in Section 5 of , under conditions of Equal-Cost Multipath (ECMP), the introduction of the FL may lead to the same problem as caused by the SFL, and the two solutions proposed for SFL would also apply here. Specifically, adding FL to an existing flow may cause that flow to take a different path, if that's a problem the operator expects to resolve, then the operator can choose to apply entropy labels or add FL to all flows.

This document introduces the performance measurement domain that is the scope of a Flow-ID label. The performance measurement domain normally has the same boundaries as the administrative domain, and the method on how to achieve multi-domain performance measurement with the same Flow-ID label is outside the scope of this document. The Flow-ID Label Indicator and Flow-ID label MUST NOT be signaled and distributed outside one performance measurement domain. Improper configuration so the Flow-ID label is passed from one measurement domain to another would result in Flow-ID conflicts. To prevent packets carrying Flow-ID label from leaking from one domain to another, the domain boundary nodes SHOULD deploy some policies (e.g., ACL) to filter out the packets. Specifically, in the sending edge, the domain boundary node SHOULD filter out the packets that carry the Flow-ID Label Indicator and are sent to other domain; in the receiving edge, the domain boundary node SHOULD drop the packets that carry the Flow-ID Label Indicator and are from other domains.

[Note to the RFC Editor - remove this section before publication, as well as remove the reference to . This section records the status of known implementations of the protocol defined by this specification at the time of posting of this Internet-Draft, and is based on a proposal described in . The description of implementations in this section is intended to assist the IETF in its decision processes in progressing drafts to RFCs. Please note that the listing of any individual implementation here does not imply endorsement by the IETF. Furthermore, no effort has been spent to verify the information presented here that was supplied by IETF contributors. This is not intended as, and must not be construed to be, a catalog of available implementations or their features. Readers are advised to note that other implementations may exist. According to , "this will allow reviewers and working groups to assign due consideration to documents that have the benefit of running code, which may serve as evidence of valuable experimentation and feedback that have made the implemented protocols more mature. It is up to the individual working groups to use this information as they see fit".

Organization: Fiberhome Corporation.
Implementation: Fiberhome R82*, R800*, S680*, S780* series routers are running the common-building block 'Flow-based PM Encapsulation in MPLS'.
Maturity Level: Product
Coverage: Partial,section 2 and example (2) of section 2.1.
Version: Draft-08
Licensing: N/A
Implementation experience: Nothing specific.
Contact: djy@fiberhome.com
Last updated: December 25, 2023

Organization: Huawei Technologies.
Implementation: Huawei ATN8XX, ATN910C, ATN980B, CX600-M2, NE40E, ME60-X1X2, ME60-X3X8X16 Routers running VRPV800R021C00 or above. Huawei NCE-IP Controller running V1R21C00 or above.
Maturity Level: Product
Coverage: Partial,section 2 and example (2) of section 2.1.
Version: Draft-08
Licensing: N/A
Implementation experience: Nothing specific.
Contact: zhoutianran@huawei.com
Last updated: January 10, 2024

Organization: ZTE Corporation.
Implementation: ZTE ZXCTN 6500-32 routers running V5.00.20 or above. ZTE ZXCTN 6170H routers running V5.00.30.20 or above. ZTE ElasticNet UME Controller running V16.22.20 or above.
Maturity Level: Product
Coverage: Partial,section 2 and example (2) of section 2.1.
Version: Draft-08
Licensing: N/A
Implementation experience: Nothing specific.
Contact: xiao.min2@zte.com.cn
Last updated: January 22, 2024

China Mobile reported that it has deployed over 300,000 Slicing Packet Network (SPN) nodes for 5G backhaul, following the specification in the latest version of this document. This report was last updated on January 10, 2024.

In the Special-Purpose MPLS Label Values registry, a new Extended Special-Purpose MPLS Label Value for the Flow-ID Label Indicator is requested from IANA as follows: Extended Special-Purpose MPLS Label Value Description Semantics Definition Reference TBA1 Flow-ID Label Indicator Section 2 This Document

The authors would like to acknowledge Loa Andersson, Tarek Saad, Stewart Bryant, Rakesh Gandhi, Greg Mirsky, Aihua Liu, Shuangping Zhan, Ming Ke, Wei He, Ximing Dong, and Darren Dukes for their careful review and very helpful comments. The authors would like to acknowledge Italo Busi and Chandrasekar Ramachandran for their insightful MPLS-RT review and very helpful comments.

Minxue Wang
China Mobile
Email: wangminxue@chinamobile.com Wen Ye
China Mobile
Email: yewen@chinamobile.com