Virtual Hub-and-Spoke in BGP EVPNs
draft-keyupate-bess-evpn-virtual-hub-00

Document Type Active Internet-Draft (individual)
Last updated 2017-03-27 (latest revision 2017-03-13)
Replaces draft-keyupate-evpn-virtual-hub
Stream (None)
Intended RFC status (None)
Formats plain text 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)
L2VPNs                                                          K. Patel
Internet-Draft                                                    Arrcus
Intended status: Standards Track                              A. Sajassi
Expires: September 12, 2017                                Cisco Systems
                                                                J. Drake
                                                                Z. Zhang
                                                  Juniper Networks, Inc.
                                                           W. Henderickx
                                                                   Nokia
                                                          March 12, 2017

                   Virtual Hub-and-Spoke in BGP EVPNs
                   draft-keyupate-bess-evpn-virtual-hub-00

Abstract

   Ethernet Virtual Private Network (EVPN) solution is becoming
   pervasive for Network Virtualization Overlay (NVO) services in data
   center (DC) applications and as the next generation virtual private
   LAN services in service provider (SP) applications.

   The use of host IP default route and host unknown MAC route within a
   DC is well understood in order to ensure that leaf nodes within a DC
   only learn and store host MAC and IP addresses for that DC.  All
   other host MAC and IP addresses from remote DCs are learned and
   stored in DC GW nodes thus alleviating leaf nodes from learning host
   MAC and IP addresses from the remote DCs.

   This draft further optimizes the MAC and IP address learning at the
   leaf nodes such that a leaf node within a DC only needs to learn and
   store MAC and IP addresses associated with the sites directly
   connected to it.  A leaf node does not need to learn and store MAC
   and IP addresses from any other leaf nodes thus reducing the number
   of learned MACs and IP addresses per EVI substantially.

   The modifications provided by this draft updates and extends RFC7024
   for BGP EVPN Address Family.

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

Patel, et al.           Expires September 8, 2017               [Page 1]
Internet-Draft                                                March 2017

   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 September 8, 2017.

Copyright Notice

   Copyright (c) 2017 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
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   4
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Routing Information Exchange for EVPN routes  . . . . . . . .   5
   5.  EVPN unknown MAC Route  . . . . . . . . . . . . . . . . . . .   5
     5.1.  Originating EVPN Unknown MAC Route by a V-Hub . . . . . .   5
     5.2.  Processing VPN-MAC EVPN unknown Route by a V-SPOKE  . . .   5
     5.3.  Aliasing  . . . . . . . . . . . . . . . . . . . . . . . .   6
     5.4.  Split-Horizon And Mass Withdraw . . . . . . . . . . . . .   7
   6.  Forwarding Considerations . . . . . . . . . . . . . . . . . .   7
     6.1.  IP-only Forwarding  . . . . . . . . . . . . . . . . . . .   7
     6.2.  MAC-only Forwarding - Bridging  . . . . . . . . . . . . .   7
     6.3.  MAC and IP Forwarding - IRB . . . . . . . . . . . . . . .   8
   7.  Handling of the Broadcast and Multicast traffic . . . . . . .   8
     7.1.  Split Horizon . . . . . . . . . . . . . . . . . . . . . .   9
     7.2.  Route Advertisement . . . . . . . . . . . . . . . . . . .   9
     7.3.  Designated Forwarder in a Cluster . . . . . . . . . . . .  10
Show full document text