EVPN Vendor-Specific Route Type
draft-rabadan-bess-vendor-evpn-route-07
Document | Type |
Expired Internet-Draft
(bess WG)
Expired & archived
|
|
---|---|---|---|
Authors | Jorge Rabadan , Martin Vigoureux , Mallika Gautam , Siddhesh Dindorkar | ||
Last updated | 2019-10-23 (Latest revision 2019-04-21) | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | Candidate for WG Adoption | |
Document shepherd | (None) | ||
IESG | IESG state | Expired | |
Consensus boilerplate | Unknown | ||
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.)