Export of MPLS Segment Routing Label Type Information in IP Flow Information Export (IPFIX)
draft-tgraf-ipfix-mpls-sr-label-type-03

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Author Thomas Graf 
Last updated 2020-03-28 (latest revision 2020-03-26)
Stream (None)
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                            T. Graf
Internet-Draft                                                  Swisscom
Intended status: Standards Track                          March 29, 2020
Expires: September 30, 2020

        Export of MPLS Segment Routing Label Type Information in
                   IP Flow Information Export (IPFIX)
                draft-tgraf-ipfix-mpls-sr-label-type-03

Abstract

   This document introduces additional code points in the Information
   Element mplsTopLabelType for IS-IS, OSPFv2, OSPFv3 MPLS Segment
   Routing (SR) extensions and a new SID type element to enable Segment
   Routing label and segment 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 30, 2020.

Copyright Notice

   Copyright (c) 2020 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Graf                   Expires September 30, 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.  MPLS Segment Routing Top Label Type . . . . . . . . . . . . .   2
   3.  Segment Routing Segment Identifier Type . . . . . . . . . . .   3
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   3
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   Besides existing MPLS control plane protocols such as BGP-4
   [RFC8277], LDP [RFC5036] and BGP VPN [RFC4364], three new routing-
   protocols, OSPFv2 Extensions [RFC8665], OSPFv3 Extensions [RFC8666]
   and IS-IS Extensions [RFC8667] 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-SR 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
   code points should be added.

2.  MPLS Segment Routing Top Label Type

   By introducing three new code points to information element #46
   mplsTopLabelType for IS-IS, OSPFv2 and OSPFv3, when Segment Routing
   with one of these three routing protocols is deployed, we get insight
   into which traffic is being forwarded based on which MPLS control
   plane protocol.

Graf                   Expires September 30, 2020               [Page 2]
Internet-Draft   IPFIX MPLS Segment Routing Information       March 2020

   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 as to which label protocol it belongs,
   since they could potentially share the same label allocation range.
   This is the case for IGP-Adjacency SID's and LDP as an example.
Show full document text