Using Entropy Label for Network Slice Identification in MPLS networks.
draft-decraene-mpls-slid-encoded-entropy-label-id-00

Document Type Active Internet-Draft (individual)
Authors Bruno Decraene  , Clarence Filsfils  , Wim Henderickx  , Tarek Saad  , Vishnu Beeram 
Last updated 2020-12-16
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)
MPLS                                                    B. Decraene, Ed.
Internet-Draft                                                    Orange
Updates: 6790 (if approved)                                  C. Filsfils
Intended status: Standards Track                     Cisco Systems, Inc.
Expires: June 19, 2021                                     W. Henderickx
                                                                   Nokia
                                                                 T. Saad
                                                               V. Beeram
                                                        Juniper Networks
                                                       December 16, 2020

 Using Entropy Label for Network Slice Identification in MPLS networks.
          draft-decraene-mpls-slid-encoded-entropy-label-id-00

Abstract

   This document defines a solution to encode a slice identifier in MPLS
   in order to distinguish packets that belong to different slices, to
   allow enforcing per network slice policies (.e.g, Qos).

   The slice identification is independent of the topology.  It allows
   for QoS/DiffServ policy on a per slice basis in addition to the per
   packet QoS/DiffServ policy provided by the MPLS Traffic Class field.

   In order to minimize the size of the MPLS stack and to ease
   incremental deployment the slice identifier is encoded as part of the
   Entropy Label.

   This document also extends the use of the TTL field of the Entropy
   Label in order to provide a flexible set of flags called the Entropy
   Label Control field.

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."

Decraene, et al.          Expires June 19, 2021                 [Page 1]
Internet-Draft       Slice Identification in MPLS EL       December 2020

   This Internet-Draft will expire on June 19, 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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Entropy Label Control field . . . . . . . . . . . . . . . . .   3
   3.  Slice Identifier  . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Ingress LSR . . . . . . . . . . . . . . . . . . . . . . .   4
     3.2.  Transit LSR . . . . . . . . . . . . . . . . . . . . . . .   4
     3.3.  Bandwidth-Allocation Slice  . . . . . . . . . . . . . . .   4
     3.4.  Backward Compatibility  . . . . . . . . . . . . . . . . .   5
     3.5.  Benefits  . . . . . . . . . . . . . . . . . . . . . . . .   5
   4.  End to end absolute loss measurements . . . . . . . . . . . .   6
   5.  Programmed sampling of packets  . . . . . . . . . . . . . . .   6
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   Segment Routing (SR) [RFC8402] leverages the source-routing paradigm.
   A node steers a packet through a controlled set of instructions,
   called segments, by prepending the packet with an SR header.  In the
   SR-MPLS data plane [RFC8660], the SR header is instantiated through a
   label stack.

   This document defines a solution to encode a slice identifier in MPLS
   in order to provide QoS on a per slice basis.  It allows for QoS/
   DiffServ policy on a per slice basis in addition to the per packet
   QoS/DiffServ policy provided by the MPLS Traffic Class field.  The
   slice identification is independent of the topology and the QoS of
   the network, thus enabling scalable network slicing.

Decraene, et al.          Expires June 19, 2021                 [Page 2]
Show full document text