| Internet-Draft | Signaling FLC and FRLD | February 2022 |
| Min, et al. | Expires 19 August 2022 | [Page] |
Flow-ID Label (FL) is used for MPLS flow identification and flow-based performance measurement with alternate marking method. The ability to process Flow-ID labels is called Flow-ID Label Capability (FLC), and the capability of reading the maximum label stack depth and performing FL-based performance measurement is called Flow-ID Readable Label Depth (FRLD). This document defines a mechanism to signal the FLC and the FRLD using IGP and BGP-LS.¶
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 19 August 2022.¶
Copyright (c) 2022 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
As specified in [I-D.ietf-mpls-inband-pm-encapsulation], Flow-ID Label (FL) is used for MPLS flow identification and flow-based performance measurement with alternate marking method.¶
Flow-ID Label may appear multiple times in a label stack with variable depth, so both the Flow-ID Label Capability (FLC) and the Flow-ID Readable Label Depth (FRLD) are defined in [I-D.ietf-mpls-inband-pm-encapsulation].¶
Analogous to [RFC9088] and [RFC9089], this document defines a mechanism to signal the FLC and the FRLD using IGP and BGP-LS, specifically, IGP includes IS-IS, OSPFv2 and OSPFv3.¶
This memo makes use of the terms defined in [I-D.ietf-mpls-inband-pm-encapsulation] and [RFC8491].¶
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.¶
FLC is a property of the node, so FLC is advertised with a node in this document.¶
If a router has multiple interfaces, the router MUST NOT announce FLC unless all of its interfaces are capable of processing FLs.¶
[RFC8667] defines SR-Capabilities sub-TLV of the IS-IS Router Capability TLV (defined in [RFC7981]). Bit 2 in the Flags field of SR-Capabilities sub-TLV is used as the FLC Flag (F-Flag), as shown in Figure 1.¶
0 1 2 3 4 5 6 7 +-+-+-+-+-+-+-+-+ |I|V|F| | +-+-+-+-+-+-+-+-+
F-Flag:¶
[RFC8665] defines some SR Capabilities TLVs as top-level TLVs of the Router Information Opaque LSA (defined in [RFC7770]). The SR Capabilities TLVs are applicable to both OSPFv2 and OSPFv3 (see also [RFC8666]). Within the SR Capabilities TLVs, the SID/Label Range TLV has a 1-octet Reserved field. Bit 0 in the Reserved field of SID/Label Range TLV is used as the FLC Flag (F-Flag), as shown in Figure 2.¶
0 1 2 3 4 5 6 7 +-+-+-+-+-+-+-+-+ |F| | +-+-+-+-+-+-+-+-+
F-Flag:¶
As requested by [RFC8491], IANA has created an IANA-managed registry titled "IGP MSD-Types" to identify MSD-Types. A new MSD-Type, called FRLD-MSD, is defined to advertise the FRLD of a given router. The MSD-Type code 3 is requested to be assigned by IANA for FRLD-MSD. The MSD-Value field is set to the FRLD in the range between 0 to 255.¶
If a router has multiple interfaces with different capabilities of reading the maximum label stack depth, the router MUST advertise the smallest value found across all of its interfaces.¶
For IS-IS, the FRLD is advertised in a Node MSD Sub-TLV [RFC8491] using the FRLD-MSD type.¶
For OSPF including both OSPFv2 and OSPFv3, the FRLD is advertised in a Node MSD TLV [RFC8476] using the FRLD-MSD type.¶
The absence of FRLD-MSD advertisements indicates only that the advertising node does not support advertisement of this capability.¶
The IGP extensions defined in this document can be advertised via BGP-LS (Distribution of Link-State and Traffic Engineering Information Using BGP) [I-D.ietf-idr-rfc7752bis] using existing BGP-LS TLVs.¶
The FLC is advertised using the SR Capabilities TLV as defined in [RFC9085].¶
The FRLD-MSD is advertised using the Node MSD TLV as defined in [RFC8814].¶
This document specifies the ability to advertise additional node capabilities using IS-IS, OSPF and BGP-LS. As such, the security considerations as described in the referenced specifications are applicable to this document.¶
Incorrectly setting the F-Flag during origination, propagation, or redistribution may lead to poor or no performance measurement of the MPLS traffic or to the MPLS traffic being discarded on the egress node.¶
Incorrectly setting the FRLD value may lead to poor or no performance measurement of the MPLS traffic.¶
This document requests the following allocation from IANA:¶
The authors would like to acknowledge Acee Lindem and Les Ginsberg for their very helpful comments.¶