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

Document Type Active Internet-Draft (bier WG)
Authors Hooman Bidgoli  , Jayant Kotalwar  , IJsbrand Wijnands  , Mankamana Mishra  , Zhaohui Zhang  , Eddie Leyton 
Last updated 2020-11-10
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                    H. Bidgoli, Ed.
Internet-Draft                                               J. Kotalwar
Intended status: Informational                                     Nokia
Expires: May 5, 2021                                         I. Wijnands
                                                               M. Mishra
                                                            Cisco System
                                                                Z. Zhang
                                                        Juniper Networks
                                                               E. Leyton
                                                                 Verizon
                                                       November 01, 2020

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

Abstract

   Consider an end to end Multipoint LDP (mLDP) network, where it is
   desirable to deploy BIER in portion of this network.  It might be
   desirable to deploy BIER with minimum disruption to the mLDP network
   or redesign of the network.

   This document describes the procedure needed for mLDP tunnels to be
   signaled over and stitched through a BIER core, allowing LDP routers
   to run traditional mLDP 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).  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 May 5, 2021.

Bidgoli, et al.            Expires May 5, 2021                  [Page 1]
Internet-Draft      M-LDP Signaling Through BIER Core      November 2020

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.  Conventions used in this document . . . . . . . . . . . . . .   2
     2.1.  Definitions . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  mLDP Signaling Through BIER domain  . . . . . . . . . . . . .   4
     3.1.  Ingress BBR procedure . . . . . . . . . . . . . . . . . .   4
       3.1.1.  Automatic tLDP session Creation . . . . . . . . . . .   5
       3.1.2.  ECMP Method on IBBR . . . . . . . . . . . . . . . . .   5
     3.2.  Egress BBR procedure  . . . . . . . . . . . . . . . . . .   5
       3.2.1.  IBBR procedure for arriving upstream assigned label .   6
   4.  Datapath Forwarding . . . . . . . . . . . . . . . . . . . . .   6
     4.1.  Datapath traffic flow . . . . . . . . . . . . . . . . . .   6
   5.  Recursive FEC . . . . . . . . . . . . . . . . . . . . . . . .   6
   6.  IANA Consideration  . . . . . . . . . . . . . . . . . . . . .   7
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   8.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   7
   9.  Informative References  . . . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   Some operators that are using mLDP P2MP LSPs for their multicast
   transport would like to deploy BIER technology in some segment of
   their network.  This draft explains a method to signal mLDP services
   through a BIER domain, with minimal disruption and operational impact
   to the mLDP domain.

2.  Conventions used in this document

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

Bidgoli, et al.            Expires May 5, 2021                  [Page 2]
Internet-Draft      M-LDP Signaling Through BIER Core      November 2020

2.1.  Definitions

   Some of the terminology specified in [RFC8279] is replicated here and
Show full document text