Network Working Group T. Graf
Internet-Draft Swisscom
Intended status: Standards Track March 15, 2020
Expires: September 16, 2020
Export of MPLS Segment Routing Label Type Information in
IP Flow Information Export (IPFIX)
draft-tgraf-ipfix-mpls-sr-label-type-00
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 16, 2020.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
Graf Expires September 16, 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. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . 3
5. Normative References . . . . . . . . . . . . . . . . . . . . 3
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4
1. Introduction
Besides existing MPLS controlplane protocols such as BGP-4 [RFC8277],
LDP [RFC5036] and BGP VPN [RFC4364], IS-IS Extensions
[I-D.ietf-isis-segment-routing-extensions] and OSPF Extensions
[I-D.ietf-ospf-segment-routing-extensions] had been added to
propagate Segment Routing labels for the MPLS dataplane
[I-D.ietf-spring-segment-routing-mpls].
Traffic Accounting in Segment Routing Networks
[I-D.ali-spring-sr-traffic-accounting] describes how IPFIX can be
laveraged 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 controlplane 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 inisghts which
traffic is being forwarded based on which MPLS controlplane protocol.
A typical use case scenario is to monitor MPLS controlplane
migrations from LDP to IS-IS or OSPF
Graf Expires September 16, 2020 [Page 2]
Internet-Draft IPFIX MPLS Segment Routing Information March 2020
2. Acknowledgements
I would like to thank Zafar Ali for his valuable comments.
3. IANA Considerations
This document specifies two additional values for IS-IS and OSPF
Segment Routing extension in the Information Element #46 at IP Flow
Information Export (IPFIX).
------------------------------------------------------------------
|ElementID|Value| Description | Abstract | Data Type |
| | | | Data Type | Semantics |
|----------------------------------------------------------------|
| 46 | x | IS-IS Segment Routing | unsigned8 | identifier |
|----------------------------------------------------------------|
| 46 | x | OSPF Segment Routing | unsigned8 | identifier |
------------------------------------------------------------------
Figure 1: Updates to "IPFIX Information Element #46" SubRegistry
4. Security Considerations
It is not believed that this document adds any additional security
considerations.
5. Normative 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.
[I-D.ietf-isis-segment-routing-extensions]
Previdi, S., Ginsberg, L., Filsfils, C., Bashandy, A.,
Gredler, H., and B. Decraene, "IS-IS Extensions for
Segment Routing", draft-ietf-isis-segment-routing-
extensions-25 (work in progress), May 2019.
[I-D.ietf-ospf-segment-routing-extensions]
Psenak, P., Previdi, S., Filsfils, C., Gredler, H.,
Shakir, R., Henderickx, W., and J. Tantsura, "OSPF
Extensions for Segment Routing", draft-ietf-ospf-segment-
routing-extensions-27 (work in progress), December 2018.
Graf Expires September 16, 2020 [Page 3]
Internet-Draft IPFIX MPLS Segment Routing Information March 2020
[I-D.ietf-spring-segment-routing-mpls]
Bashandy, A., Filsfils, C., Previdi, S., Decraene, B.,
Litkowski, S., and R. Shakir, "Segment Routing with MPLS
data plane", draft-ietf-spring-segment-routing-mpls-22
(work in progress), May 2019.
[IANA-IPFIX-IE46]
"IANA IP Flow Information Export (IPFIX) Information
Element #46 SubRegistry",
<https://www.iana.org/assignments/ipfix/ipfix.xhtml#ipfix-
mpls-label-type>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.
[RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private
Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February
2006, <https://www.rfc-editor.org/info/rfc4364>.
[RFC5036] Andersson, L., Ed., Minei, I., Ed., and B. Thomas, Ed.,
"LDP Specification", RFC 5036, DOI 10.17487/RFC5036,
October 2007, <https://www.rfc-editor.org/info/rfc5036>.
[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,
<https://www.rfc-editor.org/info/rfc5102>.
[RFC7012] Claise, B., Ed. and B. Trammell, Ed., "Information Model
for IP Flow Information Export (IPFIX)", RFC 7012,
DOI 10.17487/RFC7012, September 2013,
<https://www.rfc-editor.org/info/rfc7012>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8277] Rosen, E., "Using BGP to Bind MPLS Labels to Address
Prefixes", RFC 8277, DOI 10.17487/RFC8277, October 2017,
<https://www.rfc-editor.org/info/rfc8277>.
Author's Address
Graf Expires September 16, 2020 [Page 4]
Internet-Draft IPFIX MPLS Segment Routing Information March 2020
Thomas Graf
Swisscom
Binzring 17
Zurich 8045
Switzerland
Email: thomas.graf@swisscom.com
Graf Expires September 16, 2020 [Page 5]