EVPN control plane for Geneve
draft-ietf-bess-evpn-geneve-01
| Document | Type | Expired Internet-Draft (bess WG) | |
|---|---|---|---|
| Authors | Sami Boutros , Ali Sajassi , John Drake , Jorge Rabadan , Sam Aldrin | ||
| Last updated | 2020-12-14 (latest revision 2020-06-12) | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-bess-evpn-geneve-01.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 for NVO3 solutions. EVPN control plane can also be used by a Network Virtualization Endpoints (NVEs) to express Geneve tunnel option TLV(s)supported in transmission and/or reception of Geneve encapsulated data packets.
Authors
Sami Boutros
(sboutros@ciena.com)
Ali Sajassi
(sajassi@cisco.com)
John Drake
(jdrake@juniper.net)
Jorge Rabadan
(jorge.rabadan@nokia.com)
Sam Aldrin
(aldrin.ietf@gmail.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)