EVPN Inter-subnet Multicast Forwarding
draft-lin-bess-evpn-irb-mcast-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Authors Wen Lin  , Zhaohui Zhang  , John Drake 
Last updated 2015-04-03
Replaced by draft-ietf-bess-evpn-irb-mcast
Stream (None)
Intended RFC status (None)
Formats pdf htmlized (tools) 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                                                              W. Lin
Internet-Draft                                                  Z. Zhang
Intended status: Standards Track                                J. Drake
Expires: October 5, 2015                          Juniper Networks, Inc.
                                                           April 3, 2015

                 EVPN Inter-subnet Multicast Forwarding
                  draft-lin-bess-evpn-irb-mcast-00.txt

Abstract

   This document describes inter-subnet multicast forwarding procedures
   for Ethernet VPNs (EVPN).

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 October 5, 2015.

Copyright Notice

   Copyright (c) 2015 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

Lin, et al.              Expires October 5, 2015                [Page 1]
Internet-Draft               evpn-irb-mcast                   April 2015

   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.  Solution  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  IGMP/MLD Snooping Consideration . . . . . . . . . . . . .   5
     2.2.  Receiver sites not connected to a source subnet . . . . .   5
     2.3.  Receiver sites without IRB  . . . . . . . . . . . . . . .   5
     2.4.  Multi-homing Support  . . . . . . . . . . . . . . . . . .   6
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   4.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   5.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     5.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     5.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   EVPN provides an extensible and flexible multi-homing VPN solution
   for intra-subnet connectivity among hosts/VMs over an MPLS/IP
   network.  When forwarding among hosts/VMs across different IP subnets
   is required, Integrated Routing and Bridging (IRB) can be used [ietf-
   bess-evpn-inter-subnet-forwarding].

   An NVE device supporting IRB is called a L3 Gateway.  In a
   centralized approach, a centralized gateway provides all L3 routing
   functionality, and even two Tenant Systems on two subnets connected
   to the same NVE need to go through the central gateway, which is
   inefficient.  In a distributed approach, each NVE (or most NVEs) has
   IRB configured, and inter-subnet traffic will be locally routed
   without having to go through a central gateway.

   Inter-subnet multicast forwarding is more complicated and not covered
   in [ietf-bess-evpn-inter-subnet-forwarding].  This document describes
   the procedures for inter-subnet multicast forwarding.

   For multicast traffic sourced from a TS in subnet 1, EVPN BUM
   forwarding will deliver it to all sites, and NVEs with IRB interfaces
   for the subnet will associate the traffic with the corresponding IRB
   interfaces.  From L3 point of view, those NVEs are routers connected
   to the virtual LAN via the IRB interfaces and the source is locally
   attached.  Nothing is different from a traditional LAN and regular
   IGMP/MLD/PIM procedures kick in.

Lin, et al.              Expires October 5, 2015                [Page 2]
Internet-Draft               evpn-irb-mcast                   April 2015
Show full document text