Applicability of EVPN to NVO3 Networks
draft-rabadan-nvo3-evpn-applicability-01
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Jorge Rabadan , Matthew Bocci , Sami Boutros , Ali Sajassi | ||
Last updated | 2018-08-13 (Latest revision 2018-02-09) | ||
Replaced by | draft-ietf-nvo3-evpn-applicability | ||
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-ietf-nvo3-evpn-applicability | |
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
In NVO3 networks, Network Virtualization Edge (NVE) devices sit at the edge of the underlay network and provide Layer-2 and Layer-3 connectivity among Tenant Systems (TSes) of the same tenant. The NVEs need to build and maintain mapping tables so that they can deliver encapsulated packets to their intended destination NVE(s). While there are different options to create and disseminate the mapping table entries, NVEs may exchange that information directly among themselves via a control-plane protocol, such as EVPN. EVPN provides an efficient, flexible and unified control-plane option that can be used for Layer-2 and Layer-3 Virtual Network (VN) service connectivity. This document describes the applicability of EVPN to NVO3 networks and how EVPN solves the challenges in those networks.
Authors
Jorge Rabadan
Matthew Bocci
Sami Boutros
Ali Sajassi
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)