Network Working Group T. Graf Internet-Draft Swisscom Intended status: Standards Track March 26, 2020 Expires: September 27, 2020 Export of MPLS Segment Routing Label Type Information in IP Flow Information Export (IPFIX) draft-tgraf-ipfix-mpls-sr-label-type-02 Abstract This document introduces two additional values in the Information Element mplsTopLabelType for IS-IS and OSPF MPLS Segment Routing (SR) extensions to enable Segment Routing label type information in IP Flow Information Export (IPFIX). 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 RFC 2119 [RFC2119] RFC 8174 [RFC8174] when, and only when, they appear in all capitals, as shown here. Status of This Memo 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 September 27, 2020. Copyright Notice Copyright (c) 2020 IETF Trust and the persons identified as the document authors. All rights reserved. Graf Expires September 27, 2020 [Page 1] Internet-Draft IPFIX MPLS Segment Routing Information March 2020 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. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 3. Security Considerations . . . . . . . . . . . . . . . . . . . 3 4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 3 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5 1. Introduction Besides existing MPLS control plane protocols such as BGP-4 [RFC8277], LDP [RFC5036] and BGP VPN [RFC4364], IS-IS Extensions [RFC8667] and OSPF Extensions [RFC8665] had been added to propagate Segment Routing labels for the MPLS dataplane [RFC8660]. Traffic Accounting in Segment Routing Networks [I-D.ali-spring-sr-traffic-accounting] describes how IPFIX can be leveraged to account traffic to MPLS Segment Routing label dimensions within a Segment Routing domain. In the Information Model for IP Flow Information Export IPFIX [RFC5102], the information element #46 mplsTopLabelType describes which MPLS control plane protocol allocated the top-of-stack label in the MPLS label stack. RFC 7012 section 7.2 [RFC7012] describes the IANA Information Element #46 SubRegistry [IANA-IPFIX-IE46] where new values should be added. By introducing two new values to information element #46 mplsTopLabelType for IS-IS and OSPF, when Segment Routing with one of these two routing protocols is deployed, we get insight which traffic is being forwarded based on which MPLS control plane protocol. A typical use case scenario is to monitor MPLS control plane migrations from LDP to IS-IS or OSPF. By looking at the label value itself, it is not always clear to which label protocol it belongs to, since they could potentially share the same label allocation range. This is the case for IGP-Adjacency Segment SID's and LDP as an example. Graf Expires September 27, 2020 [Page 2] Internet-Draft IPFIX MPLS Segment Routing Information March 2020 2. IANA Considerations This document specifies two additional values for IS-IS and OSPF Segment Routing extension in the sub-registry "IPFIX MPLS label type (Value 46)" of the "IPFIX Information Elements" registry in the "IP Flow Information Export (IPFIX) Entities" name space. -------------------------------------------- | Value| Description | Reference | |------------------------------------------| | TBD1 | IS-IS Segment Routing | RFC8667 | |------------------------------------------| | TBD2 | OSPF Segment Routing | RFC8665 | -------------------------------------------- Figure 1: Updates to "IPFIX Information Element #46" SubRegistry 3. Security Considerations The same security considerations apply as for the IPFIX Protocol [RFC7012]. 4. Acknowledgements I would like to thank Paul Aitken, Loa Andersson, Tianran Zhou, Pierre Francois, Paulo Lucente for their review and valuable comments. 5. References 5.1. Normative References [IANA-IPFIX-IE46] "IANA IP Flow Information Export (IPFIX) Information Element #46 SubRegistry", . [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC5102] Quittek, J., Bryant, S., Claise, B., Aitken, P., and J. Meyer, "Information Model for IP Flow Information Export", RFC 5102, DOI 10.17487/RFC5102, January 2008, . Graf Expires September 27, 2020 [Page 3] Internet-Draft IPFIX MPLS Segment Routing Information March 2020 [RFC7012] Claise, B., Ed. and B. Trammell, Ed., "Information Model for IP Flow Information Export (IPFIX)", RFC 7012, DOI 10.17487/RFC7012, September 2013, . [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, . 5.2. Informative References [I-D.ali-spring-sr-traffic-accounting] Filsfils, C., Talaulikar, K., Sivabalan, S., Horneffer, M., Raszuk, R., Litkowski, S., Voyer, D., and R. Morton, "Traffic Accounting in Segment Routing Networks", draft- ali-spring-sr-traffic-accounting-04 (work in progress), February 2020. [RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February 2006, . [RFC5036] Andersson, L., Ed., Minei, I., Ed., and B. Thomas, Ed., "LDP Specification", RFC 5036, DOI 10.17487/RFC5036, October 2007, . [RFC8277] Rosen, E., "Using BGP to Bind MPLS Labels to Address Prefixes", RFC 8277, DOI 10.17487/RFC8277, October 2017, . [RFC8660] Bashandy, A., Ed., Filsfils, C., Ed., Previdi, S., Decraene, B., Litkowski, S., and R. Shakir, "Segment Routing with the MPLS Data Plane", RFC 8660, DOI 10.17487/RFC8660, December 2019, . [RFC8665] Psenak, P., Ed., Previdi, S., Ed., Filsfils, C., Gredler, H., Shakir, R., Henderickx, W., and J. Tantsura, "OSPF Extensions for Segment Routing", RFC 8665, DOI 10.17487/RFC8665, December 2019, . [RFC8667] Previdi, S., Ed., Ginsberg, L., Ed., Filsfils, C., Bashandy, A., Gredler, H., and B. Decraene, "IS-IS Extensions for Segment Routing", RFC 8667, DOI 10.17487/RFC8667, December 2019, . Graf Expires September 27, 2020 [Page 4] Internet-Draft IPFIX MPLS Segment Routing Information March 2020 Author's Address Thomas Graf Swisscom Binzring 17 Zurich 8045 Switzerland Email: thomas.graf@swisscom.com Graf Expires September 27, 2020 [Page 5]