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

Document Type Active Internet-Draft (individual)
Author Thomas Graf 
Last updated 2020-09-12
Stream (None)
Intended RFC status (None)
Formats plain text xml 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                      September 12, 2020
Expires: March 16, 2021

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

Abstract

   This document introduces additional code points in the
   mplsTopLabelType Information Element for IS-IS, OSPFv2, OSPFv3 and
   BGP MPLS Segment Routing (SR) extensions to enable Segment Routing
   label protocol type information in IP Flow Information Export
   (IPFIX).

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 March 16, 2021.

Copyright Notice

   Copyright (c) 2020 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

Graf                     Expires March 16, 2021                 [Page 1]
Internet-Draft   IPFIX MPLS Segment Routing Information   September 2020

   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.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   3
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   3
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   Besides BGP-4 [RFC8277], LDP [RFC5036] and BGP VPN [RFC4364], four
   new routing-protocols, OSPFv2 Extensions [RFC8665], OSPFv3 Extensions
   [RFC8666], IS-IS Extensions [RFC8667] and BGP Prefix-SID [RFC8669]
   have been added to the list of routing-protocols able 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
   [RFC7012], 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 four new code points to information element #46
   mplsTopLabelType for IS-IS, OSPFv2, OSPFv3 and BGP Prefix-SID, when
   Segment Routing with one of these four routing protocols is deployed,
   we get insight into 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 Segment Routing.  Such a
   migration can be done node by node as described in RFC8661 [RFC8661]

   Another use case is the monitoring of a migration to a Seamless MPLS
   SR [I-D.hegde-spring-mpls-seamless-sr] architecture.  Where prefixes
   are propagated with dynamic BGP labels according to RFC8277

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

   [RFC8277], BGP Prefix-SID according to RFC8669 [RFC8669] and used for
   the forwarding between IGP domains.  Adding an additional layer into
   the MPLS dataplane to above discribed use case.

   Both use cases can be verified by looking at IE46, mplsTopLabelType,
   IE47, mplsTopLabelIPv4Address, IE70, mplsTopLabelStackSection and
Show full document text