EVPN control plane for Geneve
draft-boutros-bess-evpn-geneve-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Sami Boutros , Ali Sajassi , John Drake | ||
| Last updated | 2017-12-22 (Latest revision 2017-06-20) | ||
| Replaced by | draft-ietf-bess-evpn-geneve | ||
| Stream | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
https://www.ietf.org/archive/id/draft-boutros-bess-evpn-geneve-00.txt
Abstract
This document describes how Ethernet VPN (EVPN) control plane can be used with Network Virtualization Overlay over Layer 3 (NVO3) Generic Network Virtualization Encapsulation (Geneve) encapsulation in NVO3 solutions. EVPN control plane can be used by a Network Virtualization Endpoints (NVEs) to express as well what Geneve tunnel option TLV(s) that they can transmit and/or receive.
Authors
Sami Boutros
Ali Sajassi
John Drake
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)