| Internet-Draft | IPFIX MPLS Segment Routing Information | September 2021 |
| Graf | Expires 13 March 2022 | [Page] |
This document introduces new IP Flow Information Export (IPFIX) code points to identify which traffic is being forwarded based on which MPLS control plane protocol used within a Segment Routing domain. In particular, this document defines five code points for the IPFIX mplsTopLabelType Information Element for PCE, IS-IS, OSPFv2, OSPFv3, and BGP MPLS Segment Routing extensions.¶
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 13 March 2022.¶
Copyright (c) 2021 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 Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.¶
Four routing protocol extensions, OSPFv2 Extensions [RFC8665], OSPFv3 Extensions [RFC8666], IS-IS Extensions [RFC8667], BGP Prefix Segment Identifiers (Prefix-SIDs) [RFC8669] and one Path Computation Element Communication Protocol (PCEP) Extension [RFC8664] have been defined to be able to propagate Segment Routing (SR) labels for the MPLS data plane [RFC8660].¶
Also, [I-D.ali-spring-sr-traffic-accounting] describes how IP Flow Information Export [RFC7012] can be leveraged to account traffic to MPLS SR label dimensions within a Segment Routing domain.¶
In [RFC7012], the Information Element (IE) mplsTopLabelType(46) identifies which MPLS control plane protocol allocated the top-of-stack label in the MPLS label stack. Section 7.2 of [RFC7012] creates the "IPFIX MPLS label type (Value 46)" subregistry [IANA-IPFIX] where MPLS label type should be added. This document defines new code points to address typical use cases that are discussed in Section 2.¶
By introducing five new code points to the IPFIX IE mplsTopLabelType(46) for PCE, IS-IS, OSPFv2, OSPFv3 and BGP Prefix-SID, it is possible to identify which traffic is being forwarded based upon which MPLS SR control plane protocol is in use.¶
A typical use case is to monitor MPLS control plane migrations from LDP to IS-IS or OSPF Segment Routing. Such a migration can be done node by node as described in Appendix A of [RFC8661].¶
Another use case is to monitor MPLS control plane migrations from dynamic BGP labels [RFC8277] to BGP Prefix-SIDs in the context of Seamless MPLS SR described in Section 4.6 of [I-D.hegde-spring-mpls-seamless-sr].¶
Both use cases can be verified by using mplsTopLabelType(46), mplsTopLabelIPv4Address(47), mplsTopLabelIPv6Address(140), mplsTopLabelStackSection(70) and forwardingStatus(89) IEs to infer¶
By looking at the MPLS label value itself, it is not always clear as to which label protocol it belongs. This is because they may share the same label allocation range. This is, for example, the case for IGP-Adjacency SIDs, LDP and dynamic BGP labels.¶
This document requests IANA to allocate the following code points in the existing subregistry "IPFIX MPLS label type (Value 46)" under the "IPFIX Information Elements" registry [RFC7012] available at [IANA-IPFIX].¶
+-------+--------------------------------+----------------------+
| Value | Description | Reference |
+-------+--------------------------------+----------------------+
| TBD1 | Path Computation Element | [RFC-to-be], RFC8664 |
+-------+--------------------------------+----------------------+
| TBD2 | OSPFv2 Segment Routing | [RFC-to-be], RFC8665 |
+-------+--------------------------------+----------------------+
| TBD3 | OSPFv3 Segment Routing | [RFC-to-be], RFC8666 |
+-------+--------------------------------+----------------------+
| TBD4 | IS-IS Segment Routing | [RFC-to-be], RFC8667 |
+-------+--------------------------------+----------------------+
| TBD5 | BGP Segment Routing Prefix-SID | [RFC-to-be], RFC8669 |
+-------+--------------------------------+----------------------+
Table 1: Updates to "IPFIX MPLS label type (Value 46)" subregistry
¶
Note to the RFC-Editor:¶
In the IE mplsTopLabelType(46), the BGP code point 5 refers to the label value in MP_REACH_NLRI path attribute described in Section 2 of [RFC8277], while the BGP Segment Routing Prefix-SID code point TBD4 corresponds to the label index value in the Label-Index TLV described in Section 3.1 of [RFC8669]. These values are thus used for those distinct purposes.¶
There exists no significant extra security considerations regarding the allocation of these new IPFIX IEs compared to [RFC7012].¶
I would like to thank the IE doctors, Paul Aitken and Andrew Feren, as well Benoit Claise, Loa Andersson, Tianran Zhou, Pierre Francois, Bruno Decreane, Paolo Lucente, Hannes Gredler, Ketan Talaulikar, Sabrina Tanamal, Erik Auerswald, Sergey Fomin, Mohamed Boucadair, Tom Petch, Qin Wu and Matthias Arnold for their review and valuable comments. Many thanks also to Robert Wilton for the AD review. Thanks to Alvaro Retana, Eric Vyncke and Benjamin Kaduk for the IESG review.¶