EVPN BUM Using BIER
draft-ietf-bier-evpn-00

Document Type Active Internet-Draft (bier WG)
Last updated 2017-08-15
Stream IETF
Intended RFC status (None)
Formats plain text pdf html 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)
BIER                                                            Z. Zhang
Internet-Draft                                             A. Przygienda
Intended status: Standards Track                        Juniper Networks
Expires: February 16, 2018                                    A. Sajassi
                                                           Cisco Systems
                                                              J. Rabadan
                                                                   Nokia
                                                         August 15, 2017

                          EVPN BUM Using BIER
                        draft-ietf-bier-evpn-00

Abstract

   This document specifies protocols and procedures for forwarding
   broadcast, unknown unicast and multicast (BUM) traffic of Ethernet
   VPNs (EVPN) using Bit Index Explicit Replication (BIER).

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

   This Internet-Draft will expire on February 16, 2018.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Zhang, et al.           Expires February 16, 2018               [Page 1]
Internet-Draft                  bier-evpn                    August 2017

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminologies . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Use of the PMSI Tunnel Attribute  . . . . . . . . . . . . . .   4
     2.1.  Explicit Tracking . . . . . . . . . . . . . . . . . . . .   5
       2.1.1.  Using IMET/SMET routes  . . . . . . . . . . . . . . .   5
       2.1.2.  Using S-PMSI/Leaf A-D Routes  . . . . . . . . . . . .   6
     2.2.  MPLS Label in PTA . . . . . . . . . . . . . . . . . . . .   6
   3.  Multihoming Split Horizon . . . . . . . . . . . . . . . . . .   7
   4.  Data Plane  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     4.1.  Encapsulation and Transmission  . . . . . . . . . . . . .   8
     4.2.  Disposition . . . . . . . . . . . . . . . . . . . . . . .   9
       4.2.1.  At a BFER that is an Egress PE  . . . . . . . . . . .   9
       4.2.2.  At a BFER that is a P-tunnel Segmentation Boundary  .  10
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  10
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  10
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  11
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   [RFC7432] and [I-D.ietf-bess-evpn-overlay] specify the protocols and
   procedures for Ethernet VPNs (EVPNs).  For broadcast, unknown unicast
   and multicast (BUM) traffic, provider/underlay tunnels (referred to
   as P-tunnels) are used to carry the BUM traffic.  Several kinds of
   tunnel technologies can be used, as specified in [RFC7432].

   Bit Index Explicit Replication (BIER) ([I-D.ietf-bier-architecture])
   is an architecture that provides optimal multicast forwarding through
   a "multicast domain", without requiring intermediate routers to
Show full document text