EVPN Vendor-Specific Route Type
draft-rabadan-bess-vendor-evpn-route-05
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Jorge Rabadan , Martin Vigoureux , Mallika Gautam , Siddhesh Dindorkar | ||
| Last updated | 2018-10-11 (Latest revision 2018-04-09) | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| 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) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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
Martin Vigoureux
Mallika Gautam
Siddhesh Dindorkar
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)