BGP signalled private MPLS-labels
draft-kaliraj-bess-bgp-sig-private-mpls-labels-00

Document Type Active Internet-Draft (individual)
Last updated 2017-06-22
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html 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                                   K. Vairavakkalai
Internet-Draft                                              M. Jeyananth
Intended status: Experimental                     Juniper Networks, Inc.
Expires: December 24, 2017                                 June 22, 2017

                   BGP signalled private MPLS-labels
           draft-kaliraj-bess-bgp-sig-private-mpls-labels-00

Abstract

   The MPLS-forwarding-layer in a core network is a shared resource.
   The MPLS FIB at nodes in this layer contains labels that are
   dynamically allocated and locally significant at that node.

   For some usecases like upstream-label-allocation, it is useful to be
   able to create virtual private MPLS-forwarding-layers over this
   shared MPLS-forwarding-layer.  This allows installing deterministic
   private label-values in the private-FIBs created at nodes
   participating in this private MPLS forwarding-layer, while preserving
   the "locally significant" nature of the underlying shared 'public'
   MPLS-forwarding-layer.

   This specification describes the procedures to create such virtual
   private MPLS-forwarding layers (private MPLS-planes) using a new BGP
   family.  And gives a few example use-cases on how this private
   forwarding-layers can be used.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

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 http://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."

Vairavakkalai & JeyanantExpires December 24, 2017               [Page 1]
Internet-Draft        Private MPLS-label namespaces            June 2017

   This Internet-Draft will expire on December 24, 2017.

Copyright Notice

   Copyright (c) 2017 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
   (http://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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Motivation  . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Constructs and building blocks  . . . . . . . . . . . . . . .   4
     3.1.  Context Protocol Nexthop Address  . . . . . . . . . . . .   4
     3.2.  MPLS context FIB  . . . . . . . . . . . . . . . . . . . .   4
     3.3.  Context Label . . . . . . . . . . . . . . . . . . . . . .   5
     3.4.  Roles of nodes in a MPLS-plane  . . . . . . . . . . . . .   5
       3.4.1.  Edge-nodes (PLER) . . . . . . . . . . . . . . . . . .   5
       3.4.2.  Transit-nodes (PLSR)  . . . . . . . . . . . . . . . .   5
     3.5.  Sending traffic into the MPLS plane . . . . . . . . . . .   5
   4.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   6
   5.  BGP families, routes and encoding . . . . . . . . . . . . . .   7
     5.1.  New address-families  . . . . . . . . . . . . . . . . . .   7
       5.1.1.  AFI: MPLS, SAFI: 128  . . . . . . . . . . . . . . . .   7
       5.1.2.  AFI: MPLS, SAFI: 1  . . . . . . . . . . . . . . . . .   8
     5.2.  Routes and Operational procedures . . . . . . . . . . . .   8
       5.2.1.  "Context-Nexthop" discovery route . . . . . . . . . .   8
       5.2.2.  "Private Label" routes  . . . . . . . . . . . . . . .  10
   6.  Example of Usecases . . . . . . . . . . . . . . . . . . . . .  12
     6.1.  Mezanine transport layer in a Seamless-MPLS network . . .  12
     6.2.  Service Forwarding Helper usecase . . . . . . . . . . . .  12
     6.3.  Standard BGP API to a MPLS network's forwarding-plane . .  13
     6.4.  Traffic engineering and Security advantages . . . . . . .  13
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  13
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  14
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  14
Show full document text