EVPN Vendor-Specific Route Type
draft-rabadan-bess-vendor-evpn-route-07
| Document | Type | Expired Internet-Draft (bess WG) | |
|---|---|---|---|
| Last updated | 2019-10-23 (latest revision 2019-04-21) | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | WG state | Candidate for WG Adoption | |
| 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-rabadan-bess-vendor-evpn-route-07.txt
Abstract
RFC7432 defines Ethernet VPN as a BGP address family that makes use of Typed NLRIs. IANA has a registry called "EVPN Route Types" that allocates values to Route Types. The purpose of this document is to solicit IANA the registration of a route type value for a vendor specific usage, as well as the definition of the EVPN NLRI for that route.
Authors
Jorge Rabadan
(jorge.rabadan@nokia.com)
Martin Vigoureux
(martin.vigoureux@nokia.com)
Mallika Gautam
(mallika.gautam@nokia.com)
Siddhesh Dindorkar
(siddhesh.dindorkar@nuagenetworks.net)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)