M-LDP Signaling Through BIER Core
draft-hj-bier-mldp-signaling-00

Document Type Active Internet-Draft (individual)
Last updated 2018-07-02
Stream (None)
Intended RFC status (None)
Formats plain text 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)
BIER Workgroup                                           H. Bidgoli, Ed.
Internet Draft                                               A. Dolganow
Intended status: Standard Track                              J. Kotalwar
                                                                   Nokia

Expires: January 3, 2019                                    July 2, 2018

                   M-LDP Signaling Through BIER Core
                    draft-hj-bier-mldp-signaling-00

Abstract 

   Bit Index Explicit Replication (BIER) is an architecture that
   provides multicast forwarding through a "BIER domain" without
   requiring intermediate routers to maintain multicast related per-flow
   state.  Neither does BIER require an explicit tree-building protocol
   for its operation.  A multicast data packet enters a BIER domain at a
   "Bit-Forwarding Ingress Router" (BFIR), and leaves the BIER domain at
   one or more "Bit-Forwarding Egress Routers" (BFERs).  The BFIR router
   adds a BIER header to the packet.  Such header contains a bit-string
   in which each bit represents exactly one BFER to forward the packet
   to.  The set of BFERs to which the multicast packet needs to be
   forwarded is expressed by the according set of bits switched on in
   BIER packet header.

   This document describes the procedure needed for mLDP tunnels to be
   signaled and stitched through a BIER core. Allowing LDP routers to
   run traditional Multipoint LDP services through a BIER core.

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), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   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." The list
   of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt
 

Bidgoli, et al.         Expires January 3, 2019                 [Page 1]
Internet-Draft      MLDP Stitching Through BIER Core        July 2, 2018

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

   This Internet-Draft will expire on October 8, 2017.

Copyright Notice

   Copyright (c) 2018 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. Conventions used in this document . . . . . . . . . . . . . . .  3
     2.1. Definitions . . . . . . . . . . . . . . . . . . . . . . . .  3
   3. M-LDP Signaling Through BIER domain . . . . . . . . . . . . . .  5
     3.1. Ingress BBR procedure . . . . . . . . . . . . . . . . . . .  5
     3.2. Assigning the BIER sub-domain Tree Label  . . . . . . . . .  6
       3.2.1. Method 1: IBBR as extraction point to SDN controller  .  6
       3.2.2. Method 2, EBBR assigning the BTL  . . . . . . . . . . .  7
         3.2.2.1. BIER packet construction at IBBR for Method 2 . . .  7
         3.2.2.2. Signaling mLDP through the BIER domain procedure  .  8
     3.3. SDN Controller procedure for updating BBRs with BTL . . . .  8
     3.4. BGP procedure for signaling BTL for method 2  . . . . . . .  9
     3.5. EBBR procedure method . . . . . . . . . . . . . . . . . . .  9
     3.6. Label release . . . . . . . . . . . . . . . . . . . . . . . 10
       3.6.1 Label release in method 1  . . . . . . . . . . . . . . . 10
       3.6.2 Label release in method 2  . . . . . . . . . . . . . . . 10
   4. Datapath Forwarding . . . . . . . . . . . . . . . . . . . . . . 10
     4.1. BFIR tracking of FEC  . . . . . . . . . . . . . . . . . . . 10
     4.2. Datapath traffic flow . . . . . . . . . . . . . . . . . . . 10
   5. Recursive FEC . . . . . . . . . . . . . . . . . . . . . . . . . 11
   6.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 11
   7. Security Considerations . . . . . . . . . . . . . . . . . . . . 11
   8. References  . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Show full document text