EVPN control plane for Geneve
draft-ietf-bess-evpn-geneve-06
| Document | Type |
Expired Internet-Draft
(bess WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Sami Boutros , Ali Sajassi , John Drake , Jorge Rabadan , Sam Aldrin | ||
| Last updated | 2023-11-27 (Latest revision 2023-05-26) | ||
| Replaces | draft-boutros-bess-evpn-geneve | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Waiting for Implementation | |
| Document shepherd | Matthew Bocci | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | matthew.bocci@nokia.com |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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 Network Virtualization Edges (NVEs) to express Geneve tunnel option TLV(s) supported in the transmission and/or reception of Geneve encapsulated data packets.
Authors
Sami Boutros
Ali Sajassi
John Drake
Jorge Rabadan
Sam Aldrin
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)