Skip to main content

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

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Keyur Patel , Ali Sajassi , John Drake , Wim Henderickx
Last updated 2016-01-03 (Latest revision 2015-07-02)
Replaced by draft-keyupate-bess-evpn-virtual-hub
RFC stream (None)
Intended RFC status (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-keyupate-bess-evpn-virtual-hub
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

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.

Authors

Keyur Patel
Ali Sajassi
John Drake
Wim Henderickx

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)