Multicast Source Redundancy in EVPN Networks
draft-skr-bess-evpn-redundant-mcast-source-01

Document Type Active Internet-Draft (individual)
Last updated 2019-07-05
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized 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)
BESS Workgroup                                           J. Rabadan, Ed.
Internet Draft                                               J. Kotalwar
                                                            S. Sathappan
Intended status: Standards Track                                   Nokia

                                                                Z. Zhang
                                                                  W. Lin
                                                                 Juniper

                                                                E. Rosen
                                                              Individual

Expires: January 6, 2020                                    July 5, 2019

              Multicast Source Redundancy in EVPN Networks
             draft-skr-bess-evpn-redundant-mcast-source-01

Abstract

   EVPN supports intra and inter-subnet IP multicast forwarding.
   However, EVPN (or conventional IP multicast techniques for that
   matter) do not have a solution for the case where: a) a given
   multicast group carries more than one flow (i.e., more than one
   source), and b) it is desired that each receiver gets only one of the
   several flows. Existing multicast techniques assume there are no
   redundant sources sending the same flow to the same IP multicast
   group, and, in case there were redundant sources, the receiver's
   application would deal with the received duplicated packets. This
   document extends the existing EVPN specifications and assumes that IP
   Multicast source redundancy may exist. It also assumes that, in case
   two or more sources send the same IP Multicast flows into the tenant
   domain, the EVPN PEs need to avoid that the receivers get packet
   duplication by following the described procedures.

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
 

Kotalwar,Sathappan,Rabadan et alExpires January 6, 2020         [Page 1]
Internet-Draft           EVPN Redundant Sources             July 5, 2019

   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

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

   This Internet-Draft will expire on January 6, 2020.

Copyright Notice

   Copyright (c) 2019 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
     1.1 Terminology  . . . . . . . . . . . . . . . . . . . . . . . .  4
     1.2 Background on IP Multicast Delivery in EVPN Networks . . . .  6
       1.2.1 Intra-subnet IP Multicast Forwarding . . . . . . . . . .  6
       1.2.2 Inter-subnet IP Multicast Forwarding . . . . . . . . . .  7
     1.3 Multi-Homed IP Multicast Sources in EVPN . . . . . . . . . .  9
     1.4 The Need for Redundant IP Multicast Sources in EVPN  . . . . 11
   2. Solution Overview . . . . . . . . . . . . . . . . . . . . . . . 11
   3. BGP EVPN Extensions . . . . . . . . . . . . . . . . . . . . . . 13
   4. Warm Standby (WS) Solution for Redundant G-Sources  . . . . . . 14
     4.1 WS Example in an OISM Network  . . . . . . . . . . . . . . . 16
     4.2 WS Example in a Single-BD Tenant Network . . . . . . . . . . 18
 

Kotalwar,Sathappan,Rabadan et alExpires January 6, 2020         [Page 2]
Internet-Draft           EVPN Redundant Sources             July 5, 2019

   5. Hot Standby (HS) Solution for Redundant G-Sources . . . . . . . 19
     5.1 Use of BFD in the HS Solution  . . . . . . . . . . . . . . . 22
     5.2 HS Example in an OISM Network  . . . . . . . . . . . . . . . 22
     5.3 HS Example in a Single-BD Tenant Network . . . . . . . . . . 27
Show full document text