Multicast VPN Using MPLS P2MP and BIER
draft-xie-bier-mvpn-mpls-p2mp-02

Document Type Active Internet-Draft (individual)
Last updated 2018-07-02
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                                             J. Xie
Internet-Draft                                                M. McBride
Intended status: Standards Track                                 M. Chen
Expires: January 3, 2019                             Huawei Technologies
                                                                 L. Geng
                                                            China Mobile
                                                            July 2, 2018

                 Multicast VPN Using MPLS P2MP and BIER
                    draft-xie-bier-mvpn-mpls-p2mp-02

Abstract

   MVPN is a widely deployed multicast service with mLDP or RSVP-TE P2MP
   as the P-tunnel.  Bit Index Explicit Replication (BIER) is an
   architecture that provides optimal multicast forwarding without
   requiring intermediate routers to maintain any per-flow state by
   using a multicast-specific BIER header.  This document introduces a
   seamless transition mechanism from legacy MVPN using mLDP/RSVP-TE
   P2MP to MVPN using BIER by combining P2MP and BIER to form a P2MP
   based BIER as the P-tunnel.  This will leverage the widely supported
   P2MP capability in both data-plane and control-plane, and will help
   introducing BIER in existing multicast networks to shift multicast
   delivery from MVPN using mLDP/RSVP-TE P2MP by two means: It is easier
   and more efficient for legacy routers to support BIER forwarding on
   the basis of widely supported P2MP forwarding, and it is more
   seamless for existing multicast networks to deploy BIER when some
   routers do not support BIER forwarding.

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 [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 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

Xie, et al.              Expires January 3, 2019                [Page 1]
Internet-Draft        MVPN Using MPLS P2MP and BIER            July 2018

   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 January 3, 2019.

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
   (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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Applicability Statement . . . . . . . . . . . . . . . . . . .   4
   4.  MVPN using P2MP based BIER  . . . . . . . . . . . . . . . . .   5
     4.1.  Overview  . . . . . . . . . . . . . . . . . . . . . . . .   5
     4.2.  MVPN Transition from P2MP to P2MP based BIER  . . . . . .   5
       4.2.1.  Use of the PTA in x-PMSI A-D Routes . . . . . . . . .   6
     4.3.  Building P2MP based BIER forwarding state . . . . . . . .   8
   5.  P2MP based BIER Forwarding Procedures . . . . . . . . . . . .   8
     5.1.  Overview  . . . . . . . . . . . . . . . . . . . . . . . .   8
     5.2.  P2MP based BIER forwarding  . . . . . . . . . . . . . . .   9
     5.3.  When Mid, Leaf or Bud nodes do not support P-CAPABILITY .  11
     5.4.  When Leaf or Bud nodes do not support D-CAPABILITY  . . .  13
   6.  Provisioning Considerations . . . . . . . . . . . . . . . . .  15
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  16
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  16
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  16
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  17
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  17
     10.2.  Informative References . . . . . . . . . . . . . . . . .  18
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  18
Show full document text